[JAVAMONEY-85] Tag releases when something is published to repo Created: 06/Feb/15  Updated: 06/Feb/15

Status: In Progress
Project: javamoney
Component/s: API, Impl: RI, Test: TCK
Affects Version/s: 0.9
Fix Version/s: 1.0

Type: Task Priority: Major
Reporter: keilw Assignee: keilw
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: deployment, release

 Description   

At least the milestone build 1.0-RC1 was published to MavenCentral, but no corresponding release tags could be found in any of the GitHub repositories.
It would be cumbersome to roll everything back and re-create such tag for 1.0-RC1, but for the current build 1.0-RC2 all necessary tags shall be created ASAP and ideally in future let's try to do this BEFORE publishing






[JAVAMONEY-83] Change key type in Contexts/Queries to String Created: 02/Feb/15  Updated: 05/Feb/15  Resolved: 05/Feb/15

Status: Closed
Project: javamoney
Component/s: API, Impl: RI, Spec: Specification, Test: TCK
Affects Version/s: 0.9
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: atsticks Assignee: atsticks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day


 Description   

Change key type in Contexts/Queries to String (currently it is Object). This reduces the complexity of the context class and its builders drastically.



 Comments   
Comment by atsticks [ 05/Feb/15 ]

Fixed in 1.0-RC2.





[JAVAMONEY-57] Copy and adapt tests from RI/API that are suitable to the TCK Created: 08/Aug/13  Updated: 02/Sep/14  Resolved: 02/Sep/14

Status: Closed
Project: javamoney
Component/s: Test: TCK
Affects Version/s: None
Fix Version/s: 0.9

Type: Task Priority: Major
Reporter: atsticks Assignee: atsticks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Copy and adapt tests from RI/API that are suitable to the TCK, e.g. for MonetaryAmount. Adapt the tests so the TCK configuration is considered, e.g. testing all MonetaryAmount classes configured.






[JAVAMONEY-56] Define TCK - reference implementation integration Created: 08/Aug/13  Updated: 02/Sep/14  Resolved: 02/Sep/14

Status: Closed
Project: javamoney
Component/s: Test: TCK
Affects Version/s: None
Fix Version/s: 0.9

Type: Task Priority: Major
Reporter: atsticks Assignee: atsticks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Define how the TCK must be setup, so it is able to test an arbitrary reference implementation of the JSR. This may include:

  • locate the jars containing the implementation
  • configuring the environment type (SE,EE) to be tested
  • configuring the implementation classes for MonetaryAmount and CurrencyUnit.


 Comments   
Comment by atsticks [ 10/Mar/14 ]

Basically this is done. Nevertheless the current TCK test Suite must be decoupled from the execution module itself, as a TCK testing library. An according test Suite must be provided that then can be easily called from the effective TCK running Project. Integration of the implementation to test will mainly happenthrough maven properties defining the dep reqauired.

Comment by atsticks [ 02/Sep/14 ]

There is a TCK user guide describing, what must be done. Additionally there is a GitHub project, testing the integration.





[JAVAMONEY-55] Define the areas and topics to be tested by the TCK Created: 08/Aug/13  Updated: 02/Sep/14  Resolved: 02/Sep/14

Status: Closed
Project: javamoney
Component/s: Test: TCK
Affects Version/s: None
Fix Version/s: 0.9

Type: Task Priority: Major
Reporter: atsticks Assignee: atsticks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 3 days
Time Spent: Not Specified
Original Estimate: 3 days


 Description   

The TCK contains an XML structure that must reflect the areas and topics to be tested by the TCK. The test within the TCK reference these names, so in the overall TCK output it is clear and simple what areas of a reference implementation is compatible and which not.
This XML definition must be filled with the data relevant to this JSR.

Additionally the Tasks defined in test-Audit.xml should be prepared on JUni site also for easier Integration with possible external contributors.






Generated at Sat Apr 18 21:07:05 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.