IIRC you can't specify the artifactId through a property. For good reasons.

/Anders

On Fri, Apr 22, 2011 at 15:57, maxime.lem <[email protected]> wrote:

> I couldn't find any good solution. So I'm now considering using differents
> mvn run for compiling with differents sdk versions.
> I'm using profiles for this, and a mvn clean install -Psdk... works
> perfectly. I'm getting in mvn repo 2 artifacts with different artifacts id
> (i used a variable set by profile in artifact id).
>
> But I'm getting in trouble with mvn release.
> I'm using maven release hudson's plugin for this and it is deploying the
> release to an artifactId without the variable name.
> Here is the command line hudson is executing when the release 1.0 is
> performed:
>
> mvn -B -f
> /data/workspaces/hudson/jobs/project_fonts-sdk4.0/workspace/trunk/pom.xml
> -Dproject.rel.com.company.project:project-fonts-sdk4.0=1.0
> -Dproject.dev.com.company.project:project-fonts-sdk4.0=1.1-SNAPSHOT
> -Dproject.dev.com.company.project:project-fonts=1.1-SNAPSHOT
> -Dproject.rel.com.company.project:project-fonts=1.0 -Dresume=false
> -Drelease=true -Dsdk=4.0 release:prepare release:perform
>
>
> I checked previous releases on "normal" projects, and there, I can find
> only
> occurence of -Dproject.dev.* and -Dproject.rel.*, and not twice as above.
>
> Could it be a bug in maven release hudson plugin?
>
> Is there another way to release 2 differents artifacts sharing the same
> sources?
>
> Maxime
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Build-a-project-twice-with-different-classifier-in-one-run-tp4331794p4333012.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]
>
>

Reply via email to