(Fwd) Change config of plugin outside of pom.xml

Sorry for cross-posting this mail, I didn't get an answer on user mailing list. Is it possible to overvrite plugin configuration outside of the pom.xml? I have nested elements in my plugin configuration, so I can't use a simple property that can be replaced? Regards, carsten --- Forwarded

Re: Assembly and DependencySets (Re: assemply and packaging)

;jar-with-dependencies'. You > > should move this thread to the users list. The audience that can help is > > probably greater > > there than on the dev list. > > > > -Tim > > > > Carsten Karkola schrieb: > > > What I tried to do is, t

Ant plugin and dependencies

We moving a project from ant to mvn - so I have to replace ant tasks by maven plugins. My problem: - plugin for start/stop Bea Weblogic and /deploy/undeploy a previously built EAR that gets installed in the local repo - I decided to use an Ant plugin with goals like wls:start wls:deploy, ... N

Assembly and DependencySets (Re: assemply and packaging)

What I tried to do is, to filter dependencies and unpack some of them, simply copy others to some dirs, like: 1. two dependencies with type zip /lib true runtime *.zip 2. a jar / false runtime my

Re: assemply and packaging

gt;maven-assembly-plugin > > > > > >package > > > > jar-with-dependencies > > > > > > assembly > > > > > > > > > > > > Hope this helps > > -Tim

Re: Maven 2.0.4 - Cascading POMs with packaging=pom

On 19 May 2006 at 11:30, Grzegorz Slowikowski wrote: > Yes, you can. > > Greg There is the BUG-ID: http://jira.codehaus.org/browse/MNG-2308 regards, carsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e

assemply and packaging

Hello, the usage of the assembly plugin is only possible via mvn assembly:assembly Is there a possibility to define something like assembly So I could do a mvn package in my multi-project directory and would get the needed assemblies without special calls of some subprojects, where the ass

Re: Maven 2.0.4 - Cascading POMs with packaging=pom

Hello, thank you for verifying! Can I create an JIRA issue or who is responsible for this? regards, carsten > > > Hello > > Maven should look for parent pom in parent directory first. > This have been described some time ago by Brett (I think). > > I have just tested it. It's a regression in Mav

Re: Maven 2.0.4 - Cascading POMs with packaging=pom

s get resolved in subdir a/b as they get resolved in subdir a/b/b.a regards, carsten On 18 May 2006 at 13:37, Trygve Laugstøl wrote: > Carsten Karkola wrote: > > Hi, > > > > I've created the following directory layout > > > > /a - pom.xml > >/b - pom.xml

Re: Maven 2.0.4 - Cascading POMs with packaging=pom

roject/parent/relativePath" setting ... > seems that takes precendence over repository resolution when building. > > Example for b: > > ../pom.xml > > > Does this help? > > Cheers, > Marcel > > Carsten Karkola wrote: > > Hi, > > > >

Maven 2.0.4 - Cascading POMs with packaging=pom

Hi, I've created the following directory layout /a - pom.xml /b - pom.xml - /b.a -pom.xml My executions: $> cd ~/a $> mvn compile [INFO] BUILD SUCCESSFUL $> cd ~/a/b/b.a $> mvn compile [INFO] BUILD SUCCESSFUL $> cd ~/a/b $> mvn compile [INFO] Scanning for projects.

checkstyle plugin and propertyExpansion

We have our own checkstyle config with some file references. I tried to use them with org.apache.maven.plugins maven-checkstyle-plugin ${basedir}/../../checks.xml header.regexp.file=${basedir}/../../header_regexp.txt