[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Using MAVEN2_CLASSPATH_CONTAINER
wolfc
do-not-reply at jboss.com
Thu Jun 18 04:42:52 EDT 2009
I would also say to make an eclipse profile mandatory which puts the classes in 'eclipse-target/...' instead of 'target'. I've seen some cases where JDT would create class files that where wrong and those ended up in the (snapshot) repository.
<build>
| <!-- based on the profile we switch directories -->
| <outputDirectory>${myproject.outputDirectory}</outputDirectory>
| <testOutputDirectory>${myproject.testOutputDirectory}</testOutputDirectory>
| </build>
|
| <profiles>
| <!--
| To make sure we don't end up with Eclipse compiled classes
| in the repo we use different output directories when running
| under Eclipse.
| -->
| <profile>
| <id>default</id>
| <activation>
| <activeByDefault>true</activeByDefault>
| </activation>
| <properties>
| <myproject.outputDirectory>target/classes</myproject.outputDirectory>
| <myproject.testOutputDirectory>
| target/test-classes
| </myproject.testOutputDirectory>
| </properties>
| </profile>
|
| <profile>
| <id>eclipse</id>
| <build>
| <defaultGoal>process-test-resources</defaultGoal>
| <plugins>
| <plugin>
| <artifactId>maven-eclipse-plugin</artifactId>
| <version>2.6</version>
| <configuration>
| <downloadSources>true</downloadSources>
| <buildOutputDirectory>eclipse-target/classes</buildOutputDirectory>
| </configuration>
| </plugin>
| </plugins>
| </build>
| <properties>
| <myproject.outputDirectory>eclipse-target/classes</myproject.outputDirectory>
| <myproject.testOutputDirectory>
| eclipse-target/test-classes
| </myproject.testOutputDirectory>
| </properties>
| </profile>
| </profiles>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238414#4238414
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238414
More information about the jboss-dev-forums
mailing list