|
||||||||
|
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-157) Guess at cluster for... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-157) Guess at cluste... Milos Kleint (JIRA)

another current problem is that the application assembly relies on useOSGiDependencies parameter when handling bundles. That would be sort of fine if only the user's bundles were ever present, however that's not the case. We also have bundles included in some of the IDE's clusters. So it appears that when useOSGiDependencies is false (which is a sensible default), the assembly of clusters will skip all bundles present in the IDE. That's easy to confirm when including the "ide" cluster into the application, that one has a lot of osgi bundles. Deserves raise in priority IMHO.