[JAVAMONEY-106] Clarify and document RI on JavaMoney page Created: 13/May/15  Updated: 31/Jul/15

Status: In Progress
Project: javamoney
Component/s: General: Build and quality management, Impl: RI
Affects Version/s: 1.0
Fix Version/s: 1.0.1

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

Tags: documentation, website

 Description   

While jcp.org will provide download links to official releases, many people likely will either use Maven settings or visit JavaMoney.org.

There http://javamoney.github.io/ri.html RI/Moneta is still presented as "1.0-RC1" and there's no clarification about 2 flavors of the RI for Java SE 8 or above and the still more widely expected one running SE 6/7, Android or Java ME.

This should be clarified and explained in the Readme.






[JAVAMONEY-104] Make coverage visible on all key artifacts Created: 13/May/15  Updated: 23/Aug/15

Status: Open
Project: javamoney
Component/s: API, General: Build and quality management, Impl: RI, Test: TCK
Affects Version/s: 1.0
Fix Version/s: 1.0.1

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

Issue Links:
Related
is related to JAVAMONEY-125 Add missing tests Open
Tags: coverage, test

 Description   

Considerable effort was spent on increasing code coverage recently. Similar to the public API: https://github.com/JavaMoney/jsr354-api (showing 76% that's not bad, unless you're into safety critical software even corporate projects often don't insist on more than 60 or 70%) its BP and all other major artifacts (RI+RI-BP as well as TCK where applicable) should present theirs, too. API-BP has a badge, but no Coveralls profile seems to exist. Where missing, those should be created.






[JAVAMONEY-90] Try to find a workable solution for Snapshots Created: 11/Feb/15  Updated: 31/Mar/15  Resolved: 31/Mar/15

Status: Closed
Project: javamoney
Component/s: General: Build and quality management
Affects Version/s: 0.9
Fix Version/s: None

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

Tags: build, snapshot

 Description   

As of now the Snapshot repository formerly at CloudBees is inactive or deleted. The current Travis CI build runs the default Maven job and cannot find a Snapshot version of the API once the "head" of the API project changes:
317[ERROR] Failed to execute goal on project moneta: Could not resolve dependencies for project org.javamoney:moneta:jar:1.0-SNAPSHOT: Could not find artifact javax.money:money-api:jar:1.0-SNAPSHOT in sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots/) -> [Help 1]

Ideally whenever at least API, RI and TCK change, a Snapshot repo like https://oss.sonatype.org/content/repositories/snapshots/ shall be automatically deployed to, otherwise some substitute like Cloudbees, as long as POM settings allow Maven to find it.



 Comments   
Comment by atsticks [ 31/Mar/15 ]

Changed to jfrog/BintrAY build.





[JAVAMONEY-49] Enable Sonar static Quality Checks and fix findings Created: 08/Aug/13  Updated: 05/Feb/15  Resolved: 29/Jan/15

Status: Closed
Project: javamoney
Component/s: General: Build and quality management
Affects Version/s: 0.1.0, 0.2.0, 0.3, 0.4-EDR1
Fix Version/s: 1.0

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


 Description   

Enable Sonar static analysis on the whole JSR code base and fix/discuss the findings, where useful.



 Comments   
Comment by atsticks [ 29/Jan/15 ]

Done, look at nemo.sonarsource.org





[JAVAMONEY-41] Consolidate Logging Frameworks Created: 27/Apr/13  Updated: 10/Mar/14  Resolved: 10/Mar/14

Status: Closed
Project: javamoney
Component/s: General: Build and quality management
Affects Version/s: 0.4-EDR1
Fix Version/s: 0.8

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

Tags: logging

 Description   

Various components use different logging frameworks, including

  • java.util.logging
  • SLF4J
  • Log4J

Except for those parts where only the JDK build in java.util.logging API shall be used to avoid 3rd party dependencies, all others should use SLF4J. Its bridge also to java.util.logging allows a unified logging better than direct calls to individual APIs.



 Comments   
Comment by keilw [ 02/Mar/14 ]

Is this done?

Comment by atsticks [ 10/Mar/14 ]
  • Currently API, RI and TCK only use JUL.
  • JavaMoney Library I think uses only slf4j

The JSR related parts so are clean at least.





Extended JSR Scope (JAVAMONEY-23)

[JAVAMONEY-32] Separate platform aspects from advanced features. Created: 16/Feb/13  Updated: 10/Nov/13  Due: 01/Mar/13  Resolved: 27/Apr/13

Status: Closed
Project: javamoney
Component/s: General: Build and quality management, Impl: RI, Spec: Specification
Affects Version/s: 0.3
Fix Version/s: 0.4-EDR1

Type: Sub-task Priority: Major
Reporter: atsticks Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days


 Description   

Separate platform aspects from advanced features. Ensure separation also within other area, e.g.

  • specification
  • JIRA
  • etc.

Discuss details in next EG meeting.






[JAVAMONEY-29] Consider changing Artifact Name Created: 06/Feb/13  Updated: 08/Aug/13  Resolved: 06/Feb/13

Status: Closed
Project: javamoney
Component/s: General: Build and quality management
Affects Version/s: 0.1.0
Fix Version/s: 0.2.0

Type: Improvement Priority: Major
Reporter: keilw Assignee: keilw
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: 0 minutes

Tags: maven

 Description   

Based on most JSRs published by Maven with an "*-api" artifact naming pattern, we should try to drop the "java".
While the project name is fine, under "javax.money" ideally it should just say "money-api", similar to

  • javax.persistence
  • javax.validation
  • javax.portlet
    etc.





Generated at Sat Feb 06 20:56:42 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.