You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/09/27 02:53:50 UTC
[jira] Commented: (GERONIMO-3487) Local repository location for
plugins
[ https://issues.apache.org/jira/browse/GERONIMO-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530611 ]
David Jencks commented on GERONIMO-3487:
----------------------------------------
um, ok, but including it in the first place is kind of a hack and a released plugin shouldn't have it but rather the actual expected location. On the other hand developing a plugin is incredibly painful without this.
Maybe if you are building normally it should put in the local repo location but if you are using a release profile it should put in a configured remote repo?
> Local repository location for plugins
> -------------------------------------
>
> Key: GERONIMO-3487
> URL: https://issues.apache.org/jira/browse/GERONIMO-3487
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Plugins
> Reporter: Jarek Gawor
>
> The generated geronimo-plugin.xml contains the local repository as: <source-repository>~/.m2/repository/</source-repository>. That assumes that the local repository lives in the user's home directory (the PluginRepositoryDownloader.java replaces ~ with user.home system property). However, this might not be always be true as Maven can be configured to use a different directory.
> It might be nicer to generate the geronimo-plugin.xml with <source-repository>${local.repo}</source-repository> or similar and then the PluginRepositoryDownloader.java would replace it with an appropriate value. For example. by default it would assume ~/.m2/repository but the user could specify a different directory by setting a system property or changing the configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.