Issue Details (XML | Word | Printable)

Key: METRO-19
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Martin Grebac
Reporter: gmazza
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
metro

Move buildnumber-maven-plugin into a separate Maven profile.

Created: 13/Dec/12 08:20 PM   Updated: 14/Dec/12 07:32 AM   Resolved: 14/Dec/12 07:32 AM
Component/s: code
Affects Version/s: current
Fix Version/s: 2.3

Time Tracking:
Not Specified

Tags:
Participants: gmazza and Martin Grebac


 Description  « Hide

The bottom of each Metro download page for a specific Metro version gives a Subversion URL to check out the source code for hacking/debugging our web services. For example, bottom of here: http://metro.java.net/2.2.1-1/ tells us to run "svn export https://svn.java.net/svn/wsit~svn/tags/2.2.1-1 -r 7272 metro-sources". However, we cannot presently build the project via "mvn clean package" or import the project into our Eclipse IDE via "mvn eclipse:eclipse" because of the buildnumber-maven-plugin defined in metro-sources/pom.xml. Unless I comment out that plugin, I get this error:

"[ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create (default) on project metro-project: Cannot get the revision information from the scm repository :
[ERROR] Exception while executing SCM command. svn: '/media/work1/blog-samples/metro-sources' is not a working copy"

If I comment-out this plugin, the build works fine. I suspect this plugin is primarily for the Oracle team when they're making their new releases, not for the ordinary users who want to debug their Metro web services using Metro sources. I recommend placing this particular plugin in a new Maven profile, inactive by default, so your Oracle team can activate the profile for your work while letting the regular community run "mvn clean install" etc. to quickly get the sources built. Thanks!



Martin Grebac added a comment - 14/Dec/12 07:32 AM

Added <revisionOnScmFailure>false</revisionOnScmFailure> to the plugin config, so this should be solved within next release.