Olivier, go ahead. I think all issues which could be solved within this
time frame are fixed now.
maybe we get some feedback on MSHADE-244, I'll leave it up to you if you
want to wait for it (it is the only issue marked as blocker).
Robert
[1] https://issues.apache.org/jira/browse/MSHADE-2
Hi Olivier,
that's good. Let me work on the usage of maven-artifact-transfer and
remove the maven-compat dependency at compile time.
thanks,
Robert
On Tue, 17 Jan 2017 21:03:42 +0100, Olivier Lamy wrote:
Hi
I'd like to release the shade plugin next week.
Let me know if someone has any con
Hi
I'd like to release the shade plugin next week.
Let me know if someone has any concerns with that?
Cheers
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Hi,
I'd like to release shade plugin next week (only 1 new feature)
Let me know if any issues.
Cheers,
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-
Hello,
Folks from Apache Xml need a release of Shade plugin for the blocking
issue MSHADE-105.
As there is not a lot of fixes, I will probably change the version to 1.5.1 .
So except if someone complains :-), I will start release process for
the plugin later this week.
Thanks,
--
Olivier Lamy
Ta
Daniel Kulp wrote:
Crap. Second time I've done this in the last couple weeks. :-( Why
the 1.5 javac doesn't flag these things with source/targe set to 1.4 is
beyond me. Eclipse doesn't even flag them when using 1.5 but project
is set to 1.4.
That said, I just figured out how to get the
Crap. Second time I've done this in the last couple weeks. :-( Why
the 1.5 javac doesn't flag these things with source/targe set to 1.4 is
beyond me. Eclipse doesn't even flag them when using 1.5 but project
is set to 1.4.
That said, I just figured out how to get the eclipse project to
Vincent Siveton wrote:
-1 due to compilation failure with jdk1.4 on tag.
http://rafb.net/p/jVfAXG92.html
Right - I thought the maven plugins parent POM would have fixed the
target/source JDK to 1.4.
I'd continue with vote (would avoid issuing another one) and fix JDK
compat before releasin
-1 due to compilation failure with jdk1.4 on tag.
http://rafb.net/p/jVfAXG92.html
Vincent
2007/12/12, Mauro Talevi <[EMAIL PROTECTED]>:
> Following fixes, new version 1.0-alpha-15 has been staged for release.
> Please for vote for its release and to move this version of the sandbox
> (and start d
+1
--jason
-Original Message-
From: Daniel Kulp <[EMAIL PROTECTED]>
Date: Wed, 12 Dec 2007 12:00:48
To:dev@maven.apache.org
Subject: Re: [Vote][take 2] maven-shade-plugin release 1.0-alpha-15 and move
out of sandbox
+1 to both the release and moving out of sandbox.
L
+1 to both the release and moving out of sandbox.
Looking forward to this.. :-)
Dan
On Wednesday 12 December 2007, Mauro Talevi wrote:
> Following fixes, new version 1.0-alpha-15 has been staged for release.
> Please for vote for its release and to move this version of the
> sandbox (and start
+1
--
Olivier
2007/12/12, Mauro Talevi <[EMAIL PROTECTED]>:
>
> Following fixes, new version 1.0-alpha-15 has been staged for release.
> Please for vote for its release and to move this version of the sandbox
> (and start dev of 1.0-beta-1-SNAPSHOT).
>
>
> Staging area:
> http://people.apache.org/
+1 (for sure, this time!)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Following fixes, new version 1.0-alpha-15 has been staged for release.
Please for vote for its release and to move this version of the sandbox
(and start dev of 1.0-beta-1-SNAPSHOT).
Staging area:
http://people.apache.org/~mauro/staging-repo/
Tag:
http://svn.apache.org/repos/asf/maven/plugins
Brian E. Fox wrote:
It would be cool if you could try the new candidate on 2.0.x also. I had
trouble with it excluding tons of stuff when I did 2.0.8. I can try it
later today if you can't.
Built a 2.0.9 snapshot and try it out on a sample projects.
No problems encountered. So it does look pr
Daniel Kulp wrote:
OK. I fixed one more issue with it. Can you give it another try. :-)
Getting closer.
Yup, looks good to me. I've closed MSHADE-5 again.
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additi
: dev@maven.apache.org
Cc: Dan Fabulich
Subject: Re: Changed vote Re: [Vote] maven-shade-plugin release
1.0-alpha-14 and move out of sandbox
OK. I fixed one more issue with it. Can you give it another try. :-)
Getting closer.
Dan
On Tuesday 11 December 2007, Dan Fabulich wrote:
> Fixed o
OK. I fixed one more issue with it. Can you give it another try. :-)
Getting closer.
Dan
On Tuesday 11 December 2007, Dan Fabulich wrote:
> Fixed on my end (I think... this bug is finicky); try it on your end
> to make sure I didn't break anything further?
>
> -Dan
>
> Dan Fabulich wro
Fixed on my end (I think... this bug is finicky); try it on your end to
make sure I didn't break anything further?
-Dan
Dan Fabulich wrote:
Daniel Kulp wrote:
I changed the rename logic to do a whole bunch of fallback things if the
first rename fails. It first will try a gc to see if any
Mauro Talevi wrote:
I've commented on MSHADE-7 - as far as I can tell, feature is already
implemented, via shadedArtifact attachment. Please try out the configuration
in:
MSHADE-7 is a very different feature from shadedArtifactAttached.
MSHADE-7 suggests that the generated classes just get
Daniel Kulp wrote:
I changed the rename logic to do a whole bunch of fallback things if the
first rename fails. It first will try a gc to see if any Streams that
are holding it locked can be cleaned up. If that still fails, then it
will just copy the new file over the old file. Not ideal, b
Dan,
Can you try a deploy with 1.0-alpha-15-SNAPSHOT?
I changed the rename logic to do a whole bunch of fallback things if the
first rename fails. It first will try a gc to see if any Streams that
are holding it locked can be cleaned up. If that still fails, then it
will just copy the new
Dan Fabulich wrote:
Uh, actually, I need to turn my vote to a -1. :-( I just discovered that
I'm being bitten by MSHADE-5 (and MSHADE-6) every time I go to deploy
the Surefire 2.4-SNAPSHOT. As a result, I deployed a corrupted
SNAPSHOT... yuck!
I just fixed MSHADE-6 in the sandbox, which wo
Uh, actually, I need to turn my vote to a -1. :-( I just discovered that
I'm being bitten by MSHADE-5 (and MSHADE-6) every time I go to deploy the
Surefire 2.4-SNAPSHOT. As a result, I deployed a corrupted SNAPSHOT...
yuck!
I just fixed MSHADE-6 in the sandbox, which would have at least pre
+1. This works with the latest Surefire trunk. (It's a pity MSHADE-9 is
still broken, but I think it's OK for another alpha; we should fix it for
beta-1.)
-Dan
Mauro Talevi wrote:
As version 1.0-alpha-14 has been staged for release, I'd like to call a vote
for its release and the move out
As version 1.0-alpha-14 has been staged for release, I'd like to call a
vote for its release and the move out of the sandbox and to version
1.0-beta-1-SNAPSHOT.
Staging area:
http://people.apache.org/~mauro/staging-repo/
Tag:
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-shade-plug
26 matches
Mail list logo
