The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 1.2.2.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies. See the plugin's site for
I can only speak from experience with what we have done here internally but I
can also attest that releasing too often is a real pain. You end up having a
bunch of releases publicized that no one cares about. It only serves to clutter
a repository and makes it confusing to consumers wrt which
Hi Brett,
I've been using the RC1 since your announcement with a couple of
projects without any problems.
Cheers,
Henrique
Brett Porter wrote:
Hi,
I have staged a first release candidate here:
The logic here is flawed because it is from a single
perspective of an
individual who finds it burdensome to validate each and every release.
It isn't just me. Both Paul and Brett expressed similar concerns ;-).
To keep this short, I simply disagree with Jason's assertion that a fix
should
On 2009-11-26, at 10:27 AM, Todd Thiessen wrote:
The logic here is flawed because it is from a single
perspective of an
individual who finds it burdensome to validate each and every
release.
It isn't just me. Both Paul and Brett expressed similar concerns ;-).
That's fine don't look at
On Nov 26, 2009, at 5:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here internally but I
can also attest that releasing too often is a real pain. You end up having a
bunch of releases publicized that no one cares about. It only serves to
clutter a
On Nov 26, 2009, at 5:56 AM, Jason van Zyl wrote:
On 2009-11-26, at 8:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here internally but
I can also attest that releasing too often is a real pain. You end up having
a bunch of releases publicized that
On 2009-11-26, at 11:04 AM, Ralph Goers wrote:
On Nov 26, 2009, at 5:04 AM, Todd Thiessen wrote:
I can only speak from experience with what we have done here
internally but I can also attest that releasing too often is a real
pain. You end up having a bunch of releases publicized that no
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Arnaud Héritier, Olivier
Lamy
+1 (non-binding): Nicolas De Loof, Stephen Connolly, Igor Fedorenko
I will promote the artifacts to the central repository and continue with
the release.
On 27/11/2009, at 2:27 AM, Todd Thiessen wrote:
The logic here is flawed because it is from a single
perspective of an
individual who finds it burdensome to validate each and every release.
It isn't just me. Both Paul and Brett expressed similar concerns ;-).
I don't think this was my
Issue Subscription
Filter: Design Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
11 matches
Mail list logo
