Maven 1

Download problem from internal repository

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows 2000 JDK 1.4.2
  • Number of attachments :
    1

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Lukas Theussl added a comment -

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

Show
Lukas Theussl added a comment - Must be an issue with HttpUtils.java, maybe wagon?
Hide
Permalink
Benjamin Dang added a comment -

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.

Show
Benjamin Dang added a comment - 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.
Hide
Permalink
Benjamin Dang added a comment -

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.

Show
Benjamin Dang added a comment - 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.
Hide
Permalink
Melloware added a comment -

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.

Show
Melloware added a comment - 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.
Hide
Permalink
Abel Muiņo added a comment -

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.

Show
Abel Muiņo added a comment - 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.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.