On Jul 17, 2008, at 11:33 AM, Jason van Zyl wrote:
On 17-Jul-08, at 11:27 AM, Daniel Kulp wrote:
On Jul 17, 2008, at 11:23 AM, Jason van Zyl wrote:
I'll make sure, but that would work by default as if you knew the
manifest in one of your JARs had the main-class entry you wouldn't
be sp
On 17-Jul-08, at 11:27 AM, Daniel Kulp wrote:
On Jul 17, 2008, at 11:23 AM, Jason van Zyl wrote:
I'll make sure, but that would work by default as if you knew the
manifest in one of your JARs had the main-class entry you wouldn't
be specifying it in the shade plugin.
Right, but if manif
On Jul 17, 2008, at 11:23 AM, Jason van Zyl wrote:
I'll make sure, but that would work by default as if you knew the
manifest in one of your JARs had the main-class entry you wouldn't
be specifying it in the shade plugin.
Right, but if manifest entries can come from two places, we need to
Maybe I'll make the transformers like the enforcers where they are
components that can be configured.
I could see just specifying the main-class ignoring everything else,
or allowing merging or selectively looking for an artifact which
contained the MANIFEST you wanted to win.
On 17-Jul-0
I'll make sure, but that would work by default as if you knew the
manifest in one of your JARs had the main-class entry you wouldn't be
specifying it in the shade plugin.
On 17-Jul-08, at 11:17 AM, Daniel Kulp wrote:
In general, we let the stuff that executes prior to the Shade plugin
ha
In general, we let the stuff that executes prior to the Shade plugin
handle the manifest.That might be the jar plugin, but it could be
something else like the felix bundle plugin.
I guess that would be the important thing: make sure the above
scenario still works correctly.
On Jul 1
I was just thinking about wiring in the shade plugin for the
jetty-runner (starts up wars, etc from the cli) this morning and that
would definitely require this ability...trying to remember how I did
it in the past I think I just added it manually and managed the
MANIFEST.MF but that is a nasty fil
Hi,
I was looking through JIRA and the source and there doesn't seem to be
an easy way to create an executable JAR. I don't want to add JAR
plugin configuration to set the class I want to use for "java -jar
pooky.jar".
Anyone else thought about this?
I want to add a simple configuration
