[
http://jira.codehaus.org/browse/MNBMODULE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96226
]
Milos Kleint commented on MNBMODULE-8:
--------------------------------------
I've implemented the stuff.. or at least partly.
1. swing-layout was kind of hacked when running populate-repository. based on
MD5 checksum of libraries for the module, we compare against the checksum of
the known swing-layout and included as dependency in the module's pom. This
principle could be extended or made more general in the future.
2. module.xml configuration file is not mandatory anymore.
3. This is how netbeans module runtime dependencies are resolved.
The module dependency is included, when
a. it is defined in existing module.xml file and is netbeans module.
b. when it's a direct dependency (non-transitive) and is a netbeans module.
c. when the dependency is of type "nbm". Such dependencies don't include their
transitive deps on compilation classpath
4. This is how the module libraries are resolved.
The library jar is included in the module when
a. it's defined in existing module.xml
b. is a direct dependency (non-transitive) and is not of "provided" scope
these should simplify the configuration of the module projects. The analyze
mojo should help with finding what dependencies shall be directly declared and
which shall not.
> Add transitive dependencies to the manifest classpath of a netbeans module.
> ---------------------------------------------------------------------------
>
> Key: MNBMODULE-8
> URL: http://jira.codehaus.org/browse/MNBMODULE-8
> Project: Maven 2.x Netbeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 2.4
> Environment: nbm-maven-plugin (head), maven 2.0.4
> Reporter: Rohnny Moland
> Assignee: Milos Kleint
> Fix For: 2.5
>
>
> It would be a nice feature to include all the transitive dependencies for the
> artifacts defined in the <libraries> section,
> in the netbeans module manifest class-path.
> Maybe the whole libraries section can go away, and instead use the pom
> artifacts directly? To separate netbeans modules
> from normal jar dependencies, examination of the manifest could be done. I
> mean..if it is not a normal jar dependency, or
> netbeans module dependency, then the artifact should probably go into another
> module.
> If we define new types (pom artifact types) for a module dependency (like
> spec), the dependencies section in module.xml could probably also
> go away. Maybe the netbeans module type is already defined in the manifest?
> Also the license. Why not use the pom license instead.
> I think the nbm descriptor could be merged with the pom descriptor, and just
> add things like cluster name, codenamebase to the configuration
> section for the plugin in the pom itself.
> Comments?
--
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
