Re: maven-antrun-plugin

2010-10-27 Thread paladine
yes i can see it in build log but i can't intervene after checking dependencies, ant script runs before creating war file. any suggestions ? thanks in advance -- View this message in context: http://maven.40175.n5.nabble.com/maven-antrun-plugin-tp3236582p3238246.html Sent from the Maven -

Re: maven-antrun-plugin

2010-10-27 Thread Anders Hammar
The antrun-plugin execution must be bound to the wrong phase then. /Anders On Wed, Oct 27, 2010 at 09:01, paladine yasinma...@yahoo.com wrote: yes i can see it in build log but i can't intervene after checking dependencies, ant script runs before creating war file. any suggestions ?

Re: maven-antrun-plugin

2010-10-27 Thread Jörg Schaible
paladine wrote: yes i can see it in build log but i can't intervene after checking dependencies, ant script runs before creating war file. any suggestions ? Can you hava look at help:effective-pom? Maybe you inherit another executionfrom your parent. - Jörg

maven 3 snapshot resolving

2010-10-27 Thread Tom
We use Nexus as our repository manager and publish all artifacts (snapshot and release) through one url. This was a suggested setup to solve a Maven 2.2.1 resolve behavior (I can't remember what exactly, so off the top of my head). We have switched to Maven 3 and the following behavior

Re: profile activation confusion

2010-10-27 Thread Ron Wheeler
On 27/10/2010 1:51 AM, Anders Hammar wrote: While on the topic, I'd like to mention that having a different build (through profiles for example) for each environment is not good. In Maven, there can only be one flavor of a released artifact. So if you build v1.0 of your war, cannot rebuild it

Re: maven 3 snapshot resolving

2010-10-27 Thread Benjamin Bentmann
Tom wrote: Could not find artifact nl.innovationinvestments:CheyenneServlet:jar:1.11-SNAPSHOT in kp (http://alaya.applicationplaza.com:8081/nexus/content/groups/pub lic) Could be related to [0], i.e. a problem with the metadata that Maven requires to locate the timestamped snapshot. Either

Re: profile activation confusion

2010-10-27 Thread Jörg Schaible
Anders Hammar wrote: You need Maven 3.0 to be able to activate profiles in the pom by properties set in a profile in settings.xml. The point is that this functionality is superfluous. If you want a profile be activated based on properties in settings.xml, you may as well simply add it there

Re: maven 3 snapshot resolving

2010-10-27 Thread Tom
This wiki refers to Maven 2 clients having problems accessing Maven 3 artifacts. In my situation Maven 3 clients are the problem; they does not seem to find the artifacts it deployed itself. So that would not be activating legacy behavior. On 27-10-2010 14:47, Benjamin Bentmann wrote: Tom

Re: Invoking a plugin programmatically using maven 3 and scala

2010-10-27 Thread Benjamin Bentmann
Andreas Gies wrote: [INFO] org.scala-tools:scala-mojo-support:jar:0.3-SNAPSHOT ... [INFO] | +- org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2:compile [INFO] | | \- org.sonatype.sisu:sisu-inject-bean:jar:1.4.2:compile [INFO] | | \- org.sonatype.sisu:sisu-guice:jar:noaop:2.1.7:compile ... [INFO]

Re: Invoking a plugin programmatically using maven 3 and scala

2010-10-27 Thread Jörg Schaible
Benjamin, Benjamin Bentmann wrote: Andreas Gies wrote: [INFO] org.scala-tools:scala-mojo-support:jar:0.3-SNAPSHOT ... [INFO] | +- org.sonatype.sisu:sisu-inject-plexus:jar:1.4.2:compile [INFO] | | \- org.sonatype.sisu:sisu-inject-bean:jar:1.4.2:compile [INFO] | | \-

Re: maven 3 snapshot resolving

2010-10-27 Thread Benjamin Bentmann
Tom wrote: This wiki refers to Maven 2 clients having problems From that wiki: Additionally, some repository managers [...] may not cope with the additional XML elements in the metadata file. This applies to (unpatched) Nexus versions before 1.8 where the issue manifests itself as the

Re: maven 3 snapshot resolving

2010-10-27 Thread Tom
My snapshot repositories were configured using uniqueVersionfalse/uniqueVersion. Maven 3 does not seem to respect that when releasing and releases with a date-time anyhow, but does respect it when resolving and does not find the date-time files. By modifying uniqueVersion to true, it seems to

Re: Invoking a plugin programmatically using maven 3 and scala

2010-10-27 Thread Benjamin Bentmann
Jörg Schaible wrote: Is it save now in M3 to declare a different plugin artifact as dependency? You mean plugin A having a dependency on plugin B? This shouldn't cause an issue for Maven 3 when running the plugin (it should also work in recent Maven 2.x releases IIRC). That inheriting

Re: maven 3 snapshot resolving

2010-10-27 Thread Tom
On 27-10-2010 15:04, Tom wrote: My snapshot repositories were configured using uniqueVersionfalse/uniqueVersion. Maven 3 does not seem to respect that when releasing and releases with a date-time anyhow, but does respect it when resolving and does not find the date-time files. By modifying

Re: avoiding dependency version number duplication

2010-10-27 Thread Marshall Schor
I may be over my head here, but I think that when you do a *release* (using the release plugin), there is an option to have a version of the pom created for the tag that has the properties fully resolved. See http://maven.apache.org/plugins/maven-release-plugin/prepare-with-pom-mojo.html Does

Re: Invoking a plugin programmatically using maven 3 and scala

2010-10-27 Thread Jörg Schaible
Benjamin Bentmann wrote: Jörg Schaible wrote: Is it save now in M3 to declare a different plugin artifact as dependency? You mean plugin A having a dependency on plugin B? This shouldn't cause an issue for Maven 3 when running the plugin (it should also work in recent Maven 2.x releases

Re: maven 3 snapshot resolving

2010-10-27 Thread Tom
Upgrading to Nexus 1.8 did solve it, it seems. Thanks! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Re: Including scope:provided dependencies in a shaded jar ?

2010-10-27 Thread Jörg Schaible
Hi Greg, Grégory Joseph wrote: Hi, I have a project for which I'd like to create a shaded jar. It has a bunch of dependencies in scope:provided, because they really are, in the normal use-case of this artifact; it's meant to be deployed as a plugin in another app, so, for example,

Re: Including scope:provided dependencies in a shaded jar ?

2010-10-27 Thread Wayne Fay
could split my project and have 2 modules, one simply being the standalone/shaded version of the other, but it seems overkill, since they're really the same source. This is the correct approach (imo). Two artifacts, one for the provided artifact, another for the shaded artifact. Wayne

Re: Including scope:provided dependencies in a shaded jar ?

2010-10-27 Thread Antonio Petrelli
2010/10/27 Grégory Joseph greg@gmail.com: .. but yes, this project now also needs a standalone/executable jar; some of the provided dependencies are needed at runtime for this. As far as I can tell, the shade plugin currently does not propose any solution for this. Is there any way this

Maven 3 + site plugin + tycho

2010-10-27 Thread Hari shankar
Am using maven 3 + tycho to build eclipse plugins: i wrote a windows batch file to simulate a CI setup locally: 1. checkout projects from SVN 2. Build from parent It fails with following err: [ERROR] Failed to execute goal org.apache.maven.plugins: maven-site-plugin:3.0-be

Re: profile activation confusion

2010-10-27 Thread Anders Hammar
You either need to separate the configuration from the binaries, or have different artifacts. Your current solution does not work if you do deploys to a repo and adhere to the very important Maven rule that a release may NEVER be altered. /Anders On Wed, Oct 27, 2010 at 18:52, Jon Paynter

Re: profile activation confusion

2010-10-27 Thread Jon Paynter
On Wed, Oct 27, 2010 at 11:41 AM, Anders Hammar and...@hammar.net wrote: You either need to separate the configuration from the binaries, or have different artifacts. The configuration is separated from the binaries for the most part. however some artifacts (like a war file) have environment

How to release 2 items together, with inter-dependent versions, some specified in configuration elements?

2010-10-27 Thread Marshall Schor
We have a common project parent-pom, and a build-resources-bundle project containing various build resources, bundled into a Jar artifact. One of these resources is used in configuring the maven remote-resources-plugin, for instance. We start with the configuration where both the parent-pom and

arguments versus useReleaseProfiles versus the the release plugin

2010-10-27 Thread Benson Margulies
Using release plugin 2.1: org.apache:apache:7 uses arguments to turn on a profile. I don't want that profile in prepare. I have another profile I'd like instead. So, I've got .. plugin groupIdorg.apache.maven.plugins/groupId

Re: maven-eclipse-plugin Does not resolve workspace project name

2010-10-27 Thread Ron Wheeler
On 27/10/2010 1:28 PM, Wayne Fay wrote: When I run eclipse:eclipse the project name in the .project file will be the artifactId (by default) despite the eclipse project name being something different. Yes, this is how m-e-p works. The .project file is overwritten by m-e-p and so you will lose

using the CheckoutMojo in my own plugin

2010-10-27 Thread Jared Prestwich
I'm writting a plugin that checks the dependencies and seperates my company dependencies out. That works fine but now I would like to run a checkout on those. I have the connectionUrl set in the poms. I just need to call checkout. I have tried getting an object of CheckoutMojo type but it always

[ANN] Maven Archetype Plugin 2.0 Released

2010-10-27 Thread Hervé Boutemy
The Maven team is pleased to announce the release of the Maven Archetype Plugin, version 2.0 Archetype is a Maven project templating toolkit. http://maven.apache.org/archetype/maven-archetype-plugin/ Release Notes - Maven Archetype - Version 2.0 ** Bug * [ARCHETYPE-202] - Can't download

Setting class path with Shade plugin

2010-10-27 Thread Todd Nine
Hi all, We're creating an uber jar using the shade plugin. This is working well, but I'm having trouble getting the class path set properly in my manifest. Our deployment directory structure is as follows. /appdir/service.jar /appdir/conf/log4j.properties /appdir/conf/zookeeper.properties

Re: Maven SQL plugin

2010-10-27 Thread Chris Odney
Yup, I would like to do that. However, I settled for an alternative for my project. If someone could help me with a starting point in the code(Am I asking for too much? ) I will take it from there. Thanks, Chris. On Wed, Oct 20, 2010 at 2:25 AM, Wayne Fay wayne...@gmail.com wrote: In this