[
https://jira.codehaus.org/browse/MNBMODULE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275999#comment-275999
]
Jesse Glick commented on MNBMODULE-135:
---------------------------------------
Making the project subdirectories be named according to the parent prefix is
probably not possible, as Maven Archetypes Plugin provides no way to do this in
a {{fileSet}} (you can only use {{packaged="true"}} to insert a package
prefix). But there is no rule that a (Maven) module's dir must be named
according to its {{artifactId}}; that is just a convention.
> When creating NB Maven Platform Projects, child projects should be prefixed
> with parent name
> --------------------------------------------------------------------------------------------
>
> Key: MNBMODULE-135
> URL: https://jira.codehaus.org/browse/MNBMODULE-135
> Project: Maven NetBeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 3.5
> Reporter: Brett Ryan
> Assignee: Jesse Glick
>
> When creating a Maven based NetBeans platform application the child projects
> (branding and application) should both be prefixed by the parent projects
> artifactId.
> This is apparent if you start creating multiple NetBeans platform applications
> with the same groupId you end up with application and branding being
> duplicated.
> The current workaround I employ is to perform the following:
> # Create project.
> # Close all three projects in NetBeans
> # Rename folders for "application" and "branding" to start with the parent
> projects artifactId.
> # Edit parent project (root pom.xml) file and rename each "module" entry for
> application and branding to those of the newly renamed folders.
> # Reopen the project in NetBeans and rebuild.
> Using a different groupId for projects is an incorrect assumption. The
> default behaviour within this module is to use the following as defaults:
> * Artifact Id: mavenproject1
> * Group Id: com.mycompany
> * Package: com.mycompany.mavenproject1
> These defaults are correct for maven projects, if you take NetBeans own
> modules they will all have a group ID of {{org.netbeans.modules}}. So given
> the above, the child projects for branding and application should both be
> created as:
> * Artifact Id: mavenproject1-application
> * Group Id: com.mycompany
> * Package: com.mycompany.mavenproject1
> * Artifact Id: mavenproject1-branding
> * Group Id: com.mycompany
> * Package: com.mycompany.mavenproject1
--
This message is automatically generated by JIRA.
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
