The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.16
This release addresses some serious problems with character encodings in
the test report XML files and adds a new Parallel Computer implementation
to the JUnit 4.7+ provider, offering a bunch of new
Hi,
Thanks for the suggestions. I did try configuring the reserve-network-port
goal in my pom.xml so that it sets the randomly selected port into the
property jetty.proxy.port. Then I used the properties maven plugin to write
this property to the file
[aside]
Why oh why do people always go for the most complex way to solve a
problem... using 10 million plugins when one will do
[/aside]
You were on the right track with this... you just picked a phase of `test`
which is too late in the game as the lifecycle executions will happen
before any
Hello,
Im very new to Maven (im researching it)
Im assigned to project that using maven.
I got the message when use command: Maven Test in eclipse.
Currently I don't know how to fix it :(
Can anybody help me? I really don't know the root cause
I appreciate too much...
I comment main code to
Richard,
AFAIK attachArtifact just tells Maven to install an additional binary to
it's local cache resp. to deploy it to the distribution repository.
What you want, as far as I understand, is to create an artifact which will
be picked up later on and included in a war? You should probably create
Thanks Stephen - that solved it.
I had not researched the surefire/failsafe configurations enough. I've used
option 2 and passed the port to the failsafe plugin as it is an integration
test. Also, the phase I have used is pre-integration-test. There is a
default port already setup in a properties
Hi,
does anybody have experiences with
https://github.com/tesla/tesla-concurrent-localrepo?
Does it work well?
I want to use it in a 'normal' maven build.
Is there an example on how to use it / how to configure it?
Regards, Stephan
Hi,
From the output it seems more like you might actually have an issue with
your tests, not with maven.
Does this test also fail if you run mvn test from the command line at the
root of that project?
Cheers
Le 20 août 2013 12:04, HoangVo thanho...@gmail.com a écrit :
Hello,
Im very new to
You probably should have a look to the surefire reports to see the output
of the tests and why it failed.
Reports are usually in target/surefire-reports but you seem to have its
location overriden in your pom.
On Tue, Aug 20, 2013 at 2:50 PM, Baptiste Mathus m...@batmat.net wrote:
Hi,
From
Thank you Mirko, I got a similar reply on Jira. I'll do as you suggested.
Best regards,
Richard
-Original Message-
From: Mirko Friedenhagen [mailto:mfriedenha...@gmail.com]
Sent: Tuesday, August 20, 2013 6:20 AM
To: Maven Users List
Subject: RE: artifact attached by plugin not
AFAIK, with xml entities not supported and mixins still unimplemented,
your best bet is to use the release plugin to update the versions
without going at it manually.
hth,
Manos
-
To unsubscribe, e-mail:
Is there any merit to the idea of having a configuration option in
maven-war-plugin to include attached artifacts in the webapp in the same way it
includes dependent artifacts?
-Richard
-Original Message-
From: Mirko Friedenhagen [mailto:mfriedenha...@gmail.com]
Sent: Tuesday, August
Hello Richard,
x-posted to dev, as the war-plugin is a core-plugin:
- IMO attaching would be the wrong term as it has another meaning.
- This is more of a generated jar (as generated sources, classes etc.)
- IMO packages should go in Maven modules of their own.
Regards Mirko
--
Sent from my
In my project,there is a TestBase class. All tests in the future will extend
from this class.
I have just created a basic test extends from that class. Then maven clean
install = Build success.
Next I select maven test. It failed.
I try to debug backing up code from Test Base and add basic code
Hi,
I'm using Maven 3.0.3. I have a multi-module project and want to use the
Maven release plugin (through Jenkins). When running release:prepare, the
process dies with the error
Executing Maven: -B -f /scratch/jenkins/workspace/subco/parent/pom.xml
-amd -pl
Remove version${project.version}/version from child pom
and add whole
dependency
groupIdorg.mainco.subco/groupId
artifactIdchildModuleB/artifactId
version${project.version}/version
/dependency
to main (direct parent, I guess) pom, inside dependencyManagement
element.
Regards,
Hey Ziga,
Is it possible to do the same thing for test-jar's?
It looks like maven still wants the version.
Is it OK just just use ${project.version} in that case?
*Brett VanderVeen* | brett.vanderv...@gfs.com
*Gordon Food Service®* | IS Transportation | *www.gfs.com*
P 616-717-6042 | C
Ignore my last email. inserts foot in mouth
It would help if I had the version entry on the parent pom.
Example:
dependency
groupIdorg.mainco.subco/groupId
artifactIdchildModuleB/artifactId
version${project.version}/version
typetest-jar/type
scopetest/scope
/dependency
*Brett VanderVeen* |
Would need to check but maybe try adding -DautoVersionSubmodules=true so
that all modules get released with that version.
My 2 cents.
Le 20 août 2013 19:54, laredotornado-3 laredotorn...@gmail.com a écrit :
Hi,
I'm using Maven 3.0.3. I have a multi-module project and want to use the
Maven
19 matches
Mail list logo
