[ X ] +1 Release these artifacts
Maven build passing OK from tag + svn revision with environment:
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_171, vendor: Oracle Corporation
Java home: /usr
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Configuration 2.2 was released, so I would like to
release Apache Commons Configuration 2.3.
Apache Commons Configuration 2.3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/com
Many thanks, this did the trick!
Oliver
Am 28.07.2018 um 20:29 schrieb Gary Gregory:
> - Make sure the dev dist folder is EMPTY before you start.
> - mvn -Dcommons.release-plugin.version=1.4-SNAPSHOT
> org.apache.commons:commons-release-plugin:1.4-SNAPSHOT:vote-txt
>
> Gary
>
> On Sat, Jul 28,
- Make sure the dev dist folder is EMPTY before you start.
- mvn -Dcommons.release-plugin.version=1.4-SNAPSHOT
org.apache.commons:commons-release-plugin:1.4-SNAPSHOT:vote-txt
Gary
On Sat, Jul 28, 2018 at 9:21 AM Oliver Heger
wrote:
> Hi,
>
> for the 2.3 release of [configuration] I am trying ou
Github user grimreaper commented on the issue:
https://github.com/apache/commons-collections/pull/48
IMHO yes, though that should be done separately.
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
Hi,
for the 2.3 release of [configuration] I am trying out the cool release
plugin.
Everything works fine, but I get a build failure when it adds the site
to SVN (see below). Do I have to prepare something in the dist area
before this can be done?
And another question: How can I generate such a
Github user soc commented on the issue:
https://github.com/apache/commons-collections/pull/48
@grimreaper Would it make sense in general to also annotate interfaces that
just duplicate the ones in `java.util.function` with `@Deprecated`?
---
-
