Re: [jira] [Deleted] (COMMONSSITE-126) Menghapus klien bugs

[Mark Thomas]

On 25/09/2018 15:23, Oliver Heger wrote:

Any chance this guy can be blocked? There has been similar spam like
this for other projects.


User has been disabled.

Mark



Oliver

Am 25.09.2018 um 15:35 schrieb Benedikt Ritter (JIRA):


  [ 
https://issues.apache.org/jira/browse/COMMONSSITE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benedikt Ritter deleted COMMONSSITE-126:




Menghapus klien bugs


 Key: COMMONSSITE-126
 URL: https://issues.apache.org/jira/browse/COMMONSSITE-126
 Project: Commons All
  Issue Type: Bug
 Environment: Menghapus perangkat lunak
Reporter: Moh.riza
Priority: Major

Menghapus spam issue klien




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [jira] [Deleted] (COMMONSSITE-126) Menghapus klien bugs

[Oliver Heger]

Any chance this guy can be blocked? There has been similar spam like
this for other projects.

Oliver

Am 25.09.2018 um 15:35 schrieb Benedikt Ritter (JIRA):
> 
>  [ 
> https://issues.apache.org/jira/browse/COMMONSSITE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Benedikt Ritter deleted COMMONSSITE-126:
> 
> 
> 
>> Menghapus klien bugs
>> 
>>
>> Key: COMMONSSITE-126
>> URL: https://issues.apache.org/jira/browse/COMMONSSITE-126
>> Project: Commons All
>>  Issue Type: Bug
>> Environment: Menghapus perangkat lunak
>>Reporter: Moh.riza
>>Priority: Major
>>
>> Menghapus spam issue klien
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [ALL] Multiple things broken in commons build infrastructure

[Gilles]

On Tue, 25 Sep 2018 14:52:03 +0200, Benedikt Ritter wrote:

Am Do., 20. Sep. 2018 um 11:57 Uhr schrieb Gilles <
gil...@harfang.homelinux.org>:


Hi.

On Thu, 20 Sep 2018 09:01:34 +0200, Benedikt Ritter wrote:
> Am Mi., 19. Sep. 2018 um 12:23 Uhr schrieb Gilles <
> gil...@harfang.homelinux.org>:
>
>> Hi.
>>
>> On Wed, 19 Sep 2018 11:41:53 +0200, Benedikt Ritter wrote:
>> > Hello,
>> >
>> > I'm trying to release commons-csv and there are multiple things
>> > broken at
>> > the moment:
>> >
>> > - the site build does not work because of COMMONSSITE-124
>> > - the OSGi bundle symbolic name is generated incorrectly 
because

>> fo
>> > COMMONSSITE-125
>> > - the commons-build-plugin goal prefix has been changed to from
>> > commons to
>> > commons-build, but no documentation has been updated. Neither 
our

>> > release
>> > documentation nor the plugin documentation. I had to dig into 
the

>> git
>> > history to find the commit that introduced the change. But 
there

>> is
>> > no
>> > explanation why we need this change. I'm currently updating our
>> > documentation to reflect the new plugin goal prefix.
>> >
>> > I'm asking everybody who works on commons-parent or the
>> > commons-build-plugin to take special care because our release
>> process
>> > is
>> > painful enough even without this detective work...
>>
>> +1
>> But it is clearly not enough: things that used to work should not
>> unexpectedly break, or if it does for a good reason, components
>> should be updated in a timely manner, i.e. when the change 
occurred,

>> not weeks, months or years later when nobody has a clue about the
>> problem.
>>
>
> Maybe we need to do more rigorous code reviews when these 
components

> are
> changed...

Sure, but we can observe that code reviews are not a high
priority in "Commons".
For good or bad, checks rely almost solely on the output of
automated tools.[1]



I don't see how automated build process help here. The build for
commons-collections has been broken for months... :-)


Sure, but I think that most jobs have the automatic email
notification disabled (to spare us yet another layer of
simili-spam), but we could imagine that "critical changes"
should be attended to immediately if their associated jobs
start to fail. [At least that's what I understood from your
message about "rigorous code reviews".]

Gilles



Benedikt




>>
>> Is it possible to set up Jenkins jobs (for all components) that
>> would automatically pick up the current CP snapshot to detect 
most

>> of the undesired changes?
>>
>
> I think that would be possible but it would be a lot of work.

Actually I'm asking whether it's possible to automate the creation
of these jobs (i.e. "bulk" creation from a list of existing jobs,
bypassing the Jenkins GUI, and doing the necessary changes on the
fly).

Gilles

[1] Cf. the preeminence of a Clirr report over the analysis of
 code functionality in real use-cases pre-release of RNG v1.1.



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [COLLECTIONS] japicmp:cmp is always skipped

[Benedikt Ritter]

Am Do., 20. Sep. 2018 um 12:13 Uhr schrieb Gilles <
gil...@harfang.homelinux.org>:

> On Thu, 20 Sep 2018 09:34:34 +0200, Benedikt Ritter wrote:
> > Hi,
> >
> > I'm currently working on getting the collections build to pass again.
> > We
> > can't use clirr anymore because it can't handle Java 8 default
> > methods.
> > I've replaced clirr with japicmp [1]. Problem is, that the
> > japicmp:cmp goal
> > is always skipped although I've added the profile.japicmp file to the
> > repository. Any idea?
>
> "japicmp" has been broken for months. [Rob may have more
> up-to-date information.]
> Problem (for [RNG]) was the opposite: It would run even when
>profile.japicmp
> was not present and would simply fail the build when there
> was not "older" version to compare against. :-/
>

I still haven't found a way to activate japicmp :-( Maybe I just have to
wait for the next release?

Benedikt


>
> Gilles
>
> > Regards,
> > Benedikt
> >
> > [1] https://github.com/apache/commons-collections/pull/54
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [ALL] Multiple things broken in commons build infrastructure

[Benedikt Ritter]

Am Do., 20. Sep. 2018 um 11:57 Uhr schrieb Gilles <
gil...@harfang.homelinux.org>:

> Hi.
>
> On Thu, 20 Sep 2018 09:01:34 +0200, Benedikt Ritter wrote:
> > Am Mi., 19. Sep. 2018 um 12:23 Uhr schrieb Gilles <
> > gil...@harfang.homelinux.org>:
> >
> >> Hi.
> >>
> >> On Wed, 19 Sep 2018 11:41:53 +0200, Benedikt Ritter wrote:
> >> > Hello,
> >> >
> >> > I'm trying to release commons-csv and there are multiple things
> >> > broken at
> >> > the moment:
> >> >
> >> > - the site build does not work because of COMMONSSITE-124
> >> > - the OSGi bundle symbolic name is generated incorrectly because
> >> fo
> >> > COMMONSSITE-125
> >> > - the commons-build-plugin goal prefix has been changed to from
> >> > commons to
> >> > commons-build, but no documentation has been updated. Neither our
> >> > release
> >> > documentation nor the plugin documentation. I had to dig into the
> >> git
> >> > history to find the commit that introduced the change. But there
> >> is
> >> > no
> >> > explanation why we need this change. I'm currently updating our
> >> > documentation to reflect the new plugin goal prefix.
> >> >
> >> > I'm asking everybody who works on commons-parent or the
> >> > commons-build-plugin to take special care because our release
> >> process
> >> > is
> >> > painful enough even without this detective work...
> >>
> >> +1
> >> But it is clearly not enough: things that used to work should not
> >> unexpectedly break, or if it does for a good reason, components
> >> should be updated in a timely manner, i.e. when the change occurred,
> >> not weeks, months or years later when nobody has a clue about the
> >> problem.
> >>
> >
> > Maybe we need to do more rigorous code reviews when these components
> > are
> > changed...
>
> Sure, but we can observe that code reviews are not a high
> priority in "Commons".
> For good or bad, checks rely almost solely on the output of
> automated tools.[1]
>

I don't see how automated build process help here. The build for
commons-collections has been broken for months... :-)

Benedikt


>
> >>
> >> Is it possible to set up Jenkins jobs (for all components) that
> >> would automatically pick up the current CP snapshot to detect most
> >> of the undesired changes?
> >>
> >
> > I think that would be possible but it would be a lot of work.
>
> Actually I'm asking whether it's possible to automate the creation
> of these jobs (i.e. "bulk" creation from a list of existing jobs,
> bypassing the Jenkins GUI, and doing the necessary changes on the
> fly).
>
> Gilles
>
> [1] Cf. the preeminence of a Clirr report over the analysis of
>  code functionality in real use-cases pre-release of RNG v1.1.
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[RESULT][VOTE] Release Apache Commons CSV 1.6 based on RC1

[Benedikt Ritter]

Hi,

this vote passes with the following result:

Gary Gregory: +1
Bruno P. Kinoshita: +1
Sergio Fernández: +1 (non-binding)
Benedikt Ritter: +1

I'll continue with the release procedure.

Thank you
Benedikt

Am Mi., 19. Sep. 2018 um 14:31 Uhr schrieb Benedikt Ritter <
brit...@apache.org>:

> Hi,
>
> we have fixed some bugs and added some features since Commons CSV 1.5 has
> been released, so I would like to release Commons CSV 1.6 based on RC1
>
> Commons CSV 1.6 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/csv/1.6-RC1/ (r29508)
>
> The tag is here:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-csv.git;a=tag;h=3c2d7919f325d1f046dff55e139455693cc68005
>
> The Maven Artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/
>
> These are the Maven Artifacts and their hashes:
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar.asc
> 
> (SHA1: 5ca098877478f554085dace80ef4bf484ec422c0)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar.asc
> 
> (SHA1: 2c637fa312b01e091b6bf5388bca4c40890b6f8a)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar.asc
> 
> (SHA1: 3ac363851526e57f0b833faf9ae58d93769df377)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar
> 
> (SHA1: 22b3c2f901af973a8ec4f24e80c8c0c77a600b79)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom
> 
> (SHA1: 7d6919d5b7f35a736631b37cf07c6e146e02e2d6)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar
> 
> (SHA1: 1a912bc6e79af7903600cbc9ee7c365ee356c9af)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom.asc
> 
> (SHA1: 122fd1dd76797a3df6e21de7269f65843ade912c)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar
> 
> (SHA1: 25316661324eacc7f8f61a9f389cb9efe034e43f)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar
> 
> (SHA1: 7163d5c8c70c71d32507583a3f6297302b32fa71)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar.asc
> 
> (SHA1: 0f148adef1676bb532170a6e4fffbbcf98f69dd5)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar
> 
> (SHA1: 5c5d54b48c86d4972a9894dbf35edcdc5656930f)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar.asc
> 
> (SHA1: 2f03131beeab5cf5c38e0b19e85bd0d8dfe14fd2)
>
> I have tested this with Java 8 using Maven 3.5.4.
>
> Details of changes since 1.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.6-RC1/RELEASE-NOTES.txt
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/changes-report.html
>
> Site:
>   http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/
> (note some *relative* links are broken and the 1.6 directories are not yet
> created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 1.5):
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/clirr-report.html
>
> RAT Report:
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review this release candidate and vote. This vote will close no
> sooner than 72 hours from now, i.e. sometime after 14:30 CEST 22-September
> 2018
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>  

Re: [VOTE] Release Apache Commons CSV 1.6 based on RC1

[Benedikt Ritter]

+1

Am Mi., 19. Sep. 2018 um 14:31 Uhr schrieb Benedikt Ritter <
brit...@apache.org>:

> Hi,
>
> we have fixed some bugs and added some features since Commons CSV 1.5 has
> been released, so I would like to release Commons CSV 1.6 based on RC1
>
> Commons CSV 1.6 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/csv/1.6-RC1/ (r29508)
>
> The tag is here:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-csv.git;a=tag;h=3c2d7919f325d1f046dff55e139455693cc68005
>
> The Maven Artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1380/org/apache/commons/commons-csv/1.6/
>
> These are the Maven Artifacts and their hashes:
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar.asc
> 
> (SHA1: 5ca098877478f554085dace80ef4bf484ec422c0)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar.asc
> 
> (SHA1: 2c637fa312b01e091b6bf5388bca4c40890b6f8a)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar.asc
> 
> (SHA1: 3ac363851526e57f0b833faf9ae58d93769df377)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.jar
> 
> (SHA1: 22b3c2f901af973a8ec4f24e80c8c0c77a600b79)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom
> 
> (SHA1: 7d6919d5b7f35a736631b37cf07c6e146e02e2d6)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar
> 
> (SHA1: 1a912bc6e79af7903600cbc9ee7c365ee356c9af)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6.pom.asc
> 
> (SHA1: 122fd1dd76797a3df6e21de7269f65843ade912c)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar
> 
> (SHA1: 25316661324eacc7f8f61a9f389cb9efe034e43f)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-sources.jar
> 
> (SHA1: 7163d5c8c70c71d32507583a3f6297302b32fa71)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-tests.jar.asc
> 
> (SHA1: 0f148adef1676bb532170a6e4fffbbcf98f69dd5)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-test-sources.jar
> 
> (SHA1: 5c5d54b48c86d4972a9894dbf35edcdc5656930f)
> /org/apache/commons/commons-csv/1.6/commons-csv-1.6-javadoc.jar.asc
> 
> (SHA1: 2f03131beeab5cf5c38e0b19e85bd0d8dfe14fd2)
>
> I have tested this with Java 8 using Maven 3.5.4.
>
> Details of changes since 1.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.6-RC1/RELEASE-NOTES.txt
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/changes-report.html
>
> Site:
>   http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/
> (note some *relative* links are broken and the 1.6 directories are not yet
> created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 1.5):
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/clirr-report.html
>
> RAT Report:
>
> http://home.apache.org/~britter/commons/commons-csv-1.6-RC1/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review this release candidate and vote. This vote will close no
> sooner than 72 hours from now, i.e. sometime after 14:30 CEST 22-September
> 2018
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
> Benedikt
>