Re: How to set the dependencies of plugin?
Add a dependencies section to the plugin On 22 February 2012 05:48, zhaoyi youhaod...@gmail.com wrote: I am using a maven plugin which has some dependencies. How can I modify the plugin's dependencies in my pom.xml? -- View this message in context: http://maven.40175.n5.nabble.com/How-to-set-the-dependencies-of-plugin-tp5504204p5504204.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-deploy-plugin 2.7
Plugin fail to read url tag as variable:
project.distributionManagement.repository.url
and url is HTTTP based protokol
execution
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
url${project.distributionManagement.repository.url}/url
repositoryIdsnapshots/repositoryId
file${dist.dir.client}/${client.jar.arnes.name}.jar/file
Error:
The parameters 'file', 'url' for goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file are missing or
invalid
Another maven plugin with bad documentation or error output, maven is so
unpredictable building tool.
Regards, Tomaz
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: maven: scm: clearcase URL help
Hi Lyons, Really appreciate your help here. see, the problem is that maven is not my issue here, its lack of knowledge of CC thats holding me i guess. in your reply : scm connectionscm:clearcase:*load /some/load/rule*:*/your/project/vob*:your_stream_name/connection /scm load /some/load/rule: i dont know where to get this load rule. is this a path to a rule file. at some places in the maven scm sites for cc it said some config-spec.txt /your/project/vob: is this the local path to my view like : C:/cc_views/UserName_CompanyName_ProjectName_Dev/COMP_ProjectName_vob/ my clearcase-settings.xml only has this as stated on the maven scm site for cc: clearcase-settings clearcaseTypeUCM/clearcaseType /clearcase-settings Thanks for the help. -- View this message in context: http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5504664.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0.3 Not Allowing Different Versions for Compile/Test
put the tests in a separate module and that way the module can have the alternative dependency On 21 February 2012 09:44, Daniel Jones dan...@mendeley.com wrote: Hi all, Apologies in advance if this isn't the right list to post to. Using Maven 3.0.3 and Dependency plug-in 2.4, I've encountered a strange issue whereby if I specify different versions of a dependency, one in compile scope and one in test, only one of them gets 'noticed'. I've detailed the problem on Stack Overflow (http://stackoverflow.com/questions/9364511/maven-different-dependency-version-in-test), but I'll repeat the explanation here. In my project I need to depend on a Cloudera distribution of Hadoop and a 'vanilla' version for JUnit testing, as the former only works on *nix. When I try and execute my application, I get Exception in thread main java.lang.NoClassDefFoundError: org/apache/hadoop/conf/Configuration. When I run JUnit tests from Maven or Eclipse, everything works fine. If I comment out the test dependencies, the application runs successfully, but then the tests fail because they're using the wrong version. Why is the compile dependency getting ignored when the test dependency is uncommented? dependency groupIdorg.apache.hadoop/groupId artifactIdhadoop-core/artifactId version0.20.2-cdh3u2/version scopecompile/scope /dependency dependency groupIdorg.apache.hadoop/groupId artifactIdhadoop-core/artifactId version1.0.0/version scopetest/scope /dependency dependency groupIdorg.apache.hadoop/groupId artifactIdhadoop-test/artifactId version1.0.0/version scopetest/scope /dependency mvn dependency:list shows the following, which does not show the compile scoped version at all: [INFO] The following files have been resolved: [INFO] ant:ant:jar:1.6.5:test [INFO] aopalliance:aopalliance:jar:1.0:compile [INFO] asm:asm:jar:3.3.1:compile [INFO] cglib:cglib:jar:2.2.2:compile [INFO] ch.qos.logback:logback-classic:jar:1.0.0:compile [INFO] ch.qos.logback:logback-core:jar:1.0.0:compile [INFO] com.google.guava:guava:jar:r08:compile [INFO] com.h2database:h2:jar:1.3.164:test [INFO] com.jolbox:bonecp:jar:0.7.1.RELEASE:compile [INFO] com.sun.jersey:jersey-core:jar:1.11:test [INFO] commons-beanutils:commons-beanutils:jar:1.7.0:test [INFO] commons-beanutils:commons-beanutils-core:jar:1.8.0:test [INFO] commons-cli:commons-cli:jar:1.2:test [INFO] commons-codec:commons-codec:jar:1.4:test [INFO] commons-collections:commons-collections:jar:3.2.1:test [INFO] commons-configuration:commons-configuration:jar:1.6:test [INFO] commons-digester:commons-digester:jar:1.8:test [INFO] commons-el:commons-el:jar:1.0:test [INFO] commons-httpclient:commons-httpclient:jar:3.0.1:test [INFO] commons-lang:commons-lang:jar:2.4:test [INFO] commons-logging:commons-logging:jar:1.1.1:compile [INFO] commons-net:commons-net:jar:1.4.1:test [INFO] hsqldb:hsqldb:jar:1.8.0.10:test [INFO] junit:junit:jar:4.10:test [INFO] mysql:mysql-connector-java:jar:5.1.18:compile [INFO] net.java.dev.jets3t:jets3t:jar:0.7.1:test [INFO] net.sf.kosmosfs:kfs:jar:0.3:test [INFO] org.apache.commons:commons-math:jar:2.1:test [INFO] org.apache.ftpserver:ftplet-api:jar:1.0.0:test [INFO] org.apache.ftpserver:ftpserver-core:jar:1.0.0:test [INFO] org.apache.ftpserver:ftpserver-deprecated:jar:1.0.0-M2:test [INFO] org.apache.hadoop:hadoop-core:jar:1.0.0:test [INFO] org.apache.hadoop:hadoop-test:jar:1.0.0:test [INFO] org.apache.mina:mina-core:jar:2.0.0-M5:test [INFO] org.codehaus.jackson:jackson-core-asl:jar:1.0.1:test [INFO] org.codehaus.jackson:jackson-mapper-asl:jar:1.0.1:test [INFO] org.eclipse.jdt:core:jar:3.1.1:test [INFO] org.hamcrest:hamcrest-core:jar:1.1:test [INFO] org.liquibase:liquibase-core:jar:2.0.3:test [INFO] org.liquibase.ext:liquibase-slf4j:jar:0.0.1:test [INFO] org.mortbay.jetty:jetty:jar:6.1.26:test [INFO] org.mortbay.jetty:jetty-util:jar:6.1.26:test [INFO] org.mortbay.jetty:jsp-2.1:jar:6.1.14:test [INFO] org.mortbay.jetty:jsp-api-2.1:jar:6.1.14:test [INFO] org.mortbay.jetty:servlet-api:jar:2.5-20081211:test [INFO] org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:test [INFO] org.slf4j:jcl-over-slf4j:jar:1.6.4:compile [INFO] org.slf4j:log4j-over-slf4j:jar:1.6.4:compile [INFO] org.slf4j:slf4j-api:jar:1.6.4:compile [INFO] org.springframework:spring-aop:jar:3.1.1.RELEASE:compile [INFO] org.springframework:spring-asm:jar:3.1.1.RELEASE:compile [INFO] org.springframework:spring-beans:jar:3.1.1.RELEASE:compile [INFO] org.springframework:spring-context:jar:3.1.1.RELEASE:compile [INFO] org.springframework:spring-context-support:jar:3.1.1.RELEASE:compile [INFO] org.springframework:spring-core:jar:3.1.1.RELEASE:compile [INFO]
Re: One question about Multi Project Structure in MAVEN
Thanks a lot !! That is all i wanted to confirm with you guys. So basically i have to use deploy plugin to deploy the stuffs at repository and over there i can define what components i want to publish or deployed. And locally i will have all those copy available by executing mvn install. Do be aware that if you just use the same POM files in the deployment that you use to build, you may end up with Maven complaining about missing artifacts since you are not uploading all of the files, and you may have configured them as dependencies for some of your projects. So you might need to make another set of POM files just for the deployment and remove these 2 modules and all references to them as dependencies from the POMs. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to correctly make an EJB module dependend of the interface JAR of a RAR?
types of ear, ejb and rar). To be able to compile the EJB module, I have to make it dependend of the interface JAR (which is later packed into the RAR) with compile scope. But, this leads to the fact that the EAR This is the wrong scope for such a use. Use provided. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven: scm: clearcase URL help
Lyons, I tried to use pipes in my url as i had to add my local path for the vob and there was a colon in C:\My\localpath : scm connectionscm:clearcase|[UserName_Local_finApp_Dev]|\\222.222.222.222\cc_drivespace\views\Company\Useranme\Username_Local_finApp_Dev.vws\config_spec|C:\My\localpath\Comp_Local_finApp_vob|Local_finApp_Dev/connection developerConnection/developerConnection url/url /scm it says that when i run mvn scm:validate [INFO] connectionUrl scm connection string is valid. [INFO] project.scm.connection scm connection string is valid. but then it fails with this error. Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.apache.maven.plugins:maven-scm-plugin:1.6:validate failed: String index out of range: -4 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) I will appreciate your help. Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5504733.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: One question about Multi Project Structure in MAVEN
Ya. Installing to local and overriding how the artifacts get deployed is asking for trouble. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Wednesday, February 22, 2012 5:06 AM To: Maven Users List Subject: Re: One question about Multi Project Structure in MAVEN Thanks a lot !! That is all i wanted to confirm with you guys. So basically i have to use deploy plugin to deploy the stuffs at repository and over there i can define what components i want to publish or deployed. And locally i will have all those copy available by executing mvn install. Do be aware that if you just use the same POM files in the deployment that you use to build, you may end up with Maven complaining about missing artifacts since you are not uploading all of the files, and you may have configured them as dependencies for some of your projects. So you might need to make another set of POM files just for the deployment and remove these 2 modules and all references to them as dependencies from the POMs. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven: scm: clearcase URL help
I am taking this conversation off-line as it relates more to clearcase now than maven. Sent from my Blackberry. - Original Message - From: sarmahdi sarma...@hotmail.com To: users@maven.apache.org users@maven.apache.org Sent: Wed Feb 22 04:23:58 2012 Subject: RE: maven: scm: clearcase URL help Lyons, I tried to use pipes in my url as i had to add my local path for the vob and there was a colon in C:\My\localpath : scm connectionscm:clearcase|[UserName_Local_finApp_Dev]|\\222.222.222.222\cc_drivespace\views\Company\Useranme\Username_Local_finApp_Dev.vws\config_spec|C:\My\localpath\Comp_Local_finApp_vob|Local_finApp_Dev/connection developerConnection/developerConnection url/url /scm it says that when i run mvn scm:validate [INFO] connectionUrl scm connection string is valid. [INFO] project.scm.connection scm connection string is valid. but then it fails with this error. Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.apache.maven.plugins:maven-scm-plugin:1.6:validate failed: String index out of range: -4 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) I will appreciate your help. Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5504733.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven: scm: clearcase URL help
Im sorry if i seem to be annoying, hence you taking it offline. But in pure maven's sense, its still is the maven's style of URL that is needed here. (not trying to argue, just my own understanding of my problem which of course can be wrong) I have the view name, stream name, the remote path to config_spec (in clear case), the local path to my local vob in my local view. it says: [INFO] viewName = '5510041_Local_eCorp_II_Dev' ; configSpec = 'load \\remotehost\ccstg_d\views\comp\Username\Username_Local_finApp_Dev.vws\config_spec' ; vobName = 'C:/cc_views/Username_Local_finApp_Dev/Comp_Local_finApp_vob' ; streamName = 'Local_finApp_Dev' ; elementName = 'null' [INFO] project.scm.connection scm connection string is valid. then the maven exception: maven's exception doesnt give me anything more than Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -4 I think I got all the info from CC for the URL, so What am I missing in maven? if it is the element name then where do i specify that? pls help. I will really appreciate it. Thanks Syed... -- View this message in context: http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5505214.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven: scm: clearcase URL help
the biggest problem is that you are trying to use physical locations. The load rule is definitely incorrect. this needs to be the component root. vob name is incorrect -- this needs to be the vob tag, not some physical location you also don't need to specify the view -- it creates its own view -- hence you need to give it a view storage location where it can create a view. also, don't use \ -- use /. load rule as I see it here would be load /Comp_Local_finApp_vob and the view storage location would be //remotehost/ccstg_d/views/comp/Username -Original Message- From: sarmahdi [mailto:sarma...@hotmail.com] Sent: Wednesday, February 22, 2012 8:13 AM To: users@maven.apache.org Subject: Re: maven: scm: clearcase URL help Im sorry if i seem to be annoying, hence you taking it offline. But in pure maven's sense, its still is the maven's style of URL that is needed here. (not trying to argue, just my own understanding of my problem which of course can be wrong) I have the view name, stream name, the remote path to config_spec (in clear case), the local path to my local vob in my local view. it says: [INFO] viewName = '5510041_Local_eCorp_II_Dev' ; configSpec = 'load \\remotehost\ccstg_d\views\comp\Username\Username_Local_finApp_Dev.vws\config_spec' ; vobName = 'C:/cc_views/Username_Local_finApp_Dev/Comp_Local_finApp_vob' ; streamName = 'Local_finApp_Dev' ; elementName = 'null' [INFO] project.scm.connection scm connection string is valid. then the maven exception: maven's exception doesnt give me anything more than Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -4 I think I got all the info from CC for the URL, so What am I missing in maven? if it is the element name then where do i specify that? pls help. I will really appreciate it. Thanks Syed... -- View this message in context: http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5505214.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
RE: One question about Multi Project Structure in MAVEN
So basically i have to use deploy plugin to deploy the stuffs at repository and over there i can define what components i want to publish or deployed. Sometimes the definitions are kind of vague in the maven literature. A repository is simply the thing that holds your maven artifacts. There's your local one, .m2, and zero to many remote ones. Deploy means put the artifact in a remote repository. Install means put it in your local one. The remote ones can be public, or private. You most assuredly want a private one. At some point, you might also deploy a publicly distributable artifact to a public repository, like maven central, so the public can get to it. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: customizing the snapshot version build number
P.S. I think screwing around with the Maven snapshot naming scheme is asking for trouble. Putting it in the manifest seems safer to me. Unfortunately, you didn't elaborate on *why* you want to do this, so we can't really comment on any alternative solutions. Oh, I can elaborate ;) This is currently how my team traces its way back from an binary artifact in the field to source control checkins. I assume there are much better ways to do this, but, my approach, is an incremental re-work of our nonstandard build with an eye towards the lowest hanging fruit, iteratively. Know what I mean? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: customizing the snapshot version build number
On Feb 22, 2012, at 10:16 AM, chad.da...@emc.com wrote: P.S. I think screwing around with the Maven snapshot naming scheme is asking for trouble. Putting it in the manifest seems safer to me. Unfortunately, you didn't elaborate on *why* you want to do this, so we can't really comment on any alternative solutions. Oh, I can elaborate ;) This is currently how my team traces its way back from an binary artifact in the field to source control checkins. I assume there are much better ways to do this, but, my approach, is an incremental re-work of our nonstandard build with an eye towards the lowest hanging fruit, iteratively. Know what I mean? It sounds like you're describing ad-hoc releases. Recording the SCM id in the manifest will provide traceability, but you're also opening up the can of worms that variances in snapshots of the transitive dependencies make the version of a field installation the *set* of versions for the transitive snapshots that could also vary. Make sense? Resolving issues will get a lot harder because of this. For that reason, I'd adjust your process so field engineers can generate releases on the CI in a self-service manner. If I were BigCo, I'd probably link the release generation requests to the field sites that use them so that I can figure out what customers have these releases when it comes time to get them all updated. Brian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug?
Hello, Do you have a sample project to reproduce that ? 2012/2/22 nodje nodje...@gmail.com: migration form 2.x to 3.0-betax wasn't much of a problem, but since then, I had to release components and fix version. Now with maven-site-plugin:3.0, I have a recurring error and can't find any information on it. It basically looks like this, happens on 'mvn site' goal. Number of foreign imports: 1 import: Entry[import from realm ClassRealm[maven.api, parent: null]] - at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:139) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.PluginContainerException: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-site-plugin:3.0:site: java.lang.AbstractMethodError: null I still have a couple of small components which can successfully pass the 'site' goal, but they don't seem to have anything different from the others. Can't figure anything form those, site.xml is identical in every project. See end of post for complete debug stack trace. Thanks for any help or pointer. realm = pluginorg.apache.maven.plugins:maven-site-plugin:3.0 strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy urls[0] = file:/Users/nodje/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar urls[1] = file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.0.1/maven-reporting-exec-1.0.1.jar urls[2] = file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar urls[3] = file:/Users/nodje/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar urls[4] = file:/Users/nodje/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[5] = file:/Users/nodje/.m2/repository/velocity/velocity/1.5/velocity-1.5.jar urls[6] = file:/Users/nodje/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar urls[7] = file:/Users/nodje/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar urls[8] = file:/Users/nodje/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar urls[9] = file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar urls[10] = file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar urls[11] = file:/Users/nodje/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar urls[12] = file:/Users/nodje/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar urls[13] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.2/doxia-sink-api-1.2.jar urls[14] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.2/doxia-logging-api-1.2.jar urls[15] = file:/Users/nodje/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar urls[16] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar urls[17] = file:/Users/nodje/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar urls[18] = file:/Users/nodje/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar urls[19] = file:/Users/nodje/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar urls[20] = file:/Users/nodje/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar urls[21] = file:/Users/nodje/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar urls[22] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.2/doxia-module-xhtml-1.2.jar urls[23] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.2/doxia-module-apt-1.2.jar urls[24] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.2/doxia-module-xdoc-1.2.jar urls[25] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.2/doxia-module-fml-1.2.jar urls[26] = file:/Users/nodje/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar urls[27] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.2/doxia-decoration-model-1.2.jar urls[28] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.2/doxia-site-renderer-1.2.jar urls[29] = file:/Users/nodje/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar urls[30] = file:/Users/nodje/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.4/maven-doxia-tools-1.4.jar urls[31] = file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar urls[32] =
RE: One question about Multi Project Structure in MAVEN
Put this in your pojo and java poms: plugin artifactIdmaven-deploy-plugin/artifactId configuration skiptrue/skip /configuration /plugin It will still install to local, but won't deploy to remote. -Original Message- From: Daivish Shah [mailto:daivish.s...@gmail.com] Sent: Tuesday, February 21, 2012 1:09 PM To: Maven Users List Subject: One question about Multi Project Structure in MAVEN Hi, I have a project with following structure. maven-main-project maven-ear maven-ejb maven-schema maven-pojo maven-java This is my project structure for multi-module project. And now if i don't want to publish any artifacts outside of this project. I mean to say i don't want to publish any artifactory/nexus/archiva repository copy for other people to use it. *Use Case :* Here my maven-ear is part of the maven-main-project and that's the only module which use the maven-pojo and maven-java generated artifacts and which i don't want to publish it on repository but just want to use it for building the EAR. How can i disable those 2 (maven-pojo and maven-java) projects not to publish artifacts at repository level. Looking for some solution on this, As don't want to create unncessary artifacts on repository as nobody is going to use it other then my own Main project EAR project. Thanks. __ This message, including any attachments, is confidential and contains information intended only for the person(s) named above. Any other distribution, copying or disclosure is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify us immediately by reply email and permanently delete the original transmission from all of your systems and hard drives, including any attachments, without making a copy. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven: scm: clearcase URL help
:( sigh! I changed my viewName to : the remotepath, changed my configspec to load /Comp_Local_finApp_vob (without quotes ofcourse), my vobName: Comp_Local_finApp_vob kept the stream name as it was the same. I also changed my configspec to the remote path to my UCM generated config_spec file as in : connectionscm:clearcase|//remotehost/ccstg_d/views/company/UserName|//remotehost/ccstg_d/views/comp/Username/Username_Local_finApp_Dev.vws/config_spec|/Comp_Local_finApp_vob|Local_finApp_Dev/connection I also added Username_Local_finApp_Dev.vws in the viewName at the end to give it a .vws directory to point to so for viewName I tried: 1)//remotehost/ccstg_d/views/company/UserName 2)//remotehost/ccstg_d/views/company/UserName/Username_Local_finApp_Dev.vws tried them both alternatively and Both didnt work for my configSpec part 1)load /Comp_Local_finApp_vob 2)//remotehost/ccstg_d/views/comp/Username/Username_Local_finApp_Dev.vws/config_spec (made sure it exists on the remote path and I can browse to this directory as well) tried them both alternatively and Both didnt work But all of them gave me the same exception of Stringindexoutofboundexception. SO... i looked into the exception more clearly: here it is my research on the maven scm provider code : the exception to me comes like this : Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -4 at java.lang.String.substring(String.java:1937) at java.lang.String.substring(String.java:1904) at org.apache.maven.scm.provider.ScmUrlUtils.getDelimiter(ScmUrlUtils.java:51) at org.apache.maven.scm.provider.ScmUrlUtils.getProvider(ScmUrlUtils.java:76) . I went into the http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven.scm/maven-scm-api/1.5/org/apache/maven/scm/provider/ScmUrlUtils.java#ScmUrlUtils.getDelimiter%28java.lang.String%29 ScmUrlUtils.java.getDelimeter() and it is trying to substring with int 4 scmUrl = scmUrl.substring( 4 ); // which should give it substring after scm: now this line is the one giving me the exception at substring(4). and with String index out of range: -4 it seems that it is an empty string (they didnt check for an empty string or null string). NOW! :( it seems the issue is some where else and not with any of the parameters that I am giving (at least they are not the issue here for now) I have no idea how to solve this. Maven was going very easy with me uptill now, i think it is showing me some pain now I will appreciate any comment or suggestions. (as I badly need some) Thanks for the help and bearing with me. (esp with my lack of knowledge in maven as well as clearcase) Syed... -- View this message in context: http://maven.40175.n5.nabble.com/maven-scm-clearcase-URL-help-tp5502632p5505505.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
axistools:wsdl2java
Whenever I try to run the axistoos:wsdl2java action I get the following: Feb 22, 2012 10:31:52 AM org.apache.axis.utils.JavaUtils isAttachmentSupported WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. In real-life I just needed to have javax.mail and javax.activation in my class path when I generated my sources and I don't get this. In my pom.xml I have: dependency groupIdjavax.activation/groupId artifactIdactivation/artifactId version1.1.1/version scopegenerate-sources/scope /dependency dependency groupIdjavax.mail/groupId artifactIdmail/artifactId version1.4.4/version scopegenerate-sources/scope /dependency I've tried every scope I can think of to get these dependencies to be part of the class path for the axistool:wsdl2java action, but can't seem to make it work. Anyone have any advice why these dependencies are not showing up to the axistool module action? Help... Thanks, John -- View this message in context: http://maven.40175.n5.nabble.com/axistools-wsdl2java-tp5505592p5505592.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: axistools:wsdl2java
Generate-sources is a phase, not a dependency scope. Get rid of that for a start. I'm surprised maven even allowed that. I guess it accepts anything there. -Original Message- From: jgruber [mailto:john.t.gru...@gmail.com] Sent: Wednesday, February 22, 2012 9:38 AM To: users@maven.apache.org Subject: axistools:wsdl2java Whenever I try to run the axistoos:wsdl2java action I get the following: Feb 22, 2012 10:31:52 AM org.apache.axis.utils.JavaUtils isAttachmentSupported WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. In real-life I just needed to have javax.mail and javax.activation in my class path when I generated my sources and I don't get this. In my pom.xml I have: dependency groupIdjavax.activation/groupId artifactIdactivation/artifactId version1.1.1/version scopegenerate-sources/scope /dependency dependency groupIdjavax.mail/groupId artifactIdmail/artifactId version1.4.4/version scopegenerate-sources/scope /dependency I've tried every scope I can think of to get these dependencies to be part of the class path for the axistool:wsdl2java action, but can't seem to make it work. Anyone have any advice why these dependencies are not showing up to the axistool module action? Help... Thanks, John -- View this message in context: http://maven.40175.n5.nabble.com/axistools-wsdl2java- tp5505592p5505592.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 __ This message, including any attachments, is confidential and contains information intended only for the person(s) named above. Any other distribution, copying or disclosure is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify us immediately by reply email and permanently delete the original transmission from all of your systems and hard drives, including any attachments, without making a copy. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: axistools:wsdl2java
I believe to fix your issue you need to add them as a dependency of the plugin, so similar to below. [...] build [...] plugins [...] plugin groupIdorg.apache.axis2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId [...] dependencies !-- * add dependencies here * -- /dependencies /plugin [...] John On 22 February 2012 16:38, jgruber john.t.gru...@gmail.com wrote: Whenever I try to run the axistoos:wsdl2java action I get the following: Feb 22, 2012 10:31:52 AM org.apache.axis.utils.JavaUtils isAttachmentSupported WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. In real-life I just needed to have javax.mail and javax.activation in my class path when I generated my sources and I don't get this. In my pom.xml I have: dependency groupIdjavax.activation/groupId artifactIdactivation/artifactId version1.1.1/version scopegenerate-sources/scope /dependency dependency groupIdjavax.mail/groupId artifactIdmail/artifactId version1.4.4/version scopegenerate-sources/scope /dependency I've tried every scope I can think of to get these dependencies to be part of the class path for the axistool:wsdl2java action, but can't seem to make it work. Anyone have any advice why these dependencies are not showing up to the axistool module action? Help... Thanks, John -- View this message in context: http://maven.40175.n5.nabble.com/axistools-wsdl2java-tp5505592p5505592.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
Re: axistools:wsdl2java
Generate-sources is a phase, not a dependency scope. This is correct, but ideally he would move the dependencies so they are inside the plugin declaration since he only needs these dependencies for the execution of the plugin. Get rid of that for a start. I'm surprised maven even allowed that. I guess it accepts anything there. Yes, Maven accepts anything there, a fact which some plugin authors (FlexMojos) have taken advantage of: https://docs.sonatype.org/display/FLEXMOJOS/Adding+libraries+to+compilation I am not a fan of this but it has been discussed in JIRA and Maven3 simply reports a warning but does not fail with an error: http://jira.codehaus.org/browse/MNG-3991 Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
resources
Hello, I have a Maven project with resource files in src/main/resources. Currently the jar file generated includes the resources in the jar but I'd like them outside of the jar file ideally in the same directory as the jar file so I added the resources section to my pom.xml as follows: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.4/version configuration archive manifest addClasspathtrue/addClasspath mainClassit.myapp/mainClass /manifest manifestEntries Class-Path./Class-Path /manifestEntries /archive /configuration /plugin /plugins resources resource directorysrc/main/resources/directory targetPath../targetPath /resource /resources /build The problem is when I attempt to clean and build, my JUnit tests fail due to an exception: Caused by: java.util.MissingResourceException: Can't find bundle for base name MessageResourceBundle, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1499) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322) at java.util.ResourceBundle.getBundle(ResourceBundle.java:724) If I remove the resources section, the clean and build is successful but my resources files are inside the jar. I want them on the outside. I verified the above in a separate test project without a message resource bundle so the problem is with the bundle but why? How do I fix this?
Re: resources
If you want them out of the jar just put them out of the resources folder into e.g. src/main/assets or whatever.. Then you can bundle the jar and those together later. However I fail to understand why you want to do that the first place.. manfred On 12-02-22 02:34 PM, Maria Cristina wrote: Hello, I have a Maven project with resource files in src/main/resources. Currently the jar file generated includes the resources in the jar but I'd like them outside of the jar file ideally in the same directory as the jar file so I added theresources section to my pom.xml as follows: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.4/version configuration archive manifest addClasspathtrue/addClasspath mainClassit.myapp/mainClass /manifest manifestEntries Class-Path./Class-Path /manifestEntries /archive /configuration /plugin /plugins resources resource directorysrc/main/resources/directory targetPath../targetPath /resource /resources /build The problem is when I attempt to clean and build, my JUnit tests fail due to an exception: Caused by: java.util.MissingResourceException: Can't find bundle for base name MessageResourceBundle, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1499) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322) at java.util.ResourceBundle.getBundle(ResourceBundle.java:724) If I remove theresources section, the clean and build is successful but my resources files are inside the jar. I want them on the outside. I verified the above in a separate test project without a message resource bundle so the problem is with the bundle but why? How do I fix this? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Execute maven-assembly-plugin twice during package phase
Hi, I would like to create a jar file with all the dependencies and then create a zip file which would contain the jar file. The problem is that maven creates the zip file before the jar file and then ... I'm a little bit lost. I enclosed my POM file in this post. Thanks, PY -- View this message in context: http://maven.40175.n5.nabble.com/Execute-maven-assembly-plugin-twice-during-package-phase-tp5505700p5505700.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: How to correctly make an EJB module dependend of the interface JAR of a RAR?
I suspect that you will have deployment issues if the EJB module does not have visibility of the interface classes. You should perhaps be placing this jar in the EAR/lib directory (assuming a JEE5+ compliant container) and sharing it between the RAR and EJB jar. On 22/02/2012, at 5:13 AM, Markus Karg wrote: I have set up a typical EAR scenario, where a EJB module and a RAR module are packaged into a EAR module (using the respective package types of ear, ejb and rar). To be able to compile the EJB module, I have to make it dependend of the interface JAR (which is later packed into the RAR) with compile scope. But, this leads to the fact that the EAR later contains not only the EJB and the RAR, but also the interface JAR. As the interface JAR already is contained in the RAR, this is redundant. What is The Maven Way to prevent this redundance, so the EAR will not contain the additional interface JAR? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: known problem to get JUnit 4 and TestNG working together
FYI, TestNG can run JUnit 4 tests as of last week :-) -- View this message in context: http://maven.40175.n5.nabble.com/known-problem-to-get-JUnit-4-and-TestNG-working-together-tp5500597p5506835.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: maven-failsafe-plugin incorrect reports when running parallel tests
Because this issue persists, where should I file a bug report? Regards, Christian -Ursprüngliche Nachricht- Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] Im Auftrag von Kristian Rosenvold Gesendet: Dienstag, 7. Februar 2012 21:15 An: Maven Users List; christ...@schlichtherle.de Betreff: Re: maven-failsafe-plugin incorrect reports when running parallel tests I have looked through all our current integration tests regarding failing of build with failsafe, and they all seem to be ok. You have probably uncovered some unknown problem, and I request that you do the following: svn co https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire- integration-tests/src/test/resources/failsafe-buildfail/ cd failsafe-buildfail mvn -Dsurefire.version=2.12 verify Form that point on I'd be really happy if you could try to modify this project to reproduce the failure, and in that case please submit the modified project attached to a jira. I also just updated the developer guides on how to attach a debugger to the fork, which may be just as simple: http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire- plugin/src/site/apt/developing.apt.vm?view=markup Kristian 2012/2/7 Christian Schlichtherle christ...@schlichtherle.de: Hi, I have now run the integration test suite with plugin version 2.10 and it always fails. So the results are: V2.10: Always fails = correct behavior. V2.11: Always fails = correct behavior. V2.12: Always passes = wrong behavior. The configuration is the same as before. Enclosed is a unified diff of the output from the following command line: mvn install -Pintegration-test --debug between plugin version 2.11 and 2.12. I could find nothing unexpected in it. Regards, Christian -Ursprüngliche Nachricht- Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] Im Auftrag von Kristian Rosenvold Gesendet: Dienstag, 7. Februar 2012 18:30 An: Maven Users List; christ...@schlichtherle.de Betreff: Re: maven-failsafe-plugin incorrect reports when running parallel tests The thing is, you might be hitting two different problems, which is where I'd really like for you to test 2.10. 2.11 had a *known* problem with certain classloading combinations, which could cause all tests to fail (basically all or nothing, but it would only be hitting users with specific libs/deps). Now this was fixed in 2.12, but SUREFIRE-803 (2.12) does some changes to the failure detection algorithm in failsafe, which may be the cause of some other problem. We have decent test coverage of these things but there's always the chance of some uncovered corner-case. AFIK 2.10 could be used to benchmark the behaviour of your current tests. Kristian 2012/2/7 Christian Schlichtherle christ...@schlichtherle.de: Hi Kristian, I've investigated the subject a little more. For both plugin versions, I use the same configuration (confirmed by both help:effective-pom xor the --debug option): forkMode=once parallel=both useSystemClassLoader=true I also wrote a little test class with two test methods which both simply log the System.identityHashCode() for the test class and its class loader. With both plugin versions, both test method executions report the same class and classloader instance. Yet, with version 2.11 my integration test suite always fails and with version 2.12 it always passes. Now what concerns me is that I wouldn't have noticed that there are issues in my code under test if I had started to use maven-failsafe-plugin with version 2.12. My integration test suite is large and long running, so I can be fairly sure it always fails as long as the multithreading issue(s) exist(s) in my code under test. I also know that the issue(s) in my code under test are not classic racing conditions for objects on the heap, but a failure to properly deal with some IOExceptions when concurrently accessing shared file system resources. Regards, Christian -- - -- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug?
Hum, I guess I can provide something. I can send you the smallest 'mvn site' failing project. Note that it does in a similar fashion on all failing projects. I've integrated the parent pom into the project pom for convenience, I hope it'll work without problem for you. I'll send it on you apache email. cheers Olivier Lamy [via Maven] wrote: Hello, Do you have a sample project to reproduce that ? 2012/2/22 nodje [hidden email] /user/SendEmail.jtp?type=nodenode=5505481i=0: migration form 2.x to 3.0-betax wasn't much of a problem, but since then, I had to release components and fix version. Now with maven-site-plugin:3.0, I have a recurring error and can't find any information on it. It basically looks like this, happens on 'mvn site' goal. Number of foreign imports: 1 import: Entry[import from realm ClassRealm[maven.api, parent: null]] - at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:139) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.plugin.PluginContainerException: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-site-plugin:3.0:site: java.lang.AbstractMethodError: null I still have a couple of small components which can successfully pass the 'site' goal, but they don't seem to have anything different from the others. Can't figure anything form those, site.xml is identical in every project. See end of post for complete debug stack trace. Thanks for any help or pointer. realm =pluginorg.apache.maven.plugins:maven-site-plugin:3.0 strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy urls[0] = file:/Users/nodje/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar urls[1] = file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.0.1/maven-reporting-exec-1.0.1.jar urls[2] = file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar urls[3] = file:/Users/nodje/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar urls[4] = file:/Users/nodje/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[5] = file:/Users/nodje/.m2/repository/velocity/velocity/1.5/velocity-1.5.jar urls[6] = file:/Users/nodje/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar urls[7] = file:/Users/nodje/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar urls[8] = file:/Users/nodje/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar urls[9] = file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar urls[10] = file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar urls[11] = file:/Users/nodje/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar urls[12] = file:/Users/nodje/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar urls[13] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.2/doxia-sink-api-1.2.jar urls[14] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.2/doxia-logging-api-1.2.jar urls[15] = file:/Users/nodje/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar urls[16] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar urls[17] = file:/Users/nodje/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar urls[18] = file:/Users/nodje/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar urls[19] = file:/Users/nodje/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar urls[20] = file:/Users/nodje/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar urls[21] = file:/Users/nodje/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar urls[22] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.2/doxia-module-xhtml-1.2.jar urls[23] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.2/doxia-module-apt-1.2.jar urls[24] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.2/doxia-module-xdoc-1.2.jar urls[25] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.2/doxia-module-fml-1.2.jar urls[26] = file:/Users/nodje/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar urls[27] = file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.2/doxia-decoration-model-1.2.jar urls[28] =
Re: [maven-site-plugin] trouble migrating from 3.0-beta3 to 3.0, bug?
It's not quite related to the problem you're having, but our parent pom's have
this in them:
!-- Reverting back to beta version of the site plugin. v3.0 does
not inherit the properties ('site.deploy.url'
under the 'distributionManagement' section) and results in invalid
href links during the site generation --
plugin
artifactIdmaven-site-plugin/artifactId
version3.0-beta-3/version
/plugin
which you may want to file away for future reference…
On 22/02/2012, at 2:19 PM, nodje wrote:
migration form 2.x to 3.0-betax wasn't much of a problem, but since then, I
had to release components and fix version.
Now with maven-site-plugin:3.0, I have a recurring error and can't find any
information on it. It basically looks like this, happens on 'mvn site' goal.
Number of foreign imports: 1
import: Entry[import from realm ClassRealm[maven.api, parent: null]]
-
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:139)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.plugin.PluginContainerException: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.0:site:
java.lang.AbstractMethodError: null
I still have a couple of small components which can successfully pass the
'site' goal, but they don't seem to have anything different from the others.
Can't figure anything form those, site.xml is identical in every project.
See end of post for complete debug stack trace.
Thanks for any help or pointer.
realm =pluginorg.apache.maven.plugins:maven-site-plugin:3.0
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] =
file:/Users/nodje/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
urls[1] =
file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.0.1/maven-reporting-exec-1.0.1.jar
urls[2] =
file:/Users/nodje/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
urls[3] =
file:/Users/nodje/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
urls[4] = file:/Users/nodje/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[5] =
file:/Users/nodje/.m2/repository/velocity/velocity/1.5/velocity-1.5.jar
urls[6] =
file:/Users/nodje/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
urls[7] =
file:/Users/nodje/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
urls[8] =
file:/Users/nodje/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
urls[9] =
file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
urls[10] =
file:/Users/nodje/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
urls[11] =
file:/Users/nodje/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
urls[12] =
file:/Users/nodje/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
urls[13] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.2/doxia-sink-api-1.2.jar
urls[14] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.2/doxia-logging-api-1.2.jar
urls[15] =
file:/Users/nodje/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
urls[16] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-core/1.2/doxia-core-1.2.jar
urls[17] =
file:/Users/nodje/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
urls[18] =
file:/Users/nodje/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar
urls[19] =
file:/Users/nodje/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
urls[20] =
file:/Users/nodje/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
urls[21] =
file:/Users/nodje/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
urls[22] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.2/doxia-module-xhtml-1.2.jar
urls[23] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.2/doxia-module-apt-1.2.jar
urls[24] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.2/doxia-module-xdoc-1.2.jar
urls[25] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.2/doxia-module-fml-1.2.jar
urls[26] =
file:/Users/nodje/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar
urls[27] =
file:/Users/nodje/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.2/doxia-decoration-model-1.2.jar
urls[28] =
Re: Execute maven-assembly-plugin twice during package phase
Nabble strips attached files. Do you have the executions of the plugin in the right order in the pom? First the jar and then the zip. Also, check the effective-pom (mvn help:effective-pom) to see what Maven is working on. What's the order of the executions there? /Anders On Wed, Feb 22, 2012 at 18:15, pierre46 pierreyves@gmail.com wrote: Hi, I would like to create a jar file with all the dependencies and then create a zip file which would contain the jar file. The problem is that maven creates the zip file before the jar file and then ... I'm a little bit lost. I enclosed my POM file in this post. Thanks, PY -- View this message in context: http://maven.40175.n5.nabble.com/Execute-maven-assembly-plugin-twice-during-package-phase-tp5505700p5505700.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
Re: maven-failsafe-plugin incorrect reports when running parallel tests
http://jira.codehaus.org/browse/SUREFIRE 2012/2/23 Christian Schlichtherle christ...@schlichtherle.de: Because this issue persists, where should I file a bug report? Regards, Christian -Ursprüngliche Nachricht- Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] Im Auftrag von Kristian Rosenvold Gesendet: Dienstag, 7. Februar 2012 21:15 An: Maven Users List; christ...@schlichtherle.de Betreff: Re: maven-failsafe-plugin incorrect reports when running parallel tests I have looked through all our current integration tests regarding failing of build with failsafe, and they all seem to be ok. You have probably uncovered some unknown problem, and I request that you do the following: svn co https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire- integration-tests/src/test/resources/failsafe-buildfail/ cd failsafe-buildfail mvn -Dsurefire.version=2.12 verify Form that point on I'd be really happy if you could try to modify this project to reproduce the failure, and in that case please submit the modified project attached to a jira. I also just updated the developer guides on how to attach a debugger to the fork, which may be just as simple: http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire- plugin/src/site/apt/developing.apt.vm?view=markup Kristian 2012/2/7 Christian Schlichtherle christ...@schlichtherle.de: Hi, I have now run the integration test suite with plugin version 2.10 and it always fails. So the results are: V2.10: Always fails = correct behavior. V2.11: Always fails = correct behavior. V2.12: Always passes = wrong behavior. The configuration is the same as before. Enclosed is a unified diff of the output from the following command line: mvn install -Pintegration-test --debug between plugin version 2.11 and 2.12. I could find nothing unexpected in it. Regards, Christian -Ursprüngliche Nachricht- Von: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] Im Auftrag von Kristian Rosenvold Gesendet: Dienstag, 7. Februar 2012 18:30 An: Maven Users List; christ...@schlichtherle.de Betreff: Re: maven-failsafe-plugin incorrect reports when running parallel tests The thing is, you might be hitting two different problems, which is where I'd really like for you to test 2.10. 2.11 had a *known* problem with certain classloading combinations, which could cause all tests to fail (basically all or nothing, but it would only be hitting users with specific libs/deps). Now this was fixed in 2.12, but SUREFIRE-803 (2.12) does some changes to the failure detection algorithm in failsafe, which may be the cause of some other problem. We have decent test coverage of these things but there's always the chance of some uncovered corner-case. AFIK 2.10 could be used to benchmark the behaviour of your current tests. Kristian 2012/2/7 Christian Schlichtherle christ...@schlichtherle.de: Hi Kristian, I've investigated the subject a little more. For both plugin versions, I use the same configuration (confirmed by both help:effective-pom xor the --debug option): forkMode=once parallel=both useSystemClassLoader=true I also wrote a little test class with two test methods which both simply log the System.identityHashCode() for the test class and its class loader. With both plugin versions, both test method executions report the same class and classloader instance. Yet, with version 2.11 my integration test suite always fails and with version 2.12 it always passes. Now what concerns me is that I wouldn't have noticed that there are issues in my code under test if I had started to use maven-failsafe-plugin with version 2.12. My integration test suite is large and long running, so I can be fairly sure it always fails as long as the multithreading issue(s) exist(s) in my code under test. I also know that the issue(s) in my code under test are not classic racing conditions for objects on the heap, but a failure to properly deal with some IOExceptions when concurrently accessing shared file system resources. Regards, Christian -- - -- 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:
