[vfs][all] move vfs to maven 2 to setup a vfs-sandbox

[Mario Ivankovits <ma...@ops.co.at>]

Hi!

OK, again the VFS release.

To finally come to a VFS release some of us thought it would be best to
move non-releasable code to a VFS sandbox.
That is:
*) The jcifs due to their license
*) slide due to to dependency on a non release component

Thorsten pointed out that we can take JCI as a sample how to make a
project sandbox, but it looks like they use maven 2.

I use maven 2 at work, so I have some experiences with it.
Now I would like to ask if I can move VFS at all to maven 2 so I do not
have to figure out how to do things with the somehow outdated maven 1?

This is not a vote as I would like to see whats the general meaning
about this topic first.

Ciao,
Mario


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

Re: [vfs][all] move vfs to maven 2 to setup a vfs-sandbox

[Phil Steitz <ph...@gmail.com>]

On 10/13/06, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi Torsten!
> > ...so the real question is "is it ok to have a proper component use
> > maven2" ...right?
> hehe .... didn't I ask this?
> Yes, thats the real question!
>
> As a compromise I can maintain the maven 1 build for the core only
> (using the maven 2 directory layout), and a maven 2 build for the
> core/sandbox stuff.
> That also allows me to e.g. build the site with maven 1 as long as
> Commons haven't moved to maven 2 at all.
>
I think its perfectly fine for individual components, both proper as
well as sandbox, to start moving to maven 2.  We did a lot of work
several years back to get to a common look and feel for the site and a
decent level of build standardization using maven 1 and we are not
quite there yet in maven 2; but I think the best way for us to get
there is to start developing m2 builds, which will force us to solve
the remaining problems.To make it less painful for users during
transition, keeping a working m1 build for some time is a good idea;
but I would recommend making a clean break soon - certainly by the
time you cut the release.  More valuable than keeping an m1 build
around indefinitely is a working Ant build, IMO.

Phil

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

Re: [vfs][all] move vfs to maven 2 to setup a vfs-sandbox

[Mario Ivankovits <ma...@ops.co.at>]

Hi Torsten!
> ...so the real question is "is it ok to have a proper component use
> maven2" ...right?
hehe .... didn't I ask this?
Yes, thats the real question!

As a compromise I can maintain the maven 1 build for the core only
(using the maven 2 directory layout), and a maven 2 build for the
core/sandbox stuff.
That also allows me to e.g. build the site with maven 1 as long as
Commons haven't moved to maven 2 at all.

Ciao,
Mario


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

Re: [vfs][all] move vfs to maven 2 to setup a vfs-sandbox

[Torsten Curdt <tc...@apache.org>]

...so the real question is "is it ok to have a proper component use
maven2" ...right?

cheers
--
Torsten

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