Hi All,
A couple of questions about integration tests..
1) Default vs non-default plugins
I needed to include the maven-failsafe-plugin plugin to introduce
integration tests into my project, but I didn't need to introduce the
maven-surefire-plugin to my pom.xml for unit tests. Fair enough, but
On 6 October 2014 10:31, Robert Mark Bram robertmarkb...@gmail.com wrote:
Hi All,
A couple of questions about integration tests..
1) Default vs non-default plugins
I needed to include the maven-failsafe-plugin plugin to introduce
integration tests into my project, but I didn't need to
Hi there,
we just tried to update our usage of the maven-resource-plugin to Version
2.7 but afterwards the build failed with the following error message:
Failed to execute goal
org.apache.maven.plugins:maven-resource-plugin:2.7:resource (default
resources) on project XYZ: Mark invalid - [Help
So, shouldn't the misleading warning be fixed? Sounds like something for
3.2.4 -- unless the warning is issued in the site plugin itself.
Cheers,
Paul
On Sat, Oct 4, 2014 at 2:15 AM, Hervé BOUTEMY herve.bout...@free.fr wrote:
that used to be true with Maven 2, but is not any more since Maven
Also tried useUniqueVersionsfalse/useUniqueVersions in the manifest of
the jars war. It still appends version to the SNAPSHOT jars located inside
the WAR.
--
View this message in context:
http://maven.40175.n5.nabble.com/WAR-contains-SNAPSHOT-JARs-with-timestamps-tp5807695p5807865.html
Sent
http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mapping.html
and strip the version if it is really important to you...
On 6 October 2014 15:38, captainslow srinivas.nag...@gmail.com wrote:
Also tried useUniqueVersionsfalse/useUniqueVersions in the manifest of
the jars war.
Hi,
first thanks for going so fast to a new version and finding this
issue...if it really is one...
On 10/6/14 12:04 PM, Michael Lemler wrote:
Hi there,
we just tried to update our usage of the maven-resource-plugin to Version
2.7 but afterwards the build failed with the following error
AFAIK, it was fixed in Maven 3.1.0-alpha-1
I just tested and couldn't get any warning with Maven 3.2.3, where I get it
with Maven 3.0.5
what warning are you seeing?
can you share a test project?
Regards,
Hervé
Le lundi 6 octobre 2014 09:16:31 Paul Benedict a écrit :
So, shouldn't the