Hi guys,
due to the RCx procedure we cant use the maven release plugin, any
plan to make it working with commons release procedure or do we just
wait to move all to git?
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
---
Answers inline.
2017-11-06 7:08 GMT+01:00 Gary Gregory :
> The blocker part is that the VOTE email does not follow the process or the
> format outlined on http://commons.apache.org/releases/prepare.html
>
> Specifically,
> - the tag does not contain an "RC2" postfix (since this is the 2nd RC).
> -
The blocker part is that the VOTE email does not follow the process or the
format outlined on http://commons.apache.org/releases/prepare.html
Specifically,
- the tag does not contain an "RC2" postfix (since this is the 2nd RC).
- there is not tag for RC1 so we've lost what we voted on for RC1 (too
Dist/Nexus is a manual step but ok. Rc creation is a blocker since it
prevent to use maven tools - release plugin. Did we - as commons - already
open a feature request to maven?
Anyway dont think it blocks the release *now* so can we proceed?
Also moving to git can solve it by design too since we
I probably can, yeah. Totally slipped my mind about this, though!
On 5 November 2017 at 21:46, Gary Gregory wrote:
> Hi Matt,
>
> Any chance you get take a look this week?
>
> Gary
>
> On Tue, Oct 31, 2017 at 10:58 AM, Mark Thomas wrote:
>
> > On 31/10/17 14:44, Gary Gregory wrote:
> > > On Tue
On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter wrote:
>
>
> > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl :
> >
> > Hi Gary,
> >
> > On 25.10.17 05:24, Gary Gregory wrote:
> >> Our process documented here http://commons.apache.org/
> releases/prepare.html
> >> makes it pretty clear that the R
On Fri, Oct 27, 2017 at 4:51 AM, Thomas Vandahl wrote:
> Hi Gary,
>
> On 25.10.17 05:24, Gary Gregory wrote:
> > Our process documented here http://commons.apache.org/
> releases/prepare.html
> > makes it pretty clear that the RC tag should be labeled as such and that
> a
> > tag like "commons-jc
Hi Matt,
Any chance you get take a look this week?
Gary
On Tue, Oct 31, 2017 at 10:58 AM, Mark Thomas wrote:
> On 31/10/17 14:44, Gary Gregory wrote:
> > On Tue, Oct 31, 2017 at 8:33 AM, Matt Sicker wrote:
> >
> >> On 31 October 2017 at 04:21, Mark Thomas wrote:
> >>>
> >>> If the methods ar
My +1
Gary
On Sat, Nov 4, 2017 at 12:50 PM, Gary Gregory
wrote:
> We have fixed a few bugs since Apache Commons Lang 3.6 was released, so I
> would like to release Apache Commons Lang 3.7.
>
> Apache Commons Lang 3.7 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev
On Sat, Nov 4, 2017 at 9:54 AM, Pascal Schumacher
wrote:
> Sorry if I haven't made myself clear. I was speaking of already commited
> fixes (I'm not currently planning/working on any new ones.)
Thank you for clarifying! I like clarity :-) We can loose so much in email
comms.
Gary
>
>
> Am 04
I still have some code lying around in this area. Need refreshing though :
http://mvdb.org/projects/beanunit/
It tests getters and setters automagically.
Maybe because of the magic code involved the code is not very "clean"
and maybe not suitable for a commons test component.
Mvgr,
Martin
On Sa
I don't know if this fits but I have junit-contract-testing (
https://github.com/Claudenw/junit-contracts) that I would like to
contribute.
It is an extension that performs contract tests for java interface
implementations.
Cluade
On Fri, Nov 3, 2017 at 11:11 PM, Gary Gregory
wrote:
> Hi All,
>The PR is about 1.5 weeks old, so we should still give him some more time.
+1
>Do you know him in person, Bruno? Or did you have contact with him in the past?
He helped me to organize the Brazilian Jenkins mailing list, and the two first
conferences in Brazil. He flew there to help organize an
@Mark: this is already not the case and users are used to gather them
putside Junit. Also it is pby as true as saying it would be easier to push
commons in openjdk directly no?
I see a lot of values to have a uniform backbone - rule API - and making it
easy to reuse accross test stacks so commons
Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.
+1
Oliver
Am 04.11.2017 um 19:50 schrieb Gary Gregory:
> We have fixed a few bugs since Apache Commons Lang 3.6 was released, so I
> would like to release Apache Commons Lang 3.7.
>
> Apache Commons Lang 3.7 RC1
Just out of curiosity, wouldn't it be easier (and more intuitive) for users
of JUnit to find a collection of JUnit-related tools on the JUnit project
site?
Regards,
Mark
On 5 Nov 2017 11:51 a.m., "Romain Manni-Bucau"
wrote:
> This is a bit different since my case was to get annoutput of where
This is a bit different since my case was to get annoutput of where a test
can lock and not a diff. But technically it is close.
Le 5 nov. 2017 20:21, "Bernd Eckenfels" a écrit :
> Hello,
>
>
> commons-vfs does this (at the Moment it only dumps the threads and does
> not break the build)
>
> htt
Hello,
commons-vfs does this (at the Moment it only dumps the threads and does not
break the build)
https://github.com/apache/commons-vfs/blob/trunk/commons-vfs2/src/test/java/org/apache/commons/vfs2/test/AbstractTestSuite.java#L213
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Romain Mann
Am 02.11.2017 um 00:33 schrieb Bruno P. Kinoshita:
> I think it may be worth to try to get in touch with Kohsuke. He became the
> CTO of CloudBees some time ago, but is still involved in the project (not
> writing as much code as before) mainly with decisions, and eventual pull
> request revie
It sounds like we all like the idea of this new component. I'll create the
git repo tonight or by tomorrow morning at the latest.
Gary
On Sun, Nov 5, 2017 at 8:30 AM, Romain Manni-Bucau
wrote:
> This daemon thing is interesting, I something similar to dump each N
> seconds threads to investigat
This daemon thing is interesting, I something similar to dump each N
seconds threads to investigate some tests locking on a CI. Can goes
there as well probably.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-11-05 16:23 GMT+01:00 Gary Gregory :
> On Sat, Nov 4, 2017
[PROPOSAL REDUX]
Component Name: Apache Commons Testing
A multi-module project focused on providing code for testing applications
using various testing frameworks with an initial focus on JUnit 4.
Modules:
commons-testing: no dependencies, contains code like to list all non-daemon
threads after
On Sat, Nov 4, 2017 at 11:12 AM, Gary Gregory
wrote:
> So are you advocating for a multi-module project?
>
> - commons-testing
> - commons-testing-junit4
> - commons-testing-junit5
>
> ?
>
> Gary
>
>
> On Sat, Nov 4, 2017 at 10:58 AM, Bernd Eckenfels
> wrote:
>
>> I like the idea (and prefer Com
On Sat, Nov 4, 2017 at 1:44 AM, Romain Manni-Bucau
wrote:
> Looks like a good idea but wonder if it fits commons. I kind of see a lot
> of modules already so maybe incubator?
>
> Ps: if interesting I m happy to give
> https://github.com/rmannibucau/rule-them-all and help integrating it with
> jun
GitHub user mmariotti opened a pull request:
https://github.com/apache/commons-io/pull/49
[IO-554] fixed: prevent input stream close
[IO-554] FileUtils.copyToFile(InputStream source, File destination) closes
input stream.
Fixed removing 'source' from try-with-resources.
You can
25 matches
Mail list logo
