On 19 July 2011 22:40, Alasdair Nottingham <[email protected]> wrote: > Hi, > > I think my question would be do we need to do a release of the following to > meet the request: > > org.apache.aries.jpa.blueprint.aries > org.apache.aries.jpa.container.context > > I don't know enough about JPA, but the thing they wanted was enough to do > dynamic weaving of entities. Are these two needed for that? If we can't > release the JPA code that does dynamic weaving without these then we might > have high cohesion between these bundles and we should consider merging the > bundles.
I agree we should be able to release just enough. Like you I think the objective of the release is to satisfy the demand to use a released version of Aries bundles to achieve dynamic weaving and maybe I've be overzealous in thinking of pulling these in. Right now, where the sub-modules depend on their siblings, they depend on a snapshot. Something to think about for the future is to keep sub-modules depending on released versions of their sibling modules, to make it easier to see at release time what the lowest versions of the dependencies are. > > Do we need to release the itests? You're right it's probably not necessary. What I think is important is to give a good feeling that the released artifacts have been i-tested with their dependencies - most definitely with their minimum dependencies, and for an extra bonus point, the latest releases of the dependencies (within version range of course). There are several bundles that make up the i-tests in JPA, so releasing them all is a bit of extra work. I think a statement that says what revision it's been tested with would IMO be sufficient. Anyone care to comment? > > I'm just asking, I am sure I could have got this all wrong. No, given the above, I can do a bit more to try to reduce the number of dependencies that need releasing. > Alasdair > > On 19 July 2011 13:23, Jeremy Hughes <[email protected]> wrote: > >> Hi, I've started to look at releasing Aries JPA. Based on the >> discussion a week or two ago, the feeling was we'd only need to >> release the util module in addition to the JPA ones. Now that I've >> inspected the dependency tree, there are a few more snapshot >> dependencies that I'm going try to switch back to released versions. >> If this isn't possible then we'll need to release more dependencies. >> >> I'm writing a few notes on the way where you can see the details: >> http://aries.apache.org/development/JPADrivenRelease.html >> >> Cheers, >> Jeremy >> > > > > -- > Alasdair Nottingham > [email protected] >
