Done=21

http://svn.apache.or= g/viewvc=3Frev=3D1074434&view=3Drev

I no= ticed we have a few other profiles in the 'project' pom.xml, 'release' an= d 'full' profiles.

Here they are:

   = <profile>

&nb= sp; <id>release</id>

&nb= sp; <build>

&nb= sp; <= plugins>

= <=21-- We want do the rat check

<plugin>

<groupId>o= rg.apache.rat</groupId>

<artifactId&g= t;apache-rat-plugin</artifactId>

<configuratio= n>

<exclu= des>

&l= t;exclude>**/target/**/*</exclude>

&l= t;exclude>**/cobertura.ser</exclude>

&l= t;exclude>**/.classpath</exclude>

&l= t;exclude>**/.project</exclude>

&l= t;exclude>**/.settings/**/*</exclude>

&l= t;exclude>**/*.iml</exclude>

&l= t;exclude>**/*.ipr</exclude>

&l= t;exclude>**/*.iws</exclude>

&l= t;exclude>**/MANI=46EST.M=46</exclude>

</excl= udes>

</configurati= on>

<executions&g= t;

<execu= tion>

&l= t;phase>verify</phase>

&l= t;goals>

&n= bsp; <goal>check</goal>

&l= t;/goals>

</exec= ution>

</executions&= gt;

   </plugin>

   -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-release-plugin</a= rtifactId>

= <configuration>

= &= lt;useReleaseProfile>false</useReleaseProfile>

&nb= sp; <goals>deploy</goals>

&nb= sp; <arguments>-Prelease =24=7Brelease.= altDeploymentRepository=7D</arguments>

= </configuration>

&nb= sp; <= /plugin>



= <=21-- We want a source jar -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-source-plugin</a= rtifactId>

&nb= sp; <executions>

&nb= sp; <execution>

&nb= sp; <goals>

&nb= sp; <go= al>jar</g= oal>

&nb= sp; </goals>

&nb= sp; </execution>

&nb= sp; </executions>

&nb= sp; <= /plugin>

= <=21-- We want to sign the artifact, the POM, and= all attached artifacts -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-gpg-plugin</arti= factId>

= <inherited>true&l= t;/inherited>

= <configuration>

&nb= sp; <passphrase>=24=7Bgpg.passphrase=7D= </passphrase>

= </configuration>

&nb= sp; <executions>

&nb= sp; <execution>

&nb= sp; <goals>

&nb= sp; <go= al>sign</g= oal>

&nb= sp; </goals>

&nb= sp; </execution>

&nb= sp; </executions>

&nb= sp; <= /plugin>

= <=21-- In the future... -->

= <=21-- We want to deploy the artifact to a stagin= g location for perusal -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-deploy-plugin</a= rtifactId>

= <inherited>true&l= t;/inherited>

= <configuration>

= <=21-- uncomment to enable =22stage= d=22 release process -->

= <=21--<altDeploymentRepository&g= t;=24=7Bdeploy.altRepository=7D</altDeploymentRepository>-->
=
= &= lt;updateReleaseInfo>true</updateReleaseInfo>

= </configuration>

&nb= sp; <= /plugin>

= <=21-- We want the JavaDoc JAR published with the= release -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-javadoc-plugin</a= rtifactId>

= <inherited>true&l= t;/inherited>

= <configuration>

&nb= sp; <source>1.5</source>

= </configuration>

&nb= sp; <executions>

&nb= sp; <execution>

&nb= sp; <id>attach-javadocs</id>

&nb= sp; <goals>

&nb= sp; <go= al>jar</g= oal>

&nb= sp; </goals>

&nb= sp; </execution>

&nb= sp; </executions>

&nb= sp; <= /plugin>

&nb= sp; </plugins>

&nb= sp; </build>

= </profile>

= <profile>

&nb= sp; <id>full</id>

&nb= sp; <build>

&nb= sp; <= plugins>

= <=21-- We want a source jar -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-source-plugin</a= rtifactId>

&nb= sp; <executions>

&nb= sp; <execution>

&nb= sp; <goals>

&nb= sp; <go= al>jar</g= oal>

&nb= sp; </goals>

&nb= sp; </execution>

&nb= sp; </executions>

&nb= sp; <= /plugin>

= <=21-- We want the JavaDoc JAR published with the= release -->

&nb= sp; <= plugin>

&nb= sp; <groupId>org.apache.maven.plugins</groupId>

&nb= sp; <artifactId>maven-javadoc-plugin</a= rtifactId>

= <inherited>true&l= t;/inherited>

= <configuration>

&nb= sp; <source>1.5</source>

= </configuration>

&nb= sp; <executions>

&nb= sp; <execution>

&nb= sp; <id>attach-javadocs</id>

&nb= sp; <goals>

&nb= sp; <go= al>jar</g= oal>

&nb= sp; </goals>

&nb= sp; </execution>

&nb= sp; </executions>

&nb= sp; <= /plugin>

&nb= sp; </plugins>

&nb= sp; </build>

= </profile>

<= /span>

Does anyone know if these profiles are still = used and not deprecated=3F

I'm really wondering...

Ma= ybe we should remove if they are not used anymore.

Should I schedule a new release of the 'project' pom.xml for later tod= ay=3F

Regards,
Pierre-Arnaud

= =20

On vendredi 25 f=C3=A9= vrier 2011 at 02:13, Emmanuel Lecharny wrote:

On 2/23/11 1:54 PM, Pierre-Arnaud Mar= celot wrote:
Hi Dev,

Eclipse= is great but it has one major drawback for me (and others too I believe)= , that's it's inability to import the same project twice in the workspace= .

Now, by =22the same project=22 I don't mean the exact same proje= ct (which would not make much sense) but I mean the same project but from= various SVN branches (e.g. one version from trunk and another from a bra= nch).

Considering that we're now working in two different places (= 'trunks' and 'milestones' branches), I would rather have all the projects= in a common workspace than having two workspaces (one for each branch).<= br>
The basic problem is that 'mvn eclipse:eclipse' generates the same= project names for both branches and that Eclipse only allows one project= with a given name at a time in the workspace (and I can understand that)= .

Recently, while looking at the Maven Eclipse plugin documentatio= n I found out an interesting configuration option that we could leverage = to solve this issue.

I built a specific profile that will be activ= ated if we specify a string we want to be appended to the name of the pro= ject when creating eclipse descriptors using 'mvn eclipse:eclipse -Dappend.to.project.name=3D=5B= string=5D'.

Here it is:

= <profile>
<id>append-to-project-name</id>
<act= ivation>
<property>
<name>append.to.project.name</name>
</prope= rty>
</activation>
<build>
<plugins>
<= ;plugin>
<artifactId>maven-eclipse-plugin</artifactId><= br><configuration>
<projectNameTemplate>=5BartifactId=5D-=24= =7Bappend.to.project.name=7D</projectNameTemplate>
</configuration>
</plugi= n>
</plugins>
</build>
</profile>
=

Using this profile it is now possible to import = the same project twice (and more) by providing for example the name of th= e branch, which will be appended to the name of the project.

I'd l= ike to include this new profile in the 'project' pom to be able to reuse = it across all our projects.

Thoughts=3F

Regards,
Pierre-= Arnaud
+1. Go for it =21

--
Regards,
= Cordialement,
Emmanuel L=C3=A9charny
www.iktek.com
=20 =20 =20 =20

=20