Re: [VOTE][LAZY] Move commons-imaging to git

+1 On 05/19/2017 10:03 AM, Amey Jadiye wrote: +1 On May 18, 2017 10:52 PM, "Rob Tompkins" wrote: Hello all, I would like to propose that we move commons-imaging to git in hopes of doing that before the potential of releasing a 1.0. I figure that it would be an easier migration with only a

Re: [JELLY] State of the project (Was: [VOTE][LAZY] Move Apache Commons Jelly to dormant)

Jenkins recently moved to 1.8 too, so whichever version we choose to use should be fine. If the consensus is to cut a release now with fewer changes, followed by another release with 1.8 I'd be fine as well. Once the project is ready to be released again, I'll look into the issues applied to th

Re: [JELLY] State of the project (Was: [VOTE][LAZY] Move Apache Commons Jelly to dormant)

On 19 May 2017 at 22:02, Gary Gregory wrote: > On Fri, May 19, 2017 at 12:50 PM, Oliver Heger > wrote: > >> Hi, >> >> thank you for looking into this. >> >> Am 18.05.2017 um 16:46 schrieb Benedikt Ritter: >> > Hi, >> > >> >> Am 17.05.2017 um 19:38 schrieb Gary Gregory : >> >> >> >> I think that we

Re: svn commit: r1795551 - /commons/proper/commons-parent/trunk/pom.xml

Ah okay, gotcha! I've looked at the site plugin docs and there are no special intructions for migrating to 3.6 line. Regards, Benedikt Gary Gregory schrieb am Fr. 19. Mai 2017 um 17:04: > On Fri, May 19, 2017 at 1:49 PM, Benedikt Ritter > wrote: > > > Hello Gary, > > > > > Am 18.05.2017 um 17

Re: [REMINDER][VOTE] Release Apache Commons Lang 3.6 based on RC2

On Fri, May 19, 2017 at 1:52 PM, Benedikt Ritter wrote: > Hello, > > > Am 17.05.2017 um 12:02 schrieb Benedikt Ritter : > > > > Hello, > > > > we have fixed quite a few bugs and added some nice new features since > Commons Lang 3.5 was released, so I would like to release Commons Lang 3.6 > based

Re: svn commit: r1795551 - /commons/proper/commons-parent/trunk/pom.xml

On Fri, May 19, 2017 at 1:49 PM, Benedikt Ritter wrote: > Hello Gary, > > > Am 18.05.2017 um 17:00 schrieb Gary Gregory : > > > > Since the current version of maven-site-plugin is 3.6, it would be nice > to > > note what happens for that version as well. > > I was just removing trailing white spa

Re: [JELLY] State of the project (Was: [VOTE][LAZY] Move Apache Commons Jelly to dormant)

On Fri, May 19, 2017 at 12:50 PM, Oliver Heger wrote: > Hi, > > thank you for looking into this. > > Am 18.05.2017 um 16:46 schrieb Benedikt Ritter: > > Hi, > > > >> Am 17.05.2017 um 19:38 schrieb Gary Gregory : > >> > >> I think that we could, as a community test of interest, say something > lik

[REMINDER][VOTE] Release Apache Commons Lang 3.6 based on RC2

Hello, > Am 17.05.2017 um 12:02 schrieb Benedikt Ritter : > > Hello, > > we have fixed quite a few bugs and added some nice new features since Commons > Lang 3.5 was released, so I would like to release Commons Lang 3.6 based on > RC2. > The reason we had to cut a second release is, that there

Re: svn commit: r1795551 - /commons/proper/commons-parent/trunk/pom.xml

Hello Gary, > Am 18.05.2017 um 17:00 schrieb Gary Gregory : > > Since the current version of maven-site-plugin is 3.6, it would be nice to > note what happens for that version as well. I was just removing trailing white spaces and don’t know what you’re talking about :o) Benedikt > > Gary >

Re: [JELLY] State of the project (Was: [VOTE][LAZY] Move Apache Commons Jelly to dormant)

> Am 19.05.2017 um 15:50 schrieb Oliver Heger : > > Hi, > > thank you for looking into this. > > Am 18.05.2017 um 16:46 schrieb Benedikt Ritter: >> Hi, >> >>> Am 17.05.2017 um 19:38 schrieb Gary Gregory >> >: >>> >>> I think that we could, as a community test of

Re: [JELLY] State of the project (Was: [VOTE][LAZY] Move Apache Commons Jelly to dormant)

Hi, thank you for looking into this. Am 18.05.2017 um 16:46 schrieb Benedikt Ritter: > Hi, > >> Am 17.05.2017 um 19:38 schrieb Gary Gregory : >> >> I think that we could, as a community test of interest, say something like, >> if Oliver wants to push out what is in trunk in the next 30 days or s

[VOTE] Release Commons Text 1.1 based on RC1

Hello all, This is a [VOTE] for releasing Apache Commons Text 1.1 (from RC1). Tag name: commons-text-1.1-RC1 (signature can be checked from git using 'git tag -v') Tag URL: https://git-wip-us.apache.org/repos/asf?p=commons-text.git;a=commit;h= 206931af2ad7084044aba19591a5034b634c23b1 Comm

Re: [VOTE][LAZY] Move commons-imaging to git

+1 On Thu, May 18, 2017 at 7:22 PM, Rob Tompkins wrote: > Hello all, > > I would like to propose that we move commons-imaging to git in hopes of > doing that before the potential of releasing a 1.0. I figure that it would > be an easier migration with only a trunk to manage in getting it over th

Re: [VOTE][LAZY] Move commons-imaging to git

+1 On May 18, 2017 10:52 PM, "Rob Tompkins" wrote: > Hello all, > > I would like to propose that we move commons-imaging to git in hopes of > doing that before the potential of releasing a 1.0. I figure that it would > be an easier migration with only a trunk to manage in getting it over there.

JDK 9 EA Build 170 is available on jdk.java.net

Hi Benedikt, * JDK 9 Early Access* build 170 is available at the new location : - jdk.java.net/9/ A summary of all the changes in this build are listed here . Changes which were introduced since the last availability email that m

Re: [PARENT][PROPOSAL] Add Automatic-Module-Name MANIFEST entry

Is reusing ${commons.osgi.symbolicName} a good idea? It seems to me that each project should have to opt-in to this attribute, so I'd add a new ${commons.automatic.moduile.name} variable. One reason is that the attribute should only be added if the project is suitable for use as a module (eg. no p

Re: [IMAGING] Why don't we just release it?

+1 , went through the code seems we can have all the feature in future releases and ATM seems stable API's so can release 1.0 Also, as this will be the very first release we should keep code and build clean which sets protocol for future releases. so atleast test apache-rat:check clirr:check chec