2012/12/4 Peter Palmreuther pitpa...@gmail.com:
Hello Olivier,
Am 03.12.2012 um 10:52 schrieb Olivier Lamy ol...@apache.org:
Thanks for the test project.
It's now fixed.
You can test the fix with compiler plugin 3.1-SNAPSHOT and with
plexus-compiler-eclipse 2.1-SNAPSHOT
Thanks a lot.
I
By the way, I've just noticed that you use? xmlversion=”1.1” encoding=”ISO-8859-1”whereas it should be?xmlversion="1.1" encoding="ISO-8859-1"?I've removed whitespace before xmlversion, changed quotes to ASCII, and most importantly added a missing question mark in the end./MikhailFrom: "Praveen
Sorry it is just typo in the mail.
But in real it is right as per syntax, there is no extra space
or any character.
Thanks
Warm Regards,
Praveen Jain
From: Mikhail Kalkov
[mailto:mikhail.kal...@purplescout.se]
Sent: Tuesday, December 04, 2012 3:01 PM
To: Maven Users
Hello Olivier,
Am 04.12.2012 um 09:00 schrieb Olivier Lamy ol...@apache.org:
2012/12/4 Peter Palmreuther pitpa...@gmail.com:
Hello Olivier,
Am 03.12.2012 um 10:52 schrieb Olivier Lamy ol...@apache.org:
Thanks for the test project.
It's now fixed.
You can test the fix with compiler
Hi,
While trying to migrate a project from Maven 2 to Maven 3, I
encountered a problem, the essence of which can be demonstrated by the
following simple example.
Consider the following POM:
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdA/artifactId
I have configured my project to execute a jboss-as-maven-plugin goal
(deploy) at pre-integration-test phase. When executing (mvn install), I get
:
WARNING: Failed to getClass for org.jboss.as.plugin.deployment.Deploy
And the goal fails to be executed... I already posted a question with some
more
but how can I know it allow filesetsdirectory...elements in pom?
is it from this page to know
http://maven.apache.org/plugins/maven-clean-plugin/clean-mojo.html
?
Yes, I'd say your primary information source for knowing how you can
configure a plugin's goal is that page. For some plugins,
Hi,
as part of our build wer're building client specific installer zips.
These are around 10 different assembly descriptors which have 90%
overlap. If possible I'd like to get rid of this overlap but I haven't
found a way to create an assembly from more than one assembly
descriptor. My approach