Re: Skinny WAR and SNAPSHOT
Anyone? :-) Best regards, Eric Hi I know a lot has been written about skinny WARs and the problems they represent. The strategy that we're using is: - Set dependencies in the web module to scope 'provided', except dependencies that are web-specific (PrimeFaces, ...) - Set skinnyWars to true in the EAR project The strategy works very well for releases. But for SNAPSHOTs (we use Maven 3.0.4 with timestamped JARs) we have the problem that the same dependency still exists in both the WAR/WEB-INF/lib and the EAR/lib: my.ear lib util-logging-1.13.0-SNAPSHOT.jar my-ejb.jar my.war WEB-INF lib util-logging-1.13.0-20130305.151315-24.jar From my point of view, this is what happens: - The WAR plugin for my.war resolves all dependencies and puts them into its WEB-INF/lib. For some reason, the JARs contain the timestamp instead of SNAPSHOT in the filename. - The WAR is deployed to the repo - The EAR plugin for my.ear gets the my.war and tries to figure out what files are both in its dependencies as well as in the WAR's WEB-INF/lib - However, since the two filenames of util-logging differ, it's only successful up to a certain extent - anything which is resolved to different filenames leaves me with two JARs. Am I right with this? Also, how can I solve the problem with the SNAPSHOTs? Is there any other way than to force people to always use 'provided' in the web module? (I guess I should write a Maven Enforcer rule for that) Thanks for any pointers... Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Skinny WAR and SNAPSHOT
Hi I know a lot has been written about skinny WARs and the problems they represent. The strategy that we're using is: - Set dependencies in the web module to scope 'provided', except dependencies that are web-specific (PrimeFaces, ...) - Set skinnyWars to true in the EAR project The strategy works very well for releases. But for SNAPSHOTs (we use Maven 3.0.4 with timestamped JARs) we have the problem that the same dependency still exists in both the WAR/WEB-INF/lib and the EAR/lib: my.ear lib util-logging-1.13.0-SNAPSHOT.jar my-ejb.jar my.war WEB-INF lib util-logging-1.13.0-20130305.151315-24.jar From my point of view, this is what happens: - The WAR plugin for my.war resolves all dependencies and puts them into its WEB-INF/lib. For some reason, the JARs contain the timestamp instead of SNAPSHOT in the filename. - The WAR is deployed to the repo - The EAR plugin for my.ear gets the my.war and tries to figure out what files are both in its dependencies as well as in the WAR's WEB-INF/lib - However, since the two filenames of util-logging differ, it's only successful up to a certain extent - anything which is resolved to different filenames leaves me with two JARs. Am I right with this? Also, how can I solve the problem with the SNAPSHOTs? Is there any other way than to force people to always use 'provided' in the web module? (I guess I should write a Maven Enforcer rule for that) Thanks for any pointers... Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using versions:set fails when the child version is inherited from its parent - why?
Hi I'm using the versions-maven-plugin during our semi-automated release process to set a version. However, I have a problem whenever the version of the project is the same as the one in the parent. Maven 3 shows a warning if the versions are the same, but if I remove the version (which seems reasonable), I get an error from the versions plugin: Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.3.1:set (default-cli) on project external-versions: Project version is inherited from parent. Here's the POM I'm trying to modify: parent groupIdwhatever/groupId artifactIdmy-parent/artifactId version1.13.0-SNAPSHOT/version relativePath / /parent modelVersion4.0.0/modelVersion packagingpom/packaging artifactIdexternal-versions/artifactId ... And I try to modify it with mvn org.codehaus.mojo:versions-maven-plugin:1.3.1:set -DnewVersion=1.13.0-SNAPSHOT If I create an identical version with parent groupIdwhatever/groupId artifactIdmy-parent/artifactId version1.13.0-SNAPSHOT/version relativePath / /parent modelVersion4.0.0/modelVersion packagingpom/packaging version1.13.0-SNAPSHOT/version artifactIdexternal-versions/artifactId then it works. What am I doing wrong? (Yes, what I'm trying to do seems stupid, but I don't want to change the command depending on whether the child inherits the version from its parent or not - besides I don't know how I would find out whether it has its own version or not. Also, sometimes the version is inherited from the parent and sometimes not.) Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Using versions:set fails when the child version is inherited from its parent - why?
Ok, thanks for the clarification. I was hoping that the plugin would let me know that I'm trying to do something that can't be done (since the result would be identical to the existing POM). That is: Issue a warning instead of fail the build. But anyway: How could I find out myself whether the child has a version tag and whether it differs from its parent's version? Best regards, Eric P.S. Thanks for the plugin, it's a real life saver for us! -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Freitag, 15. Februar 2013 16:48 An: Maven Users List Betreff: Re: Using versions:set fails when the child version is inherited from its parent - why? version-maven-plugin assumes that if you don't provide /project/version and instead rely on /project/parent/version being the default value then *the child must always have the same version as the parent*. If the child may have a different version, then you specify the version. This behaves similarly with update-parent. if you specify a /project/version then, even if it is the same as /project/parent/version it will not be updated, but if you don't specify a /project/version then it will get updated. On 15 February 2013 15:37, Lewis, Eric eric.le...@ipi.ch wrote: Hi I'm using the versions-maven-plugin during our semi-automated release process to set a version. However, I have a problem whenever the version of the project is the same as the one in the parent. Maven 3 shows a warning if the versions are the same, but if I remove the version (which seems reasonable), I get an error from the versions plugin: Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.3.1:set (default-cli) on project external-versions: Project version is inherited from parent. Here's the POM I'm trying to modify: parent groupIdwhatever/groupId artifactIdmy-parent/artifactId version1.13.0-SNAPSHOT/version relativePath / /parent modelVersion4.0.0/modelVersion packagingpom/packaging artifactIdexternal-versions/artifactId ... And I try to modify it with mvn org.codehaus.mojo:versions-maven-plugin:1.3.1:set -DnewVersion=1.13.0-SNAPSHOT If I create an identical version with parent groupIdwhatever/groupId artifactIdmy-parent/artifactId version1.13.0-SNAPSHOT/version relativePath / /parent modelVersion4.0.0/modelVersion packagingpom/packaging version1.13.0-SNAPSHOT/version artifactIdexternal-versions/artifactId then it works. What am I doing wrong? (Yes, what I'm trying to do seems stupid, but I don't want to change the command depending on whether the child inherits the version from its parent or not - besides I don't know how I would find out whether it has its own version or not. Also, sometimes the version is inherited from the parent and sometimes not.) Best regards, Eric - 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
AW: dependency:unpack doesn't work correctly with Nexus, SNAPSHOT and classifier?
Anyone? :-)
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Dienstag, 23. Oktober 2012 16:53
An: users@maven.apache.org
Betreff: dependency:unpack doesn't work correctly with Nexus, SNAPSHOT and
classifier?
Hi
First of all I'd like to ask you to be gentle with me :-)
The solution I'm talking about is one big hack and will have to be migrated one
day.
But for the time being, here's the issue:
We have a WAR from an old Ant build which is built in a stage-dependent way
(one WAR for local use, one for development, one for production etc.).
The old build was coaxed into deploying the WAR into our Nexus with a
classifier representing the stage, e.g.
ch.ige:wdlbrowserzk:local:3.3.0-SNAPSHOT:war
This works well, and I can see the different WARs with their build date.
To deploy the WAR, I rebuild it with a Maven build. First, I use
dependency:unpack to get the WAR and unpack it. Later on, since the Maven
project is a war project, the WAR is rebuilt and deployed.
Now, my problem is that dependency:unpack always unpacks from the local repo.
It downloads the metadata from Nexus and then assumes that the local WAR is the
same as on Nexus - which it isn't!
The classifier is given to the plugin's configuration by using a profile. The
only bug I can imagine is that the plugin downloads the metadata, sees no
difference between the local repo and Nexus (since it seems to ignore the
classifier) and then proceeds with the local repo.
Does the plugin use a different dependency resolution? Or is my approach wrong?
(I mean, apart from the obviously hacky way of doing it)
Here's the configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack-wdl-war/id
phaseprepare-package/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
!-- Note: This works only if a stage-dependent profile is
active! --
artifactItem
groupIdch.ige/groupId
artifactIdwdlbrowserzk/artifactId
version${wdlbrowserzk.version}/version
typewar/type
classifier${profile.id}/classifier
overWritetrue/overWrite
/artifactItem
/artifactItems
outputDirectory${webapp.directory}/outputDirectory
overWriteReleasestrue/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
And here's the console output:
[INFO] --- maven-dependency-plugin:2.5.1:unpack (unpack-wdl-war) @
etrademark-nt-wdl-web ---
[INFO] Configured Artifact: ch.ige:wdlbrowserzk:local:3.3.0-SNAPSHOT:war
Downloading:
http://myrepo.com/content/groups/public/ch/ige/wdlbrowserzk/3.3.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://myrepo.com/content/groups/public/ch/ige/wdlbrowserzk/3.3.0-SNAPSHOT/maven-metadata.xml
(264 B at 7.2 KB/sec)
[INFO] Unpacking
C:\jp\maven-repository\ch\ige\wdlbrowserzk\3.3.0-SNAPSHOT\wdlbrowserzk-3.3.0-SNAPSHOT-local.war
to C:\jp\esv-projects\etrademark-nt\etrademark-nt-wdl-web\target\wdl with
includes and excludes
Any hint is appreciated!
Best regards,
Eric
-
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
dependency:unpack doesn't work correctly with Nexus, SNAPSHOT and classifier?
Hi
First of all I'd like to ask you to be gentle with me :-)
The solution I'm talking about is one big hack and will have to be migrated one
day.
But for the time being, here's the issue:
We have a WAR from an old Ant build which is built in a stage-dependent way
(one WAR for local use, one for development, one for production etc.).
The old build was coaxed into deploying the WAR into our Nexus with a
classifier representing the stage, e.g.
ch.ige:wdlbrowserzk:local:3.3.0-SNAPSHOT:war
This works well, and I can see the different WARs with their build date.
To deploy the WAR, I rebuild it with a Maven build. First, I use
dependency:unpack to get the WAR and unpack it. Later on, since the Maven
project is a war project, the WAR is rebuilt and deployed.
Now, my problem is that dependency:unpack always unpacks from the local repo.
It downloads the metadata from Nexus and then assumes that the local WAR is the
same as on Nexus - which it isn't!
The classifier is given to the plugin's configuration by using a profile. The
only bug I can imagine is that the plugin downloads the metadata, sees no
difference between the local repo and Nexus (since it seems to ignore the
classifier) and then proceeds with the local repo.
Does the plugin use a different dependency resolution? Or is my approach wrong?
(I mean, apart from the obviously hacky way of doing it)
Here's the configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idunpack-wdl-war/id
phaseprepare-package/phase
goals
goalunpack/goal
/goals
configuration
artifactItems
!-- Note: This works only if a stage-dependent profile is
active! --
artifactItem
groupIdch.ige/groupId
artifactIdwdlbrowserzk/artifactId
version${wdlbrowserzk.version}/version
typewar/type
classifier${profile.id}/classifier
overWritetrue/overWrite
/artifactItem
/artifactItems
outputDirectory${webapp.directory}/outputDirectory
overWriteReleasestrue/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
/configuration
/execution
/executions
/plugin
And here's the console output:
[INFO] --- maven-dependency-plugin:2.5.1:unpack (unpack-wdl-war) @
etrademark-nt-wdl-web ---
[INFO] Configured Artifact: ch.ige:wdlbrowserzk:local:3.3.0-SNAPSHOT:war
Downloading:
http://myrepo.com/content/groups/public/ch/ige/wdlbrowserzk/3.3.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://myrepo.com/content/groups/public/ch/ige/wdlbrowserzk/3.3.0-SNAPSHOT/maven-metadata.xml
(264 B at 7.2 KB/sec)
[INFO] Unpacking
C:\jp\maven-repository\ch\ige\wdlbrowserzk\3.3.0-SNAPSHOT\wdlbrowserzk-3.3.0-SNAPSHOT-local.war
to C:\jp\esv-projects\etrademark-nt\etrademark-nt-wdl-web\target\wdl with
includes and excludes
Any hint is appreciated!
Best regards,
Eric
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Findbugs 2.4.0 fails with NoClassDefFoundError
Hi We're having a very weird error with the latest Findbugs plugin. It works fine on our test build server, but it fails on our production build server. Here's the output: [java] java.lang.NoClassDefFoundError: org/apache/bcel/classfile/ClassFormatException [java] Caused by: java.lang.ClassNotFoundException: org.apache.bcel.classfile.ClassFormatException [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:202) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:190) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:247) [java] Could not find the main class: edu.umd.cs.findbugs.FindBugs2. Program will exit. [java] Exception in thread main When running in debug mode, we can see that the classpathes of the test and production servers differ. Here are the JARs that appear on the test server, but not on the production server: [DEBUG] com.google.code.findbugs:bcel:jar:2.0.0:compile [DEBUG] com.google.code.findbugs:jsr305:jar:2.0.0:compile [DEBUG] com.google.code.findbugs:jFormatString:jar:2.0.0:compile [DEBUG] com.google.code.findbugs:annotations:jar:2.0.0:compile [DEBUG] dom4j:dom4j:jar:1.6.1:compile [DEBUG] jaxen:jaxen:jar:1.1.1:compile [DEBUG] jdom:jdom:jar:1.0:compile [DEBUG] xom:xom:jar:1.0:compile [DEBUG]xerces:xmlParserAPIs:jar:2.6.2:compile [DEBUG]xalan:xalan:jar:2.6.0:compile [DEBUG]com.ibm.icu:icu4j:jar:2.6.1:compile [DEBUG] asm:asm:jar:3.3:compile [DEBUG] asm:asm-tree:jar:3.3:compile [DEBUG] asm:asm-commons:jar:3.3:compile Any hints what we're doing wrong or how I could chase that bug better? Thanks best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Findbugs 2.4.0 fails with NoClassDefFoundError
Hi Wayne Thanks for the reply. Just now we had another idea (after searching for hours), and it showed that the fault is on our side, so I apologize for the mail... The real issue was that we had to upload our own Findbugs 2 version into our Nexus repo (due to Proxy problems), and somehow that POM was corrupted, without any dependencies. So while Findbugs 2 was found, all its dependencies were not, and the only reason it worked on the test system was the local repo. After cleaning that, the build also failed. Anyway, what we learned: Be very careful with third-party JARs that you upload to your repository. Well will now clean it up soon! Thanks best regards, Eric -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Mittwoch, 2. Mai 2012 18:00 An: Maven Users List Betreff: Re: Findbugs 2.4.0 fails with NoClassDefFoundError We're having a very weird error with the latest Findbugs plugin. It works fine on our test build server, but it fails on our production build server. ... When running in debug mode, we can see that the classpathes of the test and production servers differ. This should not occur if you have plugin versions locked down in your pom.xml files and aren't using profiles and don't have local (not checked in yet) changes in one environment. Did you check mvn help:effective-pom in both environments to compare plugin and dependency versions? Also compare the settings.xml files in the 2 environments. Are you literally checking the full code tree out from the same place into the 2 environments, then running the same command and getting different results? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-antrun-plugin fails because of missing class
Hi We're migrating our build to Maven 3.0.3 and the latest Nexus. Now I'm having a problem with the maven-antrun-plugin. I have a build that gathers some files, simple stuff. Anyway, this was building correctly on our test server, until we cleared the local Maven repo. Since then I keep getting the error below. My local build still works, but then I didn't touch my local Maven repo. Any clues? It seems to me that org.apache.tools.ant.BuildException should be part of Ant and thus be found... Thanks best regards, Eric [INFO] --- maven-antrun-plugin:1.7:run (gather-internal-xml-schemas) @ xml-schemas --- [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:jar:1.7: [DEBUG]ant:ant-optional:jar:1.5.3-1:runtime [DEBUG]org.apache.maven:maven-plugin-api:jar:2.0.11:compile [DEBUG]org.apache.maven:maven-project:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-settings:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-profile:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-model:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0.11:compile [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.1:compile [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile [DEBUG] junit:junit:jar:3.8.1:compile [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile [DEBUG]org.apache.maven:maven-artifact:jar:2.0.11:compile [DEBUG]org.codehaus.plexus:plexus-utils:jar:2.0.5:compile [DEBUG]org.apache.ant:ant:jar:1.8.2:compile [DEBUG] org.apache.ant:ant-launcher:jar:1.8.2:compile [DEBUG] Created new class realm pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7 [DEBUG] Importing foreign packages into class realm pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7 [DEBUG] Imported: maven.api [DEBUG] Populating class realm pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7 [DEBUG] Included: org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 [DEBUG] Included: ant:ant-optional:jar:1.5.3-1 [DEBUG] Included: org.codehaus.plexus:plexus-interpolation:jar:1.1 [DEBUG] Included: junit:junit:jar:3.8.1 [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:2.0.5 [DEBUG] Included: org.apache.ant:ant:jar:1.8.2 [DEBUG] Included: org.apache.ant:ant-launcher:jar:1.8.2 [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.11 [DEBUG] Excluded: org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2 [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.11 [DEBUG] Configuring mojo org.apache.maven.plugins:maven-antrun-plugin:1.7:run from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7, parent: sun.misc.Launcher$AppClassLoader@799134f4] 09.02.2012 11:15:37 org.sonatype.guice.bean.reflect.LoadedClass WARNUNG: Error injecting: org.apache.maven.plugin.antrun.AntRunMojo java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getDeclaredConstructors(Class.java:1836) at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:243) at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:96) at com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:628) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:835) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:769) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:254) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:205) at com.google.inject.internal.InjectorImpl.getInternalFactory(InjectorImpl.java:843) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:957) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:990) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:951) at
Classloading issues with Maven 3 on Linux (was: maven-antrun-plugin fails because of missing class)
[ERROR] urls[28] = file:/home/swe/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar [ERROR] urls[29] = file:/home/swe/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar [ERROR] urls[30] = file:/home/swe/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-10/doxia-decoration-model-1.0-alpha-10.jar [ERROR] urls[31] = file:/home/swe/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar [ERROR] urls[32] = file:/home/swe/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0-alpha-10/doxia-module-apt-1.0-alpha-10.jar [ERROR] urls[33] = file:/home/swe/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0-alpha-10/doxia-module-fml-1.0-alpha-10.jar [ERROR] urls[34] = file:/home/swe/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0-alpha-10/doxia-module-xdoc-1.0-alpha-10.jar [ERROR] urls[35] = file:/home/swe/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0-alpha-10/doxia-module-xhtml-1.0-alpha-10.jar [ERROR] urls[36] = file:/home/swe/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar [ERROR] urls[37] = file:/home/swe/.m2/repository/org/slf4j/slf4j-api/1.5.10/slf4j-api-1.5.10.jar [ERROR] urls[38] = file:/home/swe/.m2/repository/org/sonatype/gossip/gossip/1.2/gossip-1.2.jar [ERROR] Number of foreign imports: 1 [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]] [ERROR] [ERROR] -: groovy.lang.GroovyResourceLoader [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Donnerstag, 9. Februar 2012 12:12 An: users@maven.apache.org Betreff: maven-antrun-plugin fails because of missing class Hi We're migrating our build to Maven 3.0.3 and the latest Nexus. Now I'm having a problem with the maven-antrun-plugin. I have a build that gathers some files, simple stuff. Anyway, this was building correctly on our test server, until we cleared the local Maven repo. Since then I keep getting the error below. My local build still works, but then I didn't touch my local Maven repo. Any clues? It seems to me that org.apache.tools.ant.BuildException should be part of Ant and thus be found... Thanks best regards, Eric [INFO] --- maven-antrun-plugin:1.7:run (gather-internal-xml-schemas) @ xml-schemas --- [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:jar:1.7: [DEBUG]ant:ant-optional:jar:1.5.3-1:runtime [DEBUG]org.apache.maven:maven-plugin-api:jar:2.0.11:compile [DEBUG]org.apache.maven:maven-project:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-settings:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-profile:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-model:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.11:compile [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0.11:compile [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.1:compile [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile [DEBUG] junit:junit:jar:3.8.1:compile [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile [DEBUG]org.apache.maven:maven-artifact:jar:2.0.11:compile [DEBUG]org.codehaus.plexus:plexus-utils:jar:2.0.5:compile [DEBUG]org.apache.ant:ant:jar:1.8.2:compile [DEBUG] org.apache.ant:ant-launcher:jar:1.8.2:compile [DEBUG] Created new class realm pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7 [DEBUG] Importing foreign packages into class realm pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7 [DEBUG] Imported: maven.api [DEBUG] Populating class realm pluginorg.apache.maven.plugins:maven-antrun-plugin:1.7 [DEBUG] Included: org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 [DEBUG] Included: ant:ant-optional:jar:1.5.3-1 [DEBUG] Included: org.codehaus.plexus:plexus-interpolation:jar:1.1 [DEBUG] Included: junit:junit:jar:3.8.1 [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:2.0.5 [DEBUG] Included: org.apache.ant:ant:jar:1.8.2 [DEBUG] Included: org.apache.ant:ant-launcher:jar:1.8.2 [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.11 [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.11 [DEBUG] Excluded
Classloading issues with Maven 3 on Linux (was: maven-antrun-plugin fails because of missing class)
OK, so I checked the last possible difference with the build: Nexus I switched the settings.xml to use our productive Nexus (1.7.2) instead of our test Nexus (1.9.2.4) Then I once again cleared the local Maven repo. And to my astonishment, everything worked fine! Hmmm... has anyone experienced anything like this? Or should I ask on the Nexus mailing list? Best regards, Eric -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Donnerstag, 9. Februar 2012 15:38 An: Maven Users List Betreff: Classloading issues with Maven 3 on Linux (was: maven-antrun-plugin fails because of missing class) Me again :-) Ok, it turns out this is not a maven-antrun-problem, but a general classloading problem which we seem to have on Linux. The local builds are on Windows, and to make sure I'm in the same situation as on Linux, I removed my local Maven repo and started over, using the gmaven-plugin this time. Everything went well on Windows, all the dependencies downloaded and everything ran fine. However, once I removed the local repo on Linux, the situation was different. While the build of our Parent POM worked fine (all plugins downloaded etc.), the gmaven-plugin failed (see below). So this seems to be an artifact downloading/classloading issue. Any ideas? [INFO] [INFO] --- gmaven-plugin:1.4:execute (gather-internal-xml-schemas) @ xml-schemas --- [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.379s [INFO] Finished at: Thu Feb 09 15:33:05 CET 2012 [INFO] Final Memory: 16M/618M [INFO] [ERROR] Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.4:execute (gather-internal-xml-schemas) on project xml-schemas: Execution gather-internal-xml-schemas of goal org.codehaus.gmaven:gmaven-plugin:1.4:execute failed: A required class was missing while executing org.codehaus.gmaven:gmaven-plugin:1.4:execute: groovy/lang/GroovyResourceLoader [ERROR] - [ERROR] realm =pluginorg.codehaus.gmaven:gmaven-plugin:1.4 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/home/swe/.m2/repository/org/codehaus/gmaven/gmaven-plugin/1.4/gmaven-plugin-1.4.jar [ERROR] urls[1] = file:/home/swe/.m2/repository/org/codehaus/gmaven/runtime/gmaven-runtime-api/1.4/gmaven-runtime-api-1.4.jar [ERROR] urls[2] = file:/home/swe/.m2/repository/org/codehaus/gmaven/feature/gmaven-feature-api/1.4/gmaven-feature-api-1.4.jar [ERROR] urls[3] = file:/home/swe/.m2/repository/org/codehaus/gmaven/runtime/gmaven-runtime-loader/1.4/gmaven-runtime-loader-1.4.jar [ERROR] urls[4] = file:/home/swe/.m2/repository/org/codehaus/gmaven/feature/gmaven-feature-support/1.4/gmaven-feature-support-1.4.jar [ERROR] urls[5] = file:/home/swe/.m2/repository/org/codehaus/gmaven/runtime/gmaven-runtime-support/1.4/gmaven-runtime-support-1.4.jar [ERROR] urls[6] = file:/home/swe/.m2/repository/org/sonatype/gshell/gshell-io/2.4/gshell-io-2.4.jar [ERROR] urls[7] = file:/home/swe/.m2/repository/org/codehaus/plexus/plexus-utils/3.0/plexus-utils-3.0.jar [ERROR] urls[8] = file:/home/swe/.m2/repository/com/thoughtworks/qdox/qdox/1.12/qdox-1.12.jar [ERROR] urls[9] = file:/home/swe/.m2/repository/org/apache/maven/shared/file-management/1.2.1/file-management-1.2.1.jar [ERROR] urls[10] = file:/home/swe/.m2/repository/org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar [ERROR] urls[11] = file:/home/swe/.m2/repository/org/apache/xbean/xbean-reflect/3.4/xbean-reflect-3.4.jar [ERROR] urls[12] = file:/home/swe/.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar [ERROR] urls[13] = file:/home/swe/.m2/repository/commons-logging/commons-logging-api/1.1/commons-logging-api-1.1.jar [ERROR] urls[14] = file:/home/swe/.m2/repository/com/google/collections/google-collections/1.0/google-collections-1.0.jar [ERROR] urls[15] = file:/home/swe/.m2/repository/org/apache/maven/reporting/maven-reporting-impl/2.0.4.1/maven-reporting-impl-2.0.4.1.jar [ERROR] urls[16] = file:/home/swe/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.1/plexus-interpolation-1.1.jar [ERROR] urls[17] = file:/home/swe/.m2/repository/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar [ERROR] urls[18] = file:/home/swe/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar [ERROR] urls[19] = file:/home/swe/.m2/repository/commons-digester/commons-digester/1.6/commons-digester-1.6.jar [ERROR] urls[20] = file:/home/swe/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar [ERROR] urls[21] = file:/home/swe/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar [ERROR] urls[22] = file:/home/swe/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar [ERROR] urls[23
AW: Use mvnsh with already installed Maven - how?
Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Mittwoch, 14. Dezember 2011 11:20 An: users@maven.apache.org Betreff: Use mvnsh with already installed Maven - how? Hi I'm looking into mvnsh right now, after having installed Maven 3.0.3 Is there a way to let mvnsh use the installed Maven instead of its own bundled version 3.0.2? Best regards Eric - 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
Use mvnsh with already installed Maven - how?
Hi I'm looking into mvnsh right now, after having installed Maven 3.0.3 Is there a way to let mvnsh use the installed Maven instead of its own bundled version 3.0.2? Best regards Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Resources Plugin: escapeWindowsPaths depending on the file type?
Hi I'm using the latest and greatest Resources Plugin 2.5 Now I'm having a problem with Windows pathes: I have for instance a property x with the path C:\foo\bar and want to filter some files with it. In my properties file I want it to be C:\\foo\\bar, but in my batch file I want it to be C:\foo\bar. How do I do that using escapeWindowsPaths? As far as I know, I can't configure the Resources plugin twice in my build, since the resources can't be configured in the pluginconfiguration. Thanks for any help! Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to write a plugin that generates source files based on the source in the project?
Hi I'm trying to write a plugin which does the following: - Check the classes in the project and keep all classes that implement interface X. - For all X, get the fields, and if a field has a certain annotation, generate a class containing some constant information. Normally the plugin should be bound to the phase 'generate-sources'. However, the classes of the project aren't compiled yet at that moment, so I can't just get them from the classpath, right? Does anyone have a good idea or pointers how to do this correctly? Thanks best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Build Helper Plugin: remove-project-artifact always removes all versions?
Hi
I'm trying to remove a certain version of an artifact within my local repo.
I've written a small test script which downloads joda-time 1.0 and 1.6
Both versions exist with their directories in my local repo.
Then I download the POM for 1.6 into a temporary directory, enter that
directory, delete the distributionManagement from the POM and then call Maven:
mvn build-helper:remove-project-artifact -DremoveAll=false
However, that removes *all* versions in the local repo.
Unless I understand removeAll wrongly, it should only remove 1.6...
When running Maven in debug mode, I get
[DEBUG] Configuring mojo
'org.codehaus.mojo:build-helper-maven-plugin:1.5:remove-project-artifact' --
[DEBUG] (f) localRepository = Repository[local|file://C:/jp/maven-repository]
[DEBUG] (f) project = MavenProject: joda-time:joda-time:1.6 @
c:\jp\esv-projects\client\temp\pom.xml
[DEBUG] (f) removeAll = true
[DEBUG] -- end configuration --
[INFO] [build-helper:remove-project-artifact {execution: default-cli}]
[INFO] C:\jp\maven-repository\joda-time\joda-time removed.
Am I doing something wrong or is this a bug?
Best regards,
Eric
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: Build Helper Plugin: remove-project-artifact always removes all versions?
Hi Jeff
Thanks, that worked!
However, I'm now confused :-)
According to
http://mojo.codehaus.org/build-helper-maven-plugin/remove-project-artifact-mojo.html
the parameter is called removeAll.
My understanding of plugin parameters on the command line was that you just use
them with -D
Am I wrong?
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: jeffma...@gmail.com [mailto:jeffma...@gmail.com] Im Auftrag von Jeff MAURY
Gesendet: Mittwoch, 8. September 2010 14:25
An: Maven Users List
Betreff: Re: Build Helper Plugin: remove-project-artifact always removes all
versions?
You should use -Dbuildhelper.removeAll=true instead.
Regards
Jeff MAURY
On Wed, Sep 8, 2010 at 2:20 PM, Lewis, Eric eric.le...@ipi.ch wrote:
Hi
I'm trying to remove a certain version of an artifact within my local repo.
I've written a small test script which downloads joda-time 1.0 and 1.6
Both versions exist with their directories in my local repo.
Then I download the POM for 1.6 into a temporary directory, enter that
directory, delete the distributionManagement from the POM and then call
Maven:
mvn build-helper:remove-project-artifact -DremoveAll=false
However, that removes *all* versions in the local repo.
Unless I understand removeAll wrongly, it should only remove 1.6...
When running Maven in debug mode, I get
[DEBUG] Configuring mojo
'org.codehaus.mojo:build-helper-maven-plugin:1.5:remove-project-artifact'
--
[DEBUG] (f) localRepository =
Repository[local|file://C:/jp/maven-repository]
[DEBUG] (f) project = MavenProject: joda-time:joda-time:1.6 @
c:\jp\esv-projects\client\temp\pom.xml
[DEBUG] (f) removeAll = true
[DEBUG] -- end configuration --
[INFO] [build-helper:remove-project-artifact {execution: default-cli}]
[INFO] C:\jp\maven-repository\joda-time\joda-time removed.
Am I doing something wrong or is this a bug?
Best regards,
Eric
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Legacy code often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Does the sequence of goals/phases matter?
Hi This is probably a trivial question, but I'll ask it nonetheless :-) Does the sequence of the goals and lifecycle phases matter when I call Maven? In other words, are these two exactly the same? clean package site-deploy site-deploy clean package Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Does the sequence of goals/phases matter?
Ok, thanks for the clarification! So, is this the right sequence in your opinion? clean package findbugs:findbugs pmd:pmd pmd:cpd checkstyle:checkstyle site-deploy Or where can I find out more about that topic? http://www.sonatype.com/books/mvnref-book/reference/lifecycle.html doesn't tell me about how to call individual plugin goals within a lifecycle, unless I missed something. Best regards, Eric -Ursprüngliche Nachricht- Von: Justin Edelson [mailto:justinedel...@gmail.com] Gesendet: Dienstag, 20. Juli 2010 13:54 An: Maven Users List Betreff: Re: Does the sequence of goals/phases matter? On Jul 20, 2010, at 7:49 AM, Lewis, Eric eric.le...@ipi.ch wrote: Hi This is probably a trivial question, but I'll ask it nonetheless :-) Does the sequence of the goals and lifecycle phases matter when I call Maven? Yes In other words, are these two exactly the same? No clean package site-deploy site-deploy clean package Best regards, Eric - 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
AW: AW: Does the sequence of goals/phases matter?
Actually, it's a bit complicated :-) The Maven build is started within Hudson. The plugins within Hudson (PMD, Checkstyle etc.) require the report XMLs (created by pmd:pmd etc.) to be able to work. So I need to call those goals for every build. However, we also have a nightly build (which should also work with the Hudson plugins), which builds the Maven site (since that's not part of Continuous Integration). There are other metrics which are included there, but not the ones from the Hudson plugins. So even though e.g. the PMD plugin says that pmd:pmd should be used as a Maven report, I need it outside of the site lifecycle. Best regards, Eric -Ursprüngliche Nachricht- Von: Justin Edelson [mailto:justinedel...@gmail.com] Gesendet: Dienstag, 20. Juli 2010 14:40 An: Maven Users List Betreff: Re: AW: Does the sequence of goals/phases matter? On Jul 20, 2010, at 8:01 AM, Lewis, Eric eric.le...@ipi.ch wrote: Ok, thanks for the clarification! So, is this the right sequence in your opinion? clean package findbugs:findbugs pmd:pmd pmd:cpd checkstyle:checkstyle site-deploy Assuming that findbugs, pmd and checkstyle are configured as part of your reporting configuration, it shouldn't be necessary to include them explicitly on the command line. Or where can I find out more about that topic? http://www.sonatype.com/books/mvnref-book/reference/lifecycle.html doesn't tell me about how to call individual plugin goals within a lifecycle, unless I missed something. I find it hard to believe the Maven reference doesn't talk about binding a plugin to a phase. In any case, it is discussed here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html in the Plugins section Justin Best regards, Eric -Ursprüngliche Nachricht- Von: Justin Edelson [mailto:justinedel...@gmail.com] Gesendet: Dienstag, 20. Juli 2010 13:54 An: Maven Users List Betreff: Re: Does the sequence of goals/phases matter? On Jul 20, 2010, at 7:49 AM, Lewis, Eric eric.le...@ipi.ch wrote: Hi This is probably a trivial question, but I'll ask it nonetheless :-) Does the sequence of the goals and lifecycle phases matter when I call Maven? Yes In other words, are these two exactly the same? No clean package site-deploy site-deploy clean package Best regards, Eric - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: AW: Does the sequence of goals/phases matter?
Yep, that sounds smart! Especially since I can activate the profile by the existence of HUDSON_HOME. I'll try that, thanks! Best regards, Eric -Ursprüngliche Nachricht- Von: Jörg Schaible [mailto:joerg.schai...@gmx.de] Gesendet: Dienstag, 20. Juli 2010 15:32 An: users@maven.apache.org Betreff: Re: AW: AW: Does the sequence of goals/phases matter? Lewis, Eric wrote: Actually, it's a bit complicated :-) The Maven build is started within Hudson. The plugins within Hudson (PMD, Checkstyle etc.) require the report XMLs (created by pmd:pmd etc.) to be able to work. So I need to call those goals for every build. However, we also have a nightly build (which should also work with the Hudson plugins), which builds the Maven site (since that's not part of Continuous Integration). There are other metrics which are included there, but not the ones from the Hudson plugins. So even though e.g. the PMD plugin says that pmd:pmd should be used as a Maven report, I need it outside of the site lifecycle. Create a hudson profile and bind all these goals in this profile to e.g. the package phase. - 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
AW: Maven Best Pratices: Where to place generate re(sources)?
Hi Andreas
I don't know if my practice is best, but I certainly advise you to unpack to
the ${project.build.directory}, since
a) it's deleted during clear
b) you don't want to mess up your source directories, especially if you use SCM
And yes, you then need the buildhelper.
However, reading your message makes me wonder why you're unpacking a dependency
at all. I don't know your use case, but if you use the resources, you could
just load them from the classpath.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Andreas Sewe [mailto:s...@st.informatik.tu-darmstadt.de]
Gesendet: Dienstag, 8. Juni 2010 10:55
An: Maven Users List
Betreff: Maven Best Pratices: Where to place generate re(sources)?
Hi all,
I have a project which uses dependency:unpack to grab Java sources as
well as some binary resources from a JAR. The Java sources thus
generated have then to be compiled, the binary resources must simply
wind up in the project's artifact.
At the moment, I unpack the Java sources into
${project.build.sourceDirectory} and the resources into
src/main/resources in the generate-sources and generate-resources
phases, respectively. This setup, however, has one disadvantage: neither
the source nor resource directories are cleaned when in the clean
lifecycle phase. But this is desirable for generated (re)sources. Of
course, I can configure the m-clean-p appropriately, but the less
configuration the better, right?
So, what are best practices to handle a situation like this? Should I
rather unpack the (re)sources to a directory somewhere below
${project.build.directory}? (This is what dependency:unpack does by
default, after all.) But this would require use of the buildhelper-m-p,
for otherwise the unpacked sources won't be picked up by the compiler. :-(
Any advice?
Andreas Sewe
-
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
AW: AW: Maven Best Pratices: Where to place generate re(sources)?
Hi Andreas
I gave up my aesthetic view on POMs long ago ;-)
Seriously, though, it looks like you're only repacking existing dependencies.
So you might want to look into the Assembly plugin (after reading the chapters
in the Sonatype book).
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Andreas Sewe [mailto:s...@st.informatik.tu-darmstadt.de]
Gesendet: Dienstag, 8. Juni 2010 13:01
An: Maven Users List
Betreff: Re: AW: Maven Best Pratices: Where to place generate re(sources)?
Hi Eric,
I don't know if my practice is best, but I certainly advise you to unpack
to the ${project.build.directory}, since
a) it's deleted during clear
b) you don't want to mess up your source directories, especially if you use
SCM
true.
And yes, you then need the buildhelper.
Yes, the builderhelper-m-p does the job; the reuslting POM's not pretty,
though.
However, reading your message makes me wonder why you're unpacking a
dependency at all. I don't know your use case, but if you use the resources,
you could just load them from the classpath.
No, unfortunately, I cannot do that. I have to build a JAR which has a
specific internal structure (a couple of directories containing further
JARs and sources) which is then unzipped by a third-party application
during its execution. Not my design choice, but one I have to live
with. :-(
Best wishes,
Andreas
-
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
AW: Dependency fails, but only in reactor build
Anyone? :-)
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Mittwoch, 2. Juni 2010 11:52
An: users@maven.apache.org
Betreff: Dependency fails, but only in reactor build
Hi
I'm having problems with a dependency that can't be found, but only in a
reactor build.
We have a project 'activity' with several modules, one of them being the
'activity-client', which uses an assembly 'batch' (a ZIP for a batch client).
We have Hudson as CI server and build every project on commit changes: The
'activity' project builds flawlessly.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [source:jar-no-fork {execution: attach-sources}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-sources.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
...
[INFO] Building zip:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-batch.zip
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Wed Jun 02 11:35:03 CEST 2010
[INFO] Final Memory: 76M/631M
[INFO]
However, we also have a nightly build which builds the whole system with all
projects in one big reactor build.
Here, for some strange reason, the 'batch' assembly can't be found.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/esv-projects-tests__development/workspace/activity/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error reading assemblies: Descriptor with ID 'batch' not found
If within the checked out whole system I go to the directory of
'activity-client' and build it with 'mvn clean package', everything works.
If I do an 'mvn clean package' on the whole system, I get the error above.
So, clearly, the dependency exists in the repository. But sometimes it can't be
found...
How can that be or how can I check in a better way what's going wrong?
Best regards,
Eric
-
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
AW: Dependency fails, but only in reactor build
Well... to answer part of my own question: I noticed that this happens in the
case that I have two different modules which each use the assembly plugin.
Somehow the plugin can't resolve both pre-defined assemblies in the modules.
They're different assemblies which I reference using descriptorRef, and as
soon as I comment out one of the plugin configurations, the whole project
builds again.
Does this have anything to do with being only able to defined a plugin once in
a POM and having to define separate executions? How can I solve this?
Any hint, especially from the Assembly developers ;-) is greatly appreciated!
Best regards,
Eric
P.S.
Here are my two POM excerpts:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
dependencies
dependency
groupIdch.ipi/groupId
artifactIdipi-assembly-xml-schemas/artifactId
version${ipi-assembly-xml-schemas.version}/version
/dependency
/dependencies
executions
execution
idcreate-xml-schema-jar/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptorRefs
descriptorRefxml-schemas/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
dependencies
dependency
groupIdch.ipi/groupId
artifactIdipi-assembly-batch/artifactId
version${ipi-assembly-batch.version}/version
/dependency
/dependencies
executions
execution
idcreate-batch-distribution/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptorRefs
descriptorRefbatch/descriptorRef
/descriptorRefs
/configuration
/execution
/executions
/plugin
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Montag, 7. Juni 2010 08:29
An: Maven Users List
Betreff: AW: Dependency fails, but only in reactor build
Anyone? :-)
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Mittwoch, 2. Juni 2010 11:52
An: users@maven.apache.org
Betreff: Dependency fails, but only in reactor build
Hi
I'm having problems with a dependency that can't be found, but only in a
reactor build.
We have a project 'activity' with several modules, one of them being the
'activity-client', which uses an assembly 'batch' (a ZIP for a batch client).
We have Hudson as CI server and build every project on commit changes: The
'activity' project builds flawlessly.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [source:jar-no-fork {execution: attach-sources}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-sources.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
...
[INFO] Building zip:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-batch.zip
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Wed Jun 02 11:35:03 CEST 2010
[INFO] Final Memory: 76M/631M
[INFO]
However, we also have a nightly build which builds the whole system with all
projects in one big reactor build.
Here, for some strange reason, the 'batch' assembly can't be found.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/esv-projects-tests__development/workspace/activity/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error reading assemblies: Descriptor with ID 'batch' not found
If within the checked out whole system I go to the directory of
'activity-client' and build it with 'mvn clean package', everything works.
If I do an 'mvn clean package' on the whole system, I get the error above.
So, clearly, the dependency exists in the repository. But sometimes it can't be
found...
How can that be or how can I check in a better way what's going wrong?
Best regards,
Eric
Dependency fails, but only in reactor build
Hi
I'm having problems with a dependency that can't be found, but only in a
reactor build.
We have a project 'activity' with several modules, one of them being the
'activity-client', which uses an assembly 'batch' (a ZIP for a batch client).
We have Hudson as CI server and build every project on commit changes: The
'activity' project builds flawlessly.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [source:jar-no-fork {execution: attach-sources}]
[INFO] Building jar:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-sources.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
...
[INFO] Building zip:
/ige/hudson/work/jobs/activity/workspace/activity-client/target/activity-client-2.2.0-SNAPSHOT-batch.zip
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Wed Jun 02 11:35:03 CEST 2010
[INFO] Final Memory: 76M/631M
[INFO]
However, we also have a nightly build which builds the whole system with all
projects in one big reactor build.
Here, for some strange reason, the 'batch' assembly can't be found.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
/ige/hudson/work/jobs/esv-projects-tests__development/workspace/activity/activity-client/target/activity-client-2.2.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: create-batch-distribution}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error reading assemblies: Descriptor with ID 'batch' not found
If within the checked out whole system I go to the directory of
'activity-client' and build it with 'mvn clean package', everything works.
If I do an 'mvn clean package' on the whole system, I get the error above.
So, clearly, the dependency exists in the repository. But sometimes it can't be
found...
How can that be or how can I check in a better way what's going wrong?
Best regards,
Eric
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: build multi-projects with eclipse
Hi
Are you using m2eclipse?
If you aren't, you should :-)
As for your second question: m2eclipse has an integration with Eclipse WTP, but
personally I haven't used it yet.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: sean xiong [mailto:seanxi...@fridae.com]
Gesendet: Mittwoch, 2. Juni 2010 15:44
An: users@maven.apache.org
Betreff: build multi-projects with eclipse
Hi,
I'm new on Maven. Here's my problem,
I built a webapp and some services in another project, both of them inherit
from parent pom.
I have added dependency in webapp of service project.
Every time when I try to package webapp, it tries to download from
${user.home}/.m2/repository but failed. This happens in Eclipse only, when I
use netbeans it works. But I don't wanna change my IDE becos of this. Anyone
has experience on this?
Another question: with Maven if I change source code in service project and
webapp running on tomcat, would it take effect real-time? Or I have to rebuild
and deploy it?
Thank you.
-
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
AW: AW: build multi-projects with eclipse
Well, it creates dynamic dependencies between your projects when they are open
in Eclipse, which helps a lot for development.
However, if you close a project, its artifact has to exist in your local
repository, so you have to build it with 'install' before closing the project.
Unless I misunderstood your problem, and your Maven build doesn't find an
external dependency. In that case, you might have a Proxy configuration problem
in Eclipse.
But then, I don't know how you're building your projects within Eclipse... with
a launch configuration (Run As...)?
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: sean xiong [mailto:seanxi...@fridae.com]
Gesendet: Mittwoch, 2. Juni 2010 16:11
An: Maven Users List
Betreff: Re: AW: build multi-projects with eclipse
can m2eclipse solve my problem? I download first.
On Jun 2, 2010, at 9:49 PM, Lewis, Eric wrote:
Hi
Are you using m2eclipse?
If you aren't, you should :-)
As for your second question: m2eclipse has an integration with Eclipse WTP,
but personally I haven't used it yet.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: sean xiong [mailto:seanxi...@fridae.com]
Gesendet: Mittwoch, 2. Juni 2010 15:44
An: users@maven.apache.org
Betreff: build multi-projects with eclipse
Hi,
I'm new on Maven. Here's my problem,
I built a webapp and some services in another project, both of them inherit
from parent pom.
I have added dependency in webapp of service project.
Every time when I try to package webapp, it tries to download from
${user.home}/.m2/repository but failed. This happens in Eclipse only, when I
use netbeans it works. But I don't wanna change my IDE becos of this. Anyone
has experience on this?
Another question: with Maven if I change source code in service project and
webapp running on tomcat, would it take effect real-time? Or I have to
rebuild and deploy it?
Thank you.
-
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
AW: AW: AW: build multi-projects with eclipse
Hmmm... I have never used the Spring Tool Suite, sorry...
m2eclipse creates dynamic dependencies between Eclipse projects. When you open
one, all open projects which depend on it now depend on the opened project
instead of the project's artifact in the Maven repository. As for Use pom.xml
interface to add by search?, I don't know what you mean... pom.xml is not an
interface, it's Maven's configuration.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: sean xiong [mailto:seanxi...@fridae.com]
Gesendet: Mittwoch, 2. Juni 2010 16:28
An: Maven Users List
Betreff: Re: AW: AW: build multi-projects with eclipse
Yah I use 'Run as on server' with spring tool suite.
I just tried and maven for eclipse has been installed into STS which I have
been using.
You mentioned it creates dynamic dependencies between the projects, how? Use
pom.xml interface to add by search?
On Jun 2, 2010, at 10:16 PM, Lewis, Eric wrote:
Well, it creates dynamic dependencies between your projects when they are
open in Eclipse, which helps a lot for development.
However, if you close a project, its artifact has to exist in your local
repository, so you have to build it with 'install' before closing the project.
Unless I misunderstood your problem, and your Maven build doesn't find an
external dependency. In that case, you might have a Proxy configuration
problem in Eclipse.
But then, I don't know how you're building your projects within Eclipse...
with a launch configuration (Run As...)?
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: sean xiong [mailto:seanxi...@fridae.com]
Gesendet: Mittwoch, 2. Juni 2010 16:11
An: Maven Users List
Betreff: Re: AW: build multi-projects with eclipse
can m2eclipse solve my problem? I download first.
On Jun 2, 2010, at 9:49 PM, Lewis, Eric wrote:
Hi
Are you using m2eclipse?
If you aren't, you should :-)
As for your second question: m2eclipse has an integration with Eclipse WTP,
but personally I haven't used it yet.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: sean xiong [mailto:seanxi...@fridae.com]
Gesendet: Mittwoch, 2. Juni 2010 15:44
An: users@maven.apache.org
Betreff: build multi-projects with eclipse
Hi,
I'm new on Maven. Here's my problem,
I built a webapp and some services in another project, both of them inherit
from parent pom.
I have added dependency in webapp of service project.
Every time when I try to package webapp, it tries to download from
${user.home}/.m2/repository but failed. This happens in Eclipse only, when I
use netbeans it works. But I don't wanna change my IDE becos of this. Anyone
has experience on this?
Another question: with Maven if I change source code in service project and
webapp running on tomcat, would it take effect real-time? Or I have to
rebuild and deploy it?
Thank you.
-
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
-
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
AW: Maven Enforcer: Banned dependencies including type, classifier etc.
Ok, I checked JIRA and found http://jira.codehaus.org/browse/MENFORCER-74 http://jira.codehaus.org/browse/MENFORCER-75 http://jira.codehaus.org/browse/MENFORCER-72 (seems to be the same as 75) So, from groupId:artifactId:packaging:classifier:version everything except packaging would be done if these issues are fixed. Best regards, Eric -Ursprüngliche Nachricht- Von: Brian Fox [mailto:bri...@infinity.nu] Gesendet: Freitag, 28. Mai 2010 05:07 An: Maven Users List Betreff: Re: Maven Enforcer: Banned dependencies including type, classifier etc. Yes, it appears to support g:a:v only. I'm sure I had a reason at the time but I can't think of one now. It should be g:a:v:c:t On Thu, May 27, 2010 at 12:11 PM, Lewis, Eric eric.le...@ipi.ch wrote: Hi As far as I know, most Maven plugins rely on the Maven coordinates as described in http://maven.apache.org/pom.html#Maven_Coordinates I just tried to use them in the Maven Enforcer plugin's banned dependencies rule, but from reading the source, it looks like the Maven coordinates are only supported up to the version. Am I right with this? Should I write an enhancement request? Best regards, Eric - 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
Assembly plugin: Same file with several file extensions?
Hi I want to include several files which have the same name, but different file extensions into a JAR. Of course, the Assembly plugin comes to mind, but is this possible? And if it is, how can I do it? The idea is that if for instance I find a file my-file.xsd, I will also look for my-file.properties. Thanks for any pointers! Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Assembly plugin: Same file with several file extensions?
Hi Karl Heinz Well, I've located them by specifying something like includes include**/*.xsd/include include**/*.properties/include /includes However, this gets all those files. What I need is *pairs* of files, like bla.xsd and bla.properties - or in regex: (.*)\.xsd requires $1\.properties Best regards Eric -Ursprüngliche Nachricht- Von: Karl Heinz Marbaise [mailto:k...@soebes.de] Gesendet: Donnerstag, 27. Mai 2010 15:49 An: users@maven.apache.org Betreff: Re: Assembly plugin: Same file with several file extensions? Hi Eric, have you located the files you want to include into the src/main/resources folder? If yes than they should be included automatically ...May be i didn't understand what you like to do? Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/Assembly-plugin%3A-Same-file-with-several-file-extensions--tp28692233p28693892.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Enforcer: Banned dependencies including type, classifier etc.
Hi As far as I know, most Maven plugins rely on the Maven coordinates as described in http://maven.apache.org/pom.html#Maven_Coordinates I just tried to use them in the Maven Enforcer plugin's banned dependencies rule, but from reading the source, it looks like the Maven coordinates are only supported up to the version. Am I right with this? Should I write an enhancement request? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How to create a report based on annotations
Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Montag, 17. Mai 2010 11:07 An: Maven Users List Betreff: How to create a report based on annotations Hi I'd like to create a Maven report based on annotations (OVal annotations, to be precise). Can I use the apt-maven-plugin for this (and if yes, how would I do it)? Also, is there a tutorial for more sophisticated site plugins? Like using CSS styles, default images etc. Best regards, Eric - 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
AW: AW: How to create a report based on annotations
Yes, I know skins, but that's not what I meant. I meant how to create a rich report within a Maven plugin, using its standard images (if they exist) and formatting. Something like the output of http://mojo.codehaus.org/versions-maven-plugin/dependency-updates-report-mojo.html Best regards, Eric -Ursprüngliche Nachricht- Von: Lukas Theussl [mailto:ltheu...@apache.org] Gesendet: Dienstag, 18. Mai 2010 10:37 An: Maven Users List Betreff: Re: AW: How to create a report based on annotations No idea about the apt-maven-plugin, but for site customization, are you familiar with skins: http://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html ? HTH, -Lukas Lewis, Eric wrote: Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Montag, 17. Mai 2010 11:07 An: Maven Users List Betreff: How to create a report based on annotations Hi I'd like to create a Maven report based on annotations (OVal annotations, to be precise). Can I use the apt-maven-plugin for this (and if yes, how would I do it)? Also, is there a tutorial for more sophisticated site plugins? Like using CSS styles, default images etc. Best regards, Eric - 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
AW: AW: How to create a report based on annotations
Thanks, but it's not what I'm looking for. This describes how to customize your Maven site. But I want to know how to write a sophisticated report plugin. Best regards, Eric -Ursprüngliche Nachricht- Von: Marshall Schor [mailto:m...@schor.com] Gesendet: Dienstag, 18. Mai 2010 12:32 An: Maven Users List Betreff: Re: AW: How to create a report based on annotations On 5/18/2010 3:17 AM, Lewis, Eric wrote: Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Montag, 17. Mai 2010 11:07 An: Maven Users List Betreff: How to create a report based on annotations Hi I'd like to create a Maven report based on annotations (OVal annotations, to be precise). Can I use the apt-maven-plugin for this (and if yes, how would I do it)? Also, is there a tutorial for more sophisticated site plugins? Like using CSS styles, default images etc. This chapter of the Maven complete reference describes these topics: http://www.sonatype.com/books/mvnref-book/reference/site-generation.html -Marshall Schor Best regards, Eric - 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
How to create a report based on annotations
Hi I'd like to create a Maven report based on annotations (OVal annotations, to be precise). Can I use the apt-maven-plugin for this (and if yes, how would I do it)? Also, is there a tutorial for more sophisticated site plugins? Like using CSS styles, default images etc. Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Global dependencies report?
Hi We have a company-wide parent POM where all the versions of all dependencies are managed. Now it's very handy to have the Dependency Analysis in the site for each project, but we may have some dependencies declared in the company-wide parent POM which are never used in the projects. Is there any way to find them? Is there some sort of global overall dependency analysis? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Global dependencies report?
Hi Anders Sorry, I had some problems with the mailing list :-) I looked up your answer on Nabble, thanks for hint! I'll try it and check if it works. Best regards, Eric -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Donnerstag, 7. Januar 2010 16:32 An: Maven Users List Betreff: Re: Global dependencies report? Didn't you get my response to your mail sent on Jan 5? Did you try it? /Anders On Thu, Jan 7, 2010 at 16:26, Lewis, Eric eric.le...@ipi.ch wrote: Hi We have a company-wide parent POM where all the versions of all dependencies are managed. Now it's very handy to have the Dependency Analysis in the site for each project, but we may have some dependencies declared in the company-wide parent POM which are never used in the projects. Is there any way to find them? Is there some sort of global overall dependency analysis? Best regards, Eric - 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
AW: Multi Module: Deploy and failing modules
Hi Johannes You may want to take a look at Hudson: It builds the project and the modules, and if any of them fails, it doesn't deploy anything. Best regards, Eric -Ursprüngliche Nachricht- Von: Johannes Schneider [mailto:maili...@cedarsoft.com] Gesendet: Donnerstag, 7. Januar 2010 17:04 An: Maven Users List Betreff: Multi Module: Deploy and failing modules Hi, how do you solve that scenario: Multi module project that I try to deploy/install after a refactoring. Unfortunately one of the later modules fails. Now I have some sort of inconsistent snapshot repository. The artifacts within are no longer compatible. I'd prefer a method that first builds all modules and then deploys them together... Sincerly, Johannes - 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
Global dependencies report?
Hi We have a company-wide parent POM where all the versions of all dependencies are managed. Now it's very handy to have the Dependency Analysis in the site for each project, but we may have some dependencies declared in the company-wide parent POM which are never used in the projects. Is there any way to find them? Is there some sort of global overall dependency analysis? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: resouce files not in the built jar
Also, if you're not yet using it, get m2eclipse and import your Maven project. src/main/resources will be treated as source folder automatically. Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Mittwoch, 28. Oktober 2009 15:27 An: Maven Users List Betreff: Re: resouce files not in the built jar because resources should be in src/main/resources/___ and not src/main/java/___ eclipse is a fool... maven is a know-all -Stephen 2009/10/28 thomas2004 thomas200...@yahoo.de Hi all, I use maven 2.0.9 and Eclipse to build my program. But I met a strange thing: I put some resource files such as context.xml in the same package as my java files. But after I built the project/program with mvn clean package, I can't find the context.xml inside the jar. That's the reason why I got FileNotFoundException as I run the program. Someone knows why? -- View this message in context: http://www.nabble.com/resouce-files-not-in-the-built-jar-tp26095189p26095189.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: installing src or javadoc into local repository
Yes, m2eclipse can do that: You can right click on the dependency and choose to download the sources. However, I don't know whether you can do that for all dependencies at once. Best regards, Eric -Ursprüngliche Nachricht- Von: Roland Asmann [mailto:roland.asm...@cfc.at] Gesendet: Mittwoch, 21. Oktober 2009 10:21 An: Maven Users List Betreff: Re: installing src or javadoc into local repository Personally I use the maven-eclipse-plugin for that... mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true Not sure if the M2Eclipse -plugin can do the same, maybe someone who knows can shed a light (or already did, working through the list of unread messages as I write this). Roland On Wednesday 21 October 2009 05:16, jpswain wrote: I looked at the link but I still have these questions: Is there any sane way to simply tell maven, download and install src javadoc for all artifacts in local repository? If not is their at least a way to say, install this jar with javadoc src, AND ALSO the javadoc src of all its transitive dependencies? I'm having a heck of a time with this! Thanks, Jamie Sean Davis-5 wrote: On Fri, Oct 2, 2009 at 8:35 PM, Roland Asmann roland.asm...@cfc.at wrote: Check the install-mojo for this: http://maven.apache.org/plugins/maven-install-plugin/install-f ile-mojo.h tml Reinstall the jar into your repository and add the 'javadoc' and 'sources' switches or install them separately with the 'classifier' switch. Thanks, Roland. That is exactly what I needed. I apologize for the naive question in advance. I have installed an external jar file into my local repository--very easy. The jar file was built using ant as part of a third-party project. I would now like to add the source and/or the javadocs to my local repository, also. I have the source (in src/java/) and can generate the javadoc. How can I install these files into my local repository (so that I have the equivalent of the download sources and javadocs)? Thanks, Sean - 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 -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: roland.asm...@cfc.at Web: www.cfc.at - 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
AW: Including dependencies with assembly plugin: Scope problem
Anyone? :-)
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Freitag, 9. Oktober 2009 18:03
An: Maven Users List
Betreff: Including dependencies with assembly plugin: Scope problem
Hi
I'm trying to include all the runtime dependencies with an
assembly descriptor:
!-- The runtime dependencies --
dependencySet
useStrictFilteringtrue/useStrictFiltering
useProjectArtifactfalse/useProjectArtifact
outputDirectory${batch.zip.library}/outputDirectory
scoperuntime/scope
!-- Don't distribute sources --
excludes
exclude*:sources/exclude
/excludes
/dependencySet
Now I have a dependency which in a parent POM has the scope
'test'. In my project, however, that's redefined to 'runtime'.
The problem is that it's not included in the final ZIP file,
and I don't understand why.
Maven's debugging output handles the scope differently
(sometimes it appears to be 'test', sometimes 'runtime') and
finally filters it because it's considered 'test'.
Can someone help me?
Best regards,
Eric
-
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
AW: Running Jar file created by Maven
Hi Tom The easiest way is to use the appassembler plugin. Best regards, Eric -Ursprüngliche Nachricht- Von: jamborta [mailto:jambo...@gmail.com] Gesendet: Dienstag, 13. Oktober 2009 11:23 An: users@maven.apache.org Betreff: Running Jar file created by Maven Hi guys, I'm new to Maven. I have this problem that I created a Maven project in netbeans, added dependencies, and build it successfully, it runs in Netbeans as well. but if I try to build it from the command prompt using mvn install, it build the whole staff, but when I try to run the jar file, it just fails becuase it cannot find the library files (dependencies), looks like maven doesn't add those files, although it downloads them... please help me, i'm looking for the answer for quite a while now. thanks Tom -- View this message in context: http://www.nabble.com/Running-Jar-file-created-by-Maven-tp2586 9690p25869690.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Versions plugin and metadata
It turns out that the metadata was wrong in Nexus and copied over to the local repo. Just if anyone else has this problem... Best regards, Eric -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Mittwoch, 7. Oktober 2009 17:19 An: Maven Users List Betreff: AW: Versions plugin and metadata Umm... after re-reading: I don't mean that the versions plugin is the source of trouble, but my messed up repo is! Best regards, Eric -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Mittwoch, 7. Oktober 2009 17:17 An: Maven Users List Betreff: Versions plugin and metadata Hi I'm having a lot of trouble with the versions plugin. I was doing a lot of tests where I deployed a lot of versions and SNAPSHOTs into our local Nexus repo. After the tests I deleted all these test versions from Nexus and rebuilt the index. However, I forgot the local repo, where everything was still alive (I noticed since the versions plugin put in some of those test versions). After cleaning that up (basically deleting everything), I'm still having trouble. As was answered before, the versions plugin gets the version from the metadata in the repo and then tries to find that version/SNAPSHOT in the repo. This then is the point where things fall apart, because my metadata tells me the latest SNAPSHOT is 1.18.0-SNAPSHOT while the repo only contains 1.0.0-SNAPSHOT. To make a long story short: How can I deleted all that wrong metadata and make sure it never comes back to haunt me? Thanks for any pointer... Best regards, Eric - 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
Including dependencies with assembly plugin: Scope problem
Hi
I'm trying to include all the runtime dependencies with an assembly descriptor:
!-- The runtime dependencies --
dependencySet
useStrictFilteringtrue/useStrictFiltering
useProjectArtifactfalse/useProjectArtifact
outputDirectory${batch.zip.library}/outputDirectory
scoperuntime/scope
!-- Don't distribute sources --
excludes
exclude*:sources/exclude
/excludes
/dependencySet
Now I have a dependency which in a parent POM has the scope 'test'. In my
project, however, that's redefined to 'runtime'.
The problem is that it's not included in the final ZIP file, and I don't
understand why.
Maven's debugging output handles the scope differently (sometimes it appears to
be 'test', sometimes 'runtime') and finally filters it because it's considered
'test'.
Can someone help me?
Best regards,
Eric
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Versions plugin and metadata
Hi I'm having a lot of trouble with the versions plugin. I was doing a lot of tests where I deployed a lot of versions and SNAPSHOTs into our local Nexus repo. After the tests I deleted all these test versions from Nexus and rebuilt the index. However, I forgot the local repo, where everything was still alive (I noticed since the versions plugin put in some of those test versions). After cleaning that up (basically deleting everything), I'm still having trouble. As was answered before, the versions plugin gets the version from the metadata in the repo and then tries to find that version/SNAPSHOT in the repo. This then is the point where things fall apart, because my metadata tells me the latest SNAPSHOT is 1.18.0-SNAPSHOT while the repo only contains 1.0.0-SNAPSHOT. To make a long story short: How can I deleted all that wrong metadata and make sure it never comes back to haunt me? Thanks for any pointer... Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Versions plugin and metadata
Umm... after re-reading: I don't mean that the versions plugin is the source of trouble, but my messed up repo is! Best regards, Eric -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Mittwoch, 7. Oktober 2009 17:17 An: Maven Users List Betreff: Versions plugin and metadata Hi I'm having a lot of trouble with the versions plugin. I was doing a lot of tests where I deployed a lot of versions and SNAPSHOTs into our local Nexus repo. After the tests I deleted all these test versions from Nexus and rebuilt the index. However, I forgot the local repo, where everything was still alive (I noticed since the versions plugin put in some of those test versions). After cleaning that up (basically deleting everything), I'm still having trouble. As was answered before, the versions plugin gets the version from the metadata in the repo and then tries to find that version/SNAPSHOT in the repo. This then is the point where things fall apart, because my metadata tells me the latest SNAPSHOT is 1.18.0-SNAPSHOT while the repo only contains 1.0.0-SNAPSHOT. To make a long story short: How can I deleted all that wrong metadata and make sure it never comes back to haunt me? Thanks for any pointer... Best regards, Eric - 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: Including the project's pom.xml in generated site ?
Hi
I may be a bit late ;-) but since I had the same problem, I sending the
solution. Hope it helps you.
In your build, add the following:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
executions
execution
idadd-pom-to-site/id
phasesite/phase
goals
goalcopy-resources/goal
/goals
configuration
outputDirectory${project.reporting.outputDirectory}/outputDirectory
resources
resource
directory.//directory
includes
includepom.xml/include
/includes
filteringfalse/filtering
/resource
/resources
/configuration
/execution
/executions
/plugin
Best regards,
Eric
Tobias Gierke-2 wrote:
Hi,
Is there currently a (simple) way to deploy a project's pom.xml together
with the generated site upon release ?
The reason I'm asking is this:
All my sites get deployed into different subdirectories of the same base
directory on a webserver. I want to be able to dynamically discover the
project's documentation and render a top-level 'entry' HTML page that
provides links to each project's individual index.html along with some
details from the release POM (version,groupId,description etc.). These
details obviously can't be easily parsed from the generated site HTML.
I've already written a small patch for the site plugin (that adds a
addPom/ configuration option) but I'd really like to have this feature
without having to patch the plugin every time a new release comes up.
Thanks in advance,
Tobias
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://www.nabble.com/Including-the-project%27s-pom.xml-in-generated-site---tp22325784p25748592.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
AW: How to add generated resources directory in a plugin
Just out of curiosity: Is there a reason that you keep the .cdr files in src/main/java? IMHO you could have them in src/main/resources, since they end up in target/classes anyway. Best regards, Eric -Ursprüngliche Nachricht- Von: Werner Guttmann [mailto:wgut...@codehaus.org] Gesendet: Freitag, 2. Oktober 2009 13:13 An: Maven Users List Betreff: Re: How to add generated resources directory in a plugin That does not really match what I am observing .. :-(. If I generate Java sources and resources into target/generated-sources/castor and use project.addCompileSourceRoot(target/generated-sources/castor) within the Maven plugin for Castor, Maven will include the generated Java classes during compilation and put the class files in target/classes of the project. As a result of this, users of the Maven plugin for Castor currently have to add the following section to their project POMs. resources resource directorytarget/generated-sources/castor/directory includes include**/*.cdr/include /includes /resource resource directorysrc/main/resources/directory /resource /resources to have those .castor.cdr Files copied to target/classes as well. As we all know, this is error-prone. As such, I tried to add code to the Maven plugin for Castor as follows: Resource resource = new Resource(); resource.setDirectory( getResourceDestination().getAbsolutePath() ); ListString includes = new LinkedListString(); includes.add( **/*.cdr ); resource.setIncludes( includes ); project.addResource( resource ); Problem is that once I add that code, the Java source files start showing up in target/classes, which is not ideal. Any idea what's going wrong here ? Werner Roland Asmann wrote: I believe this can work (not 100% sure, I generate into two different directories for sources and resources), but you should probably ONLY use the addCompileSourceRoot for your directory... The way I understand it, is that if you put sources resources there, they are compiled to the output dir. Java knows how to handle .java-files -- convert them to classes, and how to handle anything else -- just copy. If you use the resource-dir, maven will handle the copying and will copy everything from the source to the target, without compiling. So, I presume you have used both calls I gave you, although you should only use one. Hope this helps, On Thursday 01 October 2009 15:15, Werner Guttmann wrote: Hi Roland, does this pattern/recipe change if both resources and Java classes would be generated in the same directory. I have tried this a few days ago (trying to automate a few things for the castor-maven-plugin), and it seems like this does not really work. Assume you have a directory where you'll find - A.java - B.java - .castor.cdr where the last is a resource file. If I use above code snippets, I can see in the target folder after a plugin run and subsequent compilation the compiled Java classes, the resource file and the source files. How can I avoid the source files to be copy across ? Regards Werner Roland Asmann wrote: Assuming you already have the maven-project as a variable in your plugin (if not, add it!): project.addCompileSourceRoot(your output directory here); And in the case of resources: Resource resource = new Resource(); resource.setDirectory(your output directory here); resource.addInclude(**/*); project.addResource(resource); On Thursday 01 October 2009 13:59, Lewis, Eric wrote: Hi I'm writing a plugin which generates resources and also test resources. How in my plugin can I add these directories to the sources paths and the test resources paths? (Except for using the build-helper plugin) Best regards, Eric - 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
AW: AW: How to add generated resources directory in a plugin
Hi Werner
Yup, I had the same problem, but I'm generating my resources into
target/generated-resources/xyz and then adding that to my build:
Resource resource = new Resource();
resource.setDirectory(targetDirectory.getAbsolutePath());
resource.addInclude(**/*);
if (createTestConfiguration) {
mavenProject.addTestResource(resource);
} else {
mavenProject.addResource(resource);
}
They will still end up in target/classes or target/test-classes.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Werner Guttmann [mailto:wgut...@codehaus.org]
Gesendet: Freitag, 2. Oktober 2009 13:46
An: Maven Users List
Betreff: Re: AW: How to add generated resources directory in a plugin
Eric,
the .castor.cdr files are a by-product of generating Java classes from
an XML schema using the XML code generator of Castor (through
the Maven
plugin for Castor).
Those resource files are being generated in
target/generated-sources/castor during code generation.
I hopes this makes it clearer
Werner
Lewis, Eric wrote:
Just out of curiosity: Is there a reason that you keep the
.cdr files in src/main/java?
IMHO you could have them in src/main/resources, since they
end up in target/classes anyway.
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Werner Guttmann [mailto:wgut...@codehaus.org]
Gesendet: Freitag, 2. Oktober 2009 13:13
An: Maven Users List
Betreff: Re: How to add generated resources directory in a plugin
That does not really match what I am observing .. :-(.
If I generate Java sources and resources into
target/generated-sources/castor
and use
project.addCompileSourceRoot(target/generated-sources/castor)
within the Maven plugin for Castor, Maven will include the
generated
Java classes during compilation and put the class files in
target/classes of the project.
As a result of this, users of the Maven plugin for Castor
currently have
to add the following section to their project POMs.
resources
resource
directorytarget/generated-sources/castor/directory
includes
include**/*.cdr/include
/includes
/resource
resource
directorysrc/main/resources/directory
/resource
/resources
to have those .castor.cdr Files copied to target/classes as
well. As we
all know, this is error-prone.
As such, I tried to add code to the Maven plugin for Castor
as follows:
Resource resource = new Resource();
resource.setDirectory(
getResourceDestination().getAbsolutePath() );
ListString includes = new LinkedListString();
includes.add( **/*.cdr );
resource.setIncludes( includes );
project.addResource( resource );
Problem is that once I add that code, the Java source files start
showing up in target/classes, which is not ideal.
Any idea what's going wrong here ?
Werner
Roland Asmann wrote:
I believe this can work (not 100% sure, I generate into two
different
directories for sources and resources), but you should
probably ONLY use the
addCompileSourceRoot for your directory...
The way I understand it, is that if you put sources
resources there, they
are compiled to the output dir. Java knows how to handle
.java-files --
convert them to classes, and how to handle anything else
-- just copy.
If you use the resource-dir, maven will handle the copying
and will copy
everything from the source to the target, without compiling.
So, I presume you have used both calls I gave you, although
you should only
use one.
Hope this helps,
On Thursday 01 October 2009 15:15, Werner Guttmann wrote:
Hi Roland,
does this pattern/recipe change if both resources and Java
classes would
be generated in the same directory. I have tried this a
few days ago
(trying to automate a few things for the
castor-maven-plugin), and it
seems like this does not really work.
Assume you have a directory where you'll find
- A.java
- B.java
- .castor.cdr
where the last is a resource file. If I use above code
snippets, I can
see in the target folder after a plugin run and subsequent
compilation
the compiled Java classes, the resource file and the
source files.
How can I avoid the source files to be copy across ?
Regards
Werner
Roland Asmann wrote:
Assuming you already have the maven-project as a variable
in your plugin
(if not, add it!):
project.addCompileSourceRoot(your output directory here);
And in the case of resources:
Resource resource = new Resource();
resource.setDirectory(your output directory here);
resource.addInclude(**/*);
project.addResource(resource);
On Thursday 01 October 2009 13:59, Lewis, Eric wrote:
Hi
I'm writing a plugin which generates resources and also
test resources.
How in my plugin can I add these directories to the
sources paths
Get dependencies in generate-sources phase?
Hi I'm trying to access my project's classpath in a plugin I'm writing, which should generate JPA's persistence.xml file from JPA entities found on the classpath. To work, this should run during the generate-sources phase, but do I have access to the projects dependencies (transivite dependencies, if possible) at that point? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Get dependencies in generate-sources phase?
Thanks, works well! Best regards, Eric -Ursprüngliche Nachricht- Von: Tony Chemit [mailto:che...@codelutin.com] Gesendet: Mittwoch, 30. September 2009 16:43 An: users@maven.apache.org Betreff: Re: Get dependencies in generate-sources phase? Le Wed, 30 Sep 2009 16:27:54 +0200, Lewis, Eric eric.le...@ipi.ch a écrit : Hi I'm trying to access my project's classpath in a plugin I'm writing, which should generate JPA's persistence.xml file from JPA entities found on the classpath. To work, this should run during the generate-sources phase, but do I have access to the projects dependencies (transivite dependencies, if possible) at that point? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org You can use the annotation @requiresDependencyResolution compile|runtime|test [0] on your mojo Then you should be able to access the project dependencies [0] http://www.sonatype.com/books/maven-book/reference/writing-plu gins-sect-class-annotations.html -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - 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
Useful tutorials about Velocity, Maven and Plexus
Hi Can someone point me to a tutorial on how to use Velocity in Maven based on Plexus? I have found only snippets, but not a full tutorial. Right now, I get the VelocityComponent, but I can't read my template... Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: How to specify a plugin version from the command line?
Hmmm... This works: mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe -Dplugin=help This doesn't work: mvn org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe -Dplugin=help Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:36 An: users@maven.apache.org Betreff: RE: AW: How to specify a plugin version from the command line? try [1.0,2.0) version 1.0 = x 2.0 inclusive http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an d+Conflict+Resolution#DependencyMediationandConflictResolution -DependencyVersionRanges Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: eric.le...@ipi.ch To: users@maven.apache.org Date: Wed, 16 Sep 2009 17:25:33 +0200 Subject: AW: How to specify a plugin version from the command line? Hi Martin Thanks, that works. However, it's not really elegant ;-) Is there a way to nail the plugin versions somewhere in the configuration? If possible with version ranges, like [2.3) Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:21 An: users@maven.apache.org Betreff: RE: How to specify a plugin version from the command line? Eric did you try running mvn with groupId:artifactId:version:goal at command line e.g. mvn PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. apache.org/guides/plugin/guide-java-plugin-development.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: eric.le...@ipi.ch To: users@maven.apache.org Date: Wed, 16 Sep 2009 17:11:46 +0200 Subject: How to specify a plugin version from the command line? Hi I'm setting the exact versions for all Maven plugins in our company-wide parent POM. However, that doesn't help when I'm using the command line. So how can I force Maven to use a certain version of a plugin? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail: Free, trusted and rich email service. http://clk.atdmt.com/GBL/go/171222984/direct/01/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Ready for Fall shows? Use Bing to find helpful ratings and reviews on digital tv's.
AW: AW: How to specify a plugin version from the command line?
Ok, that's no problem, but can I specify somewhere that Maven should at least take version x for plugin y? Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Donnerstag, 17. September 2009 10:41 An: Maven Users List Betreff: Re: AW: How to specify a plugin version from the command line? version ranges are not supported for plugins 2009/9/17 Lewis, Eric eric.le...@ipi.ch: Hmmm... This works: mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe -Dplugin=help This doesn't work: mvn org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe -Dplugin=help Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:36 An: users@maven.apache.org Betreff: RE: AW: How to specify a plugin version from the command line? try [1.0,2.0) version 1.0 = x 2.0 inclusive http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an d+Conflict+Resolution#DependencyMediationandConflictResolution -DependencyVersionRanges Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: eric.le...@ipi.ch To: users@maven.apache.org Date: Wed, 16 Sep 2009 17:25:33 +0200 Subject: AW: How to specify a plugin version from the command line? Hi Martin Thanks, that works. However, it's not really elegant ;-) Is there a way to nail the plugin versions somewhere in the configuration? If possible with version ranges, like [2.3) Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:21 An: users@maven.apache.org Betreff: RE: How to specify a plugin version from the command line? Eric did you try running mvn with groupId:artifactId:version:goal at command line e.g. mvn PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. apache.org/guides/plugin/guide-java-plugin-development.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: eric.le...@ipi.ch To: users@maven.apache.org Date: Wed, 16 Sep 2009 17:11:46 +0200 Subject: How to specify a plugin version from the command line? Hi I'm setting the exact versions for all Maven plugins in our company-wide parent POM. However, that doesn't help when I'm using the command line. So how can I force Maven to use a certain version of a plugin? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: How to specify a plugin version from the command line?
Ok, but this doesn't work when I use install:install-file, because that POM I'm using is not under my control. So in this case I have to fully qualify the plugin including the version, right? Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Donnerstag, 17. September 2009 10:44 An: Maven Users List Betreff: Re: AW: How to specify a plugin version from the command line? plugin management of current pom or any of its parents 2009/9/17 Lewis, Eric eric.le...@ipi.ch: Ok, that's no problem, but can I specify somewhere that Maven should at least take version x for plugin y? Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Donnerstag, 17. September 2009 10:41 An: Maven Users List Betreff: Re: AW: How to specify a plugin version from the command line? version ranges are not supported for plugins 2009/9/17 Lewis, Eric eric.le...@ipi.ch: Hmmm... This works: mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe -Dplugin=help This doesn't work: mvn org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe -Dplugin=help Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:36 An: users@maven.apache.org Betreff: RE: AW: How to specify a plugin version from the command line? try [1.0,2.0) version 1.0 = x 2.0 inclusive http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an d+Conflict+Resolution#DependencyMediationandConflictResolution -DependencyVersionRanges Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: eric.le...@ipi.ch To: users@maven.apache.org Date: Wed, 16 Sep 2009 17:25:33 +0200 Subject: AW: How to specify a plugin version from the command line? Hi Martin Thanks, that works. However, it's not really elegant ;-) Is there a way to nail the plugin versions somewhere in the configuration? If possible with version ranges, like [2.3) Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:21 An: users@maven.apache.org Betreff: RE: How to specify a plugin version from the command line? Eric did you try running mvn with groupId:artifactId:version:goal at command line e.g. mvn PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. apache.org/guides/plugin/guide-java-plugin-development.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni
AW: Maven2 jsf-web project on Eclipse
Have you tried m2eclipse? Best regards, Eric -Ursprüngliche Nachricht- Von: MavenZede [mailto:asiyeki...@gmail.com] Gesendet: Donnerstag, 17. September 2009 16:11 An: users@maven.apache.org Betreff: Maven2 jsf-web project on Eclipse I have been trying to run a maven2 jsf project on Eclipse Galileo, but I did not unfortunately. I tried a lot of ways, read thousands of web pages. My first problem is that I cannot import my maven2 web project into Eclipse. I know it should be happen when I run this mvn eclipse:eclipse, however it doesnt. The eclipse project file (.project) already came after I run above mentioned command, but again unfortunately this .project file could not opened with eclipse. Some specification of system are ; ---Apache tomcat 6.0 ---myFaces 1.2.7 for jsf ---Eclipse galileo (3.5 with WTP 3.1) -- View this message in context: http://www.nabble.com/Maven2-jsf-web-project-on-Eclipse-tp2549 1908p25491908.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to specify a plugin version from the command line?
Hi I'm setting the exact versions for all Maven plugins in our company-wide parent POM. However, that doesn't help when I'm using the command line. So how can I force Maven to use a certain version of a plugin? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: How to specify a plugin version from the command line?
Hi Martin Thanks, that works. However, it's not really elegant ;-) Is there a way to nail the plugin versions somewhere in the configuration? If possible with version ranges, like [2.3) Best regards, Eric -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Mittwoch, 16. September 2009 17:21 An: users@maven.apache.org Betreff: RE: How to specify a plugin version from the command line? Eric did you try running mvn with groupId:artifactId:version:goal at command line e.g. mvn PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. apache.org/guides/plugin/guide-java-plugin-development.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: eric.le...@ipi.ch To: users@maven.apache.org Date: Wed, 16 Sep 2009 17:11:46 +0200 Subject: How to specify a plugin version from the command line? Hi I'm setting the exact versions for all Maven plugins in our company-wide parent POM. However, that doesn't help when I'm using the command line. So how can I force Maven to use a certain version of a plugin? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail: Free, trusted and rich email service. http://clk.atdmt.com/GBL/go/171222984/direct/01/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
versions Plugin: Where do the versions come from?
Hi I'm using the versions plugin to update my POM to the latest availabe SNAPSHOT versions. However, one version, which was a typo, keeps creeping in: I wrote 1.44-SNAPSHOT instead of 1.4.4-SNAPSHOT, so the former is higher than the latter and any other SNAPSHOT version that I have. I've removed that version from the local repo, I've removed it from our corporate repo (Nexus), but it still comes up. So how does the versions plugin determine the versions? Can I trace this? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Compiler plugin: Ignore warnings for tests - how?
Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Dienstag, 1. September 2009 17:13 An: Maven Users List Betreff: Compiler plugin: Ignore warnings for tests - how? Hi Sorry if this has been answered before, but I didn't find anything on the mailing list. I've configured the Compiler Plugin in general, setting showWarningstrue/showWarnings. However, for the tests, I would like to set it to showWarningsfalse/showWarnings. How can I do that? Best regards, Eric - 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
AW: Automated release process
Well, if you have configured your jobs in Hudson to be built whenever something changes in your SCM, you could compare the current date to the latest build. This would answer the question whether a release is required. As for releasing with Hudson, you might want to use the release plugin and start it with Hudson's CLI or wget. However, I don't think Hudson solves your specific requirements out-of-the-box (meaning: in an automated process). I think you would have to write a script which is then called every two weeks (e.g. with cron). But you would have to do that with Maven anyway. Best regards, Eric -Ursprüngliche Nachricht- Von: Matt Milliss [mailto:matt.mill...@gmail.com] Gesendet: Montag, 14. September 2009 01:00 An: Maven Users List Betreff: Re: Automated release process Thanks Thomas, we're using hudson as our CI server but I don't really understand how this will solve my problem for me. We've got hudson setup to deploy snapshots to our archiva repository on every svn commit and we're using unique/timestamped snapshots, but not really sure how hudson can automatically perform a release:prepare/perform step at a given point in time ie every 2 weeks on only projects have changed since the last release. Am I missing some feature that hudson supplies? Or am I just doing things wrong all over the place? Cheers Matt Thomas Sundberg wrote: Hi! It sounds as you need a CI server. It would solve your issue. Take a look at CruiseControl:http://cruisecontrol.sourceforge.net/ Hudson:https://hudson.dev.java.net/ /Thomas On Thu, Sep 10, 2009 at 13:10, Matt Milliss matt.mill...@gmail.com matt.mill...@gmail.com wrote: I work at a company that has around 10 applications, each application is a maven project, each of which may or may not get modified in a given 2 week iteration. At the end of every iteration I want an automated process for checking which applications have been modified since the last release and then release only those applications. Something along the lines of the following; 1. retrieve previous release version from our archiva repo 2. in subversion compare that versions tag against trunk to see any differences 3. if any differences then perform a release of that project 4. repeat for each application I've been trying to find a maven way of doing this but haven't had any luck, has anybody done something similar with success. Cheers Matt Milliss - 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
Versions Plugin: use-latest-versions vs. use-next-versions?
Hi I'm a bit confused about these two goals in the Versions Plugin. For both, the documentation says Replaces any version with the latest version. What I want to do is replace x.y.z-SNAPSHOT by x.y.z Supposing that my project has a dependency on foo:1.2.3-SNAPSHOT and both foo:1.2.3 and foo:2.0.0 exist as releases in the repo. My guess is that use-latest-versions changes the dependency to foo:2.0.0 and use-next-versions changes it to foo:1.2.3 - is that correct? Best regards, Eric P.S. The versions plugin is great, but it's kind of hard to make the distinction between all the use-(latest|next)-(releases|snapshots|versions) goals. I mean, what is the difference between a release and a version? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Versions Plugin: use-latest-versions vs. use-next-versions?
Thanks a lot for the great explanation! And I filed http://jira.codehaus.org/browse/MVERSIONS-73 Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Montag, 14. September 2009 16:49 An: Maven Users List Betreff: Re: Versions Plugin: use-latest-versions vs. use-next-versions? Can you file a JIRA to update this page: http://mojo.codehaus.org/versions-maven-plugin/examples/advanc ing-dependency-versions.html with a matrix table showing what the different goals do exactly. Cheers -Stephen 2009/9/14 Stephen Connolly stephen.alan.conno...@gmail.com: 2009/9/14 Lewis, Eric eric.le...@ipi.ch: Hi I'm a bit confused about these two goals in the Versions Plugin. For both, the documentation says Replaces any version with the latest version. What I want to do is replace x.y.z-SNAPSHOT by x.y.z Supposing that my project has a dependency on foo:1.2.3-SNAPSHOT and both foo:1.2.3 and foo:2.0.0 exist as releases in the repo. My guess is that use-latest-versions changes the dependency to foo:2.0.0 and use-next-versions changes it to foo:1.2.3 - is that correct? yes... put you probably want: use-releases use-___-versions will consider both -SNAPSHOT and non-SNAPSHOT for any dependency use-___-releases will consider only newer releases of only -SNAPSHOT dependencies use-___-snapshots will consider only newer -SNAPSHOTs of only release dependencies use-next- will only consider the next version within the update scope you specify. use-latest-___ will only consider the absolute newest version within the update scope you specify. the available versions are 1.1.2-SNAPSHOT, 1.1.2, 1.2, 1.2.1, 1.2.2, 1.3, 1.3.1, 1.4, 1.4.1, 2.0, 2.0.1, 2.1.0, 2.2-SNAPSHOT your current version is 1.1.1 use-next-versions - 1.1.2-SNAPSHOT (if allowSnapshots, otherwise 1.1.2) use-latest-versions - 2.2-SNAPSHOT (if allowSnapshots, otherwise 2.1.0) use-next-release - 1.1.2 use-latest-release - 2.1.0 use-next-snapshots - 1.1.2-SNAPSHOT use-latest-snapshots - 1.1.2-SNAPSHOT (if allowMajorUpdates=false otherwise 2.2-SNAPSHOT) use-releases - 1.1.1 (because it's already a release) your current version is 1.3-SNAPSHOT use-next-versions - 1.3 use-latest-versions - 2.2-SNAPSHOT (if allowSnapshots, otherwise 2.1.0) use-next-release - 1.3 use-latest-release - 2.1.0 use-next-snapshots - 1.3-SNAPSHOT (if allowMajorUpdates=false otherwise 2.2-SNAPSHOT) use-latest-snapshots - 1.3-SNAPSHOT (if allowMajorUpdates=false otherwise 2.2-SNAPSHOT) use-releases - 1.3 -Stephen Best regards, Eric P.S. The versions plugin is great, but it's kind of hard to make the distinction between all the use-(latest|next)-(releases|snapshots|versions) goals. I mean, what is the difference between a release and a version? - 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
AW: How to update parent during release:prepare
Hi Dave Thanks for the answer, but it's not quite what I meant :-) I don't mean the parent version within the modules, but the parent version within the project (i.e. the module's parent). Let's say I have a company wide POM in the repo company-pom:1.2.0-SNAPSHOT which has been released to company-pom:1.2.0 All my projects depend on this (showing hierarchies by indenting and the specified parent in the POM with an arrow): my-project:3.0.0-SNAPSHOT - company-pom:1.2.0-SNAPSHOT my-module-1:2.1.0-SNAPSHOT - my-project:3.0.0-SNAPSHOT my-module-2:5.3.7-SNAPSHOT - my-project:3.0.0-SNAPSHOT Now I need to release my-project, so the result should be my-project:3.0.0 - company-pom:1.2.0 my-module-1:2.1.0 - my-project:3.0.0 my-module-2:5.3.7 - my-project:3.0.0 As you say, changing the modules from my-project:3.0.0-SNAPSHOT to my-project:3.0.0 is done with -DautoVersionSubmodules=true, but how do I update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 within my-project? Best regards, Eric -Ursprüngliche Nachricht- Von: David C. Hicks [mailto:dhi...@i-hicks.org] Gesendet: Donnerstag, 10. September 2009 19:03 An: Maven Users List Betreff: Re: How to update parent during release:prepare The autoVersionSubmodules property can be used to tell the release plugin to use the Parent's version for all of the child modules. Are your modules all the same version as your parent? If so, then it should work as-is. I normally use the command: mvn -DautoVersionSubmodules=true release:prepare to start the process on a project with about 8 modules. It'll ask me for the release version of the parent and then the next development version. Beyond that, it's all automatic. Dave On 09/10/2009 05:30 AM, Lewis, Eric wrote: Hi I'm trying to use release:prepare for a project with several modules. The project has a parent which is a SNAPSHOT. Now my question is: How can I tell release:prepare to update the project's parent version to the parent's released version? Best regards, Eric - 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
AW: How to update parent during release:prepare
Thanks, that works well! However, I'm still wondering whether I'm the only one releasing that way. It seems to me that the release plugin can only be used together with the versions plugin. I think that most developers have some sort of company-wide parent POM which they refer to, and when releasing, they probably all have the same problem as I do. Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Freitag, 11. September 2009 15:41 An: Maven Users List Betreff: Re: How to update parent during release:prepare before you run a release just run mvn versions:update-parent mvn versions:commit mvn release:prepare release:perform 2009/9/11 Lewis, Eric eric.le...@ipi.ch Hi Dave Thanks for the answer, but it's not quite what I meant :-) I don't mean the parent version within the modules, but the parent version within the project (i.e. the module's parent). Let's say I have a company wide POM in the repo company-pom:1.2.0-SNAPSHOT which has been released to company-pom:1.2.0 All my projects depend on this (showing hierarchies by indenting and the specified parent in the POM with an arrow): my-project:3.0.0-SNAPSHOT - company-pom:1.2.0-SNAPSHOT my-module-1:2.1.0-SNAPSHOT - my-project:3.0.0-SNAPSHOT my-module-2:5.3.7-SNAPSHOT - my-project:3.0.0-SNAPSHOT Now I need to release my-project, so the result should be my-project:3.0.0 - company-pom:1.2.0 my-module-1:2.1.0 - my-project:3.0.0 my-module-2:5.3.7 - my-project:3.0.0 As you say, changing the modules from my-project:3.0.0-SNAPSHOT to my-project:3.0.0 is done with -DautoVersionSubmodules=true, but how do I update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 within my-project? Best regards, Eric -Ursprüngliche Nachricht- Von: David C. Hicks [mailto:dhi...@i-hicks.org] Gesendet: Donnerstag, 10. September 2009 19:03 An: Maven Users List Betreff: Re: How to update parent during release:prepare The autoVersionSubmodules property can be used to tell the release plugin to use the Parent's version for all of the child modules. Are your modules all the same version as your parent? If so, then it should work as-is. I normally use the command: mvn -DautoVersionSubmodules=true release:prepare to start the process on a project with about 8 modules. It'll ask me for the release version of the parent and then the next development version. Beyond that, it's all automatic. Dave On 09/10/2009 05:30 AM, Lewis, Eric wrote: Hi I'm trying to use release:prepare for a project with several modules. The project has a parent which is a SNAPSHOT. Now my question is: How can I tell release:prepare to update the project's parent version to the parent's released version? Best regards, Eric - 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
AW: How to update parent during release:prepare
Yes, this is exactly what I'm doing. Still, I want to change the parent to the released version *and* release the project in one go. And it seems like this is only possible by combining the versions and the release plugins. Best regards, Eric -Ursprüngliche Nachricht- Von: David Hoffer [mailto:dhoff...@gmail.com] Gesendet: Freitag, 11. September 2009 15:57 An: Maven Users List Betreff: Re: How to update parent during release:prepare Woudn't it better to first release your company-wide parent poms first? Then release projects that refer to released poms? Otherwise it seems you would now have to chase down all the old references to the prior snapshot parent and manually update. -Dave On Fri, Sep 11, 2009 at 7:51 AM, Lewis, Eric eric.le...@ipi.ch wrote: Thanks, that works well! However, I'm still wondering whether I'm the only one releasing that way. It seems to me that the release plugin can only be used together with the versions plugin. I think that most developers have some sort of company-wide parent POM which they refer to, and when releasing, they probably all have the same problem as I do. Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Freitag, 11. September 2009 15:41 An: Maven Users List Betreff: Re: How to update parent during release:prepare before you run a release just run mvn versions:update-parent mvn versions:commit mvn release:prepare release:perform 2009/9/11 Lewis, Eric eric.le...@ipi.ch Hi Dave Thanks for the answer, but it's not quite what I meant :-) I don't mean the parent version within the modules, but the parent version within the project (i.e. the module's parent). Let's say I have a company wide POM in the repo company-pom:1.2.0-SNAPSHOT which has been released to company-pom:1.2.0 All my projects depend on this (showing hierarchies by indenting and the specified parent in the POM with an arrow): my-project:3.0.0-SNAPSHOT - company-pom:1.2.0-SNAPSHOT my-module-1:2.1.0-SNAPSHOT - my-project:3.0.0-SNAPSHOT my-module-2:5.3.7-SNAPSHOT - my-project:3.0.0-SNAPSHOT Now I need to release my-project, so the result should be my-project:3.0.0 - company-pom:1.2.0 my-module-1:2.1.0 - my-project:3.0.0 my-module-2:5.3.7 - my-project:3.0.0 As you say, changing the modules from my-project:3.0.0-SNAPSHOT to my-project:3.0.0 is done with -DautoVersionSubmodules=true, but how do I update company-pom:1.2.0-SNAPSHOT to company-pom:1.2.0 within my-project? Best regards, Eric -Ursprüngliche Nachricht- Von: David C. Hicks [mailto:dhi...@i-hicks.org] Gesendet: Donnerstag, 10. September 2009 19:03 An: Maven Users List Betreff: Re: How to update parent during release:prepare The autoVersionSubmodules property can be used to tell the release plugin to use the Parent's version for all of the child modules. Are your modules all the same version as your parent? If so, then it should work as-is. I normally use the command: mvn -DautoVersionSubmodules=true release:prepare to start the process on a project with about 8 modules. It'll ask me for the release version of the parent and then the next development version. Beyond that, it's all automatic. Dave On 09/10/2009 05:30 AM, Lewis, Eric wrote: Hi I'm trying to use release:prepare for a project with several modules. The project has a parent which is a SNAPSHOT. Now my question is: How can I tell release:prepare to update the project's parent version to the parent's released version? Best regards, Eric - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail
AW: How to update parent during release:prepare
Yes, that would be the ideal solution. In the meantime, I'm avoiding manual and error-prone work by putting the process into a shell script. Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Duncan Jr [mailto:stephen.dun...@gmail.com] Gesendet: Freitag, 11. September 2009 15:57 An: Maven Users List Betreff: Re: How to update parent during release:prepare I certainly have the exact same problem. And using the versions plugin only helps somewhat in partially automating what I currently do manually. Last time I made the mistake of not manually changing the parent version, the release plugin, I believe, offered to update to a released version, but didn't actually change it, resulting in what was essentially a broken release (since it had a SNAPSHOT parent). Similarly I face problems with the release plugin not handling SNAPSHOT versions of dependencies declared outside the dependencies section (typically using the maven-dependency plugin instead). I would like to see the release plugin updated to handle these rather than work around them with the versions plugin. -Stephen On Fri, Sep 11, 2009 at 9:51 AM, Lewis, Eric eric.le...@ipi.ch wrote: Thanks, that works well! However, I'm still wondering whether I'm the only one releasing that way. It seems to me that the release plugin can only be used together with the versions plugin. I think that most developers have some sort of company-wide parent POM which they refer to, and when releasing, they probably all have the same problem as I do. Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to update parent during release:prepare
Hi I'm trying to use release:prepare for a project with several modules. The project has a parent which is a SNAPSHOT. Now my question is: How can I tell release:prepare to update the project's parent version to the parent's released version? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release project and modules, which plugins?
Hi I'm not quite sure with what kind of combination of plugins (release, versions, reactor, ?) and commands I would be able to do the following as described below. Any help is appreciated! I have a project with different modules. Now I want to release the whole project. The project has a SNAPSHOT version, and every module can have its own independent SNAPSHOT version, but of course depends on the project's SNAPSHOT as parent. Every module should be released separately, which means I need it as an artifact with the released version in the repo and I also need a corresponding tag and branch in the SCM. Then it needs to be updated to the next SNAPSHOT of choice (incrementing major or minor or bugfix). The modules partially depend on each other, so I need to release them in the correct sequence (which normally would be done by the Maven Reactor), otherwise the release dependency isn't found in the repo. However, they also need to depend on the released parent - but how can I release it without the modules? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Compiler plugin: Ignore warnings for tests - how?
Hi Sorry if this has been answered before, but I didn't find anything on the mailing list. I've configured the Compiler Plugin in general, setting showWarningstrue/showWarnings. However, for the tests, I would like to set it to showWarningsfalse/showWarnings. How can I do that? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Force versions plugin to remove snapshots
Sorry, I wasn't precise enough. I mean to do this *only* with the dependencies in that POM, not with the version of the POM's project. Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Freitag, 28. August 2009 18:16 An: Maven Users List Betreff: Re: Force versions plugin to remove snapshots versions:set -DnewVersion=7.8.9 2009/8/28 Lewis, Eric eric.le...@ipi.ch Hi With our build, we have a top-down approach to our releases: We have a hierarchy of POMs, and the one closest to the project contains all versions of all our projects. Now, to release that, we have to remove the -SNAPSHOT from the versions. I wanted to do this with the versions plugin, but it insists on finding the releases in the repository. Is there any other way I could achieve that? Best regards, Eric - 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
AW: Re: Force versions plugin to remove snapshots
The whole point is to only remove -SNAPSHOT from dependencies _which have actually been released_ Yes, I know. However, our release build is a bit different, because we have all the internal versions in one POM, and the build masters should release that before the actual projects are released. It forces the developers to use the released projects. If we remove -SNAPSHOT from dependencies which have not been released then we'd break your build. This is true... so you would suggest that for instance project A is released, then the parent POM is adapted using versions:use-releases for project A; then project B is released, and the same happens again? In that case (as I was already thinking), the parent POM has to be replaced in the repo every time a project is released. Which is kind of a hack, but I don't see any other way... I wonder what the Maven way is for that. And versions:set is more magic than you think if you have the following structure /pom.xml foo/pom.xml bar/pom.xml manchu/pom.xml foo-manchu/pom.xml and foo-manchu depends on bar if you change directory into /foo/bar and run mvn versions:set -DnewVersion=2.0 then versions plugin will (by default or via a property, I forget) dance up the directory tree for as long as there are aggregator pom's until it reaches the top of the tree... then it will dance down looking for all projects that depend on bar:oldVersion and update them to the newVersion. This is a great feature, but we can't use it for two reasons: - As I mentioned, we have a parent POM with all our versions, and no project ever uses versions in its POM. - We build project by project (using Hudson), we don't have a full reactor build. -Stephen 2009/8/31 Lewis, Eric eric.le...@ipi.ch Sorry, I wasn't precise enough. I mean to do this *only* with the dependencies in that POM, not with the version of the POM's project. Best regards, Eric -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Freitag, 28. August 2009 18:16 An: Maven Users List Betreff: Re: Force versions plugin to remove snapshots versions:set -DnewVersion=7.8.9 2009/8/28 Lewis, Eric eric.le...@ipi.ch Hi With our build, we have a top-down approach to our releases: We have a hierarchy of POMs, and the one closest to the project contains all versions of all our projects. Now, to release that, we have to remove the -SNAPSHOT from the versions. I wanted to do this with the versions plugin, but it insists on finding the releases in the repository. Is there any other way I could achieve that? Best regards, Eric - 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
AW: dependency scope with parent module?
Hi James I think it would be easier if you include the POMs (at least the relevant parts). Best regards, Eric -Ursprüngliche Nachricht- Von: James Russo [mailto:j...@halo3.net] Gesendet: Montag, 31. August 2009 13:29 An: Maven Users List Betreff: Re: dependency scope with parent module? Can anyone help me out this this? -jr James Russo wrote: Hello, I have a parent module, and 3 sub? modules. project-common project-server project-weblogic I have parent setup in all of them, but for some reason when I can't get project-weblogic to compile if I scope set to test, and I can't get it to test if I set scope to compile? I had thought that setting it to test, would require it for both test and compile. The only solution I could come up with is to put dependency in there twice, once with scope test and once with scope compile? Am I missing something? -jr - 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
AW: Re: Re: Force versions plugin to remove snapshots
Well I'm hoping to refactor v-m-p real soon now to split out the version checking stuff as an api .jar which would allow writing an m-enforcer-p rule to allow you to force projects to only release with the latest version of internal dependencies Great, I'm looking forward to that! If we remove -SNAPSHOT from dependencies which have not been released then we'd break your build. This is true... so you would suggest that for instance project A is released, then the parent POM is adapted using versions:use-releases for project A; then project B is released, and the same happens again? In that case (as I was already thinking), the parent POM has to be replaced in the repo every time a project is released. Which is kind of a hack, but I don't see any other way... I wonder what the Maven way is for that. I would suggest in such a case not to use a parent pom to force versions, or else to release everything in one go from the parent pom... or else accept that the parent pom (which is really an integration pom) will get a lot of churn. The Maven Way as I see it is to let projects define their dependencies. with the versions-m-p you now have reports to tell you when the project is not using the latest versions... and not using the latest version of something is not a crime... it might be more stable for example the latest version of Hudson is not always the most stable (though the new weekly release cycle is improving that) Well, for external dependencies you may not want the latest, greatest, but for internal projects you definitely want your projects to depend on the latest version. Unless you want to support several versions in parallel, which most developers don't want to :-) Anyway, thanks for your insights! Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: Executing Dependency pom.xml
In that case you can just write a parent POM which contains both projects as module, and Maven will figure out how to build them. Best regards, Eric -Ursprüngliche Nachricht- Von: bandrm [mailto:rajivband...@gmail.com] Gesendet: Donnerstag, 27. August 2009 18:52 An: users@maven.apache.org Betreff: Re: AW: Executing Dependency pom.xml Yes, project B does contain Java classes, it is packagingjar/packaging. Thanks Lewis, Eric-2 wrote: Hi I think your message is a bit confusing. Is project B a JAR type (does the project contain Java classes?) or just a POM type (contains only a pom.xml)? Best regards, Eric -Ursprüngliche Nachricht- Von: bandrm [mailto:rajivband...@gmail.com] Gesendet: Donnerstag, 27. August 2009 01:02 An: users@maven.apache.org Betreff: Executing Dependency pom.xml Hello, I guess this is very elementary question, here it is. I have two projects, Project A (war type) and Project B (jar type). Project A is dependent on Project B. So, in Project A's pom.xml I mention Project B as dependent. Now, Project B has just pom.xml and has no jar file generated. How could I run Project B's pom.xml from Project A's pom.xml, so that Project B's jar file is generated and is available for Project A? Thanks -- View this message in context: http://www.nabble.com/Executing-Dependency-pom.xml-tp25163099p 25163099.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Executing-Dependency-pom.xml-tp25163099p 25174675.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Force versions plugin to remove snapshots
Hi With our build, we have a top-down approach to our releases: We have a hierarchy of POMs, and the one closest to the project contains all versions of all our projects. Now, to release that, we have to remove the -SNAPSHOT from the versions. I wanted to do this with the versions plugin, but it insists on finding the releases in the repository. Is there any other way I could achieve that? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Executing Dependency pom.xml
Hi I think your message is a bit confusing. Is project B a JAR type (does the project contain Java classes?) or just a POM type (contains only a pom.xml)? Best regards, Eric -Ursprüngliche Nachricht- Von: bandrm [mailto:rajivband...@gmail.com] Gesendet: Donnerstag, 27. August 2009 01:02 An: users@maven.apache.org Betreff: Executing Dependency pom.xml Hello, I guess this is very elementary question, here it is. I have two projects, Project A (war type) and Project B (jar type). Project A is dependent on Project B. So, in Project A's pom.xml I mention Project B as dependent. Now, Project B has just pom.xml and has no jar file generated. How could I run Project B's pom.xml from Project A's pom.xml, so that Project B's jar file is generated and is available for Project A? Thanks -- View this message in context: http://www.nabble.com/Executing-Dependency-pom.xml-tp25163099p 25163099.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: OSGi compatible dependencies
Hi I know just a little bit about OSGi :-) About 1) This isn't possible, since the OSGi Manifest states what packages are visible for the user of the JAR. You can't automate that, it has to be planned by the authors. On the other hand, a lot of Apache Commons projects already build OSGi compliant JARs, and still SpringSource has their own versions of them... Best regards, Eric -Ursprüngliche Nachricht- Von: Julien HENRY [mailto:henr...@yahoo.fr] Gesendet: Mittwoch, 19. August 2009 09:48 An: users@maven.apache.org Betreff: OSGi compatible dependencies Hi, Foreword: I hadly know anything about OSGi. I recently discovered that Springsource is maintaining a parallel set of common dependencies in their own repository using modified artifactId. For example: dependency groupIdorg.junit/groupId artifactIdcom.springsource.org.junit/artifactId version4.5.0/version scopetest/scope /dependency As I said I'm not using OSGi but I was testing the Roo tool. To make it short Roo generate a Maven2 application and the pom.xml was full of this kind of dependencies. It was very annoying to me because even if I had all these dependencies already in my local repository, I had to download them again. After asking the reason of duplicating artifacts, someone explained to me [1] that these artifact are slighly modified to be OSGi compliant (AFAIK it means adding some standard properties in the manifest, correct me if I am wrong). Again I'm not an OSGi aware developer, but I'm very concerned by avoiding duplicate artifacts. Duplicating artifact will lead to confusion for developpers, it will increase size of both local and managed repositories, Sometimes there are good reason to duplicate, but for me this is not a good reason because AFAIK an OSGi compliant JAR can work in a regular application. I'm not blaming Spring guys for what they did, as this was certainly the only quick way to have it working with full control. But IMHO it would be better to think of a standard way to provide OSGi compliant JARs, especially because I heard Maven 3 will address this area. Some proposal : 1) Make all future JAR uploaded to Central OSGi compliant (is it possible to automatically enhance the MANIFEST?) = simplest/transparent solution for end users 2) OSGi compliant JARs use a separate classifier (we can have the regular junit-XX.jar and junit-XX-osgi.jar) = this solution can be used for all existing artifacts that can't be modified on central. What do you think? Regards, Julien [1] http://forum.springsource.org/showthread.php?p=255777 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: OSGi compatible dependencies
Yes, but in an OSGi environment it makes it pretty much useless, I think. Having every package public would be the quick'n'dirty solution, but IMHO the better solution would be the real separation of API and Implementation in the JAR by the authors. Of course, this takes time and effort... Best regards, Eric -Ursprüngliche Nachricht- Von: Barrie Treloar [mailto:baerr...@gmail.com] Gesendet: Mittwoch, 19. August 2009 10:15 An: Maven Users List Betreff: Re: OSGi compatible dependencies On Wed, Aug 19, 2009 at 5:32 PM, Lewis, Ericeric.le...@ipi.ch wrote: Hi I know just a little bit about OSGi :-) About 1) This isn't possible, since the OSGi Manifest states what packages are visible for the user of the JAR. You can't automate that, it has to be planned by the authors. I think I've posted about this before but not really given it enough thought. I still can't see why if it is not OSGi compliant that the default position it to make the entire jar packages visible. Since that's what is happening in an non-OSGi environment anyway. - 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
AW: Enforcer plugin wildcards
Ok, I've created http://jira.codehaus.org/browse/MENFORCER-83 I'll see if I can find time for the patch :-) Is there any how-to for someone who's never submitted anything to Maven? (I've written some plugins for our build, though) Best regards, Eric -Ursprüngliche Nachricht- Von: Brian Fox [mailto:bri...@infinity.nu] Gesendet: Mittwoch, 19. August 2009 01:00 An: Maven Users List Betreff: Re: Enforcer plugin wildcards On Tue, Aug 18, 2009 at 4:12 AM, Lewis, Ericeric.le...@ipi.ch wrote: Hi I've started using the Enforcer plugin, with the Banned Dependencies. It's very useful, but it's also a drag having to explicitly list all artifacts one by one. Which brings me to my question: Is it possible to have more flexible wildcards? Right now, they replace a section in an all-or-nothing way. For our purposes, a regex would be the ideal solution, since our modules have standard prefixes and suffixes. For instance, we have project xyz with modules xyz-api and xyz-impl. So if I ban all our modules and just want to allow all APIs, it's not possible to use something like my.group.id:*-api as include. Are there any plans for this? Not unless Should I write an enhancement request? Yes. And a patch would be great ;-) Best regards, Eric - 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
Enforcer plugin wildcards
Hi I've started using the Enforcer plugin, with the Banned Dependencies. It's very useful, but it's also a drag having to explicitly list all artifacts one by one. Which brings me to my question: Is it possible to have more flexible wildcards? Right now, they replace a section in an all-or-nothing way. For our purposes, a regex would be the ideal solution, since our modules have standard prefixes and suffixes. For instance, we have project xyz with modules xyz-api and xyz-impl. So if I ban all our modules and just want to allow all APIs, it's not possible to use something like my.group.id:*-api as include. Are there any plans for this? Should I write an enhancement request? Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Building multiple projects without creating a single output file?
Hi Yes, normally you would do this by defining a project and several modules. Best regards, Eric -Ursprüngliche Nachricht- Von: Jan Wedel [mailto:jan.we...@ettex.de] Gesendet: Montag, 17. August 2009 09:30 An: users@maven.apache.org Betreff: Building multiple projects without creating a single output file? Hi, one of Maven's primary aims was to have one output file for one project (as far as I can remember). The question is, can I have some kind of parent pom that invokes multiple sub pom and respectively their projects to be build? E.g my project has a web application, a client applet, a PHP application and whatever. All of them belong to one project. Is it possible to trigger all project to be build without the need to package all into a jar file which would not make much sense? Thanks, Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Centralized build configuration: Improvements in 2.2?
Hi We have a standard build, but some modules need special build steps, like JAXB or OSGi stuff etc. In order to stick to DRY (Don't Repeat Yourself), we defined profiles in the parent POM which add the required plugins to the build. So for instance, to build something with JAXB, we call 'mvn clean package -Pjaxb' As nice as this is, it totally breaks as soon as we try to build the whole project with the Maven Reactor. It's not possible just to specify 'mvn clean package' for the top-level POM and to expect the profiles to be called magically. We've tried many things, but with 2.0.9 there wasn't any satisfying solution. Now, before I go into every POM and add build steps by copy paste: Has this situation become better with Maven 2.2? For instance: - Can I import XML fragments into a POM? - Can I activate profiles by some other means? I remember profile properties file, but I think that didn't work. - Any other or better ideas? Thanks best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Surefire plugin misses class NestedCheckedException
Anyone? :-)
Still having the error...
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Donnerstag, 6. August 2009 14:34
An: Maven Users List
Betreff: AW: Surefire plugin misses class NestedCheckedException
As you can see, this was my local build. On our CI build
system (Linux), I get
[INFO]
--
--
[ERROR] BUILD ERROR
[INFO]
--
--
[INFO] Error to resolving surefire provider dependency:
Unable to get dependency information: Unable to parse the
Maven built-in model: Resolving expression:
'${project.version}': Detected the following recursive
expression cycle: [] for project org.apache.maven:super-pom
org.apache.maven.surefire:surefire-booter:jar:2.4.3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
Path to dependency:
1) dummy:dummy:jar:1.0
Dummy???
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Donnerstag, 6. August 2009 14:23
An: Maven Users List
Betreff: Surefire plugin misses class NestedCheckedException
Hi
I'm having a strange phenomenon with the Surefire plugin.
It's failing in one specific project of mine, but runs
without problem in others.
It also failed only in Maven 2.2.0 - I tried the same version
(2.4.3) in Maven 2.0.9, and it worked without problem.
I found a couple of previous mails concerning this error on
the mailing list, but they're all old.
What I'm getting is listed below.
Can someone tell me how to proceed?
Thanks best regards,
Eric
...
[WARNING] POM for
'org.apache.maven.surefire:surefire-booter:pom:2.4.3:runtime'
is invalid.
Its dependencies (if any) will NOT be available to the
current build.
[WARNING] POM for
'org.codehaus.plexus:plexus-utils:pom:1.5.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the
current build.
[WARNING] POM for
'org.apache.maven:maven-toolchain:pom:1.0:runtime' is invalid.
Its dependencies (if any) will NOT be available to the
current build.
-
this realm =
app0.child-container[org.apache.maven.plugins:maven-surefire-p
lugin:2.4.3]
urls[0] = file:/C:/Documents and
Settings/lewis_lee/.m2/repository/org/apache/maven/plugins/mav
en-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.jar
urls[1] = file:/C:/Documents and
Settings/lewis_lee/.m2/repository/org/apache/maven/surefire/su
refire-booter/2.4.3/surefire-booter-2.4.3.jar
urls[2] = file:/C:/Documents and
Settings/lewis_lee/.m2/repository/org/codehaus/plexus/plexus-u
tils/1.5.1/plexus-utils-1.5.1.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
this realm = plexus.core
urls[0] = file:/c:/Programme/Maven/lib/maven-2.2.0-uber.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO]
--
--
[ERROR] BUILD ERROR
[INFO]
--
--
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test':
Unable to load the mojo
'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test'
in the plugin
'org.apache.maven.plugins:maven-surefire-plugin'. A required
class is missing:
org/apache/maven/surefire/util/NestedCheckedException
org.apache.maven.surefire.util.NestedCheckedException
[INFO]
--
--
[INFO] For more information, run Maven with the -e switch
[INFO]
--
--
[INFO] Total time: 7 seconds
[INFO] Finished
Surefire plugin misses class NestedCheckedException
Hi I'm having a strange phenomenon with the Surefire plugin. It's failing in one specific project of mine, but runs without problem in others. It also failed only in Maven 2.2.0 - I tried the same version (2.4.3) in Maven 2.0.9, and it worked without problem. I found a couple of previous mails concerning this error on the mailing list, but they're all old. What I'm getting is listed below. Can someone tell me how to proceed? Thanks best regards, Eric ... [WARNING] POM for 'org.apache.maven.surefire:surefire-booter:pom:2.4.3:runtime' is invalid. Its dependencies (if any) will NOT be available to the current build. [WARNING] POM for 'org.codehaus.plexus:plexus-utils:pom:1.5.1:runtime' is invalid. Its dependencies (if any) will NOT be available to the current build. [WARNING] POM for 'org.apache.maven:maven-toolchain:pom:1.0:runtime' is invalid. Its dependencies (if any) will NOT be available to the current build. - this realm = app0.child-container[org.apache.maven.plugins:maven-surefire-plugin:2.4.3] urls[0] = file:/C:/Documents and Settings/lewis_lee/.m2/repository/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.jar urls[1] = file:/C:/Documents and Settings/lewis_lee/.m2/repository/org/apache/maven/surefire/surefire-booter/2.4.3/surefire-booter-2.4.3.jar urls[2] = file:/C:/Documents and Settings/lewis_lee/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar Number of imports: 10 import: org.codehaus.classworlds.en...@a6c57a42 import: org.codehaus.classworlds.en...@12f43f3b import: org.codehaus.classworlds.en...@20025374 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@92758522 import: org.codehaus.classworlds.en...@ebf2705b import: org.codehaus.classworlds.en...@bb25e54 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 this realm = plexus.core urls[0] = file:/c:/Programme/Maven/lib/maven-2.2.0-uber.jar Number of imports: 10 import: org.codehaus.classworlds.en...@a6c57a42 import: org.codehaus.classworlds.en...@12f43f3b import: org.codehaus.classworlds.en...@20025374 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@92758522 import: org.codehaus.classworlds.en...@ebf2705b import: org.codehaus.classworlds.en...@bb25e54 import: org.codehaus.classworlds.en...@bece5185 import: org.codehaus.classworlds.en...@3fee8e37 import: org.codehaus.classworlds.en...@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test': Unable to load the mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test' in the plugin 'org.apache.maven.plugins:maven-surefire-plugin'. A required class is missing: org/apache/maven/surefire/util/NestedCheckedException org.apache.maven.surefire.util.NestedCheckedException [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Thu Aug 06 14:11:44 CEST 2009 [INFO] Final Memory: 17M/32M with -e switch [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test': Unable to load the mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test' in the plugin 'org.apache.maven.plugins:maven-surefire-plugin'. A required class is missing: org/apache/maven/surefire/util/NestedCheckedException org.apache.maven.surefire.util.NestedCheckedException [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test': Unable to load the mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test' in the plugin 'org.apache.maven.plugins:maven-surefire-plugin'. A required class is missing: org/apache/maven/surefire/util/NestedCheckedException at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:682) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at
AW: Surefire plugin misses class NestedCheckedException
As you can see, this was my local build. On our CI build system (Linux), I get
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error to resolving surefire provider dependency: Unable to get
dependency information: Unable to parse the Maven built-in model: Resolving
expression: '${project.version}': Detected the following recursive expression
cycle: [] for project org.apache.maven:super-pom
org.apache.maven.surefire:surefire-booter:jar:2.4.3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
Path to dependency:
1) dummy:dummy:jar:1.0
Dummy???
Best regards,
Eric
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Donnerstag, 6. August 2009 14:23
An: Maven Users List
Betreff: Surefire plugin misses class NestedCheckedException
Hi
I'm having a strange phenomenon with the Surefire plugin.
It's failing in one specific project of mine, but runs
without problem in others.
It also failed only in Maven 2.2.0 - I tried the same version
(2.4.3) in Maven 2.0.9, and it worked without problem.
I found a couple of previous mails concerning this error on
the mailing list, but they're all old.
What I'm getting is listed below.
Can someone tell me how to proceed?
Thanks best regards,
Eric
...
[WARNING] POM for
'org.apache.maven.surefire:surefire-booter:pom:2.4.3:runtime'
is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for
'org.codehaus.plexus:plexus-utils:pom:1.5.1:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
[WARNING] POM for
'org.apache.maven:maven-toolchain:pom:1.0:runtime' is invalid.
Its dependencies (if any) will NOT be available to the current build.
-
this realm =
app0.child-container[org.apache.maven.plugins:maven-surefire-p
lugin:2.4.3]
urls[0] = file:/C:/Documents and
Settings/lewis_lee/.m2/repository/org/apache/maven/plugins/mav
en-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.jar
urls[1] = file:/C:/Documents and
Settings/lewis_lee/.m2/repository/org/apache/maven/surefire/su
refire-booter/2.4.3/surefire-booter-2.4.3.jar
urls[2] = file:/C:/Documents and
Settings/lewis_lee/.m2/repository/org/codehaus/plexus/plexus-u
tils/1.5.1/plexus-utils-1.5.1.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
this realm = plexus.core
urls[0] = file:/c:/Programme/Maven/lib/maven-2.2.0-uber.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO]
--
--
[ERROR] BUILD ERROR
[INFO]
--
--
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test':
Unable to load the mojo
'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test'
in the plugin
'org.apache.maven.plugins:maven-surefire-plugin'. A required
class is missing:
org/apache/maven/surefire/util/NestedCheckedException
org.apache.maven.surefire.util.NestedCheckedException
[INFO]
--
--
[INFO] For more information, run Maven with the -e switch
[INFO]
--
--
[INFO] Total time: 7 seconds
[INFO] Finished at: Thu Aug 06 14:11:44 CEST 2009
[INFO] Final Memory: 17M/32M
with -e switch
[INFO]
--
--
[ERROR] BUILD ERROR
[INFO]
--
--
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test
Cross-project dependencies
Hi I have a problem, which might be solved using Maven's make-like reactor mode - but I'm not sure if it is! Consider the following projects/modules Project A +--- Module A1 +--- Module A2 Project B +--- Module B1 +--- Module B2 Now, if A1 depends on B1, but B2 depends on A2, it's impossible to build a refactoring done in the two projects. Let's say I changed something in A1 and B2, then neither Project A nor Project B will build, since they're caught in a kind of deadlock. I will have to build and deploy some modules by hand until the whole build works (talking of snapshots here, of course). Can the make-like reactor mode help me? As you can tell, I'm a bit confused ;-) Thanks for any hints! Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Load and run artifact from shell script
Hi I have a utility project whose classes should be called from a shell script. The problem is how to access it: It's in the local repo, so I would like to do the following: - Download it and its runtime dependencies based on group and artifact ID, using the latest version - Create a classpath to use in the shell script As far as I can see, the dependency:build-classpath would do part of it (not downloading, though), but it only works with a POM. I need to do this anywhere in the file system. Any hints how I could start? Thanks best regards Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Load and run artifact from shell script
Hi No, apparently dependency:build-classpath needs to have a POM to work - or perhaps I'm doing something wrong. Anyway, I just tried the appassembler plugin, and it works well for what I need, namely having a script call my JAR. Best regards, Eric Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Freitag, 31. Juli 2009 16:28 An: Maven Users List Betreff: Re: Load and run artifact from shell script Hello, What do you mean anywhere in system? It works fine as mvn dependency:build-classpath and could be invoked as command. You can invoke that action in script, parse output and use result classpath in script. [cid:32B@goomoji.gmail] To download all dependencies you could use dependency:go-offline. [cid:32B@goomoji.gmail] 2009/7/31 Lewis, Eric eric.le...@ipi.chmailto:eric.le...@ipi.ch Hi I have a utility project whose classes should be called from a shell script. The problem is how to access it: It's in the local repo, so I would like to do the following: - Download it and its runtime dependencies based on group and artifact ID, using the latest version - Create a classpath to use in the shell script As far as I can see, the dependency:build-classpath would do part of it (not downloading, though), but it only works with a POM. I need to do this anywhere in the file system. Any hints how I could start? Thanks best regards Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.orgmailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.orgmailto:users-h...@maven.apache.org -- Alexander
AW: Artifact Version Checker Plugin - where is it?
On the other hand, you might want to look at Nexus as your Maven repository. It gives you plenty of RSS feeds concerning artefacts. Best regards, Eric -Ursprüngliche Nachricht- Von: Andrew Close [mailto:acl...@gmail.com] Gesendet: Dienstag, 28. Juli 2009 18:40 An: Maven Users List Betreff: Artifact Version Checker Plugin - where is it? I know I've seen this mentioned either somewhere in the plugins listed on the maven site or on the mailing list, but can't seem to find it now that I need it. :) I'm looking for 'something' that will notify me during a build that a more recent version of an artifact/dependency is available in the repository for use. Thanks for any help. -- Andrew Close - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to read POMs from Java
Hi Is there a way to read a POM from a Java class without having to write a Maven plugin? I've written some plugins, but this should run outside the Maven ecosystem :-) If there is, it would most likely be some helper class which I could load and use. Best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: copy\move plugin
I do my copying with the resource plugin, which works nicely. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 08:32 An: Maven Users List Betreff: Re: copy\move plugin Hello, I knew about that plugin, but thanks anyway. With that plugin I could emulate so many maven plugins, you know.. But I'm trying to move to maven from ant and wondering if I could use some maven kung-fu. 2009/7/23 Dan Tran dant...@gmail.com maven-antrun-plugin? On Wed, Jul 22, 2009 at 11:24 PM, Alexanderthe.malk...@gmail.com wrote: Hello all, Does maven have any plugin that provides simple task as copy\move files? Sure, I could invoke ant task but really want to do all in *maven style. *I need to juggle with files a little. * * - 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
AW: copy\move plugin
No, by specifying outputDirectory, you can copy anywhere you like. See http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html Just make sure your files aren't filtered, for instance configuration outputDirectorymy_output/outputDirectory resources resource directorymy_input/directory filteringfalse/filtering /resource /resources /configuration It's really flexible, read the examples, for instance 'Including and excluding files and directories'. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 09:48 An: Maven Users List Betreff: Re: copy\move plugin Hello, You copy files to output (target) directory or to any other? I thought resource plugin helps with copying files from somewhere to output (target) only directory. 2009/7/23 Lewis, Eric eric.le...@ipi.ch I do my copying with the resource plugin, which works nicely. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 08:32 An: Maven Users List Betreff: Re: copy\move plugin Hello, I knew about that plugin, but thanks anyway. With that plugin I could emulate so many maven plugins, you know.. But I'm trying to move to maven from ant and wondering if I could use some maven kung-fu. 2009/7/23 Dan Tran dant...@gmail.com maven-antrun-plugin? On Wed, Jul 22, 2009 at 11:24 PM, Alexanderthe.malk...@gmail.com wrote: Hello all, Does maven have any plugin that provides simple task as copy\move files? Sure, I could invoke ant task but really want to do all in *maven style. *I need to juggle with files a little. * * - 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
AW: copy\move plugin
Well, you could always repeat the configuration and specify different output directories. Not very elegant, though... :-) Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 11:03 An: Maven Users List Betreff: Re: copy\move plugin Hello, It seems like it is impossible to copy one file to several different locations not under target directory. Sure, I can copy several different files to one directory but not otherwise. 2009/7/23 Lewis, Eric eric.le...@ipi.ch No, by specifying outputDirectory, you can copy anywhere you like. See http://maven.apache.org/plugins/maven-resources-plugin/copy-re sources-mojo.html Just make sure your files aren't filtered, for instance configuration outputDirectorymy_output/outputDirectory resources resource directorymy_input/directory filteringfalse/filtering /resource /resources /configuration It's really flexible, read the examples, for instance 'Including and excluding files and directories'. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 09:48 An: Maven Users List Betreff: Re: copy\move plugin Hello, You copy files to output (target) directory or to any other? I thought resource plugin helps with copying files from somewhere to output (target) only directory. 2009/7/23 Lewis, Eric eric.le...@ipi.ch I do my copying with the resource plugin, which works nicely. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 08:32 An: Maven Users List Betreff: Re: copy\move plugin Hello, I knew about that plugin, but thanks anyway. With that plugin I could emulate so many maven plugins, you know.. But I'm trying to move to maven from ant and wondering if I could use some maven kung-fu. 2009/7/23 Dan Tran dant...@gmail.com maven-antrun-plugin? On Wed, Jul 22, 2009 at 11:24 PM, Alexanderthe.malk...@gmail.com wrote: Hello all, Does maven have any plugin that provides simple task as copy\move files? Sure, I could invoke ant task but really want to do all in *maven style. *I need to juggle with files a little. * * - 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
AW: copy\move plugin
You may also want to take a look at the assembly plugin. http://maven.apache.org/plugins/maven-assembly-plugin/ And be sure to read http://www.sonatype.com/books/maven-book/reference/assemblies.html It may be a bit of an overkill for your application, but you can definitely do anything you like with it. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 11:37 An: Maven Users List Betreff: Re: copy\move plugin Nope, client looks exactly like server. They have no code difference. Only some configuration files. 2009/7/23 Alexander Vaysberg w...@vaisberg.de The simply was create 2 project client and server. You can it make with multi-project. In this case you have a separetly you client and server application. Alexander schrieb: Hello, I must distribute different set of resource files\ bat files\ images at server and client application. For server I have to copy bat files to register in servers, properties with db configuration and so on. But client don't need them - it only connects to server. I want to type mvn package and after moment see two distrinct folders for server and client use. 2009/7/23 Alexander Vaysberg w...@vaisberg.de The Maven is not same as Ant. The first question is why you need the same file on different places? If you try make a project for alls, that the maven, isn't for you. Alexander schrieb: Hello, It seems like it is impossible to copy one file to several different locations not under target directory. Sure, I can copy several different files to one directory but not otherwise. 2009/7/23 Lewis, Eric eric.le...@ipi.ch No, by specifying outputDirectory, you can copy anywhere you like. See http://maven.apache.org/plugins/maven-resources-plugin/copy-re sources-mojo.html Just make sure your files aren't filtered, for instance configuration outputDirectorymy_output/outputDirectory resources resource directorymy_input/directory filteringfalse/filtering /resource /resources /configuration It's really flexible, read the examples, for instance 'Including and excluding files and directories'. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 09:48 An: Maven Users List Betreff: Re: copy\move plugin Hello, You copy files to output (target) directory or to any other? I thought resource plugin helps with copying files from somewhere to output (target) only directory. 2009/7/23 Lewis, Eric eric.le...@ipi.ch I do my copying with the resource plugin, which works nicely. Best regards, Eric -Ursprüngliche Nachricht- Von: Alexander [mailto:the.malk...@gmail.com] Gesendet: Donnerstag, 23. Juli 2009 08:32 An: Maven Users List Betreff: Re: copy\move plugin Hello, I knew about that plugin, but thanks anyway. With that plugin I could emulate so many maven plugins, you know.. But I'm trying to move to maven from ant and wondering if I could use some maven kung-fu. 2009/7/23 Dan Tran dant...@gmail.com maven-antrun-plugin? On Wed, Jul 22, 2009 at 11:24 PM, Alexanderthe.malk...@gmail.com wrote: Hello all, Does maven have any plugin that provides simple task as copy\move files? Sure, I could invoke ant task but really want to do all in *maven style. *I need to juggle with files a little. * * - 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 - 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
AW: General purpose source generation plugin?
Anyone? :-) -Ursprüngliche Nachricht- Von: Lewis, Eric [mailto:eric.le...@ipi.ch] Gesendet: Donnerstag, 9. Juli 2009 10:51 An: Maven Users List Betreff: General purpose source generation plugin? Hi Am I missing something or is there no general purpose source generation plugin? I've written some plugins which generate files using Velocity, and that works well. However, I think that having to write a plugin every time that I want to generate a file is kind of overkill. So, do you know any plugin that does source generation? I've only found a plugin in Google code (can't find the URL right now), which hasn't had a release yet and which is totally undocumented. Best regards, Eric - 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
AW: Getting source code for existing JARs
Well, I don't know if you're using m2eclipse, but with that it's possible. Just open the Maven Dependencies, right-click on some jar and choose Maven... download sources. Best regards, Eric -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Freitag, 10. Juli 2009 00:08 An: Maven Users List Betreff: Re: Getting source code for existing JARs Hi, Not the magically way I think you're asking for, no. Not to my knowledge anyhow. What you could do, is to try to find out what artifact you have an then, if you're lucky, the source code might exist in a repository (central for instance). One way to find out what artifact you have is to use its checksum and then use a Nexus instance to try to find a match. You can find some info about this in one of Jason van Zyl's blog posts: http://www.sonatype.com/people/2009/04/mavenizing-the-appengine-sdk/ /Anders On Thu, Jul 9, 2009 at 21:55, Singhal, Pulkitpulkit.sing...@hp.com wrote: Hello, I wanted to know if maven can be used to fetch source code for existing jars on a system? Can I simply point maven to a jar on my system and expect it to do its best to fetch the source code for the correct version according to my jar from its global repository? Can I do this via an eclipse plugin? 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
