You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2008/12/02 20:44:19 UTC
[jira] Created: (MASSEMBLY-372) Maven with attached assembies and
manually invoked in one step
Maven with attached assembies and manually invoked in one step
--------------------------------------------------------------
Key: MASSEMBLY-372
URL: http://jira.codehaus.org/browse/MASSEMBLY-372
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Environment: XP SP2, Maven 2.0.9, JDK 6 u10
Reporter: Michael Osipov
Attachments: error.log, testproject.zip
This is what I tried to realize:
I have a very simple project. I wanted to create besides the regular jar and a jar with depencies. After both have been created, I wanted to create an assembly along with some other fies.
What I did:
I attached assembly:attached to phase package with descriptorRef "jar-with-depencies" and configured the assembly a bin assembly which will be invoked manually.
Well, it failed. According th Benjamin Bentmann on IRC, he advised me to create a profile to build the bin assembly. Guess what? It works if invoke:
{noformat}
$mvn package
$mvn assembly:assembly -Pbin-assembly
{noformat}
Well, I want run it rather in one step: mvn clean package assembly:assembly -Pbin-assembly. This fails with the attached log above. I also attached my project.
I expect during the one call that my package, attachment and bin assembly will be build as expected.
The log says, the descriptors are messed up.
--
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] Issue Comment Edited: (MASSEMBLY-372) Maven with attached
assembies and manually invoked in one step
Posted by "Michael Osipov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156344#action_156344 ]
Michael Osipov edited comment on MASSEMBLY-372 at 12/2/08 1:49 PM:
-------------------------------------------------------------------
.
was (Author: sgfan):
You may even move the profile configuration back to the plugin config and the result remains the same.
> Maven with attached assembies and manually invoked in one step
> --------------------------------------------------------------
>
> Key: MASSEMBLY-372
> URL: http://jira.codehaus.org/browse/MASSEMBLY-372
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: XP SP2, Maven 2.0.9, JDK 6 u10
> Reporter: Michael Osipov
> Attachments: error.log, testproject.zip
>
>
> This is what I tried to realize:
> I have a very simple project. I wanted to create besides the regular jar and a jar with depencies. After both have been created, I wanted to create an assembly along with some other fies.
> What I did:
> I attached assembly:attached to phase package with descriptorRef "jar-with-depencies" and configured the assembly a bin assembly which will be invoked manually.
> Well, it failed. According th Benjamin Bentmann on IRC, he advised me to create a profile to build the bin assembly. Guess what? It works if invoke:
> {noformat}
> $mvn package
> $mvn assembly:assembly -Pbin-assembly
> {noformat}
> Well, I want run it rather in one step: mvn clean package assembly:assembly -Pbin-assembly. This fails with the attached log above. I also attached my project.
> I expect during the one call that my package, attachment and bin assembly will be build as expected.
> The log says, the descriptors are messed up.
--
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: (MASSEMBLY-372) Maven with attached assembies and
manually invoked in one step
Posted by "Michael Osipov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156344#action_156344 ]
Michael Osipov commented on MASSEMBLY-372:
------------------------------------------
You may even move the profile configuration back to the plugin config and the result remains the same.
> Maven with attached assembies and manually invoked in one step
> --------------------------------------------------------------
>
> Key: MASSEMBLY-372
> URL: http://jira.codehaus.org/browse/MASSEMBLY-372
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: XP SP2, Maven 2.0.9, JDK 6 u10
> Reporter: Michael Osipov
> Attachments: error.log, testproject.zip
>
>
> This is what I tried to realize:
> I have a very simple project. I wanted to create besides the regular jar and a jar with depencies. After both have been created, I wanted to create an assembly along with some other fies.
> What I did:
> I attached assembly:attached to phase package with descriptorRef "jar-with-depencies" and configured the assembly a bin assembly which will be invoked manually.
> Well, it failed. According th Benjamin Bentmann on IRC, he advised me to create a profile to build the bin assembly. Guess what? It works if invoke:
> {noformat}
> $mvn package
> $mvn assembly:assembly -Pbin-assembly
> {noformat}
> Well, I want run it rather in one step: mvn clean package assembly:assembly -Pbin-assembly. This fails with the attached log above. I also attached my project.
> I expect during the one call that my package, attachment and bin assembly will be build as expected.
> The log says, the descriptors are messed up.
--
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: (MASSEMBLY-372) Maven with attached assembies and
manually invoked in one step
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-372.
--------------------------------
Resolution: Won't Fix
Assignee: John Casey
use assembly:single goal and bind separate plugin executions to the build lifecycle according to the order in which you want them to run. Then, you can use <attachmentClassifier> + <useProjectArtifacts> in your dependencySet to gain access to previously-built assemblies for inclusion in subsequent ones.
> Maven with attached assembies and manually invoked in one step
> --------------------------------------------------------------
>
> Key: MASSEMBLY-372
> URL: http://jira.codehaus.org/browse/MASSEMBLY-372
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: XP SP2, Maven 2.0.9, JDK 6 u10
> Reporter: Michael Osipov
> Assignee: John Casey
> Attachments: error.log, testproject.zip
>
>
> This is what I tried to realize:
> I have a very simple project. I wanted to create besides the regular jar and a jar with depencies. After both have been created, I wanted to create an assembly along with some other fies.
> What I did:
> I attached assembly:attached to phase package with descriptorRef "jar-with-depencies" and configured the assembly a bin assembly which will be invoked manually.
> Well, it failed. According th Benjamin Bentmann on IRC, he advised me to create a profile to build the bin assembly. Guess what? It works if invoke:
> {noformat}
> $mvn package
> $mvn assembly:assembly -Pbin-assembly
> {noformat}
> Well, I want run it rather in one step: mvn clean package assembly:assembly -Pbin-assembly. This fails with the attached log above. I also attached my project.
> I expect during the one call that my package, attachment and bin assembly will be build as expected.
> The log says, the descriptors are messed up.
--
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