[
https://jira.jboss.org/jira/browse/JBBUILD-472?page=com.atlassian.jira.pl...
]
Andrew Lee Rubinger commented on JBBUILD-472:
---------------------------------------------
Justin:
Recommend you raise this issue at
https://lists.jboss.org/mailman/listinfo/jboss-development, asking for a new release.
That'll get visibility to whomever is all parties coordinating (including Paul Gier,
the lead of JBBUILD), and it's good to show community involvement interested in dev.
S,
ALR
Maven JBoss Retro-produced jar has full paths
---------------------------------------------
Key: JBBUILD-472
URL:
https://jira.jboss.org/jira/browse/JBBUILD-472
Project: JBoss Build System
Issue Type: Bug
Components: maven-jboss-retro-plugin
Affects Versions: jboss-retro-maven-plugin-0.5.GA
Environment: Win XP.
Reporter: Justin Edelson
Priority: Critical
Fix For: maven-jboss-retro-plugin-1.0
Attachments: JBBUILD-472.patch
I have a project that uses the jboss-retro-maven-plugin to produce a 1.4-compatible JAR.
When I run my build on a Windows PC (XP SP2), the generated JAR has the full path in each
entry:
C:\home\devel\CoreLib\target>jar -tf CoreLib-jdk14.jar
META-INF/MANIFEST.MF
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\exceptions\UCSARuntimeException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\Context$ScopeMap.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\Context.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\GlobalIdException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\InternalException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\ParseException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\exception\ResolverException.class
C:\home\devel\CoreLib\target\classes-retro\com\mtvi\ucsa\uri\mgid\IdElement.class
...
I suspect there is an easy fix for this, presuambly just a hardcoded "/"
instead of getting the file separator.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira