Issue Details (XML | Word | Printable)

Key: MAVEN-1716
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Melloware
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven 1

Download problem from internal repository

Created: 13/May/05 08:04 AM   Updated: 14/Sep/06 12:26 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. screenshot-1.jpg
(49 kB)
Environment: Windows 2000 JDK 1.4.2


 Description  « Hide

I want to have all my custom plugins in the internal company repository. However the plugin:download goal has a bug where it is not finding the plugins correctly. Here is what I have discovered.

maven.repo.remote=file:///development/dev-share/maven -this fails to find the plugins but works fine for finding library dependencies.

maven.repo.remote=file://x:/maven - 2 slashes this fails to find plugins but works find for finding libraries

maven.repo.remote=file:///x:/maven - noticed the 3 slashes, this works for finding the plugins but now all libraries fail to dowload because of invalid syntax.



Lukas Theussl added a comment - 21/Oct/05 12:43 PM

Must be an issue with HttpUtils.java, maybe wagon?


Benjamin Dang added a comment - 09/Feb/06 04:29 PM

Seems this issue is fixed. There are at least two types of repositories: a general library repository and plugin repository. In the plugin, each plugin you need must have the maven-metadata.xml file residing inside the folder.


Benjamin Dang added a comment - 09/Feb/06 04:31 PM

As said earlier, you need to make sure each plugin you want has maven-metadata.xml. I'm unsure of Maven's intent for this, but it seems this metadata file will apply to all artifacts. I can see these files spread out within my packaged/installed artifacts.


Melloware added a comment - 14/Apr/06 09:04 AM

Benjamin, what you have said is true of Maven2 but not of Maven1. This bug was reported for Maven1. The repo format of Maven1 repository is just

log4j/jars/log4j-1.2.8.jar
log4j/jars/log4j-1.2.9.jar
log4j/jars/log4j-1.2.13.jar

My original bug was as of last May using Maven1.


Abel Muiño added a comment - 14/Sep/06 12:26 PM

I'm not sure about plug-ins, but it is working for me (with maven 1.0.2) by removing the slashes and changing ":" by "|".

For example: maven.repo.remote=file:X|path_to/repository

Hope it helps.