Hi,

I worked pretty hard to make those bundles loosely coupled way back in 0.1, I'm 
glad to hear that they've stayed that way!

Regards,

Tim

> Subject: Re: Aries JPA modules release: progress notes
> From: [email protected]
> Date: Wed, 20 Jul 2011 08:15:12 +0100
> To: [email protected]
> 
> I would agree with the assessment jpa.container.context and 
> jpa.blueprint.aries in particular should not have changed for the weaving 
> support. 
> 
> And as far as I can glean from the svn logs that also holds true in practice 
> :)
> 
> However, 
> 
> Regards,
> 
> Valentin
> 
> On 19 Jul 2011, at 22:40, Alasdair Nottingham 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.
> > 
> > Do we need to release the itests?
> > 
> > I'm just asking, I am sure I could have got this all wrong.
> > 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]
> 
                                          

Reply via email to