|
||||||||||||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MNBMODULE-209) Feedback on verifyIn... Eric Barboni (JIRA)
- [mojo-dev] [jira] (MNBMODULE-209) Feedback on ver... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-209) Feedback on ver... Eric Barboni (JIRA)
https://fisheye.codehaus.org/changelog/mojo?cs=18222
fixes handling of osgi bundle dependencies and additionally prints module/bundle codenamebase where the failed dependency requirement originates.
Not much I can do beyond that, in both netbeans modules and osgi bundles don't have the maven coordinates. The algo for resolving the issues should probably be:
1. attempt to find the cluster where the missing artifact could be and add it.
2. try searching the netbeans repository for the artifact with the given codenamebase (likely not automated right now)
3. try adding external dependency.
Currently platforms composed of correct set of cluster dependencies resolve correctly. (which was not the case previously)
updated codebase uploaded to snapshot repository.