[all] testing [release-plugin] with [text,1.4] disregard staging emails.

2018-05-16 Thread Rob Tompkins
Just a heads up here. I’m trying to sort out if we can retrieve the nexus staging repository url from the release build. So I’m going to stage and not release [text,1.4]. -Rob - To unsubscribe, e-mail: dev-unsubscr...@commons.ap

Re: commons-release-plugin git commit: Can't use > in Javadoc. Use a UTF-8 arrow instead.

2018-05-16 Thread Gary Gregory
It's all good :-) On Wed, May 16, 2018 at 2:30 PM, Rob Tompkins wrote: > Doh. Html…pardon. > > > On May 16, 2018, at 3:36 PM, ggreg...@apache.org wrote: > > > > Repository: commons-release-plugin > > Updated Branches: > > refs/heads/master 9283b7477 -> f4002b84e > > > > > > Can't use > in Javad

Re: [jira] [Commented] (COMMONSSITE-113) [release-plugin] Accommodate for the RC version in the dist location.

2018-05-16 Thread Rob Tompkins
If so, I may have what you’re looking for. The release-plugin skips by default, unless you set some properties in the pom.xml as to not break existing projects’ release processes. -Rob > On May 16, 2018, at 4:32 PM, Rob Tompkins wrote: > > You over on master on [collections]? > >> On May 16,

Re: [jira] [Commented] (COMMONSSITE-113) [release-plugin] Accommodate for the RC version in the dist location.

2018-05-16 Thread Rob Tompkins
You over on master on [collections]? > On May 16, 2018, at 4:24 PM, Gary Gregory (JIRA) wrote: > > >[ > https://issues.apache.org/jira/browse/COMMONSSITE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478051#comment-16478051 > ] > > Gary Gre

Re: commons-release-plugin git commit: Can't use > in Javadoc. Use a UTF-8 arrow instead.

2018-05-16 Thread Rob Tompkins
Doh. Html…pardon. > On May 16, 2018, at 3:36 PM, ggreg...@apache.org wrote: > > Repository: commons-release-plugin > Updated Branches: > refs/heads/master 9283b7477 -> f4002b84e > > > Can't use > in Javadoc. Use a UTF-8 arrow instead. > > Project: http://git-wip-us.apache.org/repos/asf/common

Re: Build and release plugin prefixes

2018-05-16 Thread Gary Gregory
On Wed, May 16, 2018 at 10:22 AM, Rob Tompkins wrote: > > > > On May 16, 2018, at 12:00 PM, Gary Gregory > wrote: > > > > Hi All: > > > > Now that we have more than one plugin in Commons, I'd like to: > > - Rename the build plugin's goal prefix from "commons" to "commons-build" > > - Release (wh

Re: Build and release plugin prefixes

2018-05-16 Thread Rob Tompkins
> On May 16, 2018, at 12:00 PM, Gary Gregory wrote: > > Hi All: > > Now that we have more than one plugin in Commons, I'd like to: > - Rename the build plugin's goal prefix from "commons" to "commons-build" > - Release (when we have added a few features soon) the release plugin with > the goal

Build and release plugin prefixes

2018-05-16 Thread Gary Gregory
Hi All: Now that we have more than one plugin in Commons, I'd like to: - Rename the build plugin's goal prefix from "commons" to "commons-build" - Release (when we have added a few features soon) the release plugin with the goal prefix "commons-release". Thoughts? Gary

Re: [io] Black Duck apparently sees vulnerability in 2.5

2018-05-16 Thread Stefan Bodewig
On 2018-05-16, Otto Fowler wrote: > I believe all security related issues and vulnerabilities need to be > handled privately by the PMC for the project. > Has this issue gone through he PMC? The "issue" is public discussion in a JIRA issue, it is public knowledge anyway. Stefan

Re: [io] Black Duck apparently sees vulnerability in 2.5

2018-05-16 Thread Otto Fowler
I believe all security related issues and vulnerabilities need to be handled privately by the PMC for the project. Has this issue gone through he PMC? On May 16, 2018 at 10:50:21, Gilles (gil...@harfang.homelinux.org) wrote: On Wed, 16 May 2018 07:33:54 -0700, Otto Fowler wrote: > Is there a PMC

Re: [io] Black Duck apparently sees vulnerability in 2.5

2018-05-16 Thread Gilles
On Wed, 16 May 2018 07:33:54 -0700, Otto Fowler wrote: Is there a PMC for IO? There is a PMC for all of "Commons". Components are unequal wrt the number of contributors (and attention they get from the PMC). Gilles On May 16, 2018 at 02:24:44, Stefan Bodewig (bode...@apache.org) wrote: Hi

Re: [io] Black Duck apparently sees vulnerability in 2.5

2018-05-16 Thread Stefan Bodewig
On 2018-05-16, Otto Fowler wrote: > Is there a PMC for IO? Sure, IO is a component overseen by the Apache Commons PMC. Maybe I should also point at http://commons.apache.org/security.html ? Stefan - To unsubscribe, e-mail: dev

Re: [io] Black Duck apparently sees vulnerability in 2.5

2018-05-16 Thread Otto Fowler
Is there a PMC for IO? On May 16, 2018 at 02:24:44, Stefan Bodewig (bode...@apache.org) wrote: Hi all https://issues.apache.org/jira/browse/IO-559 says BlackDuck would call IO 2.5 vulnerable because of this issue - so far I've not been able to verify this claim. I guess it is because of IO-556

Re: [VFS] Review for PR-30

2018-05-16 Thread Otto Fowler
https://travis-ci.org/apache/commons-vfs/jobs/342781180 On May 15, 2018 at 13:44:25, Gary Gregory (garydgreg...@gmail.com) wrote: Hopefully I can take a look this week. Do all tests pass? Like 'mvn clean test'. Gary On Mon, May 14, 2018 at 7:44 AM, Otto Fowler wrote: > https://github.com/ap