You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Se...@ardatis.com on 2005/03/24 08:21:33 UTC
maven roadmap - should i stay or should i go
Hi all,
In a project I am currently working on - which is just about to start with
the construction phase - we are considering to use maven. I have been
encountering maven in previous projects as well and based on these
experiences i was quite sure I will use it on many others as well.
However when i see the new roadmap description on maven site :
<<<<<<Maven 2.0 is a complete rewrite. It will not be backwards compatible
with any of the Maven 1.x releases>>>>>>,
i am having doubts on what exactly should we do right now.
To take off with the current release (1.0.2) and wait for a complete
rewrite of our build scripts? How "complete" will that rewrite actually
have to be? All what the explanation in the roadmap leaves us with is a
bit of hope that attempts will be made to stay backward compatible in the
new 2.0 release. What about the "conceptual approach", how many things can
we expect to be different, new or completely dissapear (multiproject,
repository, ...goals)?
Could someone point me to a document/person that can give a bit more of
vision/explanation concerning these issues? What would you suggest to a
project that is just about to jump into maven?
Thanks.
-Sejo
Re: maven roadmap - should i stay or should i go
Posted by Brett Porter <br...@gmail.com>.
> Arg I want Maven 2 now :)
>
Be patient, good things come to those who wait :)
> Just kidding, keep up the great work guys, but it's a long wait to Maven
> 2 it seems. Can you enlighten us as to the major road blocks you're
> encountering with Maven 2 ?
>
It has almost entirely been available time of the developers.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Serge Huber <sh...@jahia.com>.
Brett Porter wrote:
>Vincent has pretty well summed it up. I will try to clarify the document.
>
>Though the basic concepts are the same, Maven 2.x is really quite
>different, and it will require some work to move a project over to it.
>How much depends on how heavily you customise your Maven 1.x project -
>if you stick to the defaults and don't use Jelly, then it should be
>quite simple.
>
>Maven 1.x will still be developed until Maven 2.x is production ready
>(which is not going to be until later this year).
>
>
Arg I want Maven 2 now :)
Just kidding, keep up the great work guys, but it's a long wait to Maven
2 it seems. Can you enlighten us as to the major road blocks you're
encountering with Maven 2 ?
Regards,
Serge Huber.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Serge Huber <sh...@jahia.com>.
Gosh this Maven 2 is beginning to sound really good !
Now the waiting will be even harder :)
cheers,
Serge...
Brett Porter wrote:
>>Will there be a facility in the new (maven 2) POM to specify the default
>>goals required to build the artifact (either fully stated ${pom.goals}
>>or determined by some other variable ${pom.type}?).
>>
>>
>
>The latter, yes. We may add a default to the POM later.
>
>
>
>>Also will there be
>>a means to specify plugins and their minimum version requirements
>>in the dependencies?
>>
>>
>
>yes
>
>
>
>>I think I caught talk about even specifying the
>>difference in dependencies between build/run/test/cactus/integration time,
>>is this categorization the ability I'm looking for?
>>
>>
>
>yes
>
>Cheers,
>Brett
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Brett Porter <br...@gmail.com>.
> Will there be a facility in the new (maven 2) POM to specify the default
> goals required to build the artifact (either fully stated ${pom.goals}
> or determined by some other variable ${pom.type}?).
The latter, yes. We may add a default to the POM later.
> Also will there be
> a means to specify plugins and their minimum version requirements
> in the dependencies?
yes
> I think I caught talk about even specifying the
> difference in dependencies between build/run/test/cactus/integration time,
> is this categorization the ability I'm looking for?
yes
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Joakim Erdfelt <jo...@erdfelt.net>.
Brett Porter wrote:
>>Huh... Exactly how much trouble are we talking about to switch custom
>>plugins and such??? Is Jelly replaced?
>>
>>
>
>Yes, though we are trying hard to put in a replacement that can
>transparently run old Jelly scripts with minimal changes. Part of the
>problem is that people have come to rely on bugs in Jelly/Jexl/Maven
>for their scripts to work.
>
>
Will there be a facility in the new (maven 2) POM to specify the default
goals required to build the artifact (either fully stated ${pom.goals}
or determined by some other variable ${pom.type}?). Also will there be
a means to specify plugins and their minimum version requirements
in the dependencies? I think I caught talk about even specifying the
difference in dependencies between build/run/test/cactus/integration time,
is this categorization the ability I'm looking for?
/* Joakim Erdfelt */
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Serge Huber <sh...@jahia.com>.
Brett Porter wrote:
>http://maven.apache.org/using/bestpractices.html#Scripting
>
>
Oops sorry... I didn't check out the new content yet :)
Regards,
Serge Huber.
>
>On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <sh...@jahia.com> wrote:
>
>
>>I once got the great advice from a MevenIDE developer that I should keep
>>the maven.xml file to a strict minimum, and develop plugins mostly using
>>Java classes. I've used that advice well, and it looks like at least for
>>me, migrating to Maven 2 wouldn't be too much of a problem.
>>
>>Maybe this should be on a page somewhere, in order for people to prepare
>>for Maven 2 ? Basically telling them that in order to build scripts &
>>plugins that are compatible with Maven 2, they should follow these two
>>guidelines as much as possible ?
>>
>>Regards,
>> Serge Huber.
>>
>>Brett Porter wrote:
>>
>>
>>
>>>>Huh... Exactly how much trouble are we talking about to switch custom
>>>>plugins and such??? Is Jelly replaced?
>>>>
>>>>
>>>>
>>>>
>>>Yes, though we are trying hard to put in a replacement that can
>>>transparently run old Jelly scripts with minimal changes. Part of the
>>>problem is that people have come to rely on bugs in Jelly/Jexl/Maven
>>>for their scripts to work.
>>>
>>>
>>>
>>>
>>>
>>>>And if so, with what and why?
>>>>
>>>>
>>>>
>>>>
>>>Speed and memory usage are a big factor. In Maven 2.x, most plugins
>>>are written in pure Java, though theoretically adapters can be written
>>>for any scripting language.
>>>
>>>There will be an XML scripting language present for the benefit of
>>>users who want to interface with Ant tasks, though it won't at all be
>>>necessary to use it day to day.
>>>
>>>
>>>
>>>
>>>
>>>>Does it mean all the custom stuff I'm currently implementing will be
>>>>thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
>>>>be in production for more than a couple of months...
>>>>
>>>>
>>>>
>>>>
>>>Maven 1.x is not going to disappear - if your investment outweighs the
>>>benefit, then stick with it.
>>>
>>>More information will be available as the first releases draw near.
>>>For now - Maven 1.1 and its plugins continue to be developed.
>>>
>>>- Brett
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Milos Kleint <Mi...@Sun.COM>.
I've added a maven plugin project template into Mevenide for Netbeans.
It creates a project with plugin files, you have code completion in the
plugin.jelly file etc.
Regards
Milos Kleint
Brett Porter wrote:
>http://maven.apache.org/using/bestpractices.html#Scripting
>
>
>On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <sh...@jahia.com> wrote:
>
>
>>I once got the great advice from a MevenIDE developer that I should keep
>>the maven.xml file to a strict minimum, and develop plugins mostly using
>>Java classes. I've used that advice well, and it looks like at least for
>>me, migrating to Maven 2 wouldn't be too much of a problem.
>>
>>Maybe this should be on a page somewhere, in order for people to prepare
>>for Maven 2 ? Basically telling them that in order to build scripts &
>>plugins that are compatible with Maven 2, they should follow these two
>>guidelines as much as possible ?
>>
>>Regards,
>> Serge Huber.
>>
>>Brett Porter wrote:
>>
>>
>>
>>>>Huh... Exactly how much trouble are we talking about to switch custom
>>>>plugins and such??? Is Jelly replaced?
>>>>
>>>>
>>>>
>>>>
>>>Yes, though we are trying hard to put in a replacement that can
>>>transparently run old Jelly scripts with minimal changes. Part of the
>>>problem is that people have come to rely on bugs in Jelly/Jexl/Maven
>>>for their scripts to work.
>>>
>>>
>>>
>>>
>>>
>>>>And if so, with what and why?
>>>>
>>>>
>>>>
>>>>
>>>Speed and memory usage are a big factor. In Maven 2.x, most plugins
>>>are written in pure Java, though theoretically adapters can be written
>>>for any scripting language.
>>>
>>>There will be an XML scripting language present for the benefit of
>>>users who want to interface with Ant tasks, though it won't at all be
>>>necessary to use it day to day.
>>>
>>>
>>>
>>>
>>>
>>>>Does it mean all the custom stuff I'm currently implementing will be
>>>>thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
>>>>be in production for more than a couple of months...
>>>>
>>>>
>>>>
>>>>
>>>Maven 1.x is not going to disappear - if your investment outweighs the
>>>benefit, then stick with it.
>>>
>>>More information will be available as the first releases draw near.
>>>For now - Maven 1.1 and its plugins continue to be developed.
>>>
>>>- Brett
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Brett Porter <br...@gmail.com>.
http://maven.apache.org/using/bestpractices.html#Scripting
On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <sh...@jahia.com> wrote:
>
> I once got the great advice from a MevenIDE developer that I should keep
> the maven.xml file to a strict minimum, and develop plugins mostly using
> Java classes. I've used that advice well, and it looks like at least for
> me, migrating to Maven 2 wouldn't be too much of a problem.
>
> Maybe this should be on a page somewhere, in order for people to prepare
> for Maven 2 ? Basically telling them that in order to build scripts &
> plugins that are compatible with Maven 2, they should follow these two
> guidelines as much as possible ?
>
> Regards,
> Serge Huber.
>
> Brett Porter wrote:
>
> >>Huh... Exactly how much trouble are we talking about to switch custom
> >>plugins and such??? Is Jelly replaced?
> >>
> >>
> >
> >Yes, though we are trying hard to put in a replacement that can
> >transparently run old Jelly scripts with minimal changes. Part of the
> >problem is that people have come to rely on bugs in Jelly/Jexl/Maven
> >for their scripts to work.
> >
> >
> >
> >>And if so, with what and why?
> >>
> >>
> >
> >Speed and memory usage are a big factor. In Maven 2.x, most plugins
> >are written in pure Java, though theoretically adapters can be written
> >for any scripting language.
> >
> >There will be an XML scripting language present for the benefit of
> >users who want to interface with Ant tasks, though it won't at all be
> >necessary to use it day to day.
> >
> >
> >
> >>Does it mean all the custom stuff I'm currently implementing will be
> >>thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> >>be in production for more than a couple of months...
> >>
> >>
> >
> >Maven 1.x is not going to disappear - if your investment outweighs the
> >benefit, then stick with it.
> >
> >More information will be available as the first releases draw near.
> >For now - Maven 1.1 and its plugins continue to be developed.
> >
> >- Brett
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Serge Huber <sh...@jahia.com>.
I once got the great advice from a MevenIDE developer that I should keep
the maven.xml file to a strict minimum, and develop plugins mostly using
Java classes. I've used that advice well, and it looks like at least for
me, migrating to Maven 2 wouldn't be too much of a problem.
Maybe this should be on a page somewhere, in order for people to prepare
for Maven 2 ? Basically telling them that in order to build scripts &
plugins that are compatible with Maven 2, they should follow these two
guidelines as much as possible ?
Regards,
Serge Huber.
Brett Porter wrote:
>>Huh... Exactly how much trouble are we talking about to switch custom
>>plugins and such??? Is Jelly replaced?
>>
>>
>
>Yes, though we are trying hard to put in a replacement that can
>transparently run old Jelly scripts with minimal changes. Part of the
>problem is that people have come to rely on bugs in Jelly/Jexl/Maven
>for their scripts to work.
>
>
>
>>And if so, with what and why?
>>
>>
>
>Speed and memory usage are a big factor. In Maven 2.x, most plugins
>are written in pure Java, though theoretically adapters can be written
>for any scripting language.
>
>There will be an XML scripting language present for the benefit of
>users who want to interface with Ant tasks, though it won't at all be
>necessary to use it day to day.
>
>
>
>>Does it mean all the custom stuff I'm currently implementing will be
>>thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
>>be in production for more than a couple of months...
>>
>>
>
>Maven 1.x is not going to disappear - if your investment outweighs the
>benefit, then stick with it.
>
>More information will be available as the first releases draw near.
>For now - Maven 1.1 and its plugins continue to be developed.
>
>- Brett
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Brett Porter <br...@gmail.com>.
> Huh... Exactly how much trouble are we talking about to switch custom
> plugins and such??? Is Jelly replaced?
Yes, though we are trying hard to put in a replacement that can
transparently run old Jelly scripts with minimal changes. Part of the
problem is that people have come to rely on bugs in Jelly/Jexl/Maven
for their scripts to work.
> And if so, with what and why?
Speed and memory usage are a big factor. In Maven 2.x, most plugins
are written in pure Java, though theoretically adapters can be written
for any scripting language.
There will be an XML scripting language present for the benefit of
users who want to interface with Ant tasks, though it won't at all be
necessary to use it day to day.
> Does it mean all the custom stuff I'm currently implementing will be
> thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> be in production for more than a couple of months...
Maven 1.x is not going to disappear - if your investment outweighs the
benefit, then stick with it.
More information will be available as the first releases draw near.
For now - Maven 1.1 and its plugins continue to be developed.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Steve Molloy <sm...@convera.com>.
OK, that is usually simple stuff anyway.
Thanks for the relief... ;-)
Steve
On Thu, 2005-24-03 at 14:47 +0100, Nicolas Chalumeau wrote:
> All old plugin in jelly will be suported.
> As far I know the trouble will be with all the goal you have in your
> maven.xml as (I am maybe wrong) this file not be use in M2
>
> Nicolas
>
> On Thu, 24 Mar 2005 08:39:49 -0500, Steve Molloy <sm...@convera.com> wrote:
> > Huh... Exactly how much trouble are we talking about to switch custom
> > plugins and such??? Is Jelly replaced? And if so, with what and why?
> > Does it mean all the custom stuff I'm currently implementing will be
> > thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> > be in production for more than a couple of months...
> >
> > Steve
> >
> > On Thu, 2005-24-03 at 19:05 +1100, Brett Porter wrote:
> >
> > > Vincent has pretty well summed it up. I will try to clarify the document.
> > >
> > > Though the basic concepts are the same, Maven 2.x is really quite
> > > different, and it will require some work to move a project over to it.
> > > How much depends on how heavily you customise your Maven 1.x project -
> > > if you stick to the defaults and don't use Jelly, then it should be
> > > quite simple.
> > >
> > > Maven 1.x will still be developed until Maven 2.x is production ready
> > > (which is not going to be until later this year).
> > >
> > > - Brett
> > >
> > >
> > > On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <vm...@pivolis.com> wrote:
> > > > Hi Sejo,
> > > >
> > > > I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> > > > version before this summer too with several components from Maven2
> > > > backported. I believe the Maven2 team will make it as easy as possible for
> > > > existing Maven users to switch to Maven2.
> > > >
> > > > Most of the Maven1 concepts will stay but will be implemented differently
> > > > (new POM version for example).
> > > >
> > > > I'll let the Maven2 team comment further on details.
> > > >
> > > > -Vincent
> > > >
> > > > > -----Original Message-----
> > > > > From: Sejo.Cesic@ardatis.com [mailto:Sejo.Cesic@ardatis.com]
> > > > > Sent: jeudi 24 mars 2005 08:22
> > > > > To: Maven Users List
> > > > > Subject: maven roadmap - should i stay or should i go
> > > > >
> > > > > Hi all,
> > > > >
> > > > > In a project I am currently working on - which is just about to start with
> > > > > the construction phase - we are considering to use maven. I have been
> > > > > encountering maven in previous projects as well and based on these
> > > > > experiences i was quite sure I will use it on many others as well.
> > > > >
> > > > > However when i see the new roadmap description on maven site :
> > > > >
> > > > > <<<<<<Maven 2.0 is a complete rewrite. It will not be backwards compatible
> > > > > with any of the Maven 1.x releases>>>>>>,
> > > > >
> > > > > i am having doubts on what exactly should we do right now.
> > > > >
> > > > > To take off with the current release (1.0.2) and wait for a complete
> > > > > rewrite of our build scripts? How "complete" will that rewrite actually
> > > > > have to be? All what the explanation in the roadmap leaves us with is a
> > > > > bit of hope that attempts will be made to stay backward compatible in the
> > > > > new 2.0 release. What about the "conceptual approach", how many things can
> > > > > we expect to be different, new or completely dissapear (multiproject,
> > > > > repository, ...goals)?
> > > > >
> > > > > Could someone point me to a document/person that can give a bit more of
> > > > > vision/explanation concerning these issues? What would you suggest to a
> > > > > project that is just about to jump into maven?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > -Sejo
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: maven roadmap - should i stay or should i go
Posted by Nicolas Chalumeau <ni...@gmail.com>.
All old plugin in jelly will be suported.
As far I know the trouble will be with all the goal you have in your
maven.xml as (I am maybe wrong) this file not be use in M2
Nicolas
On Thu, 24 Mar 2005 08:39:49 -0500, Steve Molloy <sm...@convera.com> wrote:
> Huh... Exactly how much trouble are we talking about to switch custom
> plugins and such??? Is Jelly replaced? And if so, with what and why?
> Does it mean all the custom stuff I'm currently implementing will be
> thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> be in production for more than a couple of months...
>
> Steve
>
> On Thu, 2005-24-03 at 19:05 +1100, Brett Porter wrote:
>
> > Vincent has pretty well summed it up. I will try to clarify the document.
> >
> > Though the basic concepts are the same, Maven 2.x is really quite
> > different, and it will require some work to move a project over to it.
> > How much depends on how heavily you customise your Maven 1.x project -
> > if you stick to the defaults and don't use Jelly, then it should be
> > quite simple.
> >
> > Maven 1.x will still be developed until Maven 2.x is production ready
> > (which is not going to be until later this year).
> >
> > - Brett
> >
> >
> > On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <vm...@pivolis.com> wrote:
> > > Hi Sejo,
> > >
> > > I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> > > version before this summer too with several components from Maven2
> > > backported. I believe the Maven2 team will make it as easy as possible for
> > > existing Maven users to switch to Maven2.
> > >
> > > Most of the Maven1 concepts will stay but will be implemented differently
> > > (new POM version for example).
> > >
> > > I'll let the Maven2 team comment further on details.
> > >
> > > -Vincent
> > >
> > > > -----Original Message-----
> > > > From: Sejo.Cesic@ardatis.com [mailto:Sejo.Cesic@ardatis.com]
> > > > Sent: jeudi 24 mars 2005 08:22
> > > > To: Maven Users List
> > > > Subject: maven roadmap - should i stay or should i go
> > > >
> > > > Hi all,
> > > >
> > > > In a project I am currently working on - which is just about to start with
> > > > the construction phase - we are considering to use maven. I have been
> > > > encountering maven in previous projects as well and based on these
> > > > experiences i was quite sure I will use it on many others as well.
> > > >
> > > > However when i see the new roadmap description on maven site :
> > > >
> > > > <<<<<<Maven 2.0 is a complete rewrite. It will not be backwards compatible
> > > > with any of the Maven 1.x releases>>>>>>,
> > > >
> > > > i am having doubts on what exactly should we do right now.
> > > >
> > > > To take off with the current release (1.0.2) and wait for a complete
> > > > rewrite of our build scripts? How "complete" will that rewrite actually
> > > > have to be? All what the explanation in the roadmap leaves us with is a
> > > > bit of hope that attempts will be made to stay backward compatible in the
> > > > new 2.0 release. What about the "conceptual approach", how many things can
> > > > we expect to be different, new or completely dissapear (multiproject,
> > > > repository, ...goals)?
> > > >
> > > > Could someone point me to a document/person that can give a bit more of
> > > > vision/explanation concerning these issues? What would you suggest to a
> > > > project that is just about to jump into maven?
> > > >
> > > > Thanks.
> > > >
> > > > -Sejo
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven roadmap - should i stay or should i go
Posted by Steve Molloy <sm...@convera.com>.
Huh... Exactly how much trouble are we talking about to switch custom
plugins and such??? Is Jelly replaced? And if so, with what and why?
Does it mean all the custom stuff I'm currently implementing will be
thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
be in production for more than a couple of months...
Steve
On Thu, 2005-24-03 at 19:05 +1100, Brett Porter wrote:
> Vincent has pretty well summed it up. I will try to clarify the document.
>
> Though the basic concepts are the same, Maven 2.x is really quite
> different, and it will require some work to move a project over to it.
> How much depends on how heavily you customise your Maven 1.x project -
> if you stick to the defaults and don't use Jelly, then it should be
> quite simple.
>
> Maven 1.x will still be developed until Maven 2.x is production ready
> (which is not going to be until later this year).
>
> - Brett
>
>
> On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <vm...@pivolis.com> wrote:
> > Hi Sejo,
> >
> > I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> > version before this summer too with several components from Maven2
> > backported. I believe the Maven2 team will make it as easy as possible for
> > existing Maven users to switch to Maven2.
> >
> > Most of the Maven1 concepts will stay but will be implemented differently
> > (new POM version for example).
> >
> > I'll let the Maven2 team comment further on details.
> >
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Sejo.Cesic@ardatis.com [mailto:Sejo.Cesic@ardatis.com]
> > > Sent: jeudi 24 mars 2005 08:22
> > > To: Maven Users List
> > > Subject: maven roadmap - should i stay or should i go
> > >
> > > Hi all,
> > >
> > > In a project I am currently working on - which is just about to start with
> > > the construction phase - we are considering to use maven. I have been
> > > encountering maven in previous projects as well and based on these
> > > experiences i was quite sure I will use it on many others as well.
> > >
> > > However when i see the new roadmap description on maven site :
> > >
> > > <<<<<<Maven 2.0 is a complete rewrite. It will not be backwards compatible
> > > with any of the Maven 1.x releases>>>>>>,
> > >
> > > i am having doubts on what exactly should we do right now.
> > >
> > > To take off with the current release (1.0.2) and wait for a complete
> > > rewrite of our build scripts? How "complete" will that rewrite actually
> > > have to be? All what the explanation in the roadmap leaves us with is a
> > > bit of hope that attempts will be made to stay backward compatible in the
> > > new 2.0 release. What about the "conceptual approach", how many things can
> > > we expect to be different, new or completely dissapear (multiproject,
> > > repository, ...goals)?
> > >
> > > Could someone point me to a document/person that can give a bit more of
> > > vision/explanation concerning these issues? What would you suggest to a
> > > project that is just about to jump into maven?
> > >
> > > Thanks.
> > >
> > > -Sejo
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: maven roadmap - should i stay or should i go
Posted by Brett Porter <br...@gmail.com>.
Vincent has pretty well summed it up. I will try to clarify the document.
Though the basic concepts are the same, Maven 2.x is really quite
different, and it will require some work to move a project over to it.
How much depends on how heavily you customise your Maven 1.x project -
if you stick to the defaults and don't use Jelly, then it should be
quite simple.
Maven 1.x will still be developed until Maven 2.x is production ready
(which is not going to be until later this year).
- Brett
On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <vm...@pivolis.com> wrote:
> Hi Sejo,
>
> I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> version before this summer too with several components from Maven2
> backported. I believe the Maven2 team will make it as easy as possible for
> existing Maven users to switch to Maven2.
>
> Most of the Maven1 concepts will stay but will be implemented differently
> (new POM version for example).
>
> I'll let the Maven2 team comment further on details.
>
> -Vincent
>
> > -----Original Message-----
> > From: Sejo.Cesic@ardatis.com [mailto:Sejo.Cesic@ardatis.com]
> > Sent: jeudi 24 mars 2005 08:22
> > To: Maven Users List
> > Subject: maven roadmap - should i stay or should i go
> >
> > Hi all,
> >
> > In a project I am currently working on - which is just about to start with
> > the construction phase - we are considering to use maven. I have been
> > encountering maven in previous projects as well and based on these
> > experiences i was quite sure I will use it on many others as well.
> >
> > However when i see the new roadmap description on maven site :
> >
> > <<<<<<Maven 2.0 is a complete rewrite. It will not be backwards compatible
> > with any of the Maven 1.x releases>>>>>>,
> >
> > i am having doubts on what exactly should we do right now.
> >
> > To take off with the current release (1.0.2) and wait for a complete
> > rewrite of our build scripts? How "complete" will that rewrite actually
> > have to be? All what the explanation in the roadmap leaves us with is a
> > bit of hope that attempts will be made to stay backward compatible in the
> > new 2.0 release. What about the "conceptual approach", how many things can
> > we expect to be different, new or completely dissapear (multiproject,
> > repository, ...goals)?
> >
> > Could someone point me to a document/person that can give a bit more of
> > vision/explanation concerning these issues? What would you suggest to a
> > project that is just about to jump into maven?
> >
> > Thanks.
> >
> > -Sejo
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: maven roadmap - should i stay or should i go
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Sejo,
I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
version before this summer too with several components from Maven2
backported. I believe the Maven2 team will make it as easy as possible for
existing Maven users to switch to Maven2.
Most of the Maven1 concepts will stay but will be implemented differently
(new POM version for example).
I'll let the Maven2 team comment further on details.
-Vincent
> -----Original Message-----
> From: Sejo.Cesic@ardatis.com [mailto:Sejo.Cesic@ardatis.com]
> Sent: jeudi 24 mars 2005 08:22
> To: Maven Users List
> Subject: maven roadmap - should i stay or should i go
>
> Hi all,
>
> In a project I am currently working on - which is just about to start with
> the construction phase - we are considering to use maven. I have been
> encountering maven in previous projects as well and based on these
> experiences i was quite sure I will use it on many others as well.
>
> However when i see the new roadmap description on maven site :
>
> <<<<<<Maven 2.0 is a complete rewrite. It will not be backwards compatible
> with any of the Maven 1.x releases>>>>>>,
>
> i am having doubts on what exactly should we do right now.
>
> To take off with the current release (1.0.2) and wait for a complete
> rewrite of our build scripts? How "complete" will that rewrite actually
> have to be? All what the explanation in the roadmap leaves us with is a
> bit of hope that attempts will be made to stay backward compatible in the
> new 2.0 release. What about the "conceptual approach", how many things can
> we expect to be different, new or completely dissapear (multiproject,
> repository, ...goals)?
>
> Could someone point me to a document/person that can give a bit more of
> vision/explanation concerning these issues? What would you suggest to a
> project that is just about to jump into maven?
>
> Thanks.
>
> -Sejo
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org