RE : surefire-plugin and surefire-reports
Thank you very much, I've inserted the line always as suggested in the Bug Comments and the test results are shown in the right way. Regards, Carsten On 12 Jul 2006 at 12:03, Olivier Lamy wrote: > Look at http://jira.codehaus.org/browse/MSUREFIRE-114. > > -- > Olivier > > -Message d'origine- > De : Carsten Karkola [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 12 juillet 2006 10:50 > À : users@maven.apache.org > Objet : surefire-plugin and surefire-reports > > > We have different tests in the test/java dir and the > surefire-report-plugin is > specified in the pom.xml: > > > > > org.apache.maven.plugins > maven-surefire-report-plugin > > > > > If I execute mvn site, the test cases in the > target/surfire-reports/TEST*.xml > files are inserted multiple times: > > TEST-a.xml contains: > > > > > and TEST-b.xml contains again: > > > > and the new entry > > > We have more than 400 tests and the list gets longer and longer due to > the > repeated entries for every test case. Is there some misconfiguration or > is > this a bug? > > Regards, carsten > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
surefire-plugin and surefire-reports
We have different tests in the test/java dir and the surefire-report-plugin is specified in the pom.xml: org.apache.maven.plugins maven-surefire-report-plugin If I execute mvn site, the test cases in the target/surfire-reports/TEST*.xml files are inserted multiple times: TEST-a.xml contains: and TEST-b.xml contains again: and the new entry We have more than 400 tests and the list gets longer and longer due to the repeated entries for every test case. Is there some misconfiguration or is this a bug? Regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super POM
There was a Bug that is fixed in 2.0.5 (I'm waiting for the public release, to try it out :-) ): http://jira.codehaus.org/browse/MNG-2308 The super-Pom should also be found vi parent-entries if it is one dir up or the relativePath entry is specified. regards, carsten On 10 Jul 2006 at 15:11, Arnaud HERITIER wrote: > The parent POM must be deployed in your local repository to allow yours > subprojects to find it. > You just have to do : > mvn deploy > in the superPOM directory > > Arnaud > > On 7/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Hi All, > > > > I'm new to Maven and am struggling to create a super pom. I am involved > > in > > a project which has a number of sub projects and would like to have a > > super > > pom for the general configs, which are inherited by the sub projects. The > > problem is that I can create a super pom by hand, but when I reference it > > using the sub project goes of to the repo to download... I just > > wanted a super pom that I could use to set project wide configs. > > > > I tried various params with mvn archetype:create but no luck. > > > > Could someone please point me in the right direction. > > > > Many thanks in advance. > > -- > > Viz > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Change config of plugin outside of pom.xml
Hallo,
what is the best way to change a plugin config outside of the POM, so
developers can add some properties without the need to checkout/change
the pom of the project.
So I have a plugin with a config like
foo
myplugin
-Xms512m
and a developer likes to add an additional
-Xdebug
Under
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
I found this sentence, but I don't understand it:
The properties section allows you to specify free-form key-value pairs which
will be included in the interpolation process for the POM. This allows you to
specify a plugin configuration in the form of ${profile.provided.path}.
Does it mean I can add some property to my settings.xml like
-Xdebug ?!
Regards, carsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
M2: renaming tld dependencies
Hallo, we have some war subprojects with different tld dependencies. Is there some possibility to rename the tlds during packaging. I'd like to strip of the version numbers to avoid modifications in the web.xml files. regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rar Plugin and dependencies - (MVN 2.0.4)
On 31 May 2006 at 17:38, Tim Kettler wrote: The difference between bundling an ejb jar (dependency handling is done automatically by maven) and a rar (I have to do some more work in the poms, as suggested by you and Roland) in an ear lead to some obscurities on my side. >> Wouldn't it be nice to have some option? Or wouldn't it be enough to say if >> I specify manifest classpath entries, I can leave out the dependencies from >> the rar archive? > > Can you elaborate on this a bit more? This isn't entirely clear to me. > >> Therefore I thought about some option: a) maven-rar-plugin false or some implicit check b) if I add a classpath configuration like true APP-INF/lib then there is no need to bundle the dependend jars, because they will be bundled later in the ear. a) is clearer But it's only an idea. regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rar Plugin and dependencies - (MVN 2.0.4)
So I have to specify the dependencies twice? First time in the parent/pom.xml and second time in rar/pom.xml (there using provided? I have to play with this, because some of the dependencies are internal jars from other subprojects. As far as I can see, a workaround is to specifiy all dependencies for the rar- modules with provided and add them a second time to the ear pom. Wouldn't it be nice to have some option? Or wouldn't it be enough to say if I specify manifest classpath entries, I can leave out the dependencies from the rar archive? Modules: I use bundelFileName there. On 31 May 2006 at 12:05, Tim Kettler wrote: > Can't you do it like this: > > project > |--pom.xml > | > `--parent > | |--pom.xml > | > `--rar > | |--pom.xml > | > `--ear > | |--pom.xml > > parent/pom.xml: > --- > > 4.0.0 > > test > test-parent > 1.0-SNAPSHOT > > pom > > Parent > > > > >axis >axis >1.1 > > > > > > --- > > ear/pom.xml: > --- > > >4.0.0 > > > test > test-parent > 1.0-SNAPSHOT > ../parent > > >de.foo >bar-ear >1.0 >Foo::Bar EAR >ear > > > > maven-ear-plugin > >APP-INF/lib > > > > > > > >de.foo >bar-connector >1.0 >rar > > >axis >axis > > > > --- > > rar/pom.xml: > --- > >4.0.0 > > > test > test-parent > 1.0-SNAPSHOT > ../parent > > >de.foo >bar-connector >1.0 > >Foo::Bar Rar >rar > > > > > >axis >axis >provided > > > > --- > > Of course you don't need a distinct parent and aggregation pom > (project/pom.xml). You can > just merge the two and use the project level pom as the parent. > > BTW, you don't need to specify this: > > > > test > test-ejb > > > > This section is used only if you need to configure the way the module is > handled by the > plugin like specifying the bundleFileName. > > -Tim > > Carsten Karkola schrieb: > > No, I need the jar in the ear, my example - just to make clear what I try > > to > > describe :-): > > > > $>mkdir -p rar/src/main/rar/META-INF > > $>touch rar/src/main/rar/META-INF/ra.xml > > $>touch rar/pom.xml > > $>mkdir -p ear > > $>touch ear/pom.xml > > > > ear/pom.xml: > > > > > xmlns="http://maven.apache.org/POM/4.0.0"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > > http://maven.apache.org/maven-v4_0_0.xsd";> > > > > 4.0.0 > > de.foo > > bar-ear > > 1.0 > > Foo::Bar EAR > > ear > > > > > > > > maven-ear-plugin > > > > APP-INF/lib > > > > > > de.foo > > bar-connector > > > > > > > > > > > > > > > > > > de.foo > > bar-connector > > 1.0 > > rar > > > > > > > > > > rar/pom.xml: > > > > > xmlns="http://maven.apache.org/POM/4.0.0"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > > http://maven.apache.org/maven-v4_0_0.xsd";> > > > > 4.0.0 > > de.foo > > bar-connector > > 1.0 > > Foo::Bar Rar > > rar > > > > > > > > > > axis > > axis > > 1.1 > > provided > > > > > > > > > > At least the build: > > $>cd rar > > $>mvn clean install > > $>cd ../ear > > $>mvn package > > > > The problem: > > If I have provided, axis is missing
Re: Rar Plugin and dependencies - (MVN 2.0.4)
No, I need the jar in the ear, my example - just to make clear what I try to describe :-): $>mkdir -p rar/src/main/rar/META-INF $>touch rar/src/main/rar/META-INF/ra.xml $>touch rar/pom.xml $>mkdir -p ear $>touch ear/pom.xml ear/pom.xml: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 de.foo bar-ear 1.0 Foo::Bar EAR ear maven-ear-plugin APP-INF/lib de.foo bar-connector de.foo bar-connector 1.0 rar rar/pom.xml: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 de.foo bar-connector 1.0 Foo::Bar Rar rar axis axis 1.1 provided At least the build: $>cd rar $>mvn clean install $>cd ../ear $>mvn package The problem: If I have provided, axis is missing in the rar and in the ear. If I remove this line, Im ending up with axis in APP-INF/lib and inside the rar. How can I avoid this; I'd like to exclude the axis.jar only from the rar not from the ear, background: I have a lot of rars with some more dependencies, that are shared in all the rars, I'd like to deploy these dependencies only once in APP-INF/lib not in every rar and in APP-INF/lib. regards, carsten On 30 May 2006 at 18:19, Roland Asmann wrote: > Set the scope to provided ONLY on the rar-projects, NOT on the EAR. > > > > On Tuesday 30 May 2006 18:02, Carsten Karkola wrote: > > If I use "provided" the dependencies will never be included, my problem is > > 1. projects: > > rar1: dependency to my-jar > > rar2: dependency to my-jar > > ejb1: dependency to my-jar > > ear: dependency to rar1, rar2 > > 2. inside the ear: > > ejb1.jar > > rar1.rar > > rar2.rar > > lib/my-jar.jar > > 3. This works fine for packaging=ejb - the my-jar.jar gets copied to the > > lib dir during build of the ear. But the same jar gets also packaged in the > > rar1 and in the rar2 archive. So I have it three times instead only having > > the entries in MANFIFEST.MF/Class-Path and the jar only once in the lib > > subdir. > > The Manifest entries are not the problem, to get the jar not packaged in > > the rars is my problem. > > > > regards, carsten > > > > On 30 May 2006 at 10:24, Wayne Fay wrote: > > > I can't tell if you're running M2 or M1... > > > > > > But in M2, to exclude a dependency from being included in a package, > > > we use the provided tag to override the default > > > "compile" scope. Provided tells the packager that this > > > dependency/artifact/library will be provided by the app server etc, > > > and so it does not need to be included in the archive/package. > > > > > > Wayne > > > > > > On 5/30/06, Carsten Karkola <[EMAIL PROTECTED]> wrote: > > > > Hallo, > > > > > > > > I have some subprojects with rar specified. > > > > There are some dependencies specified, that need to be included in the > > > > ear. I'd like to include these dependencies (like axis) only once in > > > > the ear and not in every rar archive. > > > > This way works fine with ejb archives. But with rar archives I get > > > > these depend jars always included in the rar itself. > > > > false doesn't help. > > > > > > > > regards, carsten > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Rar Plugin and dependencies - (MVN 2.0.4)
If I use "provided" the dependencies will never be included, my problem is 1. projects: rar1: dependency to my-jar rar2: dependency to my-jar ejb1: dependency to my-jar ear: dependency to rar1, rar2 2. inside the ear: ejb1.jar rar1.rar rar2.rar lib/my-jar.jar 3. This works fine for packaging=ejb - the my-jar.jar gets copied to the lib dir during build of the ear. But the same jar gets also packaged in the rar1 and in the rar2 archive. So I have it three times instead only having the entries in MANFIFEST.MF/Class-Path and the jar only once in the lib subdir. The Manifest entries are not the problem, to get the jar not packaged in the rars is my problem. regards, carsten On 30 May 2006 at 10:24, Wayne Fay wrote: > I can't tell if you're running M2 or M1... > > But in M2, to exclude a dependency from being included in a package, > we use the provided tag to override the default > "compile" scope. Provided tells the packager that this > dependency/artifact/library will be provided by the app server etc, > and so it does not need to be included in the archive/package. > > Wayne > > On 5/30/06, Carsten Karkola <[EMAIL PROTECTED]> wrote: > > Hallo, > > > > I have some subprojects with rar specified. There > > are some dependencies specified, that need to be included in the ear. I'd > > like to include these dependencies (like axis) only once in the ear and not > > in > > every rar archive. > > This way works fine with ejb archives. But with rar archives I get these > > depend jars always included in the rar itself. > > false > > doesn't help. > > > > regards, carsten > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rar Plugin and dependencies
Hallo, I have some subprojects with rar specified. There are some dependencies specified, that need to be included in the ear. I'd like to include these dependencies (like axis) only once in the ear and not in every rar archive. This way works fine with ejb archives. But with rar archives I get these depend jars always included in the rar itself. false doesn't help. regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
checkstyle plugin and propertyExpansion
We have our own checkstyle config with some file referenzens. I tried
to use them with
org.apache.maven.plugins
maven-checkstyle-plugin
${basedir}/../../checks.xml
header.regexp.file=${basedir}/../../header_regexp.txt
this part of the pom is located in a supproject. Without the ${basedir} Maven
didn't find the
file header_regexp.txt if I call mvn site from the parent project. The
${basedir}-solution works
fine on Unix (AIX) but fails on windows, where the directory separator is
missed:
Embedded error: Error rendering Maven report: Failed during checkstyle
configuration
d:ckkckk_nextTCdevcommonaxis\..\..\header_regexp.txt
regards, carsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.4 - Mutlipe parents and POMs
Hy Markus, thank you for your quick answer. On 15 May 2006 at 16:17, Markus Reinhardt wrote: > > ../pom.xml > > You may try putting relativePath in here. This prevents maven from looking > for the POM in any > repository. Even the relativePath element doesn't work in the b subdirectory. > > Another thing that worked for me ist to run 'mvn install' on all projects > with > pom. This puts the POM in your local repo, where it is > found by maven > during the build of the submodules. > I have some profiles in the top level pom. In the profiles I have version numbers for different releases of the subprojects (b.a, b.b, ...). There I use the version numbers as pom.versionId or dependency versions. And maven doesn't replace these values (provided in a/pom.xml) in the subproject b.a. and so b.a/pom.xml fails to find the right poms from the repo. But if I cd to a/b/b.a all values get resolved ... So it seems to be a bug in maven?! regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0.4 - Mutlipe parents and POMs
Hy, I've created the following directory layout /a - pom.xml /b - pom.xml - /b.a -pom.xml My executions: $> cd ~/a $> mvn compile [INFO] BUILD SUCCESSFUL $> cd ~/a/b/b.a $> mvn compile [INFO] BUILD SUCCESSFUL $> cd ~/a/b $> mvn compile [INFO] Scanning for projects... Downloading: http://.../repository/com/foo/a/I/a-I.pom [WARNING] Unable to get resource from repository central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: com.foo ArtifactId: a Version: I I've looked at the effective poms with mvn help:effective-pom, the poms in directory a and in directory b.a are ok., the creation of the pom in b fails. It seems that there is a problem with more than one parent with packaging=pom. regards, carsten The poms - a/pom.xml: --- http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven- v4_0_0.xsd"> 4.0.0 com.foo a I Module A pom b The poms - a/b/pom.xml: --- http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven- v4_0_0.xsd"> com.foo a I 4.0.0 com.foo b I Module B pom b.a The poms - a/b/b.a/pom.xml: --- http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven- v4_0_0.xsd"> com.foo b I 4.0.0 com.foo b.a I Module B.A jar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
