Create test environment that includes log4j and associated configuration

(In [518]) re #122 Test environment that includes log4j - maven2-cargo-plugin patch

The patch(es) here fix a number of problems with the maven2-cargo-plugin. However, there is a problem with regard to how this actually gets deployed and then used. It depends on a number of cargo (and non-cargo) snapshots from codehaus' snapshot repository:

http://snapshots.repository.codehaus.org/

Also, cargo seems quite a bit in flux (in subversion) and the snapshots at codehaus lag behind subversion. However, when they do get updated, it may be necessary to rebuild (and repatch) our modifications here. (Until our patch is accepted and applied in the snapshot directly.)

I've changed the groupId of the plugin to ensure that maven does not get confused and accidentally pick up the wrong version of the plugin from the wrong repository.

How to do a build:

cd vendor/cargo cat *.patch | patch -p1 -d maven2 cd maven2; mvn -s ../settings.xml install

How to install:

Copy result from ~/.m2/repository/org/topazproject/patch/cargo/cargo-maven2-plugin to gandalf's /home/maven2/repository/org/topazproject/patch/cargo

How to use:

Place log.properties in ~/.m2/topaz/container-classes Build with the it-helper profile

Technically it would be possible to deploy this thing properly to gandalf. However, cargo's trunk/pom.xml would have to have its <distributionManagement> entries modified. Then the build would have to be run from that directory. Checksums would match then and the world would be well. However, it would also mean we'd have to build from trunk/pom.xml and then gandalf would essentially hold a copy of the snapshot. But not the other things cargo needs from the codehaus' snapshot repository, so that repository would still be needed in anything using the maven2-cargo-plugin. There is then a real problem with conflicts that is not worth dealing with. Thus, it is best to manually shove the result of this build to gandalf without relevant checksums (until a way can be figured out to generate those.)

Still todo:

• Update it-helper profile
• Since groupId changed, all projects using it-helper will need one of the groupIds in their pom.xmls to be changed.

(In [520]) fixes #122 Test environment that includes log4j configuration capability

See [518] for instructions.

I built and manually deployed http://gandalf/maven2/org/topazproject/patch from source:vendor/cargo based on instructions in [518].

There are a few more issues that should be chased down at some point that have been put in a new ticket (#138):

• log4j configuration defaults vague (and suck)
• log4j configurations for container, webapp and it-tests can conflict
• Create a ${topaz.home}

(In [541]) re #122 Test environment for log4j - patch a release, not SNAPSHOT

This eliminates dependency on codehaus snapshot repository and means that we are not subject to changes or build problems introduced to the current snapshot. We are fixed at maven2-cargo-plugin 0.2 / cargo 0.8.

I built our 0.2 patch and deployed it to gandalf. Will checkin necessary stuff for that later. Basically I just grabbed tags/0.2-maven2, applied the same patch as for 0.3-SNAPSHOT, but deleted the unit tests since they will fail due to subtle API changes in the SNAPSHOT.

Milestone august25 deleted