Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0023156 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Localization Pack: Spain] AEAT 340 | minor | always | 2013-02-25 11:13 | 2013-02-25 13:28 | |||||||
Reporter | egoitz | View Status | public | |||||||||
Assigned To | vmromanos | |||||||||||
Priority | high | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Regression date | ||||||||||||
Regression introduced by commit | ||||||||||||
Regression level | ||||||||||||
Review Assigned To | ||||||||||||
Regression introduced in release | ||||||||||||
Summary | 0023156: The 340 report should be designed to be able to define new javas to be executed for periods | |||||||||||
Description | Right now is hardcoded with java should be executed depending the year. A better design should be to have the possibility to define which java to use on each year. It will simplify the maintenance. In this way you could publish a new module for a new year instead of publishing a new release of the module. | |||||||||||
Steps To Reproduce | - | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Issue History | |||
Date Modified | Username | Field | Change |
2013-02-25 11:13 | egoitz | New Issue | |
2013-02-25 11:13 | egoitz | Assigned To | => vmromanos |
2013-02-25 13:25 | psanjuan | Summary | The 340 report should be designed to be ablo to define new javas to be executed for periods => The 340 report should be designed to be able to define new javas to be executed for periods |
Copyright © 2000 - 2009 MantisBT Group |