+1, shading of a released jar should be preferred.
But there are many solutions for deliberately using a pre-release. maven
scm plugin for instance, or using the GitHub mirror's svn view.
(Also +1 for move to git)
On 12 Jul 2016 8:01 a.m., "Jochen Wiedmann"
wrote:
>
+1
Gary
On Sun, Jul 10, 2016 at 3:45 AM, Jochen Wiedmann
wrote:
> Hello,
>
> I'd like to call a VOTE by LAZY
> consensus for migrating the Apache Commons Fileupload component to git.
> Please
> object to this vote if you see a problem with this. Otherwise this vote
>
Hi, Konstantin,
I can think of no reason, why it should be desirable to maintain a
fork, rather than simply using the release jar. I strongly suggest,
that Tomcat stops doing so, for examply by shading the jar, if the
package names might be the problem.
If required, I am quite ready to help with
I am -1 because this code is copied into Apache Tomcat, I think such
migration will impede maintenance of the fork.
https://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/tomcat/util/http/fileupload/
See svn:mergeinfo at the bottom of the page.
I am not on Commons PMC though,
The same for
+1 for Git
--
http://bernd.eckenfels.net
-Original Message-
From: Jochen Wiedmann <jochen.wiedm...@gmail.com>
To: Apache Commons Developers List <dev@commons.apache.org>
Sent: So., 10 Juli 2016 12:46
Subject: [VOTE][LAZY] Migrate Apache Commons Fileupload to Git
Hell
Hello,
I'd like to call a VOTE by LAZY
consensus for migrating the Apache Commons Fileupload component to git. Please
object to this vote if you see a problem with this. Otherwise this vote
will be considered as passed after 72 hours from now (10th June 2016, 09:00
CET)
Thank you,
Jochen
--