[
http://jira.codehaus.org/browse/MPH-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPH-39.
------------------------------
Resolution: Won't Fix
MPH-47 is closed
> New target to display useful information from a project
> -------------------------------------------------------
>
> Key: MPH-39
> URL: http://jira.codehaus.org/browse/MPH-39
> Project: Maven 2.x Help Plugin
> Issue Type: New Feature
> Affects Versions: 2.0.1
> Reporter: Martin von Gagern
>
> When there is a bug in some library, you might wish to have a look at its
> issue tracking system, or at its source code repository to look if it has
> already been fixed. To do so, you need to know the group and artifact id of
> the library containing the bug, and then one can start looking at the pom in
> the local repository. In the case of multi-modules, this is likely to
> reference a parent, and not provide any URLs itself, so you repeat the steps
> for the parent, recursively.
> After doing so for three libraries today, I believe the help plugin should do
> this automatically. I could imagine three possibilities.
> 1. Integrate into the already lengthy help:describe output
> 2. Provide help:urls so you can do "mvn help:urls -DgroupId=some.group
> -DartifactId=buggy-library" and it would list all effective pom elements
> designed to contain URLs, probably excepting all developer and contributor
> URLs, and take care of proper inheritance.
> 3. Provide help:property so you can do "mvn help:property
> -DgroupId=some.group -DartifactId=buggy-library -Dproperty=project.scm.url"
> to get at single properties, again with inheritance handled by the mojo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
