You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Jeremy Hughes <hu...@apache.org> on 2011/09/09 14:12:33 UTC

Re: Aries JPA modules release: progress notes

On 20 July 2011 19:48, zoe slattery <zo...@gmail.com> wrote:
> I *think* (and I may be completely mis-remembering this) that if you look at
> what the distro releases do there is some configuration in the maven
> assembly plugin that enables you to pick up dependencies much more easily
> than looking through dependency trees. Just a thought.

Thanks ... and now that I'm managing to spend some time on this (!) I
notice that the distro only picks up org.apache.aries.* bundles
throughout the dependency tree if they are marked with a <scope> that
is something other than 'provided'. So I'm looking for a way to tell
the assembly plugin to pick up the 'provided' ones too. Which kinda
defeats the meaning of 'provided'. So maybe the 'provided'
dependencies and second order dependencies shouldn't be marked as
'provided' after all.

> Z
>>
>> 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
>>
>
>