Is it possible to have a shared component descriptor?
All, I have a set of files that I'd like included in all of our applications assembled artifact. Rather then having the XML copy and pasted in multiple locations I was wondering if I could there was a way to setup a shared component descriptor? I realize I could add a dependency on the project that houses the component descriptor, unpack it then include it from the assembly descriptor but I was wondering if there was another way to do it much like the shared assembly descriptor functionality (http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is it possible to have a shared component descriptor?
Ah, I forgot about the remote resources plugin. Thanks for the idea. I'll look into that. On 9/28/2010 10:39 AM, Anders Hammar wrote: Maybe this: http://maven.apache.org/plugins/maven-remote-resources-plugin/ /Anders On Tue, Sep 28, 2010 at 16:24, Michael Delaneymdela...@upromise.comwrote: All, I have a set of files that I'd like included in all of our applications assembled artifact. Rather then having the XML copy and pasted in multiple locations I was wondering if I could there was a way to setup a shared component descriptor? I realize I could add a dependency on the project that houses the component descriptor, unpack it then include it from the assembly descriptor but I was wondering if there was another way to do it much like the shared assembly descriptor functionality ( http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html ) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven war plugin adds some dependencies with unique timestamp.
All,
I have a war project that is coping some dependency artifacts to
WEB-INF/lib with the unique time stamp version (i.e.
myProject-1.0.0-20100920.110440-99.jar). I'd like to have the project
copy the artifact with the simple version (i.e.
myProject-1.0.0-SNAPSHOT.jar). I was looking at the configuration
'outputFileNameMapping' option but I can't seem to get that working
properly. I tried the following value
(@{artifact...@-@{version}@@{dashclassifie...@.@{extension}@) as per the
war documentation but as soon as it tries to process a artifact with a
classifier a 'org.apache.maven.lifecycle.LifecycleExecutionException'
exception (see Stack Trace below). If I remove @{dashClassifier?}@ out
of 'outputFileNameMapping' then it works unless there's a module with a
classifier then it causes different problem.
Anyone know how I can fix this?
[ Version Information ]
$ mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_21
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7 version: 6.1 arch: x86 Family: windows
Maven War plugin: 2.1-beta-1
[ Stack Trace ]
Embedded error: Invalid argument
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to copy
file for
artifact[com.mygroupid:project:jar:modconfig:1.0.0-SNAPSHOT:compile]
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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: Failed to
copy file for
artifact[com.mygroupid:project:jar:modconfig:1.0.0-SNAPSHOT:compile]
at
org.apache.maven.plugin.war.packaging.ArtifactsPackagingTask.performPackaging(ArtifactsPackagingTask.java:125)
at
org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.handleArtifacts(WarProjectPackagingTask.java:184)
at
org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.performPackaging(WarProjectPackagingTask.java:104)
at
org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:462)
at
org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:394)
at
org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:195)
at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:157)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: java.io.IOException: Invalid argument
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:396)
at java.io.File.getCanonicalPath(File.java:559)
at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:959)
at
org.apache.maven.plugin.war.packaging.AbstractWarPackagingTask.copyFile(AbstractWarPackagingTask.java:293)
at
org.apache.maven.plugin.war.packaging.AbstractWarPackagingTask$1.registered(AbstractWarPackagingTask.java:150)
at
org.apache.maven.plugin.war.util.WebappStructure.registerFile(WebappStructure.java:180)
at
org.apache.maven.plugin.war.packaging.AbstractWarPackagingTask.copyFile(AbstractWarPackagingTask.java:145)
at
webResources not copied during build on UNIX.
All,
I have a war project (by this I mean packaging type is 'war') that, in
the maven-war-plugin, I'm defining some web resources (see snipped
below). During a build on Windows the resources specified in the
'webResources' tag are copied over but during a build on UNIX (most
explicitly Solaris) the resources are not copied over. The paths do not
contain any Windows specific slashes and the case of the files is also
correct.
Anyone know what could be causing this?
We're using maven-war-plugin version 2.1-alpha-1 and
maven-resources-plugin 2.3.
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
filteringfalse/filtering
directory${basedir}/src/main/resources/templates/directory
!-- the list has a default value of ** --
includes
includeweb.xml/include
/includes
targetPathWEB-INF/templates/targetPath
/resource
/webResources
/configuration
/plugin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
I'm using Maven 2.2.1 and didn't upgrade to the new version of the project info reports and all of my site calls are broken with the same issue. On 5/20/2010 3:37 PM, Kalle Korhonen wrote: Thanks! I tried 2.2 with the site plugin (2.1), but I'm getting: [INFO] Trace java.lang.ArrayIndexOutOfBoundsException: 1 at org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791) which seems to be caused by: http://jira.codehaus.org/browse/DOXIA-215 Assuming the problem is that the site plugin uses an older version of doxia, is there a way to configure it use doxia 1.1 or is a new release of the site plugin required? Kalle On Thu, May 20, 2010 at 3:04 AM, Olivier Lamyol...@apache.org wrote: Hi, The Maven team is pleased to announce the release of the Maven 2.x Project Info Reports Plugin, version 2.2 NOTE : this version is site plugin 2.1+ required. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin, version 2.2 Bug : * [MPIR-150] - the dependency report ignores mirrors * [MPIR-159] - ZipException during mvn clean compile site * [MPIR-172] - Be sure that anchor are unique * [MPIR-174] - remove use of container.getLoggerManager() (to be compatible wih maven 3.x) * [MPIR-179] - Dependency File Details and Dependency Repository Locations tables have a border when rendered with maven-site-plugin 2.1 Improvement * [MPIR-137] - Dependency Locations should work with an intranet repository and restricted internet access * [MPIR-186] - Update location for Subversion Home page * [MPIR-189] - Allow configuration of mailing list header text. New Feature * [MPIR-170] - Create a module overview page ala m1 Task * [MPIR-101] - Update to Doxia 1.1 * [MPIR-173] - Review the Doxia Sink calls Enjoy, -- The Maven team - 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: Attached files not getting unique identifier when deployed
I tried this and the deployed jars still lacks the unique time stamp identifier. On 5/4/2010 2:39 PM, Marshall Schor wrote: Well, I was able to reproduce your problem, and then found a work-around for it... Here's the work-around: Change your POM from: plugin artifactIdmaven-jar-plugin/artifactId version2.2/version configuration classifierconfig/classifier /configuration /plugin to plugin artifactIdmaven-jar-plugin/artifactId version2.2/version executions execution iddefault-jar/id !-- special name for normal jar build -- goalsgoaljar/goal/goals configuration classifierconfig/classifier /configuration /execution /executions /plugin If you don't put in theid.../id with that name, you get 2 jars built - one by default without the classifier, plus the classifier. I don't know why this works, and the other one doesn't work. Maybe someone else can say... -Marshall On 5/4/2010 8:30 AM, Michael Delaney wrote: Sure. Please see the attached pom file. I do have a parent defined but it's there just to define release profiles as well as version information. No additional configuration (for the maven-jar-plugin) is in the parent pom. On 5/3/2010 7:53 PM, Marshall Schor wrote: it looks like your jar file has no classifier. A plain jar file is being uploaded. Can you post the part of the POM where you are defining the classifier artifact, and attaching it? -Marshall On 5/3/2010 7:09 PM, Michael Delaney wrote: All, I have a simple maven project that generates a jar file; with the classifier 'config'. When I call the 'deploy' phase, the pom file is uploaded with unique identifier (as expected) but the jar file is not (see examples below); the maven metadata is updated with the timestamp as well. When I put a dependency on the jar file, Maven can not resolve the artifact because it's looking for the jar file with the timestamp (as denoted by the maven-metadata file). Has anyone else seen this issue? I'm using Maven 2.2.1 on Solaris. [Example] -rw-r--r-- 1 archiva archiva 382 May 3 18:47 maven-metadata.xml -rw-r--r-- 1 archiva archiva 52 May 3 18:47 maven-metadata.xml.md5 -rw-r--r-- 1 archiva archiva 60 May 3 18:47 maven-metadata.xml.sha1 -rw-r--r-- 1 archiva archiva 1106 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom.sha1 -rw-r--r-- 1 archiva archiva 1106 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom.sha1 -rw-r--r-- 1 archiva archiva 4080 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar -rw-r--r-- 1 archiva archiva 32 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar.sha1 -rw-r--r-- 1 archiva archiva 757 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom.sha1 -rw-r--r-- 1 archiva archiva 4157 May 3 18:45 myApplication-1.0.0-SNAPSHOT-config.jar -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-SNAPSHOT-config.jar.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-SNAPSHOT-config.jar.sha1 [maven-metadata.xml] ?xml version=1.0 encoding=UTF-8? metadata groupIdcom.mycompany/groupId artifactIdmyApplication/artifactId version1.0.0-SNAPSHOT/version versioning snapshot buildNumber3/buildNumber timestamp20100503.224708/timestamp /snapshot lastUpdated20100503224708/lastUpdated /versioning /metadata - 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: Attached files not getting unique identifier when deployed
Ah okay, I see what you're getting at. I changed the packing type of the project to 'pom' and tried a 'mvn deploy'. As expected both the pom file and jar artifact (including classifier) were updated to my Repository with the unique identifiers. Looks like this solves my problem. I'm glad I can avoid creating two jars from a single project, that didn't feel right. Thanks for all your help, Marshall. On 5/4/2010 4:36 PM, Marshall Schor wrote: On 5/4/2010 3:31 PM, Michael Delaney wrote: I tried this and the deployed jars still lacks the unique time stamp identifier. Sorry, I guessed wrong. To fix, change the name in theid to something other than default-jar, such as my very own jar. Then it works (it did for me), except, that you'll get an extra artifact, the main one, which is a jar without a classifier. (To get rid of this extra jar, you could change the packaging type from jar to pom. This says that the main output of the project is the POM artifact, and the rest of the outputs are attachments to that.) Maven always wants to have 1 main artifact per project; the rest of the things are called attachments. The exception is the POM, which is always carried along, and isn't normally considered the main output artifact (except for packaging type=pom). See http://www.sonatype.com/people/2010/01/how-to-create-two-jars-from-one-project-and-why-you-shouldnt/ for a discussion of this. -Marshall On 5/4/2010 2:39 PM, Marshall Schor wrote: Well, I was able to reproduce your problem, and then found a work-around for it... Here's the work-around: Change your POM from: plugin artifactIdmaven-jar-plugin/artifactId version2.2/version configuration classifierconfig/classifier /configuration /plugin to plugin artifactIdmaven-jar-plugin/artifactId version2.2/version executions execution iddefault-jar/id!-- special name for normal jar build -- goalsgoaljar/goal/goals configuration classifierconfig/classifier /configuration /execution /executions /plugin If you don't put in theid.../id with that name, you get 2 jars built - one by default without the classifier, plus the classifier. I don't know why this works, and the other one doesn't work. Maybe someone else can say... -Marshall On 5/4/2010 8:30 AM, Michael Delaney wrote: Sure. Please see the attached pom file. I do have a parent defined but it's there just to define release profiles as well as version information. No additional configuration (for the maven-jar-plugin) is in the parent pom. On 5/3/2010 7:53 PM, Marshall Schor wrote: it looks like your jar file has no classifier. A plain jar file is being uploaded. Can you post the part of the POM where you are defining the classifier artifact, and attaching it? -Marshall On 5/3/2010 7:09 PM, Michael Delaney wrote: All, I have a simple maven project that generates a jar file; with the classifier 'config'. When I call the 'deploy' phase, the pom file is uploaded with unique identifier (as expected) but the jar file is not (see examples below); the maven metadata is updated with the timestamp as well. When I put a dependency on the jar file, Maven can not resolve the artifact because it's looking for the jar file with the timestamp (as denoted by the maven-metadata file). Has anyone else seen this issue? I'm using Maven 2.2.1 on Solaris. [Example] -rw-r--r-- 1 archiva archiva 382 May 3 18:47 maven-metadata.xml -rw-r--r-- 1 archiva archiva 52 May 3 18:47 maven-metadata.xml.md5 -rw-r--r-- 1 archiva archiva 60 May 3 18:47 maven-metadata.xml.sha1 -rw-r--r-- 1 archiva archiva 1106 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom.sha1 -rw-r--r-- 1 archiva archiva 1106 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom.sha1 -rw-r--r-- 1 archiva archiva 4080 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar -rw-r--r-- 1 archiva archiva 32 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar.sha1 -rw-r--r-- 1 archiva archiva 757 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom -rw-r--r
Attached files not getting unique identifier when deployed
All, I have a simple maven project that generates a jar file; with the classifier 'config'. When I call the 'deploy' phase, the pom file is uploaded with unique identifier (as expected) but the jar file is not (see examples below); the maven metadata is updated with the timestamp as well. When I put a dependency on the jar file, Maven can not resolve the artifact because it's looking for the jar file with the timestamp (as denoted by the maven-metadata file). Has anyone else seen this issue? I'm using Maven 2.2.1 on Solaris. [Example] -rw-r--r-- 1 archiva archiva 382 May 3 18:47 maven-metadata.xml -rw-r--r-- 1 archiva archiva 52 May 3 18:47 maven-metadata.xml.md5 -rw-r--r-- 1 archiva archiva 60 May 3 18:47 maven-metadata.xml.sha1 -rw-r--r-- 1 archiva archiva 1106 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-20100503.224504-1.pom.sha1 -rw-r--r-- 1 archiva archiva 1106 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-20100503.224537-2.pom.sha1 -rw-r--r-- 1 archiva archiva 4080 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar -rw-r--r-- 1 archiva archiva 32 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:47 myApplication-1.0.0-20100503.224708-3.jar.sha1 -rw-r--r-- 1 archiva archiva 757 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom -rw-r--r-- 1 archiva archiva 32 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:47 myApplication-1.0.0-20100503.224708-3.pom.sha1 -rw-r--r-- 1 archiva archiva 4157 May 3 18:45 myApplication-1.0.0-SNAPSHOT-config.jar -rw-r--r-- 1 archiva archiva 32 May 3 18:45 myApplication-1.0.0-SNAPSHOT-config.jar.md5 -rw-r--r-- 1 archiva archiva 40 May 3 18:45 myApplication-1.0.0-SNAPSHOT-config.jar.sha1 [maven-metadata.xml] ?xml version=1.0 encoding=UTF-8? metadata groupIdcom.mycompany/groupId artifactIdmyApplication/artifactId version1.0.0-SNAPSHOT/version versioning snapshot buildNumber3/buildNumber timestamp20100503.224708/timestamp /snapshot lastUpdated20100503224708/lastUpdated /versioning /metadata - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Activated profile on the existence of a file.
Opps, I knew I forgot something. I'm using Maven 2.2.1 On 4/2/2010 10:46 AM, Maven User wrote: What version of m2 are you using? On Thu, Apr 1, 2010 at 8:58 PM, Michael Delaneymdela...@upromise.comwrote: All, I have a parent pom, where I'm activating a profile based on the existence of the directory 'src/main/java'. I then have a multi module build where the children depend on the aforementioned parent pom. When I build the modules using an aggregator pom, the profile isn't activated correctly. When building the modules one-by-one, the profiles are activated as expected. Is this the expected behavior? I would figure that even if built via an aggregator pom, the profiles should be activated when the modules are built because the path is relative to the individual module. I've attached an example project to reflect what I'm talking about. - 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
Activated profile on the existence of a file.
All, I have a parent pom, where I'm activating a profile based on the existence of the directory 'src/main/java'. I then have a multi module build where the children depend on the aforementioned parent pom. When I build the modules using an aggregator pom, the profile isn't activated correctly. When building the modules one-by-one, the profiles are activated as expected. Is this the expected behavior? I would figure that even if built via an aggregator pom, the profiles should be activated when the modules are built because the path is relative to the individual module. I've attached an example project to reflect what I'm talking about. example.tar.gz Description: application/gzip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Setting up mirrors
All, Using Maven 2.2.1, I'm trying to setup (in the $M2_HOME/conf/settings.xml file) some mirrors. Looking at the documentation (http://maven.apache.org/guides/mini/guide-mirror-settings.html) for 2.2.1, it says that, in the mirrorOf tag, I can set repository includes and repository excludes but I can't seem to get it working as expected. Can anyone provide some help? mirrors mirror idnew-repository/id urlhttp://repo.upromise.com:8080/archiva/repository/new-repo/url mirrorOf!*,platform-release,platform-snapshot/mirrorOf /mirror mirror idfull/id urlhttp://repo.upromise.com:8080/archiva/repository/full/url mirrorOf*,!platform-release,!platform-snapshot/mirrorOf /mirror /mirrors - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Showing pom files in dependency tree.
All, I'm trying to diagnose an odd problem. The problem is on *some*, but not all, machines, one of our projects is trying to download an old retired snapshot build. I can't reproduce this locally but I can on our CI server. I checked the pom (top-level and parents) and check for this reference and it isn't there. I'm trying to figure out how this jar is being included when it shouldn't and I thought being able to see exactly what pom files are being loaded in would help. I already tried using the dependency plug-in to list the pom files but that doesn't work. I even searched through our Archiva repository for references and couldn't find anything that could cause this. Anyone have any ideas? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: Showing pom files in dependency tree.
Yes, I tried that. First, a wipe of just our artifacts (from the local repository) then a complete wipe(from the local repository). After both wipes, the artifact was still trying to get pulled down. Entner Harald wrote: Have you tried to delete the complete repository (.../.m2/repository), in which the false artifact is found? Maybe there are some legacy artifacts in it, which in return have dependencies on others and so on. -Ursprüngliche Nachricht- Von: Michael Delaney [mailto:mdela...@upromise.com] Gesendet: Montag, 5. Oktober 2009 16:56 An: users@maven.apache.org Betreff: Showing pom files in dependency tree. All, I'm trying to diagnose an odd problem. The problem is on *some*, but not all, machines, one of our projects is trying to download an old retired snapshot build. I can't reproduce this locally but I can on our CI server. I checked the pom (top-level and parents) and check for this reference and it isn't there. I'm trying to figure out how this jar is being included when it shouldn't and I thought being able to see exactly what pom files are being loaded in would help. I already tried using the dependency plug-in to list the pom files but that doesn't work. I even searched through our Archiva repository for references and couldn't find anything that could cause this. Anyone have any ideas? - 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: Showing pom files in dependency tree.
I just did that and no major differences. There were some differences but they were expected; location of the local repository and user name (those were the only two). Jörg Schaible wrote: Michael Delaney wrote at Montag, 5. Oktober 2009 16:55: All, I'm trying to diagnose an odd problem. The problem is on *some*, but not all, machines, one of our projects is trying to download an old retired snapshot build. I can't reproduce this locally but I can on our CI server. I checked the pom (top-level and parents) and check for this reference and it isn't there. I'm trying to figure out how this jar is being included when it shouldn't and I thought being able to see exactly what pom files are being loaded in would help. I already tried using the dependency plug-in to list the pom files but that doesn't work. I even searched through our Archiva repository for references and couldn't find anything that could cause this. Anyone have any ideas? run mvn help:effective-pom on both machines and diff the poutput. It may give you at least a hint, where the difference begins. - 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: Showing pom files in dependency tree.
For running 'help:effective-pom tests, no. I was running as myself (but using the same settings.xml file). Running as the same user the files are 100% equivalent; if you exclude the time stamp. I've also tested it using the same user as our CI server, manually, and same results. The manual build executes just fine the CI build fails trying to find an artifact it shouldn't be looking for. This is a problem with our C.I server, I just can't figure out where things are going wrong. Tang, Ray wrote: Are all the machine running the same user ID? Ray -Original Message- From: Michael Delaney [mailto:mdela...@upromise.com] Sent: Monday, October 05, 2009 10:57 AM To: Maven Users List Subject: Re: Showing pom files in dependency tree. I just did that and no major differences. There were some differences but they were expected; location of the local repository and user name (those were the only two). Jörg Schaible wrote: Michael Delaney wrote at Montag, 5. Oktober 2009 16:55: All, I'm trying to diagnose an odd problem. The problem is on *some*, but not all, machines, one of our projects is trying to download an old retired snapshot build. I can't reproduce this locally but I can on our CI server. I checked the pom (top-level and parents) and check for this reference and it isn't there. I'm trying to figure out how this jar is being included when it shouldn't and I thought being able to see exactly what pom files are being loaded in would help. I already tried using the dependency plug-in to list the pom files but that doesn't work. I even searched through our Archiva repository for references and couldn't find anything that could cause this. Anyone have any ideas? run mvn help:effective-pom on both machines and diff the poutput. It may give you at least a hint, where the difference begins. - 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 - 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: possible bug in maven antrun plugin
My apologies. This seems to have been resolved in maven-antrun-plugin
version 1.2
From: Michael Delaney [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 10:07 AM
To: Maven Users List
Subject: possible bug in maven antrun plugin
While trying to update our builds to run on Solaris, I was put some
logic in our ant scripts to enable cross platform execution (*.bat
versus *.sh ... etc). My initial idea was to rely on the ant property
os.name (which should be set by default). I wrote my ant script and
got it working perfectly, outside of Maven. Once I attempted to execute
the same ant script in Maven, I noticed that the property os.name was
not getting expanded at all.
I have included a small pom.xml and build.xml to show the behavior. Just
untar the archive, run 'mvn install' and then ant (no additional
parameters are required for either process). You will notice that the
property 'os.name' doesn't get expanded when called via Maven but does
when getting called via Ant.
I have a feeling this is a bug but I figured I could see if anything has
any additional input, or hacks, on this issue.
[ Maven AntRun output ]
init:
[echo] The following line should contain our OS name
[echo] ${os.name} == ${os.name}
[ Ant output ]
init:
[echo] The following line should contain our OS name
[echo] ${os.name} == Windows XP
Error while executing Maven javadoc
All, There seems to have been a new maven Javadoc plug-in uploaded that is causing some issues on our side. Is anyone else seeing this issue? We are using Maven 2.0.9 and this is encountered during the call 'mvn site install' [ Console Errors ] Downloading: http://build.corp.upromise.com:8080/archiva/repository/internal//org/apa che/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin -2.5-20080810.123323-30.pom 17K downloaded Downloading: http://build.corp.upromise.com:8080/archiva/repository/bertha//org/apach e/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2 .5-20080810.123323-30.jar Downloading: http://build.corp.upromise.com:8080/archiva/repository/internal//org/apa che/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin -2.5-20080810.123323-30.jar 114K downloaded [WARNING] Attempting to build MavenProject instance for Artifact (org.apache.maven.plugins:maven-javadoc-plugin:2.5-20080810.123323-30) of type: maven-plugin; constructing POM artifact instead. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Unresolved compilation problems: Syntax error, insert } to complete ClassBody The method append(StringBuffer, String, int) is undefined for the type HelpMojo ... repeating ... The method append(StringBuffer, String, int) is undefined for the type HelpMojo Syntax error, insert } to complete Block Syntax error, insert else Statement to complete IfStatement Syntax error, insert } to complete MethodBody Syntax error, insert else Statement to complete IfStatement Syntax error, insert ) to complete MethodInvocation Syntax error, insert ; to complete Statement Syntax error, insert } to complete Block
RE: Building Maven2
Mark, Thank you for the explanation that makes a lot of sense to me. Looks like I know what to do now. Mike P.S: Hope your team won! \o/ -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2008 7:05 PM To: Maven Users List Subject: RE: Building Maven2 Hi Michael! I did some research and compared the PerforceAddConsumer version you probably use (maven-scm-1.0) with the one from trunk: private static final String PATTERN = ^([^#]+)#1 - (.*); private static final String PATTERN = ^([^#]+)#(\\d+) - (.*); The 2nd line is from trunk (anyone knows the Jira of this change?). So the reg exp which parses the line has changed! Maybe this is the problem you have :( For looking at the RE quickly I would guess the original version only could handle #1 versions, whereas the newer RE also handles your #4. I hope my thoughts are clear enough on the very long cheer- and beerfull soccer-EM evening :) good night, strub PS: the good news: if I'm right, you do not have to change your perforce installation but only use the new perforce provider. the bad news: you have to use the new perforce provider ;) --- Mark Struberg [EMAIL PROTECTED] schrieb am Sa, 14.6.2008: Von: Mark Struberg [EMAIL PROTECTED] Betreff: RE: Building Maven2 An: Maven Users List users@maven.apache.org Datum: Samstag, 14. Juni 2008, 0:32 Hi Michael! You don't need to build the whole maven2 stuff. My goal was to check if your perforce version generates slightly different logs than the one the maven-scm-provider-perforce was programmed with. Please see the following debug output files and compare them with the propriate output from your p4: http://svn.apache.org/repos/asf/maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/test/resources/perforce/ The tests of a SCM provider can be separated into 2 categories 1.) tests which are run against pre generated output files (like the ones above) 2.) TCK tests which run real use cases. For this test cases, the PerforceAddConsumer has to parse the output of the real p4 command! That's what may fail on your computer. I hope this explains why I asked you to run the tests, and which part is relevant and which not. For not loosing the context, I copy the exception from your mvn release with your p4 installation from your previous post (titled Release plugin questions): Caused by: java.lang.IllegalStateException: Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add at org.apache.maven.scm.provider.perforce.command.add.PerforceAddConsumer.consumeLine(PerforceAddConsumer.java:79) at org.apache.maven.scm.provider.perforce.command.add.PerforceAddCommand.executeAddCommand(PerforceAddCommand.java:63) At least this would be the first point to look at for searching the source of the problem. First guess: either p4 is old, or the scm-provider is old. Which version are you using? This may also be a line delimiter problem or other wired stuff ... LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Fr, 13.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: RE: Building Maven2 An: Maven Users List users@maven.apache.org Datum: Freitag, 13. Juni 2008, 16:58 Wayne, Well, I am trying to debug a possible issue with the Perforce SCM provider. I was asked to build run units tests against the Perforce SCM provider. Rather then just attempt to build then post errors that ended up being an issue with my environment, I decided it would be a good idea to build Maven 2 first to validate the environment. That way if any issue were found with the Perforce SCM provider, I could at least say that know my environment is good (or should be). Mike D. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2008 10:53 AM To: Maven Users List Subject: Re: Building Maven2 If you don't mind me asking, why are you trying to build Maven? Just for fun; because corporate says we have to be able to build everything (including our tools) from scratch; some other reason; etc? Wayne On 6/13/08, Michael Delaney [EMAIL PROTECTED] wrote: Ram, I was trying to build everything, I went into the root of the Maven 2 source distribution and executed bootstrap.bat. The steps were as follows: cd /d C:\tmp\maven-2.0.9-src\maven-2.0.9-src set M2_HOME=c:\apache-maven-2.0.9 set PATH=%M2_HOME%\bin;%PATH% bootstrap.bat The documentation I followed is listed at http://maven.apache.org/guides/development/guide-building-m2.html, and I was using the section Building Maven 2.0 Without Maven Installed. Here is a print out of the relevant environment variables JAVA_HOME=c:\Program Files\Java\jdk1.5.0_13 M2_HOME=c:\tmp\apache
RE: Building Maven2
Ram,
I was trying to build everything, I went into the root of the Maven 2
source distribution and executed bootstrap.bat. The steps were as
follows:
cd /d C:\tmp\maven-2.0.9-src\maven-2.0.9-src
set M2_HOME=c:\apache-maven-2.0.9
set PATH=%M2_HOME%\bin;%PATH%
bootstrap.bat
The documentation I followed is listed at
http://maven.apache.org/guides/development/guide-building-m2.html, and I
was using the section Building Maven 2.0 Without Maven Installed.
Here is a print out of the relevant environment variables
JAVA_HOME=c:\Program Files\Java\jdk1.5.0_13
M2_HOME=c:\tmp\apache-maven-2.0.9
-Original Message-
From: RAM [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2008 4:11 AM
To: Maven Users List
Subject: Re: Building Maven2
The error message is little bit confusing :Null Pointer Exception in
thread
main. What are you trying to build?
I did the following setup and its working fine for me:
M2_HOME = D:\apache-maven-2.0.9
JAVA_HOME = {Here the *JDK* Path] Remember Maven doesnt work properly
with
JRE
PATH: %M2_HOME%/bin
Just run mvn --version and we are good to go.
If you are getting the version printed as 2.0.9, its correctly
installed.
Also, if you can forward the apache link you are talking about (where
you
got the example), I can look into that.
Thanks Regards,
Ram
On 6/12/08, Michael Delaney [EMAIL PROTECTED] wrote:
All,
I am trying to build Maven 2.0.9 from the source, as found on the
Apache
site. I went through the necessary steps of setting M2_HOME to a valid
name (M2_HOME=c:\tmp\apache-maven-2.0.9) and adding M2_HOME to my
windows path (PATH=%M2_HOME%\bin;%PATH%) as per the documentation.
However, when I try to build I get an error. This is my first time
trying to build Maven2 so it's possible I did something stupid but I
don't know what.
Can anyone help shed some light on this?
[ Command Output ]
Building project in
C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven
--
Cleaning C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven\target...
Compiling sources ...
Packaging resources ...
Packaging
C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven\target\apache-maven.
jar ...
--
Exception in thread main java.lang.NullPointerException
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.createInstallati
on(BootstrapInstaller.java:254)
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.run(BootstrapIns
taller.java:136)
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.main(BootstrapIn
staller.java:91)
---
BUILD FAILED
---
C:\tmp\maven-2.0.9-src\maven-2.0.9-src
Mike D.
--
Thanks
Ram
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Building Maven2
Wayne,
Well, I am trying to debug a possible issue with the Perforce SCM
provider. I was asked to build run units tests against the Perforce
SCM provider. Rather then just attempt to build then post errors that
ended up being an issue with my environment, I decided it would be a
good idea to build Maven 2 first to validate the environment. That way
if any issue were found with the Perforce SCM provider, I could at least
say that know my environment is good (or should be).
Mike D.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2008 10:53 AM
To: Maven Users List
Subject: Re: Building Maven2
If you don't mind me asking, why are you trying to build Maven? Just
for fun; because corporate says we have to be able to build everything
(including our tools) from scratch; some other reason; etc?
Wayne
On 6/13/08, Michael Delaney [EMAIL PROTECTED] wrote:
Ram,
I was trying to build everything, I went into the root of the Maven 2
source distribution and executed bootstrap.bat. The steps were as
follows:
cd /d C:\tmp\maven-2.0.9-src\maven-2.0.9-src
set M2_HOME=c:\apache-maven-2.0.9
set PATH=%M2_HOME%\bin;%PATH%
bootstrap.bat
The documentation I followed is listed at
http://maven.apache.org/guides/development/guide-building-m2.html, and
I
was using the section Building Maven 2.0 Without Maven Installed.
Here is a print out of the relevant environment variables
JAVA_HOME=c:\Program Files\Java\jdk1.5.0_13
M2_HOME=c:\tmp\apache-maven-2.0.9
-Original Message-
From: RAM [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2008 4:11 AM
To: Maven Users List
Subject: Re: Building Maven2
The error message is little bit confusing :Null Pointer Exception in
thread
main. What are you trying to build?
I did the following setup and its working fine for me:
M2_HOME = D:\apache-maven-2.0.9
JAVA_HOME = {Here the *JDK* Path] Remember Maven doesnt work properly
with
JRE
PATH: %M2_HOME%/bin
Just run mvn --version and we are good to go.
If you are getting the version printed as 2.0.9, its correctly
installed.
Also, if you can forward the apache link you are talking about (where
you
got the example), I can look into that.
Thanks Regards,
Ram
On 6/12/08, Michael Delaney [EMAIL PROTECTED] wrote:
All,
I am trying to build Maven 2.0.9 from the source, as found on the
Apache
site. I went through the necessary steps of setting M2_HOME to a
valid
name (M2_HOME=c:\tmp\apache-maven-2.0.9) and adding M2_HOME to my
windows path (PATH=%M2_HOME%\bin;%PATH%) as per the documentation.
However, when I try to build I get an error. This is my first time
trying to build Maven2 so it's possible I did something stupid but I
don't know what.
Can anyone help shed some light on this?
[ Command Output ]
Building project in
C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven
--
Cleaning
C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven\target...
Compiling sources ...
Packaging resources ...
Packaging
C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven\target\apache-maven.
jar ...
--
Exception in thread main java.lang.NullPointerException
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.createInstallati
on(BootstrapInstaller.java:254)
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.run(BootstrapIns
taller.java:136)
at
org.apache.maven.bootstrap.installer.BootstrapInstaller.main(BootstrapIn
staller.java:91)
---
BUILD FAILED
---
C:\tmp\maven-2.0.9-src\maven-2.0.9-src
Mike D.
--
Thanks
Ram
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Building Maven2
All, I am trying to build Maven 2.0.9 from the source, as found on the Apache site. I went through the necessary steps of setting M2_HOME to a valid name (M2_HOME=c:\tmp\apache-maven-2.0.9) and adding M2_HOME to my windows path (PATH=%M2_HOME%\bin;%PATH%) as per the documentation. However, when I try to build I get an error. This is my first time trying to build Maven2 so it's possible I did something stupid but I don't know what. Can anyone help shed some light on this? [ Command Output ] Building project in C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven -- Cleaning C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven\target... Compiling sources ... Packaging resources ... Packaging C:\tmp\maven-2.0.9-src\maven-2.0.9-src\apache-maven\target\apache-maven. jar ... -- Exception in thread main java.lang.NullPointerException at org.apache.maven.bootstrap.installer.BootstrapInstaller.createInstallati on(BootstrapInstaller.java:254) at org.apache.maven.bootstrap.installer.BootstrapInstaller.run(BootstrapIns taller.java:136) at org.apache.maven.bootstrap.installer.BootstrapInstaller.main(BootstrapIn staller.java:91) --- BUILD FAILED --- C:\tmp\maven-2.0.9-src\maven-2.0.9-src Mike D.
RE: Release plugin questions
. at org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.addReleasePomsToScm(GenerateReleasePomsPhase.java:197) at org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.generateReleasePoms(GenerateReleasePomsPhase.java:133) at org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.execute(GenerateReleasePomsPhase.java:106) at org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.execute(GenerateReleasePomsPhase.java:93) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:136) ... 18 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:62) at org.apache.maven.scm.provider.perforce.PerforceScmProvider.add(PerforceScmProvider.java:167) at org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProvider.java:145) at org.apache.maven.scm.provider.AbstractScmProvider.add(AbstractScmProvider.java:125) at org.apache.maven.shared.release.phase.GenerateReleasePomsPhase.addReleasePomsToScm(GenerateReleasePomsPhase.java:188) ... 25 more Caused by: java.lang.IllegalStateException: Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add at org.apache.maven.scm.provider.perforce.command.add.PerforceAddConsumer.consumeLine(PerforceAddConsumer.java:79) at org.apache.maven.scm.provider.perforce.command.add.PerforceAddCommand.executeAddCommand(PerforceAddCommand.java:63) at org.apache.maven.scm.command.add.AbstractAddCommand.executeCommand(AbstractAddCommand.java:45) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58) ... 29 more [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Wed Jun 11 11:27:54 EDT 2008 [INFO] Final Memory: 8M/127M [INFO] -Original Message- From: Bracewell, Robert [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 5:12 AM To: Maven Users List Subject: RE: Release plugin questions Try the following command sequence to ensure your environment is clean: mvn -e -X release:clean clean mvn -e -X release:prepare -DdryRun=true mvn -e -X release:clean clean mvn -e -X release:prepare The -e and -X should hopefully give some more output re error conditions -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: 10 June 2008 17:01 To: Maven Users List Subject: RE: Release plugin questions Sorry, I am still getting the same error when I add that to the pom.xml file. -Original Message- From: Bracewell, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 11:28 AM To: Maven Users List Subject: RE: Release plugin questions Try specifying the developerConnection, e.g., !-- P4 Location -- scm connectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/connection developerConnectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/developerConnection /scm -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: 10 June 2008 15:20 To: Maven Users List Subject: RE: Release plugin questions Yes, it does have the scm section, as defined by http://maven.apache.org/scm/perforce.html. project ... scm connection scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils /connection /scm ... /project -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:15 AM To: Maven Users List Subject: AW: Release plugin questions Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via
RE: Release plugin questions
I wish I was using the latest version of Perforce, but sadly that is not the case. I am currently using version 2005.2/104598 (which is very old). I will build the Perforce scm provider to see what unit tests, if any, fail on my machine. Mike D. -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 12:04 PM To: Maven Users List Subject: RE: Release plugin questions It seems that the perforce consumer for the add command cannot parse the result it gets from perforce //depot/sandboxes/mdelaney/utils/release-pom.xml#4 ? Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add at org.apache.maven.scm.provider.perforce.command.add. PerforceAddConsumer.consumeLine(PerforceAddConsumer.java:79) Which perforce version do you use? maybe our maven-scm-provider-perforce is not compatible with the latest p4 version? Try to run the perforce commands the debug log shows you, or even better, try to build the perforce scm provider at your workstation (with -Ptck to run all the TCK tests). I have not looked at the p4 provider code yet, but there should be unit tests which have to fail on your computer. If not we have to add them ;) txs, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Mi, 11.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: RE: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Mittwoch, 11. Juni 2008, 17:45 I executed the commands in the order below and still getting the error. I have pasted the extended output below for your review. [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-7:prepare' -- [DEBUG] (f) addSchema = true [DEBUG] (f) allowTimestampedSnapshots = false [DEBUG] (f) autoVersionSubmodules = false [DEBUG] (s) basedir = C:\work\sandboxes\mdelaney\utils [DEBUG] (f) commitByProject = false [DEBUG] (f) dryRun = false [DEBUG] (f) generateReleasePoms = true [DEBUG] (f) password = [p4-password] [DEBUG] (f) pomFileName = release-pom.xml [DEBUG] (f) preparationGoals = clean verify [DEBUG] (f) project = MavenProject: proj:proj-utils:1.2-SNAPSHOT @ C:\work\sandboxes\mdelaney\utils\pom.xml [DEBUG] (f) reactorProjects = [MavenProject: proj:proj-utils:1.2-SNAPSHOT @ C:\work\sandboxes\mdelaney\utils\pom.xml] [DEBUG] (f) resume = true [DEBUG] (f) scmCommentPrefix = [maven-release-plugin] [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) updateDependencies = true [DEBUG] (f) useEditMode = false [DEBUG] (f) username = [p4-username] [DEBUG] -- end configuration -- [INFO] [release:prepare] [DEBUG] release.properties not found - using empty properties [INFO] Verifying that there are no local modifications... [DEBUG] SCM path in pom: //depot/sandboxes/mdelaney/utils [DEBUG] Executing: p4 -p localhost:1666 -u [p4-username] -P where C:\work\sandboxes\mdelaney\utils\pom.xml [DEBUG] //depot/sandboxes/mdelaney/utils/pom.xml //mdelaney-default/sandboxes/mdelaney/utils/pom.xml c:\work\sandboxes\mdelaney\utils\pom.xml [DEBUG] Actual POM location: //depot/sandboxes/mdelaney/utils [DEBUG] Executing p4 -d C:\work\sandboxes\mdelaney\utils -p localhost:1666 -u [p4-username] -P opened //depot/sandboxes/mdelaney/utils/... [INFO] Checking dependencies and plugins for snapshots ... [INFO] Transforming 'Proj Utils'... [DEBUG] No SCM translator found - skipping rewrite [DEBUG] Executing p4 -d C:\work\sandboxes\mdelaney\utils -p localhost:1666 -u [p4-username] -P edit pom.xml [INFO] Generating release POMs... [INFO] Generating release POM for 'Proj Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. 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
Release plugin questions
All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command.
RE: Release plugin questions
Yes, it does have the scm section, as defined by http://maven.apache.org/scm/perforce.html. project ... scm connection scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils /connection /scm ... /project -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:15 AM To: Maven Users List Subject: AW: Release plugin questions Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release plugin questions
Sorry, I am still getting the same error when I add that to the pom.xml file. -Original Message- From: Bracewell, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 11:28 AM To: Maven Users List Subject: RE: Release plugin questions Try specifying the developerConnection, e.g., !-- P4 Location -- scm connectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/connection developerConnectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/developerConnection /scm -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: 10 June 2008 15:20 To: Maven Users List Subject: RE: Release plugin questions Yes, it does have the scm section, as defined by http://maven.apache.org/scm/perforce.html. project ... scm connection scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils /connection /scm ... /project -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:15 AM To: Maven Users List Subject: AW: Release plugin questions Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Upgrading Maven 2.0.5 - 2.0.9
Brian,
Sure ... please see the text below.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO]
[INFO] Building Content Administrator APP
[INFO]task-segment: [dependency:analyze]
[INFO]
[INFO] Preparing dependency:analyze
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
for updates from REPO
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
for updates from maven-repo1
[INFO] Ignoring available plugin update: 2.2 as it requires Maven
version 2.0.6
[INFO] Ignoring available plugin update: 2.4 as it requires Maven
version 2.0.8
[INFO] Ignoring available plugin update: 2.3 as it requires Maven
version 2.0.6
[WARNING]
Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
local scope 'provided' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove
the local scope.
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] Expanding: JAR_FILES
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [dependency:analyze]
[INFO] Used declared dependencies:
[INFO]atg:dss-classes:jar:2006.3:provided
[INFO]lty:lty-utils:jar:3.0.1.2:compile
[INFO]atg.publishing:base:jar:2006.3.P2:compile
[INFO]taglibs:standard:jar:1.1.2:provided
[INFO]atg:webui-classes:jar:2006.3.P2:compile
[INFO]junit:junit:jar:4.0:compile
[INFO]jboss:system:jar:3.2:compile
[INFO]jboss:common:jar:1.0:compile
[INFO]atg:das-servlet:jar:2006.3:provided
[INFO]atg:pubportlet-classes:jar:2006.3.P2:compile
[INFO]apache:axis:jar:1.4:compile
[INFO]jboss:jboss-j2ee:jar:4.0.4.GA:provided
[INFO]atg:dps-classes:jar:2006.3.P2:provided
[INFO]atg:das-classes:jar:2006.3.P2:provided
[INFO]atg:bizui-classes:jar:2006.3.P2:compile
[INFO]jboss:jmx:jar:1.0:compile
[INFO] Used undeclared dependencies:
[WARNING]commons-fileupload:commons-fileupload:jar:1.0:provided
[INFO] Unused declared dependencies:
[INFO]jakarta-poi:jakarta-poi:jar:1.5.1:compile
[INFO]commons-discovery:commons-discovery:jar:0.2:compile
[INFO]oracle:aq:jar:1.0:compile
[INFO]gnu:regexp:jar:x:compile
[INFO]oracle:jdbc:jar:10.0:compile
[INFO]lty:lty-utils-resources:jar:1.0.0.16:compile
[INFO]jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
[INFO]velocity:velocity:jar:1.2:compile
[INFO]castor:castor_xml:jar:0.9.4.3:compile
[INFO]jboss:deploy:jar:1.0:compile
[INFO]org.apache:axis:jar:1.4:compile
[INFO]castor:castor:jar:0.9.4.3:compile
[INFO]geophile:jdbcwrapper:jar:1.0:compile
[INFO]aspectwerkz:aspectwerkz:jar:1.1:compile
[INFO]cactus-support:aspectjrt:jar:1.2.1:compile
[INFO]lty:capi:jar:1.2.0.27:compile
[INFO]xalan:xalan:jar:2.7.0:compile
[INFO]commons-net:commons-net:jar:1.3.0:compile
[INFO]com:oroinc:jar:1.0:compile
[INFO]commons-validator:commons-validator:jar:1.1.4:compile
[INFO]cactus-support:cactus:jar:1.7.2:compile
[INFO]xerces:xercesImpl:jar:2.8.0:compile
[WARNING] Potential problems discovered.
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO]Nothing in DepMgt.
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 5 minutes 2 seconds
[INFO] Finished at: Wed May 28 10:38:46 EDT 2008
[INFO] Final Memory: 17M/127M
[INFO]
C:\work\up-svcs\lty\rel\LTY-R63.0\frontoffice\caApp
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2008 5:57 PM
To: Maven Users List
Subject: RE: Upgrading Maven 2.0.5 - 2.0.9
Can you show the full output of running the command from the CLI?
-Original Message-
From: Michael Delaney [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2008 4:41 PM
To: Maven Users List
Subject: Upgrading Maven 2.0.5 - 2.0.9
All,
I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
documentation that said that there were some dependency sanity checks
one should do before upgrading to the latest version of Maven from 2.0.6
or earlier (the page I am referring to is located at
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
ng-dependencies.html).
On the page pasted above, it says to run the Maven dependency analyzer
to check that everything is okay with how your dependencies are being
RE: Upgrading Maven 2.0.5 - 2.0.9
I was basing my findings on the output where Maven stated Potential
problems discovered. Is Maven just referring to the Used undeclared
dependencies and Unused declared dependencies sections?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2008 11:03 AM
To: Maven Users List
Subject: Re: Upgrading Maven 2.0.5 - 2.0.9
I don't see any errors here. What errors do you mean?
There are a few libs you have a dependency on but don't appear to be
using. So you could reduce the size of your app by getting rid of these
(as long as you aren't using Class.forName or META-INF/services or
similar to load them by reflection, which this tool obviously can't
detect). So you are warned to look into this.
And there is the findbugs:annotations issue, where some dependency wants
that jar bundled with the app, but you (or some other dependency) has
said that the jar will be provided at runtime. If the system into
which you deploy this code *really* has that already in the classpath,
then fine. Otherwise you need to fix the declaration that is forcing its
scope to provided. So you are warned to look into this.
Neither is *definitely* a problem, and neither seems to be a *change*
that upgrading maven will introduce. Instead they appear to be issues
that your code has always had.
Regards,
Simon
Michael Delaney schrieb:
Brian,
Sure ... please see the text below.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO]
[INFO] Building Content Administrator APP
[INFO]task-segment: [dependency:analyze]
[INFO]
[INFO] Preparing dependency:analyze
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
for updates from REPO
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
for updates from maven-repo1
[INFO] Ignoring available plugin update: 2.2 as it requires Maven
version 2.0.6
[INFO] Ignoring available plugin update: 2.4 as it requires Maven
version 2.0.8
[INFO] Ignoring available plugin update: 2.3 as it requires Maven
version 2.0.6
[WARNING]
Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
local scope 'provided' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or
remove
the local scope.
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] Expanding: JAR_FILES
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [dependency:analyze]
[INFO] Used declared dependencies:
[INFO]atg:dss-classes:jar:2006.3:provided
[INFO]lty:lty-utils:jar:3.0.1.2:compile
[INFO]atg.publishing:base:jar:2006.3.P2:compile
[INFO]taglibs:standard:jar:1.1.2:provided
[INFO]atg:webui-classes:jar:2006.3.P2:compile
[INFO]junit:junit:jar:4.0:compile
[INFO]jboss:system:jar:3.2:compile
[INFO]jboss:common:jar:1.0:compile
[INFO]atg:das-servlet:jar:2006.3:provided
[INFO]atg:pubportlet-classes:jar:2006.3.P2:compile
[INFO]apache:axis:jar:1.4:compile
[INFO]jboss:jboss-j2ee:jar:4.0.4.GA:provided
[INFO]atg:dps-classes:jar:2006.3.P2:provided
[INFO]atg:das-classes:jar:2006.3.P2:provided
[INFO]atg:bizui-classes:jar:2006.3.P2:compile
[INFO]jboss:jmx:jar:1.0:compile
[INFO] Used undeclared dependencies:
[WARNING]commons-fileupload:commons-fileupload:jar:1.0:provided
[INFO] Unused declared dependencies:
[INFO]jakarta-poi:jakarta-poi:jar:1.5.1:compile
[INFO]commons-discovery:commons-discovery:jar:0.2:compile
[INFO]oracle:aq:jar:1.0:compile
[INFO]gnu:regexp:jar:x:compile
[INFO]oracle:jdbc:jar:10.0:compile
[INFO]lty:lty-utils-resources:jar:1.0.0.16:compile
[INFO]jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
[INFO]velocity:velocity:jar:1.2:compile
[INFO]castor:castor_xml:jar:0.9.4.3:compile
[INFO]jboss:deploy:jar:1.0:compile
[INFO]org.apache:axis:jar:1.4:compile
[INFO]castor:castor:jar:0.9.4.3:compile
[INFO]geophile:jdbcwrapper:jar:1.0:compile
[INFO]aspectwerkz:aspectwerkz:jar:1.1:compile
[INFO]cactus-support:aspectjrt:jar:1.2.1:compile
[INFO]lty:capi:jar:1.2.0.27:compile
[INFO]xalan:xalan:jar:2.7.0:compile
[INFO]commons-net:commons-net:jar:1.3.0:compile
[INFO]com:oroinc:jar:1.0:compile
[INFO]commons-validator:commons-validator:jar:1.1.4:compile
[INFO]cactus-support:cactus:jar:1.7.2:compile
[INFO]xerces:xercesImpl:jar:2.8.0:compile
[WARNING] Potential problems discovered.
[INFO
Upgrading Maven 2.0.5 - 2.0.9
All, I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading documentation that said that there were some dependency sanity checks one should do before upgrading to the latest version of Maven from 2.0.6 or earlier (the page I am referring to is located at http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari ng-dependencies.html). On the page pasted above, it says to run the Maven dependency analyzer to check that everything is okay with how your dependencies are being referenced. After building my project, I ran the command as per the example but the ouput was a little confusing to me. It said there were errors but didn't list what errors were there. So to try to get more information, I tried a few things: 1) Added -Dverbose=true to the command, no additional output; 2) Edited the top-level pom.xml file to include the XML element below ... again with no output. Could something please help me understand what I am doing wrong? [ POM.XML Elements ] build plugins plugin artifactIdmaven-dependency-plugin/artifactId configuration verbosetrue/verbose /configuration /plugin ... ... ... /plugins /build [ Ouput ] [INFO]cactus-support:cactus:jar:1.7.2:compile [INFO]xerces:xercesImpl:jar:2.8.0:compile [WARNING] Potential problems discovered. [INFO] Found Resolved Dependency / DependencyManagement mismatches: [INFO]Nothing in DepMgt. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Tue May 27 16:19:35 EDT 2008 [INFO] Final Memory: 17M/127M [INFO]
Maven stalls while scanning for projects
All, While trying to execute a maven goal install against a project, sometimes I see the behavior where it starts to scan for projects, within the project I am building, and the java process consumes 100% of my CPU resources for hours, where it should take seconds. Does anyone know why this might be? This only happens on my test servers, and not on production. The biggest difference between the two is that the productions run Windows XP and the test servers are running Windows 2000. Other then the Operating System, they are pretty much identical as far as software is concerned. Mike Delaney
RE: Maven stalls while scanning for projects
Brian, I didn't see an endless loop; the last output I saw is pasted below. I let it sit there for some time (~15 Minutes) and nothing happened. [java] [cc]May-06 18:07:38 ScriptRunner - [INFO] Scanning for projects... [java] [cc]May-06 18:07:38 ScriptRunner - [DEBUG] Searching for parent-POM: PROJECT.NAME of project: PROJECT.NAME in relative path: ../pom.xml [java] [cc]May-06 18:07:38 ScriptRunner - [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: PROJECT.NAME [java] [cc]May-06 18:07:38 ScriptRunner - [DEBUG] Searching for parent-POM: PROJECT.NAME of project: PROJECT.NAME in relative path: ../pom.xml [java] [cc]May-06 18:07:38 ScriptRunner - [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: PROJECT.NAME -Original Message- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 06, 2008 3:43 PM To: Maven Users List Subject: RE: Maven stalls while scanning for projects Try running with -X to see if it's spinning in a loop somewhere. -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 06, 2008 8:07 AM To: users@maven.apache.org Subject: Maven stalls while scanning for projects All, While trying to execute a maven goal install against a project, sometimes I see the behavior where it starts to scan for projects, within the project I am building, and the java process consumes 100% of my CPU resources for hours, where it should take seconds. Does anyone know why this might be? This only happens on my test servers, and not on production. The biggest difference between the two is that the productions run Windows XP and the test servers are running Windows 2000. Other then the Operating System, they are pretty much identical as far as software is concerned. Mike Delaney - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
