Perforce Unable to submit error
Hello! I'm having trouble getting scm with perforce working. I've set up a simple project (archetype:create), and then modified my pom.xml to contain this: ... scm connectionscm:perforce:p4bck:1666://my-app/connection developerConnectionscm:perforce:p4bck:1666://my-app/developerConnecti on /scm ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId configuration systemProperties property namemaven.scm.perforce.clientspec.name/name valueMavenclient/value /property /systemProperties usernameuser/username passwordpasswd/password connectionTypedeveloperConnection/connectionType /configuration /plugin /plugins /build ... I am able to do scm:update without errors, and the p4 commandline client works. However, if I do any action which tries to submits, such as release:prepare or scm:checkin, I get an Unable to submit error. For example, here I try checking in my pom.xml: [DEBUG] Executing p4 -d C:\PerforceRoot\MC\my-app -p p4bck:1666 -u user -P submit -i [DEBUG] SCM path in pom: //my-app [DEBUG] Executing: p4 -p p4bck:1666 -u user -P where C:\PerforceRoot\MC\my-app\pom.xml [DEBUG] cannot find depot = using //my-app [DEBUG] Sending changelist: Change: new Description: mvn Files: //my-app/pom.xml [ERROR] Provider message: [ERROR] Unable to submit [ERROR] Command output: [ERROR] First sign of something not working I suppose is cannot find depot, why? And when it cannot, it still uses the correct one... (I've also tried using //Mavenclient/my-app as url, only difference is that it falls back to using //Mavenclient/my-app instead of //my-app) The Mavenclient clientspec exists. I'm using Maven version 2.0.9 with JDK 1.5.0.15 on WinXP. scm-plugin is version 1.0, release-plugin is 2.0-beta-7. Have I done some misconfiguration? There are a few threads about this available when googling, however they either don't get a reply, or the solution does not solve the problem. Any other information needed to debug this? Thankful for any help Carl Pettersson
Re: Question about why/when Maven will automatically exclude transitive dependencies.
Hi, If you want to see the list of dependencies and their scope for a POM, you could try mvn dependency:tree For further information on how to use the dependency plugin, have a look a this link ; http://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html On Tue, Jun 17, 2008 at 6:04 AM, Ryan Moquin [EMAIL PROTECTED] wrote: I guess when I think about it, this looks like a stupid question because it could easily be that I excluded a dependency somewhere which caused the problem. I positive that isn't the issue, but let's pretend it could be.. is there any way to get a list of dependencies and what status maven considers them in? Such as if they are excluded or included for whichever reasons? I'm not sure how to troubleshoot this.. all I know is that it was working a few days ago and I have no idea why all of a sudden my project seems to be so problematic.. just hoping someone might have some suggestions on how to troubleshoot this. Thanks! Ryan On Mon, Jun 16, 2008 at 12:14 PM, Ryan Moquin [EMAIL PROTECTED] wrote: I have never really been able to figure this out and it's really driving me up the wall at the moment. Is there a time that Maven2 will automatically exclude transitive dependencies? Here is the scenario: I have 2 projects, then both include the exact same dependency. When I build the first library, it builds perfectly fine. When I build the second library, it files during the unit tests with NoClassDefFoundErrors. If I look at the dependencies being included, Maven2 isn't including the same transitive dependencies from that common dependency between the two projects. Basically I have to include those transitive dependencies explicitly, which I don't want to do. What are the causes where Maven won't include compile dependencies that a first level dependency is dependant on? It seems very nondeterministic, so I'm guessing there are some nonobvious reason behind the scenes for how it calculates this. Thanks! Ryan
Unit tests seeing test application context files in their dependencies
Hi, I am wondering if it's possible to do the following: My application context uses some beans from a different application context which is located in one of its dependencies. I am now writing unit tests for this project and the dependency as well. So I have my test application context in both these projects, and I would like the one from the dependency to be visible in the other one. Is that possible in any way? I tried this line: import resource=classpath:DependencyTestContext.xml / but it didn't work - that app context was not visible. Thanks, Papapara Tudu -- View this message in context: http://www.nabble.com/Unit-tests-seeing-test-application-context-files-in-their-dependencies-tp17881883p17881883.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How can I deploy parent module without deploying sub modules?
I want to deploy my parent module to the remote repository but not its child modules. How can I do this? -- View this message in context: http://www.nabble.com/How-can-I-deploy-parent-module-without-deploying-sub-modules--tp17881951p17881951.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unit tests seeing test application context files in their dependencies
Hi there; Am Tue, 17 Jun 2008 03:13:02 -0700 (PDT) schrieb Papapara Tudu [EMAIL PROTECTED]: My application context uses some beans from a different application context which is located in one of its dependencies. Looking at your terminologies and file snippets: Are you using Spring in your projects? I tried this line: import resource=classpath:DependencyTestContext.xml / but it didn't work - that app context was not visible. If (I assume so) Spring is involved, this should work, at least I do have libraries (jar artifacts) wired up with web applications (war artifacts) right this way. Where is your DependencyTestContext.xml located? Are you sure this is a maven2 related problem? Cheers, Kristian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unit tests seeing test application context files in their dependencies
Looking at your terminologies and file snippets: Are you using Spring in your projects? Yes If (I assume so) Spring is involved, this should work, at least I do have libraries (jar artifacts) wired up with web applications (war artifacts) right this way. Where is your DependencyTestContext.xml located? Are you sure this is a maven2 related problem? I'm not sure if this is a maven2 problem. The test application context in the dependency is located in the /src/test/resources folder in its project (in the project I'm writing the tests for, my app context is in /src/test/resources also). The actual error I'm getting when I use the import resource=classpath:DependencyTestContext.xml / line is: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:DependencyTestContext.xml] -- View this message in context: http://www.nabble.com/Unit-tests-seeing-test-application-context-files-in-their-dependencies-tp17881883p17882205.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: executing a profile
** nudge ** On Mon, Jun 16, 2008 at 12:42 PM, Karan Malhi [EMAIL PROTECTED] wrote: Hi, I have a requirement to configure the eclipse plugin within the pom so that I can replace the following mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true -DsomeProperty with something in the pom so that I should be able to simply run mvn eclipse:eclipse and download sources and javadocs. The someProperty is a system property which when set, executes a certain profile. I saw the docs on the maven eclipse plugin and figured out how to download sources and javadocs without specifying the properties from the command line. How do I ensure that the profile is also executed? -- Karan Singh Malhi -- Karan Singh Malhi
Re: Incorporating DLL's into Maven Project.
I will give those steps a shot today and let you all know if I run into any
problems. It sounds like a pretty logical thing to do actually, and
fortunately I do not require cross-platform compilation and support at this
point.
One quick question though, when you say that I should use the dependency
plugin to copy the DLL's to the target directory or other suitable location,
could I specify that the DLL's be put inside the jar? (that is, in the
resources folder).
Thanks!
On Mon, Jun 16, 2008 at 15:37, Kalle Korhonen [EMAIL PROTECTED]
wrote:
If you don't need to worry about cross-platform compilation support (and
sounds like you don't), the most straight-forwarded way to do this is to
deploy your dll to a Maven repository with type dll, declare a
straight-up
dependency to it in your pom and then use the dependency plugin to copy the
lib to the target dir or other suitable location for development
environment
and structure you assembly (or whatever is the format of the actual
delivery) similarly. If cross-platform support is desired, nar plugin (
http://java.freehep.org/freehep-nar-plugin/intro.html) is a bit more
involving but simplifies things greatly. However, using it requires some
code changes.
Kalle
On Mon, Jun 16, 2008 at 11:19 AM, Mikel Cármenes Cavia [EMAIL PROTECTED]
wrote:
Hey guys,
I need to include three DLL's in my Maven project. Prior to deciding to
email the list, I have looked around the archives, and haven't been able
to
find anything that would seem to answer my problem (which is a very easy
one
in nature).
I use JNA to interface with two of the three DLL's (the third one is for
Jacob, and its location needs to be set as a system variable).
In Java, I do the following:
URL libURL = this.getClass().getResource(/org/git/systems/DLLs/);
System.setProperty(jna.library.path, libURL.getPath());
And then declare the following interface
public interface CurviLibrary extends Library {
CurviLibrary CurviInitialization = (CurviLibrary)
Native.loadLibrary(Curvi,CurviLibrary.class);
CurviLibrary OptimizedSolver = (CurviLibrary)
Native.loadLibrary(OptimizedSolver,CurviLibrary.class);
DoubleByReference GIT_CURVIG(float[] timeData, float[] rawData, float[]
relax, int rawDataSize, double alphaValue,
long numberOfBins);
}
So when compiled via Eclipse, this works like a charm. I have tried
placing
the DLL's within /main/resources/org/git/systems/DLLs but this does not
seem
to work, as the jar looks in
file:/C:/DEV/Maven/GITSYSTEMS/target/GITSYSTEMS-1.0-jar-with-dependencies.jar!/org/git/systems/DLLs/
which would make sense, if only a jar wasn't a package.
How may I go about adding these DLLs to my Maven project, without having
to
modify the existing Java code?
I am assuming they will have to go outside of the jar, but I am unsure as
to
how to reference and go from there.
Thanks guys!
Re: How can I deploy parent module without deploying sub modules?
Have you tried with the command mvn -N deploy ? Giancarlo 2008/6/17, youhaodeyi [EMAIL PROTECTED]: I want to deploy my parent module to the remote repository but not its child modules. How can I do this? -- View this message in context: http://www.nabble.com/How-can-I-deploy-parent-module-without-deploying-sub-modules--tp17881951p17881951.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
help regarding checkout according to tagname using mvn scm plugin
I want to checkout my project according to tagname.Can anyone helpme out with the command? -- View this message in context: http://www.nabble.com/help-regarding-checkout-according-to-tagname-using-mvn-scm-plugin-tp17885847p17885847.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
need help on maven compile phase.
Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want
Re: How can I deploy parent module without deploying sub modules?
Oh, it works. thanks a lot. Giancarlo Degani wrote: Have you tried with the command mvn -N deploy ? Giancarlo 2008/6/17, youhaodeyi [EMAIL PROTECTED]: I want to deploy my parent module to the remote repository but not its child modules. How can I do this? -- View this message in context: http://www.nabble.com/How-can-I-deploy-parent-module-without-deploying-sub-modules--tp17881951p17881951.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-can-I-deploy-parent-module-without-deploying-sub-modules--tp17881951p1772.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unit tests seeing test application context files in their dependencies
Am Tue, 17 Jun 2008 03:39:19 -0700 (PDT) schrieb Papapara Tudu [EMAIL PROTECTED]: The test application context in the dependency is located in the /src/test/resources folder in its project (in the project I'm writing the tests for, my app context is in /src/test/resources also). I see... Used to do this only while having the context configuration somewhere in src/main/resources. The actual error I'm getting when I use the import resource=classpath:DependencyTestContext.xml / line is: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:DependencyTestContext.xml] Off-hands I am not sure whether the _test_ classpath of an artifact the project depends upon is available to that project. Looking at how things work for test classes (src/test/java , which aren't part of the deployed artifact), I'd take a guess that this might be your problem... This would explain this behaviour as, this way, things below src/test won't be available to you when depending upon the (binary) artifact (in your repository). Don't really know how to get along this, anyhow. Anyone else? :) Cheers, Kristian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: need help on maven compile phase.
Actually, I can think of seperate module inside the main root project and a seperate pom.xml for each one. Then you can build those one by one. Else, try increasing the memory with the compiler plugin (I think, you have atleast 1.5 GB RAM) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration meminitial512m/meminitial maxmem1024m/maxmem /configuration /plugin This may resolve the out of memory error. Regards, Ram On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want -- Thanks Ram
Re: Unit tests seeing test application context files in their dependencies
On Tue, Jun 17, 2008 at 12:00:51PM +, Kristian Rink wrote: Am Tue, 17 Jun 2008 03:39:19 -0700 (PDT) schrieb Papapara Tudu [EMAIL PROTECTED]: The test application context in the dependency is located in the /src/test/resources folder in its project (in the project I'm writing the tests for, my app context is in /src/test/resources also). I see... Used to do this only while having the context configuration somewhere in src/main/resources. The actual error I'm getting when I use the import resource=classpath:DependencyTestContext.xml / line is: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:DependencyTestContext.xml] Off-hands I am not sure whether the _test_ classpath of an artifact the project depends upon is available to that project. Looking at how things work for test classes (src/test/java , which aren't part of the deployed artifact), I'd take a guess that this might be your problem... This would explain this behaviour as, this way, things below src/test won't be available to you when depending upon the (binary) artifact (in your repository). Don't really know how to get along this, anyhow. Anyone else? :) The approach I've used is to have (eg) DependencyContext.xml for the live service under src/main/resources/ and one for tests (with the same name) under src/test/resources/. This way, the import... statement (which is presumably in a file under src/main/resources/) should pick up the correct resource for both situations because of the way the classpath is constructed. cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as HP CONFIDENTIAL. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: need help on maven compile phase.
I tried increasing the memory using the maxmem and memintial, initial=512mb and mac=2048m. still the same error. my 1642 files have been distributed accross four packages. src/main/java/com/abc/xyz/pkg1 pkg2 pkg3 pkg4 whould i write seperate POMs for each pkg? where should these POMs be present. then what about the main POM in the prj_home/dir? On 6/17/08, RAM [EMAIL PROTECTED] wrote: Actually, I can think of seperate module inside the main root project and a seperate pom.xml for each one. Then you can build those one by one. Else, try increasing the memory with the compiler plugin (I think, you have atleast 1.5 GB RAM) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration meminitial512m/meminitial maxmem1024m/maxmem /configuration /plugin This may resolve the out of memory error. Regards, Ram On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want -- Thanks Ram -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want
Re: Apparent Plugin Version Mismatch with maven-deploy-plugin and wagon-ftp
So I take it that the beta 3's are targeted at Maven 2.1? Is there not a way in Maven to prevent plug ins that are targeted at different versions of maven from being installed? Thanks, Chris Brian E. Fox wrote: Those wagons are not compatible with maven 2.0.9 or less. -Original Message- From: Chris Lieb [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2008 12:10 PM To: users@maven.apache.org Subject: Re: Apparent Plugin Version Mismatch with maven-deploy-plugin and wagon-ftp I was accidentally overriding the versions that were set in the master POM in the project that I was testing in. After I fixed that, the deploy phase started working again. Is there a reason why 1.0-beta-3 of wagon-ftp and wagon-provider-api don't seem to work? Chris Lieb Chris Lieb wrote: I have a project that deploys using the wagon-ftp plugin. It has been building without issue for months now through CruiseControl. Over the weekend when a build was triggered, it failed when it tried to deploy the project's POM, the first item that is deployed in the build process. I get the following error message: [INFO] Retrieving previous build number from inhouse_snapshot [FATAL ERROR] org.apache.maven.plugin.deploy.DeployMojo#execute() caused a linkage error (java.lang.AbstractMethodError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-deploy-plugin] urls[0] = file:/C:/Documents and Settings/Administrator/.m2/repository/org/apache/maven/plugins/maven-dep loy-plugin/2.3/maven-deploy-plugin-2.3.jar urls[1] = file:/C:/Documents and Settings/Administrator/.m2/repository/org/codehaus/plexus/plexus-utils/1 .1/plexus-utils-1.1.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/C:/Program Files/Apache Software Foundation/maven-2.0/bin/../lib/maven-2.0.9-uber.jar [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection()V [INFO] [DEBUG] Trace java.lang.AbstractMethodError: org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection()V at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(Defa ultWagonManager.java:435) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadat aFromDeploymentRepository(DefaultWagonManager.java:379) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM anager.getArtifactMetadataFromDeploymentRepository(DefaultRepositoryMeta dataManager.java:380) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM anager.resolveAlways(DefaultRepositoryMetadataManager.java:348) at org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatest SnapshotBuildNumber(SnapshotTransformation.java:161) at org.apache.maven.artifact.transform.SnapshotTransformation.transformForD eployment(SnapshotTransformation.java:100) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager .transformForDeployment(DefaultArtifactTransformationManager.java:78) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul tArtifactDeployer.java:71) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:152) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
-U
Hi All, From the maven command line help : -U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories Does this actually work with released artifacts ? I don't seem to be able to force an update of a released artefact. Thanks in advance Jon This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
Re: need help on maven compile phase.
The general concept with Maven would be that you should divide your code up into modules along whatever lines that make sense to you (1 module per pkg may be reasonable for your specific implementation, I suppose). Then you set up dependencies between the modules via each one's pom.xml file, and perhaps establish a parent which encompasses all modules. This would be set up like: parent/pom.xml parent/pkg1/pom.xml parent/pkg1/src/main/java/com/abc/xyz/pkg1 parent/pkg2/pom.xml parent/pkg1/src/main/java/com/abc/xyz/pkg2 parent/pkg3/pom.xml parent/pkg1/src/main/java/com/abc/xyz/pkg3 parent/pkg4/pom.xml parent/pkg1/src/main/java/com/abc/xyz/pkg4 So you would have probably 5 pom.xml files if you implemented this. You should do some reading (Better Builds With Maven etc) and look at sample projects (many open-source projects use Maven, and you can browse their code repositories to see how things are laid out and check out their pom.xml files) to see how this might apply to your specific situation. Wayne On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: I tried increasing the memory using the maxmem and memintial, initial=512mb and mac=2048m. still the same error. my 1642 files have been distributed accross four packages. src/main/java/com/abc/xyz/pkg1 pkg2 pkg3 pkg4 whould i write seperate POMs for each pkg? where should these POMs be present. then what about the main POM in the prj_home/dir? On 6/17/08, RAM [EMAIL PROTECTED] wrote: Actually, I can think of seperate module inside the main root project and a seperate pom.xml for each one. Then you can build those one by one. Else, try increasing the memory with the compiler plugin (I think, you have atleast 1.5 GB RAM) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration meminitial512m/meminitial maxmem1024m/maxmem /configuration /plugin This may resolve the out of memory error. Regards, Ram On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want -- Thanks Ram -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: need help on maven compile phase.
The easiest way is to split your sources into separate maven modules. If you have 1600 classes, this imho makes sense anyway! I (personally) mean, if a project is _that_ fat, then a modularisation would help to better understand the whole application. Each modules should have their own unit tests, etc. Simply, the whole bunch of straight forward computer engineering rules one learns in university. LieGrü, strub --- Niranjan Deshpande [EMAIL PROTECTED] schrieb am Di, 17.6.2008: Von: Niranjan Deshpande [EMAIL PROTECTED] Betreff: Re: need help on maven compile phase. An: Maven Users List users@maven.apache.org Datum: Dienstag, 17. Juni 2008, 14:46 I tried increasing the memory using the maxmem and memintial, initial=512mb and mac=2048m. still the same error. my 1642 files have been distributed accross four packages. src/main/java/com/abc/xyz/pkg1 pkg2 pkg3 pkg4 whould i write seperate POMs for each pkg? where should these POMs be present. then what about the main POM in the prj_home/dir? On 6/17/08, RAM [EMAIL PROTECTED] wrote: Actually, I can think of seperate module inside the main root project and a seperate pom.xml for each one. Then you can build those one by one. Else, try increasing the memory with the compiler plugin (I think, you have atleast 1.5 GB RAM) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration meminitial512m/meminitial maxmem1024m/maxmem /configuration /plugin This may resolve the out of memory error. Regards, Ram On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want -- Thanks Ram -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: -U
Released artifacts are never updated. If you are pushing updates to released artifacts, you will break your Maven builds in horrible, ugly, nasty, indeterminate ways. Unless you are talking about a new VERSION of a released artifact. Which is it? Wayne On 6/17/08, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: Hi All, From the maven command line help : -U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories Does this actually work with released artifacts ? I don't seem to be able to force an update of a released artefact. Thanks in advance Jon This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: -U
Unfortunately - its updates to released versions. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: 17 June 2008 14:56 To: Maven Users List Subject: Re: -U Released artifacts are never updated. If you are pushing updates to released artifacts, you will break your Maven builds in horrible, ugly, nasty, indeterminate ways. Unless you are talking about a new VERSION of a released artifact. Which is it? Wayne On 6/17/08, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: Hi All, From the maven command line help : -U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories Does this actually work with released artifacts ? I don't seem to be able to force an update of a released artefact. Thanks in advance Jon This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom.
Re: -U
Unless we are talking about snapshots, that will never, ever work and it is a very poor practice. But I am using xyz-1.2.jar! Why is yours working and mine isn't? Wayne On 6/17/08, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: Unfortunately - its updates to released versions. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: 17 June 2008 14:56 To: Maven Users List Subject: Re: -U Released artifacts are never updated. If you are pushing updates to released artifacts, you will break your Maven builds in horrible, ugly, nasty, indeterminate ways. Unless you are talking about a new VERSION of a released artifact. Which is it? Wayne On 6/17/08, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: Hi All, From the maven command line help : -U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories Does this actually work with released artifacts ? I don't seem to be able to force an update of a released artefact. Thanks in advance Jon This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This email is from Elsevier Limited, a company registered in England and Wales with company number 1982084, whose registered office is The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: -U
On Tue, Jun 17, 2008 at 6:28 AM, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: From the maven command line help : -U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories Does this actually work with released artifacts ? I don't seem to be able to force an update of a released artefact. Released artifacts should never change, so there's no reason to update them. (However, if you change the update policy for your releases repository, you can probably get it to happen.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generating PMD/CPD metrics for test code
Hi, I am unable to generate PMD/CPD metrics for a test suite as part of a multi-module build. The parent pom pulls version 2.3 of the PMD plugin and sets the includeTests setting to true. The PMD and CPD reports are generated but do not include the test metrics. However if I generate a site from within the module that contains the tests then I do get the required metrics but not when executed via the parent pom. One possible factor is that the test suite is controlled via a profile but as the tests are running I presume that the profile is being triggered correctly Anyone any ideas? -- Robert
Re: -U
On Tue, Jun 17, 2008 at 9:59 AM, SlinnHawkins, Jon (ELS-CAM) [EMAIL PROTECTED] wrote: Unfortunately - its updates to released versions. Well, as long as you recognize this isn't a particularly good idea and may have all sorts of unintended side effects, the simplest action is to clear the old jars out of your local repo, forcing Maven to look for them. - Geoffrey -- Geoffrey Wiseman
Disabling a plugin bound to a phase
Hi, We have a multiproject which contains both war and jar projects. I would like (in a profile) to disable the war projects from building their wars - as it takes ages and we only need them now and then. Is this possible? So I want to run mvn install -PnoWars At the parent and get all the jars built but not the wars. Thanks Ben Gidley
'Badly formed maven project' - Parent tag specified but no pom being pulled into org/jboss/seam/root of local repository.
Hi, I have defined a parent tag within my pom which, because no root pom is being pulled into org/jboss/seam/root in my repository, is throwing a 'Badly formed maven project' error, using Netbeans 6.1, in relation to the groupId and unspecified versions in the defined dependencies. What is the issue here? My dev platform is: Win XP SP1 Maven 2.0.9 JDK1.6.0_06 The pom in question is: [code] project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.mycompany.app/groupId artifactIdmycompany-seam-app/artifactId packagingpom/packaging version1.0-SNAPSHOT/version namemycompany-seam-app/name urlhttp://snapshots.jboss.org/maven2/url repositories repository idjboss-snapshot/id nameThe JBoss Maven Repo/name urlhttp://snapshots.jboss.org/maven2/url /repository /repositories parent groupIdorg.jboss.seam/groupId artifactIdroot/artifactId version2.0.3-SNAPSHOT/version /parent dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId scopeprovided/scope /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId scopetest/scope /dependency /dependencies modules moduleejb/module modulewar/module moduleear/module /modules build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /build /project [/code] Many thanks in advance. -- Regards Andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URLs in site.xml banner tags not rendered by site plugin if host not resolved by nslookup
Paul Spencer wrote: The URL's in the banner tags of site.xml are the maven-site-plugin is the hostname is not found by nslookup. In my case the hostname only exists in my hosts files on a the Windows machine running mvn site. The above should be: Absolute URL's in the banner tags of site.xml are translated to relative URLs by the maven-site-plugin when the hostname is not found by nslookup. In my case the hostname only exists in my hosts files on a the Windows machine running mvn site. Should I file an JIRA as bug or improvement? In the example below, the generated URLs for bannerLeft will be absolute and the URL's for bannerRight will be relative. Adding badhost.apache.org to the hosts file will not change the outcome. ?xml version=1.0 encoding=ISO-8859-1? project name=Maven bannerLeft nameMaven/name srchttp://maven.apache.org/images/apache-maven-project.png/src hrefhttp://maven.apache.org//href /bannerLeft bannerRight nameMaven/name srchttp://badhost.apache.org/images/apache-maven-project.png/src hrefhttp://badhost.apache.org//href /bannerRight /project It appears the plugin is validating the hostname. Is their a way of turning this validation off? Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can't pass -Denv=dev to scm:bootstrap goal
Greetings,
In a POM, I'm displaying the value of the env variable:
project
.
build
plugins
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseverify/phase
configuration
tasks
echo message=env: ${env}/
/tasks
/configuration
/execution
/executions
/plugin
.
/plugins
/build
...
/project
When running: mvn -Denv=dev, the displayed line is env: dev as expected.
But if I run it: mvn -Denv=dev scm:bootstrap -DconnectionUrl=...
-Dgoals=..., the display is env: ${env}. As if the -Denv=dev hasn't
given on the command line. Of course, I tried also: mvn scm:bootstrap
-Denv=dev -DconnectionUrl=... -Dgoals=... but the result is the same.
Please help !
Many thanks in advance.
Nicolas
--
View this message in context:
http://www.nabble.com/Can%27t-pass-%22-Denv%3Ddev%22-to-scm%3Abootstrap-goal-tp17912903p17912903.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disabling a plugin bound to a phase
I would probably set that up as follows: Default profile (in parent pom) only specifies modules which are jars War profile specifies all modules, jars and wars When you want a jar-only build, you just execute mvn install at the parent. When you want wars too, you execute mvn install -Dpluswars at the parent. Wayne On 6/17/08, Ben Gidley [EMAIL PROTECTED] wrote: Hi, We have a multiproject which contains both war and jar projects. I would like (in a profile) to disable the war projects from building their wars - as it takes ages and we only need them now and then. Is this possible? So I want to run mvn install -PnoWars At the parent and get all the jars built but not the wars. Thanks Ben Gidley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: need help on maven compile phase.
there are indeed seperate test classes for all those packages. but what i m not understanding is how do i write seperate poms for each pakage. and where do i kep that pom? and how do i call it? right now I am using one pom in the prj_home dir. On 6/17/08, Mark Struberg [EMAIL PROTECTED] wrote: The easiest way is to split your sources into separate maven modules. If you have 1600 classes, this imho makes sense anyway! I (personally) mean, if a project is _that_ fat, then a modularisation would help to better understand the whole application. Each modules should have their own unit tests, etc. Simply, the whole bunch of straight forward computer engineering rules one learns in university. LieGrü, strub --- Niranjan Deshpande [EMAIL PROTECTED] schrieb am Di, 17.6.2008: Von: Niranjan Deshpande [EMAIL PROTECTED] Betreff: Re: need help on maven compile phase. An: Maven Users List users@maven.apache.org Datum: Dienstag, 17. Juni 2008, 14:46 I tried increasing the memory using the maxmem and memintial, initial=512mb and mac=2048m. still the same error. my 1642 files have been distributed accross four packages. src/main/java/com/abc/xyz/pkg1 pkg2 pkg3 pkg4 whould i write seperate POMs for each pkg? where should these POMs be present. then what about the main POM in the prj_home/dir? On 6/17/08, RAM [EMAIL PROTECTED] wrote: Actually, I can think of seperate module inside the main root project and a seperate pom.xml for each one. Then you can build those one by one. Else, try increasing the memory with the compiler plugin (I think, you have atleast 1.5 GB RAM) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration meminitial512m/meminitial maxmem1024m/maxmem /configuration /plugin This may resolve the out of memory error. Regards, Ram On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want -- Thanks Ram -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want
relativePath in parent section, if modules in different VOBs
Hi, actually we have 2 ClearCase VOBs (databases) - one for the test-team, the other for developement. Both maven builds should use the same company-parent pom.xml: parent groupIdcom.mycompany/groupId artifactIdglobal-parent/artifactId version1.9.4/version !-- TODO how to define if in different VOB?-- relativePath../pom.xml/relativePath /parent This works fine, because the parent is referenced via its version But what about the relativePath? How can I setup a relative path, if the parent resides in a different ClearCase VOB? Thanx, Torsten
configuring a plugin.
I want to use the javadoc goal of the maven-javadoc-plugin. But I want to run it in three different ways 1. generate a .properties file from a source java file, using a custom doclet. My doclet expects 3 command line parameters. 2. generate javadoc for all other java files (excluding the java files of step1) So I want to run the goal javadoc, two times, but with different configuartion. I know that once needs to use the executions, execution, tasks, configuration, but I want to know what should be the order of these? executions executiongoals and tasks go here/execution configurationthis needs to be written twice /configuration /executions bu i get a parse error. maven expects a executions inside a configuration Also how do i pass command line parameter values to my doclet. With ANT, this was a paramname, value pair passed. But iwth maven we have additionalparam elemnt. where will te param value go? -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want
RE: relativePath in parent section, if modules in different VOBs
Hi Torsten,
I have faced a similar situation and unfortunately have not come up with
a silver bullet solution. I too would be interested if anyone else
has one. Fortunately for us, so far all of our projects that use maven
are small enough that we can put all modules in a single
(multi-component) VOB. However, I'm sure the day will come where we
need to work in a multi-module project across VOBs, so I've put some
thought into it.
I assume that the issue arises because your VOB tags are not the same in
your Unix region(s) as in your Windows region(s). Obviously one option
would be to make the VOB tags all the same (e.g. /vobs/my_vob and
\my_vob), but this is not always possible. If it's not, the only other
thing I can suggest is to use properties to define the relative path to
the VOB roots; the properties would be defined in profiles that are
activated based on OS family. For example:
...
profiles
profile
idunix_vobs/id
activation
os
familyunix/family
/os
/activation
properties
my_vob../../my/vob/my_vob
/properties
/profile
profile
idwindows_vobs/id
activation
os
familywindows/family
/os
/activation
properties
my_vob../my_vob/my_vob
/properties
/profile/profiles
...
Then in your POM define the path as such:
relativePath${my_vob}/relativePath
You could also activate the profile based on the presence of a 'file'
(i.e. the VOB root); I don't see any advantage/disadvantage of doing it
one way or the other.
Hope this helps!
Doron
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: June 17, 2008 11:17
To: users@maven.apache.org
Subject: relativePath in parent section, if modules in different VOBs
Hi,
actually we have 2 ClearCase VOBs (databases) - one for the test-team,
the other for developement.
Both maven builds should use the same company-parent pom.xml:
parent
groupIdcom.mycompany/groupId
artifactIdglobal-parent/artifactId
version1.9.4/version
!-- TODO how to define if in different VOB?--
relativePath../pom.xml/relativePath
/parent
This works fine, because the parent is referenced via its version But
what about the relativePath?
How can I setup a relative path, if the parent resides in a different
ClearCase VOB?
Thanx, Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mvn eclipse plugin -- Too many files (linux)
I have added the two elements to the pom (downloadSources and downloadJavadocs), the eclipse:eclipse goal does not run to completion and errors out after 6 minutes or so. It says there are too many open files. I knew I had seen this error before and it is because there is a limit of total number of files a user/shell can open. I will have to manually increase the FD's for the system/user/shell . Is there any fix for this apart from tweaking the linux kernel parameters i.e. could I tell maven to not open more than a certain number of files? -- Karan Singh Malhi
RE: need help on maven compile phase.
You have to restructure your project. Like: module-name-pkg1/src/main/java/com/abc/xyz/pkg1 module-name-pkg1/src/test/java/com/abc/xyz/pkg1 module-name-pkg1/pom.xml module-name-pkg2/src/main/java/com/abc/xyz/pkg2 module-name-pkg2/src/test/java/com/abc/xyz/pkg2 module-name-pkg2/pom.xml module-name-pkg3/src/main/java/com/abc/xyz/pkg3 module-name-pkg3/src/test/java/com/abc/xyz/pkg3 module-name-pkg3/pom.xml module-name-pkg4/src/main/java/com/abc/xyz/pkg4 module-name-pkg4/src/test/java/com/abc/xyz/pkg4 module-name-pkg4/pom.xml pom.xml The aggregate pom (now your main pom) should contain a modules section, like: modules modulemodule-name-pkg1/module modulemodule-name-pkg2/module modulemodule-name-pkg3/module modulemodule-name-pkg4/module /modules After that you would want your dependencyManagement in your aggregate pom and add a parent section to your module pom files. Then strip all version numbers in the dependencies section in your module poms and add them to the dependencyManagement section. All in all, a fairly big refactoring, but take a good look at the book at sonatype. All the elements are explained there. Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl -Original Message- From: Niranjan Deshpande [mailto:[EMAIL PROTECTED] Sent: Tue 6/17/2008 17:13 To: Maven Users List Subject: Re: need help on maven compile phase. there are indeed seperate test classes for all those packages. but what i m not understanding is how do i write seperate poms for each pakage. and where do i kep that pom? and how do i call it? right now I am using one pom in the prj_home dir. On 6/17/08, Mark Struberg [EMAIL PROTECTED] wrote: The easiest way is to split your sources into separate maven modules. If you have 1600 classes, this imho makes sense anyway! I (personally) mean, if a project is _that_ fat, then a modularisation would help to better understand the whole application. Each modules should have their own unit tests, etc. Simply, the whole bunch of straight forward computer engineering rules one learns in university. LieGrü, strub --- Niranjan Deshpande [EMAIL PROTECTED] schrieb am Di, 17.6.2008: Von: Niranjan Deshpande [EMAIL PROTECTED] Betreff: Re: need help on maven compile phase. An: Maven Users List users@maven.apache.org Datum: Dienstag, 17. Juni 2008, 14:46 I tried increasing the memory using the maxmem and memintial, initial=512mb and mac=2048m. still the same error. my 1642 files have been distributed accross four packages. src/main/java/com/abc/xyz/pkg1 pkg2 pkg3 pkg4 whould i write seperate POMs for each pkg? where should these POMs be present. then what about the main POM in the prj_home/dir? On 6/17/08, RAM [EMAIL PROTECTED] wrote: Actually, I can think of seperate module inside the main root project and a seperate pom.xml for each one. Then you can build those one by one. Else, try increasing the memory with the compiler plugin (I think, you have atleast 1.5 GB RAM) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration meminitial512m/meminitial maxmem1024m/maxmem /configuration /plugin This may resolve the out of memory error. Regards, Ram On 6/17/08, Niranjan Deshpande [EMAIL PROTECTED] wrote: Hi all My prj_home_dir/src/main/java has about 1642 classes. When Maven executes the compile life cycle, all tha 1642 classes are compiled at once and i always get a out of memory error. Is there a way that i can instruct maven to compile in steps. e.g web layer first, then the business layer etc. Please guide. -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want -- Thanks Ram -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Regards, Niranjan Deshpande Shut yourself from the world and create the reality you want
RE: Can't pass -Denv=dev to scm:bootstrap goal
Is this a good time to bring up a potential name conflict between maven
convention and ant's use of 'env'?
eg: property environment=env/
provides all environment variables as Ant properties prefixed by env.
-Original Message-
From: nicolas.duminil [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 7:59 AM
To: users@maven.apache.org
Subject: Can't pass -Denv=dev to scm:bootstrap goal
Greetings,
In a POM, I'm displaying the value of the env variable:
project
.
build
plugins
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseverify/phase
configuration
tasks
echo message=env: ${env}/
/tasks
/configuration
/execution
/executions
/plugin
.
/plugins
/build
...
/project
When running: mvn -Denv=dev, the displayed line is env: dev as expected.
But if I run it: mvn -Denv=dev scm:bootstrap -DconnectionUrl=... -Dgoals=...,
the display is env: ${env}. As if the -Denv=dev hasn't given on the command
line. Of course, I tried also: mvn scm:bootstrap -Denv=dev -DconnectionUrl=...
-Dgoals=... but the result is the same.
Please help !
Many thanks in advance.
Nicolas
--
View this message in context:
http://www.nabble.com/Can%27t-pass-%22-Denv%3Ddev%22-to-scm%3Abootstrap-goal-tp17912903p17912903.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incorporating DLL's into Maven Project.
I have followed the steps, and I am now getting the following error message
when I try to package my project:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to create assembly: Error adding file-set for
'org.git.systems:Cur
vi:dll:1.0.0' to archive: Error adding archived file-set.
PlexusIoResourceCollec
tion not found for: C:\Documents and
Settings\Mikel\.m2\repository\org\git\syste
ms\Curvi\1.0.0\Curvi-1.0.0.dll
No such archiver: 'dll'.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 seconds
[INFO] Finished at: Tue Jun 17 14:18:20 ADT 2008
[INFO] Final Memory: 12M/25M
[INFO]
Basically, I manually deployed the two dll's to Maven's repository (via mvn
install:install-file) and then made the following changes to my pom:
...
dependency
groupIdorg.git.systems/groupId
artifactIdCurvi/artifactId
version1.0.0/version
scopecompile/scope
typedll/type
/dependency
dependency
groupIdorg.git.systems/groupId
artifactIdOptimizedSolver/artifactId
version1.0.0/version
scopecompile/scope
typedll/type
/dependency
...
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy/id
phasepackage/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdorg.git.systems/groupId
artifactIdCurvi/artifactId
version1.0.0/version
typedll/type
overWritetrue/overWrite
outputDirectory/testingDLL/outputDirectory
destFileNameCurvi/destFileName
/artifactItem
/artifactItems
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
Is there something I did wrong along the process?
Thanks, I can't wait to get this to work.
On Tue, Jun 17, 2008 at 08:12, Mikel Cármenes Cavia [EMAIL PROTECTED]
wrote:
I will give those steps a shot today and let you all know if I run into any
problems. It sounds like a pretty logical thing to do actually, and
fortunately I do not require cross-platform compilation and support at this
point.
One quick question though, when you say that I should use the dependency
plugin to copy the DLL's to the target directory or other suitable location,
could I specify that the DLL's be put inside the jar? (that is, in the
resources folder).
Thanks!
On Mon, Jun 16, 2008 at 15:37, Kalle Korhonen [EMAIL PROTECTED]
wrote:
If you don't need to worry about cross-platform compilation support (and
sounds like you don't), the most straight-forwarded way to do this is to
deploy your dll to a Maven repository with type dll, declare a
straight-up
dependency to it in your pom and then use the dependency plugin to copy
the
lib to the target dir or other suitable location for development
environment
and structure you assembly (or whatever is the format of the actual
delivery) similarly. If cross-platform support is desired, nar plugin (
http://java.freehep.org/freehep-nar-plugin/intro.html) is a bit more
involving but simplifies things greatly. However, using it requires some
code changes.
Kalle
On Mon, Jun 16, 2008 at 11:19 AM, Mikel Cármenes Cavia [EMAIL PROTECTED]
wrote:
Hey guys,
I need to include three DLL's in my Maven project. Prior to deciding to
email the list, I have looked around the archives, and haven't been able
to
find anything that would seem to answer my problem (which is a very easy
one
in nature).
I use JNA to interface with two of the three DLL's (the third one is for
Jacob, and its location needs to be set as a system variable).
In Java, I do the following:
URL libURL = this.getClass().getResource(/org/git/systems/DLLs/);
System.setProperty(jna.library.path, libURL.getPath());
And then declare the following interface
public interface CurviLibrary extends Library {
CurviLibrary CurviInitialization = (CurviLibrary)
Native.loadLibrary(Curvi,CurviLibrary.class);
CurviLibrary OptimizedSolver = (CurviLibrary)
Native.loadLibrary(OptimizedSolver,CurviLibrary.class);
DoubleByReference GIT_CURVIG(float[] timeData, float[] rawData, float[]
relax, int rawDataSize, double alphaValue,
long numberOfBins);
}
So when compiled via Eclipse, this works like a charm. I have tried
placing
the DLL's within /main/resources/org/git/systems/DLLs but this does
Re: Incorporating DLL's into Maven Project.
I'm guessing you didn't install the dll with the packaging type dll (use -Dpackaging=dll, the default is jar - http://maven.apache.org/plugins/maven-deploy-plugin/usage.html). Check your local repository and the pom for the dll. Regarding your earlier question, you sure can package it into a jar and JNA's supposed to extract it out from the jar automatically if not found on library path but that was exactly your original problem: either it wasn't working or java.library.path wasn't set properly. Even with JNA, it's recommended practice to have the library in an accessible location on the system ( https://jna.dev.java.net/javadoc/com/sun/jna/Native.html#loadLibrary(java.lang.String,%20java.lang.Class)) Kalle On Tue, Jun 17, 2008 at 10:23 AM, Mikel Cármenes Cavia [EMAIL PROTECTED] wrote: I have followed the steps, and I am now getting the following error message when I try to package my project: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to create assembly: Error adding file-set for 'org.git.systems:Cur vi:dll:1.0.0' to archive: Error adding archived file-set. PlexusIoResourceCollec tion not found for: C:\Documents and Settings\Mikel\.m2\repository\org\git\syste ms\Curvi\1.0.0\Curvi-1.0.0.dll No such archiver: 'dll'. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Tue Jun 17 14:18:20 ADT 2008 [INFO] Final Memory: 12M/25M [INFO] Basically, I manually deployed the two dll's to Maven's repository (via mvn install:install-file) and then made the following changes to my pom: ... dependency groupIdorg.git.systems/groupId artifactIdCurvi/artifactId version1.0.0/version scopecompile/scope typedll/type /dependency dependency groupIdorg.git.systems/groupId artifactIdOptimizedSolver/artifactId version1.0.0/version scopecompile/scope typedll/type /dependency ... ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy/id phasepackage/phase goals goalcopy/goal /goals configuration artifactItems artifactItem groupIdorg.git.systems/groupId artifactIdCurvi/artifactId version1.0.0/version typedll/type overWritetrue/overWrite outputDirectory/testingDLL/outputDirectory destFileNameCurvi/destFileName /artifactItem /artifactItems /configuration /execution /executions /plugin /plugins /build /project Is there something I did wrong along the process? Thanks, I can't wait to get this to work. On Tue, Jun 17, 2008 at 08:12, Mikel Cármenes Cavia [EMAIL PROTECTED] wrote: I will give those steps a shot today and let you all know if I run into any problems. It sounds like a pretty logical thing to do actually, and fortunately I do not require cross-platform compilation and support at this point. One quick question though, when you say that I should use the dependency plugin to copy the DLL's to the target directory or other suitable location, could I specify that the DLL's be put inside the jar? (that is, in the resources folder). Thanks! On Mon, Jun 16, 2008 at 15:37, Kalle Korhonen [EMAIL PROTECTED] wrote: If you don't need to worry about cross-platform compilation support (and sounds like you don't), the most straight-forwarded way to do this is to deploy your dll to a Maven repository with type dll, declare a straight-up dependency to it in your pom and then use the dependency plugin to copy the lib to the target dir or other suitable location for development environment and structure you assembly (or whatever is the format of the actual delivery) similarly. If cross-platform support is desired, nar plugin ( http://java.freehep.org/freehep-nar-plugin/intro.html) is a bit more involving but simplifies things greatly. However, using it requires some code changes. Kalle On Mon, Jun 16, 2008 at 11:19 AM, Mikel Cármenes Cavia [EMAIL PROTECTED] wrote: Hey guys, I need to include three DLL's in my Maven project. Prior to deciding to email the list, I have looked around the archives, and haven't been able to find anything that would seem to answer my problem (which is a very easy one in nature).
Re: Incorporating DLL's into Maven Project.
Kalle, I have made sure to carefully deploy the dll's to my repository, with the appropriate packaging parameters and all. Initially I was using mvn install:install-file, I now use mvn deploy:deploy-file, and when I look inside the repository, it all seems to be there, and it looks to be correct. The problem I am having is still at the packaging stage, with the error handling file set... and the PlexusIoResourceCollection not found. This is the same error I had before. It also says no such archiver dll. Does my pom look good to you? (I don't wanna clutter pasting it all again, the pom and error are in the previous message). Thanks for your help. Mikel On Tue, Jun 17, 2008 at 15:14, Kalle Korhonen [EMAIL PROTECTED] wrote: I'm guessing you didn't install the dll with the packaging type dll (use -Dpackaging=dll, the default is jar - http://maven.apache.org/plugins/maven-deploy-plugin/usage.html). Check your local repository and the pom for the dll. Regarding your earlier question, you sure can package it into a jar and JNA's supposed to extract it out from the jar automatically if not found on library path but that was exactly your original problem: either it wasn't working or java.library.path wasn't set properly. Even with JNA, it's recommended practice to have the library in an accessible location on the system ( https://jna.dev.java.net/javadoc/com/sun/jna/Native.html#loadLibrary(java.lang.String,%20java.lang.Class) ) Kalle On Tue, Jun 17, 2008 at 10:23 AM, Mikel Cármenes Cavia [EMAIL PROTECTED] wrote: I have followed the steps, and I am now getting the following error message when I try to package my project: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to create assembly: Error adding file-set for 'org.git.systems:Cur vi:dll:1.0.0' to archive: Error adding archived file-set. PlexusIoResourceCollec tion not found for: C:\Documents and Settings\Mikel\.m2\repository\org\git\syste ms\Curvi\1.0.0\Curvi-1.0.0.dll No such archiver: 'dll'. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Tue Jun 17 14:18:20 ADT 2008 [INFO] Final Memory: 12M/25M [INFO] Basically, I manually deployed the two dll's to Maven's repository (via mvn install:install-file) and then made the following changes to my pom: ... dependency groupIdorg.git.systems/groupId artifactIdCurvi/artifactId version1.0.0/version scopecompile/scope typedll/type /dependency dependency groupIdorg.git.systems/groupId artifactIdOptimizedSolver/artifactId version1.0.0/version scopecompile/scope typedll/type /dependency ... ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy/id phasepackage/phase goals goalcopy/goal /goals configuration artifactItems artifactItem groupIdorg.git.systems/groupId artifactIdCurvi/artifactId version1.0.0/version typedll/type overWritetrue/overWrite outputDirectory/testingDLL/outputDirectory destFileNameCurvi/destFileName /artifactItem /artifactItems /configuration /execution /executions /plugin /plugins /build /project Is there something I did wrong along the process? Thanks, I can't wait to get this to work. On Tue, Jun 17, 2008 at 08:12, Mikel Cármenes Cavia [EMAIL PROTECTED] wrote: I will give those steps a shot today and let you all know if I run into any problems. It sounds like a pretty logical thing to do actually, and fortunately I do not require cross-platform compilation and support at this point. One quick question though, when you say that I should use the dependency plugin to copy the DLL's to the target directory or other suitable location, could I specify that the DLL's be put inside the jar? (that is, in the resources folder). Thanks! On Mon, Jun 16, 2008 at 15:37, Kalle Korhonen [EMAIL PROTECTED] wrote: If you don't need to worry about cross-platform compilation support (and sounds like you don't), the most straight-forwarded way to do this is to deploy your dll to a Maven repository with type
Re: Question about why/when Maven will automatically exclude transitive dependencies.
A nice, thanks.. didn't even realize I could do that with that plugin. Thank! Hopefully that will tell me what is being excluded.. must be something indirect since I wouldn't exclude my own core dependencies. :) (or at least not intentionally). On Tue, Jun 17, 2008 at 4:45 AM, Julien Simon [EMAIL PROTECTED] wrote: Hi, If you want to see the list of dependencies and their scope for a POM, you could try mvn dependency:tree For further information on how to use the dependency plugin, have a look a this link ; http://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html On Tue, Jun 17, 2008 at 6:04 AM, Ryan Moquin [EMAIL PROTECTED] wrote: I guess when I think about it, this looks like a stupid question because it could easily be that I excluded a dependency somewhere which caused the problem. I positive that isn't the issue, but let's pretend it could be.. is there any way to get a list of dependencies and what status maven considers them in? Such as if they are excluded or included for whichever reasons? I'm not sure how to troubleshoot this.. all I know is that it was working a few days ago and I have no idea why all of a sudden my project seems to be so problematic.. just hoping someone might have some suggestions on how to troubleshoot this. Thanks! Ryan On Mon, Jun 16, 2008 at 12:14 PM, Ryan Moquin [EMAIL PROTECTED] wrote: I have never really been able to figure this out and it's really driving me up the wall at the moment. Is there a time that Maven2 will automatically exclude transitive dependencies? Here is the scenario: I have 2 projects, then both include the exact same dependency. When I build the first library, it builds perfectly fine. When I build the second library, it files during the unit tests with NoClassDefFoundErrors. If I look at the dependencies being included, Maven2 isn't including the same transitive dependencies from that common dependency between the two projects. Basically I have to include those transitive dependencies explicitly, which I don't want to do. What are the causes where Maven won't include compile dependencies that a first level dependency is dependant on? It seems very nondeterministic, so I'm guessing there are some nonobvious reason behind the scenes for how it calculates this. Thanks! Ryan
codehaus repos fried?
getting long hangs on both codehaus repos: http://snapshots.repository.codehaus.org/ http://repository.codehaus.org does anyone know of any mirror for these? tia, -Russ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: codehaus repos fried?
At 12:25 PM -0700 6/17/08, Russ Tremain wrote: getting long hangs on both codehaus repos: http://snapshots.repository.codehaus.org/ http://repository.codehaus.org does anyone know of any mirror for these? tia, -Russ as a temporary work-around, assuming you don't need to update anything, you can add this to your ~/.m2/settings.xml file: settings mirrors mirror idfake-codehaus-snapshots-mirror/id urlhttp://repo1.maven.org/maven2/url mirrorOfcodehaus-plugin-snapshots/mirrorOf /mirror mirror idfake-codehaus-mirror/id urlhttp://repo1.maven.org/maven2/url mirrorOfCodehaus/mirrorOf /mirror ... best to use your favorite mirror of central so as not to overload it... /r - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: codehaus repos fried?
Hi, It's back now. (http://jira.codehaus.org/browse/HAUS-1700). -- Olivier 2008/6/17 Russ Tremain [EMAIL PROTECTED]: At 12:25 PM -0700 6/17/08, Russ Tremain wrote: getting long hangs on both codehaus repos: http://snapshots.repository.codehaus.org/ http://repository.codehaus.org does anyone know of any mirror for these? tia, -Russ as a temporary work-around, assuming you don't need to update anything, you can add this to your ~/.m2/settings.xml file: settings mirrors mirror idfake-codehaus-snapshots-mirror/id urlhttp://repo1.maven.org/maven2/url mirrorOfcodehaus-plugin-snapshots/mirrorOf /mirror mirror idfake-codehaus-mirror/id urlhttp://repo1.maven.org/maven2/url mirrorOfCodehaus/mirrorOf /mirror ... best to use your favorite mirror of central so as not to overload it... /r - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to copy unpacked nar file contents into target directory?
Thanks for your help Brian. I'm afriad I'm not quite following your suggestion though. If I add the narUnArchiver dependency to the maven-dependency-plugin like so: plugin groupIdorg.freehep/groupId artifactIdfreehep-nar-plugin/artifactId executions execution iddownload-a-nar/id phasepackage/phase goals goalnar-download/goal goalnar-unpack/goal /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idunpack/id phasepackage/phase goals goalunpack/goal /goals configuration artifactItems artifactItem groupIdnarUnArchiver/groupId artifactIdnarUnArchiver/artifactId version0.1/version /artifactItem /artifactItems /configuration /execution /executions /plugin /plugins This results in the file component.xml (from narUnArchiver.jar) being unpacked in the target directory. I don't think this the desired result. What am I missing here? Thanks! Brian E Fox wrote: I then added the dependency tags as described in your blog post as follows: snip You need to add the dependency to the maven-dependency-plugin unpack execution --Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-to-copy-unpacked-nar-file-contents-into-target-directory--tp17834192p17957042.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Transitive dependency problem
Hi,
I'm having a problem where a project using the assembly plugin is
copying two versions of the jaxb-api jar (1.0.5 2.0) to the
WEB-INF/lib directory of a webapp the assembly is creating.
I tried using dependency management to explicitly specify to use version
2.0 like this:
dependencyManagement
dependencies
dependency
groupIdjavax.xml.bind/groupId
artifactIdjaxb-api/artifactId
version2.0/version
/dependency
/dependencies
/dependencyManagement
But it is still including version 1.0.5! I am using Maven 2.0.8 and
Assembly Plugin 2.1. I have also uncluded the projects pom.xml and
assembly dep.xml.
Thanks,
Matias.
assembly
idbin/id
formats
formattar.gz/format
/formats
dependencySets
!--
Unpack dependecy modules
--
dependencySet
outputDirectory/modules/thelma-core/outputDirectory
unpacktrue/unpack
scoperuntime/scope
includes
includeicsglobal:thelma-core/include
/includes
/dependencySet
dependencySet
outputDirectory/modules/thelma-mainapp/outputDirectory
unpacktrue/unpack
scoperuntime/scope
includes
includeicsglobal:thelma-mainapp/include
/includes
/dependencySet
!--
Create the WEBAPP
--
dependencySet
outputDirectorywebapp/ROOT/outputDirectory
unpacktrue/unpack
scoperuntime/scope
includes
includeicsglobal:thelma-us-web/include
/includes
/dependencySet
!-- This places all runtime libraries into the WEB-INF lib --
dependencySet
outputDirectorywebapp/ROOT/WEB-INF/lib/outputDirectory
unpackfalse/unpack
scoperuntime/scope
excludes
excludejavax.servlet:jsp-api/exclude
excludejavax.servlet:servlet-api/exclude
/excludes
/dependencySet
/dependencySets
fileSets
/fileSets
/assembly
project
modelVersion4.0.0/modelVersion
groupIdicsglobal/groupId
artifactIdthelma-us-assembly/artifactId
nameICSGlobal THELMA-US Assembly/name
version1.2-SNAPSHOT/version
urlx/url
packagingjar/packaging
repositories
repository
idcentral/id
nameICS Global Maven Repository/name
url/url
snapshots
enabledtrue/enabled
/snapshots
/repository
/repositories
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
id1/id
phaseprocess-resources/phase
goals
goalrun/goal
/goals
configuration
tasks
echo${project.version}/echo
/tasks
/configuration
/execution
/executions
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.1/version
configuration
descriptors
descriptorsrc/main/assembly/dep.xml/descriptor
/descriptors
/configuration
/plugin
/plugins
/build
dependencyManagement
dependencies
dependency
groupIdjavax.xml.bind/groupId
artifactIdjaxb-api/artifactId
version2.0/version
/dependency
/dependencies
/dependencyManagement
dependencies
dependency
groupIdicsglobal/groupId
artifactIdthelma-core/artifactId
version2.5-SNAPSHOT/version
/dependency
dependency
groupIdicsglobal/groupId
artifactIdthelma-mainapp/artifactId
version1.13/version
/dependency
dependency
groupIdicsglobal/groupId
artifactIdthelma-us-web/artifactId
version1.1-SNAPSHOT/version
/dependency
dependency
groupIdicsglobal/groupId
Re: Transitive dependency problem
On Tue, Jun 17, 2008 at 8:15 PM, Matias Otero [EMAIL PROTECTED] wrote: I'm having a problem where a project using the assembly plugin is copying two versions of the jaxb-api jar (1.0.5 2.0) to the WEB-INF/lib directory of a webapp the assembly is creating. My guess is that you're picking up jaxb-api from two different groupIds, and so Maven does not know they are the same. I can see jaxb-api listed in at least two groups: javax.xml and javax.xml.bind http://repo1.maven.org/maven2/javax/xml/jaxb-api http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api You can build with -X or use the dependency plugin to display all the information, and then you may need to use exclusions to get rid of the one you don't want. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Transitive dependency problem
Yes, I had a suspicion that was the problem when I saw the jaxb jars in multiple group Ids in the maven repository. I have fixed the problem now by adding exclusions in the assembly dep.xml file using the groupId javax.xml as that's where all the jaxb 1.x jars live. Thanks very much for your help. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 June 2008 1:31 PM To: Maven Users List Subject: Re: Transitive dependency problem On Tue, Jun 17, 2008 at 8:15 PM, Matias Otero [EMAIL PROTECTED] wrote: I'm having a problem where a project using the assembly plugin is copying two versions of the jaxb-api jar (1.0.5 2.0) to the WEB-INF/lib directory of a webapp the assembly is creating. My guess is that you're picking up jaxb-api from two different groupIds, and so Maven does not know they are the same. I can see jaxb-api listed in at least two groups: javax.xml and javax.xml.bind http://repo1.maven.org/maven2/javax/xml/jaxb-api http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api You can build with -X or use the dependency plugin to display all the information, and then you may need to use exclusions to get rid of the one you don't want. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Failing the build on dep convergence problems
This seems like a common/obvious request but a bit of googling didn't turn it up. At my work we're using the Dependency Convergence report to detect dependency conflicts. We'd like to fail the build if we don't have 100% dependency convergence on that report. I had hoped that I'd be able to do this using maven-dependency-plugin, but it's not obvious how to get it to do that. The analyze-dep-mgt is sort-of what I want, but not exactly, since I'm concerned about sibling conflicts as well as conflicts with the root POM's dependencyManagement section. (And anyway, I seem to be having problems with analyze-dep-mgt; when ignoreDirect is enabled it complains about dependency problems that I don't see in the Dependency Convergence report, and that don't show up with dependency:tree -Dverbose.) The Dependency Convergence report doesn't use maven-dependency-plugin, does it? How does it work? Can I make my build fail when that report says 100%? -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
location of application.xml?
I'm not sure when you put META-INF\application.xml. Does it go under src\main\resources or src\main\application? mvn eclipse:eclipse generates a source dir reference to src\main\application, and that is what it appears to need to be able to run the test app in the environment. However, although maven generates a correct application.xml (one that uses the correct version numbers from the war/ejb modules) it does not put it in the generated ear file - not if I use src\main\application. If I use src\main\application then it uses what is in the file system and not generate one. Which almost makes me take the approach of using both src\main\resources and src\main\application - yuk! Which is correct? -Chris ** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
