creating an assembly from more than one descriptor?

2012-12-04 Thread Dirk Olmes
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 would be to factor the stuff that's common in
all assembly descriptors into a shared one and only put what's different
for each customer into a separate ones.

Is there a way to do this?

-dirk

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: how to know what configuration element I can add in a plugin?

2012-12-04 Thread Anders Hammar
> but how can I know it allow ...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, the developer has
also written example(s) which could guide you.

/Anders


plugin configuration (jboss-as-maven-plugin)

2012-12-04 Thread aldric
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 information on Stackoverfow :
http://stackoverflow.com/questions/13694243

Thanks in advance for any help


Wrong resolution of dependency scope by Maven 3?

2012-12-04 Thread Dmitry Batrak
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:


4.0.0

test
A
1.0



org.apache.axis2
axis2-xmlbeans
1.5
provided


org.apache.axis2
axis2-codegen
1.5


org.apache.geronimo.specs
geronimo-stax-api_1.0_spec






Running 'mvn dependency:resolve' for this POM yields a strange result.
Namely, it says that that my module depends on
geronimo-stax-api_1.0_spec with 'compile' scope.
This artifact is a transitive dependency of both axis2-xmlbeans and
axis2-codegen, and, according to rules for transitive dependencies, I
would expect the resolved scope of geronimo-stax-api_1.0_spec to be
'provided'. With Maven 2 I get exactly the result I expect.

Should I raise a JIRA ticket for this issue, or am I missing some
point, and this is the desired behaviour in the new version of Maven?

For reference - I used Maven version 3.0.4. I also checked the above
with the latest version (2.6) of dependency plugin - result was the
same.

Best regards,
Dmitry Batrak

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: No compile errors with plexus-compiler-eclipse

2012-12-04 Thread Peter Palmreuther
Hello Olivier,

Am 04.12.2012 um 09:00 schrieb Olivier Lamy :

> 2012/12/4 Peter Palmreuther :
>> Hello Olivier,
>> 
>> Am 03.12.2012 um 10:52 schrieb Olivier Lamy :
>> 
>>> 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 was able to get maven-compiler-plugin:3.1-SNAPSHOT from Apache snapshot 
>> repository.
>> Sadly I can't find plexus-compiler-*:2.1-SNAPSHOT.
>> I've set my Nexus to proxy 
>> https://nexus.codehaus.org/content/repositories/snapshots/, but that seems 
>> to be the wrong location.
>> Can you point me to the correct repository?
> 
> Use: https://oss.sonatype.org/content/repositories/plexus-snapshots

Thanks, seems to work. Both, the repository URL and the fix.
-- 
Regards,

Peter
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



RE: problem while conversion in build

2012-12-04 Thread Praveen Jain








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 List
Subject: Re: problem while conversion in build





 



By
the way, I've just noticed that you use

whereas it should be




I've
removed whitespace before xmlversion, changed quotes to ASCII, and most
importantly added a missing question mark in the end.

/Mikhail



 









From: "Praveen Jain"

To: "Maven Users List" 
Sent: Tuesday, December 4, 2012 6:01:34 AM
Subject: RE: problem while conversion in build

I am using Xdoclet 1.2.3 and org.apache.maven.plugin is 1.6.

There is no encoding tag in validator-global.xml

If I add 



Then it simply added to validation.xml with all other tag and 

This line is added 2 time in Validation.xml   and it
fails while xml validation. but conversion done properly. So I cannot add
explicit encoding in validator-global.xml.

If encoding is UTF-8 then german character converted to garbage
value.

 

How can we define which encoding should use while merging ? by
default it is UTF-8 which is not working.



 

 

Thanks

Warm Regards,

Praveen Jain

 



 





From: Mikhail Kalkov [mailto:mikhail.kal...@purplescout.se] 
Sent: Monday, December 03, 2012 11:05 PM
To: Maven Users List
Subject: Re: problem while conversion in build





 



I've
never used XDoclet but it sounds like xmlencoding attribute of  tag only sets the output encoding,
and there is no simple way to set the input incoding. It is also noteworthy
that the default output encoding is UTF-8. Can you try to convert your
validator-global.xml from iso-8859-1 to utf-8? Which version of xdoclet and
xdoclet-maven-plugin do you use by the way?




/Mikhail



 









From: "Praveen Jain"

To: "Maven Users List" 
Sent: Monday, December 3, 2012 11:57:39 AM
Subject: RE: problem while conversion in build

When we include xdoclet in the project there is no need to write
validation.xml (for struts validation).

All rules are defined in validator-global.xml and when user
build using maven validation.xml is generated runtime and validator-global.xml
is merged in validation.xml

All properties are defined in 

http://xdoclet.sourceforge.net/xdoclet/ant/xdoclet/modules/apache/struts/StrutsValidationXmlSubTask.html

 

if I write some german character in the validator-global.xml ,
and when build all german character are converted to some garbage value in
validation.xml.

 

hope this is will clear the problem.

 



 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 



 





From: Mikhail Kalkov [mailto:mikhail.kal...@purplescout.se] 
Sent: Monday, December 03, 2012 3:47 PM
To: Maven Users List
Subject: Re: problem while conversion in build





 



Hi,

I don't understand your problem and doubt many people do. What is
validation.xml and how does it relate to validation-global.xml? Why is
form-validation tag relevant? I am afraid your question is as cryptic as
Napoleon's kremlin letter (http://www.bbc.co.uk/news/world-europe-20572136). If
you succinctly describe how your problem can be reproduced by any mailing list
subscriber, there is a better chance you get a helpful reply.




Kind regards,
Mikhail Kalkov



 









From: "Praveen Jain"

To: "Maven Users List" 
Sent: Monday, December 3, 2012 5:46:40 AM
Subject: RE: problem while conversion in build

Can u please someone tell , how can I add german characters in
validation.global.xml?

So that it can be converted exactly in validation.xml m while
building.

 



 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 



 





From: Praveen Jain 
Sent: Thursday, November 29, 2012 4:25 PM
To: Maven Users List
Subject: RE: problem while conversion in build





 

Yes I am using ISO-8859-1

 

 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 

 



From: Martin Eisengardt [mailto:martin.eisenga...@gmail.com] 
Sent: Thursday, November 29, 2012 4:17 PM
To: Maven Users List
Subject: Re: problem while conversion in build



 



Do you set any encoding in your
pom.xml?





for example see http://maven.apache.org/plugins/maven-resources-plugin/examples/encoding.html





 





 



On Thu, Nov 29, 2012 at 11:44 AM,
Praveen Jain 
wrote:





 

Hi

 I am building my project using maven,

I have some german character in my validation-global.xml

When I build it they got converted to some garbage value in
validation.xml.

 

If I add 
in validation-global.xml , then after build german character placed as it is in
validation.xml.

But in validation.xm

Re: problem while conversion in build

2012-12-04 Thread Mikhail Kalkov
By the way, I've just noticed that you usewhereas it should beI've removed whitespace before xmlversion, changed quotes to ASCII, and most importantly added a missing question mark in the end./MikhailFrom: "Praveen Jain" To: "Maven Users List" Sent: Tuesday, December 4, 2012 6:01:34 AMSubject: RE: problem while conversion in build













I am using Xdoclet 1.2.3 and org.apache.maven.plugin is 1.6.

There is no encoding tag in validator-global.xml

If I add 



Then it simply added to validation.xml with all other tag and 

This line is added 2 time in Validation.xml   and it fails while
xml validation. but conversion done properly. So I cannot add explicit encoding
in validator-global.xml.

If encoding is UTF-8 then german character converted to garbage
value.

 

How can we define which encoding should use while merging ? by
default it is UTF-8 which is not working.



 

 

Thanks

Warm Regards,

Praveen Jain

 



 





From: Mikhail Kalkov
[mailto:mikhail.kal...@purplescout.se] 
Sent: Monday, December 03, 2012 11:05 PM
To: Maven Users List
Subject: Re: problem while conversion in build





 



I've
never used XDoclet but it sounds like xmlencoding attribute of  tag only sets the output encoding,
and there is no simple way to set the input incoding. It is also noteworthy
that the default output encoding is UTF-8. Can you try to convert your
validator-global.xml from iso-8859-1 to utf-8? Which version of xdoclet and
xdoclet-maven-plugin do you use by the way?




/Mikhail



 









From: "Praveen Jain"

To: "Maven Users List" 
Sent: Monday, December 3, 2012 11:57:39 AM
Subject: RE: problem while conversion in build

When we include xdoclet in the project there is no need to write
validation.xml (for struts validation).

All rules are defined in validator-global.xml and when user
build using maven validation.xml is generated runtime and validator-global.xml
is merged in validation.xml

All properties are defined in 

http://xdoclet.sourceforge.net/xdoclet/ant/xdoclet/modules/apache/struts/StrutsValidationXmlSubTask.html

 

if I write some german character in the validator-global.xml ,
and when build all german character are converted to some garbage value in
validation.xml.

 

hope this is will clear the problem.

 



 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 



 





From: Mikhail Kalkov [mailto:mikhail.kal...@purplescout.se] 
Sent: Monday, December 03, 2012 3:47 PM
To: Maven Users List
Subject: Re: problem while conversion in build





 



Hi,

I don't understand your problem and doubt many people do. What is
validation.xml and how does it relate to validation-global.xml? Why is
form-validation tag relevant? I am afraid your question is as cryptic as
Napoleon's kremlin letter (http://www.bbc.co.uk/news/world-europe-20572136). If
you succinctly describe how your problem can be reproduced by any mailing list
subscriber, there is a better chance you get a helpful reply.




Kind regards,
Mikhail Kalkov



 









From: "Praveen Jain"

To: "Maven Users List" 
Sent: Monday, December 3, 2012 5:46:40 AM
Subject: RE: problem while conversion in build

Can u please someone tell , how can I add german characters in
validation.global.xml?

So that it can be converted exactly in validation.xml m while
building.

 



 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 



 





From: Praveen Jain 
Sent: Thursday, November 29, 2012 4:25 PM
To: Maven Users List
Subject: RE: problem while conversion in build





 

Yes I am using ISO-8859-1

 

 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 

 



From: Martin Eisengardt [mailto:martin.eisenga...@gmail.com] 
Sent: Thursday, November 29, 2012 4:17 PM
To: Maven Users List
Subject: Re: problem while conversion in build



 



Do you set any encoding in your
pom.xml?





for example see http://maven.apache.org/plugins/maven-resources-plugin/examples/encoding.html





 





 



On Thu, Nov 29, 2012 at 11:44 AM,
Praveen Jain 
wrote:





 

Hi

 I am building my project using maven,

I have some german character in my validation-global.xml

When I build it they got converted to some garbage value in
validation.xml.

 

If I add 
in validation-global.xml , then after build german character placed as it is in
validation.xml.

But in validation.xml  after  I
have again   which violets
the XML structure and it doesnot work.

 

Please assist

 

 

Thanks

Warm Regards,

Praveen Jain

 


Praveen Jain | 020-66563094
Prime Sourcing, Oracle Financial Services, Oracle Park,
Pune, India

 

 







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.or

Re: No compile errors with plexus-compiler-eclipse

2012-12-04 Thread Olivier Lamy
2012/12/4 Peter Palmreuther :
> Hello Olivier,
>
> Am 03.12.2012 um 10:52 schrieb Olivier Lamy :
>
>> 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 was able to get maven-compiler-plugin:3.1-SNAPSHOT from Apache snapshot 
> repository.
> Sadly I can't find plexus-compiler-*:2.1-SNAPSHOT.
> I've set my Nexus to proxy 
> https://nexus.codehaus.org/content/repositories/snapshots/, but that seems to 
> be the wrong location.
> Can you point me to the correct repository?

Use: https://oss.sonatype.org/content/repositories/plexus-snapshots

> --
> Thanks in advance,
> and best regards,
>
> Peter
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org