Netbeans profile causes mojos to execute twice
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Netbeans profile causes mojos to execute twice
by Magne Nordtveit
::
Rate this Message:
Hello,
I just recently updated to version 3.1.1 of the mevenide plugin to Netbeans and ran into a little ... snag... Those projects that had a netbeans-public profile generated to be able to run/debug no longer built properly! I had a glance at the build plan, and discovered that the mojos were all executing twice, and thus crashing with the following error: [ERROR] [ERROR] [ERROR]Your build attempted to attach multiple artifacts with the same classifier to the main project. [ERROR] [ERROR]Mojo responsible for second attachment attempt:org.apache.maven.plugins:maven-source-plugin:2.0.4:jar [ERROR] [ERROR]Reported for project: [ERROR]Group-Id: no.offsim [ERROR]Artifact-Id: smallapp [ERROR]Version: 1.1-SNAPSHOT [ERROR]From file: /home/magne/work/source/smallapp/pom.xml [ERROR] [ERROR] [ERROR]Artifact attachment: [ERROR] [ERROR]Group-Id: no.offsim [ERROR]Artifact-Id: smallapp [ERROR]Version: 1.1-SNAPSHOT [ERROR]Type: java-source [ERROR]Scope: null [ERROR]Classifier: sources which is caused by the maven-source-plugin running twice and trying to attach two similar files smallapp-1.1-SNAPSHOT-sources.jar. Does anyone have a solution to this other than "Remove the netbeans profiles"? All the projects are created with the old simple archetype in netbeans 5.5-6.0.1 (Possibly in 6.1 too) and with mevenide 3.0.12 (and preceeding versions built on Maven 2.0.4). Cheers, Magne --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Netbeans profile causes mojos to execute twice
by Daniel Mutch
::
Rate this Message:
Try changing the goal in the profile from directory to directory-inline. This will prevent Maven from forking the process when it finds the assembly profile, which can have some unexpected concequences including building the project more than once. cheers Dan
|
|
|
Re: Netbeans profile causes mojos to execute twice
by Magne Nordtveit
::
Rate this Message:
Cheers, that did solve the problem without breaking anything. BUT I now
have a deprecated warning when I am building [WARN]DEPRECATED: Binding aggregator mojos to lifecycle phases in the POM is considered dangerous. [WARN]This feature has been deprecated. Please adjust your POM files accordingly. On Tue, 2008-05-13 at 17:20 -0700, Daniel Mutch wrote: > > Try changing the goal in the profile from directory to directory-inline. > This will prevent Maven from forking the process when it finds the assembly > profile, which can have some unexpected concequences including building the > project more than once. > > cheers > Dan > > > Magne Nordtveit-2 wrote: > > > > Hello, > > > > I just recently updated to version 3.1.1 of the mevenide plugin to > > Netbeans and ran into a little ... snag... Those projects that had a > > netbeans-public profile generated to be able to run/debug no longer > > built properly! I had a glance at the build plan, and discovered that > > the mojos were all executing twice, and thus crashing with the following > > error: > > > > [ERROR] > > [ERROR] > > [ERROR]Your build attempted to attach multiple artifacts with the same > > classifier to the main project. > > [ERROR] > > [ERROR]Mojo responsible for second attachment > > attempt:org.apache.maven.plugins:maven-source-plugin:2.0.4:jar > > [ERROR] > > [ERROR]Reported for project: > > [ERROR]Group-Id: no.offsim > > [ERROR]Artifact-Id: smallapp > > [ERROR]Version: 1.1-SNAPSHOT > > [ERROR]From file: /home/magne/work/source/smallapp/pom.xml > > [ERROR] > > [ERROR] > > [ERROR]Artifact attachment: > > [ERROR] > > [ERROR]Group-Id: no.offsim > > [ERROR]Artifact-Id: smallapp > > [ERROR]Version: 1.1-SNAPSHOT > > [ERROR]Type: java-source > > [ERROR]Scope: null > > [ERROR]Classifier: sources > > > > which is caused by the maven-source-plugin running twice and trying to > > attach two similar files smallapp-1.1-SNAPSHOT-sources.jar. > > > > Does anyone have a solution to this other than "Remove the netbeans > > profiles"? > > > > All the projects are created with the old simple archetype in netbeans > > 5.5-6.0.1 (Possibly in 6.1 too) and with mevenide 3.0.12 (and preceeding > > versions built on Maven 2.0.4). > > > > Cheers, > > Magne > > > > --------------------------------------------------------------------- > > 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 |
|
|
Re: Netbeans profile causes mojos to execute twice
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
I suggest you "upgrade" to the default way of running/debugging maven
projects in 3.1.x that includes running maven-exec-plugin rather than generating a custom profile with assembly+jar plugins configuration (thus the whole profile can be deleted altogether) Milos On 5/14/08, Magne Nordtveit <magne.nordtveit@...> wrote: > Cheers, that did solve the problem without breaking anything. BUT I now > have a deprecated warning when I am building > > [WARN]DEPRECATED: Binding aggregator mojos to lifecycle phases in the > POM is considered dangerous. > [WARN]This feature has been deprecated. Please adjust your POM files > accordingly. > > > On Tue, 2008-05-13 at 17:20 -0700, Daniel Mutch wrote: > > > > Try changing the goal in the profile from directory to directory-inline. > > This will prevent Maven from forking the process when it finds the assembly > > profile, which can have some unexpected concequences including building the > > project more than once. > > > > cheers > > Dan > > > > > > Magne Nordtveit-2 wrote: > > > > > > Hello, > > > > > > I just recently updated to version 3.1.1 of the mevenide plugin to > > > Netbeans and ran into a little ... snag... Those projects that had a > > > netbeans-public profile generated to be able to run/debug no longer > > > built properly! I had a glance at the build plan, and discovered that > > > the mojos were all executing twice, and thus crashing with the following > > > error: > > > > > > [ERROR] > > > [ERROR] > > > [ERROR]Your build attempted to attach multiple artifacts with the same > > > classifier to the main project. > > > [ERROR] > > > [ERROR]Mojo responsible for second attachment > > > attempt:org.apache.maven.plugins:maven-source-plugin:2.0.4:jar > > > [ERROR] > > > [ERROR]Reported for project: > > > [ERROR]Group-Id: no.offsim > > > [ERROR]Artifact-Id: smallapp > > > [ERROR]Version: 1.1-SNAPSHOT > > > [ERROR]From file: /home/magne/work/source/smallapp/pom.xml > > > [ERROR] > > > [ERROR] > > > [ERROR]Artifact attachment: > > > [ERROR] > > > [ERROR]Group-Id: no.offsim > > > [ERROR]Artifact-Id: smallapp > > > [ERROR]Version: 1.1-SNAPSHOT > > > [ERROR]Type: java-source > > > [ERROR]Scope: null > > > [ERROR]Classifier: sources > > > > > > which is caused by the maven-source-plugin running twice and trying to > > > attach two similar files smallapp-1.1-SNAPSHOT-sources.jar. > > > > > > Does anyone have a solution to this other than "Remove the netbeans > > > profiles"? > > > > > > All the projects are created with the old simple archetype in netbeans > > > 5.5-6.0.1 (Possibly in 6.1 too) and with mevenide 3.0.12 (and preceeding > > > versions built on Maven 2.0.4). > > > > > > Cheers, > > > Magne > > > > > > --------------------------------------------------------------------- > > > 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 > > > |
|
|
Re: Netbeans profile causes mojos to execute twice
by Magne Nordtveit
::
Rate this Message:
It was suppose to contain some more info in that mail, but my client
thought it would be a good idea to send it anyway... Is that the error that the directory-single goal is bypassing? Or am I miss understanding something? Magne On Wed, 2008-05-14 at 10:57 +0200, Magne Nordtveit wrote: > Cheers, that did solve the problem without breaking anything. BUT I now > have a deprecated warning when I am building > > [WARN]DEPRECATED: Binding aggregator mojos to lifecycle phases in the > POM is considered dangerous. > [WARN]This feature has been deprecated. Please adjust your POM files > accordingly. > > On Tue, 2008-05-13 at 17:20 -0700, Daniel Mutch wrote: > > > > Try changing the goal in the profile from directory to directory-inline. > > This will prevent Maven from forking the process when it finds the assembly > > profile, which can have some unexpected concequences including building the > > project more than once. > > > > cheers > > Dan > > > > > > Magne Nordtveit-2 wrote: > > > > > > Hello, > > > > > > I just recently updated to version 3.1.1 of the mevenide plugin to > > > Netbeans and ran into a little ... snag... Those projects that had a > > > netbeans-public profile generated to be able to run/debug no longer > > > built properly! I had a glance at the build plan, and discovered that > > > the mojos were all executing twice, and thus crashing with the following > > > error: > > > > > > [ERROR] > > > [ERROR] > > > [ERROR]Your build attempted to attach multiple artifacts with the same > > > classifier to the main project. > > > [ERROR] > > > [ERROR]Mojo responsible for second attachment > > > attempt:org.apache.maven.plugins:maven-source-plugin:2.0.4:jar > > > [ERROR] > > > [ERROR]Reported for project: > > > [ERROR]Group-Id: no.offsim > > > [ERROR]Artifact-Id: smallapp > > > [ERROR]Version: 1.1-SNAPSHOT > > > [ERROR]From file: /home/magne/work/source/smallapp/pom.xml > > > [ERROR] > > > [ERROR] > > > [ERROR]Artifact attachment: > > > [ERROR] > > > [ERROR]Group-Id: no.offsim > > > [ERROR]Artifact-Id: smallapp > > > [ERROR]Version: 1.1-SNAPSHOT > > > [ERROR]Type: java-source > > > [ERROR]Scope: null > > > [ERROR]Classifier: sources > > > > > > which is caused by the maven-source-plugin running twice and trying to > > > attach two similar files smallapp-1.1-SNAPSHOT-sources.jar. > > > > > > Does anyone have a solution to this other than "Remove the netbeans > > > profiles"? > > > > > > All the projects are created with the old simple archetype in netbeans > > > 5.5-6.0.1 (Possibly in 6.1 too) and with mevenide 3.0.12 (and preceeding > > > versions built on Maven 2.0.4). > > > > > > Cheers, > > > Magne > > > > > > --------------------------------------------------------------------- > > > 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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Newbie Questions
by Aaron Metzger
::
Rate this Message:
Is there a FAQ for mevenide? I'm using mevenide 3.1.1 in NetBeans 6.1. I have a simple maven 2 project which builds fine outside of NetBeans using "mvn clean install" on the command line with either maven 2.0.8 or maven 2.0.9 but fails to build inside of NetBeans when I choose "Build / Clean and Build" from the main menu. The error message is a very specific maven error message about my use of the GWT plugin "gwt:generateClientBeans doesn't have a default lifecycle phase. Please specify a <phase /> for this goal in your POM.". I intend to futz around with my POM to try to satisfy whatever it is complaining about but my real question is: What do I have to do to expect that any maven projects which build fine on the command line using maven 2.0.9 will also have a chance of building using NetBeans and mevenide? Does the embedded maven in mevenide lag behind the 2.0.9 or is it actually doing better error checking and complaining about a real error in my POM that maven 2.0.9 didn't catch? Is there a way to tell mevenide to use the externally installed maven 2.0.9 and associated ".m2" directory so that I know they are in sync? I look forward to being able to build my maven projects both inside of and outside of NetBeans using identical POMs. Thanks for any advice you can give. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Newbie Questions
by Bugzilla from mkleint@gmail.com
::
Rate this Message:
On 5/14/08, Aaron Metzger <ametzger@...> wrote:
> > Is there a FAQ for mevenide? http://mevenide.codehaus.org/m2-site/faq.html but it's not uptodate with regard to 3.1.1 > > I'm using mevenide 3.1.1 in NetBeans 6.1. I have a simple maven 2 project > which builds fine outside of NetBeans using "mvn clean install" on the > command line with either maven 2.0.8 or maven 2.0.9 but fails to build > inside of NetBeans when I choose "Build / Clean and Build" from the main > menu. The error message is a very specific maven error message about my use > of the GWT plugin "gwt:generateClientBeans doesn't have a default lifecycle > phase. Please specify a <phase /> for this goal in your POM.". > > I intend to futz around with my POM to try to satisfy whatever it is > complaining about but my real question is: What do I have to do to expect > that any maven projects which build fine on the command line using maven > 2.0.9 will also have a chance of building using NetBeans and mevenide? Does > the embedded maven in mevenide lag behind the 2.0.9 or is it actually doing > better error checking and complaining about a real error in my POM that > maven 2.0.9 didn't catch? well, it's 2.1-SNAPSHOT (from april or march) which means it's not 100% the same codebase as 2.0.9. Unfortunately 2.0.x is not embeddable. IMHO it's not doing a good job at being backward compatible. It fails miserably when you declare RELEASE or LATEST version in your pom for example. Your problem seems to be another similar problem. > > Is there a way to tell mevenide to use the externally installed maven 2.0.9 > and associated ".m2" directory so that I know they are in sync? yes, you can go to Tools/Options dialog and in the Miscellaneous/Maven2 panel, setup the command line maven instance for use in building. You can set it to be the default for all projects there or select some projects selectively only (that would be in project customizer then) hope that helps. Milos > > I look forward to being able to build my maven projects both inside of and > outside of NetBeans using identical POMs. > > Thanks for any advice you can give. > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > 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 |
| Free embeddable forum powered by Nabble | Forum Help |
