You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Cornuau Frédéric <fr...@atosorigin.com> on 2009/10/08 11:49:12 UTC
Maven classifiers and profiles dependencies inheritance
Hello,
I've a project with 2 profiles defined as follows:
<profiles>
<profile>
<id>jdk1.5</id>
<build>
<plugins>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<classifier>jdk1.5</classifier>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15</artifactId>
<version>1.43</version>
</dependency>
</dependencies>
</profile>
<profile>
<id>jdk1.6</id>
<build>
<plugins>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<classifier>jdk1.6</classifier>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk16</artifactId>
<version>1.43</version>
</dependency>
</dependencies>
</profile>
</profiles>
<dependencies>
<!-- common dependencies -->
</dependencies>
When I use my project dependency (with a given classifier) in another project, the dependency defined in the associated profile is not inherited.
It seems there is no link between classifiers and profiles, doesn't it ?
Do I need to create two distinct projects with different artifact ids ? And in this case, how can I manage the sources of my project in the two new projects ?
Thanks in advance
Frederic
________________________________
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Creating a branch in non-interactive mode
Posted by Matt Milliss <ma...@gmail.com>.
I have a project on a particular version eg 09.20.00-SNAPSHOT I want to
create a branch so I run the following command;
mvn release:branch -DbranchName=09.20.00_BRANCH
-DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
and when prompted for the branch version I enter 09.20.01-SNAPSHOT, this
works as expected and the branch is created with the version
09.20.01-SNAPSHOT.
Now I want to automate this process and try the following command;
mvn release:branch -DbranchName=09.20.00_BRANCH
-DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
-Dproject.rel.net.moneyswitch:extranet=09.20.01-SNAPSHOT --batch-mode
is this case the branch is created but the version is still at
09.20.00-SNAPSHOT not 09.20.01-SNAPSHOT as expected. I found these
instructions here
http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html,
am I misunderstanding how this goal is meant to work.
Regards
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org