We decided to try this again.
On Mon, Sep 22, 2014 at 5:27 PM, Benson Margulies wrote:
> Hi,
>
> Here is release 15 of the POM we maintain for the entire ASF. The
> changes since release 14 can be seen here:
>
> http://svn.apache.org/viewvc/maven/pom/tags/apache-15/pom.xml?r1=HEAD&r2=1575044&diff
I will cancel and respin at some point today.
On Wed, Sep 24, 2014 at 2:02 AM, Dennis Lundberg
wrote:
> I agree with Hervé and others that javadoc-plugin 2.10 is too untested to
> be put into the ASF pom yet.
>
> So we to respin the release, because the tag has 2.10 in it.
> Den 24 sep 2014 05:56
I agree with Hervé and others that javadoc-plugin 2.10 is too untested to
be put into the ASF pom yet.
So we to respin the release, because the tag has 2.10 in it.
Den 24 sep 2014 05:56 skrev "Hervé BOUTEMY" :
> -1 to upgrading m-javadoc-p to 2.10: seems someone really needs to work on
> 2.10.1 b
-1 to upgrading m-javadoc-p to 2.10: seems someone really needs to work on
2.10.1 because 2.10 is causing real problems for a lot of people
therefore the actual choice to stay with 2.9.1 in ASF-15 is a great choice :)
Regards,
Hervé
Le mardi 23 septembre 2014 13:13:48 Anders Hammar a écrit :
>
Oh, I got it _backwards_. Let's see what other people think.
On Tue, Sep 23, 2014 at 7:13 AM, Anders Hammar wrote:
>>
>> My view is that we should soak plugin updates in the Maven project pom for
>> at least 5 releases or 1 month (whichever is sooner) before "promoting" up
>> to the ASF parent.
>
>
> My view is that we should soak plugin updates in the Maven project pom for
> at least 5 releases or 1 month (whichever is sooner) before "promoting" up
> to the ASF parent.
I agree and that's why I asked about m-javadoc-p v2.10 which was just
recently released and it seems as it has cause som
I agree with conservative in this pom.
My view is that we should soak plugin updates in the Maven project pom for
at least 5 releases or 1 month (whichever is sooner) before "promoting" up
to the ASF parent.
In the case of GIT I am happy to make an exception as it can block others
from releasing.
I guess I am conservative about this pom; it's not very hard for
anyone who wants a newer version of something to configure it, and if
I start respinning some other plugin will go release itself in the
middle. If folks really want things in here, perhaps the plugin
release procedure should include
+1 on these changes... you could go further... but if you are only prepared
to bite off that much right now it is better than nothing!
On 22 September 2014 22:27, Benson Margulies wrote:
> Hi,
>
> Here is release 15 of the POM we maintain for the entire ASF. The
> changes since release 14 can be
Is it safe/good to upgrade to m-javadoc-p v2.10, as there has been several
reported issues [1] [2] [3]? We don't want to cause a lot of issues for
apache projects.
[1] http://jira.codehaus.org/i#browse/MJAVADOC-407
[2] http://jira.codehaus.org/i#browse/MJAVADOC-408
[3]
http://stackoverflow.com/que
I am just trying to help some git sufferers.
On Sep 22, 2014 6:55 PM, "Gary Gregory" wrote:
> The Javadoc plugin is at 2.10, is it not used because it is not considered
> stable?
>
> Gary
>
> On Mon, Sep 22, 2014 at 5:27 PM, Benson Margulies
> wrote:
>
> > Hi,
> >
> > Here is release 15 of the P
The Javadoc plugin is at 2.10, is it not used because it is not considered
stable?
Gary
On Mon, Sep 22, 2014 at 5:27 PM, Benson Margulies
wrote:
> Hi,
>
> Here is release 15 of the POM we maintain for the entire ASF. The
> changes since release 14 can be seen here:
>
>
> http://svn.apache.org/v
Hi,
Here is release 15 of the POM we maintain for the entire ASF. The
changes since release 14 can be seen here:
http://svn.apache.org/viewvc/maven/pom/tags/apache-15/pom.xml?r1=HEAD&r2=1575044&diff_format=h
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1001
S
13 matches
Mail list logo
