[cle-release-team] unique versions, well and truly borked

[Matthew Jones]

Thanks, it looks like adding "-Dmaven.metadata.legacy=true" to the maven
opts fixes this.

However adding it to the global maven opts as Seth suggested isn't having
any effect.

I added it to the global, tried to build entitybroker trunk and the
metadata was still "wrong"
I added it to the local, tried to build entitybroker trunk and the metadata
was correct

So I either need to add it to all of the local opts or figure out why the
global opts aren't working/being loaded correctly.

It seems like if it's not one thing it's another! ;) I'd think that at
least these two modules *should* be fixed at the moment.

On Mon, Mar 19, 2012 at 9:21 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Confirming that switching to Maven 3 allows trunk to build fine. I'm now
> using similar shell scripts to you to specify which Maven version to use
> when I run either mvn/mvn3 etc (the Applescript I mentioned earlier is no
> longer relevant).
>
> cheers,
> Steve
>
>
>
> On 19/03/2012, at 10:04 PM, Matthew Buckett wrote:
>
> > On 19 March 2012 10:50, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
> >> Yeah that's what I was concerned about.
> >>
> >> I wrapped something like that up into an applescript that you can run
> from the top
> >> menu bar. I'll dig it out, tidy it up and send it around.
> >
> > Just to be clear this affects trunk and 2.9, as 2.9 is using the
> > sonatype repository.
> >
> > --
> >   Matthew Buckett
> >   VLE Developer, LTG, Oxford University Computing Services
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120319/d1f561a4/attachment-0006.html