[jira] Commented: (MAVEN-1357) make maven inherit properties from parent projects

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: Carlos Sanchez
    Created: Fri, 2 Jul 2004 10:50 AM
       Body:
Maven does inherit properties.

Check putty and cygwin ssh clients for windows
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1357?page=comments#action_21305

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1357

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1357
    Summary: make maven inherit properties from parent projects
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: 4 hours
 Time Spent: Unknown
  Remaining: 4 hours

    Project: maven
 Components: 
             core
   Versions:
             1.0-rc3

   Assignee: 
   Reporter: Eirik Maus

    Created: Fri, 2 Jul 2004 9:58 AM
    Updated: Fri, 2 Jul 2004 10:50 AM

Description:
The only reasonable way I have found to share repository for windows-based developers is to have all local projects extend a common parent project. 

Windows-based organisations have the following in common:
- one maven installation per (client) computer, 
- no ssh

Consequently, 
- the deploy plugin cannot be configured to deploy to local network directory (necessary for commercial closed-source projects), as it is based on ssh. 
- making local adjustments based on a custom plugin in no good, since everybody most manually install the plugin ang make sure they are up-to-date with it all the time. 

So, I made a common "site-defaults" project with some goals, and made all projects inherit from it. And everything is inherited EXCEPT the property values that specify locations of fiels, urls to repository etc. 

The property values work for the goals in the project at the same level that they are defined, but they are not available in the inheriting project, so they cannot be used to adjust plugin parameters in the "real" projects. 

I cannot see any reason for this behaviour, and find it contratictory to the behaviour of inheriting maven.xml and project.xml contents. I think "parent-project/project.properties" should be first for the properties evaluation, before project.properties, build.properties and ~/*.properties


---------------------------------------------------------------------
JIRA INFORMATION:
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org