Maven 1

'maven.repo.local' not honored by all

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0.2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows XP SP2; Java 1.5.0_02; Maven 1.0.2
  • Number of attachments :
    0

Description

1. In project.properties file, set maven.repo.local=C:\blah\repository
2. Delete, completely, %HOMEDRIVE%%HOMEPATH%\.maven\repository, if it already exists
3. Run maven java:compile
4. I see where it downloads my project's dependencies, and places them in the appropriate local repository location (see maven.repo.local above)
5. However, it also downloads commons-lang, antlr & commons-jelly-tags-antlr, which I'm assuming Maven is using under the covers. That wouldn't be a problem, except they are still being put in %HOMEDRIVE%%HOMEPATH%\.maven\repository. Am I missing some other property, or is this a bug?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

confirmed bug

Show
Brett Porter added a comment - confirmed bug
Hide
Permalink
Davy Toch added a comment -

I think it's best to override maven.repo.local it in $

{user.home}

/build.properties. In this case the problem you indicated doesn't appear.

On the other hand : is there a sense in overriding the default value of maven.repo.local in project.properties?

  • if you have 20 Maven projects that have to use the same local repository, then you have to verify 20 times project.properties
  • having several local Maven repositories on your machine seems pointless to me (it is only a local cache of what is available on the central repositories)
Show
Davy Toch added a comment - I think it's best to override maven.repo.local it in $ {user.home} /build.properties. In this case the problem you indicated doesn't appear. On the other hand : is there a sense in overriding the default value of maven.repo.local in project.properties? if you have 20 Maven projects that have to use the same local repository, then you have to verify 20 times project.properties having several local Maven repositories on your machine seems pointless to me (it is only a local cache of what is available on the central repositories)
Hide
Permalink
Jamie Bisotti added a comment -

If a property can be over-ridden, it should be capable of being over-ridden from anywhere (i.e. command line, ${user.home|/build.properties, project.properties, etc.). A new user might not think to try all 10,000 different ways of doing the same thing; they might (probably will) stop after the first, obvious, way of doing it does not work. I'm not saying putting it in project.propeties makes sense or is the best way to do it; I'm saying it isn't working as advertised.

So, are you saying putting it in $

{user.home}

/build.properties works with 1.0.2?

Jamie

Show
Jamie Bisotti added a comment - If a property can be over-ridden, it should be capable of being over-ridden from anywhere (i.e. command line, ${user.home|/build.properties, project.properties, etc.). A new user might not think to try all 10,000 different ways of doing the same thing; they might (probably will) stop after the first, obvious, way of doing it does not work. I'm not saying putting it in project.propeties makes sense or is the best way to do it; I'm saying it isn't working as advertised. So, are you saying putting it in $ {user.home} /build.properties works with 1.0.2? Jamie
Hide
Permalink
Davy Toch added a comment -

Regarding your question:

"So, are you saying putting it in $

{user.home}

/build.properties works with 1.0.2?"

Answer : yes (tested on Maven 1.0.2 and Maven 1.1 beta1)

Show
Davy Toch added a comment - Regarding your question: "So, are you saying putting it in $ {user.home} /build.properties works with 1.0.2?" Answer : yes (tested on Maven 1.0.2 and Maven 1.1 beta1)

People

  • Assignee:
    Unassigned
    Reporter:
    Jamie Bisotti
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: