DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42168>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42168 Summary: [PATCH] have the build produce maven2 bundles Product: Batik Version: 1.7 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Utilities AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Would it be possible to generate maven2 bundles as part of the build, so that it is easy to get them deployed into the official repositories. Having the bundle produced as part of the official release process would help avoid the disaster of the 1.6 bundles. I have a patch to the build that adds a mvnbundle target which produces a batik-all-VERSION-bundle.jar, which contains the batik-all jar as well as javadocs and source code. I made all the dependencies optional except the xml-apis stuff. For more information on the bundle structure: http://maven.apache.org/guides/mini/guide-ibiblio-upload.html I set the groupId to org.apache.batik - this is inconsistent with the previous 1.6/1.6-1 bundle, which had groupId=batik. However the mistake lies with 1.6/1.6-1 and it is imho better to fix it now than later. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
