RE: [CRYPTO]1.0.0 Release Plan

2016-07-12 Thread Sun, Dapeng
Copy the native files from other platforms to target is worked. I also uploaded a SNAPSHOT version contains native of Linux and Mac. If there is no concerns, I will try to add windows and kick off the first release. https://repository.apache.org/content/repositories/snapshots/org/apache/commons/

Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC8

2016-07-12 Thread Jörg Schaible
+1, build from source tar ball works with my compiler zoo. Benedikt Ritter wrote: > Hi all, > > hopefully the final RC for releasing Apache Commons BCEL 6.0 :-) Changes > since RC7: > > - fixed failing build on Windows plattforms > - corrected fix for BCEL-262 > > Apache Commons BCEL 6.0 is av

ApacheCon EU 2016

2016-07-12 Thread Benedikt Ritter
Dear Apache Enthusiast, As you are no doubt already aware, we will be holding ApacheCon in Seville, Spain, the week of November 14th, 2016. The call for papers (CFP) for this event is now open, and will remain open until September 9th. The event is divided into two parts, each with its own CFP. T

Re: [CRYPTO]1.0.0 Release Plan

2016-07-12 Thread sebb
On 12 July 2016 at 14:54, sebb wrote: > On 12 July 2016 at 14:20, Sun, Dapeng wrote: >> Separating artifacts for each native library, I think it should be same as >> copying the native binary files. We also need to collect the artifacts for >> unpacking and bundling. > > Yes. > >> About using t

Re: [CRYPTO]1.0.0 Release Plan

2016-07-12 Thread sebb
On 12 July 2016 at 14:20, Sun, Dapeng wrote: > Separating artifacts for each native library, I think it should be same as > copying the native binary files. We also need to collect the artifacts for > unpacking and bundling. Yes. > About using the 'all' artifact, users may be confused about do

RE: [CRYPTO]1.0.0 Release Plan

2016-07-12 Thread Sun, Dapeng
Separating artifacts for each native library, I think it should be same as copying the native binary files. We also need to collect the artifacts for unpacking and bundling. About using the 'all' artifact, users may be confused about downloading the artifacts for all the different platforms, es

RE: [CRYPTO]1.0.0 Release Plan

2016-07-12 Thread Sun, Dapeng
I think we can copy the native binary files complied by different platforms, and put them into target folder. Then all the native files would be packaged into one jar. Okay, I will build a SNAPSHOT contains Linux and Mac. Regards Dapeng -Original Message- From: sebb [mailto:seb...@gma

Re: [VOTE] Release Apache Commons BCEL 6.0 based on RC8

2016-07-12 Thread Olivier Lamy
+1 Thanks to keep groupId:artifactId. It's so simple to override the dependency in a maven plugin and to get it work with 1.8. Thanks!! On 11 July 2016 at 06:57, Benedikt Ritter wrote: > Hi all, > > hopefully the final RC for releasing Apache Commons BCEL 6.0 :-) Changes > since RC7: > > - fixe

Re: [VOTE][LAZY] Migrate Apache Commons Fileupload to Git

2016-07-12 Thread Jochen Wiedmann
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