RE: Error building CAS with Maven 2.0.10
Something is horribly wrong with your setup or the CAS poms. The war plugin here: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/mav en-war-plugin-20030413.023708.pom Is not the right one. It should be in org/apache/maven/plugins not /maven. I'm guessing somehow you got a Maven1 plugin in the pom? -Original Message- From: Vinicius Borges [mailto:vinicius...@gmail.com] Sent: Friday, February 20, 2009 12:57 PM To: users@maven.apache.org Subject: Error building CAS with Maven 2.0.10 Hello everybody, I want to build CAS project... but something is gonna wrong... I builded CAS server 3.3.1 with Maven 2.0.10... [INFO] [INFO] Building JA-SIG CAS Web Application [INFO]task-segment: [package, install] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/ 2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/ 2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar 72K downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/mav en-war-plugin-20030413.023708.pom 165b downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/mav en-war-plugin-20030413.023708.jar 4K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana ger.java:327) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1275) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl e(DefaultLifecycleExecutor.java:1239) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java:1005) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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: 10 minutes 18 seconds [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 [INFO] Final Memory: 25M/51M [INFO] What should be this? Thanks! - 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: M2Eclipse Plugin can't resolve workspace dependency during MVN compile
Jason van Zyl-5 wrote: > >> So when, in Eclipse, I do: Run As -> Maven Build >> Is that invoking the CLI or is m2eclipse doing the work? If it's >> actually invoking the CLI, then that's the reason, but if m2eclipse is >> doing the work, I would expect it to find my workspace dependencies >> during the build. (Which it's not) > > When you are executing a build the default is to use the embedder and > _not_ use artifacts in the workspace. You have to enable that in the > run configurations. There is a toggle for that. > Jason, since 0.9.7 the default is to respect the workspace resolution setting from project preferences, i.e. default is to have workspace resolution on. Bu like you said, that can be changed in Maven launch configuration. regards, Eugene -- View this message in context: http://www.nabble.com/Maven-friendly-Open-Source-project-setup-tp21889533p22130199.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: Error building CAS
It seems to me that the POM for CAS has specified both the Maven 1 version and the Maven 2 version of the WAR Plugin. See pointers below... Vinicius Borges wrote: > Hello everybody, > > I want to build CAS project... but something is gonna wrong... > > [INFO] > > [INFO] Building JA-SIG CAS Web Application > [INFO]task-segment: [package, install] > [INFO] > Downloading the Maven 2 WAR Plugin > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom > 7K downloaded > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar > 72K downloaded Downloading a timestamped SNAPSHOT of the Maven 1 WAR Plugin. This is wrong and shouldn't be here. You can't use a Maven 1 plugin with Maven 2. > Downloading: > http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom > 165b downloaded > Downloading: > http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar > 4K downloaded > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] The PluginDescriptor for the plugin Plugin > [maven:maven-war-plugin] was not found. > [INFO] > > [INFO] Trace > java.lang.IllegalStateException: The PluginDescriptor for the plugin > Plugin [maven:maven-war-plugin] was not found. > at > org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) > at > org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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: 10 minutes 18 seconds > [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 > [INFO] Final Memory: 25M/51M > [INFO] > > > What should be this? > Thanks! > > - > 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
Problem with maven-ear-plugin
I am trying to use the maven-ear-plugin, and I keep getting:- [INFO] Failed to initialize ear modules Embedded error: Unknown artifact type[zip] I have tried using -X to get the debug messages, but I can not see where it is finding a ZIP file to use as an artifact. There are three modules I have specified (all jar files), but nothing else. How do I find out what it was trying to package that is causing it to try package a ZIP file. David - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Using the option within an assembly descriptor
I think I've discovered what's tripping me up a bit here.
Does this filtering take into consideration properties defined within
the mavenProject object or ONLY stuff pass in via the filtering file.
I'm referencing this page in particular:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/fi
ltering-some-distribution-files.html
"All the above files are in the root directory of the project but only
the README and the NOTICE files should be filtered. The property file
used to filter these are files is found in
src/assemble/filter.properties."
However, there is some conflicting documatation up there - in one place,
it suggests filters only exist for but it's clearly there in
.
Mick - I just saw your reply, and no, I've not set up in my
pom.
I've been under the impression (until right now) that the filtering that
the assembly plugin did factored in any of the mavenProject properties -
which apparently it doesn't.
Am I correct?
-Original Message-
From: EJ Ciramella [mailto:ecirame...@upromise.com]
Sent: Friday, February 20, 2009 3:06 PM
To: users@maven.apache.org
Subject: Using the option within an assembly descriptor
Hello again list, I'm struggling to get this thing working.
I'm trying my hardest to not process files (for a war project) once to
the target directory then AGAIN into the final assembly location.
So I'm using mvn assembly:directory but I don't see any of the tokens
expanded for the files when inside the descriptor, I have something like
this:
src/main/resources/java-properties
somedir
true
unix
true
hibernate.properties
The resulting hibernate.properties file still has ${stuff} type
properties left in there.
Any suggestions?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using the option within an assembly descriptor
Do those properties exist in your filter.properties file?
Did you setup ... in your pom.xml as well?
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Twitter: http://twitter.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Fri, Feb 20, 2009 at 3:05 PM, EJ Ciramella wrote:
> Hello again list, I'm struggling to get this thing working.
>
> I'm trying my hardest to not process files (for a war project) once to
> the target directory then AGAIN into the final assembly location.
>
> So I'm using mvn assembly:directory but I don't see any of the tokens
> expanded for the files when inside the descriptor, I have something like
> this:
>
>
> src/main/resources/java-properties
> somedir
> true
> unix
> true
>
>hibernate.properties
>
>
>
> The resulting hibernate.properties file still has ${stuff} type
> properties left in there.
>
> Any suggestions?
>
Using the option within an assembly descriptor
Hello again list, I'm struggling to get this thing working.
I'm trying my hardest to not process files (for a war project) once to
the target directory then AGAIN into the final assembly location.
So I'm using mvn assembly:directory but I don't see any of the tokens
expanded for the files when inside the descriptor, I have something like
this:
src/main/resources/java-properties
somedir
true
unix
true
hibernate.properties
The resulting hibernate.properties file still has ${stuff} type
properties left in there.
Any suggestions?
Fwd: Error building CAS with Maven 2.0.10
Hello Stephen, Maven 2.0.9 won't build CAS 3.3.1... I guess that the maven-war-plugin plugin is missing. But I don't know which place he's will be stay... Thanks -- Forwarded message -- From: Stephen Connolly Date: 2009/2/20 Subject: Re: Error building CAS with Maven 2.0.10 To: Maven Users List Does it build with 2.0.9? If it builds with 2.0.9 then you have a point. If it won't build with 2.0.9 then you have a regression -Stephen 2009/2/20 Vinicius Borges : > of course... but the error is in Maven > > thanks > > 2009/2/20 Rusty Wright : >> Have you tried the CAS mailing list? >> >> http://www.jasig.org/cas/mailing-lists >> >> >> Vinicius Borges wrote: >>> >>> Hello everybody, >>> >>> I want to build CAS project... but something is gonna wrong... >>> I builded CAS server 3.3.1 with Maven 2.0.10... >>> >>> [INFO] >>> >>> [INFO] Building JA-SIG CAS Web Application >>> [INFO]task-segment: [package, install] >>> [INFO] >>> >>> Downloading: >>> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom >>> 7K downloaded >>> Downloading: >>> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar >>> 72K downloaded >>> Downloading: >>> http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom >>> 165b downloaded >>> Downloading: >>> http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar >>> 4K downloaded >>> [INFO] >>> >>> [ERROR] FATAL ERROR >>> [INFO] >>> >>> [INFO] The PluginDescriptor for the plugin Plugin >>> [maven:maven-war-plugin] was not found. >>> [INFO] >>> >>> [INFO] Trace >>> java.lang.IllegalStateException: The PluginDescriptor for the plugin >>> Plugin [maven:maven-war-plugin] was not found. >>> at >>> org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) >>> at >>> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) >>> at >>> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:585) >>> 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: 10 minutes 18 seconds >>> [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 >>> [INFO] Final Memory: 25M/51M >>> [INFO] >>> >>> >>> What should be this? >>> Thanks! >>> >>> - >>> 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: Error building CAS
That's ok Wayne, Maybe the title of the email should be wrong. For your information, I have sent this question to the CAS forum, but the problem isn't with CAS. For that, I became here to find help... no problems. You can resolve my problem? Ok, I'll be satisfied, If not, thanks for your help and I will find more sources for my application... And I have used Maven for 2 days only. It's impossible that I turn expert in this little time... No more.. 2009/2/20 Wayne Fay : >> but the error is in Maven... if you take a look in the ERROR, you'll >> see what I talking about... > > If you are not at least a little bit competent in Maven, then it is > really not worth discussing this issue. Instead, you should send this > to the CAS User list and ask a CAS person who knows Maven to help. > > While Maven is reporting the problem, your issue is "CAS does not > build for me", and this is clearly an issue for the CAS Users and > Developers. > > Wayne > > - > 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: Error building CAS
Maven produces errors that look like something is wrong with maven but they can be coming from configuration errors in the pom.xml. In this case the lines [INFO] The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. are probably the clue to what's wrong. The java.lang.IllegalStateException could be considered a red herring. Vinicius Borges wrote: but the error is in Maven... if you take a look in the ERROR, you'll see what I talking about... 2009/2/20 Wayne Fay : I want to build CAS project... but something is gonna wrong... This is a "support" forum for users of Maven, not CAS. Please contact the CAS team and ask them to look into their issue. If this is a real problem, they will appreciate you telling them about it, and will probably get it fixed quickly. Wayne - 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: Error building CAS
> but the error is in Maven... if you take a look in the ERROR, you'll > see what I talking about... If you are not at least a little bit competent in Maven, then it is really not worth discussing this issue. Instead, you should send this to the CAS User list and ask a CAS person who knows Maven to help. While Maven is reporting the problem, your issue is "CAS does not build for me", and this is clearly an issue for the CAS Users and Developers. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error building CAS with Maven 2.0.10
Does it build with 2.0.9? If it builds with 2.0.9 then you have a point. If it won't build with 2.0.9 then you have a regression -Stephen 2009/2/20 Vinicius Borges : > of course... but the error is in Maven > > thanks > > 2009/2/20 Rusty Wright : >> Have you tried the CAS mailing list? >> >> http://www.jasig.org/cas/mailing-lists >> >> >> Vinicius Borges wrote: >>> >>> Hello everybody, >>> >>> I want to build CAS project... but something is gonna wrong... >>> I builded CAS server 3.3.1 with Maven 2.0.10... >>> >>> [INFO] >>> >>> [INFO] Building JA-SIG CAS Web Application >>> [INFO]task-segment: [package, install] >>> [INFO] >>> >>> Downloading: >>> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom >>> 7K downloaded >>> Downloading: >>> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar >>> 72K downloaded >>> Downloading: >>> http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom >>> 165b downloaded >>> Downloading: >>> http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar >>> 4K downloaded >>> [INFO] >>> >>> [ERROR] FATAL ERROR >>> [INFO] >>> >>> [INFO] The PluginDescriptor for the plugin Plugin >>> [maven:maven-war-plugin] was not found. >>> [INFO] >>> >>> [INFO] Trace >>> java.lang.IllegalStateException: The PluginDescriptor for the plugin >>> Plugin [maven:maven-war-plugin] was not found. >>> at >>> org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) >>> at >>> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) >>> at >>> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:585) >>> 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: 10 minutes 18 seconds >>> [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 >>> [INFO] Final Memory: 25M/51M >>> [INFO] >>> >>> >>> What should be this? >>> Thanks! >>> >>> - >>> 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: Error building CAS with Maven 2.0.10
of course... but the error is in Maven thanks 2009/2/20 Rusty Wright : > Have you tried the CAS mailing list? > > http://www.jasig.org/cas/mailing-lists > > > Vinicius Borges wrote: >> >> Hello everybody, >> >> I want to build CAS project... but something is gonna wrong... >> I builded CAS server 3.3.1 with Maven 2.0.10... >> >> [INFO] >> >> [INFO] Building JA-SIG CAS Web Application >> [INFO]task-segment: [package, install] >> [INFO] >> >> Downloading: >> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom >> 7K downloaded >> Downloading: >> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar >> 72K downloaded >> Downloading: >> http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom >> 165b downloaded >> Downloading: >> http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar >> 4K downloaded >> [INFO] >> >> [ERROR] FATAL ERROR >> [INFO] >> >> [INFO] The PluginDescriptor for the plugin Plugin >> [maven:maven-war-plugin] was not found. >> [INFO] >> >> [INFO] Trace >> java.lang.IllegalStateException: The PluginDescriptor for the plugin >> Plugin [maven:maven-war-plugin] was not found. >> at >> org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) >> at >> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) >> at >> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:585) >> 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: 10 minutes 18 seconds >> [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 >> [INFO] Final Memory: 25M/51M >> [INFO] >> >> >> What should be this? >> Thanks! >> >> - >> 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: Error building CAS
but the error is in Maven... if you take a look in the ERROR, you'll see what I talking about... 2009/2/20 Wayne Fay : >> I want to build CAS project... but something is gonna wrong... > > This is a "support" forum for users of Maven, not CAS. Please contact > the CAS team and ask them to look into their issue. If this is a real > problem, they will appreciate you telling them about it, and will > probably get it fixed quickly. > > Wayne > > - > 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: Error building CAS with Maven 2.0.10
Have you tried the CAS mailing list? http://www.jasig.org/cas/mailing-lists Vinicius Borges wrote: Hello everybody, I want to build CAS project... but something is gonna wrong... I builded CAS server 3.3.1 with Maven 2.0.10... [INFO] [INFO] Building JA-SIG CAS Web Application [INFO]task-segment: [package, install] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar 72K downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom 165b downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar 4K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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: 10 minutes 18 seconds [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 [INFO] Final Memory: 25M/51M [INFO] What should be this? Thanks! - 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: Error building CAS
> I want to build CAS project... but something is gonna wrong... This is a "support" forum for users of Maven, not CAS. Please contact the CAS team and ask them to look into their issue. If this is a real problem, they will appreciate you telling them about it, and will probably get it fixed quickly. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Error building CAS with Maven 2.0.10
Hello everybody, I want to build CAS project... but something is gonna wrong... I builded CAS server 3.3.1 with Maven 2.0.10... [INFO] [INFO] Building JA-SIG CAS Web Application [INFO]task-segment: [package, install] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar 72K downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom 165b downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar 4K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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: 10 minutes 18 seconds [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 [INFO] Final Memory: 25M/51M [INFO] What should be this? Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Error building CAS
Hello everybody, I want to build CAS project... but something is gonna wrong... [INFO] [INFO] Building JA-SIG CAS Web Application [INFO]task-segment: [package, install] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.jar 72K downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.pom 165b downloaded Downloading: http://repo1.maven.org/maven2/maven/maven-war-plugin/20030413.023708/maven-war-plugin-20030413.023708.jar 4K downloaded [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven:maven-war-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:327) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1239) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1005) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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: 10 minutes 18 seconds [INFO] Finished at: Fri Feb 20 13:20:56 BRST 2009 [INFO] Final Memory: 25M/51M [INFO] What should be this? Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mirror-any setup doesn't work with snapshots
On 20-Feb-09, at 4:05 AM, Olivier THIERRY wrote: Hi, I try to user mirror-any setup with Maven 2.0.10 and Artifactory 2.0.2 but it doesn't work with snapshots. Any time I have a dependency to a snapshot artifact in a POM file, it fails at resolving it. Here's a setup that works for Nexus (but generally applies): http://www.sonatype.com/books/nexus-book/reference/maven-sect-snapshot-repo.html For example : [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.andromda.maven.plugins ArtifactId: andromdapp-maven-plugin Version: 3.4-SNAPSHOT Reason: Unable to download the artifact from any repository org.andromda.maven.plugins:andromdapp-maven-plugin:pom:3.4-SNAPSHOT from the specified remote repositories: artifactory (http://intrabe:8080/artifactory/repo) But I can see this artifact using Artifactory web client, so it exists ! I configured mirror-any this way in Maven settings.xml file : artifactory * Horoquartz Repository http://intrabe:8080/artifactory/repo I see nothing in Artifactory logs, so it looks like no request is sent to Artifactory. Anyone has an idea what I did wrong ? Regards, Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com http://twitter.com/jvanzyl -- believe nothing, no matter where you read it, or who has said it, not even if i have said it, unless it agrees with your own reason and your own common sense. -- Buddha - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: How to use Checkstyle 5
See http://jira.codehaus.org/browse/MCHECKSTYLE-105 Lewis, Eric wrote: > Yep, I read it, I was just hoping... :-) > > Does anyone know whether Checkstyle 5 is on the Checkstyle Plugin's agenda? > > Best regards, > Eric > >> -Ursprüngliche Nachricht- >> Von: Wayne Fay [mailto:wayne...@gmail.com] >> Gesendet: Donnerstag, 19. Februar 2009 19:56 >> An: Maven Users List >> Betreff: Re: How to use Checkstyle 5 >> >>> Has anyone tried to use the Checkstyle plugin with >> Checkstyle 5 beta? >>> The plugin uses 4.4, but I tried the following hack >>> http://www.sonatype.com/people/2008/04/23/ >> Did you read this on that page: >> "That was easy, right? As long as the new version you have introduced >> is api compatible with the version the plugin was linked against, you >> should be good." >> >> The error indicates that Checkstyle 5 is probably not "api compatible" >> with Checkstyle 4. Therefore, you get breaks like you're experiencing. >> >> Wayne >> >> - >> 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 > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: scm plugin help please
Does not look like that is it: 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ *svn --non-interactive up At revision 5.* 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup --non-interactive 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $* svn up At revision 5.* 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Fri, Feb 20, 2009 at 9:44 AM, Mark Struberg wrote: > may this be a reincarnation of the --non-interactive bug with svn-1.5 on > MacOsX? > > http://jira.codehaus.org/browse/SCM-402 > > what says svn if you execute the SVN command with and without the > --non-interactive? > > txs and LieGrue, > strub > > --- Mick Knutson schrieb am Fr, 20.2.2009: > > > Von: Mick Knutson > > Betreff: scm plugin help please > > An: "maven" > > Datum: Freitag, 20. Februar 2009, 15:38 > > I am trying to use the scm plugin to perform an svn update. > > I can > > successfully run svn cleanup, svn up, and svn ci from the > > command line. But > > when I run a mvn scm:update -e I get an error saying my > > pom.xml is locked as > > shown below: > > > > > > *733...@d5400lpl: > > /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup > > > > 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom > > $ svn up > > At revision 5.* > > > > *733...@d5400lpl: > > /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ mvn > > scm:update -e* > > *+ Error stacktraces are turned on.* > > *[INFO] Scanning for projects...* > > *[INFO] Searching repository for plugin with prefix: > > 'scm'.* > > *WAGON_VERSION: 1.0-beta-2* > > *[INFO] > > * > > *[INFO] Building FXG:: POM* > > *[INFO]task-segment: [scm:update] (aggregator-style)* > > *[INFO] > > * > > *[INFO] [scm:update]* > > *[INFO] Executing: cmd.exe /X /C "svn > > --non-interactive update > > c:\opt\projects\grd\trunk\fxg-pom"* > > *[INFO] Working directory: > > c:\opt\projects\grd\trunk\fxg-pom* > > *[INFO] Svn command failed due to some locks in working > > copy. We try to run > > a 'svn cleanup'.* > > *[INFO] Executing: cmd.exe /X /C "svn"* > > *[INFO] Working directory: > > c:\opt\projects\grd\trunk\fxg-pom* > > *[ERROR] Provider message:* > > *[ERROR] The svn command failed.* > > *[ERROR] Command output:* > > *[ERROR] svn: Working copy > > 'c:\opt\projects\grd\trunk\fxg-pom' > > locked > > svn: run 'svn cleanup' to remove locks (type > > 'svn help cleanup' for details) > > Type 'svn help' for usage.* > > > > *[INFO] > > * > > *[ERROR] BUILD ERROR* > > *[INFO] > > * > > *[INFO] Command failed.The svn command failed.* > > *[INFO] > > * > > *[INFO] Trace* > > *org.apache.maven.lifecycle.LifecycleExecutionException: > > Command failed.The > > svn command failed.* > > *at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > > * > > *at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > > * > > *at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > > * > > *at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > > * > > *at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) > > * > > *at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > > * > > *at > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)* > > *at > > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)* > > *at > > org.apache.maven.cli.MavenCli.main(MavenCli.java:287)* > > *at > > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)* > > *at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > * > > *at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > * > > *at > > java.lang.reflect.Method.invoke(Method.java:
AW: scm plugin help please
may this be a reincarnation of the --non-interactive bug with svn-1.5 on MacOsX? http://jira.codehaus.org/browse/SCM-402 what says svn if you execute the SVN command with and without the --non-interactive? txs and LieGrue, strub --- Mick Knutson schrieb am Fr, 20.2.2009: > Von: Mick Knutson > Betreff: scm plugin help please > An: "maven" > Datum: Freitag, 20. Februar 2009, 15:38 > I am trying to use the scm plugin to perform an svn update. > I can > successfully run svn cleanup, svn up, and svn ci from the > command line. But > when I run a mvn scm:update -e I get an error saying my > pom.xml is locked as > shown below: > > > *733...@d5400lpl: > /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup > > 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom > $ svn up > At revision 5.* > > *733...@d5400lpl: > /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ mvn > scm:update -e* > *+ Error stacktraces are turned on.* > *[INFO] Scanning for projects...* > *[INFO] Searching repository for plugin with prefix: > 'scm'.* > *WAGON_VERSION: 1.0-beta-2* > *[INFO] > * > *[INFO] Building FXG:: POM* > *[INFO]task-segment: [scm:update] (aggregator-style)* > *[INFO] > * > *[INFO] [scm:update]* > *[INFO] Executing: cmd.exe /X /C "svn > --non-interactive update > c:\opt\projects\grd\trunk\fxg-pom"* > *[INFO] Working directory: > c:\opt\projects\grd\trunk\fxg-pom* > *[INFO] Svn command failed due to some locks in working > copy. We try to run > a 'svn cleanup'.* > *[INFO] Executing: cmd.exe /X /C "svn"* > *[INFO] Working directory: > c:\opt\projects\grd\trunk\fxg-pom* > *[ERROR] Provider message:* > *[ERROR] The svn command failed.* > *[ERROR] Command output:* > *[ERROR] svn: Working copy > 'c:\opt\projects\grd\trunk\fxg-pom' > locked > svn: run 'svn cleanup' to remove locks (type > 'svn help cleanup' for details) > Type 'svn help' for usage.* > > *[INFO] > * > *[ERROR] BUILD ERROR* > *[INFO] > * > *[INFO] Command failed.The svn command failed.* > *[INFO] > * > *[INFO] Trace* > *org.apache.maven.lifecycle.LifecycleExecutionException: > Command failed.The > svn command failed.* > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > * > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > * > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > * > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > * > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) > * > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > * > *at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)* > *at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)* > *at > org.apache.maven.cli.MavenCli.main(MavenCli.java:287)* > *at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)* > *at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > * > *at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)* > *Caused by: org.apache.maven.plugin.MojoExecutionException: > Command > failed.The svn command failed.* > *at > org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:400) > * > *at > org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:93)* > *at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > * > *at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > * > *... 16 more* > *[INFO] > * > *[INFO] Total time: 7 seconds* > *[INFO] Finished at: Fri Feb 20 09:34:57 EST 2009* > *[INFO] Final Memory: 8M/16M* > *[INFO] > * > > *733...@d5400lpl: > /cygdrive/c/opt/
scm plugin help please
I am trying to use the scm plugin to perform an svn update. I can successfully run svn cleanup, svn up, and svn ci from the command line. But when I run a mvn scm:update -e I get an error saying my pom.xml is locked as shown below: *733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn cleanup 733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ svn up At revision 5.* *733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $ mvn scm:update -e* *+ Error stacktraces are turned on.* *[INFO] Scanning for projects...* *[INFO] Searching repository for plugin with prefix: 'scm'.* *WAGON_VERSION: 1.0-beta-2* *[INFO] * *[INFO] Building FXG:: POM* *[INFO]task-segment: [scm:update] (aggregator-style)* *[INFO] * *[INFO] [scm:update]* *[INFO] Executing: cmd.exe /X /C "svn --non-interactive update c:\opt\projects\grd\trunk\fxg-pom"* *[INFO] Working directory: c:\opt\projects\grd\trunk\fxg-pom* *[INFO] Svn command failed due to some locks in working copy. We try to run a 'svn cleanup'.* *[INFO] Executing: cmd.exe /X /C "svn"* *[INFO] Working directory: c:\opt\projects\grd\trunk\fxg-pom* *[ERROR] Provider message:* *[ERROR] The svn command failed.* *[ERROR] Command output:* *[ERROR] svn: Working copy 'c:\opt\projects\grd\trunk\fxg-pom' locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) Type 'svn help' for usage.* *[INFO] * *[ERROR] BUILD ERROR* *[INFO] * *[INFO] Command failed.The svn command failed.* *[INFO] * *[INFO] Trace* *org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.The svn command failed.* *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) * *at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)* *at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)* *at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)* *at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)* *at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) * *at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)* *Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.The svn command failed.* *at org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java:400) * *at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:93)* *at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) * *... 16 more* *[INFO] * *[INFO] Total time: 7 seconds* *[INFO] Finished at: Fri Feb 20 09:34:57 EST 2009* *[INFO] Final Memory: 8M/16M* *[INFO] * *733...@d5400lpl: /cygdrive/c/opt/projects/grd/trunk/fxg-pom $* --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com ---
RE: Removing: jar from forked lifecycle, to prevent recursive invocation
bump... Is anyone able provide some insite here? It would be really nice to remove warnings such as this from my build ;-). --- Todd Thiessen > -Original Message- > From: Thiessen, Todd (BVW:9T16) > Sent: Wednesday, February 18, 2009 9:05 AM > To: 'Maven Users List' > Subject: RE: Removing: jar from forked lifecycle, to prevent > recursive invocation > > I am wondering if Brian, or any other Maven expert our there, > could explain how this warning could be avoided entirely. I > have looked into this at length when adding, for example, > source jars to my distribution. However, the warning always occurs. > > I have a pretty good understanding of why the warning occurs. > If you look at the documentation for the source plugin here: > > http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html > > You will notice in the fourth bullet it says: > > * Invokes the execution of the lifecycle phase > generate-sources prior to executing itself. > > Thus, if you attach this goal to your build, then if you > execute any phase at or above package (if you use the default > phase binding of package) then this plugin effectively runs > the lifecycle twice; once up to "generate-sources" when it > executes the goal, then again for your actual build. The > warning is just letting you know that running the lifecycle > twice isn't necessary since the "generate-sources" phase will > get executed via the execution of the package phase. > > I also understand that the goal is purposefully designed this > way so it can be called from the command line and still > behave as expected without having to explicitly generate > sources if any sources need to be generated. > > So I believe I understand the warning, but I would love to > properly configure the plugin such that it does not emmit > this warning when attaching the goal to your build. Or > perhaps this warning should simply be suppressed entirely > since Maven already seems to be aware of plugins which fork > their own lifecycle when bound to a phase of the lifecycle > and properly remove the extra fork. The warning seems to > cause more confusion than anything else. > > My best guess is that for now, this is just part of Maven's > core architecture and hasn't been important enough to change. > Some of this "may" be fixed in the 3.0 release but I can't be > sure of that. Hopefully some of the experts could comment further. > > --- > Todd Thiessen > > > > -Original Message- > > From: Brian E. Fox [mailto:bri...@reply.infinity.nu] > > Sent: Tuesday, February 17, 2009 7:31 PM > > To: Maven Users List > > Subject: RE: Removing: jar from forked lifecycle, to > prevent recursive > > invocation > > > > This means the plugin that caused the fork to occur is removed from > > that forked lifecycle so it doesn't fork again. > > > > -Original Message- > > From: Romain Gilles [mailto:romain.gil...@thomsonreuters.com] > > Sent: Tuesday, February 17, 2009 5:08 AM > > To: Maven Users List > > Subject: Removing: jar from forked lifecycle, to prevent recursive > > invocation > > > > > > Hi all, > > I have this message during my build process but I don't > understand it: > > > > invocation> > > > > It does not provide the name of the Jar, is there anybody that can > > help me, please? > > > > Romain. > > > > This email was sent to you by Thomson Reuters, the global news and > > information company. > > Any views expressed in this message are those of the individual > > sender, except where the sender specifically states them to be the > > views of Thomson Reuters. > > > > > > > > > - > > 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: Searching for Artifacts in maven
I wouldn't recommend using mvnbrowser, these guys were scraping the repository and bashing it hard. Essentially abusing the central repository. It's easy to setup Nexus and create your own federated search that is local to you. Or use repository.sonatype.org which is managed by the same people who manage central so we're not hogging all the resources to create an index. Really having your own local setup is ideal, or using the search capabilities in m2eclipse (m2eclipse.sonatype.org). On 20-Feb-09, at 5:56 AM, Nord, James wrote: Either use a managed proxy like nexus that has this functionality or try here http://www.mvnbrowser.com/artifacts-search.html /James -Original Message- From: Vishal Pahwa [mailto:vpa...@sapient.com] Sent: 20 February 2009 10:52 To: Maven Users List Subject: Searching for Artifacts in maven Hi As we know that in maven we used to address any artifact with the groupId and artifactId. Now if I just know which version of a specific artifact I need to use in my project, then what would be the best way to get to know the artifactId and the groupId with which this artifact would be available in any of the Maven mirrors so that I can add this dependency in pom.xml Regards Vishal ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS. To protect the environment please do not print this e-mail unless necessary. NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00 ** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com http://twitter.com/jvanzyl -- You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Filtering Out Dependency Classes
On Fri, Feb 20, 2009 at 5:36 AM, wrote: > Hi guys, > > I was wondering if any of you know how to tell Maven to ignore certain > classes within a dependency package. My Maven project needs part of the > dependency (3rd party software), but this dependency has other classes which > are used by Java when they should not. > > Namely it's the Web-logic JAR, and Java's XSLT transformer factory that are > encouraged in making my Friday longer than it should be :( I use the resources plugin to only copy 3rd party stuff from the repo into a staging folder. Then my assembly plugin pulls jars from there. http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html HTH, -Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Change the default output location of test resources
The reason why the resource:testResources is being run twice might be because > The goals that are configured will be added to the goals already bound to > the lifecycle from the packaging selected. > as documented in http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Plugins On the #maven IRC i did get some inputs about using an alternate approach: target/test-resources But i haven't yet been able to get this working. The target/test-resources is not created and the resources are not copied over. -- View this message in context: http://www.nabble.com/Change-the-default-output-location-of-test-resources-tp22097054p22119883.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 Eclipse plugin: How to include source path in .classpath?
Thanks Dirk! The plugin solved my problem. /Roland On Fri, Feb 20, 2009 at 11:20 AM, Dirk Olmes wrote: > Roland Bali wrote: > > Hi, > > > > I would like to add the following to my .classpath when running > > eclipse:eclipse. How can I do this? > > > > > > Use the build-helper plugin [1] to add the fixtures directory to your > sources. The maven-eclipse-plugin will pick it up when generating the > .classpath file. > > [1] http://mojo.codehaus.org/build-helper-maven-plugin/ > > HTH, > > -dirk > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Searching for Artifacts in maven
Try the Repositories tab. On Fri, Feb 20, 2009 at 10:18 PM, Vishal Pahwa wrote: > > Thanx for giving me the search link. > > Now that I know what is the groupId and artifactId of the particular > artifact. > > How can I get to know on which mirror this artifact is present so that I > can add that mirror url in my proxy apllication. > > Regards > > Vishal > > -Original Message- > From: Nord, James [mailto:jn...@nds.com] > Sent: Friday, February 20, 2009 4:26 PM > To: Maven Users List > Subject: RE: Searching for Artifacts in maven > > Either use a managed proxy like nexus that has this functionality or try > here > http://www.mvnbrowser.com/artifacts-search.html > > /James > > > -Original Message- > > From: Vishal Pahwa [mailto:vpa...@sapient.com] > > Sent: 20 February 2009 10:52 > > To: Maven Users List > > Subject: Searching for Artifacts in maven > > > > > > Hi > > > > As we know that in maven we used to address any artifact with > > the groupId and artifactId. > > > > Now if I just know which version of a specific artifact I > > need to use in my project, then what would be the best way to > > get to know the artifactId and the groupId with which this > > artifact would be available in any of the Maven mirrors so > > that I can add this dependency in pom.xml > > > > > > Regards > > > > Vishal > > > > > > > ** > This e-mail is confidential, the property of NDS Ltd and intended for the > addressee only. Any dissemination, copying or distribution of this message > or any attachments by anyone other than the intended recipient is strictly > prohibited. If you have received this message in error, please immediately > notify the postmas...@nds.com and destroy the original message. Messages > sent to and from NDS may be monitored. NDS cannot guarantee any message > delivery method is secure or error-free. Information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. > We do not accept responsibility for any errors or omissions in this message > and/or attachment that arise as a result of transmission. You should carry > out your own virus checks before opening any attachment. Any views or > opinions presented are solely those of the author and do not necessarily > represent those of NDS. > > To protect the environment please do not print this e-mail unless > necessary. > > NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 > 4EX, United Kingdom. A company registered in England and Wales Registered > no. 3080780 VAT no. GB 603 8808 40-00 > > ** > > - > 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: Searching for Artifacts in maven
Thanx for giving me the search link. Now that I know what is the groupId and artifactId of the particular artifact. How can I get to know on which mirror this artifact is present so that I can add that mirror url in my proxy apllication. Regards Vishal -Original Message- From: Nord, James [mailto:jn...@nds.com] Sent: Friday, February 20, 2009 4:26 PM To: Maven Users List Subject: RE: Searching for Artifacts in maven Either use a managed proxy like nexus that has this functionality or try here http://www.mvnbrowser.com/artifacts-search.html /James > -Original Message- > From: Vishal Pahwa [mailto:vpa...@sapient.com] > Sent: 20 February 2009 10:52 > To: Maven Users List > Subject: Searching for Artifacts in maven > > > Hi > > As we know that in maven we used to address any artifact with > the groupId and artifactId. > > Now if I just know which version of a specific artifact I > need to use in my project, then what would be the best way to > get to know the artifactId and the groupId with which this > artifact would be available in any of the Maven mirrors so > that I can add this dependency in pom.xml > > > Regards > > Vishal > > ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS. To protect the environment please do not print this e-mail unless necessary. NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00 ** - 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: Searching for Artifacts in maven
Either use a managed proxy like nexus that has this functionality or try here http://www.mvnbrowser.com/artifacts-search.html /James > -Original Message- > From: Vishal Pahwa [mailto:vpa...@sapient.com] > Sent: 20 February 2009 10:52 > To: Maven Users List > Subject: Searching for Artifacts in maven > > > Hi > > As we know that in maven we used to address any artifact with > the groupId and artifactId. > > Now if I just know which version of a specific artifact I > need to use in my project, then what would be the best way to > get to know the artifactId and the groupId with which this > artifact would be available in any of the Maven mirrors so > that I can add this dependency in pom.xml > > > Regards > > Vishal > > ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS. To protect the environment please do not print this e-mail unless necessary. NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00 ** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Searching for Artifacts in maven
Hi As we know that in maven we used to address any artifact with the groupId and artifactId. Now if I just know which version of a specific artifact I need to use in my project, then what would be the best way to get to know the artifactId and the groupId with which this artifact would be available in any of the Maven mirrors so that I can add this dependency in pom.xml Regards Vishal
Filtering Out Dependency Classes
Hi guys, I was wondering if any of you know how to tell Maven to ignore certain classes within a dependency package. My Maven project needs part of the dependency (3rd party software), but this dependency has other classes which are used by Java when they should not. Namely it's the Web-logic JAR, and Java's XSLT transformer factory that are encouraged in making my Friday longer than it should be :( Any help is would be really appreciated! Cheers. Fernando Álvarez
Re: Mirror-any setup doesn't work with snapshots
2009/2/20 Yoav Landman :
> Hi,
>
> Did you experience a different behavior with 2.0.9?
> Can you try explicitly overriding central and snapshots ("classic setup" -
> http://wiki.jfrog.org/confluence/display/RTF/Configuring+Artifacts+Resolution
> ).
>
> Yoav
>
> On Fri, Feb 20, 2009 at 11:05 AM, Olivier THIERRY > wrote:
>
>> Hi,
>>
>> I try to user mirror-any setup with Maven 2.0.10 and Artifactory 2.0.2
>> but it doesn't work with snapshots. Any time I have a dependency to a
>> snapshot artifact in a POM file, it fails at resolving it.
>>
>> For example :
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>>
>> [INFO] Failed to resolve artifact.
>>
>> GroupId: org.andromda.maven.plugins
>> ArtifactId: andromdapp-maven-plugin
>> Version: 3.4-SNAPSHOT
>>
>> Reason: Unable to download the artifact from any repository
>>
>> org.andromda.maven.plugins:andromdapp-maven-plugin:pom:3.4-SNAPSHOT
>>
>> from the specified remote repositories:
>> artifactory (http://intrabe:8080/artifactory/repo)
>>
>> But I can see this artifact using Artifactory web client, so it exists !
>>
>> I configured mirror-any this way in Maven settings.xml file :
>>
>>
>> artifactory
>> *
>> Horoquartz Repository
>> http://intrabe:8080/artifactory/repo
>>
>>
>> I see nothing in Artifactory logs, so it looks like no request is sent
>> to Artifactory.
>>
>> Anyone has an idea what I did wrong ?
>>
>> Regards,
>>
>> Olivier
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
Thanks for your response Yoav !
First, no different behaviour for Maven 2.0.9 or 2.0.10, same problem.
I have explicitely overriden snapshots and central repositories in my
pom.xml as you suggested and it works.
Actually that's the way I used to do it before upgrading to 2.0.10.
But I tried mirror-any feature to avoid this explicit overriding,
because I don't think it's a very good point to configure the same
entreprise repository url in both settings.xml and pom.xml. When I
discovered mirror-any feature I loved the idea that you setup a mirror
to artifactory once, and it will be used for all your Maven projects.
But maybe I misunderstood why mirror-any feature has been added ?
Regards,
Olivier
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Eclipse plugin: How to include source path in .classpath?
Roland Bali wrote: > Hi, > > I would like to add the following to my .classpath when running > eclipse:eclipse. How can I do this? > > Use the build-helper plugin [1] to add the fixtures directory to your sources. The maven-eclipse-plugin will pick it up when generating the .classpath file. [1] http://mojo.codehaus.org/build-helper-maven-plugin/ HTH, -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mirror-any setup doesn't work with snapshots
Hi,
Did you experience a different behavior with 2.0.9?
Can you try explicitly overriding central and snapshots ("classic setup" -
http://wiki.jfrog.org/confluence/display/RTF/Configuring+Artifacts+Resolution
).
Yoav
On Fri, Feb 20, 2009 at 11:05 AM, Olivier THIERRY wrote:
> Hi,
>
> I try to user mirror-any setup with Maven 2.0.10 and Artifactory 2.0.2
> but it doesn't work with snapshots. Any time I have a dependency to a
> snapshot artifact in a POM file, it fails at resolving it.
>
> For example :
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
>
> GroupId: org.andromda.maven.plugins
> ArtifactId: andromdapp-maven-plugin
> Version: 3.4-SNAPSHOT
>
> Reason: Unable to download the artifact from any repository
>
> org.andromda.maven.plugins:andromdapp-maven-plugin:pom:3.4-SNAPSHOT
>
> from the specified remote repositories:
> artifactory (http://intrabe:8080/artifactory/repo)
>
> But I can see this artifact using Artifactory web client, so it exists !
>
> I configured mirror-any this way in Maven settings.xml file :
>
>
> artifactory
> *
> Horoquartz Repository
> http://intrabe:8080/artifactory/repo
>
>
> I see nothing in Artifactory logs, so it looks like no request is sent
> to Artifactory.
>
> Anyone has an idea what I did wrong ?
>
> Regards,
>
> Olivier
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Exclude properties in certain situations
Just use a profile[1]. There is tons of information & posts out there about the possibilities :) Stefan [1] http://maven.apache.org/pom.html#Profiles On Fri, 20 Feb 2009 01:18:09 -0800 (PST) "Mathias P.W Nilsson" wrote: > > Hi, > > I'm using Spring, Eclipse and maven2 as build tool. In my development > environment I use a Spring property overrider to set certain properties for > my computer whereas my co-workers use their. > > The problem is when we do mvn clean:clean install. The my.properties is > included and will of course override spring. If I alter the pom file > > > false > src/main/resources > > **/my.properties > > > > The war file will be ok but when deployed with eclipse on tomcat the > my.properties will be exluded. Is there a way to include, exclude this file > in certain situations. Is pretty annoing to go back and comment out lines in > the pom for deployment. -- Mit freundlichen Grüßen, Stefan Seidel Software-Entwickler VUB Printmedia GmbH Chopinstraße 4, 04103 Leipzig tel.+49 (341) 9 60 50 93 fax.+49 (341) 9 60 50 92 mail. ssei...@vub.de web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Exclude properties in certain situations
Hi, I'm using Spring, Eclipse and maven2 as build tool. In my development environment I use a Spring property overrider to set certain properties for my computer whereas my co-workers use their. The problem is when we do mvn clean:clean install. The my.properties is included and will of course override spring. If I alter the pom file false src/main/resources **/my.properties The war file will be ok but when deployed with eclipse on tomcat the my.properties will be exluded. Is there a way to include, exclude this file in certain situations. Is pretty annoing to go back and comment out lines in the pom for deployment. -- View this message in context: http://www.nabble.com/Exclude-properties-in-certain-situations-tp22117356p22117356.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
Mirror-any setup doesn't work with snapshots
Hi, I try to user mirror-any setup with Maven 2.0.10 and Artifactory 2.0.2 but it doesn't work with snapshots. Any time I have a dependency to a snapshot artifact in a POM file, it fails at resolving it. For example : [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.andromda.maven.plugins ArtifactId: andromdapp-maven-plugin Version: 3.4-SNAPSHOT Reason: Unable to download the artifact from any repository org.andromda.maven.plugins:andromdapp-maven-plugin:pom:3.4-SNAPSHOT from the specified remote repositories: artifactory (http://intrabe:8080/artifactory/repo) But I can see this artifact using Artifactory web client, so it exists ! I configured mirror-any this way in Maven settings.xml file : artifactory * Horoquartz Repository http://intrabe:8080/artifactory/repo I see nothing in Artifactory logs, so it looks like no request is sent to Artifactory. Anyone has an idea what I did wrong ? Regards, Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How to use Checkstyle 5
Yep, I read it, I was just hoping... :-) Does anyone know whether Checkstyle 5 is on the Checkstyle Plugin's agenda? Best regards, Eric > -Ursprüngliche Nachricht- > Von: Wayne Fay [mailto:wayne...@gmail.com] > Gesendet: Donnerstag, 19. Februar 2009 19:56 > An: Maven Users List > Betreff: Re: How to use Checkstyle 5 > > > Has anyone tried to use the Checkstyle plugin with > Checkstyle 5 beta? > > > > The plugin uses 4.4, but I tried the following hack > > http://www.sonatype.com/people/2008/04/23/ > > Did you read this on that page: > "That was easy, right? As long as the new version you have introduced > is api compatible with the version the plugin was linked against, you > should be good." > > The error indicates that Checkstyle 5 is probably not "api compatible" > with Checkstyle 4. Therefore, you get breaks like you're experiencing. > > Wayne > > - > 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: Unable to attach assembly during release:perform.
Excellent! Thanks!
Reinhard Nägele wrote:
David,
I created a patch for the issue and attached it to the JIRA ticket you had
created.
http://jira.codehaus.org/browse/MRELEASE-415
Reinhard
-Original Message-
From: David C. Hicks [mailto:dhi...@i-hicks.org]
Sent: Thursday, February 19, 2009 5:56 PM
To: Maven Users List
Subject: Re: Unable to attach assembly during release:perform.
I mis-spoke, Reinhard. That fixes my problem!
I remembered, after the fact, that I had changed the assembly to run on
the "deploy" phase, yesterday. The assembly wasn't being created until
after the rest of the artifacts were already deployed. Changing that
back to the "package" phase made sure it was created prior to deployments.
Good call, again! I'd still call this a bug. :-)
Thanks,
Dave
David C. Hicks wrote:
Good catch, Reinhard! I took a brief look at the source code, but I
didn't have time to dig into it deeply.
I tried your suggestion and added a dummy profile to the parent
project. That got me half-way there. The ZIP file is actually built
now, but apparently it doesn't get attached to the result of the
module. Only the POM is added to the repository.
I'd call this a bug/defect. I guess I have two tasks, now.
1) Figure out how to get done what I need to get done.
2) Create a sample project and file it with a JIRA.
Thanks for the input,
Dave
Reinhard Nägele wrote:
I had kind of the same problem this week with our custom release
plugin. It works similar to the Maven release plugin in that it adds
the active profiles to the forked Maven process. Actually, I had
taken this code from the Release plugin.
The Release plugin gets the profile as follows:
List profiles = project.getActiveProfiles();
If you have a profile that is only defined in a child module, it
won't show up in that list. I'm not sure if this is a bug. Is this
method supposed to return all active profiles in the reactor? If so,
then there's a bug in the Release plugin. Should I open a JIRA ticket?
If fixed our custom plugin by adding the active profiles of all
reactor projects:
Set profileIds = new HashSet();
for (MavenProject rp : reactorProjects) {
List profiles = rp.getActiveProfiles();
for (Profile profile : profiles) {
profileIds.add(profile.getId());
}
}
So, in your case, it might help to add a dummy release profile to
your parent pom.
HTH,
Reinhard
-Original Message-
From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Thursday,
February 19, 2009 3:52 AM
To: Maven Users
Subject: Unable to attach assembly during release:perform.
Hi folks,
I've been working on this all day, and I'm no closer to getting it to
work than I was this morning. I hope someone has that little tid-bit
of information that I'm clearly missing.
I have a multi-module project that is distributed in the form of a
ZIP file. The assembly is built in a module of its own, with the
maven-assembly-plugin being bound to - originally the "package"
phase, but more recently the "deploy" phase. (I found in the
maven-release-plugin documentation that the release:perform goal
executes the deploy and site-deploy goals, only. Hence, the change
to the "deploy" phase.)
Additionally, the assembly plugin is located in a profile that I
activate when performing the release. This is meant to prevent this
step from executing when a developer does a build.
I can execute this over and over again and successfully build the ZIP
file in testing, but as soon as I execute using the release plugin's
release:perform goal, the building and deployment of the ZIP file is
skipped. I'm including the profile that contains my assembly plugin
configuration.
Thanks in advance,
Dave
PS - I added the specific version of assembly plugin because of
another problem I encountered for which I found a JIRA indicating
that something had broken in beta-2 that worked in beta-1 having to
do with attachments.
release
maven-assembly-plugin
2.2-beta-1
assembly.xml
make-assembly
deploy
attached
-
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...@ma
RE: Unable to attach assembly during release:perform.
David,
I created a patch for the issue and attached it to the JIRA ticket you had
created.
http://jira.codehaus.org/browse/MRELEASE-415
Reinhard
-Original Message-
From: David C. Hicks [mailto:dhi...@i-hicks.org]
Sent: Thursday, February 19, 2009 5:56 PM
To: Maven Users List
Subject: Re: Unable to attach assembly during release:perform.
I mis-spoke, Reinhard. That fixes my problem!
I remembered, after the fact, that I had changed the assembly to run on
the "deploy" phase, yesterday. The assembly wasn't being created until
after the rest of the artifacts were already deployed. Changing that
back to the "package" phase made sure it was created prior to deployments.
Good call, again! I'd still call this a bug. :-)
Thanks,
Dave
David C. Hicks wrote:
> Good catch, Reinhard! I took a brief look at the source code, but I
> didn't have time to dig into it deeply.
>
> I tried your suggestion and added a dummy profile to the parent
> project. That got me half-way there. The ZIP file is actually built
> now, but apparently it doesn't get attached to the result of the
> module. Only the POM is added to the repository.
>
> I'd call this a bug/defect. I guess I have two tasks, now.
> 1) Figure out how to get done what I need to get done.
> 2) Create a sample project and file it with a JIRA.
>
> Thanks for the input,
> Dave
>
>
> Reinhard Nägele wrote:
>> I had kind of the same problem this week with our custom release
>> plugin. It works similar to the Maven release plugin in that it adds
>> the active profiles to the forked Maven process. Actually, I had
>> taken this code from the Release plugin.
>>
>> The Release plugin gets the profile as follows:
>>
>> List profiles = project.getActiveProfiles();
>>
>> If you have a profile that is only defined in a child module, it
>> won't show up in that list. I'm not sure if this is a bug. Is this
>> method supposed to return all active profiles in the reactor? If so,
>> then there's a bug in the Release plugin. Should I open a JIRA ticket?
>>
>> If fixed our custom plugin by adding the active profiles of all
>> reactor projects:
>>
>> Set profileIds = new HashSet();
>> for (MavenProject rp : reactorProjects) {
>> List profiles = rp.getActiveProfiles();
>> for (Profile profile : profiles) {
>> profileIds.add(profile.getId());
>> }
>> }
>>
>> So, in your case, it might help to add a dummy release profile to
>> your parent pom.
>>
>> HTH,
>> Reinhard
>>
>>
>> -Original Message-
>> From: David C. Hicks [mailto:dhi...@i-hicks.org] Sent: Thursday,
>> February 19, 2009 3:52 AM
>> To: Maven Users
>> Subject: Unable to attach assembly during release:perform.
>>
>> Hi folks,
>>
>> I've been working on this all day, and I'm no closer to getting it to
>> work than I was this morning. I hope someone has that little tid-bit
>> of information that I'm clearly missing.
>>
>> I have a multi-module project that is distributed in the form of a
>> ZIP file. The assembly is built in a module of its own, with the
>> maven-assembly-plugin being bound to - originally the "package"
>> phase, but more recently the "deploy" phase. (I found in the
>> maven-release-plugin documentation that the release:perform goal
>> executes the deploy and site-deploy goals, only. Hence, the change
>> to the "deploy" phase.)
>>
>> Additionally, the assembly plugin is located in a profile that I
>> activate when performing the release. This is meant to prevent this
>> step from executing when a developer does a build.
>>
>> I can execute this over and over again and successfully build the ZIP
>> file in testing, but as soon as I execute using the release plugin's
>> release:perform goal, the building and deployment of the ZIP file is
>> skipped. I'm including the profile that contains my assembly plugin
>> configuration.
>>
>> Thanks in advance,
>> Dave
>>
>> PS - I added the specific version of assembly plugin because of
>> another problem I encountered for which I found a JIRA indicating
>> that something had broken in beta-2 that worked in beta-1 having to
>> do with attachments.
>>
>>
>>
>> release
>>
>>
>>
>> maven-assembly-plugin
>> 2.2-beta-1
>>
>> assembly.xml
>>
>>
>>
>> make-assembly
>> deploy
>>
>> attached
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
Matthieu Brouillard est absent(e).
Je serai absent(e) du 20/02/2009 au 22/02/2009. Je répondrai à votre message dès mon retour. I am actually out of office. I will answer you once I am back.
