[jira] (MPLUGIN-208) HelpMojo class generated by helpmojo goal uses deprecated annotations
[
https://jira.codehaus.org/browse/MPLUGIN-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MPLUGIN-208:
-
Fix Version/s: 3.1
Assignee: Olivier Lamy
> HelpMojo class generated by helpmojo goal uses deprecated annotations
> -
>
> Key: MPLUGIN-208
> URL: https://jira.codehaus.org/browse/MPLUGIN-208
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.0
>Reporter: Martin Ellis
>Assignee: Olivier Lamy
> Fix For: 3.1
>
> Attachments: annots-test.tar.gz
>
>
> The helpmojo goal generates a HelpMojo class that uses 'expression'
> annotations on parameter fields rather than 'property' annotations. This
> results in a lots of output at warning level when building a plugin that uses
> the helpmojo goal for documentation.
> This issue refers to javadoc/qdox style annotations generated by the
> maven-plugin-plugin 3.0 helpmojo. This version of the 'plugin' plugin does
> output Java 5 style annotations too but they are commented out.
> Sample project attached. Running {{mvn package}} on the project will show the
> warnings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-37) Add (name and) version of used skin as comment in the page-header
[ https://jira.codehaus.org/browse/MSKINS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSKINS-37: Summary: Add (name and) version of used skin as comment in the page-header (was: Add(name and) version of used skin as comment in the page-header) > Add (name and) version of used skin as comment in the page-header > - > > Key: MSKINS-37 > URL: https://jira.codehaus.org/browse/MSKINS-37 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin, Stylus Skin >Affects Versions: stylus-1.4, fluido-1.2 >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Minor > Fix For: stylus-1.5, fluido-1.2.1 > > > The fluido-skin already adds line with the skin name, but without the version. > The stylus-skin adds nothing yet. > The other skins use the default skin-template as provided by Doxia, so it > can't be fixed on skin-level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-52) Stylus skins swallows unknown tags in header, for example
Herve Boutemy created MSKINS-52: --- Summary: Stylus skins swallows unknown tags in header, for example Key: MSKINS-52 URL: https://jira.codehaus.org/browse/MSKINS-52 Project: Maven Skins Issue Type: Bug Components: Stylus Skin Affects Versions: stylus-1.4 Reporter: Herve Boutemy this causes problem with 404 error page of maven site: for example http://maven.apache.org/an/unknown/page/test the source xdoc/errors/404.xml provides http://maven.apache.org/errors"; /> but it is not rendered, then images and css are broken -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-52) Stylus skins swallows unknown tags in header, for example
[ https://jira.codehaus.org/browse/MSKINS-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSKINS-52. --- Resolution: Fixed Fix Version/s: stylus-1.5 Assignee: Herve Boutemy done in [r1345663|http://svn.apache.org/viewvc?rev=1345663&view=rev] > Stylus skins swallows unknown tags in header, for example > > > Key: MSKINS-52 > URL: https://jira.codehaus.org/browse/MSKINS-52 > Project: Maven Skins > Issue Type: Bug > Components: Stylus Skin >Affects Versions: stylus-1.4 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: stylus-1.5 > > > this causes problem with 404 error page of maven site: for example > http://maven.apache.org/an/unknown/page/test > the source xdoc/errors/404.xml provides href="http://maven.apache.org/errors"; /> but it is not rendered, then images > and css are broken -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIATOOLS-38) use plugin java 5 annotations instead of old-style javadoc annotations
Herve Boutemy created DOXIATOOLS-38: --- Summary: use plugin java 5 annotations instead of old-style javadoc annotations Key: DOXIATOOLS-38 URL: https://jira.codehaus.org/browse/DOXIATOOLS-38 Project: Maven Doxia Tools Issue Type: Task Components: Doxia Book Maven Plugin Affects Versions: doxia-book-maven-plugin-1.2 Reporter: Herve Boutemy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIATOOLS-38) use plugin java 5 annotations instead of old-style javadoc annotations
[ https://jira.codehaus.org/browse/DOXIATOOLS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed DOXIATOOLS-38. --- Resolution: Fixed Fix Version/s: doxia-book-maven-plugin-1.3 Assignee: Herve Boutemy done in [r1345773|http://svn.apache.org/viewvc?rev=1345773&view=rev] > use plugin java 5 annotations instead of old-style javadoc annotations > -- > > Key: DOXIATOOLS-38 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-38 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Book Maven Plugin >Affects Versions: doxia-book-maven-plugin-1.2 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: doxia-book-maven-plugin-1.3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-209) use maven-plugin-tools' java 5 annotations
Herve Boutemy created MPLUGIN-209: - Summary: use maven-plugin-tools' java 5 annotations Key: MPLUGIN-209 URL: https://jira.codehaus.org/browse/MPLUGIN-209 Project: Maven 2.x Plugin Tools Issue Type: Task Components: Plugin Plugin Affects Versions: 3.0 Reporter: Herve Boutemy apply to self :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-209) use maven-plugin-tools' java 5 annotations
[ https://jira.codehaus.org/browse/MPLUGIN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-209. - Resolution: Fixed Fix Version/s: 3.1 Assignee: Herve Boutemy done in [r1345787|http://svn.apache.org/viewvc?rev=1345787&view=rev] > use maven-plugin-tools' java 5 annotations > -- > > Key: MPLUGIN-209 > URL: https://jira.codehaus.org/browse/MPLUGIN-209 > Project: Maven 2.x Plugin Tools > Issue Type: Task > Components: Plugin Plugin >Affects Versions: 3.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.1 > > > apply to self :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIATOOLS-38) use plugin java 5 annotations instead of old-style javadoc annotations
[ https://jira.codehaus.org/browse/DOXIATOOLS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300268#comment-300268 ] Herve Boutemy commented on DOXIATOOLS-38: - finished in [r1345791|http://svn.apache.org/viewvc?rev=1345791&view=rev] > use plugin java 5 annotations instead of old-style javadoc annotations > -- > > Key: DOXIATOOLS-38 > URL: https://jira.codehaus.org/browse/DOXIATOOLS-38 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Book Maven Plugin >Affects Versions: doxia-book-maven-plugin-1.2 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: doxia-book-maven-plugin-1.3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-210) NPE in generated help mojo with M2 when no goal has description
Herve Boutemy created MPLUGIN-210: - Summary: NPE in generated help mojo with M2 when no goal has description Key: MPLUGIN-210 URL: https://jira.codehaus.org/browse/MPLUGIN-210 Project: Maven 2.x Plugin Tools Issue Type: Bug Affects Versions: 3.0 Reporter: Herve Boutemy java-basic-annotations IT fails under M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-211) @Mojo annotations aren't inherited
Joseph Walton created MPLUGIN-211: - Summary: @Mojo annotations aren't inherited Key: MPLUGIN-211 URL: https://jira.codehaus.org/browse/MPLUGIN-211 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: maven-plugin-tools-annotations Affects Versions: 3.0 Reporter: Joseph Walton Priority: Trivial We have a project where a mojo defined in one plugin module is inherited from in another. With Javadoc-style markup, the child class is also declared as an mojo. With @Mojo, the child class needs to re-declare @Mojo in order to be included in the plugin definition. I'm reporting this as 'trivial' priority. I've fixed it by copying those @Mojo annotations across. I wouldn't have a problem with WONTFIXing this. I think the new behaviour is clearer, and I'm not convinced that the previous behaviour was intentional or desirable. However, it is still a change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
