[
http://jira.codehaus.org/browse/MNBMODULE-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint closed MNBMODULE-31.
---------------------------------
Resolution: Won't Fix
not sure what can be done on our side (the nbm-plugin), the error seems to be
somewhere in the maven core and how it handles plugins with extensions. closing
with "wontfix" resolution.
As a workaround in 3.1 of the plugin, you could setup the nbm projects as
"jar" packaging, just with a bit more configuration in the pom, resulting in
not needing the <extensions>true</extensions> element in the plugin definition.
> Different behaviour when building from different root projects
> --------------------------------------------------------------
>
> Key: MNBMODULE-31
> URL: http://jira.codehaus.org/browse/MNBMODULE-31
> Project: Maven 2.x Netbeans Module Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Johan Andrén
> Assignee: Milos Kleint
> Fix For: 3.1
>
>
> We have a project structure where the netbeans platform application is not
> the root project, something like this
> masterproject
> -- netbeansplatform app
> ----suite1
> ----suite2
> ------module1
> ------module2
> All subprojects are setup as modules in the parent maven projects.
> When we build from the netbeansplatform app all modules are deployed as
> jar-files to the maven repository, but when we run from the masterproject the
> nbm-files instead of the jars are deployed. Since we have intermodule
> dependencies this makes the build fail.
> Not sure about what project information to attach to the issue to help
> resolve this.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
