Hi Zoe, I'm not sure how you retrieved information about dependencies between Aries subprojects. You may have already used the approach that I'm talking about below, but if not, it's definitely worth trying. It may save you time :).
This (or similar command) run on the parent project should give you detailed info on dependencies and will filter out artifacts that are not Aries subprojects. mvn dependency:tree -Dincludes=org.apache.aries* There's still some information to filter out, but not so much. Best regards, Bartek 2010/9/8 zoe slattery <[email protected]>: > Hi all > > I put together this page http://incubator.apache.org/aries/releasenotes.html > (with help from Camel, thx :-) ). It's for discussion, what have I missed > for the 0.2 release? Are there any other categories I should have added? > > Bearing in mind the previous release-by-module discussion I thought it would > also be an idea to indicate which other Aries modules a particular module > depends on and which version, so I've added in a table showing that > (actually I realise now that I have missed Samples, so will add that). > > Zoė >
