Please add elements to the in Excalibur POMs

[Stefan Bodewig <bo...@apache.org>]

Dear Excalibur devs

it is great to see Excalibur starting some activity again.

When you removed the Maven 1.x buildsystem sometime last week (or so)
you forced Gump to use your mvn descriptors (no problem here, other
than that of metadata maintenance).

So far Gump has split up Excalibur into many small buildable pieces,
each one corresponding to a single artifact.  Those pieces know how
they depend on each other (based on the care by people who knew what
they did, i.e. not me 8-).

We'd like to keep it that way for the Maven 2 build which means we'd
like to build Excalibur without using the reactor build because the
later doesn't allow us a state where some of the pieces built
successfully and other didn't.  The reactor is an all or nothing
thing.

My first naive conversions (for framework/api and
cornerstone/sockets/api) fail because mvn cannot locate the parent
POM.  It tries to locate it inside the (local) repository but it can't
find it there since it has never been deployed there in the first
place.

Unless anybody with more mvn foo than I have can tell me how to deploy
the parent POM (using mvn and no manual intervention of any kind, that
is) another option would be if you could provide <relativePath>
elements for all your <parent> definitions in your POMs.  I think this
would benefit occasional developers anyway.

Thanks

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Please add elements to the in Excalibur POMs

[Robert Burrell Donkin <ro...@gmail.com>]

On Monday, June 22, 2009, Stefan Bodewig <bo...@apache.org> wrote:
> Dear Excalibur debs
>
> it is great to see Excalibur starting some activity again.
>
> When you removed the Maven 1.x buildsystem sometime last week (or so)
> you forced Gump to use your mvn descriptors (no problem here, other
> than that of metadata maintenance).
>
> So far Gump has split up Excalibur into many small buildable pieces,
> each one corresponding to a single artifact.  Those pieces know how
> they depend on each other (based on the care by people who knew what
> they did, i.e. not me 8-).
>
> We'd like to keep it that way for the Maven 2 build which means we'd
> like to build Excalibur without using the reactor build because the
> later doesn't allow us a state where some of the pieces built
> successfully and other didn't.  The reactor is an all or nothing
> thing.

Sounds good to me

> My first naive conversions (for framework/api and
> cornerstone/sockets/api) fail because mvn cannot locate the parent
> POM.  It tries to locate it inside the (local) repository but it can't
> find it there since it has never been deployed there in the first
> place.
>
> Unless anybody with more mvn foo than I have can tell me how to deploy
> the parent POM (using mvn and no manual intervention of any kind, that
> is) another option would be if you could provide <relativePath>
> elements for all your <parent> definitions in your POMs.  I think this
> would benefit occasional developers anyway.

I'll go through the relative paths but I'm away ATM so it might be a
little while. If any one else feels inspired be jump in without
waiting for me.

- robert
>
> Thanks
>
>         Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
> For additional commands, e-mail: dev-help@excalibur.apache.org
>
>e

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org