Vadim Gritsenko wrote:
Completely agree: next release can use ant build, it does not have to be
maven
I hope that my recent work on the deployer for monolithic Cocoon apps has solved
the remaining problems with the build system. There is some work left as
described in my other mail, but
Vadim Gritsenko wrote:
It means keep 2.1 as is, with 2.1.9 being the last release, and concentrate
on
getting 2.2 out.
Big +1
Carsten
--
Carsten Ziegeler - Open Source Group, SN AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Andrew Stevens wrote:
From: Ralph Goers [EMAIL PROTECTED]
Date: Fri, 24 Mar 2006 14:22:18 -0800
Even if trunk isn't released for months, I'd prefer that 2.1.9 become 2.2
before switching to JDK 1.4. In other words, I'm not in favor of 2.1.x
ever being upgraded to JDK 1.4. However, I'm
Antonio Gallardo wrote:
WDYT?
I agree with all points, but personally I'd prefer to release 2.2 (defined as:
2.1 + new core + mvn monolithic build) and stop maintenance of 2.1 branch. Don't
you think this will be a better alternative? :)
Vadim
Vadim Gritsenko escribió:
Antonio Gallardo wrote:
WDYT?
I agree with all points, but personally I'd prefer to release 2.2
(defined as: 2.1 + new core + mvn monolithic build) and stop
maintenance of 2.1 branch. Don't you think this will be a better
alternative? :)
While I understand the
Antonio Gallardo wrote:
Vadim Gritsenko escribió:
Antonio Gallardo wrote:
WDYT?
I agree with all points, but personally I'd prefer to release 2.2
(defined as: 2.1 + new core + mvn monolithic build) and stop
maintenance of 2.1 branch. Don't you think this will be a better
alternative? :)
Vadim Gritsenko wrote:
rather than wait several more years for Cocoon Vista to appear on horizon.
^
Man, that's nasty ;)
Luca Morandini
www.lucamorandini.it
Vadim Gritsenko wrote:
rather than wait several more years for Cocoon Vista to appear on horizon.
And that's even nastier ;)
Luca Morandini
www.lucamorandini.it
Vadim Gritsenko escribió:
Antonio Gallardo wrote:
WDYT?
I agree with all points, but personally I'd prefer to release 2.2
(defined as: 2.1 + new core + mvn monolithic build) and stop
maintenance of 2.1 branch. Don't you think this will be a better
alternative? :)
Vadim
retrying...
What
Antonio Gallardo wrote:
Vadim Gritsenko escribió:
Antonio Gallardo wrote:
WDYT?
I agree with all points, but personally I'd prefer to release 2.2
(defined as: 2.1 + new core + mvn monolithic build) and stop
maintenance of 2.1 branch. Don't you think this will be a better
alternative? :)
Vadim Gritsenko wrote:
Antonio Gallardo wrote:
WDYT?
I agree with all points, but personally I'd prefer to release 2.2
(defined as: 2.1 + new core + mvn monolithic build) and stop
maintenance of 2.1 branch. Don't you think this will be a better
alternative? :)
Vadim
Even if trunk
From: Ralph Goers [EMAIL PROTECTED]
Date: Fri, 24 Mar 2006 14:22:18 -0800
Even if trunk isn't released for months, I'd prefer that 2.1.9 become 2.2
before switching to JDK 1.4. In other words, I'm not in favor of 2.1.x
ever being upgraded to JDK 1.4. However, I'm ok with creating a 2.2.x
12 matches
Mail list logo
