I will try to fix that. (as I remember changes plugin need to be
upgraded with new jira version)
So I can try redeploy the site with the fix.
2013/6/25 Ralph Goers :
> KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS
>
> svn tag -
> http://svn.apache.org/repos/asf/maven/plugins/ta
KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS
svn tag -
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1
+1 on the release however it is odd that the Release Notes page is empty.
Ralph
On Jun 24, 2013, at 7:15 PM, sebb wrote:
> On 25 June 2013 02:
+1
Sources at
https://repository.apache.org/content/repositories/maven-066/org/apache/maven/plugins/maven-javadoc-plugin/2.9.1/maven-javadoc-plugin-2.9.1-sources.jar,
based on r1496317
Kristian
-
To unsubscribe, e-mail: dev-uns
On 25 June 2013 02:48, Olivier Lamy wrote:
> 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
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:
https://jira.codehaus.org/secure/ReleaseNote.jsp
Great.
Quick note have a look at
http://maven.apache.org/developers/conventions/code.html
:-)
2013/6/25 :
> Author: sebb
> Date: Tue Jun 25 00:51:03 2013
> New Revision: 1496315
>
> URL: http://svn.apache.org/r1496315
> Log:
> Allow list of digests to be provided on command-line
> Allow extensio
On 25 June 2013 00:26, wrote:
> Author: olamy
> Date: Mon Jun 24 23:26:16 2013
> New Revision: 1496295
>
> URL: http://svn.apache.org/r1496295
> Log:
> fix name
>
> Modified:
> maven/plugins/trunk/maven-javadoc-plugin/pom.xml
>
> Modified: maven/plugins/trunk/maven-javadoc-plugin/pom.xml
> UR
+1 to release from somebody outside (but provided the frame injection patch)!
Just a funny detail: The maven-javadoc-plugin-2.9.1-javadoc.jar on the staging
repository of course have the frame injection bug! Somehow a chicken-egg
problem. :-)
Theoretically the pom.xml of the plugin should use i
On 24 June 2013 23:58, Olivier Lamy wrote:
> 2013/6/25 sebb :
>> On 24 June 2013 13:04, Olivier Lamy wrote:
>>> 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.
>>>
>>> We fixe
2013/6/25 sebb :
> On 24 June 2013 13:04, Olivier Lamy wrote:
>> 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.
>>
>> We fixed 6 issues:
>> https://jira.codehaus.org/secure/Releas
Voted canceled
If too many external rules depend on the signatures of the standard rules,
then I have to cancel it.
Some dirty things were done with the exposed fields and of course
checkstyle complained about it. It's a shame it has become impossible to
remove this kind of "bugs".
If these
On 24 June 2013 13:04, Olivier Lamy wrote:
> 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.
>
> We fixed 6 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&st
+1 (non binding)
Both testapidoc and apidoc contains the fixed javascript.
Regards
-Message d'origine-
De : Olivier Lamy [mailto:ol...@apache.org]
Envoyé : lundi 24 juin 2013 14:05
À : Maven Developers List
Objet : [VOTE] Apache Maven Javadoc Plugin 2.9.1
Hi,
I'd like to release Apach
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.
We fixed 6 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18843&styleName=Text&projectId=11138&Create=Create
Staging reposi
+1 on that one: going onto a major version change like 2.x could be better
here imo.
I'm totally OK with releasing things that are more correct (not working
correctly about artifact resolution here).
But since this is likely to break a lot of internal rules (for example,
it's gonna break 50% of th
+1 on going 3.1.0.
At least, alphas is surely a too "frightening" name for many people to try
it.
Maybe RC would be more seen as already usable by a larger part of the
community, but not sure it's worth the effort/debate.
Cheers
2013/6/24 Sievers, Jan
> >Almost zero people have given feedback
>Almost zero people have given feedback
tycho has recently adapted to the changes in maven 3.1.0-alpha-1 with version
0.19.0-SNAPSHOT [1]
All our ITs are passing with maven 3.1.0-alpha-1 and we didn't get tycho bugs
reported w.r.t. maven 3.1.0-alpha-1
Not sure how many people are using it thou
17 matches
Mail list logo
