I am not aware of any convention in that area. And I am breaking my
pledge to stop trying to answer emails. Hopefully I don't give you bad
advice this time. :-)
Some options/issues:
1. ../lib -- fails if /bin is not the current working directory, like if
you run './target/bin/somestartscript.sh' while in the project/module
directory.
2. token replacement during build to produce absolute path to lib dir --
fails if you move this stuff, like if you delivered the contents of
target as an artifact.
3. fancy scripting that figures out where the bin script lives (or
really, where the app "home" is), and then find the libs relative to
that -- robust but complex, perhaps you can borrow this functionality
from the start script of another app, many app start scripts behave this
way, including the 'mvn' script
-Max
EJ Ciramella wrote:
In a related note, how are the scripts that are used to start/stop
applications built by maven supposed to build up the proper class path?
So during the build for this one application we have, the jar file is
placed in target/lib now.
ALSO - as the resources are processed, the scripts wind up in
target/scripts. The developers want to be able to cd into scripts and
run somestartscript.sh which looks into the lib directory (../lib) to
build up the classpath (just load all jars).
Am I approaching this wrong?
-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 6:53 PM
To: Maven Users List
Subject: RE: One more simple question
That would be a misuse of final name:
finalName The filename (excluding the extension, and with no path
information) that the produced artifact will be called. The default
value is ${artifactId}-${version}.
-----Original Message-----
From: Max Cooper [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 6:51 PM
To: Maven Users List
Subject: Re: One more simple question
Oh yeah, that's better than my jarName solution.
Okay, I think I will stop trying to answer emails today before I give
any more lousy advice. :-)
-Max
EJ Ciramella wrote:
Also, wouldn't it be basedir according to that documentation?
-----Original Message-----
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 6:46 PM
To: Maven Users List
Subject: RE: One more simple question
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
configuring: org.apache.maven.plugins:maven-jar-plugin. Reason: ERROR:
Cannot overr
ide read-only parameter: outputDirectory in goal: jar:jar
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<outputDirectory>${project.build.outputDirectory}/lib</outputDirectory>
</configuration>
</plugin>
-----Original Message-----
From: Max Cooper [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 6:40 PM
To: Maven Users List
Subject: Re: One more simple question
http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html
Set outputDirectory to ${project.build.outputDirectory}/lib in the jar
plugin configuration.
-Max
EJ Ciramella wrote:
By default, jars are placed in the root of target, how do you move
them
to target/lib?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
