You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Pötz <re...@apache.org> on 2011/01/04 00:36:34 UTC
Preparing releases: cocoon-maven-plugin, cocoon-jnet, cocoon-thien-maven-site-skin
For the last couple of months I haven't been following Cocoon
development closely, but I want to work again on a couple of things
related to Cocoon.
First I'd like to start with the release of some long overdue modules:
* cocoon-maven-plugin (plus cocoon-rcl-*):
Using the Cocoon Maven plugin to provide a launcher environment
(cocoon:prepare) which references Spring 3, causes an
AbstractMethodError.
See http://cocoon.markmail.org/message/hapiusamiic4uzq2
It has been in use for quite a while, hence I'd like to
release it as 1.0.0
* cocoon-jnet
There is a chance to produce a NPE in
DynamicURLStreamHandlerFactoryBecause
See https://issues.apache.org/jira/browse/COCOON-2277
Since it's only a bug fix release that can be used as a
drop-in replacement for 1.1.0, I suggest releasing it as
1.1.1
* cocoon-thien-maven-site-skin
It has never been released yet. Cocoon 3 also uses this
skin which requires a manual build of it before the
Cocoon 3 site can be created. That's not a really comfortable
for people that are only interested in building the C3 site.
It has been in use for quite a while, hence I'd like to
release it as 1.0.0
Since the Cocoon Maven plugin and the cocoon-rcl-* modules are used in
Cocoon 2 and 3 I'd like to move them to a more general place. For that
purpose I suggest moving them to cocoon/trunk/subprojects.
WDYT?
--
Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch
http://www.indoqa.com/people/reinhard-poetz.html
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
Re: Preparing releases: cocoon-maven-plugin, cocoon-jnet, cocoon-thien-maven-site-skin
Posted by Simone Tripodi <si...@apache.org>.
+1 for me, there I don't see any blocking issue.
thanks for taking care about it!
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Tue, Jan 4, 2011 at 4:27 PM, Peter Hunsberger
<pe...@gmail.com> wrote:
> On Tue, Jan 4, 2011 at 1:51 AM, Reinhard Pötz <re...@apache.org> wrote:
>> On 01/04/2011 03:38 AM, Peter Hunsberger wrote:
>>>
>>> On Mon, Jan 3, 2011 at 5:36 PM, Reinhard Pötz<re...@apache.org> wrote:
>>>>
>>>>
>>>
>>> +1 - I'm not completely sure about whether 1.0 is completely correct
>>> in some cases, but OTOH I don't think it's worth worrying about...
>>
>> Neither am I but changing any contracts without some deprecation phase in
>> the cocoon-maven-plugin or the site-skin wouldn't be very helpful to the
>> existing users. And, there's always the chance of a 2.x release ;-)
>>
> Hah. I won't say, "not in my life time", but I'm sure not going to
> hold my breath....
>
> --
> Peter Hunsberger
>
Re: Preparing releases: cocoon-maven-plugin, cocoon-jnet, cocoon-thien-maven-site-skin
Posted by Peter Hunsberger <pe...@gmail.com>.
On Tue, Jan 4, 2011 at 1:51 AM, Reinhard Pötz <re...@apache.org> wrote:
> On 01/04/2011 03:38 AM, Peter Hunsberger wrote:
>>
>> On Mon, Jan 3, 2011 at 5:36 PM, Reinhard Pötz<re...@apache.org> wrote:
>>>
>>>
>>
>> +1 - I'm not completely sure about whether 1.0 is completely correct
>> in some cases, but OTOH I don't think it's worth worrying about...
>
> Neither am I but changing any contracts without some deprecation phase in
> the cocoon-maven-plugin or the site-skin wouldn't be very helpful to the
> existing users. And, there's always the chance of a 2.x release ;-)
>
Hah. I won't say, "not in my life time", but I'm sure not going to
hold my breath....
--
Peter Hunsberger
Re: Preparing releases: cocoon-maven-plugin, cocoon-jnet, cocoon-thien-maven-site-skin
Posted by Reinhard Pötz <re...@apache.org>.
On 01/04/2011 03:38 AM, Peter Hunsberger wrote:
> On Mon, Jan 3, 2011 at 5:36 PM, Reinhard Pötz<re...@apache.org> wrote:
>>
>> For the last couple of months I haven't been following Cocoon development closely, but I want to work again on a couple of things related to Cocoon.
>>
>> First I'd like to start with the release of some long overdue modules:
>>
>> * cocoon-maven-plugin (plus cocoon-rcl-*):
>
>> It has been in use for quite a while, hence I'd like to
>> release it as 1.0.0
>>
>> * cocoon-jnet
>
>> Since it's only a bug fix release that can be used as a
>> drop-in replacement for 1.1.0, I suggest releasing it as
>> 1.1.1
>>
>> * cocoon-thien-maven-site-skin
>
>> It has been in use for quite a while, hence I'd like to
>> release it as 1.0.0
>>
>> Since the Cocoon Maven plugin and the cocoon-rcl-* modules are used in Cocoon 2 and 3 I'd like to move them to a more general place. For that purpose I suggest moving them to cocoon/trunk/subprojects.
>>
>> WDYT?
>>
>
> +1 - I'm not completely sure about whether 1.0 is completely correct
> in some cases, but OTOH I don't think it's worth worrying about...
Neither am I but changing any contracts without some deprecation phase
in the cocoon-maven-plugin or the site-skin wouldn't be very helpful to
the existing users. And, there's always the chance of a 2.x release ;-)
--
Reinhard Pötz Founder & Managing Director, Indoqa and Deepsearch
http://www.indoqa.com/people/reinhard-poetz.html
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________
Furthermore, I think Oracle has to honor the JSPA agreement.
http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
Re: Preparing releases: cocoon-maven-plugin, cocoon-jnet, cocoon-thien-maven-site-skin
Posted by Peter Hunsberger <pe...@gmail.com>.
On Mon, Jan 3, 2011 at 5:36 PM, Reinhard Pötz <re...@apache.org> wrote:
>
> For the last couple of months I haven't been following Cocoon development closely, but I want to work again on a couple of things related to Cocoon.
>
> First I'd like to start with the release of some long overdue modules:
>
> * cocoon-maven-plugin (plus cocoon-rcl-*):
> It has been in use for quite a while, hence I'd like to
> release it as 1.0.0
>
> * cocoon-jnet
> Since it's only a bug fix release that can be used as a
> drop-in replacement for 1.1.0, I suggest releasing it as
> 1.1.1
>
> * cocoon-thien-maven-site-skin
> It has been in use for quite a while, hence I'd like to
> release it as 1.0.0
>
> Since the Cocoon Maven plugin and the cocoon-rcl-* modules are used in Cocoon 2 and 3 I'd like to move them to a more general place. For that purpose I suggest moving them to cocoon/trunk/subprojects.
>
> WDYT?
>
+1 - I'm not completely sure about whether 1.0 is completely correct
in some cases, but OTOH I don't think it's worth worrying about...
--
Peter Hunsberger