You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/09/01 22:24:32 UTC
[jira] Created: (MNG-4788) [regression] Appassembler Maven Plugin
doesn't work like as it should
[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
[jira] Commented: (MNG-4788) [regression] Appassembler Maven Plugin
doesn't work like as it should
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233981#action_233981 ]
Brett Porter commented on MNG-4788:
-----------------------------------
in my recollection, the appassembler plugin looks up a custom ArtifactRepositoryLayout 'flat' that it defines itself, then uses the standard APIs to populate it. I would suppose Aether doesn't support other repository layouts at this time since the legacy one had been removed.
> [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
> Attachments: MNG-4788.zip
>
>
> 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
[jira] Closed: (MNG-4788) [regression] Appassembler Maven Plugin
doesn't work like as it should
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4788.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta-4
Assignee: Benjamin Bentmann
Fixed in [r995272|http://svn.apache.org/viewvc?view=revision&revision=995272].
> [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
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-4
>
> Attachments: MNG-4788.zip
>
>
> 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
[jira] Commented: (MNG-4788) [regression] Appassembler Maven Plugin
doesn't work like as it should
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235006#action_235006 ]
Dennis Lundberg commented on MNG-4788:
--------------------------------------
I just wanted to confirm that this has been fixed in trunk. I tried it on my own project and it works as expected now using a freshly built Maven 3.0-SNAPSHOT.
> [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
> Assignee: Benjamin Bentmann
> Fix For: 3.0-beta-4
>
> Attachments: MNG-4788.zip
>
>
> 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
[jira] Updated: (MNG-4788) [regression] Appassembler Maven Plugin
doesn't work like as it should
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MNG-4788:
---------------------------------
Attachment: MNG-4788.zip
Minimal project that shows this issue.
> [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
> Attachments: MNG-4788.zip
>
>
> 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