Re: Releases from trunk
Reinhard Poetz wrote:
I think it's time to release the next milestone of some of our modules:
- org.apache.cocoon:cocoon(pom)
- org.apache.cocoon:cocoon-core-modules (pom)
- org.apache.cocoon:cocoon-core (jar)
- org.apache.cocoon:cocoon-blocks-modules (pom)
- org.apache.cocoon:cocoon-template (pom)
- org.apache.cocoon:cocoon-flowscript (pom)
- org.apache.cocoon:cocoon-template-impl (jar)
- org.apache.cocoon:cocoon-flowscript-impl(jar)
- org.apache.cocoon:cocoon-blocks-fw (pom)
- org.apache.cocoon:cocoon-blocks-fw-impl (jar)
- org.apache.cocoon:cocoon-tools-modules (pom)
- org.apache.cocoon:cocoon-archetypes (pom)
- org.apache.cocoon:cocoon-22-archetype-block (archetype jar)
I copied the artifacts to the m2-ibibio-sync directory on people.apache.org. If
the automatic synchronization works correctly, the new artifacts should be
available from the central Maven repository (repo1.maven.org) very soon.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: Releases from trunk
Reinhard Poetz wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I think it's time to release the next milestone of some of our modules:
- org.apache.cocoon:cocoon(pom)
- org.apache.cocoon:cocoon-core-modules (pom)
- org.apache.cocoon:cocoon-core (jar)
- org.apache.cocoon:cocoon-blocks-modules (pom)
- org.apache.cocoon:cocoon-template (pom)
- org.apache.cocoon:cocoon-flowscript (pom)
- org.apache.cocoon:cocoon-template-impl (jar)
- org.apache.cocoon:cocoon-flowscript-impl(jar)
- org.apache.cocoon:cocoon-blocks-fw (pom)
- org.apache.cocoon:cocoon-blocks-fw-impl (jar)
- org.apache.cocoon:cocoon-tools-modules (pom)
- org.apache.cocoon:cocoon-archetypes (pom)
- org.apache.cocoon:cocoon-22-archetype-block (archetype jar)
I've started with the release of these modules. Please don't check in
into SVN if this changed any of them. Thanks!
So far I've released all pom modules. Tommorrow I'm going to continue
with the jar modules. As I've already set the versions in the pom.xml
files of the 'to be released' jar modules to the release version, you
won't have much luck to build Cocoon. Please don't fix this. Tommorrow
evening everything should work again.
I released all jar modules except the archetype. It will follow very soon,
together with instructions how to test/use and the vote.
- o -
cocoon/trunk should work again now. I was able to build it completly with an
empty local repository. I've changed all versions to the incremented snapshot
versions again. Thanks to Andreas for his script (pom-updater) which made this
task manageable at all.
This also means that you can check in to cocoon/trunk again as this shouldn't
cause any problems for the archetypes which are largely independent from the
rest of the codebase.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
Re: Releases from trunk
Reinhard Poetz wrote:
I think it's time to release the next milestone of some of our modules:
- org.apache.cocoon:cocoon(pom)
- org.apache.cocoon:cocoon-core-modules (pom)
- org.apache.cocoon:cocoon-core (jar)
- org.apache.cocoon:cocoon-blocks-modules (pom)
- org.apache.cocoon:cocoon-template (pom)
- org.apache.cocoon:cocoon-flowscript (pom)
- org.apache.cocoon:cocoon-template-impl (jar)
- org.apache.cocoon:cocoon-flowscript-impl(jar)
- org.apache.cocoon:cocoon-blocks-fw (pom)
- org.apache.cocoon:cocoon-blocks-fw-impl (jar)
- org.apache.cocoon:cocoon-tools-modules (pom)
- org.apache.cocoon:cocoon-archetypes (pom)
- org.apache.cocoon:cocoon-22-archetype-block (archetype jar)
I've started with the release of these modules. Please don't check in into SVN
if this changed any of them. Thanks!
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Releases from trunk
Reinhard Poetz wrote:
Reinhard Poetz wrote:
I think it's time to release the next milestone of some of our modules:
- org.apache.cocoon:cocoon(pom)
- org.apache.cocoon:cocoon-core-modules (pom)
- org.apache.cocoon:cocoon-core (jar)
- org.apache.cocoon:cocoon-blocks-modules (pom)
- org.apache.cocoon:cocoon-template (pom)
- org.apache.cocoon:cocoon-flowscript (pom)
- org.apache.cocoon:cocoon-template-impl (jar)
- org.apache.cocoon:cocoon-flowscript-impl(jar)
- org.apache.cocoon:cocoon-blocks-fw (pom)
- org.apache.cocoon:cocoon-blocks-fw-impl (jar)
- org.apache.cocoon:cocoon-tools-modules (pom)
- org.apache.cocoon:cocoon-archetypes (pom)
- org.apache.cocoon:cocoon-22-archetype-block (archetype jar)
I've started with the release of these modules. Please don't check in
into SVN if this changed any of them. Thanks!
So far I've released all pom modules. Tommorrow I'm going to continue with the
jar modules. As I've already set the versions in the pom.xml files of the 'to be
released' jar modules to the release version, you won't have much luck to build
Cocoon. Please don't fix this. Tommorrow evening everything should work again.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Releases from trunk
Reinhard Poetz wrote: I think it's time to release the next milestone of some of our modules: - org.apache.cocoon:cocoon(pom) - org.apache.cocoon:cocoon-core-modules (pom) - org.apache.cocoon:cocoon-core (jar) - org.apache.cocoon:cocoon-blocks-modules (pom) - org.apache.cocoon:cocoon-template (pom) - org.apache.cocoon:cocoon-flowscript (pom) - org.apache.cocoon:cocoon-template-impl (jar) - org.apache.cocoon:cocoon-flowscript-impl(jar) - org.apache.cocoon:cocoon-blocks-fw (pom) - org.apache.cocoon:cocoon-blocks-fw-impl (jar) - org.apache.cocoon:cocoon-tools-modules (pom) - org.apache.cocoon:cocoon-archetypes (pom) - org.apache.cocoon:cocoon-22-archetype-block (archetype jar) That's the minimal set of artifacts to do something useful with Cocoon and to follow the getting started guide. I know that we should release some more blocks (forms, fop, apples, etc.) and the archetype-webapp artifact, but they need some more polishing. I propose that we change the release procedure this time: The person who performs the release, releases the artifacts into our staging repository. Then he calls for a vote, open for 72 hours. If the vote passes, the artifacts are moved to the official Apache sync directory on people.apache.org. The last step is asking on repository@apache.org to sync with the Maven central repo. Is the list of artifacts and the outlined release procedure okay for everybody? If yes, I can do the relase on Thuesday, starting in the afternoon (MET). I am not clear about what is being suggested for this plan. If it is a milestone then it should not end up on the public central repository. If it is a release then it should be accompanied by the sources, etc. Also it should be on the w.a.o/dist mirrors as well as whatever Maven does. http://www.apache.org/dev/release.html#releases http://www.apache.org/dev/#releases -David
Re: Releases from trunk
Reinhard Poetz wrote:
I think it's time to release the next milestone of some of our modules:
- org.apache.cocoon:cocoon(pom)
- org.apache.cocoon:cocoon-core-modules (pom)
- org.apache.cocoon:cocoon-core (jar)
- org.apache.cocoon:cocoon-blocks-modules (pom)
- org.apache.cocoon:cocoon-template (pom)
- org.apache.cocoon:cocoon-flowscript (pom)
- org.apache.cocoon:cocoon-template-impl (jar)
- org.apache.cocoon:cocoon-flowscript-impl(jar)
- org.apache.cocoon:cocoon-blocks-fw (pom)
- org.apache.cocoon:cocoon-blocks-fw-impl (jar)
- org.apache.cocoon:cocoon-tools-modules (pom)
- org.apache.cocoon:cocoon-archetypes (pom)
- org.apache.cocoon:cocoon-22-archetype-block (archetype jar)
That's the minimal set of artifacts to do something useful with Cocoon
and to follow the getting started guide. I know that we should release
some more blocks (forms, fop, apples, etc.) and the archetype-webapp
artifact, but they need some more polishing.
I propose that we change the release procedure this time:
The person who performs the release, releases the artifacts into our
staging repository. Then he calls for a vote, open for 72 hours. If the
vote passes, the artifacts are moved to the official Apache sync
directory on people.apache.org. The last step is asking on
repository@apache.org to sync with the Maven central repo.
Is the list of artifacts and the outlined release procedure okay for
everybody? If yes, I can do the relase on Thuesday, starting in the
afternoon (MET).
Unfortunatly we have one showstopper: the dependency of cocoon-core on
commons-jci. The problem is that there is no release available and we can't
release something if it has a dependency on a snapshot releases.
For the time being I only see two options:
a) we get a release of commons-jci within the next few days, or
b) comment dependencies on this library for now
As I know about the current workload of Torsten, I don't think that we will get
a release very soon. So I guess that only option b) remains. Or is somebody of
us willing to support commons-jci to get a release out of the door?
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Releases from trunk
Reinhard Poetz schrieb: Reinhard Poetz wrote: I think it's time to release the next milestone of some of our modules: - org.apache.cocoon:cocoon(pom) - org.apache.cocoon:cocoon-core-modules (pom) - org.apache.cocoon:cocoon-core (jar) - org.apache.cocoon:cocoon-blocks-modules (pom) - org.apache.cocoon:cocoon-template (pom) - org.apache.cocoon:cocoon-flowscript (pom) - org.apache.cocoon:cocoon-template-impl (jar) - org.apache.cocoon:cocoon-flowscript-impl(jar) - org.apache.cocoon:cocoon-blocks-fw (pom) - org.apache.cocoon:cocoon-blocks-fw-impl (jar) - org.apache.cocoon:cocoon-tools-modules (pom) - org.apache.cocoon:cocoon-archetypes (pom) - org.apache.cocoon:cocoon-22-archetype-block (archetype jar) That's the minimal set of artifacts to do something useful with Cocoon and to follow the getting started guide. I know that we should release some more blocks (forms, fop, apples, etc.) and the archetype-webapp artifact, but they need some more polishing. I propose that we change the release procedure this time: The person who performs the release, releases the artifacts into our staging repository. Then he calls for a vote, open for 72 hours. If the vote passes, the artifacts are moved to the official Apache sync directory on people.apache.org. The last step is asking on repository@apache.org to sync with the Maven central repo. Is the list of artifacts and the outlined release procedure okay for everybody? If yes, I can do the relase on Thuesday, starting in the afternoon (MET). +1 for the procedure, +1 for you to go ahead :) I personally would like to see a release of the ajax and forms stuff as well; so including those modules would be great... :) Unfortunatly we have one showstopper: the dependency of cocoon-core on commons-jci. The problem is that there is no release available and we can't release something if it has a dependency on a snapshot releases. For the time being I only see two options: a) we get a release of commons-jci within the next few days, or b) comment dependencies on this library for now As I know about the current workload of Torsten, I don't think that we will get a release very soon. So I guess that only option b) remains. Or is somebody of us willing to support commons-jci to get a release out of the door? Let's comment this stuff out, I think we should move this into a separate module anyway and keep the core as small as possible. Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: Releases from trunk
Carsten Ziegeler wrote: Let's comment this stuff out, I think we should move this into a separate module anyway and keep the core as small as possible. +1 Jorg
Re: Releases from trunk
Carsten Ziegeler wrote:
Unfortunatly we have one showstopper: the dependency of cocoon-core on
commons-jci. The problem is that there is no release available and we can't
release something if it has a dependency on a snapshot releases.
For the time being I only see two options:
a) we get a release of commons-jci within the next few days, or
b) comment dependencies on this library for now
As I know about the current workload of Torsten, I don't think that we will get
a release very soon. So I guess that only option b) remains. Or is somebody of
us willing to support commons-jci to get a release out of the door?
Let's comment this stuff out, I think we should move this into a
separate module anyway and keep the core as small as possible.
For the last couple of days I have been working on a reloading classloader web
application wrapper. It reuses your code from the shielding classloader as it
intercepts all calls to servlets, filters and listeners. So far I have an
experimental version running on my laptop. The next step is writing a Maven
plugin that creates a Cocoon web application and integrates the wrapper.
I hope that I can check in a working version of the wrapper and the plugin over
the next days so that others, and especially Torsten can review my work.
If everything works as expected (setting classloaders can sometimes be very
tricky with a lot of strange exceptions) we can discuss whether we need the
feature of setting classloaders at sitemap level at all.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
