if plugin has dependencies, the plugin props should be consulted for remote
repositories to check.
--------------------------------------------------------------------------------------------------
Key: MAVEN-1578
URL: http://jira.codehaus.org/browse/MAVEN-1578
Project: maven
Type: Bug
Components: plugin manager
Versions: 1.0.2
Environment: maven 1.0.2, mandrake linux 10.1
Reporter: Milos Kleint
I have a plugin for creating Netbeans module artifacts
(http://mevenide.codehaus.org/maven-nbm-plugin), the plugin is uploaded to
ibiblio.
However, internally it uses Netbeans.org custom ant tasks to create the
artifacts. I don't want to upload that to the central repository (it's not my
jar, I just use it - in the case they come after me or release it on their own
to ibiblio, it's easy to get rid of)
So I've put the artifact in my custom remote repository
http://mevenide.codehaus.org/repository
The idea was that when specifying the maven.repo.remote in the plugin's project
properties, it would download it from the correct place. However that's not
happening, and one has to define that custom remote repository in every project
that wants to use the plugin. That's unfortunate.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
