You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/21 10:06:19 UTC
[jira] Created: (MAVEN-1329) Provide informative plugins
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1329
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1329
Summary: Provide informative plugins
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin manager
Assignee:
Reporter: Peter Nabbefeld
Created: Mon, 21 Jun 2004 4:05 AM
Updated: Mon, 21 Jun 2004 4:05 AM
Description:
please provide some mechanism to ask a plugin for the parameters it uses, either from the commandline or from an application. This should not only result in a list of parameters, but also in a description of the parameter (and the plugin).
On the commandline this could look like this:
1. Describe plugin
maven describe plugin
result:
This plugin downloads and installs artifacts. Its goals are
download
...
2. Describe goal
maven describe plugin:download
result:
This goal downloads an artifact. It uses the following parameters:
artifactId
...
3. Describe parameter
maven describe plugin:download -DparamId=artifactId
This parameter ...
But of course, this is only a proposal how it could look like. On the other hand, to be able to do this programmatically, would it make easier to integrate maven with tools like IDEs. That's why I think, this is a bug: Maven is not easy to use, so tool integration will be an important matter for use of maven.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1329) Provide informative plugins
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Peter Nabbefeld
Created: Tue, 22 Jun 2004 3:42 AM
Body:
4. Show some examples:
maven describe plugin:download examples
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1329?page=comments#action_20894
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1329
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1329
Summary: Provide informative plugins
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin manager
Assignee:
Reporter: Peter Nabbefeld
Created: Mon, 21 Jun 2004 4:05 AM
Updated: Tue, 22 Jun 2004 3:42 AM
Description:
please provide some mechanism to ask a plugin for the parameters it uses, either from the commandline or from an application. This should not only result in a list of parameters, but also in a description of the parameter (and the plugin).
On the commandline this could look like this:
1. Describe plugin
maven describe plugin
result:
This plugin downloads and installs artifacts. Its goals are
download
...
2. Describe goal
maven describe plugin:download
result:
This goal downloads an artifact. It uses the following parameters:
artifactId
...
3. Describe parameter
maven describe plugin:download -DparamId=artifactId
This parameter ...
But of course, this is only a proposal how it could look like. On the other hand, to be able to do this programmatically, would it make easier to integrate maven with tools like IDEs. That's why I think, this is a bug: Maven is not easy to use, so tool integration will be an important matter for use of maven.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MAVEN-1329) Provide informative plugins
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1329?page=all ]
Brett Porter closed MAVEN-1329:
-------------------------------
Resolution: Won't Fix
not in the 1.x series.
> Provide informative plugins
> ---------------------------
>
> Key: MAVEN-1329
> URL: http://jira.codehaus.org/browse/MAVEN-1329
> Project: maven
> Type: Bug
> Components: plugin manager
> Reporter: Peter Nabbefeld
>
>
> please provide some mechanism to ask a plugin for the parameters it uses, either from the commandline or from an application. This should not only result in a list of parameters, but also in a description of the parameter (and the plugin).
> On the commandline this could look like this:
> 1. Describe plugin
> maven describe plugin
> result:
> This plugin downloads and installs artifacts. Its goals are
> download
> ...
> 2. Describe goal
> maven describe plugin:download
> result:
> This goal downloads an artifact. It uses the following parameters:
> artifactId
> ...
> 3. Describe parameter
> maven describe plugin:download -DparamId=artifactId
> This parameter ...
> But of course, this is only a proposal how it could look like. On the other hand, to be able to do this programmatically, would it make easier to integrate maven with tools like IDEs. That's why I think, this is a bug: Maven is not easy to use, so tool integration will be an important matter for use of maven.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org