[jira] (MINVOKER-158) Ability to clean up files and folders after successfull run
Robert Scholte created MINVOKER-158: --- Summary: Ability to clean up files and folders after successfull run Key: MINVOKER-158 URL: https://jira.codehaus.org/browse/MINVOKER-158 Project: Maven 2.x Invoker Plugin Issue Type: New Feature Affects Versions: 1.8 Reporter: Robert Scholte When having an aggregator to execute a lot of projects, the target-directory can increase very hard, especially the localrepo folder. To be more storage-friendly, we should introduce some strategies to clean up stuff afterwards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-95) Enhance documentation of install-file
[ https://jira.codehaus.org/browse/MINSTALL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MINSTALL-95. -- Resolution: Fixed Fix Version/s: 2.5 Assignee: Robert Scholte Fixed in [r1505143|http://svn.apache.org/r1505143] > Enhance documentation of install-file > - > > Key: MINSTALL-95 > URL: https://jira.codehaus.org/browse/MINSTALL-95 > Project: Maven 2.x Install Plugin > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Stephen Colebourne >Assignee: Robert Scholte >Priority: Minor > Fix For: 2.5 > > > When you want to install a pre-built third party jar file into a local repo > google will [point > you|https://www.google.co.uk/search?q=maven+install+artifact&ie=utf-8] at > these pages: > * http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html > * > http://maven.apache.org/plugins/maven-install-plugin/examples/specific-local-repo.html > Neither of these pages explains what to do if you have a pom that you want to > deploy as well as the jar file. The right answer is already documented here: > * > http://maven.apache.org/plugins/maven-install-plugin/examples/custom-pom-installation.html > Please enhance the documentation in two ways: > * enhance the > [mini-guide|http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html] > to include an example with a pom > * enhance the [plugin > guides|http://maven.apache.org/plugins/maven-install-plugin/examples/specific-local-repo.html] > to provide cross-links between the individual pages. ie, after the example > at links along the lines of "if you want to install a pom as well click here" > etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-372) Index page should refer to Apache Maven for at least the first mention
[ https://jira.codehaus.org/browse/MJAVADOC-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329043#comment-329043 ] SebbASF commented on MJAVADOC-372: -- Apache branding rules. See: http://www.apache.org/foundation/marks/pmcs#projectname (and the rest of the page is worth reading). > Index page should refer to Apache Maven for at least the first mention > -- > > Key: MJAVADOC-372 > URL: https://jira.codehaus.org/browse/MJAVADOC-372 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: SebbASF >Priority: Minor > > Index page should refer to Apache Maven for at least the first mention, i.e. > it should start: > Apache Maven Javadoc Plugin > The Apache Maven Javadoc Plugin uses the Javadoc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-372) Index page should refer to Apache Maven for at least the first mention
[ https://jira.codehaus.org/browse/MJAVADOC-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329044#comment-329044 ] Dennis Lundberg commented on MJAVADOC-372: -- Does that apply to subprojects such as Maven plugins as well? It's a little vague on that. Even so, it should be enough that we have "Apache Maven Javadoc Plugin" both in the breadcrumb path and in the page title. > Index page should refer to Apache Maven for at least the first mention > -- > > Key: MJAVADOC-372 > URL: https://jira.codehaus.org/browse/MJAVADOC-372 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: SebbASF >Priority: Minor > > Index page should refer to Apache Maven for at least the first mention, i.e. > it should start: > Apache Maven Javadoc Plugin > The Apache Maven Javadoc Plugin uses the Javadoc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-743) Add support for generation of attributes
[
https://jira.codehaus.org/browse/MECLIPSE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitko Kolev updated MECLIPSE-743:
-
Attachment: patch.txt
> Add support for generation of attributes
> -
>
> Key: MECLIPSE-743
> URL: https://jira.codehaus.org/browse/MECLIPSE-743
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Affects Versions: 2.9
>Reporter: Mitko Kolev
> Attachments: patch.txt
>
>
> Currently it is not possible to configure attributes for the
> {{}} element. The goal is to be able to generate
> classpath entries wth attributes:
>
>
>
>value="/WEB-INF/lib"/>
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-743) Add support for generation of attributes
[
https://jira.codehaus.org/browse/MECLIPSE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitko Kolev updated MECLIPSE-743:
-
Patch Submitted: Yes
> Add support for generation of attributes
> -
>
> Key: MECLIPSE-743
> URL: https://jira.codehaus.org/browse/MECLIPSE-743
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Affects Versions: 2.9
>Reporter: Mitko Kolev
> Attachments: patch.txt
>
>
> Currently it is not possible to configure attributes for the
> {{}} element. The goal is to be able to generate
> classpath entries wth attributes:
>
>
>
>value="/WEB-INF/lib"/>
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-743) Add support for generation of attributes
[
https://jira.codehaus.org/browse/MECLIPSE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329045#comment-329045
]
Mitko Kolev commented on MECLIPSE-743:
--
The attached patch extends the configuration with the possibility to configure
custom attributes for dependencies and classpath containers based on the
classpath entry path. Example:
{code:xml}
someStringInPath
custom
attribute
{code}
> Add support for generation of attributes
> -
>
> Key: MECLIPSE-743
> URL: https://jira.codehaus.org/browse/MECLIPSE-743
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Affects Versions: 2.9
>Reporter: Mitko Kolev
> Attachments: patch.txt
>
>
> Currently it is not possible to configure attributes for the
> {{}} element. The goal is to be able to generate
> classpath entries wth attributes:
>
>
>
>value="/WEB-INF/lib"/>
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-204) recognize classical Maven objects as components
[
https://jira.codehaus.org/browse/MPLUGIN-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-204:
--
Description:
$\{session}, $\{project}, $\{mojo}, $\{plugin}, $\{settings} expressions are
classical Maven objects injected into Mojos with readonly attribute (ie not
configurable)
As [discussed on the dev list|http://markmail.org/message/fruuocvtrhmkbo3y],
having them automatically injected with @component annotation, recognized by
their type, would simplify code
was:
${session}, ${project}, ${mojo}, ${plugin}, ${settings} expressions are
classical Maven objects injected into Mojos with readonly attribute (ie not
configurable)
As [discussed on the dev list|http://markmail.org/message/fruuocvtrhmkbo3y],
having them automatically injected with @component annotation, recognized by
their type, would simplify code
> recognize classical Maven objects as components
> ---
>
> Key: MPLUGIN-204
> URL: https://jira.codehaus.org/browse/MPLUGIN-204
> Project: Maven 2.x Plugin Tools
> Issue Type: New Feature
>Affects Versions: 2.9
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 3.0
>
>
> $\{session}, $\{project}, $\{mojo}, $\{plugin}, $\{settings} expressions are
> classical Maven objects injected into Mojos with readonly attribute (ie not
> configurable)
> As [discussed on the dev list|http://markmail.org/message/fruuocvtrhmkbo3y],
> having them automatically injected with @component annotation, recognized by
> their type, would simplify code
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-249) give snippets to show use of expressions to get Maven objects
Herve Boutemy created MPLUGIN-249: - Summary: give snippets to show use of expressions to get Maven objects Key: MPLUGIN-249 URL: https://jira.codehaus.org/browse/MPLUGIN-249 Project: Maven 2.x Plugin Tools Issue Type: Wish Components: maven-plugin-tools-annotations, maven-plugin-tools-java Reporter: Herve Boutemy pseudo-components were added in MPLUGIN-204 for some ultra-classical but there are more use case, giving snippets and pointer to http://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html is useful -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-79) pull-right class compresses listitem
[ https://jira.codehaus.org/browse/MSKINS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329046#comment-329046 ] Michael Osipov commented on MSKINS-79: -- This bugs comes from the incorrect design of the breadcrumbs bar. See [stackoverflow|http://stackoverflow.com/questions/12452134/twitter-bootstrap-navigation-bar-right-align-dropdown-menu] for a correct solution. I will create another ticket for that. > pull-right class compresses listitem > > > Key: MSKINS-79 > URL: https://jira.codehaus.org/browse/MSKINS-79 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Minor > Fix For: fluido-1.3.1 > > Attachments: mskins_pullright.PNG > > > there should be a margin between the pipe-sign and the version and > publishDate (see attachment). > It also seems that the divider class has no effect anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-249) give snippets to show use of expressions to get Maven objects
[ https://jira.codehaus.org/browse/MPLUGIN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-249. - Resolution: Fixed Fix Version/s: 3.3 Assignee: Herve Boutemy done in [r1505210|http://svn.apache.org/r1505210] > give snippets to show use of expressions to get Maven objects > - > > Key: MPLUGIN-249 > URL: https://jira.codehaus.org/browse/MPLUGIN-249 > Project: Maven 2.x Plugin Tools > Issue Type: Wish > Components: maven-plugin-tools-annotations, maven-plugin-tools-java >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.3 > > > pseudo-components were added in MPLUGIN-204 for some ultra-classical > but there are more use case, giving snippets and pointer to > http://maven.apache.org/ref/current/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html > is useful -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSKINS-80. Resolution: Fixed > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-80: - Remaining Estimate: 0 minutes Original Estimate: 0 minutes > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329048#comment-329048 ] Michael Osipov commented on MSKINS-80: -- Fixed with r1505214. > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSKINS-80: - Fix Version/s: fluido-1.3.1 > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Fix For: fluido-1.3.1 > > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
[
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPLUGIN-248.
-
Resolution: Fixed
Fix Version/s: 3.3
Assignee: Herve Boutemy
patch applied in [r1505215|http://svn.apache.org/r1505215]
thank you
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---
>
> Key: MPLUGIN-248
> URL: https://jira.codehaus.org/browse/MPLUGIN-248
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-ant
>Affects Versions: 3.2
> Environment: git-svn-id:
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
> 13f79535-47bb-0310-9956-ffa450edef68
>Reporter: Mirko Friedenhagen
>Assignee: Herve Boutemy
> Fix For: 3.3
>
> Attachments: MPLUGIN-248.patch
>
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
> element pluginMetadata: Schemas validity error : Element
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of
> this. I consider this major because the documentation
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
> just references the ITs and all the examples therefore are broken for users.
> I will submit a patch and Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-222) 'Since' information is not shown on generated site (ANT Mojos)
[ https://jira.codehaus.org/browse/MPLUGIN-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329050#comment-329050 ] Herve Boutemy commented on MPLUGIN-222: --- [r1367250|http://svn.apache.org/r1367250] > 'Since' information is not shown on generated site (ANT Mojos) > -- > > Key: MPLUGIN-222 > URL: https://jira.codehaus.org/browse/MPLUGIN-222 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: Metadata Model >Affects Versions: 2.5.1, 2.6, 2.7, 2.8, 2.9, 3.0, 3.1 > Environment: Any. >Reporter: Tinguaro Barreno >Assignee: Olivier Lamy >Priority: Minor > Fix For: 3.2 > > Attachments: fix-since-samples-v2.zip, fix-since-samples-v3.zip, > maven-plugin-tools.patch > > > Hi, > The plugin site for an ANT Mojo doesn't shows the 'since' information for > goals and parameters. > The problem seems to be in the 'PluginMetadataParser.java'; this class gets > the Mojo data object and convert it to a MojoDescriptor. Just two lines are > enough to pass the 'since' data to the descriptor (and then, include it on > the site). > I attach the patch and two tests cases for Maven 2.2.1 and Maven 3.0. I've > test the patch with maven-plugin-plugin v2.5.1, v2.9 and 3.1. > Best wishes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-250) since element is not in version 1.0.0 of plugin-metadata: should create a new version of the descriptor
Herve Boutemy created MPLUGIN-250: - Summary: since element is not in version 1.0.0 of plugin-metadata: should create a new version of the descriptor Key: MPLUGIN-250 URL: https://jira.codehaus.org/browse/MPLUGIN-250 Project: Maven 2.x Plugin Tools Issue Type: Wish Components: maven-plugin-tools-ant Affects Versions: 3.2 Reporter: Herve Boutemy this element was added for MPLUGIN-222 in [r1367250|http://svn.apache.org/r1367250] without creating a new descriptor version then the 1.0.0 xsd doesn't contain the element we should create 1.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-250) since element is not in version 1.0.0 of plugin-metadata: should create a new version of the descriptor
[ https://jira.codehaus.org/browse/MPLUGIN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-250. - Resolution: Fixed Fix Version/s: 3.3 Assignee: Herve Boutemy done in [r1505220|http://svn.apache.org/r1505220] > since element is not in version 1.0.0 of plugin-metadata: should create a new > version of the descriptor > --- > > Key: MPLUGIN-250 > URL: https://jira.codehaus.org/browse/MPLUGIN-250 > Project: Maven 2.x Plugin Tools > Issue Type: Wish > Components: maven-plugin-tools-ant >Affects Versions: 3.2 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.3 > > > this element was added for MPLUGIN-222 in > [r1367250|http://svn.apache.org/r1367250] without creating a new descriptor > version > then the 1.0.0 xsd doesn't contain the element > we should create 1.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-241) Source compatibility with Ant 1.9
Emmanuel Bourg created MANTTASKS-241:
Summary: Source compatibility with Ant 1.9
Key: MANTTASKS-241
URL: https://jira.codehaus.org/browse/MANTTASKS-241
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Affects Versions: 2.1.3
Reporter: Emmanuel Bourg
Priority: Minor
Attachments: ant-1.9-compatibility.patch
Maven Ant Tasks 2.1.3 fails to compile against Ant 1.9.x. This is a caused by
generics added to {{org.apache.tools.ant.Project}} in the new version.
Here is a patch fixing this issue while preserving the compatibility with the
previous versions of Ant.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-245) @Parameter property names are not written to the plugin-help.xml file
[ https://jira.codehaus.org/browse/MPLUGIN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329052#comment-329052 ] Herve Boutemy commented on MPLUGIN-245: --- an IT please > @Parameter property names are not written to the plugin-help.xml file > - > > Key: MPLUGIN-245 > URL: https://jira.codehaus.org/browse/MPLUGIN-245 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Reporter: SebbASF > Attachments: HelpMojo.java, HelpMojo.java > > > The generated HelpMojo fails to show user parameter names if the Mojo is > generated from Java 5 annotations. > This appears to be because the plugin-help.xml file does not include the > information. HelpMojo.java is expecting to find an "expression" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-372) Index page should refer to Apache Maven for at least the first mention
[ https://jira.codehaus.org/browse/MJAVADOC-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329053#comment-329053 ] SebbASF commented on MJAVADOC-372: -- It applies to all Apache trademarks, of which Maven is one. bq. Even so, it should be enough that we have "Apache Maven Javadoc Plugin" both in the breadcrumb path and in the page title. No, because they are not the primary mention of the brand; that is the page content. > Index page should refer to Apache Maven for at least the first mention > -- > > Key: MJAVADOC-372 > URL: https://jira.codehaus.org/browse/MJAVADOC-372 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: SebbASF >Priority: Minor > > Index page should refer to Apache Maven for at least the first mention, i.e. > it should start: > Apache Maven Javadoc Plugin > The Apache Maven Javadoc Plugin uses the Javadoc ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-246) Clarify that super class must also use annotations
[ https://jira.codehaus.org/browse/MPLUGIN-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPLUGIN-246. - Resolution: Fixed Fix Version/s: 3.3 Assignee: Herve Boutemy done in [r1505228|http://svn.apache.org/r1505228] > Clarify that super class must also use annotations > -- > > Key: MPLUGIN-246 > URL: https://jira.codehaus.org/browse/MPLUGIN-246 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Environment: > http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html >Reporter: SebbASF >Assignee: Herve Boutemy >Priority: Minor > Fix For: 3.3 > > > The page > http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html > says: > "NOTE With annotations, it's not any more mandatory to have your Mojos super > classes in the same project. Super classes can now come from reactor projects > or external dependencies." > It would help if were made explicit that this will only work if the > super-class also uses annotations. Something like: > "NOTE With annotations, your Mojo super class does not have to be in the same > project. Provided that the super class also uses annotations, it > can now come from reactor projects or external dependencies." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-244) Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
[
https://jira.codehaus.org/browse/MPLUGIN-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-244:
--
Fix Version/s: 3.3
> Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
> ---
>
> Key: MPLUGIN-244
> URL: https://jira.codehaus.org/browse/MPLUGIN-244
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.2
>Reporter: Evgeny Mandrikov
> Fix For: 3.3
>
> Attachments: reproducer.zip
>
>
> "mvn clean package" on [^reproducer.zip] leads to:
> {noformat}
> 00:51:47 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.9:jar (default) on project
> example: MavenReportException: Error while creating archive:
> 00:51:47 [ERROR] Exit code: 1 -
> /tmp/help/reproducer/target/generated-sources/plugin/example/HelpMojo.java:24:
> error: self-closing element not allowed
> 00:51:47 [ERROR] * Display help information on example.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
[
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329055#comment-329055
]
Mirko Friedenhagen commented on MPLUGIN-248:
Hervé, the Maven site still shows it wrong, so probably it has to be
regenerated?
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---
>
> Key: MPLUGIN-248
> URL: https://jira.codehaus.org/browse/MPLUGIN-248
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-ant
>Affects Versions: 3.2
> Environment: git-svn-id:
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
> 13f79535-47bb-0310-9956-ffa450edef68
>Reporter: Mirko Friedenhagen
>Assignee: Herve Boutemy
> Fix For: 3.3
>
> Attachments: MPLUGIN-248.patch
>
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
> element pluginMetadata: Schemas validity error : Element
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of
> this. I consider this major because the documentation
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
> just references the ITs and all the examples therefore are broken for users.
> I will submit a patch and Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-245) @Parameter property names are not written to the plugin-help.xml file
[ https://jira.codehaus.org/browse/MPLUGIN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329056#comment-329056 ] SebbASF commented on MPLUGIN-245: - Sorry, no idea how to create an IT. > @Parameter property names are not written to the plugin-help.xml file > - > > Key: MPLUGIN-245 > URL: https://jira.codehaus.org/browse/MPLUGIN-245 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Reporter: SebbASF > Attachments: HelpMojo.java, HelpMojo.java > > > The generated HelpMojo fails to show user parameter names if the Mojo is > generated from Java 5 annotations. > This appears to be because the plugin-help.xml file does not include the > information. HelpMojo.java is expecting to find an "expression" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-244) Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
[
https://jira.codehaus.org/browse/MPLUGIN-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329057#comment-329057
]
Herve Boutemy commented on MPLUGIN-244:
---
doclint: http://openjdk.java.net/jeps/172
> Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
> ---
>
> Key: MPLUGIN-244
> URL: https://jira.codehaus.org/browse/MPLUGIN-244
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.2
>Reporter: Evgeny Mandrikov
> Fix For: 3.3
>
> Attachments: reproducer.zip
>
>
> "mvn clean package" on [^reproducer.zip] leads to:
> {noformat}
> 00:51:47 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.9:jar (default) on project
> example: MavenReportException: Error while creating archive:
> 00:51:47 [ERROR] Exit code: 1 -
> /tmp/help/reproducer/target/generated-sources/plugin/example/HelpMojo.java:24:
> error: self-closing element not allowed
> 00:51:47 [ERROR] * Display help information on example.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-243) add an option to hide a mojo parameter from generated documentation
[ https://jira.codehaus.org/browse/MPLUGIN-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPLUGIN-243: -- Fix Version/s: 3.3 > add an option to hide a mojo parameter from generated documentation > --- > > Key: MPLUGIN-243 > URL: https://jira.codehaus.org/browse/MPLUGIN-243 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Components: maven-plugin-annotations, > maven-plugin-tools-annotations, maven-plugin-tools-java, > maven-plugin-tools-javadoc >Affects Versions: 3.2 >Reporter: Herve Boutemy >Priority: Minor > Fix For: 3.3 > > > when a parameter is defined in a parent mojo, because it needs to be shared > by some child mojos, but some other child mojos don't use the feature, > parameter documentation just adds unnecessary complexity > see MDEP-413 for such an example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-244) Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
[
https://jira.codehaus.org/browse/MPLUGIN-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329058#comment-329058
]
Herve Boutemy commented on MPLUGIN-244:
---
I don't have JDK8 installed, nor experience with this doclint: why is this self
closing element not allowed?
Is it valid if we replace with paragraphs?
> Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
> ---
>
> Key: MPLUGIN-244
> URL: https://jira.codehaus.org/browse/MPLUGIN-244
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.2
>Reporter: Evgeny Mandrikov
> Fix For: 3.3
>
> Attachments: reproducer.zip
>
>
> "mvn clean package" on [^reproducer.zip] leads to:
> {noformat}
> 00:51:47 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.9:jar (default) on project
> example: MavenReportException: Error while creating archive:
> 00:51:47 [ERROR] Exit code: 1 -
> /tmp/help/reproducer/target/generated-sources/plugin/example/HelpMojo.java:24:
> error: self-closing element not allowed
> 00:51:47 [ERROR] * Display help information on example.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-245) @Parameter property names are not written to the plugin-help.xml file
[ https://jira.codehaus.org/browse/MPLUGIN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329059#comment-329059 ] Herve Boutemy commented on MPLUGIN-245: --- so please provide a project, and explain what you expect when running xxx and what you get, in plain english > @Parameter property names are not written to the plugin-help.xml file > - > > Key: MPLUGIN-245 > URL: https://jira.codehaus.org/browse/MPLUGIN-245 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Reporter: SebbASF > Attachments: HelpMojo.java, HelpMojo.java > > > The generated HelpMojo fails to show user parameter names if the Mojo is > generated from Java 5 annotations. > This appears to be because the plugin-help.xml file does not include the > information. HelpMojo.java is expecting to find an "expression" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-248) XML-Namespace in ITs for ant-based mojos are wrong.
[
https://jira.codehaus.org/browse/MPLUGIN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329060#comment-329060
]
Herve Boutemy commented on MPLUGIN-248:
---
the site will be regenerated when we'll do the release: for the moment, you
have to build it for yourself
or I can publish it in
http://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST if you feel
it useful to have a copy just now
> XML-Namespace in ITs for ant-based mojos are wrong.
> ---
>
> Key: MPLUGIN-248
> URL: https://jira.codehaus.org/browse/MPLUGIN-248
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-ant
>Affects Versions: 3.2
> Environment: git-svn-id:
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk@1470122
> 13f79535-47bb-0310-9956-ffa450edef68
>Reporter: Mirko Friedenhagen
>Assignee: Herve Boutemy
> Fix For: 3.3
>
> Attachments: MPLUGIN-248.patch
>
>
> Example error:
> {code}
> [mifr@LMKA-2HPPHFDTY3 maven-plugin-tools]$ xmllint --schema
> http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml >
> /dev/null
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml:23:
> element pluginMetadata: Schemas validity error : Element
> '{http://maven.apache.org/POM/4.0.0}pluginMetadata': No matching global
> declaration available for the validation root.
> maven-plugin-plugin/src/it/ant-basic/src/main/scripts/touch.mojos.xml fails
> to validate
> {code}
> While Maven seems not choke on this, XML support in IDEs is broken because of
> this. I consider this major because the documentation
> (http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/ant-mojo.html)
> just references the ITs and all the examples therefore are broken for users.
> I will submit a patch and Github-Pull request for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-245) @Parameter property names are not written to the plugin-help.xml file
[ https://jira.codehaus.org/browse/MPLUGIN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329061#comment-329061 ] SebbASF commented on MPLUGIN-245: - Any plugin that uses annotations and has a generated help goal will do. For example, compare the output of (A) mvn help:describe -Dplugin=javadoc -Dgoal=help -Ddetail with the output of (B) mvn javadoc:help -Dgoal=help -Ddetail They should both show the same detailed help for javadoc:help However (B) does not show any property names. > @Parameter property names are not written to the plugin-help.xml file > - > > Key: MPLUGIN-245 > URL: https://jira.codehaus.org/browse/MPLUGIN-245 > Project: Maven 2.x Plugin Tools > Issue Type: Bug >Reporter: SebbASF > Attachments: HelpMojo.java, HelpMojo.java > > > The generated HelpMojo fails to show user parameter names if the Mojo is > generated from Java 5 annotations. > This appears to be because the plugin-help.xml file does not include the > information. HelpMojo.java is expecting to find an "expression" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRRESOURCES-69) Spurious blank lines in generated N&L files
SebbASF created MRRESOURCES-69: -- Summary: Spurious blank lines in generated N&L files Key: MRRESOURCES-69 URL: https://jira.codehaus.org/browse/MRRESOURCES-69 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Reporter: SebbASF The generated NOTICE and LICENSE files have a spurious blank line at the start. The NOTICE file has an additional two blank lines at the end. These extra blank lines are not part of the official files, and should be removed. These extra lines appear to be due to problems with the apache jar resources bundle 1.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
