There is an open issue in NMaven to investigate the problem of conflicting packaging names : http://jira.codehaus.org/browse/NMAVEN-65. The most likely solution is to change the packaging name to include a dotnet: identifier; so instead of "library", we would use "dotnet:library".
Shane On 6/13/07, Peter Nilsson <[EMAIL PROTECTED]> wrote:
Renaming the packagings that conflict is probably the short-term workaround we will have to use. I like your way of setting all lifecycle mappings in a new project and not specify the existing plugins as extensions. That way I don't have to modify any third party plugins. When browsing around JIRA I find multiple issues that seem the address the same or a similar problem, eg http://jira.codehaus.org/browse/MNG-1949 So I guess it is a well known issue. Peter -----Original Message----- From: Tom Huybrechts [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 5:15 PM To: Maven Users List Subject: Re: Inteference between multiple plugins with extensions I've had a problem using different extension plugins that contribute a lifecycle in one multi-module project. My workaround has been to copy the contents of the components.xml for each lifecycle I need into a single separate maven-lifecycle-plugin. I only specify this plugin as an extension, and that fixes it for me. If you have the same packaging name mapped several times, you might need to give it different names. Tom On 6/12/07, Peter Nilsson <[EMAIL PROTECTED]> wrote: > Hi, > > We are using Maven 2.0.6 to build both Java, C++ and C#. > C++ is built with the help of maven-native-plugin and C# with NMaven. > > Our project tree has the following structure: > > Top > Cpp > Project_A > Project_B > CS > Project_C > Project_D > > The problem we encounter is that while C# and C++ builds work fine on their own it will fail if the same build command tries to build both C++ and C#. > Ie, running "mvn install" in project "Cpp" or "CS" works but not doing it in project "Top". > > One hypothesis we have is that the components.xml files in the maven-native-plugin and NMaven plugins map the same packaging but to different goals and for some reason these mappings interfere with each other even though the plugins are not being used in the same project. > Project_A and Project_B in the example above only use the maven-native-plugin while Project_C and Project_D only use NMaven plugins. > > Can anybody confirm that the declared lifecycle mappings (in components.xml) for one plugin can have effect outside of the projects where this plugin is being used? > > If this is the case, is this a known bug? Is there any workaround? > > TIA, > > Peter > > > > ________________________________ > This e-mail is confidential and may contain legally privileged information. It is intended only for the addressees. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message from your system. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
