Maven 1

Property "maven.home.local" doesn't get overriden

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 1.0.1
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
  • Number of attachments :
    0

Description

The property "maven.home.local" doesn't get overidden anymore with an entry in project.properties. It always defaults to "${user.home}/.maven"

There is a workaround for this issue:

- Create the file "build.properties" in ${user.home} and set the property "maven.home.local" to the desired directory.

Issue Links

Activity

Hide
Ross Burnett added a comment -

I'm not sure if the current behaviour is by accident or design, but I believe that it is correct and should not be changed.

The project.properties file is for project-specific, not user-specific, properties. Since ${maven.home.local} is about a user's own local environment, it shouldn't be set in project.properties. Doing so could lead to build failures if not all users have access to the specified path.

Or is there some valid use case that I've missed?

Show
Ross Burnett added a comment - I'm not sure if the current behaviour is by accident or design, but I believe that it is correct and should not be changed. The project.properties file is for project-specific, not user-specific, properties. Since ${maven.home.local} is about a user's own local environment, it shouldn't be set in project.properties. Doing so could lead to build failures if not all users have access to the specified path. Or is there some valid use case that I've missed?
Hide
Erwin van der Koogh added a comment -

There are valid use cases yes.. The way we have set it up here at work is to have project specific repositories on our local network.

And the issue is that it was possible in a previous version and people are using it. We have quite a few projects set up like this.

Show
Erwin van der Koogh added a comment - There are valid use cases yes.. The way we have set it up here at work is to have project specific repositories on our local network. And the issue is that it was possible in a previous version and people are using it. We have quite a few projects set up like this.
Hide
Brett Porter added a comment -

that'll likely be fixed, but it's not a valid use case. You should be changing maven.repo.local

I don't understand why differing local repos per project is useful though?

Show
Brett Porter added a comment - that'll likely be fixed, but it's not a valid use case. You should be changing maven.repo.local I don't understand why differing local repos per project is useful though?

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: