Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me please with proof-reading the announcment message
Jeroen Reijn wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me please with proof-reading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Giacomo Pati wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Could somebody help me please
Reinhard Poetz said the following on 26/10/07 18:34:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Sorry to reply so late, I'm currently out
hepabolu wrote:
Reinhard Poetz said the following on 26/10/07 18:34:
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2
page and hope to finish it this weekend.
Sorry to reply so late,
Grzegorz Kossakowski wrote:
BTW. When can we expect new release officialy announced?
I've started to work on it together with a What's new in Cocoon 2.2 page and
hope to finish it this weekend.
--
Reinhard PötzManaging Director, {Indoqa} GmbH
Reinhard Poetz pisze:
The relese of these artifacts has been accepted by 5 +1 votes and no -1.
I will move the artifacts into the Apache Maven M2 sync repository asap
and also prepare an announcement mail.
I was late on voting (gosh, I'm really busy now...) but I would like to say
that I
Reinhard Poetz wrote:
I've prepared another series of releases from trunk, see the list of all 45
artifacts below.
[...]
SUBPROJECT: COCOON CONFIGURATION
- cocoon-configuration-api-1.0.1.jar
- cocoon-spring-configurator-1.0.1.jar
SUBPROJECT:
Reinhard Poetz wrote:
I've prepared another series of releases from trunk, see the list of all 45
artifacts below.
...
- cocoon-configuration-api-1.0.1.jar
- cocoon-spring-configurator-1.0.1.jar
- cocoon-servlet-service-impl-1.0.0-RC1.jar
- cocoon-servlet-service-components-1.0.0-RC1.jar
On 15.10.2007 3:38 Uhr, Reinhard Poetz wrote:
I've prepared another series of releases from trunk, see the list of all 45
artifacts below. This time most of the modules are proposed to be
released as RC2 (release candidate 2) or RC1.
+1
Joerg
I've prepared another series of releases from trunk, see the list of all 45
artifacts below. This time most of the modules are proposed to be released as
RC2 (release candidate 2) or RC1.
This is probably be the last release before the final release of all those
modules. For this final
Reinhard Poetz wrote:
I've prepared another series of releases from trunk
+1
--
Reinhard PötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I've prepared another series of releases from trunk
+1
We need to revert CTemplate springification for RC2, what about CForms?
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
Leszek Gawron wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I've prepared another series of releases from trunk
+1
We need to revert CTemplate springification for RC2, what about CForms?
Sorry about the noise - I forgot those are branched. The CTemplate
release is ok.
--
Leszek
On 10/15/07, Reinhard Poetz [EMAIL PROTECTED] wrote:
I've prepared another series of releases from trunk, see the list of all 45
artifacts below. This time most of the modules are proposed to be released as
RC2 (release candidate 2) or RC1.
Nicely done. +1
--
Peter Hunsberger
Reinhard Poetz schrieb:
I've prepared another series of releases from trunk.
+1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
You can find the staged versions of the modules (sources, binaries,
javadocs +
checksums + gpg signatures) at http://people.apache.org/builds/cocoon/.
SVN tags
of all these artifacts can be found at
Reinhard Poetz schrieb:
I prepared another series of releases from trunk, see the list of all 43
modules below. Most of them are proposed to be released as RC1
(release candidate 1). The exceptions are
- the forms and the ajax block which need more work related to their
usage
of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo Pati wrote:
Reinhard Poetz wrote:
You can find the staged versions of the modules (sources, binaries,
javadocs +
checksums + gpg signatures) at http://people.apache.org/builds/cocoon/.
SVN tags
of all these artifacts can be found
Giacomo Pati pisze:
I could confirm that Cocoon was working up to last friday. But after updating
my local repo an hour
ago or so, I'm facing serious problems with Cocoon throwing an exception like
the one below so I
have to revert my previous vote to a _-1_:
Do you use Cocoon from trunk or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
I could confirm that Cocoon was working up to last friday. But after
updating my local repo an hour
ago or so, I'm facing serious problems with Cocoon throwing an
exception like the one below so
Giacomo Pati wrote:
Grzegorz Kossakowski wrote:
Giacomo Pati pisze:
I could confirm that Cocoon was working up to last friday. But after
updating my local repo an hour
ago or so, I'm facing serious problems with Cocoon throwing an
exception like the one below so I
have to revert my previous
The proposed modules have been accepted by 4 +1 (Giacomo voted at a different
thread but meant take 3) and 1 +0 vote. I will move the artifacts into the
Apache Maven M2 sync repository asap.
I will work on the website and an announcement mail but this will take some more
time though.
--
Reinhard Poetz wrote:
Because of Vadim's findings
(http://marc.info/?l=xml-cocoon-devm=118295221205686w=2) I've
recreated following release artifacts
org.apache.cocoon.cocoon:4
org.apache.cocoon:cocoon-pipeline-impl:1.0.0-RC1
org.apache.cocoon:cocoon-core:2.2.0-RC1
Thanks for all your
Because of Vadim's findings
(http://marc.info/?l=xml-cocoon-devm=118295221205686w=2) I've recreated
following release artifacts
org.apache.cocoon.cocoon:4
org.apache.cocoon:cocoon-pipeline-impl:1.0.0-RC1
org.apache.cocoon:cocoon-core:2.2.0-RC1
- o -
I
+1
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Reinhard Poetz pisze:
Because of Vadim's findings
(http://marc.info/?l=xml-cocoon-devm=118295221205686w=2) I've
recreated following release artifacts
org.apache.cocoon.cocoon:4
org.apache.cocoon:cocoon-pipeline-impl:1.0.0-RC1
org.apache.cocoon:cocoon-core:2.2.0-RC1
Reinhard, I've searched
Reinhard Poetz wrote:
I prepared another series of releases from trunk, see the list of all 43
artifacts below.
...
Core artifacts (jar)
org.apache.cocoon:cocoon-pipeline-api:1.0.0-RC1
org.apache.cocoon:cocoon-util:1.0.0-RC1
org.apache.cocoon:cocoon-xml-api:1.0.0-RC1
All of maven-metadata.xml files have no license header either.
Dejavu? We had that on commons already ;)
IMO not required to have a license in there.
cheers
--
Torsten
Torsten Curdt wrote:
All of maven-metadata.xml files have no license header either.
Dejavu? We had that on commons already ;)
IMO not required to have a license in there.
Shrug. :) As I've said I've no idea if this is indeed not required.
Vadim
Vadim Gritsenko wrote:
cocoon-core-2.2.0-RC1-tests.jar and
cocoon-pipeline-impl-1.0.0-RC1-tests.jar have no required LICENSE,
NOTICE files.
*argh*
cocoon-4.pom file has no license header.
I guess it got lost after the first release :-(
All of maven-metadata.xml files have no license
Since no PMC can overrule ASF wide release guidelines (see Vadim's findings), we
can't release the proposed artifacts as they are.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
All of maven-metadata.xml files have no license header either.
Do we really have to add our license header to those files? AFAICS
nobody does it. Do they really contain (enough) protectable
intellectual property? I don't think so.
Me neither. I think that's nitpicking. It's more than
Reinhard Poetz pisze:
I prepared another series of releases from trunk, see the list of all 43
artifacts below. The problems with references to snapshots and the usage
of the repository element in some of the poms are sorted out.
snip/
This majority vote stays open for 120 hours.
+1
The best I could do would be +0. I haven't had time to work with it.
Ralph
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
I prepared another series of releases from trunk, see the list of all 43
artifacts below. The problems with references to snapshots and the
usage of the repository
On 26.06.2007 19:32, Ralph Goers wrote:
The best I could do would be +0. I haven't had time to work with it.
Unfortunately the same here.
Joerg
Hi all,
I'm afraid it's the same here. I've been going through some samples.
They seem to be fine, but I've been too occupied lately to give a good
vote. So +0 on my behalve.
Regards,
Jeroen Reijn
Joerg Heinicke wrote:
On 26.06.2007 19:32, Ralph Goers wrote:
The best I could do would be
Reinhard Poetz wrote:
snip/
You can find the staged versions of all modules (sources, binaries,
javadocs +
checksums + gpg signatures) at
- http://people.apache.org/builds/cocoon/
(Maven 2 repo)
- http://people.apache.org/builds/cocoon/cocoon-2.2RC1-all.tar.gz
(tar archive of all
Reinhard Poetz pisze:
I prepared another series of releases from trunk, see the list of all 43
artifacts below. The problems with references to snapshots and the usage
of the repository element in some of the poms are sorted out.
Most of the modules are proposed to be released as RC1
I prepared another series of releases from trunk, see the list of all 43
artifacts below. The problems with references to snapshots and the usage of the
repository element in some of the poms are sorted out.
Most of the modules are proposed to be released as RC1 (release candidate 1).
The
Because of Joakim's and Grek's findings, I hereby withdraw the vote. I will
provide the corrected artifacts
org.apache.cocoon:cocoon-22-archetype-block:1.0.0-RC1
org.apache.cocoon:cocoon-22-archetype-block-plain:1.0.0-RC1
org.apache.cocoon:cocoon-22-archetype-webapp:1.0.0-RC1
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
I prepared another series of releases from trunk, see the list of all 43
artifacts below.
...
You can find the staged versions of the modules (sources, binaries,
javadocs + checksums + gpg signatures) at
http://people.apache.org/builds/cocoon/.
I prepared another series of releases from trunk, see the list of all 43
artifacts below. This time most of the modules are proposed to be released as
RC1 (release candidate 1). The exceptions are
- the forms and the ajax block which need more work related to their usage
of the servlet
Reinhard Poetz wrote:
snip/
You can find the staged versions of the modules (sources, binaries,
javadocs +
checksums + gpg signatures) at http://people.apache.org/builds/cocoon/.
SVN tags
of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
snip/
Reinhard Poetz wrote:
I prepared another series of releases from trunk, see the list of all 43
artifacts below.
...
You can find the staged versions of the modules (sources, binaries,
javadocs + checksums + gpg signatures) at http://people.apache.org/builds/cocoon/.
To produce a binding
I count
4 binding +1 votes
1 non-binding +1 vote
This means that the vote passed. I will push the proposed artifacts to the
official Maven repository and draft an announcment mail ASAP.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
Please cast your votes, whether we want to make the proposed artifacts
official releases and publish them to the Maven repository. The vote is
open for 72 hours.
+1
- --
Giacomo Pati
Otego AG, Switzerland -
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
Please cast your votes, whether we want to make the proposed artifacts
official releases and publish them to the Maven repository. The vote is
open for 72 hours.
+1
+1 .. and hoping for fast final
Leszek Gawron wrote:
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinhard Poetz wrote:
Please cast your votes, whether we want to make the proposed artifacts
official releases and publish them to the Maven repository. The vote is
open for 72 hours.
+1
+1 .. and
I added [vote] to the subject of this thread.
Reinhard Poetz wrote:
Please cast your votes, whether we want to make the proposed artifacts
official
releases and publish them to the Maven repository. The vote is open for 72
hours.
+1
Carsten
--
Carsten Ziegeler
Carsten Ziegeler napisał(a):
I added [vote] to the subject of this thread.
Reinhard Poetz wrote:
Please cast your votes, whether we want to make the proposed artifacts official
releases and publish them to the Maven repository. The vote is open for 72 hours.
+1
I've tested it
Carsten Ziegeler wrote:
I added [vote] to the subject of this thread.
Reinhard Poetz wrote:
Please cast your votes, whether we want to make the proposed artifacts official
releases and publish them to the Maven repository. The vote is open for 72 hours.
+1
+1
--
Reinhard Pötz
It's time for another series of module releases, see the list of all 41
artifacts below. SVN tags of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
Note that this time there are two artifacts that are proposed to be final
releases. See
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
The build runs through again, at least for me. I tested with an
empty local repository. Could others please verify?
Consistently fails with
Strange :-(
Can you run the tests from within your IDE
Reinhard Poetz wrote:
Thanks.
When I ran the tests the last time, they run through but this was before
Carsten
has started with his refactorings of the portal-impl block.
I guess that he will clean up the tests too after he has finished his work.
Sure :)
I started converting all
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
The build runs through again, at least for me. I tested with an
empty local repository. Could others please verify?
Consistently fails with
Strange :-(
Can you run the tests from within your IDE and find out what exactly
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
The build runs through again, at least for me. I tested with an
empty local repository. Could others please verify?
Consistently fails with
---
T E S T S
Simone Gianni wrote:
Reinhard Poetz wrote:
I've been working on the release for the past couple of hours. As it's
late here, I need some sleep. Unfortunatly this means that the trunk
is broken ATM. I will continue later today and fix all poms.
Sorry for any inconveniences.
Just a quick
Reinhard Poetz wrote:
I've been working on the release for the past couple of hours. As it's
late here, I need some sleep. Unfortunatly this means that the trunk is
broken ATM. I will continue later today and fix all poms.
Sorry for any inconveniences.
So far I've created the release
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I've been working on the release for the past couple of hours. As it's
late here, I need some sleep. Unfortunatly this means that the trunk is
broken ATM. I will continue later today and fix all poms.
Sorry for any inconveniences.
So far I've
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I've been working on the release for the past couple of hours. As it's
late here, I need some sleep. Unfortunatly this means that the trunk is
broken ATM. I will continue later today and fix all poms.
Sorry for any
Reinhard Poetz wrote:
The build runs through again, at least for me. I tested with an empty
local repository. Could others please verify?
Consistently fails with
---
T E S T S
---
Running
Reinhard Poetz wrote:
I've been working on the release for the past couple of hours. As it's
late here, I need some sleep. Unfortunatly this means that the trunk
is broken ATM. I will continue later today and fix all poms.
Sorry for any inconveniences.
Just a quick question. Why don't we
On Tue, Feb 13, 2007 at 12:00:19PM +0100, Simone Gianni wrote:
Reinhard Poetz wrote:
I've been working on the release for the past couple of hours. As it's
late here, I need some sleep. Unfortunatly this means that the trunk
is broken ATM. I will continue later today and fix all poms.
I've been working on the release for the past couple of hours. As it's late
here, I need some sleep. Unfortunatly this means that the trunk is broken ATM. I
will continue later today and fix all poms.
Sorry for any inconveniences.
--
Reinhard Pötz Independent Consultant, Trainer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 9 Feb 2007, Jorg Heymans wrote:
Date: Fri, 09 Feb 2007 22:19:22 +0100
From: Jorg Heymans [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Releasing from trunk
Giacomo Pati wrote:
It's the default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 7 Feb 2007, Carsten Ziegeler wrote:
Date: Wed, 07 Feb 2007 11:21:32 +0100
From: Carsten Ziegeler [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Releasing from trunk
Andrew Savory wrote:
Hi
Vadim Gritsenko wrote:
Make it easy to try it and people will come.
I do totally agree. As showed at cocoon-gt, I have a IzPack based
installer that already delivers a cocoon dist, with a small gui with
three buttons (start server, stop server, open welcome page) that start
and stop an embedded
Giacomo Pati wrote:
Andrew Savory wrote:
And yes, I'm putting my money where my mouth is and trying to use 2.2
to build a site ;-)
I absolutely support Carsten here. Addmittedly we only have a few core
devs that use 2.2 for their daily work and business. But tell me,
Andrew, who else is
Simone Gianni wrote:
Vadim Gritsenko wrote:
Make it easy to try it and people will come.
I do totally agree. As showed at cocoon-gt, I have a IzPack based
installer that already delivers a cocoon dist, with a small gui with
three buttons (start server, stop server, open welcome page) that
Vadim Gritsenko wrote:
Simone Gianni wrote:
Vadim Gritsenko wrote:
Make it easy to try it and people will come.
I do totally agree. As showed at cocoon-gt, I have a IzPack based
installer that already delivers a cocoon dist, with a small gui with
three buttons (start server, stop server,
Vadim Gritsenko wrote:
Simone Gianni wrote:
Vadim Gritsenko wrote:
Make it easy to try it and people will come.
I do totally agree. As showed at cocoon-gt, I have a IzPack based
installer that already delivers a cocoon dist, with a small gui with
three buttons (start server, stop server,
Hi,
On 9 Feb 2007, at 15:04, Giacomo Pati wrote:
I absolutely support Carsten here. Addmittedly we only have a few
core devs that use 2.2 for their daily work and business. But tell
me, Andrew, who else is using/testing 2.2 in real world
environments, you?
Hang on, that's my point - not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 7 Feb 2007, Jorg Heymans wrote:
Date: Wed, 07 Feb 2007 20:03:46 +0100
From: Jorg Heymans [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Releasing from trunk
Vadim Gritsenko wrote:
Continuum
Hi,
On 9 Feb 2007, at 16:15, Simone Gianni wrote:
As soon as someone else gives it's +1, I'll work on it on Sunday.
As discussed offline: a huge +1!
Thanks,
Andrew.
--
Andrew Savory, Managing Director, Luminas Limited
Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135
Web:
Giacomo Pati wrote:
It's the default of Continuum to build a modularized M2 project in
isolation (see build command in the Continuum Config Page). We build our
modularized M2 project as a hole and do not have the problem you
mentioned above. It is just a matter how you define your project in
Carsten Ziegeler wrote:
Perhaps David can help as he did the conversion for Cocoon.
FYI David is working on this. As soon as he's ready i'll reroll the
release (from trunk) and call the vote.
Jorg
Reinhard Poetz wrote:
I also think that it is an *important signal to us*: 2.2 is complete,
the contracts are stable and they can't be changed
One thing to add: As Cocoon is modularized now, we can and _will_ have different
release cycles for our modules, e.g. if we think it's useful we can
On 2/7/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...The version from trunk is used by several of us
already in production, several people have tried it out and it seems
that most of the problems have been fixed. So I really think that this
qualifies for an RC release...
Excuse the silly
Reinhard Poetz skrev:
Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
RC has a meaning of release candidate, which to most people means
well tested almost production quality code. Going through recent
commits I noticed a lot of refactoring, new code, untested code, and
so on. This hardly
Hi,
On 7 Feb 2007, at 07:13, Carsten Ziegeler wrote:
I really doubt that most of the code for final releases (or rc) is
tested better than what we currently have in trunk. We do releases for
2.1.x without real tests for most of the code base. We rely on user
experience/tests. The version from
Andrew Savory wrote:
Hi,
Not wishing to spread FUD and rain on the parade, but ... I think 2.2
is *massively* less tested than 2.1.x. The main reason 2.1.x goes out
with not much testing is because it's been used in production by a
very large number of people. How many are actually
Carsten Ziegeler wrote:
Andrew Savory wrote:
Hi,
Not wishing to spread FUD and rain on the parade, but ... I think 2.2
is *massively* less tested than 2.1.x. The main reason 2.1.x goes out
with not much testing is because it's been used in production by a
very large number of people.
Reinhard Poetz wrote:
What we need now is more people
who use/try it and in this sense it doesn't help to ship more milestone
releases.
Make it easy to try it and people will come.
http://cocoon.apache.org/mirror.cgi
http://cocoon.apache.org/2.2/
Contrast and compare with 2.1
Vadim Gritsenko wrote:
You are missing a point. It's not about a bug free version. It is about a
version which seen more than like 4 hours of testing after major surgery.
Sorry, but that's not fair. There were no code or api changes to the
core in the last weeks (apart from bug fixes). There
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
[...]
We need to get a 2.2 out; imho it is more important to have something
out after so many years than having a 115% bug free version.
You are missing a point. It's not about a bug free version. It is about
a version which seen more than
Carsten Ziegeler wrote:
[...]
Anyways, I'm a little bit clueless how to continue. Some of us say,
let's call it RC, some say no as things are missing.
Since writing more mails would take longer than releasing another series of core
milestone releases, I will release cocoon-core-2.2 as M3.
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
It is a bit
different for 2.2 though: there were no real downloadable release yet,
And maybe there will never be one. Don't know. There doesn't seem to be
much energy in this community to provide it - especially if you use
Maven 2 you don't
Hi,
On 7 Feb 2007, at 14:01, Carsten Ziegeler wrote:
Now, I will ask the open question right away: who will work on the
missing parts?
FX: TUMBLEWEED
Gosh, no rush of people to say I will! ;-)
On 7 Feb 2007, at 14:49, Reinhard Poetz wrote:
From my experience over the last months, I'd say
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
It is a bit different for 2.2 though: there were no real
downloadable release yet,
And maybe there will never be one. Don't know. There doesn't seem to
be much energy in this community to provide it - especially if you
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
[...]
Anyways, I'm a little bit clueless how to continue. Some of us say,
let's call it RC, some say no as things are missing.
Since writing more mails would take longer than releasing another series of
core
milestone releases, I will
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Regardless of download presence, at the very least there should be a
2.2 site set up and running.
http://cocoon.apache.org/2.2/
IMNSHO we don't have http://cocoon.apache.org/2.2/ anymore. Information
about the core will be available at
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Anyways, I'm a little bit clueless how to continue. Some of us say,
let's call it RC, some say no as things are missing.
Since writing more mails would take longer than releasing another series of core
milestone releases,
Vadim Gritsenko wrote:
Continuum was stopped because I started to flatten the POM hierarchy
in trunk. This will hopefully save me a lot of time during the release
process.
Do I understand it correctly - it should be turned off to simplify
release process? Sounds Ok to me if that's the case.
Jorg Heymans wrote:
So for me, currently, the best solution ATM for CI would be to cron
something like this:
#!/bin/bash
rm -fr ~/.m2/repository
Or:
rm -rf ~/.m2/repository/org/apache/cocoon
cd src/cocoon-trunk
svn update
mvn clean install ~/cocoon-build.log 21
if [ $? -ne 0 ]; then
Vadim Gritsenko wrote:
#!/bin/bash
rm -fr ~/.m2/repository
Or:
rm -rf ~/.m2/repository/org/apache/cocoon
possibly yes. I'm still debating the usefulness of downloading
everything new each time. It was useful back in the days where existing
poms were updated, they seem to have this
Reinhard Poetz wrote:
As scheduled some weeks ago I want to ask for opinions about a next
series of module releases.
Here my proposal:
- release cocoon-configuration-api and cocoon-spring-configuratur as 1.0
- release cocoon-core (+ all submodules) as RC1
- release the archetypes as RC1
1 - 100 of 133 matches
Mail list logo
