> On Aug 30, 2017, at 11:20 AM, Gary Gregory wrote:
>
> Hi Rob,
>
> Since we are re-rolling, may I ask that the release notes be updated since
> they currently state "This is the first stable release of Jelly", which it
> is now the second.
>
> Also, should we add a BUILDING.md and a CONTRIBU
Hi Rob,
Since we are re-rolling, may I ask that the release notes be updated since
they currently state "This is the first stable release of Jelly", which it
is now the second.
Also, should we add a BUILDING.md and a CONTRIBUTING.md?
Since there are some old tools at play, better building docs w
> On Aug 30, 2017, at 10:51 AM, Gary Gregory wrote:
>
> The src zip contains a "_MAXOSX" folder. Surely we do not need that.
Agreed. Cancelling. I will roll an RC3 in the coming days.
My vote is a -1.
>
> Gary
>
> On Tue, Aug 29, 2017 at 8:18 AM, Rob Tompkins wrote:
>
>> Hello,
>>
>> Comm
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
ues. The manual
nature of it made it a tad overwhelming keeping track of all of the changes
that I needed to make, and I tend to err on the side of minimal change. So,
seeing the RELEASE-NOTES.txt issues I’m ok with making another go at it.
Thoughts everyone?
-Rob
>
> The only issue that concerns
Bruno
From: Rob Tompkins
To: Commons Developers List
Sent: Wednesday, 30 August 2017, 2:18:26 AM NZST
Subject: Release Commons Jelly 1.0.1 Based on RC2
Hello,
Commons Jelly 1.0.1 R2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jel
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
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
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 needs to get an environment for building and testing the
release candidate, I have created a docker container such that if you are
currently in
