Yes, after a great deal of paddling around, I ran into dependency:unpack
and that is what I ended up using.
Perry Hoekstra
Stephen Connolly wrote:
dependency:unpack???
2009/3/30 <[email protected]>
Jeff:
If it was a single file (ie. CheckStyle) I would have most likely gone down
the URL route. However, I have multiple configuration files (CheckStyle,
PMD, FindBugs, testing, etc) so I would like it all as single dependency.
If I go down the *.jar route, it works for CheckStyle but does not seem to
work for other plug-ins. That is why I was looking for a solution that
would allow a *.jar file to be pulled from a repository and explode to a
defined directory. All of the plug-ins have an option to point to a given
directory for configuration files. I can do it through the Ant plug-in
(unzip) but I was trying to find a pure Maven solution first.
Perry Hoekstra
---- Jeff Jensen <[email protected]> wrote:
Hi Perry,
Typically, I have used the configuration options of the
tool, such as
specifying the config file via a URL with Checkstyle. I
have also
bundled them together a separate project, deployed that
jar, and made
it a dependency of the projects. This works when the
respective tool
can can load the config file via the classpath.
HTH
On Mon, 30 Mar 2009 10:55:09 -0400
<[email protected]> wrote:
Hello all:
I am working in a Maven multi-project environment and I
would like to maintain some consistency across projects
for some tools like CheckStyle, FindBugs, etc. In order
to do this, I am thinking of using the remote resource
plugin. However, the documentation states that the files
>from the resource bundle is deposited in the
$basedir/target/classes directory. However, I would like
it deposited in the $basedir/some_arbitrary_location
directory? Can I configure the directory where the files
are deposited or am I off in the weeds and there is an
easier way?
Thank you,
Perry Hoekstra
---------------------------------------------------------------------
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]
