Re: Release Commons Jelly 1.0.1 Based on RC2

2017-08-30 Thread Gary Gregory
The src zip contains a "_MAXOSX" folder. Surely we do not need that. Gary On Tue, Aug 29, 2017 at 8:18 AM, Rob Tompkins wrote: > Hello, > > Commons Jelly 1.0.1 R2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/jelly (svn revision > 21342) > > Note, if anyone ne

Re: Release Commons Jelly 1.0.1 Based on RC2

2017-08-30 Thread Rob Tompkins
> On Aug 30, 2017, at 1:22 AM, Bruno P. Kinoshita > wrote: > > Hi Rob, > Thanks for RM'ing Commons Jelly 1.0.1. Here's my initial tests results: > > Downloaded JDK from Oracle archives, version 5.0u22. > > Then downloaded Apache Ant following what was in the Dockerfile. > > curl > http:

Re: Release Commons Jelly 1.0.1 Based on RC2

2017-08-29 Thread Bruno P. Kinoshita
Hi Rob, Thanks for RM'ing Commons Jelly 1.0.1. Here's my initial tests results: Downloaded JDK from Oracle archives, version 5.0u22. Then downloaded Apache Ant following what was in the Dockerfile.     curl http://archive.apache.org/dist/ant/binaries/apache-ant-1.6.0-bin.tar.gz -o /tmp/apache-

Re: Release Commons Jelly 1.0.1 Based on RC2

2017-08-29 Thread Rob Tompkins
So I built everything using ant and manually uploaded everything to nexus using the existent pom.xml in nexus with the version number changed. The way I ran the build was in that docker container (essentially a VM) with a directory inside the container mounted to my project directory. That’s the

Re: Release Commons Jelly 1.0.1 Based on RC2

2017-08-29 Thread Gary Gregory
Hi Rob, Thank you for preparing the RC. I think we are going to need a little guidance as to how best test an RC based on such an old tool set. This is a Maven 1 project (I see maven.xml)? But I also see a pom.xml so it's confusing. No tests run when I use Maven 2 or 3. I can even get a Maven 1