[regression] Appassembler Maven Plugin doesn't work like as it should
---------------------------------------------------------------------
Key: MNG-4788
URL: http://jira.codehaus.org/browse/MNG-4788
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0-beta-3
Environment: The 3.0-beta-3 that is staged for release.
Reporter: Dennis Lundberg
Comparing the results between beta-2 and beta-3 I see a difference in my builds
for the Appassembler Maven Plugin (@mojo.codehaus.org). In beta-2 the plugin
(correctly) assembles the dependencies in a flat structure in my configured
"lib" directory. Whereas beta-3 puts the dependencies in my configured "lib"
directory using a Maven repository layout structure.
Example in beta 2:
{noformat}
[INFO] Installing C:\Documents and
Settings\dlg01\.m2\repository\commons-dbutils\commons-dbutils\1.1\commons-dbutils-1.1.jar
to
C:\Program\apache-continuum\data\working-directory\15\dennislundberg-beansprout\target\appassembler\lib\commons-dbutils-1.1.jar
{noformat}
Example in beta 3:
{noformat}
[INFO] Installing C:\Documents and
Settings\dlg01\.m2\repository\commons-dbutils\commons-dbutils\1.1\commons-dbutils-1.1.jar
to
C:\Program\apache-continuum\data\working-directory\15\dennislundberg-beansprout\target\appassembler\lib\commons-dbutils\commons-dbutils\1.1\commons-dbutils-1.1.jar
{noformat}
The result is that the assembled apps gets an invalid classpath and won't start.
Test case coming soon.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
