tbee wrote:
>
> - include bootstrap-1.0.jar as a resource in plugin-1.0.jar, so it can be
> opened as a resource when the plugin runs
That was easy; first use the maven-dependency-plugin to put all dependencies
in a separate folder and then configure a resource including only the one
jar.
--
Stephen Connolly-2 wrote:
>
> fetching the artifact directly can cause issues when you want to use the
> release plugin if the artifact you want to fetch is part of the reactor
> you
> are fetching.
>
The plugin knows it requires "bootstrap-1.0.jar"; it needs to fetch it
somehow, unpack it an
fetching the artifact directly can cause issues when you want to use the
release plugin if the artifact you want to fetch is part of the reactor you
are fetching.
if you will always be releasing this artifact separately from the "onejar"
projects, then you can fetch it directly
if you will have d
I'm well on my way in creating my first Maven plugin. One unexpected
behavior, but I've coded around that. But what I require now is some what
deviating; the plugin creates a special jar similar to onejar, containing
all files that are required at runtime as a single deliverable.
Naturally there
