JBossMC-2.0.0.Beta10

[starksm64]

We need a JBossMC-2.0.0.Beta10 release for jbossas beta4 issues. I have created this with a scheduled release of next Monday, the 21. Is that doable? The 25th would be the latest.

[starksm64]

I added http://jira.jboss.com/jira/browse/JBMICROCONT-226, to remove the dependency on the osgi version class from the default class loader version.

[pgier]

Scott, can I do this release? I'd like to make sure everything is working with the maven release process for microcontainer. Then I'll write up some notes on the wiki for whoever does the release next time.

[starksm64]

Sure.

[alesj]

I released VFS beta7.
It should be in the maven2 repo, as well as in the old CVS.

Can someone verify that?
Doing release at the airport isn't the most reliable thing. :-)

[alesj]

"alesj" wrote:

It should be in the maven2 repo, as well as in the old CVS.

It's in the CVS. :-)
But I also added it where it's supposed to be, in SVN. :-)

I commited my MC changes related to this VFS change.

[starksm64]

Yes, its in the maven2 and jboss repositories.

[starksm64]

Everything is done for this. Can you start the release Paul?

[pgier]

Sorry, I didn't see this post yesterday. I'll do the release today.

[pgier]

The release has been tagged and uploaded to the maven repository.

I'm working on putting stuff in the jboss repository now. Scott, was this a manual process for the last couple releases? (Copying jars to the lib directory and updating component-info.xml. Or am I just missing an easier way to do this?

Also there is some stuff that was not in Beta9: osgi, reliance, spring-int. Should these be included in this release in the build magic repository?

[starksm64]

Its manual as just a subset of the artifacts go into the jboss repo. Here is a sh script I have used to copy the artifacts from the maven repo into the jboss repo microcontainer/lib directory for a release.

[starksm@succubus jbossmc]$ cat ../install.sh
#!/bin/sh

VER=2.0.0.Beta10
M2=/home/svn/repository.jboss.com/maven2/org/jboss/microcontainer
JBOSS=/home/svn/repository.jboss.com/jboss/microcontainer
JARS="jboss-aop-mc-int jboss-classloader jboss-container jboss-container-metadata jboss-container-metadata-spi jboss-dependency jboss-deployers-client jboss-deployers-client-spi jboss-deployers-core jboss-deployers-core-spi jboss-deployers-impl jboss-deployers-spi jboss-deployers-structure-spi jboss-deployers-vfs jboss-deployers-vfs-spi jboss-kernel jboss-managed jboss-metatype"

mkdir $JBOSS/$VER
mkdir $JBOSS/$VER/lib
for j in $JARS
do
 jar=`find $M2 -name $j-${VER}.jar`
 if [ -n $jar ]
 then
 cp $jar $JBOSS/$VER/lib/$j.jar
 fi
 sjar=`find $M2 -name $j-${VER}-sources.jar`
 if [ -n $sjar ]
 then
 cp $sjar $JBOSS/$VER/lib/${j}-sources.jar
 fi
done

[pgier]

I created this wiki entry with some notes from the release.
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess_Microcontainer

The process had a couple bumps, but it should be fine for the next release. The things left to work on is fixing the pom in the docs directory (I will do that today), and automating the process for putting together the jars for the buildmagic repo.

For the buildmagic artifact, would it make sense to have a single large combined jar like we have for javaee? That way component-info.xml is small and simple, and I can set it up to be automated pretty easily.

[starksm64]

No because the jars are loaded at different levels during the server bootstrap process. Classes would be unnecessarily pushed to a parent class loader if only one jar existed.

[pgier]

Ok, makes sense. I'll see if I can get maven to automate generating this layout for next time, so the shell script isn't needed.