Problem with maven-invoker plugin

Hi, I like to use the maven-invoker plugin in my own plugin, but it failes with an error... i use maven 2.2.1, in the pom.xml i have dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-invoker/artifactId version2.0.11/version /dependency and the error is: [INFO]

General exclusion of a dependency

Hi, is it possible to exclude a dependency without specifying from which other dependency it might come from ? Like wherever depA is coming from, exclude it ? Thanks

how to patch releases

Hi all, this might be a simple one and if there is documentation about it I'm happy to read that. Its a basic understanding question: I have a maven project and do a release - lets say 1.1 The maven release plugin manipulates the poms and tags the software in the scm. the trunk itself

Re: : how to patch releases

Hi Julien Thanks for your mail. You are right the scm section has to be changed too. I will just try with a dummy project how release:branch works. But its good to know that the release plugin then works fine Cheers -Original Message- From: Julien HENRY henr...@yahoo.fr

Re: maven is a swamp

On Fri, Oct 15, 2010 3:00 am, Jason van Zyl wrote: A fact to note though is that I've asked over 2k people over the last two years at talks and in any average crowd the people who care to have a different format or DSL is around 3%. And I one of them :-) I always havent been a friend of

Re: maven is a swamp

oh sorry for this misunderstanding. I just quoted your (Jason) statement that just a few people like to have a dsl instead of xml and that I'm one of them ... The rest is basically to Ken, as I dont understand at all why he is complaining on this list or for what purpose sorry

multimodul and parent pom question

Hi, we have a multimodul project with a lot of modules. Currently the root-pom of the multimodul project is also the parent pom of each submodul project. This stroke us quite some time when we made changes in the parent pom regarding dependency versions in dependencyManagement or other

Re: Can't specify distributionManagement in settings.xml

hey, Artifactory (http://www.jfrog.org/products.php) has the possibility to copy an artifact to another repository - about the if and how to use it, there are smarter people here already discussing it cheers -Original Message- From: Phillip Hellewell ssh...@gmail.com To:

Re: Can't specify distributionManagement in settings.xml

Well, at this point all I'm mainly after is the ability to copy anartifact from snapshot to release repo (removing -SNAPSHOT from theversion) without having to go through the rebuild process. If thatfunctionality does not exist as a free plugin or anything at themoment, who knows,

getting all sources of a multimodulproject

Hi, I have a multimodul project. What is the best/easy way to create a zip containing all sources / javadocs from all modules ? (this modules themselve can either be projects or again multimodules) ? Thanks

Re: getting all sources of a multimodulproject

we have migrated our ant structure to maven projects and need to keep the existing distributions for legacy reasons. So what I'm looking for is a way to easily include all source files from the multimodule project in a zip which is given to the clients - there is always the way of having an

how to resolve dependencies in plugins

Hi, in a maven plugin I like to resolve the dependencies of a project. My current way to do so is: for (Dependency dep: project.getModel().getDependencies()) { // factory is Artifact artifact = factory.createArtifact(dependency.getGroupId(), dependency.getArtifactId(),

release - modify SCM information

Hi, is it possible to manipulate the SCM modification of the maven-release-plugin ? Our project is found under the following URL: https://svn-server/repository/svn/foobar/trunk/ourProject ourProject is a multimodule project with several children. when I ran the maven release plugin it creates

add plugin to lifecycle

Hi, I have a self made plugin which requires to get project.getArtifactSet(). As far as I understood this is done lazy, so depending on the state of the lifecycle this method returns differen results. I want my plugin to get the compile dependencies, but not run automatically whenever compile

scope of transitive deps

hi, I have a project A which defines a dependency to project B in scope test. project B itself has several dependencies in scope compile. Surprinsingly these dependencies are also included in Project A in compile scope. ?! E.g. project A requires a dependency to project C in productive

Re: sharing assembly descriptor

Thanks for that, but unfortunately its still not working for me. My Assembly-Descriptor project now has the assembly-desc.xml under src/main/resources/assemblies. In the resulting jar file I see the package assemblies with the xml. In the rest projects i didnt change anything. My project

sharing assembly descriptor

Hi all, I'm trying to use a shared assembly descriptor as described in http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html Unfortunately it fails with Error: java.net.MalformedURLException: no protocol: assembly-desc.xml My setup is: 1) A project calles