Github user lewismc closed the pull request at:
https://github.com/apache/commons-rdf/pull/38
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Github user lewismc commented on the issue:
https://github.com/apache/commons-rdf/pull/39
+1 @ansell this fixes 62 and should therefore supersede #38
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
Github user ansell commented on a diff in the pull request:
https://github.com/apache/commons-rdf/pull/38#discussion_r138501891
--- Diff: README.md ---
@@ -102,6 +102,9 @@ Building has been tested with [Apache Maven
3.2](http://maven.apache.org/downloa
[INFO] Final Memory:
GitHub user ansell opened a pull request:
https://github.com/apache/commons-rdf/pull/39
COMMONSRDF-62 : Ignore japicmp by default while version is 0.x
japicmp is activated by commons-parent profile with it set to break the
build on any incompatibilities. In order to have it still ru
GitHub user lewismc opened a pull request:
https://github.com/apache/commons-rdf/pull/38
COMMONSRDF-62 japicmp-maven-plugin breaking build because there is atleast
one incompatibility
This issue addresses https://issues.apache.org/jira/browse/COMMONSRDF-62
You can merge this pull r
On Tue, 12 Sep 2017 13:07:24 +0200, Jochen Wiedmann wrote:
On Sat, Sep 2, 2017 at 12:50 AM, Gilles
wrote:
Because of "Commons" rules, it is not "equivalent": There was
a long thread concluding that all modules must be released
_together_, and with the same top-level package name and version
n
Hi Jochen,
Jochen Wiedmann wrote:
> On Sat, Sep 2, 2017 at 12:50 AM, Gilles
> wrote:
>
>> Because of "Commons" rules, it is not "equivalent": There was
>> a long thread concluding that all modules must be released
>> _together_, and with the same top-level package name and version
>> number.
>>
Github user kinow closed the pull request at:
https://github.com/apache/commons-collections/pull/26
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.o
Github user kinow commented on the issue:
https://github.com/apache/commons-collections/pull/26
Fixed in 1081b725bea339fcda33d70c71b9eb1859d60d8f and
6a10051a7b5b3c615180413fe116c61780754969. Thanks to @garydgregory !
---
-
Github user kinow closed the pull request at:
https://github.com/apache/commons-collections/pull/26
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.o
OK, the POM now uses ${commons.findbugs.version}.
Gary
On Tue, Sep 12, 2017 at 4:24 PM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:
> Hi Gary,
>
> Besides updating the parent to 42, the PR also changes the FindBugs
> version to use the version defined in the parent properties
Hi Gary,
Besides updating the parent to 42, the PR also changes the FindBugs version to
use the version defined in the parent properties. This way the `mvn site`
command passes on JVM 7 and 8. In case you have time to review it too :)
https://github.com/apache/commons-collections/pull/26
Just
I tried with both Java 7, 8 and 9 and I committed the change to
commons-parent 42 already.
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T13:39:06-06:00)
Maven home: C:\Java\apache-maven-3.5.0\bin\..
Java version: 1.7.0_80, vendor: Oracle Corporation
Java home: C:\Program
I built it last night with JVM 7 and the tests were passing (mvn clean site,
but confirmed surefire reports were OK).
Submitted a PR that updates common-parent to version 42 that should fix site
generation on JVM 8.
Could you share your `mvn -v` please?
CheersBruno
On Wed, 13 Sep 2017 at 3
Great news Benedikt!
Keep us posted :-)
Gary
On Tue, Sep 12, 2017 at 10:44 AM, Benedikt Ritter
wrote:
> Hi,
>
> BCEL-286 has now been resolved and I’m slowly working towards RC1.
>
> Regards,
> Benedikt
>
> > Am 30.08.2017 um 21:37 schrieb Benedikt Ritter :
> >
> > Hello,
> >
> > I’ve committe
Hi,
BCEL-286 has now been resolved and I’m slowly working towards RC1.
Regards,
Benedikt
> Am 30.08.2017 um 21:37 schrieb Benedikt Ritter :
>
> Hello,
>
> I’ve committed the patches. BCEL-286 [1] can not be applied to trunk because
> it updates a file that does not exist.
>
> Cheers,
> Bened
I'm not on my laptop, giving it a try later. What do Travis and Jenkis say?
Benedikt
Gary Gregory schrieb am Di. 12. Sep. 2017 um 16:47:
> Hi All:
>
> I currently get 44 unit test failures in [collections] master.
>
> Can anyone duplicate this?
>
> Thank you,
> Gary
>
> On Sep 12, 2017, at 12:38 AM, Amey Jadiye wrote:
>
> Hello Rob,
I'm going to be away from my computer until Friday. I'll give it a look then if
that's alright with you.
Cheers,
-Rob
>
> I have submitted pull req. let me know if below action plan looks good.
>
> * RandomStringGenerator i
Hi All:
I currently get 44 unit test failures in [collections] master.
Can anyone duplicate this?
Thank you,
Gary
+1
On Sat, Aug 26, 2017 at 11:19 AM, Pascal Schumacher
wrote:
> +1
>
> Am 21.08.2017 um 08:33 schrieb Benedikt Ritter:
>>
>> +1
>>
>>> Am 20.08.2017 um 12:14 schrieb Pascal Schumacher
>>> :
>>>
>>> Hi all,
>>>
>>> as discussed, I'd like to propose to move Apache Commons Discovery to
>>> dormant.
Github user coveralls commented on the issue:
https://github.com/apache/commons-collections/pull/26
[](https://coveralls.io/builds/13232186)
Coverage increased (+0.02%) to 85.138% when pulling
**c6996173991d0c
GitHub user kinow opened a pull request:
https://github.com/apache/commons-collections/pull/26
COLLECTIONS-656 Update commons-parent version, and use inherited FindBugs
plugin version
Copied settings from [text] component after Javadocs issues were fixed but
then the `mvn site` com
On Sat, Sep 2, 2017 at 12:50 AM, Gilles wrote:
> Because of "Commons" rules, it is not "equivalent": There was
> a long thread concluding that all modules must be released
> _together_, and with the same top-level package name and version
> number.
> It is very "maintainer(s)-unfriendly" because
Hello Rob,
I have submitted pull req. let me know if below action plan looks good.
* RandomStringGenerator in commons-text
* new RandomStringUtils in commons-text with different package using
RandomStringGenerator
* Mark RandomStringUtils in commons-lang as deprecated
* release commons-text 1.2
*
24 matches
Mail list logo
