[
http://jira.codehaus.org/browse/MNBMODULE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint updated MNBMODULE-30:
----------------------------------
Fix Version/s: 3.0
i've implemented it in a similar way. There's new packaging now
"nbm-application", which needs dependencies of type "nbm-file" in it's
dependency list. These point to the actual *.nbm files, and when the final
application (and the zip) is constructed, all nbm files from repository are
expanded into their respective clusters.
I don't think there is a need to creating clusters only.
A way to organize dependencies into clusters is to use a special "pom" typed
midlle-man dependencies that will incorporate all nbm files in the given
cluster. That way the nbm-application can depend on "platform9", "java1" and
"maven1" clusters (pom files) only and have the complete cluster included.
Please note that the nbm:populate-repository goal will now generate these
cluster pom files into the org.netbeans.clusters groupId (if module's nbm files
are available to it)
> NetBeans Suite from Maven dependencies instead of modules
> ---------------------------------------------------------
>
> Key: MNBMODULE-30
> URL: http://jira.codehaus.org/browse/MNBMODULE-30
> Project: Maven 2.x Netbeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 2.7
> Reporter: Filip Jirsák
> Assignee: Milos Kleint
> Fix For: 3.0
>
> Attachments: nbm-maven-plugin.patch, nbm-maven-plugin.patch
>
>
> Attached patch createsnew type (packaging) of Maven Project -
> nbm-application. Further it appends new goal - nbm:nbm-cluster. This goal
> works on nbm-application packaging. It is similar to nbm:cluster goal on
> "pom" packaging - it creates NetBeans Suite from given modules. The only
> difference between nbm:cluster and nbm:nbm-cluster is in way, how it obtains
> modules. nbm:cluster (with pom packaging) uses Maven multiproject, so it is
> necessary to have all modules with their source code together with suite
> project. With nbm:nbm-cluster you need only .nbm archives in local or remote
> Maven repository (deployed by "mvn nbm:nbm install" or "mvn nbm:nbm deploy"),
> because nbm-application suite uses Maven dependency mechanism for receiving
> modules.
--
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
