Wildcards don't preserve jar order. If your classpath ends up with mutliple jars and the order matters, then you have problems.
On Sun, Jun 8, 2014 at 5:30 AM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > Hi Benson, > > there is an option to use short path names: > > http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/assemble-mojo.html#useWildcardClassPath > > Will that help? > > Kind regards > Karl-Heinz Marbaise > > On 6/7/14 11:17 PM, Benson Margulies (JIRA) wrote: >> >> Benson Margulies >> <https://jira.codehaus.org/secure/ViewProfile.jspa?name=bmargulies> >> *created* an issue >> >> >> Mojo's AppAssembler Maven Plugin >> <https://jira.codehaus.org/browse/MAPPASM> / Improvement >> <https://jira.codehaus.org/browse/MAPPASM-231> MAPPASM-231 >> <https://jira.codehaus.org/browse/MAPPASM-231> >> >> Use manifest-only jars for classpath >> <https://jira.codehaus.org/browse/MAPPASM-231> >> >> Issue Type: Improvement Improvement >> Assignee: Unassigned >> Created: 07/Jun/14 4:16 PM >> Priority: Major Major >> Reporter: Benson Margulies >> <https://jira.codehaus.org/secure/ViewProfile.jspa?name=bmargulies> >> >> >> All the messes with Windows pathname limitations and the ordering >> problems with wildcards could be eliminated by a manifest-only jar. >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
