|
||||||||
|
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 |
||||||||
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers


Yes, amdatu-parent has an individual lifecycle. IMHO it would be a good practice to keep all "native" projects on the same parent. It's on organizational pom that also tries to provides cross cutting defaults. Maybe it tries to do too much and we need to move some stuff away to make it more stable. Obviously, anyone can choose not to extend it or override it's default settings.
Well, bundles are created by the bundle plugin [0]. It is configured in the parent and has been upgraded. So that's your starting point. I have not seen any such behavior before. Maybe the default on embed transitive changed?
[0] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
http://www.amdatu.org/confluence/display/Amdatu/Development+environment