Re: [release-plugin] fail when dist dev folder already contains source and binaries folders

Yeah. That makes some sense. Still in the polishing stage :-) . I’ll do that after the [rng] release. -Rob > On Jul 7, 2018, at 8:16 PM, Gary Gregory wrote: > > Hi Rob, > > I just tripped over this when trying to create for Commons Collections 4.2 > RC1: The release plugin fails during *stag

[VOTE] Release Apache Commons Collections 4.2 based on RC1

We have fixed quite a few bugs and added some significant enhancements since Apache Commons Collections 4.1 was released, so I would like to release Apache Commons Collections 4.2. Apache Commons Collections 4.2 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/c

Fwd: Build failed in Jenkins: commons-dbcp #262

Any ideas on how to solve this? -- Forwarded message - From: Apache Jenkins Server Date: Sun, Jul 8, 2018, 12:34 Subject: Build failed in Jenkins: commons-dbcp #262 To: See < https://builds.apache.org/job/commons-dbcp/262/display/redirect?page=changes > Changes: [garydgregory

[DBCP] Ready for Java 8, JDBC 4.2, as version 2.5.0.

Hi All: DBCP in git master is, I think, ready for Java 8, JDBC 4.2, as version 2.5.0. Let me know if you want me to delay releasing for you to add features/verify git master in your environment. Gary

[BeanUtils] Release 2.0.0 soonish

Hi All: Once I am done with releasing Commons Collections 4.2, I plan on releasing Commons BeanUtils 2. This will be a major version change due to the update from Commons Collections 3 to 4. If you want to change BeanUtils so that Commons Collections classes are NOT surfaced in the BeanUtils pub

Re: Build failed in Jenkins: commons-dbcp #262

Ask on the builds mailing list On 8 July 2018 at 20:14, Gary Gregory wrote: > Any ideas on how to solve this? > > -- Forwarded message - > From: Apache Jenkins Server > Date: Sun, Jul 8, 2018, 12:34 > Subject: Build failed in Jenkins: commons-dbcp #262 > To: > > > See < > https: