maven-kodo-plugin-4.0.0-EA2 ISSUE

[Chandramohan Balkrishna Sawant]

Hi All,

We are using maven 1.0.2 & upgrading kodo 4.0.1 to 4.1.4.

For running kodo:enhance goal, we are using maven-kodo-plugin-4.0.0-EA2 but I 
guess this plugin supports only kodo 4.0.1 & not 4.1.4 because If I run this 
goal then it gives the error like -

kodo:init:

kodo:enhance:
[echo] JDO-enhancing classes for Kodo
[java] Exception in thread "Main Thread" java.lang.ClassCastException: 
kodo.jdo.JDOMetaDataFactory
[java]  at 
kodo.conf.KodoConfigurationImpl.newMetaDataFactoryInstance(KodoConfigurationImpl.java:1117)
[java]  at 
kodo.meta.MetaDataRepository.(MetaDataRepository.java:112)
[java]  at kodo.enhance.PCEnhancer.run(PCEnhancer.java:3774)
[java]  at kodo.enhance.PCEnhancer.run(PCEnhancer.java:3754)
[java]  at kodo.enhance.PCEnhancer.main(PCEnhancer.java:3720)

So could you please tell me is there any new plugin released for running 
kodo:enhance on kodo 4.1.4.

Warm Regards,
Chandramohan Sawant
Infosys Technologies Ltd
PUNE, INDIA
Direct : +91 20 4023 5756
Mobile: +91 9923330445




 CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not 
to copy, disclose, or distribute this e-mail or its contents to any other 
person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken 
every reasonable precaution to minimize this risk, but is not liable for any 
damage 
you may sustain as a result of any virus in this e-mail. You should carry out 
your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***

RE: [ANN] Maven 2.2.0 Released

[Mark Struberg]

If it still doesn't work yet, the mirror I've been using was

http://www.eu.apache.org/dist/maven/binaries/apache-maven-2.2.0-bin.tar.gz

LieGrue,
strub

--- Jason Chaffee  schrieb am Mi, 1.7.2009:

> Von: Jason Chaffee 
> Betreff: RE: [ANN] Maven 2.2.0 Released
> An: "Maven Users List" 
> Datum: Mittwoch, 1. Juli 2009, 1:35
> I tried all the mirror links that
> were provided on that page and none of them worked for me so
> I thought there might be something else going on.
> 
> I will try again later.  
> 
> Thanks.
> 
> -Original Message-
> From: Mark Struberg [mailto:strub...@yahoo.de]
> 
> Sent: Tuesday, June 30, 2009 4:29 PM
> To: Maven Users List
> Subject: RE: [ANN] Maven 2.2.0 Released
> 
> 
> Works for me.
> 
> Sometimes it takes a bit for all mirrors to get synced.
> Please try it again in a a few hours.
> 
> LieGrue,
> strub
> 
> --- Jason Chaffee 
> schrieb am Mi, 1.7.2009:
> 
> > Von: Jason Chaffee 
> > Betreff: RE: [ANN] Maven 2.2.0 Released
> > An: "Maven Users List" ,
> "annou...@maven.apache.org"
> 
> > Datum: Mittwoch, 1. Juli 2009, 1:04
> > I have not been able to download this
> > release.  It seems the artifact(s) are not at the
> > specified URL. 
> > 
> > -Original Message-
> > From: John Casey [mailto:jdca...@apache.org]
> > 
> > Sent: Tuesday, June 30, 2009 3:21 PM
> > To: annou...@maven.apache.org;
> > Maven Users List
> > Subject: [ANN] Maven 2.2.0 Released
> > 
> > The Maven team is pleased to announce the release of
> the
> > Maven 2.2.0.
> > 
> > Maven is a software project management and
> comprehension
> > tool. It offers
> > users the ability to build project binaries, generate
> a
> > project website,
> > and more.
> > 
> > http://maven.apache.org/
> > 
> > 
> > Release Notes - Maven 2 - Version 2.2.0
> > 
> > ** Sub-task
> >      * [MNG-4144] - document escape
> > character for curly braces in
> > clear-text passwords for settings.xml password
> security
> >      * [MNG-4145] - switch to released
> > versions of plexus-sec-dispatcher
> > (and by ext. plexus-cipher) once they're available
> > 
> > ** Bug
> >      * [MNG-2258] - Wrong execution
> > order of plugins in same phase
> >      * [MNG-3401] - Plugin parameters
> > must be specified outside an
> > execution block when they are invoked from the
> command
> > line
> >      * [MNG-3553] - cannot resolve
> > dependency with scope import
> >      * [MNG-3776] - Namespace
> > misspelled in settings.xml
> >      * [MNG-4074] - cyclic reference
> > with 2.1.0-RC1 that doesn't occur
> > with 2.0.10
> >      * [MNG-4082] - Encryption is
> > triggered if passwords merely contain
> > curly braces
> >      * [MNG-4126] - [regression]
> > Properties defined in profiles.xml of
> > parent are not inherited during multimodule build
> >      * [MNG-4137] - NPE in
> > DefaultLIfecycleExecutor when run from within
> > Hudson builds
> >      * [MNG-4140] - Properties
> > incorrectly replaced in pom
> >      * [MNG-4146] - password security
> > doesn't work with custom password
> > providers
> >      * [MNG-4147] - very long passwords
> > cause LightweightHTTP wagon to
> > line-wrap the Base64-encoded Authorization header
> >      * [MNG-4165] - http session
> > cookies rejected with non-lightweight
> > http wagon (maybe with lightweight one too)
> >      * [MNG-4166] - Problem parsing
> > command-line options in release:perform
> >      * [MNG-4167] - version-expression
> > transformation interferes with
> > plugins like GPG
> >      * [MNG-4168] - String index out of
> > range: 43807
> >      * [MNG-4179] - [regression]
> > Artifact download hangs upon transfer
> > failure
> >      * [MNG-4184] - [regression]
> > maven2.1 fails with cyclic dependency
> > in case of extension/dependency for report-plugin to
> > reactor-project
> >      * [MNG-4207] - Plugins that use
> > ArtifactResolver with http
> > repositories AND depend on log4j run into
> > ExceptionInInitializerError
> >      * [MNG-4213] - preemptive auth in
> > non-lightweight http wagon causes
> > Unauthorized responses from some servers
> >      * [MNG-4219] - update plexus-utils
> > to avoid leaking processes in
> > CommandLineUtils.getSystemEnvars()
> > 
> > ** Improvement
> >      * [MNG-2979] - Cross module
> > dependencies for multi-module site
> >      * [MNG-3203] - maven should
> > execute compiler:compile and
> > :test-compile in separate executions, to allow
> separate
> > configuration
> >      * [MNG-3834] - Improve error
> > message when dependency with
> > classifier is missing version
> >      * [MNG-4210] - Remove log4j
> > configuration warning
> > 
> > 
> > ** Task
> >      * [MNG-4143] - Update Java
> > requirement to 1.5
> >      * [MNG-4169] - Remove invocation
> > of
> > maven-plugin-plugin:updatePluginRegistry from default
> > lifecycle bindings
> > 
> > 
> > ** Wish
> >      * [MNG-4139] - avoid the schema
> > location in generated
> > maven-metadata*.xml
> > 
> > 
> > Enjoy,
> > 
> > -The Maven team
> > 
> > 
> > -- 
> > John Casey
> 

Re: Build gets extra dependencies.

[Jörg Schaible]

David C. Hicks wrote at Mittwoch, 1. Juli 2009 00:18:

> I've got an automated build that runs on Hudson that is producing a WAR
> that cannot load and run.  It appears that it is picking up extra
> dependencies during the build process.  One of those is
> spring-2.0.6.jar.  I believe this is causing my load/run problem because
> the error I get is related to loading the Spring context.  My question
> is simply this...
> 
> Can anyone tell me why a Maven build would pick up extra dependencies if
> everything appears to be the same between two machines.  Same JDK, same
> version of Maven, same settings.xml in .m2, same build command ("mvn
> clean install").  Yet, the automated build ends up with 5 extra jars in
> the WEB-INF/lib directory.  I'm stumped, and this is causing us a world
> of problems.

The artifacts of your repository might have been loaded from different
repos. Repo at java.net and JBoss tend to have sometimes different POMs for
artifacts that are also available on Maven central or (at least java.net)
redeploys already released artifacts ;-/

Therefore ensure that you setup a mirror for anything in settings.xml and
use a proxy/archive manager with a well-defined sequence for the repos to
search for artifacts.

- Jörg


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

Re: bug? strange resolution of commons-logging dependency

[Jörg Schaible]

Lucas Bergman wrote at Dienstag, 30. Juni 2009 21:49:

> Dennis Lundberg wrote:
>> Lucas Bergman wrote:
>> > Running this test with Maven 2.1.0 fails:
>> >
>> >   java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
>> >   [ ... ]
>> >
>> > The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
>> > (compile-scope) dependency, so this seems wrong.  There seems to
>> > be some interaction between that POM and the dependent POMs.
>> > Indeed:
>> >
>> >   [ ... ]
>> >
>> >   2.  Adding an exclusion of commons-logging to the
>> >   hibernate-ehcache dependency causes the test to succeed.  I
>> >   tried this, because the hibernate-ehcache POM depends on
>> >   commons-logging version 99.0-does-not-exist, a rather famous
>> >   JBoss kludge[1].
>> >
>> > [ ... ]
>> >
>> > Footnotes:
>> > [1] 
>> >
[http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html
>>
>> That is your problem. What this does is mess the dependency-tree. It
>> removes commons-logging from the dependency tree because that
>> version "99.0-..." is larger than the latest current release of
>> commons-logging.  The "99.0-..." version should *never ever* reach
>> end users. It can *only* be used by internal project.
> 
> Thanks for the input.  Are you saying that the dependency of the
> hibernate-ehcache POM on commons-logging 99.0-does-not-exist is a bug?

It's an inappropriate solution for their problem with commons-logging.

> I'm sympathetic to that view, but I just want to be sure.  To be sure,
> it seems foolish for the Hibernate developers to put something like
> this in a library's POM, since it would seem to impose their kludge
> on the programmer using the library.

At least you should report this as a bug, since it actually breaks your
build. They should get at least aware or if.

> Of course, we fixed our particular problem by adding an 
> for commons-logging from our hibernate-ehcache dependency.

You can declare commons-logging in a dependency management section. This
version and scope will have precedence over any transitive dep.

- Jörg


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

Re: bug? strange resolution of commons-logging dependency

[Jörg Schaible]

Rusty Wright wrote at Mittwoch, 1. Juli 2009 00:15:

> This may be a dumb or inappropriate question, but why does Tomcat need
> commons logging?  Why can't it just use java util logging?

Who did mention Tomcat in this thread? And no, recent versions of Tomcat use
their own logging framework JULI which is based on JUL.

- Jörg


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

Maven kodo issue

[Chandramohan Balkrishna Sawant]

Hi Team,

I'm using KODO 4.1.4 & maven 1.0.2 so should I upgrade maven to the newer 
version for KODO enhancing goal, because when I'm executing enhance goal, am 
facing the error as - Exception in thread "Main Thread" 
java.lang.ClassCastException: kodo.jdo.JDOMetaDataFactory

If yes then tell me please that to which version we should upgrade maven.


Warm Regards,
Chandramohan Sawant
Infosys Technologies Ltd
PUNE, INDIA
Direct : +91 20 4023 5756
Mobile: +91 9923330445




 CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not 
to copy, disclose, or distribute this e-mail or its contents to any other 
person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken 
every reasonable precaution to minimize this risk, but is not liable for any 
damage 
you may sustain as a result of any virus in this e-mail. You should carry out 
your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***

release:perform fails with "The PluginDescriptor for [org.apache.maven.plugins:maven-javadoc-plugin] was not found"

[Ovidiu Feodorov]

After fixing release:prepare, the release process fails at 
"release:perform".


The interaction with the repository seem to go well, Maven fails after 
forking:


$ mvn release:perform
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Top Level Project Name
[INFO]   Sub-Module One
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 


[INFO] Building Top Level Project Name
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO] 


[INFO] [release:perform]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout 
svn+ssh://example.com/home/svn/server/repos/playground/tags/maven-release-experiment-1.0.1 
c:\work\playground\maven\release-plugin-experiments\target\checkout"
[INFO] Working directory: 
c:\work\playground\maven\release-plugin-experiments\target

[INFO] Executing goals 'clean install deploy'...
[WARNING] Maven will be executed in interactive mode, but no input 
stream has been configured for this MavenInvoker instance.

[INFO] [INFO] Scanning for projects...
[INFO] [INFO] Reactor build order:
[INFO] [INFO]   Top Level Project Name
[INFO] [INFO]   Sub-Module One
[INFO] [INFO] 


[INFO] [INFO] Building Top Level Project Name
[INFO] [INFO]task-segment: [clean, install, deploy]
[INFO] [INFO] 

[INFO] [INFO] 


[INFO] [ERROR] FATAL ERROR
[INFO] [INFO] 

[INFO] [INFO] The PluginDescriptor for the plugin Plugin 
[org.apache.maven.plugins:maven-javadoc-plugin] was not found.
[INFO] [INFO] 


[INFO] [INFO] Trace
[INFO] java.lang.IllegalStateException: The PluginDescriptor for the 
plugin Plugin [org.apache.maven.plugins:maven-javadoc-plugin] was not found.
[INFO]  at 
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325)
[INFO]  at 
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212)
[INFO]  at 
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
[INFO]  at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)

[INFO]  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
[INFO]  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
[INFO]  at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
[INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[INFO]  at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[INFO]  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

[INFO]  at java.lang.reflect.Method.invoke(Method.java:585)
[INFO]  at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

[INFO]  at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
[INFO]  at 
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

[INFO]  at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] [INFO] 


[INFO] [INFO] Total time: < 1 second
[INFO] [INFO] Finished at: Tue Jun 30 21:47:16 PDT 2009
[INFO] [INFO] Final Memory: 2M/4M
[INFO] [INFO] 

[INFO] 


[ERROR] BUILD ERROR
[INFO] 


[INFO] Maven execution failed, exit code: '1'


Any idea?

I found this: 
http://www.mail-archive.com/users@maven.apache.org/msg70197.html but 
those suggestions didn't help.


Cheers,
Ovidiu


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For add

Re: ConversionException

[mlavannis]

I ran a "maven clean" and that seems to have resolved this problem.
-- 
View this message in context: 
http://www.nabble.com/ConversionException-tp19730105p24283588.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: [ANN] Maven 2.2.0 Released

[Jason Chaffee]

I tried all the mirror links that were provided on that page and none of them 
worked for me so I thought there might be something else going on.

I will try again later.  

Thanks.

-Original Message-
From: Mark Struberg [mailto:strub...@yahoo.de] 
Sent: Tuesday, June 30, 2009 4:29 PM
To: Maven Users List
Subject: RE: [ANN] Maven 2.2.0 Released


Works for me.

Sometimes it takes a bit for all mirrors to get synced.
Please try it again in a a few hours.

LieGrue,
strub

--- Jason Chaffee  schrieb am Mi, 1.7.2009:

> Von: Jason Chaffee 
> Betreff: RE: [ANN] Maven 2.2.0 Released
> An: "Maven Users List" , "annou...@maven.apache.org" 
> 
> Datum: Mittwoch, 1. Juli 2009, 1:04
> I have not been able to download this
> release.  It seems the artifact(s) are not at the
> specified URL. 
> 
> -Original Message-
> From: John Casey [mailto:jdca...@apache.org]
> 
> Sent: Tuesday, June 30, 2009 3:21 PM
> To: annou...@maven.apache.org;
> Maven Users List
> Subject: [ANN] Maven 2.2.0 Released
> 
> The Maven team is pleased to announce the release of the
> Maven 2.2.0.
> 
> Maven is a software project management and comprehension
> tool. It offers
> users the ability to build project binaries, generate a
> project website,
> and more.
> 
> http://maven.apache.org/
> 
> 
> Release Notes - Maven 2 - Version 2.2.0
> 
> ** Sub-task
>      * [MNG-4144] - document escape
> character for curly braces in
> clear-text passwords for settings.xml password security
>      * [MNG-4145] - switch to released
> versions of plexus-sec-dispatcher
> (and by ext. plexus-cipher) once they're available
> 
> ** Bug
>      * [MNG-2258] - Wrong execution
> order of plugins in same phase
>      * [MNG-3401] - Plugin parameters
> must be specified outside an
> execution block when they are invoked from the command
> line
>      * [MNG-3553] - cannot resolve
> dependency with scope import
>      * [MNG-3776] - Namespace
> misspelled in settings.xml
>      * [MNG-4074] - cyclic reference
> with 2.1.0-RC1 that doesn't occur
> with 2.0.10
>      * [MNG-4082] - Encryption is
> triggered if passwords merely contain
> curly braces
>      * [MNG-4126] - [regression]
> Properties defined in profiles.xml of
> parent are not inherited during multimodule build
>      * [MNG-4137] - NPE in
> DefaultLIfecycleExecutor when run from within
> Hudson builds
>      * [MNG-4140] - Properties
> incorrectly replaced in pom
>      * [MNG-4146] - password security
> doesn't work with custom password
> providers
>      * [MNG-4147] - very long passwords
> cause LightweightHTTP wagon to
> line-wrap the Base64-encoded Authorization header
>      * [MNG-4165] - http session
> cookies rejected with non-lightweight
> http wagon (maybe with lightweight one too)
>      * [MNG-4166] - Problem parsing
> command-line options in release:perform
>      * [MNG-4167] - version-expression
> transformation interferes with
> plugins like GPG
>      * [MNG-4168] - String index out of
> range: 43807
>      * [MNG-4179] - [regression]
> Artifact download hangs upon transfer
> failure
>      * [MNG-4184] - [regression]
> maven2.1 fails with cyclic dependency
> in case of extension/dependency for report-plugin to
> reactor-project
>      * [MNG-4207] - Plugins that use
> ArtifactResolver with http
> repositories AND depend on log4j run into
> ExceptionInInitializerError
>      * [MNG-4213] - preemptive auth in
> non-lightweight http wagon causes
> Unauthorized responses from some servers
>      * [MNG-4219] - update plexus-utils
> to avoid leaking processes in
> CommandLineUtils.getSystemEnvars()
> 
> ** Improvement
>      * [MNG-2979] - Cross module
> dependencies for multi-module site
>      * [MNG-3203] - maven should
> execute compiler:compile and
> :test-compile in separate executions, to allow separate
> configuration
>      * [MNG-3834] - Improve error
> message when dependency with
> classifier is missing version
>      * [MNG-4210] - Remove log4j
> configuration warning
> 
> 
> ** Task
>      * [MNG-4143] - Update Java
> requirement to 1.5
>      * [MNG-4169] - Remove invocation
> of
> maven-plugin-plugin:updatePluginRegistry from default
> lifecycle bindings
> 
> 
> ** Wish
>      * [MNG-4139] - avoid the schema
> location in generated
> maven-metadata*.xml
> 
> 
> Enjoy,
> 
> -The Maven team
> 
> 
> -- 
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
> 
> -
> 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

RE: [ANN] Maven 2.2.0 Released

[Andrei Solntsev]

Maven main site hasn't link to 2.2.0 Release Notes:

Get Maven

* Download
* Release Notes (2.1.0)
* Release Notes (2.0.10)
* License


Andrei Solntsev,
Software Developer 

HireRight Estonia AS


-Original Message-
From: Mark Struberg [mailto:strub...@yahoo.de] 
Sent: Wednesday, July 01, 2009 2:29 AM
To: Maven Users List
Subject: RE: [ANN] Maven 2.2.0 Released


Works for me.

Sometimes it takes a bit for all mirrors to get synced.
Please try it again in a a few hours.

LieGrue,
strub

--- Jason Chaffee  schrieb am Mi, 1.7.2009:

> Von: Jason Chaffee 
> Betreff: RE: [ANN] Maven 2.2.0 Released
> An: "Maven Users List" , "annou...@maven.apache.org" 
> 
> Datum: Mittwoch, 1. Juli 2009, 1:04
> I have not been able to download this
> release.  It seems the artifact(s) are not at the
> specified URL. 
> 
> -Original Message-
> From: John Casey [mailto:jdca...@apache.org]
> 
> Sent: Tuesday, June 30, 2009 3:21 PM
> To: annou...@maven.apache.org;
> Maven Users List
> Subject: [ANN] Maven 2.2.0 Released
> 
> The Maven team is pleased to announce the release of the
> Maven 2.2.0.
> 
> Maven is a software project management and comprehension
> tool. It offers
> users the ability to build project binaries, generate a
> project website,
> and more.
> 
> http://maven.apache.org/
> 
> 
> Release Notes - Maven 2 - Version 2.2.0
> 
> ** Sub-task
>      * [MNG-4144] - document escape
> character for curly braces in
> clear-text passwords for settings.xml password security
>      * [MNG-4145] - switch to released
> versions of plexus-sec-dispatcher
> (and by ext. plexus-cipher) once they're available
> 
> ** Bug
>      * [MNG-2258] - Wrong execution
> order of plugins in same phase
>      * [MNG-3401] - Plugin parameters
> must be specified outside an
> execution block when they are invoked from the command
> line
>      * [MNG-3553] - cannot resolve
> dependency with scope import
>      * [MNG-3776] - Namespace
> misspelled in settings.xml
>      * [MNG-4074] - cyclic reference
> with 2.1.0-RC1 that doesn't occur
> with 2.0.10
>      * [MNG-4082] - Encryption is
> triggered if passwords merely contain
> curly braces
>      * [MNG-4126] - [regression]
> Properties defined in profiles.xml of
> parent are not inherited during multimodule build
>      * [MNG-4137] - NPE in
> DefaultLIfecycleExecutor when run from within
> Hudson builds
>      * [MNG-4140] - Properties
> incorrectly replaced in pom
>      * [MNG-4146] - password security
> doesn't work with custom password
> providers
>      * [MNG-4147] - very long passwords
> cause LightweightHTTP wagon to
> line-wrap the Base64-encoded Authorization header
>      * [MNG-4165] - http session
> cookies rejected with non-lightweight
> http wagon (maybe with lightweight one too)
>      * [MNG-4166] - Problem parsing
> command-line options in release:perform
>      * [MNG-4167] - version-expression
> transformation interferes with
> plugins like GPG
>      * [MNG-4168] - String index out of
> range: 43807
>      * [MNG-4179] - [regression]
> Artifact download hangs upon transfer
> failure
>      * [MNG-4184] - [regression]
> maven2.1 fails with cyclic dependency
> in case of extension/dependency for report-plugin to
> reactor-project
>      * [MNG-4207] - Plugins that use
> ArtifactResolver with http
> repositories AND depend on log4j run into
> ExceptionInInitializerError
>      * [MNG-4213] - preemptive auth in
> non-lightweight http wagon causes
> Unauthorized responses from some servers
>      * [MNG-4219] - update plexus-utils
> to avoid leaking processes in
> CommandLineUtils.getSystemEnvars()
> 
> ** Improvement
>      * [MNG-2979] - Cross module
> dependencies for multi-module site
>      * [MNG-3203] - maven should
> execute compiler:compile and
> :test-compile in separate executions, to allow separate
> configuration
>      * [MNG-3834] - Improve error
> message when dependency with
> classifier is missing version
>      * [MNG-4210] - Remove log4j
> configuration warning
> 
> 
> ** Task
>      * [MNG-4143] - Update Java
> requirement to 1.5
>      * [MNG-4169] - Remove invocation
> of
> maven-plugin-plugin:updatePluginRegistry from default
> lifecycle bindings
> 
> 
> ** Wish
>      * [MNG-4139] - avoid the schema
> location in generated
> maven-metadata*.xml
> 
> 
> Enjoy,
> 
> -The Maven team
> 
> 
> -- 
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
> 
> -
> 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-

RE: [ANN] Maven 2.2.0 Released

[Mark Struberg]

Works for me.

Sometimes it takes a bit for all mirrors to get synced.
Please try it again in a a few hours.

LieGrue,
strub

--- Jason Chaffee  schrieb am Mi, 1.7.2009:

> Von: Jason Chaffee 
> Betreff: RE: [ANN] Maven 2.2.0 Released
> An: "Maven Users List" , "annou...@maven.apache.org" 
> 
> Datum: Mittwoch, 1. Juli 2009, 1:04
> I have not been able to download this
> release.  It seems the artifact(s) are not at the
> specified URL. 
> 
> -Original Message-
> From: John Casey [mailto:jdca...@apache.org]
> 
> Sent: Tuesday, June 30, 2009 3:21 PM
> To: annou...@maven.apache.org;
> Maven Users List
> Subject: [ANN] Maven 2.2.0 Released
> 
> The Maven team is pleased to announce the release of the
> Maven 2.2.0.
> 
> Maven is a software project management and comprehension
> tool. It offers
> users the ability to build project binaries, generate a
> project website,
> and more.
> 
> http://maven.apache.org/
> 
> 
> Release Notes - Maven 2 - Version 2.2.0
> 
> ** Sub-task
>      * [MNG-4144] - document escape
> character for curly braces in
> clear-text passwords for settings.xml password security
>      * [MNG-4145] - switch to released
> versions of plexus-sec-dispatcher
> (and by ext. plexus-cipher) once they're available
> 
> ** Bug
>      * [MNG-2258] - Wrong execution
> order of plugins in same phase
>      * [MNG-3401] - Plugin parameters
> must be specified outside an
> execution block when they are invoked from the command
> line
>      * [MNG-3553] - cannot resolve
> dependency with scope import
>      * [MNG-3776] - Namespace
> misspelled in settings.xml
>      * [MNG-4074] - cyclic reference
> with 2.1.0-RC1 that doesn't occur
> with 2.0.10
>      * [MNG-4082] - Encryption is
> triggered if passwords merely contain
> curly braces
>      * [MNG-4126] - [regression]
> Properties defined in profiles.xml of
> parent are not inherited during multimodule build
>      * [MNG-4137] - NPE in
> DefaultLIfecycleExecutor when run from within
> Hudson builds
>      * [MNG-4140] - Properties
> incorrectly replaced in pom
>      * [MNG-4146] - password security
> doesn't work with custom password
> providers
>      * [MNG-4147] - very long passwords
> cause LightweightHTTP wagon to
> line-wrap the Base64-encoded Authorization header
>      * [MNG-4165] - http session
> cookies rejected with non-lightweight
> http wagon (maybe with lightweight one too)
>      * [MNG-4166] - Problem parsing
> command-line options in release:perform
>      * [MNG-4167] - version-expression
> transformation interferes with
> plugins like GPG
>      * [MNG-4168] - String index out of
> range: 43807
>      * [MNG-4179] - [regression]
> Artifact download hangs upon transfer
> failure
>      * [MNG-4184] - [regression]
> maven2.1 fails with cyclic dependency
> in case of extension/dependency for report-plugin to
> reactor-project
>      * [MNG-4207] - Plugins that use
> ArtifactResolver with http
> repositories AND depend on log4j run into
> ExceptionInInitializerError
>      * [MNG-4213] - preemptive auth in
> non-lightweight http wagon causes
> Unauthorized responses from some servers
>      * [MNG-4219] - update plexus-utils
> to avoid leaking processes in
> CommandLineUtils.getSystemEnvars()
> 
> ** Improvement
>      * [MNG-2979] - Cross module
> dependencies for multi-module site
>      * [MNG-3203] - maven should
> execute compiler:compile and
> :test-compile in separate executions, to allow separate
> configuration
>      * [MNG-3834] - Improve error
> message when dependency with
> classifier is missing version
>      * [MNG-4210] - Remove log4j
> configuration warning
> 
> 
> ** Task
>      * [MNG-4143] - Update Java
> requirement to 1.5
>      * [MNG-4169] - Remove invocation
> of
> maven-plugin-plugin:updatePluginRegistry from default
> lifecycle bindings
> 
> 
> ** Wish
>      * [MNG-4139] - avoid the schema
> location in generated
> maven-metadata*.xml
> 
> 
> Enjoy,
> 
> -The Maven team
> 
> 
> -- 
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
> 
> -
> 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: [ANN] Maven 2.2.0 Released

[Jason Chaffee]

I have not been able to download this release.  It seems the artifact(s) are 
not at the specified URL. 

-Original Message-
From: John Casey [mailto:jdca...@apache.org] 
Sent: Tuesday, June 30, 2009 3:21 PM
To: annou...@maven.apache.org; Maven Users List
Subject: [ANN] Maven 2.2.0 Released

The Maven team is pleased to announce the release of the Maven 2.2.0.

Maven is a software project management and comprehension tool. It offers
users the ability to build project binaries, generate a project website,
and more.

http://maven.apache.org/


Release Notes - Maven 2 - Version 2.2.0

** Sub-task
 * [MNG-4144] - document escape character for curly braces in
clear-text passwords for settings.xml password security
 * [MNG-4145] - switch to released versions of plexus-sec-dispatcher
(and by ext. plexus-cipher) once they're available

** Bug
 * [MNG-2258] - Wrong execution order of plugins in same phase
 * [MNG-3401] - Plugin parameters must be specified outside an
execution block when they are invoked from the command line
 * [MNG-3553] - cannot resolve dependency with scope import
 * [MNG-3776] - Namespace misspelled in settings.xml
 * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur
with 2.0.10
 * [MNG-4082] - Encryption is triggered if passwords merely contain
curly braces
 * [MNG-4126] - [regression] Properties defined in profiles.xml of
parent are not inherited during multimodule build
 * [MNG-4137] - NPE in DefaultLIfecycleExecutor when run from within
Hudson builds
 * [MNG-4140] - Properties incorrectly replaced in pom
 * [MNG-4146] - password security doesn't work with custom password
providers
 * [MNG-4147] - very long passwords cause LightweightHTTP wagon to
line-wrap the Base64-encoded Authorization header
 * [MNG-4165] - http session cookies rejected with non-lightweight
http wagon (maybe with lightweight one too)
 * [MNG-4166] - Problem parsing command-line options in release:perform
 * [MNG-4167] - version-expression transformation interferes with
plugins like GPG
 * [MNG-4168] - String index out of range: 43807
 * [MNG-4179] - [regression] Artifact download hangs upon transfer
failure
 * [MNG-4184] - [regression] maven2.1 fails with cyclic dependency
in case of extension/dependency for report-plugin to reactor-project
 * [MNG-4207] - Plugins that use ArtifactResolver with http
repositories AND depend on log4j run into ExceptionInInitializerError
 * [MNG-4213] - preemptive auth in non-lightweight http wagon causes
Unauthorized responses from some servers
 * [MNG-4219] - update plexus-utils to avoid leaking processes in
CommandLineUtils.getSystemEnvars()

** Improvement
 * [MNG-2979] - Cross module dependencies for multi-module site
 * [MNG-3203] - maven should execute compiler:compile and
:test-compile in separate executions, to allow separate configuration
 * [MNG-3834] - Improve error message when dependency with
classifier is missing version
 * [MNG-4210] - Remove log4j configuration warning


** Task
 * [MNG-4143] - Update Java requirement to 1.5
 * [MNG-4169] - Remove invocation of
maven-plugin-plugin:updatePluginRegistry from default lifecycle bindings


** Wish
 * [MNG-4139] - avoid the schema location in generated
maven-metadata*.xml


Enjoy,

-The Maven team


-- 
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

-
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

[ANN] Maven Wagon 1.0-beta-6 Released

[John Casey]

The Maven team is pleased to announce the release of Maven Wagon,
version 1.0-beta-6.

Wagon is an API for retrieving files from various types of remote
sources, including support for proxies, authentication, and more.

http://maven.apache.org/wagon/


Release Notes - Maven Wagon - Version 1.0-beta-6


** Bug
* [WAGON-220] - Wagon HTTP Deadlocks under high load
* [WAGON-270] - preemptive auth in non-lightweight http wagon
causes Unauthorized responses from some servers

** Improvement
* [WAGON-264] - compressed tarball download problems
* [WAGON-269] - Allow configuration of httpclient to change cookie
policy, other options
* [WAGON-271] - Provide configurability of httpclient parameters to
allow user to tell Maven to ignore cookies


Enjoy,

-The Maven team


--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

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

[ANN] Maven 2.2.0 Released

[John Casey]

The Maven team is pleased to announce the release of the Maven 2.2.0.

Maven is a software project management and comprehension tool. It offers
users the ability to build project binaries, generate a project website,
and more.

http://maven.apache.org/


Release Notes - Maven 2 - Version 2.2.0

** Sub-task
* [MNG-4144] - document escape character for curly braces in
clear-text passwords for settings.xml password security
* [MNG-4145] - switch to released versions of plexus-sec-dispatcher
(and by ext. plexus-cipher) once they're available

** Bug
* [MNG-2258] - Wrong execution order of plugins in same phase
* [MNG-3401] - Plugin parameters must be specified outside an
execution block when they are invoked from the command line
* [MNG-3553] - cannot resolve dependency with scope import
* [MNG-3776] - Namespace misspelled in settings.xml
* [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur
with 2.0.10
* [MNG-4082] - Encryption is triggered if passwords merely contain
curly braces
* [MNG-4126] - [regression] Properties defined in profiles.xml of
parent are not inherited during multimodule build
* [MNG-4137] - NPE in DefaultLIfecycleExecutor when run from within
Hudson builds
* [MNG-4140] - Properties incorrectly replaced in pom
* [MNG-4146] - password security doesn't work with custom password
providers
* [MNG-4147] - very long passwords cause LightweightHTTP wagon to
line-wrap the Base64-encoded Authorization header
* [MNG-4165] - http session cookies rejected with non-lightweight
http wagon (maybe with lightweight one too)
* [MNG-4166] - Problem parsing command-line options in release:perform
* [MNG-4167] - version-expression transformation interferes with
plugins like GPG
* [MNG-4168] - String index out of range: 43807
* [MNG-4179] - [regression] Artifact download hangs upon transfer
failure
* [MNG-4184] - [regression] maven2.1 fails with cyclic dependency
in case of extension/dependency for report-plugin to reactor-project
* [MNG-4207] - Plugins that use ArtifactResolver with http
repositories AND depend on log4j run into ExceptionInInitializerError
* [MNG-4213] - preemptive auth in non-lightweight http wagon causes
Unauthorized responses from some servers
* [MNG-4219] - update plexus-utils to avoid leaking processes in
CommandLineUtils.getSystemEnvars()

** Improvement
* [MNG-2979] - Cross module dependencies for multi-module site
* [MNG-3203] - maven should execute compiler:compile and
:test-compile in separate executions, to allow separate configuration
* [MNG-3834] - Improve error message when dependency with
classifier is missing version
* [MNG-4210] - Remove log4j configuration warning


** Task
* [MNG-4143] - Update Java requirement to 1.5
* [MNG-4169] - Remove invocation of
maven-plugin-plugin:updatePluginRegistry from default lifecycle bindings


** Wish
* [MNG-4139] - avoid the schema location in generated
maven-metadata*.xml


Enjoy,

-The Maven team


--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/

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

[ANN] Maven Wagon 1.0-beta-6

[John Casey]

The Maven team is pleased to announce the release of Maven Wagon, 
version 1.0-beta-6.


Wagon is an API for retrieving files from various types of remote 
sources, including support for proxies, authentication, and more.


http://maven.apache.org/wagon/


Release Notes - Maven Wagon - Version 1.0-beta-6


** Bug
* [WAGON-220] - Wagon HTTP Deadlocks under high load
* [WAGON-270] - preemptive auth in non-lightweight http wagon 
causes Unauthorized responses from some servers


** Improvement
* [WAGON-264] - compressed tarball download problems
* [WAGON-269] - Allow configuration of httpclient to change cookie 
policy, other options
* [WAGON-271] - Provide configurability of httpclient parameters to 
allow user to tell Maven to ignore cookies



Enjoy,

-The Maven team

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

[ANN] Maven 2.2.0

[John Casey]

The Maven team is pleased to announce the release of the Maven 2.2.0.

Maven is a software project management and comprehension tool. It offers 
users the ability to build project binaries, generate a project website, 
and more.


http://maven.apache.org/


Release Notes - Maven 2 - Version 2.2.0

** Sub-task
* [MNG-4144] - document escape character for curly braces in 
clear-text passwords for settings.xml password security
* [MNG-4145] - switch to released versions of plexus-sec-dispatcher 
(and by ext. plexus-cipher) once they're available


** Bug
* [MNG-2258] - Wrong execution order of plugins in same phase
* [MNG-3401] - Plugin parameters must be specified outside an 
execution block when they are invoked from the command line

* [MNG-3553] - cannot resolve dependency with scope import
* [MNG-3776] - Namespace misspelled in settings.xml
* [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur 
with 2.0.10
* [MNG-4082] - Encryption is triggered if passwords merely contain 
curly braces
* [MNG-4126] - [regression] Properties defined in profiles.xml of 
parent are not inherited during multimodule build
* [MNG-4137] - NPE in DefaultLIfecycleExecutor when run from within 
Hudson builds

* [MNG-4140] - Properties incorrectly replaced in pom
* [MNG-4146] - password security doesn't work with custom password 
providers
* [MNG-4147] - very long passwords cause LightweightHTTP wagon to 
line-wrap the Base64-encoded Authorization header
* [MNG-4165] - http session cookies rejected with non-lightweight 
http wagon (maybe with lightweight one too)

* [MNG-4166] - Problem parsing command-line options in release:perform
* [MNG-4167] - version-expression transformation interferes with 
plugins like GPG

* [MNG-4168] - String index out of range: 43807
* [MNG-4179] - [regression] Artifact download hangs upon transfer 
failure
* [MNG-4184] - [regression] maven2.1 fails with cyclic dependency 
in case of extension/dependency for report-plugin to reactor-project
* [MNG-4207] - Plugins that use ArtifactResolver with http 
repositories AND depend on log4j run into ExceptionInInitializerError
* [MNG-4213] - preemptive auth in non-lightweight http wagon causes 
Unauthorized responses from some servers
* [MNG-4219] - update plexus-utils to avoid leaking processes in 
CommandLineUtils.getSystemEnvars()


** Improvement
* [MNG-2979] - Cross module dependencies for multi-module site
* [MNG-3203] - maven should execute compiler:compile and 
:test-compile in separate executions, to allow separate configuration
* [MNG-3834] - Improve error message when dependency with 
classifier is missing version

* [MNG-4210] - Remove log4j configuration warning


** Task
* [MNG-4143] - Update Java requirement to 1.5
* [MNG-4169] - Remove invocation of 
maven-plugin-plugin:updatePluginRegistry from default lifecycle bindings



** Wish
* [MNG-4139] - avoid the schema location in generated 
maven-metadata*.xml



Enjoy,

-The Maven team

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

Build gets extra dependencies.

[David C. Hicks]

I've got an automated build that runs on Hudson that is producing a WAR
that cannot load and run.  It appears that it is picking up extra
dependencies during the build process.  One of those is
spring-2.0.6.jar.  I believe this is causing my load/run problem because
the error I get is related to loading the Spring context.  My question
is simply this...

Can anyone tell me why a Maven build would pick up extra dependencies if
everything appears to be the same between two machines.  Same JDK, same
version of Maven, same settings.xml in .m2, same build command ("mvn
clean install").  Yet, the automated build ends up with 5 extra jars in
the WEB-INF/lib directory.  I'm stumped, and this is causing us a world
of problems.

Thanks in advance.
Dave


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

Re: bug? strange resolution of commons-logging dependency

[Rusty Wright]

This may be a dumb or inappropriate question, but why does Tomcat need commons 
logging?  Why can't it just use java util logging?


Jörg Schaible wrote:

Hi Ceki,

Ceki Gulcu wrote at Dienstag, 30. Juni 2009 16:45:



Jörg Schaible wrote:


You've been right, I should have read your question closer. See Dennis'
answer. Actually there was an attempt to release an official empty
commons-logging at Apache recently and it was tunred down exactly because
we could foresee this problem you're facing now :-/

Note that we wanted to release version 0.0-EMPTY, not version 99. One
could argue that releasing 0.0-EMPTY could have prevented this issue
from occurring.


Since the algorithm takes the distance into account, it could have been
happened also:

A depends on B, C
B depends on D
C depends on CL-0.0-EMPTY
D depends on CL-1.1.1

C' dep to CL-0.0-EMPTY is nearer -> compilation fails.

As said, it's a good solution for an end application, but not for libraries
used by others ;-)

- Jörg


-
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: bug? strange resolution of commons-logging dependency

[Lucas Bergman]

Dennis Lundberg wrote:
> Lucas Bergman wrote:
> > Running this test with Maven 2.1.0 fails:
> >
> >   java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
> >   [ ... ]
> >
> > The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
> > (compile-scope) dependency, so this seems wrong.  There seems to
> > be some interaction between that POM and the dependent POMs.
> > Indeed:
> >
> >   [ ... ]
> >
> >   2.  Adding an exclusion of commons-logging to the
> >   hibernate-ehcache dependency causes the test to succeed.  I
> >   tried this, because the hibernate-ehcache POM depends on
> >   commons-logging version 99.0-does-not-exist, a rather famous
> >   JBoss kludge[1].
> >
> > [ ... ]
> >
> > Footnotes:
> > [1]  
> > http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html
>
> That is your problem. What this does is mess the dependency-tree. It
> removes commons-logging from the dependency tree because that
> version "99.0-..." is larger than the latest current release of
> commons-logging.  The "99.0-..." version should *never ever* reach
> end users. It can *only* be used by internal project.

Thanks for the input.  Are you saying that the dependency of the
hibernate-ehcache POM on commons-logging 99.0-does-not-exist is a bug?
I'm sympathetic to that view, but I just want to be sure.  To be sure,
it seems foolish for the Hibernate developers to put something like
this in a library's POM, since it would seem to impose their kludge
on the programmer using the library.

Of course, we fixed our particular problem by adding an 
for commons-logging from our hibernate-ehcache dependency.

-- Lucas

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

help: antrun does not do anything

[Qiner Yang]

Because some functions not available or not easily accomplishable in maven, so 
I turned to the antrun in maven. But I can never get the antrun working, please 
help me out. 

I read the Maven AntRun Plugnin page, 
http://maven.apache.org/plugins/maven-antrun-plugin/, and followed all the 
instructions and tried all the examples in the examples section,  
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html. 
But nothing is generated from the antrun. I tried a very simple ant command, 
, or an ant task 

 

between the maven . The ant "test target" is to make a directory, which 
works fine when issuing "ant test", but nothing happen in mvn. Strange, the mvn 
command shows execution successful, see below:
[INFO] Scanning for projects...
[INFO] 
[INFO] Building RTJDBC
[INFO]task-segment: [antrun:run]
[INFO] 
[INFO] [antrun:run]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Tue Jun 30 11:04:56 PDT 2009
[INFO] Final Memory: 2M/5M
[INFO] 

I tried removing the antrun plugin from the pom.xml, the mvn antrun output is 
exactly the same as above. Got confused.
thanks for any help.

Qiner

Re: Scope

[Max Bowsher]

> Sipungora wrote:
>> I need provided transitive scope. Scope provided isn't transitive. Is
>> there a solution for it?

Jaikiran wrote:
> From what i understand of the table here
>
http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-transitive.html
> transitive dependencies for a "provided" scope dependencies are infact
> "provided". Are you seeing a different behaviour?


"provided" is transitive through "provided".

Much to my confusion and occasional annoyance, "provided" isn't
transitive through "compile" or "test", which logic, to me at leasts,
suggests it should be. Sipungora: Is this the problem you refer to?


Max.




signature.asc
Description: OpenPGP digital signature

Re: antrun does not do anything

[Qiner Yang]

attached are the pom.xml and build.xml files. 
run ant, generates the abc2 folder, but
run mvn antrun:run, generates nothing.

  - Original Message - 
  From: Qiner Yang 
  To: users@maven.apache.org 
  Sent: Tuesday, June 30, 2009 11:36 AM
  Subject: help: antrun does not do anything


  Because some functions not available or not easily accomplishable in maven, 
so I turned to the antrun in maven. But I can never get the antrun working, 
please help me out. 

  I read the Maven AntRun Plugnin page, 
http://maven.apache.org/plugins/maven-antrun-plugin/, and followed all the 
instructions and tried all the examples in the examples section,  
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html. 
But nothing is generated from the antrun. I tried a very simple ant command, 
, or an ant task 
  
  
  
  between the maven . The ant "test target" is to make a directory, 
which works fine when issuing "ant test", but nothing happen in mvn. Strange, 
the mvn command shows execution successful, see below:
  [INFO] Scanning for projects...
  [INFO] 

  [INFO] Building RTJDBC
  [INFO]task-segment: [antrun:run]
  [INFO] 

  [INFO] [antrun:run]
  [INFO] Executing tasks
  [INFO] Executed tasks
  [INFO] 

  [INFO] BUILD SUCCESSFUL
  [INFO] 

  [INFO] Total time: 1 second
  [INFO] Finished at: Tue Jun 30 11:04:56 PDT 2009
  [INFO] Final Memory: 2M/5M
  [INFO] 


  I tried removing the antrun plugin from the pom.xml, the mvn antrun output is 
exactly the same as above. Got confused.
  thanks for any help.

  Qiner

  4.0.0
  my-test-app
  my-test-group
  1.0-SNAPSHOT

  


  
org.apache.maven.plugins
maven-antrun-plugin

  
compile
compile

  





  


  run

  

  

  

  	

		




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

RE: Skip package phase for one subproject

[Marouane Amraoui]

We have 5 subproject. The last is a web application. At mvn clean install
Generation of the war take 4 minutes. We don't need to generate this war so if 
I skip this
Phase I will win 4 minute at build maven.


-Message d'origine-
De : Jaikiran [mailto:jai_forums2...@yahoo.co.in]
Envoyé : mardi 30 juin 2009 17:13
À : users@maven.apache.org
Objet : Re: Skip package phase for one subproject


As far as i know, you cannot skip the default lifecycle phases. Why exactly
do you want to do this?

-Jaikiran

Marouane Amraoui-2 wrote:
>
> Hi,
> I have a multiproject maven
>
> Parent1 :
>
> è Child1
>
> è Child2
>
> I launch mvn clean install on Parent1.
> I need to skip package phase in subproject  Child2.
>
> It is possible ?
>
> Thx in advance.
>
>

--
View this message in context: 
http://www.nabble.com/Skip-package-phase-for-one-subproject-tp24269066p24274859.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: bug? strange resolution of commons-logging dependency

[Jörg Schaible]

Hi Ceki,

Ceki Gulcu wrote at Dienstag, 30. Juni 2009 16:45:

> 
> 
> Jörg Schaible wrote:
> 
>> You've been right, I should have read your question closer. See Dennis'
>> answer. Actually there was an attempt to release an official empty
>> commons-logging at Apache recently and it was tunred down exactly because
>> we could foresee this problem you're facing now :-/
> 
> Note that we wanted to release version 0.0-EMPTY, not version 99. One
> could argue that releasing 0.0-EMPTY could have prevented this issue
> from occurring.

Since the algorithm takes the distance into account, it could have been
happened also:

A depends on B, C
B depends on D
C depends on CL-0.0-EMPTY
D depends on CL-1.1.1

C' dep to CL-0.0-EMPTY is nearer -> compilation fails.

As said, it's a good solution for an end application, but not for libraries
used by others ;-)

- Jörg


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

Re: Skip package phase for one subproject

[Jaikiran]

As far as i know, you cannot skip the default lifecycle phases. Why exactly
do you want to do this?

-Jaikiran

Marouane Amraoui-2 wrote:
> 
> Hi,
> I have a multiproject maven
> 
> Parent1 :
> 
> è Child1
> 
> è Child2
> 
> I launch mvn clean install on Parent1.
> I need to skip package phase in subproject  Child2.
> 
> It is possible ?
> 
> Thx in advance.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Skip-package-phase-for-one-subproject-tp24269066p24274859.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: Scope

[Jaikiran]

>From what i understand of the table here
http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-transitive.html
transitive dependencies for a "provided" scope dependencies are infact
"provided". Are you seeing a different behaviour?


-Jaikiran

Sipungora wrote:
> 
> Hi,
> 
> I need provided transitive scope. Scope provided isn't transitive. Is
> there a solution for it?
> 
> Thanks in advance.
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Scope-tp24270252p24274815.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

Custom dependency resolver for a Maven project

[Jaikiran]

Hello everyone,

I am trying to find some inputs on how best to manipulate the dependency
resolution within Maven. Given a project X and its set of dependencies, is
there a way wherein i can sort of filter out the dependencies? Or is there
some documentation or any pointer on how to implement and configure/hook a
custom dependency resolver? For example, if the project X depends on 1.0.0
version of xxx.yyy.zzz:someproject then is there some way where in i can
modify this dependency (without actually modifying the dependency in the
pom.xml) when the dependency resolution for the project is taking place? 

Also, which exact lifecycle phase does Maven do the dependency resolution
for the project? And is the resolution done through some Maven plugin? Is it
the same dependency plugin which is used for dependency:tree?

-- 
View this message in context: 
http://www.nabble.com/Custom-dependency-resolver-for-a-Maven-project-tp24274681p24274681.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

Using parent POMs effectively

[J . T . Halliley]

I've created a parent POM, in which to house a few common dependencies, 
but mostly to set up how a site is built:

*  CheckStyle rules,
*  JavaDoc stylesheet,
*  JXR stylesheet,
*  site stylesheet.

But the latter site.css is not being picked up:  It lives in 
src/site/resources/css/site.css 
under the parent project.  If I put site.css under the child project, it 
is copied to 
target/site/css just fine.

Should I be able to put such resources under the parent POM's project? 
I've even tried specifying the following in the parent POM:



   
   
org.apache.maven.plugins
maven-site-plugin


 ${env.FSB_PROJECTS_HOME}/fsb-master-pom/src/site/resources/css/site.css


   
  ...

It'd be nice to specify such things once in the parent project to be used 
by all child projects.

Ideas?

Tom
j.t.halli...@flagstar.com


This e-mail may contain data that is confidential, proprietary or non-public 
personal information, as that term is defined in the Gramm-Leach-Bliley Act 
(collectively, Confidential Information). The Confidential Information is 
disclosed conditioned upon your agreement that you will treat it confidentially 
and in accordance with applicable law, ensure that such data isn't used or 
disclosed except for the limited purpose for which it's being provided and will 
notify and cooperate with us regarding any requested or unauthorized disclosure 
or use of any Confidential Information. 
By accepting and reviewing the Confidential information, you agree to indemnify 
us against any losses or expenses, including attorney's fees that we may incur 
as a result of any unauthorized use or disclosure of this data due to your acts 
or omissions. If a party other than the intended recipient receives this 
e-mail, he or she is requested to instantly notify us of the erroneous delivery 
and return to us all data so delivered.

[Workaround] RE: OutOfMemoryError when deploying large files

[Rakesh Arora]

We have resolved the problem by using dav:http protocol instead of http
protocol.

I have raised a jira against wagon-http-lightweight:
http://jira.codehaus.org/browse/WAGON-272

-Rakesh



> -Original Message-
> From: Arora, Rakesh (CAR:9S00) 
> Sent: Friday, June 26, 2009 4:19 PM
> To: users@maven.apache.org
> Subject: OutOfMemoryError when deploying large files
> 
> When deploying a large artifact we get the OutOfMemoryError 
> (please check the attached stack trace). This is similar to 
> error reported here:
> http://www.mail-archive.com/users@maven.apache.org/msg99157.html
> 
> We traced the issue to wagon-http-lightweight using 
> PosterOutputStream/ByteArrayOutputStream.write(). This method 
> consumes lot of memory when dealing with large files as reported here:
> https://issues.alfresco.com/jira/browse/ETHREEOH-974
> 
> In  our case, we are trying to deploy a around 600M file and 
> have set the maximum heap space to 1024M (-Xmx1024m). We are 
> still running out of memory. We are using maven 2.0.8 but had 
> the same issue when tried with 2.1.0 version.
> 
> Is there a way to use another Wagon provider (wagon-http ?) 
> that can deal better with large files? If yes, how can we 
> configure this?
> 
> Should I raise a jira for this (against which component 
> maven-deploy-plugin or wagon-http-lightweight)?
> 
> Thanks,
> -Rakesh
> 
> 
> 
> ;-STACK TRACE- 
> [DEBUG] -- end configuration -- [INFO] [deploy:deploy-file]
> Uploading: http:foo/1.0/foo-1.0.zip
> [INFO]
> --
> --
> [ERROR] FATAL ERROR
> [INFO]
> --
> --
> [INFO] Java heap space
> [INFO]
> --
> --
> [DEBUG] Trace
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at
> java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at
> sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> 
> at
> org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:338)
> 
> at
> org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:305)
> 
> at
> org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:267)
> 
> at
> org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:2
> 38)
> at 
> org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:143)
> at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(Lightw
> eightHttpWagon.java:148)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(D
> efaultWagonManager.java:237)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Def
> aultWagonManager.java:153)
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Def
> aultArtifactDeployer.java:80)
> at
> org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.
> java:240)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:447)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:224)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:143)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at 
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> 
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> --
> --
> [INFO] Total time: 1 minute 22 seconds
> [INFO] Finished at: Fri Jun 26 15:

Re: bug? strange resolution of commons-logging dependency

[Ceki Gulcu]

Jörg Schaible wrote:


You've been right, I should have read your question closer. See Dennis'
answer. Actually there was an attempt to release an official empty
commons-logging at Apache recently and it was tunred down exactly because
we could foresee this problem you're facing now :-/


Note that we wanted to release version 0.0-EMPTY, not version 99. One
could argue that releasing 0.0-EMPTY could have prevented this issue
from occurring.


- Jörg


--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch

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

Problem with Maven 2.1 and NSIS plugin

[Mikael.Bertlin]

Hi,

I've searched a lot and can't find any awnser so you are my last hope.

The problem I have is that I want a NSIS plugin for Maven 2.1

I've tried: 
http://mojo.codehaus.org/nsis-maven-plugin/examples/sample-nsis-project.html 
whcih I had to bouild from source with maven. But didn't get is to work ...

Then I tried 
http://mindtreeinsight.sourceforge.net/releng/maven-nsis-plugin/index.html 
using the POM and jar found here: 
http://mindtreeinsight.svn.sourceforge.net/viewvc/mindtreeinsight/maven-repo/trunk/release/com/mindtree/techworks/insight/releng/maven-nsis-plugin/0.2.0-M1/

I install the plugin(the second one) like this:
mvn install:install-file 
-Dfile=C:\maven\apache-maven-2.1.0\maven_plugins\newnsis\maven-nsis-plugin-0.2.0-M1.jar
 
-DpomFile=C:\maven\apache-maven-2.1.0\maven_plugins\newnsis\maven-nsis-plugin-0.2.0-M1.pom

I search around a little and findout that I need to update my projects pom.xml 
with insctuctions here: 
http://mindtreeinsight.sourceforge.net/releng/maven-nsis-plugin/0.1.0/usage.html
 So I get my pom.xml looking like this:

http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
  4.0.0
  com.mycompany.app
  my-app
  jar
  1.0-SNAPSHOT
  my-app
  http://maven.apache.org
  

  junit
  junit
  3.8.1
  test

  



  maven-repo
  
http://mindtreeinsight.svn.sourceforge.net/viewvc/mindtreeinsight/maven-repo/trunk/release

  

  

   
com.mindtree.techworks.insight.releng
maven-nsis-plugin
0.2.0-M1

target\










Now I get a new error from Maven, running mvn package:

C:\Documents and Settings\bertlmik\my-app>mvn package
[INFO] Scanning for projects...
[INFO] 
[INFO] Building my-app
[INFO]task-segment: [package]
[INFO] 
Downloading: http://repo1.maven.org/maven2/com/mindtree/techworks/insight/parent
/1.0.0/parent-1.0.0.pom
[INFO] Unable to find resource 'com.mindtree.techworks.insight:parent:pom:1.0.0'
 in repository central (http://repo1.maven.org/maven2)
Downloading: http://mindtreeinsight.svn.sourceforge.net/viewvc/mindtreeinsight/m
aven-repo/trunk/release/com/mindtree/techworks/insight/parent/1.0.0/parent-1.0.0
.pom

[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] The plugin descriptor for the plugin Plugin [com.mindtree.techworks.insig
ht.releng:maven-nsis-plugin] was not found. Please verify that the plugin JAR C:
\Documents and Settings\bertlmik\.m2\repository\com\mindtree\techworks\insight\r
eleng\maven-nsis-plugin\0.2.0-M1\maven-nsis-plugin-0.2.0-M1.jar is intact.
[INFO] 
[INFO] Trace
java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin [co
m.mindtree.techworks.insight.releng:maven-nsis-plugin] was not found. Please ver
ify that the plugin JAR C:\Documents and Settings\bertlmik\.m2\repository\com\mi
ndtree\techworks\insight\releng\maven-nsis-plugin\0.2.0-M1\maven-nsis-plugin-0.2
.0-M1.jar is intact.
at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM
anager.java:353)
at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De
faultPluginManager.java:217)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug
inManager.java:177)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
ultLifecycleExecutor.java:1517)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifec
ycle(DefaultLifecycleExecutor.java:1479)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycl
eMappings(DefaultLifecycleExecutor.java:1245)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:518)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(

Re: Failed to validate an ostensibly valid pom

[John Casey]

If you run with -X, it may give you more information about why it's invalid.

Just a thought.

-john

daniel.green wrote:

dgr...@dgreen-desktop:~/redacted_renovation/workspace/dto$ mvn compileb

[WARNING] POM for 'com.redacted:utility:pom:1.0:compile' is invalid. It will
be ignored for artifact resolution. Reason: Failed to validate POM for
project com.redacted:utility at Artifact
[com.redacted:utility:pom:1.0:compile]
Downloading:
http://10.1.102.139:8081/artifactory/repo/org/apache/maven/doxia/doxia-converter/1.1-SNAPSHOT/doxia-converter-1.1-SNAPSHOT.pom
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Jun 26 19:52:22 EDT 2009
[INFO] Final Memory: 8M/16M
[INFO] ---

Notice the warning regarding com.redacted:utility:pom:1.0. However I can
compile com.redacted:utility without any complaints. I can also do a compile
of the parent pom.

dto/pom.xml:




com.redacted
maven
1.0
../maven/pom.xml


4.0.0
dto
${artifactId}
../../${artifactId}/target/site
1.0
DTO



com.redacted
utility
1.0




And the one of utility/pom.xml




com.redacted
maven
1.0
../maven/pom.xml


4.0.0
utility
${artifactId}
../../${artifactId}/target/site
1.0
Utility  



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

Scope

[Sipungora]

Hi,

I need provided transitive scope. Scope provided isn't transitive. Is there
a solution for it?

Thanks in advance.


-- 
View this message in context: 
http://www.nabble.com/Scope-tp24270252p24270252.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

Mojo for listing all the packaged and attached artifacts.

[Kiss Tibor]

I would like to find or write a maven plugin which once declared in the
company's parent pom, all the builds descending from that, will print out on
the console some information about the packaged and attached artifacts. Here
are some sample patterns.

For JAR:
HERE_YOU_CAN_FIND: /home/me/Sample/target/Sample-1.0.0-SNAPSHOT.jar
THE_PACKAGED_ARTIFACT: org.somegroupid.Sample

For EJB:
HERE_YOU_CAN_FIND: /home/me/SampleEJB/target/SampleEJB-1.0.0-SNAPSHOT.jar
THE_PACKAGED_ARTIFACT: org.somegroupid.SampleEJB.ejb
HERE_YOU_CAN_FIND:
/home/me/SampleEJB/target/SampleEJB-1.0.0-SNAPSHOT-client.jar
THE_PACKAGED_ARTIFACT: org.somegroupid.SampleEJB.ejb-client

For WebApp:
HERE_YOU_CAN_FIND: /home/me/SampleWeb/target/SampleWeb-1.0.0-SNAPSHOT.war
THE_PACKAGED_ARTIFACT: org.somegroupid.SampleWeb.war

Unfortunately I couldn't find a simple pattern which can be easily expressed
within an ant-run plugin, because:
- the ${project.build.directory}/${project.build.finalName} also needs a
file extension too which is not always the same as ${project.packaging}
- in case of attached artifacts (ex: ejb-client) I need an enumeration with
multiple lines which will append the ".ejb-client" type to the
${project.groupId}.${project.artifactId}

Somebody knows how to enlist all the packaged and attached artifacts within
a Mojo?

Skip package phase for one subproject

[Marouane Amraoui]

Hi,
I have a multiproject maven

Parent1 :

è Child1

è Child2

I launch mvn clean install on Parent1.
I need to skip package phase in subproject  Child2.

It is possible ?

Thx in advance.

Re: SCM SVN Provider fails on Windows with cygwin/svn because of "C:/" prefix

[Ovidiu Feodorov]

Hi Olivier, yes, I actually tried that, it does not help, see my 
previous reply to the list (sent a couple of minutes ago) for an 
explanation why. The answer is in 
org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.addTarget(). 
I'd change it to take into account the  setting, it 
currently doesn't.



Olivier Lamy wrote:

Did you have a look here : http://maven.apache.org/scm/subversion.html

  true in order to use cygwin path /cygdrive/c
  the mount path to use default is /cygwin

Personnaly I use windows svn even if I use cygwin.

--
Olivier

2009/6/30 Ovidiu Feodorov :
  

I know this is not a new problem, I found several JIRA issues related to it
(SCM-213 , for example), all
reported "Resolved", but yet I am using Maven SCM 1.2 and the 2.0 Beta 9
release plug-in and , and I am still seeing it.

This is what happens in my case:

I am running mvn release:prepare for a multi-module project, (cygwin,
Windows) and the operation fails with:

  [INFO] Checking in modified POMs...
  [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
  c:\Users\ovidiu\AppData\Local\Temp\maven-scm-1114844030.commit
  --targets c:\Users\ovidiu\AppData\Local\Temp\maven-scm-59263-targets"
  [INFO] Working directory:
  c:\work\playground\maven\release-plugin-experiments
  [INFO]
  
  [ERROR] BUILD FAILURE
  [INFO]
  
  [INFO] Unable to commit files
  Provider message:
  The svn command failed.
  Command output:
  svn:
  '/cygdrive/c/work/playground/maven/release-plugin-experiments/C:' is
  not a working copy
  svn: Can't open file

'/cygdrive/c/work/playground/maven/release-plugin-experiments/C:/.svn/entries':
  No such file or directory

The temporary file maven-scm-x-targets contains

  c:/work/playground/maven/release-plugin-experiments/pom.xml
  C:/work/playground/maven/release-plugin-experiments/sub-module-one/pom.xml


which confuses svn. C:/work/playground/maven/release-plugin-experiments is
the correct project home, cygwin svn is bothered by the C:/ prefix.
It seems quite obvious that this could be handled by cygwin svn, but I
believe it could also be worked around from the Maven layer, with minimum of
effort, especially that Maven SCM already has Cygwin-related configuration
options. If Maven would generate maven-scm-x-targets to contain cygwin
paths Windows paths, that would quell svn.

The file list in maven-scm-x-targets is generated by
org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.addTargets()
(https://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.2/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java).

SvnCommandLineUtils.addTargets() could take into consideration
Cygwin-related   ( and ) and
build the paths accordingly.  and  are
already there, and this was probably the hardest part  (see
http://maven.apache.org/scm/subversion.html).

If you think this is a sensible solution that'll make the life of the
developers easier, and are willing to apply it, I'll submit the patch.

Or, it is also quite possible that I am totally missing something obvious
here, and I will be happy to be guided to the right path.

Cheers,
Ovidiu





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

  



--
Ovidiu Feodorov
CEO
Nova Ordis LLC
650-255-0323
ovi...@novaordis.com 

Re: SCM SVN Provider fails on Windows with cygwin/svn because of "C:/" prefix

[Ovidiu Feodorov]

Jörg Schaible wrote:

Hi,
  

Hi, thanks for answering.

Ovidiu Feodorov wrote at Dienstag, 30. Juni 2009 04:55:

[snip]
  

It seems quite obvious that this could be handled by cygwin svn



No. Cygwin provides a POSIX layer for the file operations to allow unix
utilities to compile and work in the Cygwin environment. Although some
basic commands in Cygwin understand DOSish syntax, its up to the individual
maintainer to patch that into the code and maintain this patch. Obviously
this is no fun and normally not done.
  


One more reason to handle this at the Maven level, especially given the 
fact that someone else bumped into similar problems and introduced 
support for .



[...]
IMHO the flag useCygwinPath should be enough. The implementation can
determin the paths itself by executing "cygpath -u path" for each. The
cygwinMountPath option is not a good choice, since it depends on the
developer's environment and might not work at all if the path is on the
network.
  


Yes, that's what I thought too, but

   
   org.apache.maven.plugins
   maven-scm-plugin
   
   
   true
   
   
   

had no effect whatsoever when I first tried it, and then after looking 
at 
https://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.2/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java, 
I found out why, SvnCommandLineUtils, the code that generates the 
content of the --targets file, doesn't even look at anything remotely 
related to SCM configuration.


It is just:

   for ( Iterator i = files.iterator(); i.hasNext(); )
   {
   File f = (File) i.next();
   sb.append( f.getPath().replace( '\\', '/' ) );
   sb.append( ls );
   }

which dumps OS-dependent path representation into the text file (yes, 
changing backslashes into forward slashes, but this doesn't help with "C:".


This is where I would to try to patch.

If I have time tomorrow, I'll actually write the patch and see if it works.

Re: SCM SVN Provider fails on Windows with cygwin/svn because of "C:/" prefix

[Jörg Schaible]

Hi,

Ovidiu Feodorov wrote at Dienstag, 30. Juni 2009 04:55:

[snip]

> It seems quite obvious that this could be handled by cygwin svn

No. Cygwin provides a POSIX layer for the file operations to allow unix
utilities to compile and work in the Cygwin environment. Although some
basic commands in Cygwin understand DOSish syntax, its up to the individual
maintainer to patch that into the code and maintain this patch. Obviously
this is no fun and normally not done.

> , but I 
> believe it could also be worked around from the Maven layer, with
> minimum of effort, especially that Maven SCM already has Cygwin-related
> configuration options. If Maven would generate maven-scm-x-targets
> to contain cygwin paths Windows paths, that would quell svn.
> 
> The file list in maven-scm-x-targets is generated by
>
org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.addTargets()
>
(https://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.2/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java).
> 
> SvnCommandLineUtils.addTargets() could take into consideration
> Cygwin-related   ( and )
> and build the paths accordingly.  and 
> are already there, and this was probably the hardest part  (see
> http://maven.apache.org/scm/subversion.html).
> 
> If you think this is a sensible solution that'll make the life of the
> developers easier, and are willing to apply it, I'll submit the patch.
>
> Or, it is also quite possible that I am totally missing something
> obvious here, and I will be happy to be guided to the right path.

IMHO the flag useCygwinPath should be enough. The implementation can
determin the paths itself by executing "cygpath -u path" for each. The
cygwinMountPath option is not a good choice, since it depends on the
developer's environment and might not work at all if the path is on the
network.

- Jörg


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

RE: tools.jar

[McElroy Sean]

Thanks Roman. 

I have checked the maven version and the java home value is correct:
C:\Program Files\Java\jdk1.6.0_06

-Original Message-
From: Roman Kournjaev [mailto:kournj...@gmail.com] 
Sent: 29 June 2009 17:04
To: Maven Users List
Subject: Re: tools.jar

Hi

I had this problem a few times. Its definitely a jdk problem.
check your mvn -version , verify it takes the right java home.

C:\Documents and Settings\rkournja>mvn -version
Maven version: 2.0.9
Java version: 1.5.0_18
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

C:\Documents and Settings\rkournja>ECHO %JAVA_HOME%
C:\Program Files\Java\jdk1.5.0_18

Roman


On Mon, Jun 29, 2009 at 6:46 PM, McElroy Sean
wrote:

> Hello,
>
> My JAVA_HOME variable points to: C:\Program Files\Java\jdk1.6.0_06
>
> Regards,
>
> Seam
>
> -Original Message-
> From: Roman Kournjaev [mailto:kournj...@gmail.com]
> Sent: 29 June 2009 16:36
> To: Maven Users List
> Subject: Re: tools.jar
>
> Hi
>
>
> You ll probably will get rid of this error if you run will have the
JDK
> ,
> instaead of the JRE in your PATH.
> Check your JAVA_HOME , it should always point to a JDK when working
with
> maven.
>
>
> The tools.jar is already inside the jdk in its the lib folder.
>
> Roman
>
> On Mon, Jun 29, 2009 at 6:29 PM, McElroy Sean
> wrote:
>
> > Hello,
> >
> >
> >
> > I'm getting this error: java.lang.ClassNotFoundException:
> > com.sun.mirror.apt.AnnotationProcessorFactory, when I try to compile
a
> > web-service project using jaxws-maven-plugin. I understand that this
> > problem relates to tools.jar. So having read the FAQ on the Maven
site
> I
> > added this to my pom:
> >
> >
> >
> > 
> >
> >  com.sun
> >
> >  tools
> >
> >  1.6/version>
> >
> >  system
> >
> >  ${java.home}/../lib/tools.jar
> >
> > 
> >
> >
> >
> > but this didn't fix the problem. I have read a few posts about this
> but
> > none have provided the answer. Has anyone solved this?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Seam
> >
> >
> >
> >
> >
> >
>
> -
> 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: SCM SVN Provider fails on Windows with cygwin/svn because of "C:/" prefix

[Olivier Lamy]

Did you have a look here : http://maven.apache.org/scm/subversion.html

  true in order to use cygwin path /cygdrive/c
  the mount path to use default is /cygwin

Personnaly I use windows svn even if I use cygwin.

--
Olivier

2009/6/30 Ovidiu Feodorov :
>
> I know this is not a new problem, I found several JIRA issues related to it
> (SCM-213 , for example), all
> reported "Resolved", but yet I am using Maven SCM 1.2 and the 2.0 Beta 9
> release plug-in and , and I am still seeing it.
>
> This is what happens in my case:
>
> I am running mvn release:prepare for a multi-module project, (cygwin,
> Windows) and the operation fails with:
>
>   [INFO] Checking in modified POMs...
>   [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>   c:\Users\ovidiu\AppData\Local\Temp\maven-scm-1114844030.commit
>   --targets c:\Users\ovidiu\AppData\Local\Temp\maven-scm-59263-targets"
>   [INFO] Working directory:
>   c:\work\playground\maven\release-plugin-experiments
>   [INFO]
>   
>   [ERROR] BUILD FAILURE
>   [INFO]
>   
>   [INFO] Unable to commit files
>   Provider message:
>   The svn command failed.
>   Command output:
>   svn:
>   '/cygdrive/c/work/playground/maven/release-plugin-experiments/C:' is
>   not a working copy
>   svn: Can't open file
>
> '/cygdrive/c/work/playground/maven/release-plugin-experiments/C:/.svn/entries':
>   No such file or directory
>
> The temporary file maven-scm-x-targets contains
>
>   c:/work/playground/maven/release-plugin-experiments/pom.xml
>   C:/work/playground/maven/release-plugin-experiments/sub-module-one/pom.xml
>
>
> which confuses svn. C:/work/playground/maven/release-plugin-experiments is
> the correct project home, cygwin svn is bothered by the C:/ prefix.
> It seems quite obvious that this could be handled by cygwin svn, but I
> believe it could also be worked around from the Maven layer, with minimum of
> effort, especially that Maven SCM already has Cygwin-related configuration
> options. If Maven would generate maven-scm-x-targets to contain cygwin
> paths Windows paths, that would quell svn.
>
> The file list in maven-scm-x-targets is generated by
> org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.addTargets()
> (https://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.2/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/SvnCommandLineUtils.java).
>
> SvnCommandLineUtils.addTargets() could take into consideration
> Cygwin-related   ( and ) and
> build the paths accordingly.  and  are
> already there, and this was probably the hardest part  (see
> http://maven.apache.org/scm/subversion.html).
>
> If you think this is a sensible solution that'll make the life of the
> developers easier, and are willing to apply it, I'll submit the patch.
>
> Or, it is also quite possible that I am totally missing something obvious
> here, and I will be happy to be guided to the right path.
>
> Cheers,
> Ovidiu
>
>

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

Re: bug? strange resolution of commons-logging dependency

[Jörg Schaible]

Lucas Bergman wrote at Montag, 29. Juni 2009 18:11:

> Jörg Schaible wrote:
>> Lucas Bergman wrote:
>> > Jörg Schaible wrote:
>> > > Lucas Bergman wrote:
>> > > > Running this test with Maven 2.1.0 fails:
>> > > >
>> > > >   java.lang.NoClassDefFoundError:
>> > > >   org/apache/commons/logging/LogFactory
>> > > >   [ ... ]
>> > > >
>> > > > The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
>> > > > (compile-scope) dependency, so this seems wrong.  There seems to
>> > > > be some interaction between that POM and the dependent POMs...
>> > >
>> > > By default commons-logging tries to discover the logger in use
>> > > on its own.  Somehow a log4j is available from somewhere else,
>> > > but the classpath does not match. Therefore disable the
>> > > discovery by either providing a commons-logging.properties file
>> > > in src/test/resources or set a system property in the surefire
>> > > configuration for your tests.
>> >
>> > Thank you for the answer, but I don't think that that is the
>> > problem.  The commons-logging library never gets as far as
>> > configuration sniffing, since Maven doesn't include it in the
>> > classpath at all.  Running Maven with -X confirms that
>> > commons-logging-*.jar is never included in the classpath when
>> > running tests, unless I do one or more of the rain dances I
>> > detailed in my original message[1].
>> >
>> > The more I think about this, the more this seems like a Maven bug.
>>
>> See http://jira.codehaus.org/browse/MNG-4207 for background.
> 
> I understand what you're saying, but that's not it.  Look at the error
> above: the commons-logging classes are not even loaded, let alone
> configured.  Am I missing something?

You've been right, I should have read your question closer. See Dennis'
answer. Actually there was an attempt to release an official empty
commons-logging at Apache recently and it was tunred down exactly because
we could foresee this problem you're facing now :-/

- Jörg


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

Re: bug? strange resolution of commons-logging dependency

[Dennis Lundberg]

Lucas Bergman wrote:
> I ran into a strange dependency resolution problem at work, which a
> colleague and I whittled down to a fairly simple test case.  Consider
> the following POM:
> 
>   http://maven.apache.org/POM/4.0.0";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.example
> htmlunitbug
> jar
> 2.71828
> 
> 
>   
> 
>   
> maven-compiler-plugin
> 
>   1.5
>   1.5
> 
>   
> 
>   
> 
> 
> 
>   
> junit
> junit
> 4.6
> test
>   
>   
> net.sourceforge.htmlunit
> htmlunit
> 2.5
> test
>   
>   
> org.hibernate
> hibernate-ehcache
> 3.3.1.GA
> runtime
>   
>   
>   
> net.sf.ehcache
> ehcache
> 1.6.0
> runtime
>   
> 
>   
> 
> And, consider the following test class:
> 
>   import com.gargoylesoftware.htmlunit.WebClient;
>   import org.junit.Test;
> 
>   public class MyTest {
>   @Test public void test() { new WebClient(); }
>   }
> 
> Running this test with Maven 2.1.0 fails:
> 
>   java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
>   [ ... ]
> 
> The POM for htmlunit 2.5 declares commons-logging 1.1.1 as a
> (compile-scope) dependency, so this seems wrong.  There seems to be
> some interaction between that POM and the dependent POMs.  Indeed:
> 
>   1.  Moving the htmlunit dependency element below the
>   hibernate-ehcache and ehcache dependency elements causes
>   commons-logging to be a test-scope dependency, and the test
>   succeeds.  This seems bizarre.  Should the ordering of dependency
>   elements ever matter?

It does matter, but only for artifacts at the same distance from the
dependency.

>   2.  Adding an exclusion of commons-logging to the hibernate-ehcache
>   dependency causes the test to succeed.  I tried this, because the
>   hibernate-ehcache POM depends on commons-logging version
>   99.0-does-not-exist, a rather famous JBoss kludge[1].

That is your problem. What this does is mess the dependency-tree. It
removes commons-logging from the dependency tree because that version
"99.0-..." is larger than the latest current release of commons-logging.
The "99.0-..." version should *never ever* reach end users. It can
*only* be used by internal project.

>   3.  Removing the dependency on hibernate-ehcache causes the test to
>   succeed.  This is perhaps not surprising, in light of (2).
> 
>   4.  Removing the dependency on ehcache causes the test to succeed.
>   This is very strange to me, since ehcache directly depends on
>   commons-logging 1.0.4; it contains no funny business.
> 
> Am I doing something wrong here?  I'll be happy to follow this through
> with a JIRA ticket, if somebody here can convince me that I haven't
> done anything stupid; I'm not a very confident Maven user.
> 
> Best,
> -- Lucas
> 
> Footnotes:
> [1]  
> http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 


-- 
Dennis Lundberg

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