Simple portal & samples packaging

[julien1]

I moved the simple portal and the samples out of the test package.

The simple portal is created by the assembly plugin that packages it, for now only for JBoss AS 4.2. I need to do it for tomcat.

The samples are not built anymore, I need to fix that too.

[julien1]

I worked on it and now it is back to normal.

Now the portal is its own "portal" module

Samples have been also moved to the "samples" module, I think we can now migrate the existing 2.6 samples which are not using the JBoss Portal api to that module. This module only consumes the portlet API.

The test module is still the same (except it does not contain anymore the simple portal and the samples. I plan here to bundle the testsuite and the tck in the same war file in order to avoid duplication of the same files.

I think also I am going to introduce profiles that should also provide subset of what someone needs when he uses the build, i.e one profile for the simple portal building and one profile for the testsuite&tck building. By default it will build everything.

[julien1]

I have used a new directory called "artifacts" that contains the various pseudo artifact we have like foo-bar-war, instead of using the resources directory.

The resources directory in maven seems to be used for the jar resources, i.e the whole content is also present in the jar.

I did that for the new 'samples' directory but I did not apply it everywhere.

If you want to suggest a better name than "artifacts", feel free to propose.

[prabhat.jha]

How about changing the name to test-artifact instead of artifact?

[julien1]

How about changing the name to test-artifact instead of artifact?

actually there can be artifacts for non test and for tests that would give:

src/main/artifacts or src/test/artifacts

among

src/main/java
src/test/java
src/main/resources
src/test/resources

[julien1]

so I have added the following profiles:

test : only test
simple-portal : the simple portal
docs : only the doc
release : for doing a release

it can be activated by using the -P switch, for instance :

mvn -Ptest install -Dtests=tomcat

[julien1]

I updated a few things in the packaging:

- distribution:
1/ need to use the "release" profile with maven to build project
2/ then use distrib.xml file to build the releases

mvn -Prelease install
cd build/distrib
ant -f distrib.xml

- use tomcat and jboss archives in order to ensure that we get clean bundles (we should do that too in core portal), also it seems to speed up the build a bit.

export JBOSS_4_2_PATH=..../jboss-4.2.2.GA.zip
export TOMCAT_6_0_PATH=..../apache-tomcat-6.0.16.zip

[julien1]

one remaining issue is logging configuration in tomcat, for now it displays everything single line of jboss aop trace :-(

[dgashby]

one remaining issue is logging configuration in tomcat, for now it displays everything single line of jboss aop trace :-(

Hi Julien,

Is there an easy fix for this? I'm new to AOP based logging and after having a look around couldn't find any docs or obvious configuration files that might control this. I would greatly appreciate being able to turn the trace and debug output off.

Cheers,

Dean

[julien1]

I need to do that because it sucks badly.

I plan to do a CR2 release this week or next week (with the new event debugger :-) ), I'll try to get it fixed.

"dgashby" wrote:

one remaining issue is logging configuration in tomcat, for now it displays everything single line of jboss aop trace :-(

Hi Julien,

Is there an easy fix for this? I'm new to AOP based logging and after having a look around couldn't find any docs or obvious configuration files that might control this. I would greatly appreciate being able to turn the trace and debug output off.

Cheers,

Dean