making a repository read-only
Hi all, I've got the requirement of providing different settings.xml files to different clients. Currently we've got different repositories: Third Party (TP), SNAPSHOTS and Releases. Each client has got different requirements. For instance, developers can only use all repositories as read-only, our CI environment can upload artifacts to the SNAPSHOT but have read-only access to TP and Releases while our build software can only upload to Releases but have read-only to TP and SNAPSHOTS. Is there a way to setup this kind of configuration via settings.xml or other elements inside a POM? So far it seems I couldn't find a way. Regards, M. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: making a repository read-only
No, we don't use Nexus, just the file system. We've got a single account (sys_account) who is entitled to upload to this repository through ssh using an infrastructure given key, so also the possibility to use multiple usernames/passwords doesn't seem feasable. Any other suggestions? Regards, M. On Tue, 2010-06-29 at 16:22 -0700, Manfred Moser wrote: Hi all, I've got the requirement of providing different settings.xml files to different clients. Currently we've got different repositories: Third Party (TP), SNAPSHOTS and Releases. Each client has got different requirements. For instance, developers can only use all repositories as read-only, our CI environment can upload artifacts to the SNAPSHOT but have read-only access to TP and Releases while our build software can only upload to Releases but have read-only to TP and SNAPSHOTS. Is there a way to setup this kind of configuration via settings.xml or other elements inside a POM? So far it seems I couldn't find a way. Just use different username/password combinations in your repository server with different access rights and use the different roles in pom.xml profiles and settings.xml. - 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 Meetup Locations
London, we've got good beer :-) On Mon, 2010-06-21 at 15:55 -0400, Jason van Zyl wrote: The Maven Meetups Sonatype puts on have been very popular in the past. We're starting to take input from users on where they should be in the future: Sonatype’s coming to a city near you Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Branch with Google guice?
Stuart, a couple of things re the below: 1) The first URL downloads spice-inject and the whole Guice. Question: was Guice extended for this compatibility layer? What actually is the compatibility layer? Is it just spice or the whole lot? If it's just spice, could we avoid from build the whole Guice and have the dependencies downloaded from the net? 2) The second URL points to a Maven repository. You were talking of a replacement container (which I thought of as being classworlds). However I was looking for the source code. To summarise, I'd like to have the URLs only to the source code needed to build Maven 3 with the Guice bit. I understand that there is a compatibility layer, and I can build that (after knowing if I have to build the whole Guice as well with it). I understand that there is a replacement container (but I don't have a precise URL to the SVN code for it); I'd like to know if the Maven 3 trunk builds already on top of the above, or if I need another URL with Guice support, and if this case I'd like a precise URL for it. Thanks for your time. M. On Sun, 2010-06-06 at 16:40 +0800, Stuart McCulloch wrote: On 6 June 2010 02:27, Jemos Infra jemos.in...@googlemail.com wrote: Hi, Can somebody point me to the Maven 3 branch with Google guice? I undertsand that Google guice will replace Plexus classworlds, but the trunk still has Plexus in it. I'd like to have a look at what Maven 3 will look like when finished (from a code perspective). The idea is for Guice to replace the Plexus container by using a compatibility layer to inject requirements into components. (Plexus classworlds is more about classloader isolation, which is orthogonal to injection and may or may not be replaced in the near future) The Plexus container compatibility layer is here: http://svn.sonatype.org/spice/trunk/spice-inject Note that because this supports Plexus components on top of Guice/JSR330 there's actually no changes needed to Maven 3 to run it on top of Guice - that's all handled by the compatibility layer, you can even mix JSR330 and Plexus components/annotations. Below is the patch to build M3 with the replacement container - note you'll need to build the spice-inject project beforehand, unless you use the Sonatype forge repository to get the latest snapshots: https://repository.sonatype.org/content/groups/forge Changing future plugins / Maven to use pure JSR330 annotations is a separate discussion that will happen on the dev list - first I need to write up our experience at Sonatype with using a JSR330 component model* so people have something concrete to discuss. [* apologies to the dev-list for delays in writing this up] HTH Index: maven-repository/pom.xml === --- maven-repository/pom.xml(revision 951813) +++ maven-repository/pom.xml(working copy) @@ -39,8 +39,8 @@ artifactIdmaven-compat/artifactId /dependency dependency - groupIdorg.codehaus.plexus/groupId - artifactIdplexus-container-default/artifactId + groupIdorg.sonatype.spice/groupId + artifactIdspice-inject-plexus/artifactId /dependency dependency groupIdorg.codehaus.plexus/groupId Index: apache-maven/pom.xml === --- apache-maven/pom.xml(revision 951813) +++ apache-maven/pom.xml(working copy) @@ -43,8 +43,8 @@ artifactIdmaven-compat/artifactId /dependency dependency - groupIdorg.codehaus.plexus/groupId - artifactIdplexus-container-default/artifactId + groupIdorg.sonatype.spice/groupId + artifactIdspice-inject-plexus/artifactId /dependency !-- CLI -- dependency Index: maven-compat/pom.xml === --- maven-compat/pom.xml(revision 951813) +++ maven-compat/pom.xml(working copy) @@ -53,8 +53,8 @@ artifactIdplexus-interpolation/artifactId /dependency dependency - groupIdorg.codehaus.plexus/groupId - artifactIdplexus-container-default/artifactId + groupIdorg.sonatype.spice/groupId + artifactIdspice-inject-plexus/artifactId /dependency dependency groupIdorg.codehaus.plexus/groupId Index: maven-model-builder/pom.xml === --- maven-model-builder/pom.xml(revision 951813) +++ maven-model-builder/pom.xml(working copy) @@ -41,8 +41,8 @@ artifactIdmaven-model/artifactId /dependency dependency - groupIdorg.codehaus.plexus/groupId - artifactIdplexus-container-default/artifactId + groupIdorg.sonatype.spice/groupId + artifactIdspice-inject-plexus/artifactId scopetest/scope /dependency /dependencies Index: pom.xml
Re: Branch with Google guice?
Stuart, thank you for your email. Do you think that future emails related to the process below (mainly if I found any difficulties in building the whole thing plus observations, suggestions, etc) should be addressed to the dev mailing list? M. On Sun, 2010-06-06 at 18:11 +0800, Stuart McCulloch wrote: On 6 June 2010 17:22, Jemos Infra jemos.in...@googlemail.com wrote: Stuart, a couple of things re the below: 1) The first URL downloads spice-inject and the whole Guice. Question: was Guice extended for this compatibility layer? What actually is the compatibility layer? Is it just spice or the whole lot? The first URL is the umbrella project that provides the compatibility layer - it contains a patched version of Guice because we needed to tweak and experiment with certain behavior during development, and handle some corner-cases wrt. Nexus Most changes have been committed into Guice trunk. There's only one patch left needed for Maven, which is the type converter feature and this should go in soon. (diff vanilla.src vs. src to see the remaining patches) We're still keeping our patched tree around for further experimentation / point-releases because Guice 2.1 has not yet been officially released - otherwise you'd need to download and build Guice from scratch too. spice-inject also contains various modules that provide classpath scanning and Plexus-like features on top of Guice - these modules are combined into the two main distro jars: spice-inject-bean and spice-inject-plexus for convenience sake. [ these are not going back into Guice as they're external extensions ] spice-inject-bean provides a component model on top of JSR330 (component scanning, dynamic collections) - see the examples module for, well, an example ;) spice-inject-plexus adds support for Plexus to replace the Plexus container in Maven3 you need: spice-inject-bean-1.2.1-SNAPSHOT.jar spice-inject-plexus-1.2.1-SNAPSHOT.jar guice-patches-2.1.4-SNAPSHOT-noaop.jar at least until the type converter patches go into Guice If it's just spice, could we avoid from build the whole Guice and have the dependencies downloaded from the net? if you just want to download the dependencies then add that second URL (the Sonatype Forge) as a snapshot repository in your settings.xml, apply the patch from the end of my original email to Maven 3 trunk, and do a build 2) The second URL points to a Maven repository. You were talking of a replacement container (which I thought of as being classworlds). However I was looking for the source code. for the new container source code see 1) ... specifically guice-bean / guice-plexus which form most of the code [ it's modular so there's no single project source tree ] also look at the example to see JSR330 in practice To summarise, I'd like to have the URLs only to the source code needed to build Maven 3 with the Guice bit. you already have it... build 1) and you have everything needed - as explained you still need the patch of Guice for now, but won't in the future or just use 2) to download the binary snapshots I understand that there is a compatibility layer, and I can build that (after knowing if I have to build the whole Guice as well with it). I understand that there is a replacement container (but I don't have a precise URL to the SVN code for it); I'd like to know if the Maven 3 trunk builds already on top of the above, or if I need another URL with Guice support, and if this case I'd like a precise URL for it. Maven 3 trunk still builds with Plexus at the moment, but if you take the patch from the bottom of my earlier email and apply it to Maven 3 then it will build with the new artifacts or just grab a snapshot build of Maven 3, remove the Plexus container jar and add the three artifacts listed above... Thanks for your time. M. On Sun, 2010-06-06 at 16:40 +0800, Stuart McCulloch wrote: On 6 June 2010 02:27, Jemos Infra jemos.in...@googlemail.com wrote: Hi, Can somebody point me to the Maven 3 branch with Google guice? I undertsand that Google guice will replace Plexus classworlds, but the trunk still has Plexus in it. I'd like to have a look at what Maven 3 will look like when finished (from a code perspective). The idea is for Guice to replace the Plexus container by using a compatibility layer to inject requirements into components. (Plexus classworlds is more about classloader isolation, which is orthogonal to injection and may or may not be replaced in the near future) The Plexus container compatibility layer is here: http://svn.sonatype.org/spice/trunk/spice-inject Note that because this supports Plexus components on top of Guice/JSR330 there's actually no changes needed to Maven 3 to run it on top of Guice - that's all handled by the compatibility layer, you can even mix
Re: Branch with Google guice?
On Sun, 2010-06-06 at 16:58 +0200, Olivier Lamy wrote: stuff is here : http://svn.apache.org/repos/asf/maven/maven-3/branches/guice-support/ Thanks ! Hi Oliver, I take it this branch contains everything that's needed, right? I mean Maven-3, the Plexus-Guice adapter and all required dependencies in the POM. Correct? Thanks. M. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3 and M2_HOME environment variable
Hi all, In Maven 3, will the Maven environment variable still be M2_HOME? Has this been done for backward compatibility? Regards, M. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Branch with Google guice?
Hi, Can somebody point me to the Maven 3 branch with Google guice? I undertsand that Google guice will replace Plexus classworlds, but the trunk still has Plexus in it. I'd like to have a look at what Maven 3 will look like when finished (from a code perspective). Thanks. M. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Integrating persistence (sub)module into web app
Dan, I don't understand the requirement here. Why would you need the persistence.xml file in the WEBAPP/meta-inf folder? Why not to have the webapp which includes the persistence module as a dependency, thus the persistence module will be placed under webapp/lib and the classes will be available in the classpath? On Thu, 2010-05-13 at 07:32 -0700, Dan King wrote: Hi all, How can I get maven to automatically copy (or move) my persistence.xml file from my persistence module's meta-inf directory to the web app's meta-inf directory? I have a persistence module that contains, among other things, entity classes and the persistence.xml file. I've stored the persistence.xml file in src/main/resources/meta-inf. When I build the app from the parent directory (directory that contains the parent pom), the persistence.xml file is NOT added to the META-INF directory of the web app. Also, since the persistence.xml file currently resides in the same jar as the entity classes, I do not need to specify them; if I move the persistence.xml file to the meta-inf directory I'd have to list the entities. Is there a way around this? Thanks. -Dan - 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: Automate build and test process in maven
Another way to test this is to create a WAR project, include your jar as dependency and use the jetty plugin. On Mon, 2010-05-10 at 20:16 -0700, AnshuGupta wrote: We are using Maven as the build automation tool. The build process generates a jar file. The requirement here is to start execution of the java application which will be generated by the build - Wait for a few seconds to let the application start completely and then move onto the test phase, which will perform start a test tool (SoapUI) that will issue soap calls against the java application that was just started. We tried using the exec plugin, to start the java application. However, when we moved onto the test phase, the java application terminated. Also, we couldn't figure out how to introduce a delay before the start of the soapUI tests. What will be the best way to achieve the above? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Advice: How do you setup your Maven project for Continuous Integration?
We use profiles per project and then setup integration test CI modules running those profiles. On Tue, 2010-05-11 at 13:03 +0930, Barrie Treloar wrote: I'm struggling to work out the best way to get my maven projects and continuous integration to play nicely together. Here's some background: Our build takes approximately 8 minutes to complete. To help keep the build time down the developers build doesn't do things like: * create source jars * create javadoc jars * run the integration test suite These extra tasks are all done when we release our software, or the integration tests suite can also be invoked via profiles. What I'd like to do is make sure that our continuous integration environment does these extra tasks. Ideally I'd like to define this once in our corporate parent pom and have it inherited. But profiles don't work this way (http://maven.apache.org/guides/introduction/introduction-to-profiles.html) It looks like the best I can do is to have a per-project profile (which I duplicate across all projects) at the root pom of the project to enable these extra tasks. I've also looked at the way maven development process enforces some common tasks during the release process. e.g. in org.apache:apache:7 pom uses plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration useReleaseProfilefalse/useReleaseProfile goalsdeploy/goals arguments-Papache-release/arguments /configuration /plugin and further down defines the profile profile idapache-release/id I have no idea how this actually manages to get that profile to run since help:effective-pom doesn't list it as a valid profile. So my question is how are you doing continuous integration? - 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: mvn goal site - not generating project info pages
Have a look at https://cwiki.apache.org/confluence/display/MAVEN/Maven +3.x+and+site+plugin Regards, M. On Sat, 2010-05-08 at 23:44 +0200, Ralph Soika wrote: Hi, after I upgraded my m2eclipse plugin to version 0.10 the maven command site:site did no longer process reports nor the maven-project-info-reports When I run the mvn site goal from my external maven2 installation the reports are created. Has anybody an idea what I do wrong? thanks for help ralph - 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 filter and hsqldb mem hibernate.hbm2ddl.auto
Stephane, the pom doesn't show any filtering / hibernate plugin. Regards, M. On Sun, 2010-05-09 at 11:03 -0700, Stephane Eybert wrote: Hello, I have a pom.xml file with a filter for some data source properties. The filter works for the data source properties, that is, for: hibernate.dialect=org.hibernate.dialect.HSQLDialect dataSource.driverClassName=org.hsqldb.jdbcDriver dataSource.url=jdbc:hsqldb:mem:testdb dataSource.username=sa dataSource.password= and my integration test is successful. But when having also the following property in the filter file hibernate.hbm2ddl.auto=create I get an error message saying the sql statement could not be performed because the table does not exist. What happens is that HSQLDB (in memory) does not create my table before running the test, if the hibernate.hbm2ddl.auto is in the filter file instead of being hard coded in the spring hibernate factory bean. But the property hibernate.dialect does not pose such a problem. It is happily replaced by the value in the filter file. I would like to have the property hibernate.hbm2ddl.auto being replaced by the value in the filter file, so as to have a different value, when running the integration test in HSQLDB (value should be create) and when running in production (value should be validate). http://old.nabble.com/file/p28504415/spring-hibernate.xml spring-hibernate.xml http://old.nabble.com/file/p28504415/data-source.properties data-source.properties http://old.nabble.com/file/p28504415/pom.xml pom.xml - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven filter and hsqldb mem hibernate.hbm2ddl.auto
I believe the following snippet (from
http://maven.apache.org/pom.html#Resources) could solve your situation:
resources
resource
targetPathMETA-INF/plexus/targetPath
filteringfalse/filtering
directory${basedir}/src/main/plexus/directory
includes
includeconfiguration.xml/include
/includes
excludes
exclude**/*.properties/exclude
/excludes
/resource
/resources
testResources
...
/testResources
From what you are saying it appears that filtering has not been applied to
test resources.
M.
On Sun, 2010-05-09 at 13:05 -0700, Stephane Eybert wrote:
Hi Jemos,
Thanks for your reply. But I wonder how come the file in the target
directory shows all the properties being filtered fine.
A look at the file core/target/classes/spring-hibernate.xml shows the
property place holders replaced by the corresponding values.
But a look at the file core/target/test-classes/spring-hibernate.xml shows
that the property place holders were NOT replaced.
So, the filtering works in a way that escapes me... It seems to filter
something, creating a filtered file at
core/target/classes/spring-hibernate.xml but not doing it for the file
core/target/test-classes/spring-hibernate.xml
What puzzles me is that I only run an integration test with the command:
mvn clean test -Pitest
Here are the generated files in the target directory, one in classes/
filtered fine and the other one in test-classes not filtered:
http://old.nabble.com/file/p28505207/spring-hibernate.xml
spring-hibernate.xml
http://old.nabble.com/file/p28505207/spring-hibernate.xml
spring-hibernate.xml
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven filter and hsqldb mem hibernate.hbm2ddl.auto
This is a snippet from your message: [quote] Thanks for your reply. But I wonder how come the file in the target directory shows all the properties being filtered fine. A look at the file core/target/classes/spring-hibernate.xml shows the property place holders replaced by the corresponding values. But a look at the file core/target/test-classes/spring-hibernate.xml shows that the property place holders were NOT replaced. [/quote] From what you wrote it seemed that you did not specify filtering for your test resources (hence only the src/main/resources were filtered and I suggested to you do declared the testResources element in your POM also giving you a link to a page which shows the syntax. Regards, M. On Sun, 2010-05-09 at 14:15 -0700, Stephane Eybert wrote: Hum... I wonder what you meant here.. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Manipulating the build's classpath programmatically (in a custom mojo)
I think this question was answered recently in the list and involved using extensions. http://maven.apache.org/guides/mini/guide-using-extensions.html Regards, M. On Thu, 2010-05-06 at 22:29 -0700, Alex Ruiz wrote: Greetings, I know this is not the Maven way, but I need to add a bunch of jars to a build's classpath. The problem is those jars cannot be distributed in any way, and they are so many, that adding them as dependencies is just too overwhelming. Plus the jar names and/or number of jars can change at any time. I'm writing a little maven plugin for this, but I don't know how to add them to the current classpath. Any pointers will be greatly appreciated :) Thanks, -Alex - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Conveniently switch between settings
Gadre, I think it's assumed that your security configuration will remain stable per environment. So at work you will have a settings.xml with proxy settings and at home a file without proxy settings. Isn't this a one-off change? Or do you have any particular requirements for which you need to switch from work/home at runtime? In this case having a script which swaps the two settings.xml files could be the solution. M. On Fri, 2010-05-07 at 12:13 +0530, Kalpak Gadre wrote: Hi, I use Maven from workplace and home. At workplace we have proxy as well as a maven repository. Where at home I don't need any proxy and don't have a repository. Is there no convenient way to switch between these configurations other than specifying alternate settings file? It would be nice if it was at profile level where I could just say mvn -P home I know that there are lot of issue with that. I hope most of us face this problem. What do you guys do? Thanks, Kalpak - 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: avoiding kludge when factoring common build steps into parent pom
It seems a good solution to me. M. On Fri, 2010-05-07 at 14:30 -0400, Marshall Schor wrote: I have a bunch of project that execute some common build steps. I factored these out into a parent-pom, and change the projects to specify this as their parent. My parent-pom is of package-type pom. The problem I'm having is that the factored-out build steps run when I do mvn install on the parent-pom to get it into my local repo. These steps don't work and throw errors, when run here. So I fixed this with a kludge - and I'm hoping to learn a better way. My kludge: I moved the build steps into a profile, and activated the profile on the absence of a file, named something like marker-file-identifying-parent-pom-XXX. And then, I put a dummy file of that name into the parent project. This keeps the pom from running the build steps in the parent, but makes those steps available to the children. Is there a better way? -Marshall Schor - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Log2j / Maven problem
The error suggests that this is an error in the test suite. I think more of a question for the log4j folks! M. -Original Message- From: Hadzic, Tarik [mailto:hadz...@wusm.wustl.edu] Sent: 07 May 2010 20:12 To: users@maven.apache.org Subject: Log2j / Maven problem I keep getting this on trying to install Log4j on my Snow Leopard: Any ideas? Thanks, T [INFO] An Ant BuildException has occured: The following error occurred while executing this line: /Users/tarikhadzic/Downloads/apache-log4j-1.2.16/tests/build.xml:187: Test org.apache.log4j.CoreTestSuite failed [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: An Ant BuildException has occured: The following error occurred while executing this line: /Users/tarikhadzic/Downloads/apache-log4j-1.2.16/tests/build.xml:187: Test org.apache.log4j.CoreTestSuite failed at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife cycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle (DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec ycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail ures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa ultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle Executor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: An Ant BuildException has occured: The following error occurred while executing this line: /Users/tarikhadzic/Downloads/apache-log4j-1.2.16/tests/build.xml:187: Test org.apache.log4j.CoreTestSuite failed at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo. java:131) at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:98) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage r.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife cycleExecutor.java:678) ... 17 more Caused by: The following error occurred while executing this line: /Users/tarikhadzic/Downloads/apache-log4j-1.2.16/tests/build.xml:187: Test org.apache.log4j.CoreTestSuite failed at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper .java:539) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo. java:118) ... 20 more Caused by: /Users/tarikhadzic/Downloads/apache-log4j-1.2.16/tests/build.xml:187: Test org.apache.log4j.CoreTestSuite failed at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.actOnTestResult(JUnit Task.java:1468) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.jav a:691) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitT ask.java:1434) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.jav a:632) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckEx ecutor.java:37) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at
Re: Ignoring distributionmanagement repositories and use only the settings.xml repository list to upload artifacts
You can create a super-parent POM, which defines only the distribution repositories. This is very unlikely to change therefore having all your projects to extend this one should be relatively safe. M. On Fri, 2010-05-07 at 05:00 +0530, Lahiru Gunathilake wrote: Hi Ron, In my case I have so many modules which are having so many parent poms :( Lahiru On Wed, May 5, 2010 at 5:24 PM, Ron Wheeler rwhee...@artifact-software.comwrote: On 05/05/2010 1:36 AM, Lahiru Gunathilake wrote: Hi all, I have tons of pom files in my project and each file is having its own maven repository listed in their distributionmanagement elements, so I want to use a single repo to do the mvn deploy and point my repository using settings.xml file. I like to know whether this is possible with maven 2.1.0 or not, if this is possible can someone please point me on how to do that ! Thanks in advance Lahiru Wouldn't that be easier in a parent pom? The project poms would not have any distribution management which makes them a lot simpler. Ron - 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: Ignoring distributionmanagement repositories and use only the settings.xml repository list to upload artifacts
No, you can run deploy from any child project. meta information, such as dependencymanagement and distributionmanagement elements are just meta-data. Children inherit those information as these were declared in their POM. M. On Fri, 2010-05-07 at 05:38 +0530, Lahiru Gunathilake wrote: Yeah got it ... thanks guys, so that I can simply run a mvn deploy from the super parent location. Lahiru On Fri, May 7, 2010 at 5:31 AM, Martin Gainty mgai...@hotmail.com wrote: all child project poms have one parent pom which identifies the common repository Martin Gainty __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Fri, 7 May 2010 05:00:38 +0530 Subject: Re: Ignoring distributionmanagement repositories and use only thesettings.xml repository list to upload artifacts From: glah...@gmail.com To: users@maven.apache.org Hi Ron, In my case I have so many modules which are having so many parent poms :( Lahiru On Wed, May 5, 2010 at 5:24 PM, Ron Wheeler rwhee...@artifact-software.comwrote: On 05/05/2010 1:36 AM, Lahiru Gunathilake wrote: Hi all, I have tons of pom files in my project and each file is having its own maven repository listed in their distributionmanagement elements, so I want to use a single repo to do the mvn deploy and point my repository using settings.xml file. I like to know whether this is possible with maven 2.1.0 or not, if this is possible can someone please point me on how to do that ! Thanks in advance Lahiru Wouldn't that be easier in a parent pom? The project poms would not have any distribution management which makes them a lot simpler. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Apache Qpid, Worlds dominant messaging middleware..!!! Senior Software Engineer WSO2 Inc _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
