[Updated] (MSCMPUB-46) drop custom scmpublish lifecycle with its scmpublish goal

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Updated] (MSCMPUB-46) drop custom scmpublish lifecycle with its scmpublish goal

Amelia Eiras (Jira)

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

Herve Boutemy updated MSCMPUB-46:
---------------------------------
    Description:
when preparing a new release, generating the site with Java 8, I found that the aggregate tag for the scmpublish goal contained a typo: it was written @aggregate when it should have been @aggregator (then makes Javadoc 8 fail)
this proves that this feature has never really been used, and can be dropped: this will simplify the code

(notice that in addition, it was not possible to switch from plugin-tools javadoc annotation to Java annotations, because Java annotations don't permit custom lifecycle)

  was:
when preparing a new release, generating the site with Java 8, I found that the aggregate tag for the scmpublish goal contained a typo: it was written @aggregate when it should have been @aggregator (then makes Javadoc 8 fail)
this proves that this feature has never really been used, and can be dropped: this will simplify the code


> drop custom scmpublish lifecycle with its scmpublish goal
> ---------------------------------------------------------
>
>                 Key: MSCMPUB-46
>                 URL: https://issues.apache.org/jira/browse/MSCMPUB-46
>             Project: Maven SCM Publish Plugin
>          Issue Type: Task
>    Affects Versions: 3.0.0
>            Reporter: Herve Boutemy
>            Priority: Major
>             Fix For: 3.1.0
>
>
> when preparing a new release, generating the site with Java 8, I found that the aggregate tag for the scmpublish goal contained a typo: it was written @aggregate when it should have been @aggregator (then makes Javadoc 8 fail)
> this proves that this feature has never really been used, and can be dropped: this will simplify the code
> (notice that in addition, it was not possible to switch from plugin-tools javadoc annotation to Java annotations, because Java annotations don't permit custom lifecycle)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)