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 fr
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
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 n
dependency:unpack???
2009/3/30
> 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
Hi there.
I don't seem to get exactly what you want to accomplish, but it sounds
like this is what you want to do:
http://maven.apache.org/plugins/maven-dependency-plugin/examples/unpacking-artifacts.html
You can download a specific artifact from a repository and unpack it
to a certain dir
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
Jeff:
If it was a single file (ie. CheckStyle) I would have most likely gone down
the URL route. However, I
