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
Hmmmtry configuring the jar plugin. There's an outputDirectory
property there but I think this is still in SVN. The old version used
basedir for this and was a readonly attribute but it was changed to
outputDirectory to allow users to direct where the jar will be
generated. You may have to
Hi,
I'm trying to migrate for the first time one of my projects to Maven2. In
Maven 1, I used to have the following line in the user level configuration
file:
maven.build.dir=c:/temp/maven/${pom.artifactId}
this was for Windows-based workstations; on a server, the build directory
would
Dmitry Beransky wrote:
Hi,
I'm trying to migrate for the first time one of my projects to
Maven2. In Maven 1, I used to have the following line in the user
level configuration file:
maven.build.dir=c:/temp/maven/${pom.artifactId}
this was for Windows-based workstations; on a server,
I don't see an outputDirectory/ specified under build/ element for
profile/ in the pom descriptor.
http://maven.apache.org/maven-model/maven.html
Not sure if its an 'error of omission' in online docs or if a profile
does (or does not) supports overriding the build outputDirectory? You
Hello,
According to the schema (http://maven.apache.org/maven-v4_0_0.xsd),
outputDirectory is indeed not defined in the profile section. But I
think, by configuring the compiler plugin, you can set the path in plugin
under the plugins section of profile.
Cheers!
Nap
On 1/11/06, Rinku [EMAIL
Yep, that would address a specific scenario where Compiler plugin is
being invoked.
But, what happens if user wants the outputDirectory set for more than
just the compiler plugin ? ;-)
My understanding from M1 was that all the plugins derived the build
output directory value from
Rinku wrote:
I don't see an outputDirectory/ specified under build/ element for
profile/ in the pom descriptor.
http://maven.apache.org/maven-model/maven.html
Not sure if its an 'error of omission' in online docs or if a
profile does (or does not) supports overriding the build
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
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
10 matches
Mail list logo
