Re: Wrong number of tests run when running JUnit tests in parallel: any help?
Please note that the parallel provider actually requires correctly defined junit4/junit3 tests to run, annotate your methods with @Test. The classic Junit 4 provider would run a large number of tests that were incorrectly defined according to junit specifications. The concurrent provider uses the same selection mechanism as the junit 4 provider, but junit itself adds an additional compliance check before running the test. I also recommend you use the latest release of Junit; 4.8.2, or 4.8.1 if 4.8.2 hasn't reached the repos yet. Kristian Den 11.04.2010 23:58, skrev Paolo Castagna: Hi, I am trying to see if running JUnit tests in parallel makes any difference and/or significant speed-up. I have this in my pom.xml: dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.7/version scopetest/scope /dependency [...] plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.5/version configuration includes include[...]/include /includes parallelmethods/parallel threadCount4/threadCount /configuration /plugin When I run the tests without parallel and threadCount I see: Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: ... While when I run the tests with parallel and threadCount as showed above: Tests run: 40, Failures: 0, Errors: 0, Skipped: 0 Is this a bug? Am I doing something wrong here? Thanks, Paolo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Custom Ant Task in Maven
I solved it !! jw_amp wrote: Hi All, I am using an custom Ant Task in Maven POM, but I am not managed to fix it. The Custom Ant Task is provided by RedLine Library (http://www.introspectrum.com/oss/redline/usage.html): project name='test' default='rpm' xmlns:redline='antlib:org.freecompany.redline.ant' target name='rpm' mkdir dir='rpms'/ redline:rpm group='Java Development' name='test' version='1.2.3' destination='rpms' zipfileset prefix='/usr/share/java' file='test-1.2.3.jar'/ link path='/usr/share/java/test.jar' target='/usr/share/java/test-1.2.3.jar'/ depends name='test-lib' version='1.2.3'/ /redline:rpm /target /project I went to maven-antrun-plugin docs and tried this with provided example there, but still not succeeded. Can anyone help me that how to use this. - thanks, -- View this message in context: http://old.nabble.com/Custom-Ant-Task-in-Maven-tp28210289p28214878.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Dependencies and Aggregation
Hi,
i'm trying to understand the handling of dependencies/aggregation in
Maven...
So i've setup the following structure:
+--- root (root pom)
+--- m1
+--- m1.1
+--- m1.2
+--- m1.3
+--- m1.4
+--- m1.5
+--- m2
+--- m2.1
+--- m2.2
+--- m2.3
+--- m2.4
+--- m2.5
+--- m3
+--- m3.1
+--- m3.2
+--- m3.3
+--- m3.4
+--- m3.5
+--- m4
+--- m4.1
+--- m4.2
+--- m4.3
+--- m4.4
+--- m4.5
The root-pom has only modules listed (m1, m2, m3, m4)...
The m1 (m2, m3, m4) has a list of modules as well ( m1.1, m1.2 ...
m1.5)...m1 has defined the parent (root-pom)...and the modules m1.1 till
m1.5 has the parent m1 whereas the m2.1 till m2.5 has the parent m2...and so
on...
The modules m1.1 till m4.5 are simple packages which have default packaging
type (jar)...and contain a simple class and of course a test case for test
purposes.
So if i call mvn install on the root pom everything works as expected
So my next step was to define a dependency of one module to an
other...(m3.2)...so in m3.2 pom i used the following:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
/dependencies
Ok...just tried to build...mvn install as expected the reactor order
changed
But now i tried something different. I defined the dependency in m3.2's pom
to use m4 as dependency:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
dependency
groupId${project.groupId}/groupId
artifactIdm4/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
Ok..tried to build mvn install and was a little bit confused...
The order in the reactor has changed, but only the module m4 itself has been
built before m2 instead of all sub-modules of m4...what i got was the
following:
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ModuleTest :: Parent .. SUCCESS
[3.323s]
[INFO] ModuleTest :: M1 .. SUCCESS
[0.031s]
[INFO] ModuleTest :: M1 :: M1.1 .. SUCCESS
[2.941s]
[INFO] ModuleTest :: M1 :: M1.2 .. SUCCESS
[1.216s]
[INFO] ModuleTest :: M1 :: M1.3 .. SUCCESS
[0.867s]
[INFO] ModuleTest :: M1 :: M1.4 .. SUCCESS
[0.963s]
[INFO] ModuleTest :: M1 :: M1.5 .. SUCCESS
[0.672s]
[INFO] ModuleTest :: M2 .. SUCCESS
[0.034s]
[INFO] ModuleTest :: M2 :: M2.1 .. SUCCESS
[0.932s]
[INFO] ModuleTest :: M2 :: M2.2 .. SUCCESS
[0.703s]
[INFO] ModuleTest :: M2 :: M2.3 .. SUCCESS
[0.777s]
[INFO] ModuleTest :: M2 :: M2.4 .. SUCCESS
[0.740s]
[INFO] ModuleTest :: M2 :: M2.5 .. SUCCESS
[0.745s]
[INFO] ModuleTest :: M3 .. SUCCESS
[0.035s]
[INFO] ModuleTest :: M3 :: M3.1 .. SUCCESS
[0.748s]
[INFO] ModuleTest :: M4 .. SUCCESS
[0.035s]
[INFO] ModuleTest :: M3 :: M3.2 .. SUCCESS
[1.023s]
[INFO] ModuleTest :: M3 :: M3.3 .. SUCCESS
[0.763s]
[INFO] ModuleTest :: M3 :: M3.4 .. SUCCESS
[0.668s]
[INFO] ModuleTest :: M3 :: M3.5 .. SUCCESS
[0.694s]
[INFO] ModuleTest :: M4 :: M4.1 .. SUCCESS
[0.724s]
[INFO] ModuleTest :: M4 :: M4.2 .. SUCCESS
[0.748s]
[INFO] ModuleTest :: M4 :: M4.3 .. SUCCESS
[0.679s]
[INFO] ModuleTest :: M4 :: M4.4 .. SUCCESS
[0.876s]
[INFO] ModuleTest :: M4 :: M4.5 .. SUCCESS
[0.660s]
[INFO]
Maybe i misunderstand the usage of a module ...or do i have to give simply
the modules m4.1...m4.5 as dependency instead of using m4?
The m4 module is a aggregation of multiple modules (m4.1...m4.5) which are
needed as dependency so it would be nice just to give m4 as dependency
Or does exist an other solution to handle such a problem?
Kind
Re: Custom Ant Task in Maven
Hi, it would be great if you post your solution... Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/Custom-Ant-Task-in-Maven-tp28210289p28214943.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependencies and Aggregation
Hi Karl,
m4 does not have any dependencies to its submodules (it just aggregates
them). so in order to build 3.2, it is sufficient that m4 is built first
(e.g. maven includes modules and dependencies defined in m4).
Does it built correctly if you delete your repository (at least the m*
entries? If it does, i don't see a problem, as it is still working that way.
)
with best regards, Harald
2010/4/12 Karl Heinz Marbaise k...@soebes.de
Hi,
i'm trying to understand the handling of dependencies/aggregation in
Maven...
So i've setup the following structure:
+--- root (root pom)
+--- m1
+--- m1.1
+--- m1.2
+--- m1.3
+--- m1.4
+--- m1.5
+--- m2
+--- m2.1
+--- m2.2
+--- m2.3
+--- m2.4
+--- m2.5
+--- m3
+--- m3.1
+--- m3.2
+--- m3.3
+--- m3.4
+--- m3.5
+--- m4
+--- m4.1
+--- m4.2
+--- m4.3
+--- m4.4
+--- m4.5
The root-pom has only modules listed (m1, m2, m3, m4)...
The m1 (m2, m3, m4) has a list of modules as well ( m1.1, m1.2 ...
m1.5)...m1 has defined the parent (root-pom)...and the modules m1.1 till
m1.5 has the parent m1 whereas the m2.1 till m2.5 has the parent m2...and
so
on...
The modules m1.1 till m4.5 are simple packages which have default packaging
type (jar)...and contain a simple class and of course a test case for test
purposes.
So if i call mvn install on the root pom everything works as expected
So my next step was to define a dependency of one module to an
other...(m3.2)...so in m3.2 pom i used the following:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
/dependencies
Ok...just tried to build...mvn install as expected the reactor order
changed
But now i tried something different. I defined the dependency in m3.2's pom
to use m4 as dependency:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
dependency
groupId${project.groupId}/groupId
artifactIdm4/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
Ok..tried to build mvn install and was a little bit confused...
The order in the reactor has changed, but only the module m4 itself has
been
built before m2 instead of all sub-modules of m4...what i got was the
following:
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ModuleTest :: Parent .. SUCCESS
[3.323s]
[INFO] ModuleTest :: M1 .. SUCCESS
[0.031s]
[INFO] ModuleTest :: M1 :: M1.1 .. SUCCESS
[2.941s]
[INFO] ModuleTest :: M1 :: M1.2 .. SUCCESS
[1.216s]
[INFO] ModuleTest :: M1 :: M1.3 .. SUCCESS
[0.867s]
[INFO] ModuleTest :: M1 :: M1.4 .. SUCCESS
[0.963s]
[INFO] ModuleTest :: M1 :: M1.5 .. SUCCESS
[0.672s]
[INFO] ModuleTest :: M2 .. SUCCESS
[0.034s]
[INFO] ModuleTest :: M2 :: M2.1 .. SUCCESS
[0.932s]
[INFO] ModuleTest :: M2 :: M2.2 .. SUCCESS
[0.703s]
[INFO] ModuleTest :: M2 :: M2.3 .. SUCCESS
[0.777s]
[INFO] ModuleTest :: M2 :: M2.4 .. SUCCESS
[0.740s]
[INFO] ModuleTest :: M2 :: M2.5 .. SUCCESS
[0.745s]
[INFO] ModuleTest :: M3 .. SUCCESS
[0.035s]
[INFO] ModuleTest :: M3 :: M3.1 .. SUCCESS
[0.748s]
[INFO] ModuleTest :: M4 .. SUCCESS
[0.035s]
[INFO] ModuleTest :: M3 :: M3.2 .. SUCCESS
[1.023s]
[INFO] ModuleTest :: M3 :: M3.3 .. SUCCESS
[0.763s]
[INFO] ModuleTest :: M3 :: M3.4 .. SUCCESS
[0.668s]
[INFO] ModuleTest :: M3 :: M3.5 .. SUCCESS
[0.694s]
[INFO] ModuleTest :: M4 :: M4.1 .. SUCCESS
[0.724s]
[INFO] ModuleTest :: M4 :: M4.2 .. SUCCESS
[0.748s]
[INFO] ModuleTest :: M4 :: M4.3 .. SUCCESS
[0.679s]
[INFO] ModuleTest :: M4 :: M4.4 .. SUCCESS
Re: Dependencies and Aggregation
Hi Harald,
first of all thanks for your help...
Harald Entner-3 wrote:
m4 does not have any dependencies to its submodules (it just aggregates
them).
That seemed to be not the full truth...if i try to supplemental define a
dependency in my m4 module to make the dependency to m4.1 explicit...
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm4.1/artifactId
version${project.version}/version
/dependency
dependency
I will get the following message:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='com.xyz.test.build:m4.1'}' and
'Vertex{label='com.xyz.test.build:m4.1'}' introduces to cycle in the graph
com.xyz.test.build:m4.1 -- com.xyz.test.build:m4.1
That's indicating that the dependency has been inserted already...
Harald Entner-3 wrote:
so in order to build 3.2, it is sufficient that m4 is built first
(e.g. maven includes modules and dependencies defined in m4).
In my opinion the dependencies of m4 should be built
first...(m4.1...m4.5)...
Harald Entner-3 wrote:
Does it built correctly if you delete your repository (at least the m*
entries? If it does, i don't see a problem, as it is still working that
way.
Doesn't change anything in the order of the build
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Dependencies-and-Aggregation-tp28214892p28215393.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Custom Ant Task in Maven
Sure ... I used maven-antrun-plugin and I wrote the following in to the configuration section of this plug-in: tasks ant antfile=D:\my_maven_project\build.xml target name=rpm/ /ant /tasks In the build.xml, you just copy all the contents of redline (posted earlier) into this file. In my my_maven_project, I have both pom.xml,build.xml. Also, you have to specify the redline dependency into POM. Then, mvn install ... you will have your source package into RPM package. I used in this way succeeded. -- Karl Heinz Marbaise wrote: Hi, it would be great if you post your solution... Kind regards Karl Heinz Marbaise - thanks, -- View this message in context: http://old.nabble.com/Custom-Ant-Task-in-Maven-tp28210289p28215611.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Dependencies and Aggregation
hmm, i would rather say that m4.1 has already a dependency to m4 (via parent
definition, if there is a parent definition, i could be wrong though).
E.g. in order to build m4.1 m4 needs to be built first. So if you define a
dependency to m4.1 in m4 that build cannot work (due to the cycle).
-Ursprüngliche Nachricht-
Von: Karl Heinz Marbaise [mailto:k...@soebes.de]
Gesendet: Montag, 12. April 2010 11:09
An: users@maven.apache.org
Betreff: Re: Dependencies and Aggregation
Hi Harald,
first of all thanks for your help...
Harald Entner-3 wrote:
m4 does not have any dependencies to its submodules (it just aggregates
them).
That seemed to be not the full truth...if i try to supplemental define a
dependency in my m4 module to make the dependency to m4.1 explicit...
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm4.1/artifactId
version${project.version}/version
/dependency
dependency
I will get the following message:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='com.xyz.test.build:m4.1'}' and
'Vertex{label='com.xyz.test.build:m4.1'}' introduces to cycle in the graph
com.xyz.test.build:m4.1 -- com.xyz.test.build:m4.1
That's indicating that the dependency has been inserted already...
Harald Entner-3 wrote:
so in order to build 3.2, it is sufficient that m4 is built first
(e.g. maven includes modules and dependencies defined in m4).
In my opinion the dependencies of m4 should be built
first...(m4.1...m4.5)...
Harald Entner-3 wrote:
Does it built correctly if you delete your repository (at least the m*
entries? If it does, i don't see a problem, as it is still working that
way.
Doesn't change anything in the order of the build
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Dependencies-and-Aggregation-tp28214892p28215393.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
Hi All,
Basically what I am trying to achieve is to break the default build
lifecycle into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The packaging for this project did not assign a file to the build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it successfully
deploys my project's jar file.
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Dependencies and Aggregation
btw: two commands that could be useful for you:
mvn dependency:tree (to see the dependencies explicitly)
and
mvn help:effective-pom (to see the effective pom)
with best regards, harald
-Ursprüngliche Nachricht-
Von: Entner Harald [mailto:entner.har...@afb.de]
Gesendet: Montag, 12. April 2010 11:47
An: Maven Users List
Betreff: AW: Dependencies and Aggregation
hmm, i would rather say that m4.1 has already a dependency to m4 (via parent
definition, if there is a parent definition, i could be wrong though).
E.g. in order to build m4.1 m4 needs to be built first. So if you define a
dependency to m4.1 in m4 that build cannot work (due to the cycle).
-Ursprüngliche Nachricht-
Von: Karl Heinz Marbaise [mailto:k...@soebes.de]
Gesendet: Montag, 12. April 2010 11:09
An: users@maven.apache.org
Betreff: Re: Dependencies and Aggregation
Hi Harald,
first of all thanks for your help...
Harald Entner-3 wrote:
m4 does not have any dependencies to its submodules (it just aggregates
them).
That seemed to be not the full truth...if i try to supplemental define a
dependency in my m4 module to make the dependency to m4.1 explicit...
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm4.1/artifactId
version${project.version}/version
/dependency
dependency
I will get the following message:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='com.xyz.test.build:m4.1'}' and
'Vertex{label='com.xyz.test.build:m4.1'}' introduces to cycle in the graph
com.xyz.test.build:m4.1 -- com.xyz.test.build:m4.1
That's indicating that the dependency has been inserted already...
Harald Entner-3 wrote:
so in order to build 3.2, it is sufficient that m4 is built first
(e.g. maven includes modules and dependencies defined in m4).
In my opinion the dependencies of m4 should be built
first...(m4.1...m4.5)...
Harald Entner-3 wrote:
Does it built correctly if you delete your repository (at least the m*
entries? If it does, i don't see a problem, as it is still working that
way.
Doesn't change anything in the order of the build
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Dependencies-and-Aggregation-tp28214892p28215393.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
Use nexus and staged deployment then you can do it in one go.
The artifacts produced in one maven execution are no longer in the reactor
when you run a second time.
Staged deployment is what you want, then you just do mvn deploy... run your
tests of the artifacts and either drop the staged deployment or promote
it...
If you cannot get the purchase of pro-Nexus, then you can do poor man's
staging with wagon-maven-plugin... or you can wait until staging is required
by me and I scratch my own itch and write an OSS plugin to provide staging
in Nexus Open Source ;-)
-Stephen
P.S. I do NOT work for Sonatype, but I like and use Nexus.
On 12 April 2010 10:52, Henika Tekwani htekw...@adobe.com wrote:
Hi All,
Basically what I am trying to achieve is to break the default build
lifecycle into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The packaging for this project did not assign a file to the build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it successfully
deploys my project's jar file.
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
Thank you Kristian,
my mistake. I was trying to use parallel with an old project which
uses JUnit3 tests via JUnit4, so no @Test annotations.
Now, I am trying again with another project which is using JUnit4
with tests annotated with @Test.
But I do not see any speed-up improvement (on a Quad Core).
Also, I see:
[INFO] Concurrency config is {threadCount=4, parallel=both,
configurableParallelComputerPresent=false}
What the configurableParallelComputerPresent=false means?
I am not even sure if threadCount=4 means 4 threads per core
or 4 threads in total.
But, at least, this time the number of tests executed is correct.
Thanks again,
Paolo
Kristian Rosenvold wrote:
Please note that the parallel provider actually requires correctly
defined junit4/junit3 tests to run, annotate your methods with @Test.
The classic Junit 4 provider would run a large number of tests that
were incorrectly defined according to junit specifications. The
concurrent provider uses the same
selection mechanism as the junit 4 provider, but junit itself adds an
additional compliance check before running the test.
I also recommend you use the latest release of Junit; 4.8.2, or 4.8.1 if
4.8.2 hasn't reached the repos yet.
Kristian
Den 11.04.2010 23:58, skrev Paolo Castagna:
Hi,
I am trying to see if running JUnit tests in parallel makes any
difference and/or significant speed-up.
I have this in my pom.xml:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.7/version
scopetest/scope
/dependency
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.5/version
configuration
includes
include[...]/include
/includes
parallelmethods/parallel
threadCount4/threadCount
/configuration
/plugin
When I run the tests without parallel and threadCount I see:
Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: ...
While when I run the tests with parallel and threadCount as showed
above:
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0
Is this a bug?
Am I doing something wrong here?
Thanks,
Paolo
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
All your questions should be answered here;
http://incodewetrustinc.blogspot.com/2010/01/run-your-junit-tests-concurrently-with.html
I generally do not advise the use of both, classes is both easier to
get running and usually faster.
Kristian
Den 12.04.2010 12:58, skrev Paolo Castagna:
Thank you Kristian,
my mistake. I was trying to use parallel with an old project which
uses JUnit3 tests via JUnit4, so no @Test annotations.
Now, I am trying again with another project which is using JUnit4
with tests annotated with @Test.
But I do not see any speed-up improvement (on a Quad Core).
Also, I see:
[INFO] Concurrency config is {threadCount=4, parallel=both,
configurableParallelComputerPresent=false}
What the configurableParallelComputerPresent=false means?
I am not even sure if threadCount=4 means 4 threads per core
or 4 threads in total.
But, at least, this time the number of tests executed is correct.
Thanks again,
Paolo
Kristian Rosenvold wrote:
Please note that the parallel provider actually requires correctly
defined junit4/junit3 tests to run, annotate your methods with @Test.
The classic Junit 4 provider would run a large number of tests that
were incorrectly defined according to junit specifications. The
concurrent provider uses the same
selection mechanism as the junit 4 provider, but junit itself adds an
additional compliance check before running the test.
I also recommend you use the latest release of Junit; 4.8.2, or 4.8.1
if 4.8.2 hasn't reached the repos yet.
Kristian
Den 11.04.2010 23:58, skrev Paolo Castagna:
Hi,
I am trying to see if running JUnit tests in parallel makes any
difference and/or significant speed-up.
I have this in my pom.xml:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.7/version
scopetest/scope
/dependency
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.5/version
configuration
includes
include[...]/include
/includes
parallelmethods/parallel
threadCount4/threadCount
/configuration
/plugin
When I run the tests without parallel and threadCount I see:
Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: ...
While when I run the tests with parallel and threadCount as showed
above:
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0
Is this a bug?
Am I doing something wrong here?
Thanks,
Paolo
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Can I control the number string by which the SNAPSHOT keyword is replaced at the time of deployment to snapshot repository?
Hi, As we know that when we deploy an artifact to a snapshot repository the SNAPSHOT keyword in the artifact version, say 9.5.0-SNAPSHOT, is replaced by a timestamp number (e.g., my-app-9.5.0-20100412.084615-1.jar). In this case SNAPSHOT is replaced by “20100412.084615” which is an automatically generated timestamp number. I wanted to know that is there any way by which I can control the number string by which the SNAPSHOT keyword is replaced at the time of deployment, i.e., instead of this automatically generated timestamp number can I supply some other uniquely generated number string (e.g., 20100412.1.234071) at the time of deployment such that the SNAPSHOT keyword is replaced by my uniquely generated number string. Thanks Regards, -Henika -- View this message in context: http://old.nabble.com/Can-I-control-the-number-string-by-which-the-SNAPSHOT-keyword-is-replaced-at-the-time-of-deployment-to-snapshot-repository--tp28216688p28216688.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Can I control the number string by which the SNAPHOT keyword is replaced at the time of deployment to snapshot repository?
Hi, As we know that when we deploy an artifact to a snapshot repository the SNAPHOT keyword in the artifact version, say 9.5.0-SNAPSHOT, is replaced by a timestamp number (e.g., my-app-9.5.0-20100412.084615-1.jar). In this case SNAPHOT is replaced by 20100412.084615 which is an automatically generated timestamp number. I wanted to know that is there any way by which I can control the number string by which the SNAPHOT keyword is replaced at the time of deployment, i.e., instead of this automatically generated timestamp number can I supply some other uniquely generated number string (e.g., 20100412.1.234071) at the time of deployment such that the SNAPHOT keyword is replaced by my uniquely generated number string. Thanks Regards, -Henika
Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
Hi All,
Basically what I am trying to achieve is to break the default build livecycle
into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The packaging for this project did not assign a file to the build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it successfully deploys
my project's jar file.
Thanks Regards,
-Henika
including LD_LIBRARY_PATH in JAR manifest file
Hi, i'm deploying a java application (jar) on a linux server using rpm (maven-rpm-plugin). the jar uses JNI code which needs LD_LIBRARY_PATH defined, in order to find the .so files. can i define it in the manifest file (similar to class-path?) what's the best practice to do it? I've tried putting it in the cron file that launch the app but it doesn't work.. thanks. -- Eyal Edri
Re: Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
Thanks for such a prompt response.
I don't have much idea about how the staging feature of nexus works. I will
have to understand first.
But I wanted to know that is there a way that we can configure our deploy
plugin such that it deploys only when the tests that were run in test phase
pass with 100%?
I mean that based on the outcome of the tests can we control the execution
of the other build phases?
So my case is that
Stephen Connolly-2 wrote:
Use nexus and staged deployment then you can do it in one go.
The artifacts produced in one maven execution are no longer in the reactor
when you run a second time.
Staged deployment is what you want, then you just do mvn deploy... run
your
tests of the artifacts and either drop the staged deployment or promote
it...
If you cannot get the purchase of pro-Nexus, then you can do poor man's
staging with wagon-maven-plugin... or you can wait until staging is
required
by me and I scratch my own itch and write an OSS plugin to provide staging
in Nexus Open Source ;-)
-Stephen
P.S. I do NOT work for Sonatype, but I like and use Nexus.
On 12 April 2010 10:52, Henika Tekwani htekw...@adobe.com wrote:
Hi All,
Basically what I am trying to achieve is to break the default build
lifecycle into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] The packaging for this project did not assign a file to the build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it successfully
deploys my project's jar file.
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216800.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
Kristian Rosenvold wrote:
All your questions should be answered here;
http://incodewetrustinc.blogspot.com/2010/01/run-your-junit-tests-concurrently-with.html
Thanks for the link, very useful.
I have installed the configurable-parallel-computer as well.
Now I see configurableParallelComputerPresent=true. :-)
But, I am still confused by the threadCount option...
Does it have any effect without the configurable-parallel-computer?
Does it have any effect if used in conjunction with perCoreThreadCount?
I generally do not advise the use of both, classes is both easier to
get running and usually faster.
I am now using classes, I trust you.
For the project I am currently testing the parallel execution of
tests, I am probably in this scenario, as you wrote: For a fairly
optimized unit-test set, expect little or no gain - maybe 15-20%.
But, I'll use the approach for other projects.
Paolo
Kristian
Den 12.04.2010 12:58, skrev Paolo Castagna:
Thank you Kristian,
my mistake. I was trying to use parallel with an old project which
uses JUnit3 tests via JUnit4, so no @Test annotations.
Now, I am trying again with another project which is using JUnit4
with tests annotated with @Test.
But I do not see any speed-up improvement (on a Quad Core).
Also, I see:
[INFO] Concurrency config is {threadCount=4, parallel=both,
configurableParallelComputerPresent=false}
What the configurableParallelComputerPresent=false means?
I am not even sure if threadCount=4 means 4 threads per core
or 4 threads in total.
But, at least, this time the number of tests executed is correct.
Thanks again,
Paolo
Kristian Rosenvold wrote:
Please note that the parallel provider actually requires correctly
defined junit4/junit3 tests to run, annotate your methods with @Test.
The classic Junit 4 provider would run a large number of tests that
were incorrectly defined according to junit specifications. The
concurrent provider uses the same
selection mechanism as the junit 4 provider, but junit itself adds an
additional compliance check before running the test.
I also recommend you use the latest release of Junit; 4.8.2, or 4.8.1
if 4.8.2 hasn't reached the repos yet.
Kristian
Den 11.04.2010 23:58, skrev Paolo Castagna:
Hi,
I am trying to see if running JUnit tests in parallel makes any
difference and/or significant speed-up.
I have this in my pom.xml:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.7/version
scopetest/scope
/dependency
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.5/version
configuration
includes
include[...]/include
/includes
parallelmethods/parallel
threadCount4/threadCount
/configuration
/plugin
When I run the tests without parallel and threadCount I see:
Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: ...
While when I run the tests with parallel and threadCount as showed
above:
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0
Is this a bug?
Am I doing something wrong here?
Thanks,
Paolo
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
You're describing Maven's default behavior. Perhaps you have
configured surefire or Maven to react differently to a test failure.
Justin
On Apr 12, 2010, at 7:58 AM, Henika Tekwani htekw...@adobe.com wrote:
Thanks for such a prompt response.
I don't have much idea about how the staging feature of nexus works.
I will
have to understand first.
But I wanted to know that is there a way that we can configure our
deploy
plugin such that it deploys only when the tests that were run in
test phase
pass with 100%?
I mean that based on the outcome of the tests can we control the
execution
of the other build phases?
So my case is that
Stephen Connolly-2 wrote:
Use nexus and staged deployment then you can do it in one go.
The artifacts produced in one maven execution are no longer in the
reactor
when you run a second time.
Staged deployment is what you want, then you just do mvn deploy...
run
your
tests of the artifacts and either drop the staged deployment or
promote
it...
If you cannot get the purchase of pro-Nexus, then you can do poor
man's
staging with wagon-maven-plugin... or you can wait until staging is
required
by me and I scratch my own itch and write an OSS plugin to provide
staging
in Nexus Open Source ;-)
-Stephen
P.S. I do NOT work for Sonatype, but I like and use Nexus.
On 12 April 2010 10:52, Henika Tekwani htekw...@adobe.com wrote:
Hi All,
Basically what I am trying to achieve is to break the default build
lifecycle into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it
gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
---
---
--
[ERROR] BUILD ERROR
[INFO]
---
---
--
[INFO] The packaging for this project did not assign a file to the
build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it
successfully
deploys my project's jar file.
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216800.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
Do you mean that by default the build process halts if tests fail?
justinedelson wrote:
You're describing Maven's default behavior. Perhaps you have
configured surefire or Maven to react differently to a test failure.
Justin
On Apr 12, 2010, at 7:58 AM, Henika Tekwani htekw...@adobe.com wrote:
Thanks for such a prompt response.
I don't have much idea about how the staging feature of nexus works.
I will
have to understand first.
But I wanted to know that is there a way that we can configure our
deploy
plugin such that it deploys only when the tests that were run in
test phase
pass with 100%?
I mean that based on the outcome of the tests can we control the
execution
of the other build phases?
So my case is that
Stephen Connolly-2 wrote:
Use nexus and staged deployment then you can do it in one go.
The artifacts produced in one maven execution are no longer in the
reactor
when you run a second time.
Staged deployment is what you want, then you just do mvn deploy...
run
your
tests of the artifacts and either drop the staged deployment or
promote
it...
If you cannot get the purchase of pro-Nexus, then you can do poor
man's
staging with wagon-maven-plugin... or you can wait until staging is
required
by me and I scratch my own itch and write an OSS plugin to provide
staging
in Nexus Open Source ;-)
-Stephen
P.S. I do NOT work for Sonatype, but I like and use Nexus.
On 12 April 2010 10:52, Henika Tekwani htekw...@adobe.com wrote:
Hi All,
Basically what I am trying to achieve is to break the default build
lifecycle into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it
gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
---
---
--
[ERROR] BUILD ERROR
[INFO]
---
---
--
[INFO] The packaging for this project did not assign a file to the
build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it
successfully
deploys my project's jar file.
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216800.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216953.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Is it possible to execute just the deploy phase without executing all the other phases that precede deploy in the default build lifecycle?
Hi Henika,
That is exactly right. By default, the build process will halt if there are
fails or errors in tests.
On Mon, Apr 12, 2010 at 8:14 PM, Henika Tekwani htekw...@adobe.com wrote:
Do you mean that by default the build process halts if tests fail?
justinedelson wrote:
You're describing Maven's default behavior. Perhaps you have
configured surefire or Maven to react differently to a test failure.
Justin
On Apr 12, 2010, at 7:58 AM, Henika Tekwani htekw...@adobe.com wrote:
Thanks for such a prompt response.
I don't have much idea about how the staging feature of nexus works.
I will
have to understand first.
But I wanted to know that is there a way that we can configure our
deploy
plugin such that it deploys only when the tests that were run in
test phase
pass with 100%?
I mean that based on the outcome of the tests can we control the
execution
of the other build phases?
So my case is that
Stephen Connolly-2 wrote:
Use nexus and staged deployment then you can do it in one go.
The artifacts produced in one maven execution are no longer in the
reactor
when you run a second time.
Staged deployment is what you want, then you just do mvn deploy...
run
your
tests of the artifacts and either drop the staged deployment or
promote
it...
If you cannot get the purchase of pro-Nexus, then you can do poor
man's
staging with wagon-maven-plugin... or you can wait until staging is
required
by me and I scratch my own itch and write an OSS plugin to provide
staging
in Nexus Open Source ;-)
-Stephen
P.S. I do NOT work for Sonatype, but I like and use Nexus.
On 12 April 2010 10:52, Henika Tekwani htekw...@adobe.com wrote:
Hi All,
Basically what I am trying to achieve is to break the default build
lifecycle into two parts:
1. mvn install.
2. mvn deploy:deploy.
The first step runs fine. But when I run mvn deploy:deploy it
gives the
following error:
[INFO] [deploy:deploy {execution: default-cli}]
[INFO]
---
---
--
[ERROR] BUILD ERROR
[INFO]
---
---
--
[INFO] The packaging for this project did not assign a file to the
build
artifact
What am I doing wrong?
Please note that when I run mvn deploy on my project it
successfully
deploys my project's jar file.
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28215706.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
--
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216800.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/Is-it-possible-to-execute-just-the-deploy-phase-without-executing-all-the-other-phases-that-precede-deploy-in-the-default-build-lifecycle--tp28215706p28216953.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Garin Yan
Software Engineer, International Service
Founder International Co.,Ltd.
Address: Suzhou International Science Park (Phase V)
328 Xinghu Rd., Suzhou, Jiangsu, P.R.China, 215123
Tel：+86 512 86665500-7063 Fax：+86 512 87183808 Cell:151 0621 9276
yangu...@gmail.com || www.founderinternational.com
Enjoying 20 years of success satisfying global leaders with every IT need --
Founder’s 30,000 employees are committed to helping you succeed.
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
As the blogpost mentions, junit+surefire by itself is unable to
constrain the number of threads; you need CPC=true for any kind of
thread limitation.
Both threadCount and perCoreThreadCount are thread constraints, so you
need CPC for both of them.
And btw; if you like running betas you'll get a significant speed boost
by switching to jdk 7 ;)
Kristian
Den 12.04.2010 14:05, skrev Paolo Castagna:
Kristian Rosenvold wrote:
All your questions should be answered here;
http://incodewetrustinc.blogspot.com/2010/01/run-your-junit-tests-concurrently-with.html
Thanks for the link, very useful.
I have installed the configurable-parallel-computer as well.
Now I see configurableParallelComputerPresent=true. :-)
But, I am still confused by the threadCount option...
Does it have any effect without the configurable-parallel-computer?
Does it have any effect if used in conjunction with perCoreThreadCount?
I generally do not advise the use of both, classes is both easier
to get running and usually faster.
I am now using classes, I trust you.
For the project I am currently testing the parallel execution of
tests, I am probably in this scenario, as you wrote: For a fairly
optimized unit-test set, expect little or no gain - maybe 15-20%.
But, I'll use the approach for other projects.
Paolo
Kristian
Den 12.04.2010 12:58, skrev Paolo Castagna:
Thank you Kristian,
my mistake. I was trying to use parallel with an old project which
uses JUnit3 tests via JUnit4, so no @Test annotations.
Now, I am trying again with another project which is using JUnit4
with tests annotated with @Test.
But I do not see any speed-up improvement (on a Quad Core).
Also, I see:
[INFO] Concurrency config is {threadCount=4, parallel=both,
configurableParallelComputerPresent=false}
What the configurableParallelComputerPresent=false means?
I am not even sure if threadCount=4 means 4 threads per core
or 4 threads in total.
But, at least, this time the number of tests executed is correct.
Thanks again,
Paolo
Kristian Rosenvold wrote:
Please note that the parallel provider actually requires correctly
defined junit4/junit3 tests to run, annotate your methods with @Test.
The classic Junit 4 provider would run a large number of tests
that were incorrectly defined according to junit specifications.
The concurrent provider uses the same
selection mechanism as the junit 4 provider, but junit itself adds
an additional compliance check before running the test.
I also recommend you use the latest release of Junit; 4.8.2, or
4.8.1 if 4.8.2 hasn't reached the repos yet.
Kristian
Den 11.04.2010 23:58, skrev Paolo Castagna:
Hi,
I am trying to see if running JUnit tests in parallel makes any
difference and/or significant speed-up.
I have this in my pom.xml:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.7/version
scopetest/scope
/dependency
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.5/version
configuration
includes
include[...]/include
/includes
parallelmethods/parallel
threadCount4/threadCount
/configuration
/plugin
When I run the tests without parallel and threadCount I see:
Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
...
While when I run the tests with parallel and threadCount as
showed
above:
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0
Is this a bug?
Am I doing something wrong here?
Thanks,
Paolo
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
Kristian Rosenvold wrote:
As the blogpost mentions, junit+surefire by itself is unable to
constrain the number of threads; you need CPC=true for any kind of
thread limitation.
Both threadCount and perCoreThreadCount are thread constraints, so you
need CPC for both of them.
Let's say I have a Quad Core and I want to run 1 thread per core.
Do I need to use: threadCount4/threadCount?
Or: perCoreThreadCount1/perCoreThreadCount?
Or, they are both equivalent on a Quad Core?
What happens if I use both the options and they have conflicting values?
threadCount100/threadCount
perCoreThreadCount2/perCoreThreadCount
Will this setting be running 100 threads in parallel or 8 on a Quad Core
system?
I re-read the blogpost, but I did not find an answer there.
And btw; if you like running betas you'll get a significant speed boost
by switching to jdk 7 ;)
Thanks for the suggestion and for your patience.
Paolo
Kristian
Den 12.04.2010 14:05, skrev Paolo Castagna:
Kristian Rosenvold wrote:
All your questions should be answered here;
http://incodewetrustinc.blogspot.com/2010/01/run-your-junit-tests-concurrently-with.html
Thanks for the link, very useful.
I have installed the configurable-parallel-computer as well.
Now I see configurableParallelComputerPresent=true. :-)
But, I am still confused by the threadCount option...
Does it have any effect without the configurable-parallel-computer?
Does it have any effect if used in conjunction with perCoreThreadCount?
I generally do not advise the use of both, classes is both easier
to get running and usually faster.
I am now using classes, I trust you.
For the project I am currently testing the parallel execution of
tests, I am probably in this scenario, as you wrote: For a fairly
optimized unit-test set, expect little or no gain - maybe 15-20%.
But, I'll use the approach for other projects.
Paolo
Kristian
Den 12.04.2010 12:58, skrev Paolo Castagna:
Thank you Kristian,
my mistake. I was trying to use parallel with an old project which
uses JUnit3 tests via JUnit4, so no @Test annotations.
Now, I am trying again with another project which is using JUnit4
with tests annotated with @Test.
But I do not see any speed-up improvement (on a Quad Core).
Also, I see:
[INFO] Concurrency config is {threadCount=4, parallel=both,
configurableParallelComputerPresent=false}
What the configurableParallelComputerPresent=false means?
I am not even sure if threadCount=4 means 4 threads per core
or 4 threads in total.
But, at least, this time the number of tests executed is correct.
Thanks again,
Paolo
Kristian Rosenvold wrote:
Please note that the parallel provider actually requires correctly
defined junit4/junit3 tests to run, annotate your methods with @Test.
The classic Junit 4 provider would run a large number of tests
that were incorrectly defined according to junit specifications.
The concurrent provider uses the same
selection mechanism as the junit 4 provider, but junit itself adds
an additional compliance check before running the test.
I also recommend you use the latest release of Junit; 4.8.2, or
4.8.1 if 4.8.2 hasn't reached the repos yet.
Kristian
Den 11.04.2010 23:58, skrev Paolo Castagna:
Hi,
I am trying to see if running JUnit tests in parallel makes any
difference and/or significant speed-up.
I have this in my pom.xml:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.7/version
scopetest/scope
/dependency
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.5/version
configuration
includes
include[...]/include
/includes
parallelmethods/parallel
threadCount4/threadCount
/configuration
/plugin
When I run the tests without parallel and threadCount I see:
Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
...
While when I run the tests with parallel and threadCount as
showed
above:
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0
Is this a bug?
Am I doing something wrong here?
Thanks,
Paolo
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html
perCoreThreadCount is true or false, not a digit. So threadCount=2
and perCoreThreadCount=true gives 16 threads on an 8 core machine.
Kristian
Den 12.04.2010 14:49, skrev Paolo Castagna:
Kristian Rosenvold wrote:
As the blogpost mentions, junit+surefire by itself is unable to
constrain the number of threads; you need CPC=true for any kind of
thread limitation.
Both threadCount and perCoreThreadCount are thread constraints, so
you need CPC for both of them.
Let's say I have a Quad Core and I want to run 1 thread per core.
Do I need to use: threadCount4/threadCount?
Or: perCoreThreadCount1/perCoreThreadCount?
Or, they are both equivalent on a Quad Core?
What happens if I use both the options and they have conflicting values?
threadCount100/threadCount
perCoreThreadCount2/perCoreThreadCount
Will this setting be running 100 threads in parallel or 8 on a Quad Core
system?
I re-read the blogpost, but I did not find an answer there.
And btw; if you like running betas you'll get a significant speed
boost by switching to jdk 7 ;)
Thanks for the suggestion and for your patience.
Paolo
Kristian
Den 12.04.2010 14:05, skrev Paolo Castagna:
Kristian Rosenvold wrote:
All your questions should be answered here;
http://incodewetrustinc.blogspot.com/2010/01/run-your-junit-tests-concurrently-with.html
Thanks for the link, very useful.
I have installed the configurable-parallel-computer as well.
Now I see configurableParallelComputerPresent=true. :-)
But, I am still confused by the threadCount option...
Does it have any effect without the configurable-parallel-computer?
Does it have any effect if used in conjunction with perCoreThreadCount?
I generally do not advise the use of both, classes is both
easier to get running and usually faster.
I am now using classes, I trust you.
For the project I am currently testing the parallel execution of
tests, I am probably in this scenario, as you wrote: For a fairly
optimized unit-test set, expect little or no gain - maybe 15-20%.
But, I'll use the approach for other projects.
Paolo
Kristian
Den 12.04.2010 12:58, skrev Paolo Castagna:
Thank you Kristian,
my mistake. I was trying to use parallel with an old project which
uses JUnit3 tests via JUnit4, so no @Test annotations.
Now, I am trying again with another project which is using JUnit4
with tests annotated with @Test.
But I do not see any speed-up improvement (on a Quad Core).
Also, I see:
[INFO] Concurrency config is {threadCount=4, parallel=both,
configurableParallelComputerPresent=false}
What the configurableParallelComputerPresent=false means?
I am not even sure if threadCount=4 means 4 threads per core
or 4 threads in total.
But, at least, this time the number of tests executed is correct.
Thanks again,
Paolo
Kristian Rosenvold wrote:
Please note that the parallel provider actually requires
correctly defined junit4/junit3 tests to run, annotate your
methods with @Test.
The classic Junit 4 provider would run a large number of tests
that were incorrectly defined according to junit specifications.
The concurrent provider uses the same
selection mechanism as the junit 4 provider, but junit itself
adds an additional compliance check before running the test.
I also recommend you use the latest release of Junit; 4.8.2, or
4.8.1 if 4.8.2 hasn't reached the repos yet.
Kristian
Den 11.04.2010 23:58, skrev Paolo Castagna:
Hi,
I am trying to see if running JUnit tests in parallel makes any
difference and/or significant speed-up.
I have this in my pom.xml:
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.7/version
scopetest/scope
/dependency
[...]
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.5/version
configuration
includes
include[...]/include
/includes
parallelmethods/parallel
threadCount4/threadCount
/configuration
/plugin
When I run the tests without parallel and threadCount I see:
Tests run: 9491, Failures: 0, Errors: 0, Skipped: 0, Time
elapsed: ...
While when I run the tests with parallel and threadCount as
showed
above:
Tests run: 40, Failures: 0, Errors: 0, Skipped: 0
Is this a bug?
Am I doing something wrong here?
Thanks,
Paolo
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe,
Re: Wrong number of tests run when running JUnit tests in parallel: any help?
Kristian Rosenvold wrote: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html perCoreThreadCount is true or false, not a digit. So threadCount=2 and perCoreThreadCount=true gives 16 threads on an 8 core machine. Slap in my face. :-) Thanks, I am happy now. Paolo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependencies and Aggregation
By adding a dependency to m4, you simply add that dependency to all its
childs.
Said that, the m4.1 now contains dependency of himself, which is what the
system informed you.
without the dependency on m4, the system should work fine.
2010/4/12 Karl Heinz Marbaise k...@soebes.de
Hi Harald,
first of all thanks for your help...
Harald Entner-3 wrote:
m4 does not have any dependencies to its submodules (it just aggregates
them).
That seemed to be not the full truth...if i try to supplemental define a
dependency in my m4 module to make the dependency to m4.1 explicit...
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm4.1/artifactId
version${project.version}/version
/dependency
dependency
I will get the following message:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge
between
'Vertex{label='com.xyz.test.build:m4.1'}' and
'Vertex{label='com.xyz.test.build:m4.1'}' introduces to cycle in the graph
com.xyz.test.build:m4.1 -- com.xyz.test.build:m4.1
That's indicating that the dependency has been inserted already...
Harald Entner-3 wrote:
so in order to build 3.2, it is sufficient that m4 is built first
(e.g. maven includes modules and dependencies defined in m4).
In my opinion the dependencies of m4 should be built
first...(m4.1...m4.5)...
Harald Entner-3 wrote:
Does it built correctly if you delete your repository (at least the m*
entries? If it does, i don't see a problem, as it is still working that
way.
Doesn't change anything in the order of the build
Kind regards
Karl Heinz Marbaise
--
View this message in context:
http://old.nabble.com/Dependencies-and-Aggregation-tp28214892p28215393.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependencies and Aggregation
On 4/12/10 4:02 AM, Karl Heinz Marbaise wrote: ... Maybe i misunderstand the usage of a module ...or do i have to give simply the modules m4.1...m4.5 as dependency instead of using m4? The m4 module is a aggregation of multiple modules (m4.1...m4.5) which are needed as dependency so it would be nice just to give m4 as dependency This is the source of your misunderstanding. m4 is an aggregation for build purposes ONLY. It is not an aggregation of the artifacts and sub-modules are not considered when calculating the dependency tree. Or does exist an other solution to handle such a problem? If your problem is that you don't want to explicitly declare five dependencies in m3.2, I don't really consider that a problem. You're saving like 90 seconds in copying-and-pasting. But if you really wanted, you could create an intermediate project which aggregates dependencies the way you want, just via the dependencies element, i.e. m3.2 depends upon m4.a m4.a depends upon m4.1, m4.2, m4.3, etc. I'm pretty sure m4.a needs to be a JAR project, but I could be wrong about this. Justin Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Dependencies and Aggregation
Does this help you?
http://maven.apache.org/guides/introduction/introduction-to-dependency-m
echanism.html#Importing_Dependencies
Subir
-Original Message-
From: Karl Heinz Marbaise [mailto:k...@soebes.de]
Sent: Monday, April 12, 2010 1:32 PM
To: users@maven.apache.org
Subject: Dependencies and Aggregation
Hi,
i'm trying to understand the handling of dependencies/aggregation in
Maven...
So i've setup the following structure:
+--- root (root pom)
+--- m1
+--- m1.1
+--- m1.2
+--- m1.3
+--- m1.4
+--- m1.5
+--- m2
+--- m2.1
+--- m2.2
+--- m2.3
+--- m2.4
+--- m2.5
+--- m3
+--- m3.1
+--- m3.2
+--- m3.3
+--- m3.4
+--- m3.5
+--- m4
+--- m4.1
+--- m4.2
+--- m4.3
+--- m4.4
+--- m4.5
The root-pom has only modules listed (m1, m2, m3, m4)...
The m1 (m2, m3, m4) has a list of modules as well ( m1.1, m1.2 ...
m1.5)...m1 has defined the parent (root-pom)...and the modules m1.1 till
m1.5 has the parent m1 whereas the m2.1 till m2.5 has the parent
m2...and so on...
The modules m1.1 till m4.5 are simple packages which have default
packaging type (jar)...and contain a simple class and of course a test
case for test purposes.
So if i call mvn install on the root pom everything works as expected
So my next step was to define a dependency of one module to an
other...(m3.2)...so in m3.2 pom i used the following:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
/dependencies
Ok...just tried to build...mvn install as expected the reactor order
changed
But now i tried something different. I defined the dependency in m3.2's
pom to use m4 as dependency:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
dependency
groupId${project.groupId}/groupId
artifactIdm4/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
Ok..tried to build mvn install and was a little bit confused...
The order in the reactor has changed, but only the module m4 itself has
been built before m2 instead of all sub-modules of m4...what i got was
the
following:
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ModuleTest :: Parent .. SUCCESS
[3.323s] [INFO] ModuleTest :: M1 ..
SUCCESS [0.031s] [INFO] ModuleTest :: M1 :: M1.1
.. SUCCESS [2.941s] [INFO] ModuleTest :: M1
:: M1.2 .. SUCCESS [1.216s] [INFO]
ModuleTest :: M1 :: M1.3 .. SUCCESS [0.867s]
[INFO] ModuleTest :: M1 :: M1.4 .. SUCCESS
[0.963s] [INFO] ModuleTest :: M1 :: M1.5 ..
SUCCESS [0.672s] [INFO] ModuleTest :: M2
.. SUCCESS [0.034s] [INFO]
ModuleTest :: M2 :: M2.1 .. SUCCESS [0.932s]
[INFO] ModuleTest :: M2 :: M2.2 .. SUCCESS
[0.703s] [INFO] ModuleTest :: M2 :: M2.3 ..
SUCCESS [0.777s] [INFO] ModuleTest :: M2 :: M2.4
.. SUCCESS [0.740s] [INFO] ModuleTest :: M2
:: M2.5 .. SUCCESS [0.745s] [INFO]
ModuleTest :: M3 .. SUCCESS [0.035s]
[INFO] ModuleTest :: M3 :: M3.1 .. SUCCESS
[0.748s] [INFO] ModuleTest :: M4 ..
SUCCESS [0.035s] [INFO] ModuleTest :: M3 :: M3.2
.. SUCCESS [1.023s] [INFO] ModuleTest :: M3
:: M3.3 .. SUCCESS [0.763s] [INFO]
ModuleTest :: M3 :: M3.4 .. SUCCESS [0.668s]
[INFO] ModuleTest :: M3 :: M3.5 .. SUCCESS
[0.694s] [INFO] ModuleTest :: M4 :: M4.1 ..
SUCCESS [0.724s] [INFO] ModuleTest :: M4 :: M4.2
.. SUCCESS [0.748s] [INFO] ModuleTest :: M4
:: M4.3 .. SUCCESS [0.679s] [INFO]
ModuleTest :: M4 :: M4.4 .. SUCCESS [0.876s]
[INFO] ModuleTest :: M4 :: M4.5 .. SUCCESS
[0.660s] [INFO]
Maybe i misunderstand the usage of
Re: Dependencies and Aggregation
Hi Karl Heinz,
Karl Heinz Marbaise wrote at Montag, 12. April 2010 10:02:
[snip]
But now i tried something different. I defined the dependency in m3.2's
pom to use m4 as dependency:
dependencies
dependency
groupId${project.groupId}/groupId
artifactIdm2.1/artifactId
version${project.version}/version
/dependency
dependency
groupId${project.groupId}/groupId
artifactIdm4/artifactId
version${project.version}/version
typepom/type
/dependency
/dependencies
Ok..tried to build mvn install and was a little bit confused...
The order in the reactor has changed, but only the module m4 itself has
been built before m2 instead of all sub-modules of m4...
[snip]
Every Maven project defines one main artifact. I suppose all your Mx.y
modules produce some kind of Java archive. However, the parent project have
only the POM file itself as main artifact. Since it has no dependencies, it
can be build immediately. It does not matter that it defines submodules.
Therefore Maven simply builds M4 alone before M3.2 to satisfy M3.2's
dependencies. If M3.2 is depending on one of the artifacts of M4.x, you have
to define the dependency explicitly.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
How to get some menus expanded by default
When I go here, the project information menu is expanded by default. http://maven.apache.org/plugins/maven-site-plugin/ None of my projects have this, in spite of the fact that site.xml describes the default for collapse as 'false'. Is there something happening in the skin that arranges this. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
site plugin and site.xml inheritance
Using site 2.1. I have a parent project with packagingpom/packaging. So, its site.xml is not getting published. If I want to share a site.xml at this level, do I need to make a skin? Is there some other trick? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
some question
one ： I use maven version 2.2.1，I can download pom file，but the *.jar not。 the pom file and jar in the same dictory two： maven-jetty-plugin how to write the jetty-env.xml and jetty.xml thanks
Re: How to get some menus expanded by default
I do this by manually specifying the menus for all my reports and not using the reports variable in site.xml. There may be other ways. If there are, I'd like to know. -K On Apr 12, 2010, at 9:38 AM, Benson Margulies wrote: When I go here, the project information menu is expanded by default. http://maven.apache.org/plugins/maven-site-plugin/ None of my projects have this, in spite of the fact that site.xml describes the default for collapse as 'false'. Is there something happening in the skin that arranges this. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: some question
42 12.04.2010 17:56, perfer_chen ??: one ?? I use maven version 2.2.1??I can download pom file??but the *.jar not?? the pom file and jar in the same dictory two?? maven-jetty-plugin how to write the jetty-env.xml and jetty.xml thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
appassembler-maven-plugin how to set CLASSPATH_PREFIX
I see there is an unused CLASSPATH_PREFIX macro in the generated batch file, how can I set this value in the pom? -Dave
Re: How to get some menus expanded by default
That doesn't seem to be the situation at the maven-site-plugin itself. And updating to 2.1 seems to have changed this for some of my projects. On Mon, Apr 12, 2010 at 11:49 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: I do this by manually specifying the menus for all my reports and not using the reports variable in site.xml. There may be other ways. If there are, I'd like to know. -K On Apr 12, 2010, at 9:38 AM, Benson Margulies wrote: When I go here, the project information menu is expanded by default. http://maven.apache.org/plugins/maven-site-plugin/ None of my projects have this, in spite of the fact that site.xml describes the default for collapse as 'false'. Is there something happening in the skin that arranges this. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to get some menus expanded by default
Well, I don't like collapsed menus, so I specify all the menus in site.xml. But that's just me. -K On Apr 12, 2010, at 12:17 PM, Benson Margulies wrote: That doesn't seem to be the situation at the maven-site-plugin itself. And updating to 2.1 seems to have changed this for some of my projects. On Mon, Apr 12, 2010 at 11:49 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: I do this by manually specifying the menus for all my reports and not using the reports variable in site.xml. There may be other ways. If there are, I'd like to know. -K On Apr 12, 2010, at 9:38 AM, Benson Margulies wrote: When I go here, the project information menu is expanded by default. http://maven.apache.org/plugins/maven-site-plugin/ None of my projects have this, in spite of the fact that site.xml describes the default for collapse as 'false'. Is there something happening in the skin that arranges this. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to get some menus expanded by default
Do you have the maven-project-info-reports-plugin configured to generate the index report? For the site plugin the menu is only expanded because the About menu item points to index.html. HTH, -Lukas Benson Margulies wrote: That doesn't seem to be the situation at the maven-site-plugin itself. And updating to 2.1 seems to have changed this for some of my projects. On Mon, Apr 12, 2010 at 11:49 AM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: I do this by manually specifying the menus for all my reports and not using the reports variable in site.xml. There may be other ways. If there are, I'd like to know. -K On Apr 12, 2010, at 9:38 AM, Benson Margulies wrote: When I go here, the project information menu is expanded by default. http://maven.apache.org/plugins/maven-site-plugin/ None of my projects have this, in spite of the fact that site.xml describes the default for collapse as 'false'. Is there something happening in the skin that arranges this. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: some question
appears someone on this list has been watching Dr Who Martin -- __ Note de déni et de confidentialité Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 12 Apr 2010 20:47:49 +0400 From: di...@magenta-technology.ru To: users@maven.apache.org Subject: Re: some question 42 12.04.2010 17:56, perfer_chen §á§Ú§ê§Ö§ä: one £º I use maven version 2.2.1£¬I can download pom file£¬but the *.jar not¡£ the pom file and jar in the same dictory two£º maven-jetty-plugin how to write the jetty-env.xml and jetty.xml thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
Re: some question
appears someone on this list doesn't know their references... Hitchhiker's Guide to the Galaxy -Stephen On 12 April 2010 19:00, Martin Gainty mgai...@hotmail.com wrote: appears someone on this list has been watching Dr Who Martin -- __ Note de déni et de confidentialité Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Mon, 12 Apr 2010 20:47:49 +0400 From: di...@magenta-technology.ru To: users@maven.apache.org Subject: Re: some question 42 12.04.2010 17:56, perfer_chen §á§Ú§ê§Ö§ä: one £º I use maven version 2.2.1£¬I can download pom file£¬but the *.jar not¡£ the pom file and jar in the same dictory two£º maven-jetty-plugin how to write the jetty-env.xml and jetty.xml thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
Re: README.txt bundled with maven doesn't mention M2_HOME
Okay. Thanks for the input guys. So it seems like _not_ defining it is the more flexible option, which would mean removing it from the web site materials. I guess a JIRA is in order. I'll point it at this thread. Any tooling absolutely require this M2_HOME var that you know of? M2Eclipse? IntelliJ? Thanks, -Matthew On Thu, Apr 8, 2010 at 12:56 AM, Jörg Schaible joerg.schai...@gmx.de wrote: Brett Porter wrote at Donnerstag, 8. April 2010 05:53: Sounds like making them consistent makes sense. Note that the env var is not required - it is mostly for people that wish to run multiple versions of Maven. Actually I do explicitly not set it, *because* I run different versions of Maven. The Maven start script will set it accordingly itself. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
