On Aug 16, 2010, at 5:24 PM, Justin Edelson wrote:
Can you think of any potential
problems in binding build-helper to the deploy phase instead? Thanks,
Well, that would mean the artifacts never end up in your local
repository, which seems weird.
Good point, but in this case the artifacts
On Aug 16, 2010, at 5:19 PM, Trevor Harmon wrote:
On Aug 16, 2010, at 5:04 PM, Justin Edelson wrote:
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
Thanks, that looks like just what I need.
I experimented some more with this issue, and it turns out I don't
On 17 August 2010 16:33, Trevor Harmon tre...@vocaro.com wrote:
On Aug 16, 2010, at 5:19 PM, Trevor Harmon wrote:
On Aug 16, 2010, at 5:04 PM, Justin Edelson wrote:
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
Thanks, that looks like just what I need.
I
Hi,
My project is a Java GUI app, and when I deploy it, its JAR artifact
is uploaded to the repository. I also use a couple of plugins to
generate platform-specific executables for the app: launch4j [1] and
osxappbundle [2]. I'd like to deploy these executables to the
repository too, so
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
On 8/16/10 8:03 PM, Trevor Harmon wrote:
Hi,
My project is a Java GUI app, and when I deploy it, its JAR artifact is
uploaded to the repository. I also use a couple of plugins to generate
platform-specific
On Aug 16, 2010, at 5:04 PM, Justin Edelson wrote:
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
Thanks, that looks like just what I need.
The only problem is that it binds by default to the package phase,
which would require binding the launch4j and
On 8/16/10 8:19 PM, Trevor Harmon wrote:
On Aug 16, 2010, at 5:04 PM, Justin Edelson wrote:
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
Thanks, that looks like just what I need.
The only problem is that it binds by default to the package phase, which
