Kevan Miller wrote:

On Feb 26, 2008, at 10:13 AM, Joe Bohn wrote:


Is there a plan on how to release the samples for 2.1 and forward? It looks like the changes in the build structure have necessitated that we do something to release samples independently (or perhaps it was other changes). In past releases it looks like the samples were built, voted on, and released as part of the Geronimo release itself. However, they are no longer included under our configs with the restructure and hence they were not included in the process.

Should we create a tag for the 2.1 samples (thus far there are no tags in the samples svn (see https://svn.apache.org/repos/asf/geronimo/samples/ )? Do we need to create release candidates and vote on releasing samples now?

I ran into this because I took a first pass at generating a new geronimo-plugins.xml for 2.1 yesterday since the old version was still referencing 2.1-SNAPSHOT for all of the plugins. To include the samples I built https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/ but the poms there are versioned as 2.1-SNAPSHOT and are dependent upon the Geornimo 2.1-SNAPSHOT release.

Definitely something we need to do. Probably should have been something we did concurrently with a major release (e.g. 2.1).

I agree. I think this is something that we need to be doing concurrent with a release in the future. At the moment things are kinda broken from a user perspective. They can't install the 2.1-SNAPSHOT plugins on the 2.1 server. This looks especially bad since we include links in the welcome page ("/") to download and install the samples which currently fail. BTW, I tried to just change the dependent geronimo release in geronimo-plugins.xml for the samples but they still would not install because there are dependencies are missing (looks like there are references to non-existent org.apache.geronimo.configs car files).

Joe


So, I certainly think we should be tagging sample releases, they should be dependent upon G 2.1, and they need to be voted on.

--kevan



Reply via email to