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 Poetz <re...@apache.org> on 2007/03/28 18:57:42 UTC
[release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
I plan to release the next series of Cocoon artifacts (core + many blocks +
achetypes + rcl-maven-plugin) after the Easter break, this time called "RC1 -
release candidate ". Actually I wanted to do it this week but there are some
issues open that need to be resolved before:
- I want to get a (minimal) Cocoon 2.2 website online. Otherwise most of the
work is only for insiders as people not following dev@ don't know where to
start or even worse, don't know that 2.2 exists.
- Our root POM has dependencies on the Daisy Maven plugin which is currently
only available as a SNAPSHOT version. For the previous releases I commented
the relevent sections but this is tedious, actually unproductive work
that I want to get rid of.
- Torsten will provide a first release candidate of commons-jci very soon. This
means that we can release the cocoon-rcl-* modules too.
Are there any other issues that have to be resolved before we ship modules as
release candidates (remember, RC means that the contracts will become stable)?
- o -
Some things that would be nice to have but I don't want to let them delay the
release of other modules:
- the cforms block still depends on a xreporter library which isn't
available at the central Maven repo. I'm -1 on shipping anything as RC or
final, that has a depenency on some artifact that is not available at
the central Maven repo.
- the cforms block should make use of the features, that the servlet service
framework provides. Grek is working on it in our whiteboard. IIRC we
agreed on copying all blocks that are included into branch_21 using
svn_externals at the end of March (forms, ajax, template, etc.).
If those two issues are not resolved within the next 10 days, I will release
cforms as M3 instead of RC1.
Comments?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> Reinhard Poetz wrote:
>
>>
>> The limiting factor is that nobody has done it yet. It would be great
>> if you create the artifact and put it into the Apache snapshot repo.
>> Then we have some time to test it and if everything works fine, Marc will
>
> I've created a 1.3-SNAPSHOT off [1] and put it in
> m1-snapshot-repository. I've tested this locally and it seems to be OK.
>
> You can test it by modifying the cforms-impl pom :
>
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 525249)
> +++ pom.xml (working copy)
> @@ -129,7 +129,7 @@
> <dependency>
> <groupId>xreporter</groupId>
> <artifactId>xreporter-expression</artifactId>
> - <version>r683</version>
> + <version>1.3-SNAPSHOT</version>
> </dependency>
> <dependency>
> <groupId>junit</groupId>
>
> Please have a look and let me know in case of problems.
>
>
> Regards
> Jorg
>
> [1]
> http://svn.cocoondev.org/viewsvn/trunk/xreporter/?rev=684&root=xreporter
>
>
Thanks Jorg! I will add it to forms-impl/pom.xml ASAP and test it.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
Posted by Jorg Heymans <jh...@apache.org>.
Reinhard Poetz wrote:
>
> The limiting factor is that nobody has done it yet. It would be great if
> you create the artifact and put it into the Apache snapshot repo. Then
> we have some time to test it and if everything works fine, Marc will
I've created a 1.3-SNAPSHOT off [1] and put it in
m1-snapshot-repository. I've tested this locally and it seems to be OK.
You can test it by modifying the cforms-impl pom :
Index: pom.xml
===================================================================
--- pom.xml (revision 525249)
+++ pom.xml (working copy)
@@ -129,7 +129,7 @@
<dependency>
<groupId>xreporter</groupId>
<artifactId>xreporter-expression</artifactId>
- <version>r683</version>
+ <version>1.3-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>junit</groupId>
Please have a look and let me know in case of problems.
Regards
Jorg
[1] http://svn.cocoondev.org/viewsvn/trunk/xreporter/?rev=684&root=xreporter
Re: [release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
Posted by Reinhard Poetz <re...@apache.org>.
Jorg Heymans wrote:
> Reinhard Poetz wrote:
>
>> - the cforms block still depends on a xreporter library which isn't
>> available at the central Maven repo. I'm -1 on shipping anything as RC
>> or final, that has a depenency on some artifact that is not
>> available at the central Maven repo.
>
> what is blocking this? If its just that someone needs to put the jar
> into maven2 jira for upload then i'll do it.
I remember having already answered to this mail ... anyway.
The limiting factor is that nobody has done it yet. It would be great if you
create the artifact and put it into the Apache snapshot repo. Then we have some
time to test it and if everything works fine, Marc will release it officially.
It's important that the release comes from the xreporter core developer team and
not from us.
Thanks Jorg for picking up this issue!
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
Posted by Jorg Heymans <jh...@apache.org>.
Reinhard Poetz wrote:
> - the cforms block still depends on a xreporter library which isn't
> available at the central Maven repo. I'm -1 on shipping anything as
> RC or final, that has a depenency on some artifact that is not
> available at the central Maven repo.
what is blocking this? If its just that someone needs to put the jar
into maven2 jira for upload then i'll do it.
Jorg
Re: Eclipse: Uppercase META-INF files
Posted by Carsten Ziegeler <cz...@apache.org>.
Andreas Hartmann wrote:
> Joerg Heinicke schrieb:
>
> [...]
>
>> There is currently a problem with that setup with the
>> branch in Eclipse. All the linked trunk blocks have notice.txt and
>> license.txt - but in different cases (actually all have in lower case
>> except template block where everything is in upper case). Eclipse does
>> not like it as they all will end up in the same target directory:
>>
>> The project was not built due to "A resource exists with a different
>> case: /Cocoon 2.1.10-dev/build/eclipse/classes/META-INF/notice.txt.".
>> Fix the problem, then try refreshing this project and building it since
>> it may be inconsistent.
>
> Will this be solved soon, or is it recommended to use a local workaround
> (e.g. rename the files)?
>
Though I hope that this will be solved soon, excluding the files in
Eclipse works well.
Carsten
--
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/
Eclipse: Uppercase META-INF files (was: [release] Prepare RC1 from
trunk)
Posted by Andreas Hartmann <an...@apache.org>.
Joerg Heinicke schrieb:
[...]
> There is currently a problem with that setup with the
> branch in Eclipse. All the linked trunk blocks have notice.txt and
> license.txt - but in different cases (actually all have in lower case
> except template block where everything is in upper case). Eclipse does
> not like it as they all will end up in the same target directory:
>
> The project was not built due to "A resource exists with a different
> case: /Cocoon 2.1.10-dev/build/eclipse/classes/META-INF/notice.txt.".
> Fix the problem, then try refreshing this project and building it since
> it may be inconsistent.
Will this be solved soon, or is it recommended to use a local workaround
(e.g. rename the files)?
TIA!
-- Andreas
Re: [release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
Posted by Joerg Heinicke <jo...@gmx.de>.
On 28.03.2007 18:57, Reinhard Poetz wrote:
> I plan to release the next series of Cocoon artifacts (core + many
> blocks + achetypes + rcl-maven-plugin) after the Easter break, this time
> called "RC1 - release candidate ".
+1
> IIRC we
> agreed on copying all blocks that are included into branch_21 using
> svn_externals at the end of March (forms, ajax, template, etc.).
Yes, finally! There is currently a problem with that setup with the
branch in Eclipse. All the linked trunk blocks have notice.txt and
license.txt - but in different cases (actually all have in lower case
except template block where everything is in upper case). Eclipse does
not like it as they all will end up in the same target directory:
The project was not built due to "A resource exists with a different
case: /Cocoon 2.1.10-dev/build/eclipse/classes/META-INF/notice.txt.".
Fix the problem, then try refreshing this project and building it since
it may be inconsistent.
Regards
Joerg
Re: [release] Prepare RC1 from trunk (core + many blocks + achetypes
+ rcl-maven-plugin)
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Reinhard Poetz napisał(a):
>
> I plan to release the next series of Cocoon artifacts (core + many
> blocks + achetypes + rcl-maven-plugin) after the Easter break, this
> time called "RC1 - release candidate ". Actually I wanted to do it
> this week but there are some issues open that need to be resolved before:
>
> - I want to get a (minimal) Cocoon 2.2 website online. Otherwise most
> of the
> work is only for insiders as people not following dev@ don't know
> where to
> start or even worse, don't know that 2.2 exists.
I agree and consider it as most important issue now. Speaking for
myself, I'm going to write Forms and Ajax migration guide and some
documents on servlet service fw. Some help would be greatly appreciated,
though. If nothing changes, I'll do it during Easter break.
> - the cforms block should make use of the features, that the servlet
> service
> framework provides. Grek is working on it in our whiteboard. IIRC we
> agreed on copying all blocks that are included into branch_21 using
> svn_externals at the end of March (forms, ajax, template, etc.).
>
> If those two issues are not resolved within the next 10 days, I will
> release cforms as M3 instead of RC1.
>
> Comments?
>
Yes I work on it but don't think I'll finish it within 10 days. I'm
going to have important exam on Monday and give presentation (about
Cocoon) for Warsaw Java User Group on Tuesday so serious work start in
mid of next week. I wonder if we want postable sources implemented
before RC is released?
This should not break any existing contracts as it will be an addition
but will seriously impact how applications should be developed.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/