The way I've done this in the past is to use the assembly plugin to
generate a distribution zip/tar.
The unpacked structure looks like:
/bin
/lib
/conf
/log
In the bin directory, you would add a shell script that sets up the
runtime environment and invokes the mule runtime. The lib directory
would be the destination of all of the dependency jars. The conf
directory would hold your mule, log4j, db, etc configuration files. The
log directory would be the destination for any log files created when
running mule.
The advantage to this method is that you shouldn't have to touch your
base installation of mule to run your application.
Hope this helps,
Joe Hindsley
Steve Lihn wrote:
Hi,
When maven builds a project, it figures out all the dependent jar
files, adds them to the classpath, produces the project's jar file
under target/.
My question is -- is there a way to ask maven also puts all (or some)
those dependent jar files under target/ too.
The origin of the issue is that we have a project that builds a jar
for Mule. However, when deploying this jar file to Mule, we still have
to collect all the dependent jar files that Mule does not have and
place them under Mule's lib/user/ folder. So every time we upgrade a
dependency, for instance, json-lib from 2.2.2 to 2.2.3, we not only
have to modify the pom.xml, but also look for json-lib 2.2.3 jar and
make sure we upgrade it in lib/user/.
Wouldn't it be easier if maven can figure these all out for us since
it is all in pom.xml ?
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
