Build System Meeting Agenda for Feb 15

[pgier]

Progress Since Previous Meeting

Created generic parent pom called jboss-parent. This name was chosen based on what other maven based projects are using.
Updated the jboss-common pom.xml files to use the new parent, and inherit from their project parent (build/pom.xml).
Updated jboss-microcontainer pom files to use the new inheritance structure.
Created pom.xml for jbossretro - checked in to cvs.
Created pom.xml for jboss-test - checked in to svn. Created pom.xml for javaassist - This was sent to chiba for review
Created a basic jbossretro maven plugin - still needs more testing.
Talked to IT about creating a snapshot repository - Eric said it will take some time before we can deploy to the snapshot repository via scp or sftp For now, we can check into svn similar to the way that we are doing now.
Researched maven antlib for using a shared repository - An easier option might be to add configuration to the maven build scripts that can deploy to both repositories.

Topics to discuss

Snapshot repository - Is the snapshot repository a good idea, and how should it be
implemented?
1. Use scp or sftp to transfer the files to snapshot repository
2. Copy the files to a local folder and commit via cvs/svn

Do we want nightly builds copied to a snapshot repository?
1. We could let developers create snapshots on an as needed basis.
2. Create nightly updates and allow as needed updates.

How do we make the switch to maven?
Set up nightly maven builds.
Deploy these builds to the maven and non-maven repo.
Find out if there are problems with other projects that are dependent on these projects.

Release process with Maven
The current jboss common wiki has a manual step of committing the tag.
The maven release plugin can be used to tag the release and update the pom.xml files.
Can we use the maven release plugin with jboss common?

To Do List By Next Meeting

Set up nightly cruise control builds for common, jboss-test, and micrcontainer.
Finish jboss retro maven plugin and create a profile for building retro jars
Create a roadmap for mavenization of jboss app server
Create a maven plugin to generate the non-maven repository distribution (component-info.xml, etc).

[ryan.campbell]

There are tests in JBossRetro that will validate the retroweaving. Are you running those?

[pgier]

There are tests in JBossRetro that will validate the retroweaving. Are you running those?

Do you mean retro-check? The plugin is not running those tests yet, but I will try to set it up.

[ryan.campbell]

The plugin needs to implement retrocheck as well, but I'm talking about the "test" target in the existing build.xml which is run using a 1.4 jvm to validate that the 1.5 features used in the src/tests are correctly/completely transformed.

Can the module be considered migrated unless the tests are executed under maven as well?

[pgier]

Ok, I will look into duplicating that functionality in maven.

No, the module shouldn't be considered fully migrated until all the steps are duplicated or replaced, and we actually remove the ant scripts.

[pgier]

Meeting Notes
----------------

We agree that having a separate snapshot repository is a good idea. Until we get this repository, we will set up a temporary server maybe using one of the QA servers.

For each project we should have the options of doing nightly snapshot builds and/or as needed developer builds.

For the next meeting I will create a demo/guide of using the maven release and assembly plugins.

[starksm64]

"pgier" wrote:

Researched maven antlib for using a shared repository - An easier option might be to add configuration to the maven build scripts that can deploy to both repositories.

Paul, what is the status of this feature? I would like to be doing the jboss and maven2 repo builds from the maven build for the mavenized projects like common, vfs, mc, ...

[pgier]

Paul, what is the status of this feature? I would like to be doing the jboss and maven2 repo builds from the maven build for the mavenized projects like common, vfs, mc, ...

I'm working on a plugin to do this. I will check it in later this week, maybe Thursday?

[pgier]

I created a new plugin called jboss-deploy-maven-plugin, and added the code here: https://svn.labs.jboss.org/labs/jbossbuild/trunk/projects/maven-plugins/jboss-deploy-maven-plugin

However I'm waiting for the helpdesk to update my ssh key so I can commit the plugin to the maven repository. Once the plugin is in the repository, then I can commit the updated poms for common that will use the plugin.

Should common always be built separately, or should it also be possible to build a single jar with all the classes for common?

[starksm64]

common-core, common-logging-spi, ..., jbossxb you mean? Certainly jbossxb will be released separately. I would expect common-logging-jdk and common-logging-log4j can be released separately.