Maven plugins orchestrator
Hi all, I'm wondering if something in maven (a plugin for example) could help me to chain different plugin goals, not bounded to the default maven lifecycle. My particular example is the fact that I'd want sort of maven alias allowing to say when I launch 'mvn myAlias' I'd want to chain clean:clean, dependency:copy-dependencies and other home made plugin not bound to the default lifecycle (no need to validate, compile, package etc...). I just browsed the existing maven plugins in apache codehaus and it doesn't seem such a plugin exists. Am I completely off the standard maven behaviour ? I tried, too, to create a custom lifecycle in my home made plugin, which would call clean:clean and dependency:copy-dependencies before executing my plugin main goal .. but I didn't succeeded due to the lack of documentation about new lifecycle creation (not bound to existing default, clean and site lifecycles) :-( *(In every maven plugins I looked at, only the maven release plugin seems to create its own new lifecycle ... but I admit this plugin seems really complicated to understand !)* Would you have some pointers/advice about this problematic ? Thanks in advance. Frédéric
Re: Maven plugins orchestrator
You are completely off standard maven behaviour. easiest solution is to create two files: myAlias.sh and myAlias.bat myAlias.sh #!/bin/sh mvn clean:clean dependency:copy-dependencies ... myAlias.bat @mvn clean:clean dependency:copy-dependencies ... Either that or use ANT. Maven has a standardised lifecycle for a reason if you don't like the standardised lifecycle, either use ANT or change your preferences ;-) -Stephen On 17 May 2010 08:42, Frederic Camblor fcamb...@gmail.com wrote: Hi all, I'm wondering if something in maven (a plugin for example) could help me to chain different plugin goals, not bounded to the default maven lifecycle. My particular example is the fact that I'd want sort of maven alias allowing to say when I launch 'mvn myAlias' I'd want to chain clean:clean, dependency:copy-dependencies and other home made plugin not bound to the default lifecycle (no need to validate, compile, package etc...). I just browsed the existing maven plugins in apache codehaus and it doesn't seem such a plugin exists. Am I completely off the standard maven behaviour ? I tried, too, to create a custom lifecycle in my home made plugin, which would call clean:clean and dependency:copy-dependencies before executing my plugin main goal .. but I didn't succeeded due to the lack of documentation about new lifecycle creation (not bound to existing default, clean and site lifecycles) :-( *(In every maven plugins I looked at, only the maven release plugin seems to create its own new lifecycle ... but I admit this plugin seems really complicated to understand !)* Would you have some pointers/advice about this problematic ? Thanks in advance. Frédéric
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
Re: Maven plugins orchestrator
Hi Stephen, I agree with you, I'll surely use the script-like approach. Nevertheless, I'd like to point I don't want to reinvent the wheel with my own lifecycle. I undestand your position which is let's standardize lifecycles : this way, we'll can provide out-of-the box features and maintain homogeneity between plugins. I understand, then, the fact that you shouldn't encourage creation of new lifecycles (this is perhaps the reason why there is a big lack in the documentation about this point ?). In my specific case, there is a good reason why I don't why to plug the clean copy-dependencies my-home-made-plugin-goal on the default lifecycle : I want to execute this specific lifecycle by hand (for example, after a change in the dependency section in my pom). Plugging this on the default lifecycle implies some problems, especially when using the maven-release-plugin (ex: first step which verify if no local modifications has been made is blocking sometimes). I think maven users will always have specific needs that can't be satisfied by the default (or standards) lifecycle nor all-made-plugin. To my mind, maven users should have the possibility to create their own lifecycles if they understand the pros cons of doing so (no problems if there are lots of disclaimers like creating your own lifecycle is bad ! Maven team doesn't guarantee the good execution of this lifecycle in the next version of maven). I find too bad to say if you want to chain maven plugins, then call maven via ANT or shell scripts Frédéric On Mon, May 17, 2010 at 9:51 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: You are completely off standard maven behaviour. easiest solution is to create two files: myAlias.sh and myAlias.bat myAlias.sh #!/bin/sh mvn clean:clean dependency:copy-dependencies ... myAlias.bat @mvn clean:clean dependency:copy-dependencies ... Either that or use ANT. Maven has a standardised lifecycle for a reason if you don't like the standardised lifecycle, either use ANT or change your preferences ;-) -Stephen On 17 May 2010 08:42, Frederic Camblor fcamb...@gmail.com wrote: Hi all, I'm wondering if something in maven (a plugin for example) could help me to chain different plugin goals, not bounded to the default maven lifecycle. My particular example is the fact that I'd want sort of maven alias allowing to say when I launch 'mvn myAlias' I'd want to chain clean:clean, dependency:copy-dependencies and other home made plugin not bound to the default lifecycle (no need to validate, compile, package etc...). I just browsed the existing maven plugins in apache codehaus and it doesn't seem such a plugin exists. Am I completely off the standard maven behaviour ? I tried, too, to create a custom lifecycle in my home made plugin, which would call clean:clean and dependency:copy-dependencies before executing my plugin main goal .. but I didn't succeeded due to the lack of documentation about new lifecycle creation (not bound to existing default, clean and site lifecycles) :-( *(In every maven plugins I looked at, only the maven release plugin seems to create its own new lifecycle ... but I admit this plugin seems really complicated to understand !)* Would you have some pointers/advice about this problematic ? Thanks in advance. Frédéric
Put applet jar to WAR root
Hello all, I need to put the applet jar to my WAR root folder. Applet jar are developed in the same project, just another module. I define applet jar as module dependency, but in this case it was put in WEB-INF/lib. Is at possible to make some mapping to put this jar to root folder? And use outputFileMapping in the same time. I use maven-war-plugin. Thanks, Aleksey. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven plugins orchestrator
On 17 May 2010 10:25, Frederic Camblor fcamb...@gmail.com wrote: Hi Stephen, I agree with you, I'll surely use the script-like approach. Nevertheless, I'd like to point I don't want to reinvent the wheel with my own lifecycle. I undestand your position which is let's standardize lifecycles : this way, we'll can provide out-of-the box features and maintain homogeneity between plugins. I understand, then, the fact that you shouldn't encourage creation of new lifecycles (this is perhaps the reason why there is a big lack in the documentation about this point ?). In my specific case, there is a good reason why I don't why to plug the clean copy-dependencies my-home-made-plugin-goal on the default lifecycle : I want to execute this specific lifecycle by hand (for example, after a change in the dependency section in my pom). But your plugin bindings should ensure that your build works for a clean checkout no matter what. If you need to run something else to get your build to work, then you have not populated the standard lifecycle correctly... what it sounds like is that you are doing stuff that should be in the standard lifecycle, but you have not figured out how/where to bind it (or the plugins you are using to not provide the caching/prevent redundant operation support) you require. Plugging this on the default lifecycle implies some problems, especially when using the maven-release-plugin (ex: first step which verify if no local modifications has been made is blocking sometimes). I think maven users will always have specific needs that can't be satisfied by the default (or standards) lifecycle nor all-made-plugin. To my mind, maven users should have the possibility to create their own lifecycles if they understand the pros cons of doing so (no problems if there are lots of disclaimers like creating your own lifecycle is bad ! Maven team doesn't guarantee the good execution of this lifecycle in the next version of maven). I find too bad to say if you want to chain maven plugins, then call maven via ANT or shell scripts Frédéric On Mon, May 17, 2010 at 9:51 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: You are completely off standard maven behaviour. easiest solution is to create two files: myAlias.sh and myAlias.bat myAlias.sh #!/bin/sh mvn clean:clean dependency:copy-dependencies ... myAlias.bat @mvn clean:clean dependency:copy-dependencies ... Either that or use ANT. Maven has a standardised lifecycle for a reason if you don't like the standardised lifecycle, either use ANT or change your preferences ;-) -Stephen On 17 May 2010 08:42, Frederic Camblor fcamb...@gmail.com wrote: Hi all, I'm wondering if something in maven (a plugin for example) could help me to chain different plugin goals, not bounded to the default maven lifecycle. My particular example is the fact that I'd want sort of maven alias allowing to say when I launch 'mvn myAlias' I'd want to chain clean:clean, dependency:copy-dependencies and other home made plugin not bound to the default lifecycle (no need to validate, compile, package etc...). I just browsed the existing maven plugins in apache codehaus and it doesn't seem such a plugin exists. Am I completely off the standard maven behaviour ? I tried, too, to create a custom lifecycle in my home made plugin, which would call clean:clean and dependency:copy-dependencies before executing my plugin main goal .. but I didn't succeeded due to the lack of documentation about new lifecycle creation (not bound to existing default, clean and site lifecycles) :-( *(In every maven plugins I looked at, only the maven release plugin seems to create its own new lifecycle ... but I admit this plugin seems really complicated to understand !)* Would you have some pointers/advice about this problematic ? Thanks in advance. Frédéric
Using Maven without internet access
I think my first mail was lost, so here I go again... I am new to Maven, so if the answer is simple, I apologies. I am trying to use Maven on a network with firewall restrictions disallowing Maven access to the different remote internet repositories. Therefore I need to install a Maven remote repository within the network, and have all Maven plug-in retrieved from this server. For testing purposes, I have installed a Tomcat server on localhost, and added the artifactory.war file. After installion artifactory, I have downloaded the following plug-in http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.jar and deployed it in Artifactory. In order to get Maven to use the remote repository running in Tomcat, I have added the following snippet to my pom.xml repositories repository releases enabledfalse/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots idLPK/id nameLPK Repository/name urlhttp://localhost:8080/artifactory/url layoutdefault/layout /repository /repositories I expected this to tell Maven not to use the standard remote repositories, but use my local version. When I now execute mvn package, I get the following message: [INFO] Scanning for projects... [INFO] [INFO] Building FutoramaUtil [INFO] task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), LPK (http://localhost:8080/artifactory) for project org.apache.maven.plugins:maven-resources-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 43 seconds [INFO] Finished at: Mon May 17 11:35:46 CEST 2010 [INFO] Final Memory: 1M/15M From this I conclude that I did not succeed in telling Maven to use my central repository. Where do I tell Maven to only use the localhost repository? Best regards Kenneth Petersen
Re: Using Maven without internet access
This is described in the Nexus book: http://www.sonatype.com/books/nexus-book/reference/maven.html It should be the same with Artifactory, maybe just some other urls. /Anders On Mon, May 17, 2010 at 13:07, Kenneth Petersen k...@lpk.dk wrote: I think my first mail was lost, so here I go again... I am new to Maven, so if the answer is simple, I apologies. I am trying to use Maven on a network with firewall restrictions disallowing Maven access to the different remote internet repositories. Therefore I need to install a Maven remote repository within the network, and have all Maven plug-in retrieved from this server. For testing purposes, I have installed a Tomcat server on localhost, and added the artifactory.war file. After installion artifactory, I have downloaded the following plug-in http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.jar and deployed it in Artifactory. In order to get Maven to use the remote repository running in Tomcat, I have added the following snippet to my pom.xml repositories repository releases enabledfalse/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots idLPK/id nameLPK Repository/name urlhttp://localhost:8080/artifactory/url layoutdefault/layout /repository /repositories I expected this to tell Maven not to use the standard remote repositories, but use my local version. When I now execute mvn package, I get the following message: [INFO] Scanning for projects... [INFO] [INFO] Building FutoramaUtil [INFO] task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), LPK (http://localhost:8080/artifactory) for project org.apache.maven.plugins:maven-resources-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 43 seconds [INFO] Finished at: Mon May 17 11:35:46 CEST 2010 [INFO] Final Memory: 1M/15M From this I conclude that I did not succeed in telling Maven to use my central repository. Where do I tell Maven to only use the localhost repository? Best regards Kenneth Petersen
Using Maven without internet access
I am new to Maven, so if the answer is simple, I apologies. I am trying to use Maven on a network with firewall restrictions disallowing Maven access to the different remote internet repositories. Therefore I need to install a Maven remote repository within the network, and have all Maven plug-in retrieved from this server. For testing purposes, I have installed a Tomcat server on localhost, and added the artifactory.war file. After installion artifactory, I have downloaded the following plug-in http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.jar and deployed it in Artifactory. In order to get Maven to use the remote repository running in Tomcat, I have added the following snippet to my pom.xml repositories repository releases enabledfalse/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots idLPK/id nameLPK Repository/name urlhttp://localhost:8080/artifactory/url layoutdefault/layout /repository /repositories I expected this to tell Maven not to use the standard remote repositories, but use my local version. When I now execute mvn package, I get the following message: [INFO] Scanning for projects... [INFO] [INFO] Building FutoramaUtil [INFO] task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), LPK (http://localhost:8080/artifactory) for project org.apache.maven.plugins:maven-resources-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 43 seconds [INFO] Finished at: Mon May 17 11:35:46 CEST 2010 [INFO] Final Memory: 1M/15M From this I conclude that I did not succeed in telling Maven to use my central repository. Where do I tell Maven to only use the localhost repository? Best regards Kenneth Petersen
Re: Using Maven without internet access
Use mirror settings in settings.xml. It make you possible to redirect every maven request to you local repo. http://maven.apache.org/guides/mini/guide-mirror-settings.html hth, Aleksey 17.05.2010 15:07, Kenneth Petersen пишет: I think my first mail was lost, so here I go again... I am new to Maven, so if the answer is simple, I apologies. I am trying to use Maven on a network with firewall restrictions disallowing Maven access to the different remote internet repositories. Therefore I need to install a Maven remote repository within the network, and have all Maven plug-in retrieved from this server. For testing purposes, I have installed a Tomcat server on localhost, and added the artifactory.war file. After installion artifactory, I have downloaded the following plug-in http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.jar and deployed it in Artifactory. In order to get Maven to use the remote repository running in Tomcat, I have added the following snippet to my pom.xml repositories repository releases enabledfalse/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots idLPK/id nameLPK Repository/name urlhttp://localhost:8080/artifactory/url layoutdefault/layout /repository /repositories I expected this to tell Maven not to use the standard remote repositories, but use my local version. When I now execute mvn package, I get the following message: [INFO] Scanning for projects... [INFO] [INFO] Building FutoramaUtil [INFO] task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), LPK (http://localhost:8080/artifactory) for project org.apache.maven.plugins:maven-resources-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 43 seconds [INFO] Finished at: Mon May 17 11:35:46 CEST 2010 [INFO] Final Memory: 1M/15M From this I conclude that I did not succeed in telling Maven to use my central repository. Where do I tell Maven to only use the localhost repository? Best regards Kenneth Petersen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using Maven without internet access
Not sure if you intended to write some reply? Your mail was blank. /Anders On Mon, May 17, 2010 at 11:56, Kenneth Petersen k...@lpk.dk wrote: I am new to Maven, so if the answer is simple, I apologies. I am trying to use Maven on a network with firewall restrictions disallowing Maven access to the different remote internet repositories. Therefore I need to install a Maven remote repository within the network, and have all Maven plug-in retrieved from this server. For testing purposes, I have installed a Tomcat server on localhost, and added the artifactory.war file. After installion artifactory, I have downloaded the following plug-in http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.jar and deployed it in Artifactory. In order to get Maven to use the remote repository running in Tomcat, I have added the following snippet to my pom.xml repositories repository releases enabledfalse/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots idLPK/id nameLPK Repository/name urlhttp://localhost:8080/artifactory/url layoutdefault/layout /repository /repositories I expected this to tell Maven not to use the standard remote repositories, but use my local version. When I now execute mvn package, I get the following message: [INFO] Scanning for projects... [INFO] [INFO] Building FutoramaUtil [INFO] task-segment: [package] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-resources-plugin Reason: POM 'org.apache.maven.plugins:maven-resources-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), LPK (http://localhost:8080/artifactory) for project org.apache.maven.plugins:maven-resources-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 43 seconds [INFO] Finished at: Mon May 17 11:35:46 CEST 2010 [INFO] Final Memory: 1M/15M From this I conclude that I did not succeed in telling Maven to use my central repository. Where do I tell Maven to only use the localhost repository? Best regards Kenneth Petersen
release:prepare - EMBEDDED/bin/mvn.bat not found
I am attempting to run a release:prepare using M2Eclipse. At first I
thought my issue was a M2Eclipse issue so I posted on that list but did
not get much of a response. After looking at it a while it seems it might
be a issue with the release plugin, or at least someone familiar with the
release plugin my be able to point me in the right direction.
When I run a release:prepare I get the error Maven executable not found
at: C:\Documents and
Settings\tmcginni\rational\workspace\aes-maven-master-1.4.16-SNAPSHOT\EMBEDDED\bin\mvn.bat
.
Why is it looking for mvn.bat? Here is a snippet of the debug output.
[INFO] Building AES Maven Master 1.4.16
[INFO]
[DEBUG] === PROJECT BUILD PLAN
[DEBUG] Project: com.aes:aes-maven-master:1.4.16
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [test]
[DEBUG]
---
[DEBUG] Goal:
org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
(default-cli)
[DEBUG] Style: Aggregating
[DEBUG] Configuration: ?xml version=1.0 encoding=UTF-8?
configuration
addSchema default-value=true${addSchema}/addSchema
allowReleasePluginSnapshot
default-value=false${allowReleasePluginSnapshot}/allowReleasePluginSnapshot
allowTimestampedSnapshots
default-value=false${ignoreSnapshots}/allowTimestampedSnapshots
arguments${arguments}/arguments
autoVersionSubmodules
default-value=falsetrue/autoVersionSubmodules
basedir${basedir}/basedir
commitByProject
default-value=false${commitByProject}/commitByProject
developmentVersion${developmentVersion}/developmentVersion
dryRun default-value=false${dryRun}/dryRun
generateReleasePoms
default-value=false${generateReleasePoms}/generateReleasePoms
javaHome default-value=${java.home}/
localRepoDirectory default-value=${maven.repo.local}/
mavenExecutorId
default-value=invoker${mavenExecutorId}/mavenExecutorId
mavenHome default-value=${maven.home}/
password${password}/password
pomFileName${pomFileName}/pomFileName
preparationGoals default-value=clean
verify${preparationGoals}/preparationGoals
project${project}/project
reactorProjects${reactorProjects}/reactorProjects
releaseVersion${releaseVersion}/releaseVersion
remoteTagging default-value=true${remoteTagging}/remoteTagging
resume default-value=true${resume}/resume
scmCommentPrefix default-value=[maven-release-plugin]
${scmCommentPrefix}/scmCommentPrefix
settings${settings}/settings
tag${tag}/tag
tagBase${tagBase}/tagBase
updateDependencies
default-value=true${updateDependencies}/updateDependencies
useEditMode default-value=false${useEditMode}/useEditMode
username${username}/username
/configuration
[DEBUG]
===
[INFO]
[INFO] --- maven-release-plugin:2.0-beta-9:prepare (default-cli) @
aes-maven-master ---
[DEBUG] Created new class realm
pluginorg.apache.maven.plugins:maven-release-plugin:2.0-beta-9
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-release-plugin:2.0-beta-9
[DEBUG] Included:
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-9
[DEBUG] Included:
org.apache.maven.release:maven-release-manager:jar:2.0-beta-9
[DEBUG] Included: junit:junit:jar:3.8.1
[DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG] Included:
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-6
[DEBUG] Included: org.apache.maven.shared:maven-invoker:jar:2.0.9
[DEBUG] Included: commons-cli:commons-cli:jar:1.0
[DEBUG] Included: commons-logging:commons-logging:jar:1.0
[DEBUG] Included: commons-lang:commons-lang:jar:1.0
[DEBUG] Included:
org.apache.maven.scm:maven-scm-providers-standard:pom:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-accurev:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-api:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.2
[DEBUG] Included: regexp:regexp:jar:1.3
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-cvsexe:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-cvs-commons:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-cvsjava:jar:1.2
[DEBUG] Included: org.netbeans.lib:cvsclient:jar:20060125
[DEBUG] Included: ch.ethz.ganymed:ganymed-ssh2:jar:build210
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-gitexe:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-git-commons:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-hg:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-perforce:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-starteam:jar:1.2
[DEBUG] Included:
Re: mvn release:prepare fails with missing artifacts when project to be released runs an assembly
I'm releasing a Maven2 multi-module project. One of the modules is a POM project (assembly project) that uses the maven-assembly-plugin in order to build an assembly (zip archive). The artifacts to be assembled are specified via dependencies in the POM. They point to modules contained in the same multi-module project. When running mvn release:prepare on the multi-module project, the build of the assembly project fails with the message that the dependencies cannot be resolved. These dependencies are reported with the version that should be released, e.g. 0.0.3. Before running the goal, all dependency versions are 0.0.3-SNAPSHOT. What seems to happen is that the snapshot version 0.0.3-SNAPSHOT is replaced by 0.0.3 and then the assembly plugin is started (which is bound to the package phase). what goal did you bind with? It needs to be assembly:single Yes, it is goalsingle/goal The assembly plugin tries to resolve the dependencies based on version 0.0.3 which however do not yet exist at that point. The exist in the reactor, providing the project in which assembly is being invoked has dependencies on those artifacts so that maven knows the build order must build the dependent projects first. to test if you have this working, here is a simple test procedure: 1. mvn versions:set -DnewVersion=0.0.3-reltesting-SNAPSHOT 2. mvn clean verify 3. mvn versions:rollback 3. mvn versions:revert I executed this test procedure on the assembly project and in fact it produces the same problem as described above: the artifacts to be assembled are looked up in the repository with version 0.0.3-reltesting-SNAPSHOT and the build fails because the artifacts have not yet been installed with this version. For me it looks like a hen-and-egg problem: releasing the assembly project implies building the assembly in the release version, but the assembly in turn requires the released artifacts to be installed in the repository. Would it be possible to have the release procedure work like this: 1) Release plugin changes the version in the multi module project (that includes the assembly project and the artifacts to be assembled), i.e. to 0.0.4 2) The artifacts to be assembled are built and installed in the repository in version 0.0.4 3) The assembly is run and picks up the artifacts to be assembled from the repository in version 0.0.4 4) The assembly project is installed in the repository in version 0.0.4 Currently the install step in 2) is not happening -- this seems to be the crucial part - Markus it is essential that you only run up the lifecycle as far as verify when testing, as if you go as far as install, the artifacts will have been pushed to the local repo (and hence issues with your reactor will be missed) If you are under the clock [i.e. your manager is saying this needs to be released yesterday, why did you recommend maven, your future at this company is being questioned] then just change the preparationGoals from clean verify to clean install to get a release out the door. But the reality is that such a release can end up with mixed build artifacts, wherein the dependencies copied into your assembly where the ones built during the release:prepare, while the same artifacts copied to your remote repository were built during release:perform... so that if somebody checks say the md5 of the jar inside the assembly against the md5 of that same jar deployed to the maven repo, they will find that the checksums do not match (different timestamps)... additionally, if you use remoteTagging (which you pretty much need to) and somebody commits while release:prepare is running, then the release:perform will checkout different code and the subtle issues of bundled artifact mismatches _will_ bite you in the ass. So what I am saying is that you need to fix it so that your build works with clean verify on a virgin version number (i.e. a version number that has never been built before)... but if time pressures are forced on you, you can get a release out... just don't forget to fix the real problem -Stephen I guess it is not a problem in Maven but I'm missing practice on how to perform a successful release in this situation. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ear Plugin Version 5 issue
I go into the maven repository to \org\apache\maven\plugins\maven-ear-plugin
and delete the 2.4.1. folder then run the build again.
snicoll wrote:
And it probably doesn't. I am not sure I get your it works if I delete
the
plugin thing. Can you replace the . by ${basedir} to avoid any
reactor-related issue?
Thx,
S.
On Fri, May 14, 2010 at 6:01 PM, Wale12 chris.w...@ontario.ca wrote:
Fair point.
I am using hudson so this is all I get.
Deployment descriptor:
D:\Hudson\jobs\HCV_1.0_Dev\workspace\hud_HCV_1.0_view1\UcmVob08A\Src_Java\HCVWebService\HCVServiceEAR\target\HCVServiceEAR\META-INF\application.xml
does not exist.
C.
snicoll wrote:
uh? Why on Earth would you do this:
earSourceDirectory./earSourceDirectory
Can you post the full stacktrace. Are you running from the reactor when
it
happens?
S.
On Fri, May 14, 2010 at 4:21 PM, Wale12 chris.w...@ontario.ca wrote:
I have a weird issue with a project I have. I am using maven 2 and
version
2.4.1 of the ear plugin and am using the version 5 no application.xml
options for packing the ear.
plugin
artifactIdmaven-ear-plugin/artifactId
version2.4.1/version
configuration
version5/version
generateApplicationXmlfalse/generateApplicationXml
earSourceDirectory./earSourceDirectory
earSourceExcludespom.xml,pom.properties,.settings\,lib\,target\,.project/earSourceExcludes
finalName${project.artifactId}-${project.version}.${BUILD_NUMBER}/finalName
modules
:
/modules
archive
addMavenDescriptorfalse/addMavenDescriptor
manifestEntries
Implementation-Version${PRJVERSION}/Implementation-Version
/manifestEntries
/archive
/configuration
/plugin
On one of my projects that use these option, I have several, I am
finding
that I need to delete the plugin in the maven repository so that I get
a
fresh download of the plugin to get it to package the ear and not
complain
about not having an application xml file. Any time I already have the
plugin in the repository and build the project it fails with the
application.xml does not exist error. If I go and then delete the
plugin
again and built the project it builds fine.
This does not happen with other project that I have using the same
options?
Any idea why this would happen?
Thanks.
--
View this message in context:
http://old.nabble.com/Ear-Plugin-Version-5-issue-tp28560014p28560014.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
--
View this message in context:
http://old.nabble.com/Ear-Plugin-Version-5-issue-tp28560014p28561249.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
--
View this message in context:
http://old.nabble.com/Ear-Plugin-Version-5-issue-tp28560014p28583646.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn release:prepare fails with missing artifacts when project to be released runs an assembly
On 17 May 2010 14:13, Markus Muenkel markus.muen...@fernuni-hagen.dewrote: I'm releasing a Maven2 multi-module project. One of the modules is a POM project (assembly project) that uses the maven-assembly-plugin in order to build an assembly (zip archive). The artifacts to be assembled are specified via dependencies in the POM. They point to modules contained in the same multi-module project. When running mvn release:prepare on the multi-module project, the build of the assembly project fails with the message that the dependencies cannot be resolved. These dependencies are reported with the version that should be released, e.g. 0.0.3. Before running the goal, all dependency versions are 0.0.3-SNAPSHOT. What seems to happen is that the snapshot version 0.0.3-SNAPSHOT is replaced by 0.0.3 and then the assembly plugin is started (which is bound to the package phase). what goal did you bind with? It needs to be assembly:single Yes, it is goalsingle/goal The assembly plugin tries to resolve the dependencies based on version 0.0.3 which however do not yet exist at that point. The exist in the reactor, providing the project in which assembly is being invoked has dependencies on those artifacts so that maven knows the build order must build the dependent projects first. to test if you have this working, here is a simple test procedure: 1. mvn versions:set -DnewVersion=0.0.3-reltesting-SNAPSHOT 2. mvn clean verify 3. mvn versions:rollback 3. mvn versions:revert I executed this test procedure on the assembly project and in fact it produces the same problem as described above: the artifacts to be assembled are looked up in the repository with version 0.0.3-reltesting-SNAPSHOT and the build fails because the artifacts have not yet been installed with this version. For me it looks like a hen-and-egg problem: releasing the assembly project implies building the assembly in the release version, but the assembly in turn requires the released artifacts to be installed in the repository. Would it be possible to have the release procedure work like this: 1) Release plugin changes the version in the multi module project (that includes the assembly project and the artifacts to be assembled), i.e. to 0.0.4 2) The artifacts to be assembled are built and installed in the repository in version 0.0.4 3) The assembly is run and picks up the artifacts to be assembled from the repository in version 0.0.4 4) The assembly project is installed in the repository in version 0.0.4 Currently the install step in 2) is not happening -- this seems to be the crucial part If you bind things to the correct phases and have the correct project structure then there is no need to invoke the local repository and everything is resolved from the reactor. You just need to restructure your project. Where is the assembly created? Where is that in relation to it's dependencies? you cannot create an assembly in a project which is the xpath:/project/parent of the dependencies to be included in the assembly -Stephen - Markus it is essential that you only run up the lifecycle as far as verify when testing, as if you go as far as install, the artifacts will have been pushed to the local repo (and hence issues with your reactor will be missed) If you are under the clock [i.e. your manager is saying this needs to be released yesterday, why did you recommend maven, your future at this company is being questioned] then just change the preparationGoals from clean verify to clean install to get a release out the door. But the reality is that such a release can end up with mixed build artifacts, wherein the dependencies copied into your assembly where the ones built during the release:prepare, while the same artifacts copied to your remote repository were built during release:perform... so that if somebody checks say the md5 of the jar inside the assembly against the md5 of that same jar deployed to the maven repo, they will find that the checksums do not match (different timestamps)... additionally, if you use remoteTagging (which you pretty much need to) and somebody commits while release:prepare is running, then the release:perform will checkout different code and the subtle issues of bundled artifact mismatches _will_ bite you in the ass. So what I am saying is that you need to fix it so that your build works with clean verify on a virgin version number (i.e. a version number that has never been built before)... but if time pressures are forced on you, you can get a release out... just don't forget to fix the real problem -Stephen I guess it is not a problem in Maven but I'm missing practice on how to perform a successful release in this situation. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: New PMC Member
Congratulations Paul ! Arnaud On May 14, 2010, at 11:34 PM, Brian Fox wrote: The Maven PMC recently voted to invite Paul Gier to join us as a member of the PMC Committee. He accepted and is now officially part of the Maven PMC. Congratulations Paul! If you'd like to read more about what his exactly means, take a look at http://www.apache.org/foundation/how-it-works.html --Brian Fox Maven PMC Chair. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
About Maven3 M2Eclipse plug-in versioning problem
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2 we
could specify a variable for the application version in the parent pom, so that
in the child poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out the version tag or
swapping the expressions between projectVersion and version
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService /description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
Build checksum for assembly?
Upping a question I asked previously to a separate thread - seems like it should be simple to solve, but research is not helping. I have an assembly packaged as a tgz file, and I'm trying to deploy it to an Artifactory repository, but I get this error: [INFO] Error deploying artifact: Resource to deploy not found: File: http://xxx/artifactory/libs-snapshots-local/com/my/site/1.1-SNAPSHOT/pkg-1.1-20100516.231424-1-blankdb.tar.gz. md5 does not exist How do I tell maven to create this md5 checksum? mvn deploy -DcreateChecksum=true didn't do it... -- C. Benson Manica cbman...@gmail.com
Announcement: Atomic multi-module deploys
Hi all. I've written a plugin which allows you to do atomic multi-module builds. It's beta at the moment, but should work for simple cases. Usage is available on the home page. Bug reports enhancement requests welcome! http://code.google.com/p/maven-deferred-deploy-plugin/ http://code.google.com/p/maven-deferred-deploy-plugin/ Jake -- View this message in context: http://old.nabble.com/Announcement%3A-Atomic-multi-module-deploys-tp28585091p28585091.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: unit test not finding dependent class
I abbreviated the company name for privacy. That shouldn't be the cause. On Sun, May 16, 2010 at 2:28 PM, Ron Wheeler rwhee...@artifact-software.com wrote: com/iq/m2m/platform/tester/MergePkgsTester /com/ciq/m2m/platform/tester/MergePkgsTester.class 2 different package names ciq!=iq Ron On 16/05/2010 3:41 PM, Ted Yu wrote: The classes are not dynamically loaded. Thanks On Sunday, May 16, 2010, Kalpak Gadrekalpa...@gmail.com wrote: Just in case.. Are you dynamically loading these classes from your code? You can see these kind of errors in case you are dynamically loading classes using System class loader instead of the immediate class loader. The test runner will segregate the classes by providing a custom class loader for each test. All your classes will be added to this child class loader. So trying to load classes from System class loader will fail as the System class loader does not know about these classes. - Kalpak -rw-r--r-- 1 tyu staff 5691 May 16 08:58 target/classes/com/ciq/m2m/platform/mmp2/input/OtaUploadRecordReader.class That test passes. But the same problem appears for other tests: arvindmac:m2m-platform tyu$ vi target/surefire-reports/com.ciq.m2m.platform.mmp2.MeasureMergeReducerTest.txt java.lang.NoClassDefFoundError: com/iq/m2m/platform/tester/MergePkgsTester Although the class has been generated: ... -rw-r--r-- 1 tyu staff 5141 May 16 08:58 target/classes/com/ciq/m2m/platform/tester/MergePkgsTester.class On Sun, May 16, 2010 at 7:16 AM, Anders Hammarand...@hammar.net wrote: Is OtaUploadRecordReader a class you've written and that's in the same Maven project? If so, check that it is being compiled by checking that the .class file exists under target/classes/ If it's not being compiled there's some error you need to fix in your project. /Anders On Fri, May 14, 2010 at 19:41, Ted Yuyuzhih...@gmail.comwrote: Hi, Here is the information about maven I use: Apache Maven 2.2.0 (r788681; 2009-06-26 06:04:01-0700) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.3 arch: x86_64 Family: mac I see strange unit test failure which was due to a dependent class in the same package not being found: java.lang.NoClassDefFoundError: com/ciq/m2m/platform/mmp2/input/OtaUploadRecordReader at com.ciq.m2m.platform.mmp2.input.OtaUploadRecordReaderSingleFileTest.createRecordReader(OtaUploadRecordReaderSingleFileTest.java:18) In Eclipse, I can successfully run the same unit test. Can someone provide hint ? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Need publicly available TestNG build with working parallel tests
I'm looking into making some performance improvements with parallel running of surefire tests and I need a project with stable working parallel TestNG tests. The project must be public and have stable tests, I can add external repositories if needed. Anyone know any such project ? Kristian
Re: Build checksum for assembly?
Just as an update, it turns out that it was actually a problem with Artifactory 2.2.2 - upgrading to 2.2.3 fixed the problem. On Mon, May 17, 2010 at 10:29 AM, C. Benson Manica cbman...@gmail.comwrote: Upping a question I asked previously to a separate thread - seems like it should be simple to solve, but research is not helping. I have an assembly packaged as a tgz file, and I'm trying to deploy it to an Artifactory repository, but I get this error: [INFO] Error deploying artifact: Resource to deploy not found: File: http://xxx/artifactory/libs-snapshots-local/com/my/site/1.1-SNAPSHOT/pkg-1.1-20100516.231424-1-blankdb.tar.gz. md5 does not exist How do I tell maven to create this md5 checksum? mvn deploy -DcreateChecksum=true didn't do it... -- C. Benson Manica cbman...@gmail.com -- C. Benson Manica cbman...@gmail.com
RE: unit test not finding dependent class
Yu Anders..Kalpak and Ron are correct ..changing the package name causes this problem If you disagree.. post your code and pom.xml and settings.xml (and indicate which version of maven) so we can download and test your configuration Are you using the shaded plugin ? Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Mon, 17 May 2010 09:39:47 -0700 Subject: Re: unit test not finding dependent class From: yuzhih...@gmail.com To: users@maven.apache.org I abbreviated the company name for privacy. That shouldn't be the cause. On Sun, May 16, 2010 at 2:28 PM, Ron Wheeler rwhee...@artifact-software.com wrote: com/iq/m2m/platform/tester/MergePkgsTester /com/ciq/m2m/platform/tester/MergePkgsTester.class 2 different package names ciq!=iq Ron On 16/05/2010 3:41 PM, Ted Yu wrote: The classes are not dynamically loaded. Thanks On Sunday, May 16, 2010, Kalpak Gadrekalpa...@gmail.com wrote: Just in case.. Are you dynamically loading these classes from your code? You can see these kind of errors in case you are dynamically loading classes using System class loader instead of the immediate class loader. The test runner will segregate the classes by providing a custom class loader for each test. All your classes will be added to this child class loader. So trying to load classes from System class loader will fail as the System class loader does not know about these classes. - Kalpak -rw-r--r-- 1 tyu staff 5691 May 16 08:58 target/classes/com/ciq/m2m/platform/mmp2/input/OtaUploadRecordReader.class That test passes. But the same problem appears for other tests: arvindmac:m2m-platform tyu$ vi target/surefire-reports/com.ciq.m2m.platform.mmp2.MeasureMergeReducerTest.txt java.lang.NoClassDefFoundError: com/iq/m2m/platform/tester/MergePkgsTester Although the class has been generated: ... -rw-r--r-- 1 tyu staff 5141 May 16 08:58 target/classes/com/ciq/m2m/platform/tester/MergePkgsTester.class On Sun, May 16, 2010 at 7:16 AM, Anders Hammarand...@hammar.net wrote: Is OtaUploadRecordReader a class you've written and that's in the same Maven project? If so, check that it is being compiled by checking that the .class file exists under target/classes/ If it's not being compiled there's some error you need to fix in your project. /Anders On Fri, May 14, 2010 at 19:41, Ted Yuyuzhih...@gmail.com wrote: Hi, Here is the information about maven I use: Apache Maven 2.2.0 (r788681; 2009-06-26 06:04:01-0700) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.3 arch: x86_64 Family: mac I see strange unit test failure which was due to a dependent class in the same package not being found: java.lang.NoClassDefFoundError: com/ciq/m2m/platform/mmp2/input/OtaUploadRecordReader at com.ciq.m2m.platform.mmp2.input.OtaUploadRecordReaderSingleFileTest.createRecordReader(OtaUploadRecordReaderSingleFileTest.java:18) In Eclipse, I can successfully run the same unit test. Can someone provide hint ? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
Re: About Maven3 M2Eclipse plug-in versioning problem
Yes variable version names are not allowed as of Maven 3. I believe the
reason will be deploying into repositories, as pom with version as some
properties instead of a proper version could get deployed.
A quick fix is to configure Eclipse to use external installation of
Maven 2. But remember that variable versions will not be supported in
the future releases. I personally use version number derived out of
properties for our Continuous Integration server to generate the tick
part of version (1.0.0.[123]). I haven't personally found a solution yet
using Maven 3.
Thanks,
Kalpak
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2 we
could specify a variable for the application version in the parent pom, so that
in the child poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Apache Common Parent Pom 7 - use of maven-source-plugin - why not use the no-fork version?
When doing an apache-release , the common Apache Parent version 7 invokes: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId executions execution idattach-sources/id goals goaljar/goal !-- == ITEM OF INTEREST -- /goals /execution /executions /plugin This causes re-running of the lifecycle up to the package goal, which is inefficient, I think. Is there a reason the goal jar-no-fork isn't used instead? -Marshall Schor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Apache Common Parent Pom 7 - use of maven-source-plugin - why not use the no-fork version?
When that was written the jar goal didn't fork iirc. On Mon, May 17, 2010 at 2:37 PM, Marshall Schor m...@schor.com wrote: When doing an apache-release , the common Apache Parent version 7 invokes: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId executions execution idattach-sources/id goals goaljar/goal !-- == ITEM OF INTEREST -- /goals /execution /executions /plugin This causes re-running of the lifecycle up to the package goal, which is inefficient, I think. Is there a reason the goal jar-no-fork isn't used instead? -Marshall Schor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Apache Common Parent Pom 7 - use of maven-source-plugin - why not use the no-fork version?
ok - where do Jira's for updating the common Apache Parent go? The pom in question is missing an issueManagement element... ;-) -Marshall Schor On 5/17/2010 3:00 PM, Brian Fox wrote: When that was written the jar goal didn't fork iirc. On Mon, May 17, 2010 at 2:37 PM, Marshall Schor m...@schor.com wrote: When doing an apache-release , the common Apache Parent version 7 invokes: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId executions execution idattach-sources/id goals goaljar/goal !-- == ITEM OF INTEREST -- /goals /execution /executions /plugin This causes re-running of the lifecycle up to the package goal, which is inefficient, I think. Is there a reason the goal jar-no-fork isn't used instead? -Marshall Schor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Multi-module source release assembly, using Common Apache POM version 7 not using moduleSets?
The current common apache parent POM (version 7) [1], when you specify the apache-release profile, activates a part: plugins !-- Create a source-release artifact that contains the fully buildable project directory source structure. This is the artifact which is the official subject of any release vote. -- plugin artifactIdmaven-assembly-plugin/artifactId . . . executions execution idsource-release-assembly/id . . . configuration runOnlyAtExecutionRoottrue/runOnlyAtExecutionRoot . . . /configuration When used on a multi-module aggregate project, this only creates the source-release-assembly at the aggregate project level. It seems to me, since this artifact is the official subject of any release vote, that this source assembly should include the sources from this aggregate project, plus all of the sub-modules . (Currently it only has the the source from this aggregate project; none of the submodules are included.) I think the assembly plugin attempts to support this use case, via its moduleSets elements. Are multi-module projects in Apache supposed to override the common Apache Parent and specify the moduleSets form of assembly? Or is there another preferred way to do this? -Marshall Schor [1] http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: I have the right version, but maven can't find it
Who is asking for 1.2.13 now? I only see 1.2.15 in your poms? I am not sure why you have the [] around the version in mmm's pom.xml The [] means this version and no other. Any other version tag in Maven merely indicates a preference for a version of a plugin or dependency, which Maven will pay attention to but it may not actually use that version if it does not feel like it. Whereas with [], Maven will actually fail the build if it cannot or does not use that version specifically. If you have [1.2] for a plugin in one module and [1.3] in another and you're building from the parent, the build will (should) fail. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: unit test not finding dependent class
We don't use shaded plugin. arvindmac:m2m-platform tyu$ mvn -version Apache Maven 2.2.0 (r788681; 2009-06-26 06:04:01-0700) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.3 arch: x86_64 Family: mac On Mon, May 17, 2010 at 10:45 AM, Martin Gainty mgai...@hotmail.com wrote: Yu Anders..Kalpak and Ron are correct ..changing the package name causes this problem If you disagree.. post your code and pom.xml and settings.xml (and indicate which version of maven) so we can download and test your configuration Are you using the shaded plugin ? Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Mon, 17 May 2010 09:39:47 -0700 Subject: Re: unit test not finding dependent class From: yuzhih...@gmail.com To: users@maven.apache.org I abbreviated the company name for privacy. That shouldn't be the cause. On Sun, May 16, 2010 at 2:28 PM, Ron Wheeler rwhee...@artifact-software.com wrote: com/iq/m2m/platform/tester/MergePkgsTester /com/ciq/m2m/platform/tester/MergePkgsTester.class 2 different package names ciq!=iq Ron On 16/05/2010 3:41 PM, Ted Yu wrote: The classes are not dynamically loaded. Thanks On Sunday, May 16, 2010, Kalpak Gadrekalpa...@gmail.com wrote: Just in case.. Are you dynamically loading these classes from your code? You can see these kind of errors in case you are dynamically loading classes using System class loader instead of the immediate class loader. The test runner will segregate the classes by providing a custom class loader for each test. All your classes will be added to this child class loader. So trying to load classes from System class loader will fail as the System class loader does not know about these classes. - Kalpak -rw-r--r-- 1 tyu staff 5691 May 16 08:58 target/classes/com/ciq/m2m/platform/mmp2/input/OtaUploadRecordReader.class That test passes. But the same problem appears for other tests: arvindmac:m2m-platform tyu$ vi target/surefire-reports/com.ciq.m2m.platform.mmp2.MeasureMergeReducerTest.txt java.lang.NoClassDefFoundError: com/iq/m2m/platform/tester/MergePkgsTester Although the class has been generated: ... -rw-r--r-- 1 tyu staff 5141 May 16 08:58 target/classes/com/ciq/m2m/platform/tester/MergePkgsTester.class On Sun, May 16, 2010 at 7:16 AM, Anders Hammarand...@hammar.net wrote: Is OtaUploadRecordReader a class you've written and that's in the same Maven project? If so, check that it is being compiled by checking that the .class file exists under target/classes/ If it's not being compiled there's some error you need to fix in your project. /Anders On Fri, May 14, 2010 at 19:41, Ted Yuyuzhih...@gmail.com wrote: Hi, Here is the information about maven I use: Apache Maven 2.2.0 (r788681; 2009-06-26 06:04:01-0700) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.3 arch: x86_64 Family: mac I see strange unit test failure which was due to a dependent class in the same package not being found: java.lang.NoClassDefFoundError: com/ciq/m2m/platform/mmp2/input/OtaUploadRecordReader at com.ciq.m2m.platform.mmp2.input.OtaUploadRecordReaderSingleFileTest.createRecordReader(OtaUploadRecordReaderSingleFileTest.java:18) In Eclipse, I can successfully run the same unit test. Can someone provide hint ? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi-module source release assembly, using Common Apache POM version 7 not using moduleSets?
This descriptor assumes that all modules ate children of the execution root...or a tree. If that's not the case in your project then you would need to create a custom bundle descriptor. --Brian (mobile) On May 17, 2010, at 3:20 PM, Marshall Schor m...@schor.com wrote: The current common apache parent POM (version 7) [1], when you specify the apache-release profile, activates a part: plugins !-- Create a source-release artifact that contains the fully buildable project directory source structure. This is the artifact which is the official subject of any release vote. -- plugin artifactIdmaven-assembly-plugin/artifactId . . . executions execution idsource-release-assembly/id . . . configuration runOnlyAtExecutionRoottrue/runOnlyAtExecutionRoot . . . /configuration When used on a multi-module aggregate project, this only creates the source-release-assembly at the aggregate project level. It seems to me, since this artifact is the official subject of any release vote, that this source assembly should include the sources from this aggregate project, plus all of the sub-modules . (Currently it only has the the source from this aggregate project; none of the submodules are included.) I think the assembly plugin attempts to support this use case, via its moduleSets elements. Are multi-module projects in Apache supposed to override the common Apache Parent and specify the moduleSets form of assembly? Or is there another preferred way to do this? -Marshall Schor [1] http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom - 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: About Maven3 M2Eclipse plug-in versioning problem
So how do I use my documentation-producing plugin in its own documentation
without a variable version number?
See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xml for
an example. It's in the site profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote:
Yes variable version names are not allowed as of Maven 3. I believe the
reason will be deploying into repositories, as pom with version as some
properties instead of a proper version could get deployed.
A quick fix is to configure Eclipse to use external installation of Maven 2.
But remember that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2
we
could specify a variable for the application version in the parent pom, so
that
in the child poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
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: About Maven3 M2Eclipse plug-in versioning problem
you have to use the previously release version
On 17 May 2010 22:24, Kathryn Huxtable kath...@kathrynhuxtable.org wrote:
So how do I use my documentation-producing plugin in its own documentation
without a variable version number?
See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xmlfor
an example. It's in the site profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote:
Yes variable version names are not allowed as of Maven 3. I believe the
reason will be deploying into repositories, as pom with version as some
properties instead of a proper version could get deployed.
A quick fix is to configure Eclipse to use external installation of Maven
2. But remember that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with
maven2 we
could specify a variable for the application version in the parent pom,
so that
in the child poms we could able to specify the version by the same
variable.
That helps us saving our time for updating version number in each
project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have
been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc..
However,
the solution never comes up.. Maybe I am doing something wrong, but
could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
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: About Maven3 M2Eclipse plug-in versioning problem
MYMVN.bat:
Preprocess.exe mypom.xml pom.xml
mvn %1 %2 %3 %4 %5 %6 %7
del pom.xml
Remember what happened when they started making C compilers more restrictive?
The C preprocessor was born.
Actually, these days, the above BAT file would probably run an ant script. :-)
The harder you squeeze people into a mold, the more violent and sudden will be
the leap to the next plateau of people getting what they want.
!-- Frank Gorham-Engard →
Be kinder than necessary.
Everyone you work here with is fighting some kind of battle.
-Original Message-
From: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org]
Sent: Monday, May 17, 2010 5:24 PM
To: Maven Users List
Subject: Re: About Maven3 M2Eclipse plug-in versioning problem
So how do I use my documentation-producing plugin in its own documentation
without a variable version number?
See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xml for
an example. It's in the site profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote:
Yes variable version names are not allowed as of Maven 3. I believe the
reason will be deploying into repositories, as pom with version as some
properties instead of a proper version could get deployed.
A quick fix is to configure Eclipse to use external installation of Maven 2.
But remember that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2
we
could specify a variable for the application version in the parent pom, so
that
in the child poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
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: About Maven3 M2Eclipse plug-in versioning problem
In the words of John McEnroe, you cannot be serious!
Okay, it can be worked around, not by Frank's suggestion about using a
preprocessor, which is, I think, antithetical to Maven's design.
But it's still moderately restrictive.
I don't like it.
-K
On May 17, 2010, at 4:37 PM, Stephen Connolly wrote:
you have to use the previously release version
On 17 May 2010 22:24, Kathryn Huxtable kath...@kathrynhuxtable.org wrote:
So how do I use my documentation-producing plugin in its own documentation
without a variable version number?
See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xmlfor
an example. It's in the site profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote:
Yes variable version names are not allowed as of Maven 3. I believe the
reason will be deploying into repositories, as pom with version as some
properties instead of a proper version could get deployed.
A quick fix is to configure Eclipse to use external installation of Maven
2. But remember that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with
maven2 we
could specify a variable for the application version in the parent pom,
so that
in the child poms we could able to specify the version by the same
variable.
That helps us saving our time for updating version number in each
project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have
been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc..
However,
the solution never comes up.. Maybe I am doing something wrong, but
could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi-module source release assembly, using Common Apache POM version 7 not using moduleSets?
Hi Brian,
I think the moduleSet support was upgraded in the more recent releases,
to support other than tree-structures. My projects are *not* in a
directory tree, but are instead, flat. The modules elements look
like module../submodule1/module.
I built the following and tested it and it seems to work nicely. First,
I created another assembly descriptor and saved it as a loadable
resource for the assembly plugin to reference. This descriptor is
designed to work for either multi-module assemblies, or just single
projects (no modules):
assembly
idsource-release/id !-- match the previous one, becomes
classifier --
formats
formatzip/format
/formats
moduleSets
moduleSet
sources
outputDirectory//outputDirectory
useDefaultExcludestrue/useDefaultExcludes
excludes
!-- here, I copied all those hairy regex things from the
Apache Common Parent version --
...
/excludes
/sources
/moduleSet
/moduleSets
fileSets
!-- this gets the aggregate artifact source, or if no modules,
the main source, as before --
fileSet
directory./directory
outputDirectory/${project.artifactId}/outputDirectory
useDefaultExcludestrue/useDefaultExcludes
excludes
!-- here, I (once again) copied all those hairy regex things
from the Apache Common Parent version --
...
/excludes
/fileSet
!-- license, readme, etc. calculated at build time --
fileSet
directory${project.build.directory}/maven-shared-archive-resources/META-INF/directory
outputDirectory//outputDirectory
/fileSet
/fileSets
/assembly
Having that, I then overrode the Apache Common Parent POM build action
when apache-release is specified as a profile:
properties
sourceReleaseAssemblyDescriptormultimodule-source-release/sourceReleaseAssemblyDescriptor
/properties
plugin
artifactIdmaven-assembly-plugin/artifactId
dependencies
dependency !-- here I stuck in the dependency on the above
saved asm descriptor --
groupIdorg.apache.uima/groupId
artifactIduima-jar-resource-bundle/artifactId
version1-SNAPSHOT/version
/dependency
/dependencies
/plugin
This seems to work (at least for my project). I think it should be
considered for the common Apache Parent pom. Should I open a Jira for
this, and if so, what Jira system is being used for the Apache Parent poms?
-Marshall Schor
On 5/17/2010 5:13 PM, Brian E. Fox wrote:
This descriptor assumes that all modules ate children of the execution
root...or a tree. If that's not the case in your project then you
would need to create a custom bundle descriptor.
--Brian (mobile)
On May 17, 2010, at 3:20 PM, Marshall Schor m...@schor.com wrote:
The current common apache parent POM (version 7) [1], when you specify
the apache-release profile, activates a part:
plugins
!--
Create a source-release artifact that contains the fully buildable
project directory source structure. This is the artifact
which is
the official subject of any release vote.
--
plugin
artifactIdmaven-assembly-plugin/artifactId
. . .
executions
execution
idsource-release-assembly/id
. . .
configuration
runOnlyAtExecutionRoottrue/runOnlyAtExecutionRoot
. . .
/configuration
When used on a multi-module aggregate project, this only creates the
source-release-assembly at the aggregate project level. It seems to me,
since this artifact is the official subject of any release vote, that
this source assembly should include the sources from this aggregate
project, plus all of the sub-modules . (Currently it only has
the the source from this aggregate project; none of the submodules are
included.)
I think the assembly plugin attempts to support this use case, via its
moduleSets elements. Are multi-module projects in Apache supposed
to override the common Apache Parent and specify the moduleSets form
of assembly?
Or is there another preferred way to do this?
-Marshall Schor
[1] http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: unit test not finding dependent class
We don't use shaded plugin. Seems like you've exhausted the capabilities of this list without providing either more information or more ideally a sample project that demonstrates the issue. Can you provide one? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Put applet jar to WAR root
Use the dependency plugin. See http://svn.apache.org/repos/asf/incubator/shiro/trunk/samples/spring/pom.xml for example, doing exactly the same thing for deploying a webstart app to webapp broot. Kalle On Mon, May 17, 2010 at 3:40 AM, Aleksey Didik di...@magenta-technology.ru wrote: Hello all, I need to put the applet jar to my WAR root folder. Applet jar are developed in the same project, just another module. I define applet jar as module dependency, but in this case it was put in WEB-INF/lib. Is at possible to make some mapping to put this jar to root folder? And use outputFileMapping in the same time. I use maven-war-plugin. Thanks, Aleksey. - 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: unit test not finding dependent class
I ran into something similar yesterday (however, in that case it didn't work with m2e either). The scm used was clearcase (dynamic view) which was likely causing the problem (it had happened before apparently). I don't know why, but after several mvn clean install and removing the local repo at least once, I got it to work. Are you using clearcase? /Anders On Tue, May 18, 2010 at 03:44, Wayne Fay wayne...@gmail.com wrote: We don't use shaded plugin. Seems like you've exhausted the capabilities of this list without providing either more information or more ideally a sample project that demonstrates the issue. Can you provide one? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
