[
https://issues.apache.org/jira/browse/ANY23-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238188#comment-13238188
]
Simone Tripodi commented on ANY23-54:
-------------------------------------
Hi Mike,
If we will adopt Aether, I think that we could hide to users they have to
download plugins, and reuse what we learnt from Maven; when invoking any23tools
with a specific plugin, any23 always check the latest version on central repo,
update it, and execute.
Take in consideration how you would manage the maven site plugin:
{code}
mvn site:site site:deploy
{code}
Here you don't explicitly define the "download plugin" action, it is performed
under the hood.
Maven gives us also a list of suggestions:
* users could define a list of repositories for looking for plugins;
* users specify plugins updates have to be forced;
* users specify plugins should not updated;
...
But I would postpone that big improvement for a next release, I'd suggest to
let release 0.7.0 working in the way Any23 users are already used to.
WDYT?
> any23tools CLI runner doesn't detect plugin CLI classes
> -------------------------------------------------------
>
> Key: ANY23-54
> URL: https://issues.apache.org/jira/browse/ANY23-54
> Project: Apache Any23
> Issue Type: Bug
> Reporter: Michele Mostarda
> Assignee: Michele Mostarda
> Priority: Critical
> Attachments: ANY23-mvn-clean-install.txt,
> org.apache.any23.plugin.PluginIT.txt
>
>
> The core/bin/any23tools should auto detect the CLI Tool class implementations
> declared in plugins/ and allow to run them.
> The auto discovery has broken with #ANY23-50 refactoring and should be
> addressed before release 0.7.0 .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
