Hi Benedikt,
An RC normally has a sry src and bin zips and tars. I usually test based on
a src zip.
Gary
On Sun, Oct 2, 2016 at 8:23 AM, Benedikt Ritter wrote:
> Hi,
>
> a long time has passed since we released Apache Commons Lang 3.4. We fixed
> quite a few bugs and
Hello Pascal,
no I think I'll be able to resolve the conflicts when I merge the release
branch.
Thank you!
Hi Benedikt,
sorry.
Shall I revert the changes?
-Pascal
Am 02.10.2016 um 18:47 schrieb Benedikt Ritter:
Hi Pascal,
please don't modify changes.xml for 3.5. I've already created 3.5 RC1 and
this will cause trouble when merging the release branch back to Master.
Thank you
Benedikt
Hi Pascal,
please don't modify changes.xml for 3.5. I've already created 3.5 RC1 and
this will cause trouble when merging the release branch back to Master.
Thank you
Benedikt
schrieb am So. 2. Okt. 2016 um 18:23:
> Repository: commons-lang
> Updated Branches:
>
Hi,
since no development has happened for a long while, the Apache Commons EL
component has been moved to dormant. No further development is expected.
Please refer to Commons EL successor which is developed at the Apache
Tomcat project: http://svn.apache.org/repos/asf/tomcat/trunk/java/javax/el/
Hi,
a long time has passed since we released Apache Commons Lang 3.4. We fixed
quite a few bugs and introduced some nice new features. For this reason,
I'd like to call a vote for releasing Apache Commons Lang 3.5 based on RC1.
Commons Lang 3.5 RC1 is available for review here:
Hi.
On Thu, 29 Sep 2016 11:48:29 +0100, Stian Soiland-Reyes wrote:
Having all modules in the project have the same is just a
convention.
That's not what I've been told.
Anyways, I agree that interdependent modules _of the same project_
should preferably share the same version number.
It