Re: Lenya and Maven

Florent André <[email protected]>
Newsgroups gmane.comp.cms.lenya.devel
Message-ID <[email protected]>
On Fri, 16 Jul 2010 14:40:49 +0200 (CEST), Rainer Schöpf
<[email protected]> wrote:
> On Fri, 16 Jul 2010, Richard Frovarp wrote:
> 
>  > On 7/16/2010 3:34 AM, Andreas Hartmann wrote:
>  > > Am 16.07.10 09:55, schrieb Vik Tara:
>  > > > On 07/16/2010 08:53 AM, Vik Tara wrote:
>  > > > > > 
[[..]]
>  > > 
>  > > 
>  > I'm a big fan of maven, but I'm with Andreas on this one. I don't
think
>  > that
>  > a switch to Maven on the current branch (2.1.x) is worth the risks.
As a
>  > community, I think we have more urgent needs than switching the
current
>  > version to maven. Here's my list:
> 
> OK, I see your point, Richard.
> 
>  > 1) Fix editor problem (some tasks are remaining)
>  > 2) Better documentation (specifically surrounding editor problems)
>  > 3) Release 2.1.0
>  > 4) Close tickets (over 200 open, some for years, looks very bad)
>  > 5) Design V3
>  > 6) Implement V3

OK for this plan. Nice. 
What will contain the 2.1.0 ?

>  > 
>  > At the meeting, there was strong consensus that v3 is going to be
>  > completely
>  > different. It will be built from the ground up on JCR and Cocoon
>  > probably
>  > won't be our primary engine. V3 will be built from the ground up to
use
>  > maven
>  > and probably OSGi. The issues surrounding converting the existing
>  > project to
>  > maven won't be the same with a fresh project.

Just to be sure, you imagine restart from scratch with V3 ? 

>  > 
>  > I think we need to do 1 & 2 above quickly, which would result in 3.
We
>  > should
>  > also be working towards 5, so we can do 6. It would be so nice to go
to
>  > Apache Con in November with a design for v3 and to be able to
encourage
>  > people to work on the project.
>  > 
>  > The 2.2 branch is there to do Cocoon 2.2 and maven. Experimenting
there,
>  > learning there is a good thing and can be a useful set of skills and
>  > experiences for the future. I am -1 on switching 2.1.x to maven.

Problem with 2.2 branch is that it include too many new things : maven and
C2.2 (not really "clean" for now).
What about : 
A) release 2.1.0 as your plan
B) Begin the maven stuff on a new branch from 2.1 

... and continue Lenya 3 definition in parallel ??


> 
> Actually, I was going to propose to do new development and migration to
> maven on 
> different branches, with the possibility to merge later on.
> 
> So, I'm +1 on your proposal.
> 
>   Rainer
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.