Re: Plans to release Maven 3.0

[Brett Porter]

Most are seeing it in the other direction.

Are you able to reproduce it on a sample project you can post? Or is there 
anything distinctive about the build that is slower? Do you notice where it 
spends most of its time?

- Brett

On 10/09/2010, at 11:49 PM, Tim wrote:

> I've been using m3 for a while now but just switched over to beta 3.
> This version is vastly more stable than the previous versions
> (seemingly obvious statement :))
> But it is definitely slower than version 2x.
> I'm seeing a consistent ~10-20% increase in build times (a 50 second
> build increased to a minute etc)
> When I run it with -T 2 or -T 1c (on 2 core MBP) I am able to get back
> that build time increase but not gain any.
> I have not tried it with maven shell in this version.
> Anyone else seeing the same thing?
> 
> On Wed, Sep 8, 2010 at 8:49 AM, Brian Fox  wrote:
>> On the dev list we've been discussing more formal plans to drive to
>> the Maven 3.0 final release. The plan is to release weekly release
>> candidate releases with the goal of having 3.0 final by the beginning
>> of October. So far Maven 3.0 beta 3 is pretty stable with only a
>> couple of regressions identified. We need your help to determine what
>> else needs to be fixed before the final release. So if you haven't
>> yet, we would like you to grab the latest 3.x build and give us your
>> feedback. You can find the download link here:
>> http://maven.apache.org/download.html
>> 
>> 
>> --Brian
>> Apache Maven PMC Chair
>> 
>> -
>> 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
> 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/





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

Re: ScriptRunner exception when calling Rhino script in Ant build from maven antrun plugin

[Jacob Beard]

Hi Armin,

I believe that that is what the ant-nodeps Maven package is for: ant
with all of the dependencies included into one package. It seems that
if I were able to get this package to install correctly, then the
other problem may be resolved as well.

Do you have any idea as to why a fatal error is being thrown when
ant-nodeps is added to the antrun plugin dependencies, or how to
understand the stack produced by this error?

Please let me know. Thanks,

Jake

On Thu, Sep 9, 2010 at 4:43 AM, Armin Ehrenfels
 wrote:
> Hi Jacob,
>
>  you can see from the error message that an optional ant functionality is
> missing. Now, you have to find the ant-xxx.jar that contains this class and
> add it to ant-run's dependencies.
>
> HTH
>
> Armin
>
> Am 09.09.2010 05:09, schrieb Jacob Beard:
>>
>> Hi,
>>
>> It actually seems that including the Bean Scripting Framework as a
>> dependency is causing the problems. Consider the following reduced
>> example. The following succeeds:
>>
>>
>>  
>>    
>>       
>>         maven-antrun-plugin
>>         1.4
>>         
>>           
>>        test
>>             initialize
>>             
>>               
>>                Hello world!
>>                
>>                        x=0;
>>                
>>                Hello world 2!
>>               
>>             
>>             
>>               run
>>             
>>           
>>         
>>        
>>                
>>                
>>                        rhino
>>                        js
>>                        1.7R2
>>                
>>        
>>       
>>    
>>  
>>
>>
>> And produces the following output:
>>
>>
>>      [echo] Hello world!
>>      [echo] Hello world 2!
>>
>>
>> But when the bsf plugin dependency is turned on, the script tag throws
>> the ClassNotFoundException with ScriptRunner:
>>
>>
>>  
>>    
>>       
>>         maven-antrun-plugin
>>         1.4
>>         
>>           
>>        test
>>             initialize
>>             
>>               
>>                Hello world!
>>                
>>                        x=0;
>>                
>>                Hello world 2!
>>               
>>             
>>             
>>               run
>>             
>>           
>>         
>>        
>>                
>>                        bsf
>>                        bsf
>>                        2.4.0
>>                
>>                
>>                        rhino
>>                        js
>>                        1.7R2
>>                
>>        
>>       
>>    
>>  
>>
>>
>> [INFO] Executing tasks
>>      [echo] Hello world!
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] An Ant BuildException has occured:
>> java.lang.ClassNotFoundException:
>> org.apache.tools.ant.util.optional.ScriptRunner
>>
>>
>> I tried ant-nodeps as well, but adding that dependency produced a very
>> unusual error:
>>
>>
>> [INFO] [antrun:run {execution: test}]
>> [FATAL ERROR] org.apache.maven.plugin.antrun.AntRunMojo#execute()
>> caused a linkage error (java.lang.NoSuchMethodError) and may be
>> out-of-date. Check the realms:
>> [FATAL ERROR] Plugin realm =
>> app0.child-container[org.apache.maven.plugins:maven-antrun-plugin:1.4]
>> urls[0] =
>> file:/home/jacob/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.4/maven-antrun-plugin-1.4.jar
>> urls[1] = file:/home/jacob/.m2/repository/rhino/js/1.7R2/js-1.7R2.jar
>> urls[2] =
>> file:/home/jacob/.m2/repository/ant/ant-nodeps/1.6.5/ant-nodeps-1.6.5.jar
>> urls[3] =
>> file:/home/jacob/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
>> urls[4] =
>> file:/home/jacob/.m2/repository/org/apache/ant/ant-nodeps/1.8.1/ant-nodeps-1.8.1.jar
>> urls[5] =
>> file:/home/jacob/.m2/repository/org/apache/ant/ant/1.8.1/ant-1.8.1.jar
>> urls[6] =
>> file:/home/jacob/.m2/repository/org/apache/ant/ant-launcher/1.8.1/ant-launcher-1.8.1.jar
>> [FATAL ERROR] Container realm = plexus.core
>> urls[0] = file:/usr/share/maven2/lib/maven-debian-uber.jar
>> [INFO]
>> 
>> [ERROR] FATAL ERROR
>> [INFO]
>> 
>> [INFO]
>> org.apache.tools.ant.launch.Locator.fromJarURI(Ljava/lang/String;)Ljava/lang/String;
>> [INFO]
>> 
>> [INFO] Trace
>> java.lang.NoSuchMethodError:
>>
>> org.apache.tools.ant.launch.Locator.fromJarURI(Ljava/lang/String;)Ljava/lang/String;
>>         at
>> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:274)
>>         at
>> org.apache.tools.ant.helper.ProjectHelper2.parseUnknownElement(ProjectHelper2.java:130)
>>         at
>> org.apache.tools.ant.helper.ProjectHelper2.parseAntlibDescriptor(ProjectHelper2.java:110)
>>        

Re: maven-gpg-plugin blocked during the execution

[Simone Tripodi]

Hi Marshall,
thanks a lot for your hints, very appreciated!
Have a nice day,
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Fri, Sep 10, 2010 at 9:41 PM, Marshall Schor  wrote:
>  Another approach is to install a version of the underlying gpg which includes
> support for an agent.
>
> Then, when gpg needs to get your pass phrase, it asks the agent.  The agent 
> pops
> up an interactive window, and gets your pass phrase, right when it needs it.  
> It
> then keeps it around for a few minutes, in case you're running things which
> which need lots of signings, so it doesn't bother you for the pass phrase all
> the time.
>
> To activate this capability in your maven settings file, you add
>
> true
>
> -Marshall Schor
>
>
>
> On 9/10/2010 1:29 PM, Simone Tripodi wrote:
>> Hi Kalle,
>> thanks a lot for your help, very appreciated.
>> Have a nice day,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Sep 10, 2010 at 7:06 PM, Kalle Korhonen
>>  wrote:
>>> You need to specify:
>>> forked-path
>>> in release plugin configuration. See http://jira.codehaus.org/browse/MGPG-9
>>>
>>> Kalle
>>>
>>>
>>> On Fri, Sep 10, 2010 at 9:30 AM, Simone Tripodi
>>>  wrote:
 Hi all guys,
 using the maven-release-plugin and signing artifacts with GnuPG,
 during the verifying phase, when the gpg-plugin is invoked, the build
 process is completely stalled. If I don't pass the gpg.passphare I'd
 expect it would be asked in the prompt, but it doesn't happen :(
 Follow below my attempts:

 mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
 -Dgpg.passphrase=
 mvn release:prepare -DdryRun=true -Dgpg.passphrase= -PXXX (the
 keyname is defined as property in the XXX profile)
 mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the 
 prompt)

 Do you have any idea why? Many thanks in advance,
 Simo

 http://people.apache.org/~simonetripodi/
 http://www.99soft.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: maven-gpg-plugin blocked during the execution

[Marshall Schor]

 Another approach is to install a version of the underlying gpg which includes
support for an agent.

Then, when gpg needs to get your pass phrase, it asks the agent.  The agent pops
up an interactive window, and gets your pass phrase, right when it needs it.  It
then keeps it around for a few minutes, in case you're running things which
which need lots of signings, so it doesn't bother you for the pass phrase all
the time.

To activate this capability in your maven settings file, you add

true

-Marshall Schor



On 9/10/2010 1:29 PM, Simone Tripodi wrote:
> Hi Kalle,
> thanks a lot for your help, very appreciated.
> Have a nice day,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Fri, Sep 10, 2010 at 7:06 PM, Kalle Korhonen
>  wrote:
>> You need to specify:
>> forked-path
>> in release plugin configuration. See http://jira.codehaus.org/browse/MGPG-9
>>
>> Kalle
>>
>>
>> On Fri, Sep 10, 2010 at 9:30 AM, Simone Tripodi
>>  wrote:
>>> Hi all guys,
>>> using the maven-release-plugin and signing artifacts with GnuPG,
>>> during the verifying phase, when the gpg-plugin is invoked, the build
>>> process is completely stalled. If I don't pass the gpg.passphare I'd
>>> expect it would be asked in the prompt, but it doesn't happen :(
>>> Follow below my attempts:
>>>
>>> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
>>> -Dgpg.passphrase=
>>> mvn release:prepare -DdryRun=true -Dgpg.passphrase= -PXXX (the
>>> keyname is defined as property in the XXX profile)
>>> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the 
>>> prompt)
>>>
>>> Do you have any idea why? Many thanks in advance,
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.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: maven-gpg-plugin blocked during the execution

[Simone Tripodi]

Hi Kalle,
thanks a lot for your help, very appreciated.
Have a nice day,
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Fri, Sep 10, 2010 at 7:06 PM, Kalle Korhonen
 wrote:
> You need to specify:
> forked-path
> in release plugin configuration. See http://jira.codehaus.org/browse/MGPG-9
>
> Kalle
>
>
> On Fri, Sep 10, 2010 at 9:30 AM, Simone Tripodi
>  wrote:
>> Hi all guys,
>> using the maven-release-plugin and signing artifacts with GnuPG,
>> during the verifying phase, when the gpg-plugin is invoked, the build
>> process is completely stalled. If I don't pass the gpg.passphare I'd
>> expect it would be asked in the prompt, but it doesn't happen :(
>> Follow below my attempts:
>>
>> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
>> -Dgpg.passphrase=
>> mvn release:prepare -DdryRun=true -Dgpg.passphrase= -PXXX (the
>> keyname is defined as property in the XXX profile)
>> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the 
>> prompt)
>>
>> Do you have any idea why? Many thanks in advance,
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.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

How to skip cobertura report for single module?

[David Hoffer]

I'm using the cobertura-maven-plugin to generate code coverage reports
during site builds, but it always fails on one module of a large
multi-module project/build.  How can I skip the cobertura report for
the one module?  (The problem module is auto generated code so it
doesn't need this anyway.)

Thanks,
-Dave

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

Re: maven-gpg-plugin blocked during the execution

[Kalle Korhonen]

You need to specify:
forked-path
in release plugin configuration. See http://jira.codehaus.org/browse/MGPG-9

Kalle


On Fri, Sep 10, 2010 at 9:30 AM, Simone Tripodi
 wrote:
> Hi all guys,
> using the maven-release-plugin and signing artifacts with GnuPG,
> during the verifying phase, when the gpg-plugin is invoked, the build
> process is completely stalled. If I don't pass the gpg.passphare I'd
> expect it would be asked in the prompt, but it doesn't happen :(
> Follow below my attempts:
>
> mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
> -Dgpg.passphrase=
> mvn release:prepare -DdryRun=true -Dgpg.passphrase= -PXXX (the
> keyname is defined as property in the XXX profile)
> mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the 
> prompt)
>
> Do you have any idea why? Many thanks in advance,
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.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

maven-gpg-plugin blocked during the execution

[Simone Tripodi]

Hi all guys,
using the maven-release-plugin and signing artifacts with GnuPG,
during the verifying phase, when the gpg-plugin is invoked, the build
process is completely stalled. If I don't pass the gpg.passphare I'd
expect it would be asked in the prompt, but it doesn't happen :(
Follow below my attempts:

mvn release:prepare -DdryRun=true -Darguments=-Dgpg.keyname=\
-Dgpg.passphrase=
mvn release:prepare -DdryRun=true -Dgpg.passphrase= -PXXX (the
keyname is defined as property in the XXX profile)
mvn release:prepare -DdryRun=true (tried to insert gpg.passphrase in the prompt)

Do you have any idea why? Many thanks in advance,
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/

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

Re: RE: Maven *.ear build for SAP Web AS

[Wayne Fay]

>  Here´s some more detailed information, where the same problem has
> appeared:
>
> http://forums.sdn.sap.com/message.jspa?messageID=4753421

I've run into this with SAP Web AS (among with a great number of other
"issues" in wars and ears that otherwise deploy with zero issues on
all the other major app servers in the market) and all I can say is...
don't use SAP Web AS unless you have a lot of time and patience to
deal with these kinds of problems manually.

Wayne

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

RE: Issue with help:effective-pom

[Ken Beal]

Great, thanks Ron (sorry for delay in response, my Inbox rules need a
little assist as this dropped to the folder).
--
Ken Beal
Senior Software Engineer, Build/Release

Cross Country Automotive Services
One Cabot Road
Medford, MA 02155
p: (781) 306-3605
m: (978) 423-8977
e: kb...@crosscountry-auto.com


-Original Message-
From: GALLAGHER, RON (ATTSI) [mailto:rg7...@att.com] 
Sent: Tuesday, September 07, 2010 3:36 PM
To: Maven Users List
Subject: RE: Issue with help:effective-pom

Ken,

The default packaging type is "jar" [1].  If the the "packaging" entry
is missing from the output of "help:effective-pom", then you can safely
assume that the packaging is "jar".

[1]
http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_project

Ron Gallagher

-Original Message-
From: Ken Beal [mailto:kb...@crosscountry-auto.com] 
Sent: Tuesday, September 07, 2010 11:50 AM
To: users@maven.apache.org
Subject: Issue with help:effective-pom

Hi,

 

We have a POM.XML file which has a  element in it.

 

When I run "mvn help:effective-pom > effective-pom.txt" and then open
the resulting file, the  element is missing.

 

I'm fairly new to this so I might be overlooking something.  Is this the
expected behavior?

 

In searching I found this page
(http://www.avajava.com/tutorials/lessons/how-do-i-display-the-effective
-pom-of-a-project.html), which shows an example of processing a pom and
the example shows (but doesn't point out) that the  element
is present in the original POM.XML, and missing in the output from "mvn
help:effective-pom"-which does seem to support that this is the expected
behavior, but I figured I'd ask anyway.

 

 

(Background: we're automating Maven builds, and I'm working on a way of
determining all the output files that will be produced by a particular
POM.XML, so we can automate adding builds to the automation.  My (again,
limited) understanding was that the  element determines the
output type, and we produced automation that worked against a parent
POM; but when pointed at a POM that doesn't have any children, the
 element is stripped.  As a workaround I'll add code saying
"if no  element, and this is a child-less POM, read in the
POM itself and extract the  element, then continue
processing."  Critique of this approach would also be appreciated-there
may be an easier way of doing this.)

 

Thanks,

--
Ken Beal
Senior Software Engineer, Build/Release

Cross Country Automotive Services
One Cabot Road
Medford, MA 02155
p: (781) 306-3605
m: (978) 423-8977
e: kb...@crosscountry-auto.com  


Confidentiality Note: This e-mail message and any attachments may
contain 
confidential or privileged information. If you are not the intended
recipient, 
please notify me immediately by replying to this message and destroy all

copies of this message and any attachments. Thank you.

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


Confidentiality Note: This e-mail message and any attachments may contain 
confidential or privileged information. If you are not the intended recipient, 
please notify me immediately by replying to this message and destroy all 
copies of this message and any attachments. Thank you.

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

Re: Plans to release Maven 3.0

[Tim]

I've been using m3 for a while now but just switched over to beta 3.
This version is vastly more stable than the previous versions
(seemingly obvious statement :))
But it is definitely slower than version 2x.
I'm seeing a consistent ~10-20% increase in build times (a 50 second
build increased to a minute etc)
When I run it with -T 2 or -T 1c (on 2 core MBP) I am able to get back
that build time increase but not gain any.
I have not tried it with maven shell in this version.
Anyone else seeing the same thing?

On Wed, Sep 8, 2010 at 8:49 AM, Brian Fox  wrote:
> On the dev list we've been discussing more formal plans to drive to
> the Maven 3.0 final release. The plan is to release weekly release
> candidate releases with the goal of having 3.0 final by the beginning
> of October. So far Maven 3.0 beta 3 is pretty stable with only a
> couple of regressions identified. We need your help to determine what
> else needs to be fixed before the final release. So if you haven't
> yet, we would like you to grab the latest 3.x build and give us your
> feedback. You can find the download link here:
> http://maven.apache.org/download.html
>
>
> --Brian
> Apache Maven PMC Chair
>
> -
> 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

Antwort: RE: Maven *.ear build for SAP Web AS

[torsten . reinhard]

Hi, 

at first thanx to all replies until now!

 Here´s some more detailed information, where the same problem has 
appeared:

http://forums.sdn.sap.com/message.jspa?messageID=4753421

In our environment we see:

com.sap.engine.services.library_container.deploy.LCDeploymentException: 
[ERROR CODE DPL.LIB.103] Class-path entry jaxb-api.jar specified in 
/usr/sap/GZG/J00/j2ee/cluster/server0/temp/deploy/kvkams-ear-SAP.ear1283962052624/lib/jaxb-impl-2.1.9.jar/META-INF/MANIFEST.MF
 
file cannot be resolved.] 

Thanx, Torsten
 



Martin Gainty  
10.09.2010 12:54
Bitte antworten an
"Maven Users List" 


An

Kopie

Thema
RE: Maven *.ear build for SAP Web AS







can you display the error you see when Application Server encounters 
Version-specific jars jaxp-api-VERSION.jar jax-qname-VERSION.jar 
activation-VERSION.jar servlet-VERSION.jar
does your filesystem accept alpha, dash and numeric characters in jar 
filename?
 
gruss
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene 
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte 
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht 
dient lediglich dem Austausch von Informationen und entfaltet keine 
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von 
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
 

> To: users@maven.apache.org
> Subject: Maven *.ear build for SAP Web AS
> From: torsten.reinh...@gi-de.com
> Date: Fri, 10 Sep 2010 08:57:24 +0200
> 
> Hi, 
> 
> actually we´re trying to get our *.ear built by Maven to be deployable 
und 
> executable on SAP Web Application Server.
> 
> We run into problems, caused by a classpath in (for example)
> 
> javax.xml.soap
> saaj-api
> 1.3
> 
> This jar has a MANIFEST.MF containing
> 
> Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
> 
> The application server is complaining about this classpath because Maven 

> puts the *.jars with their version names into it, 
> that means jaxp-api-1.4.jar (for example)
> 
> => Is there a way to come around this? Do I have to customize all my 
> module filenames?
> 
> Torsten 
> 
  

RE: Custom execution steps when no lifecycle given

[Martin Gainty]

when you declare the plugin in your plugins group you can either associate your 
plugin with the desired lifecycle phase ..
in the first case the plugin goal of goal1 is tied to the validate phase
when execution is not tied to a specific phase goal2 is executed  e.g.
 
   
  
org.apache.maven.plugins
maven-antrun-plugin
false


first

goal1

validate


second

goal2




http://www.avajava.com/tutorials/lessons/how-do-i-specify-the-phase-of-a-lifecycle-in-a-mojo.html
HTH
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.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: Fri, 10 Sep 2010 11:07:23 +
> Subject: Custom execution steps when no lifecycle given
> From: anis...@gmail.com
> To: users@maven.apache.org
> 
> Hello All,
> 
> I am a relatively new user to maven so please bear with me. I am using the 
> maven-release-plugin and as part of the release:prepare goal i want to run 
> some custom ant code. Can some one please help me how to do this? I found 
> the maven-ant plugin but it requires a  to add custom ant execution 
> steps, the release plugin has no such phase ?
> 
> Thanks
> Anishek
  

Re: Custom execution steps when no lifecycle given

[Anders Hammar]

Possibly you could use the preparationGoals parameter:
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals

However, as you're new to Maven, it would so much better if you told us what
you want to do and we would be able to tell you have to do it. Doing what
you're explaining is most likely not the correct Maven way.

/Anders

On Fri, Sep 10, 2010 at 13:07,  wrote:

> Hello All,
>
> I am a relatively new user to maven so please bear with me. I am using the
> maven-release-plugin and as part of the release:prepare goal i want to run
> some custom ant code. Can some one please help me how to do this? I found
> the maven-ant plugin but it requires a  to add custom ant execution
> steps, the release plugin has no such phase ?
>
> Thanks
> Anishek
>

Re: How to contact uploader to maven central of org.eclipse.core artifacts

[Marshall Schor]

On 9/9/2010 11:59 AM, Brian Fox wrote:
> This should be fixed now.

I just now went to maven central, and looked up this example, and see it is just
the same as before.  (I even tried clearing all the settings out of an extra
browser I use occasionally, to insure nothing was being "cached").

So I'm confused - it seems to me it is not fixed?  What (if anything) changed?

-Marshall Schor
> On Tue, Sep 7, 2010 at 12:27 PM, Marshall Schor  wrote:
>>  Today, Maven central was updated with incomplete uploads of several eclipse
>> artifacts:
>>
>> see http://repo2.maven.org/maven2/org/eclipse/core
>>
>> and within that directory are the following subdirectories:
>>
>> org.eclipse.core.contenttype/  07-Sep-2010 06:27
>> org.eclipse.core.expressions/  07-Sep-2010 06:27
>> org.eclipse.core.filesystem/   07-Sep-2010 06:27
>> org.eclipse.core.jobs/ 07-Sep-2010 06:27
>> org.eclipse.core.resources/07-Sep-2010 06:27
>> org.eclipse.core.runtime/  07-Sep-2010 06:27
>> org.eclipse.core.runtime.compatibility.auth/   07-Sep-2010 06:27
>> org.eclipse.core.variables/07-Sep-2010 06:27
>>
>> Each of these directories has just the maven-metadata.xml file (plus 
>> checksums),
>> but no poms, etc.  Here's a sample:
>>
>> maven-metadata.xml 03-Sep-2010 12:30
>> maven-metadata.xml.md5 03-Sep-2010 12:30
>> maven-metadata.xml.sha103-Sep-2010 12:30
>>
>> Is this a failure to complete an upload to central?
>>
>> Should someone be contacted to fix this (and if so, who?)?
>>
>> -Marshall Schor
>>
>> -
>> 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

Custom execution steps when no lifecycle given

[anishek]

Hello All,

I am a relatively new user to maven so please bear with me. I am using the  
maven-release-plugin and as part of the release:prepare goal i want to run  
some custom ant code. Can some one please help me how to do this? I found  
the maven-ant plugin but it requires a  to add custom ant execution  
steps, the release plugin has no such phase ?


Thanks
Anishek

RE: Maven *.ear build for SAP Web AS

[Martin Gainty]

can you display the error you see when Application Server encounters 
Version-specific jars jaxp-api-VERSION.jar jax-qname-VERSION.jar 
activation-VERSION.jar servlet-VERSION.jar
does your filesystem accept alpha, dash and numeric characters in jar filename?
 
gruss
Martin 
__ 
Verzicht und Vertraulichkeitanmerkung

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
 

> To: users@maven.apache.org
> Subject: Maven *.ear build for SAP Web AS
> From: torsten.reinh...@gi-de.com
> Date: Fri, 10 Sep 2010 08:57:24 +0200
> 
> Hi, 
> 
> actually we´re trying to get our *.ear built by Maven to be deployable und 
> executable on SAP Web Application Server.
> 
> We run into problems, caused by a classpath in (for example)
> 
> javax.xml.soap
> saaj-api
> 1.3
> 
> This jar has a MANIFEST.MF containing
> 
> Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
> 
> The application server is complaining about this classpath because Maven 
> puts the *.jars with their version names into it, 
> that means jaxp-api-1.4.jar (for example)
> 
> => Is there a way to come around this? Do I have to customize all my 
> module filenames?
> 
> Torsten 
> 
  

Re: Maven *.ear build for SAP Web AS

[João Ferreira]

I think this is his problem...
http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mapping.html

The ear plugin also has the same option(fileNameMapping) I think:
http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html

2010/9/10 Anders Hammar :
> No, I believe his problem is that the jar file names in the manifest of that
> jar doesn't match with the actual jar file names on the app server. Not sure
> how to fix this other than patch the saaj-api.jar.
>
> However, I'm somewhat surprised that the app server complains about this as
> I don't think that the classpath in the manifest should be used for Java EE.
> However, I could be wrong...
>
> /Anders
>
> On Fri, Sep 10, 2010 at 09:19, per-henrik hedman  wrote:
>
>> If I understand you correctly, you are building ear-file and you want
>> to remove certain jars from that ear?
>>
>> You could do that by:
>>
>> 
>> javax.xml.soap
>> saaj-api
>> 1.3
>> 
>>        
>>          {groupId for jaxp-api}
>>          jaxp-api.jar
>>          1.4
>>        
>> 
>> 
>>
>> Cheers,
>> Per-Henrik
>>
>> Don't thi
>> On Fri, Sep 10, 2010 at 8:57 AM,   wrote:
>> > Hi,
>> >
>> > actually we´re trying to get our *.ear built by Maven to be deployable
>> und
>> > executable on SAP Web Application Server.
>> >
>> > We run into problems, caused by a classpath in (for example)
>> >
>> > javax.xml.soap
>> > saaj-api
>> > 1.3
>> >
>> > This jar has a MANIFEST.MF containing
>> >
>> > Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
>> >
>> > The application server is complaining about this classpath because Maven
>> > puts the *.jars with their version names into it,
>> > that means jaxp-api-1.4.jar (for example)
>> >
>> > => Is there a way to come around this? Do I have to customize all my
>> > module filenames?
>> >
>> > Torsten
>> >
>> >
>>
>> -
>> 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 fail Maven build when exec started Ant build fails? [SOLVED]

[NickDeGraeve]

Brian Fox-3 wrote:
> you could use the enforcer to check for the existence of certain files
> produced by that build.
It may not be the cleanest solution but at least it works. Thanks.
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-fail-Maven-build-when-exec-started-Ant-build-fails-tp2827248p2834669.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: Maven *.ear build for SAP Web AS

[Anders Hammar]

No, I believe his problem is that the jar file names in the manifest of that
jar doesn't match with the actual jar file names on the app server. Not sure
how to fix this other than patch the saaj-api.jar.

However, I'm somewhat surprised that the app server complains about this as
I don't think that the classpath in the manifest should be used for Java EE.
However, I could be wrong...

/Anders

On Fri, Sep 10, 2010 at 09:19, per-henrik hedman  wrote:

> If I understand you correctly, you are building ear-file and you want
> to remove certain jars from that ear?
>
> You could do that by:
>
> 
> javax.xml.soap
> saaj-api
> 1.3
> 
>
>  {groupId for jaxp-api}
>  jaxp-api.jar
>  1.4
>
> 
> 
>
> Cheers,
> Per-Henrik
>
> Don't thi
> On Fri, Sep 10, 2010 at 8:57 AM,   wrote:
> > Hi,
> >
> > actually we´re trying to get our *.ear built by Maven to be deployable
> und
> > executable on SAP Web Application Server.
> >
> > We run into problems, caused by a classpath in (for example)
> >
> > javax.xml.soap
> > saaj-api
> > 1.3
> >
> > This jar has a MANIFEST.MF containing
> >
> > Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
> >
> > The application server is complaining about this classpath because Maven
> > puts the *.jars with their version names into it,
> > that means jaxp-api-1.4.jar (for example)
> >
> > => Is there a way to come around this? Do I have to customize all my
> > module filenames?
> >
> > Torsten
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Maven *.ear build for SAP Web AS

[per-henrik hedman]

If I understand you correctly, you are building ear-file and you want
to remove certain jars from that ear?

You could do that by:


javax.xml.soap
saaj-api
1.3


  {groupId for jaxp-api}
  jaxp-api.jar
  1.4




Cheers,
Per-Henrik

Don't thi
On Fri, Sep 10, 2010 at 8:57 AM,   wrote:
> Hi,
>
> actually we´re trying to get our *.ear built by Maven to be deployable und
> executable on SAP Web Application Server.
>
> We run into problems, caused by a classpath in (for example)
>
> javax.xml.soap
> saaj-api
> 1.3
>
> This jar has a MANIFEST.MF containing
>
> Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar
>
> The application server is complaining about this classpath because Maven
> puts the *.jars with their version names into it,
> that means jaxp-api-1.4.jar (for example)
>
> => Is there a way to come around this? Do I have to customize all my
> module filenames?
>
> Torsten
>
>

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