Hi,
The vote has passed with the following result:
+1 (binding): Kristian, Ralph, Robert, Hervé, Olivier
+1 (non binding): Tony
-1 (non binding): Fred Cooke
Will finish release complete.
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
--
+1
2013/6/25 Olivier Lamy :
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>
> This version contains the code to fix the javadoc security issue after
> the javadoc generation.
>
> Since previous try I fix the @since for applying the javadoc security fix.
>
> We fixed 6 issues:
> ht
+1
Regards,
Hervé
Le mardi 25 juin 2013 22:23:13 Robert Scholte a écrit :
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=190
> 11
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jsp
+1
Regards,
Hervé
Le mardi 25 juin 2013 11:48:55 Olivier Lamy a écrit :
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>
> This version contains the code to fix the javadoc security issue after
> the javadoc generation.
>
> Since previous try I fix the @since for applying the j
This suggestion is much like what we came up with the last time
we discussed this - about 3 weeks ago.
This behaviour is simple to achieve without a single line
of change; the release plugin already asks for a SCM tag name
distinct from the version number. (we *could* add some kind
of support for
Can you provide the steps required to get the release plugin to work this way?
Ralph
On Jun 27, 2013, at 2:24 PM, Mirko Friedenhagen wrote:
> Hello,
>
> this seems to be the most popular discussion, so another 2 cents:
> - Today I read the man page of git-tag again.
> - It states very clearly y
Hello,
this seems to be the most popular discussion, so another 2 cents:
- Today I read the man page of git-tag again.
- It states very clearly you should never reuse tags, because unlike is the
case with subversion, once a git tag is out in the wild (and pushing to
git-wip is the jungle here), ev
The file
http://www.apache.org/dist/maven/KEYS
has two entries for F0E309FF - Vincent Massol
One of them should be deleted.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@ma
On 25 June 2013 12:20, Fred Cooke wrote:
> Absolutely, sebb! This is what I've been saying all along. If I had more
> time I'd vote -1 to every attempted release that used or intended to use
> respun tags/artifacts without revisions and checksums. So here's one for
> this one until rectified prope
On 27 June 2013 15:05, Ralph Goers wrote:
> I do not believe that can be done with the release plugins as the pom has to
> specify the same version as the tag. If you then rename the tag you would
> have to modify the poms in the tag, which makes the release invalid.
>
> Have you ever used the
Agreed.
Our tooling and policy is embodied in the release plugin. I am personally fine
with any policy changes that are required, but would argue anything we have is
grandfathered in because we've been doing it so long. If changes are required,
my requirement is that I do nothing more than I cu
I do not believe that can be done with the release plugins as the pom has to
specify the same version as the tag. If you then rename the tag you would have
to modify the poms in the tag, which makes the release invalid.
Have you ever used the release plugin? If not, I would suggest you try it
On 25 June 2013 21:23, Robert Scholte wrote:
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19011
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530&status=1
>
>
GitHub user nill14 opened a pull request:
https://github.com/apache/maven-wagon/pull/2
Fix for SFTP on windows machine
I encountered a problem with SFTP on windows (using bitvise ssh server).
The following change has resolved the problem for me.
You can merge this pull request i
+1
2013/6/26 Robert Scholte :
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19011
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11530&status=1
>
> Staging repo:
>
15 matches
Mail list logo