I guess I was too quick to declare victory.
While the compiled classes do go into the newly configured directory, the
jar file is still being placed into the default directory, which in my
case, happens to be smack in the middle of the versioned source tree.
So, how can I change the output directory for the package goal? Is there a
universal way to divert output of any and all goals?
Thanks
Dmitry
At 08:58 PM 1/10/2006, Henry Isidro wrote:
Dmitry Beransky wrote:
worked like a charm! I ended up putting the following into the profile
section:
<properties>
<buildDir>${java.io.tmpDir}/maven/${pom.artifactId}</buildDir>
</properties>
now the settings file is portalble among different platforms. Very cool,
indeed.
Thanks
Dmitry
I was thinking in the lines of using profiles in settings.xml or
profiles.xml where you specify a property which would be used in the pom, ie:
- inside profiles.xml (which resides only in the system that is used):
<profiles>
<profile>
<id>myProfile</id>
<properties>
<myoutput>c:\test\target</myoutput>
</properties>
</profile>
</profiles>
- inside pom.xml (which is portable):
....
<build>
<outputDirectory>${myoutput}</outputDirectory>
</build>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
