You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Wim Deblauwe (JIRA)" <ji...@codehaus.org> on 2005/05/31 20:20:21 UTC

[jira] Created: (MAVEN-1610) failing inheritance for project.properties

failing inheritance for project.properties
------------------------------------------

         Key: MAVEN-1610
         URL: http://jira.codehaus.org/browse/MAVEN-1610
     Project: maven
        Type: Bug
    Versions: 1.0.2    
 Environment: Maven 1.0.2
Windows XP
    Reporter: Wim Deblauwe
 Attachments: pmdproblem.zip

All my projects extend from a master project.xml. Along this is a
project.properties file. Normally these values are being used, the
same as they where in a project.properties file along the "real"
project.xml. But I have a problem with the PMD plugin. It seems that
this rule is not being followed.

I created a test with this structure:

+ moduleA
   |
  + project.xml
  + project.properties
+ rootProject
  |
  + project.xml
  + project.properties

In my project.xml I <extend>..\rootproject\project.xml</extend>

In project.properties I have:
maven.jar.override=on
maven.jar.pmd=3.1

When running "maven pmd" from the moduleA directory with these
properties in the project.properties of moduleA, I get an error from
pmd that I should specify the 'targetjdk' value, which is good(!)
because that way I'm sure I'm using the new version 3.1.
However when I move these properties to the project.properties of
rootproject, pmd does not give an error, meaning that he is not using
the new jar.

I have attached a setup that demonstrates the problem.


-- 
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
-
For more information on JIRA, 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


[jira] Updated: (MAVEN-1610) failing inheritance for project.properties

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MAVEN-1610?page=all ]

Brett Porter updated MAVEN-1610:
--------------------------------

    Fix Version: 1.1-beta-1

> failing inheritance for project.properties
> ------------------------------------------
>
>          Key: MAVEN-1610
>          URL: http://jira.codehaus.org/browse/MAVEN-1610
>      Project: maven
>         Type: Bug
>     Versions: 1.0.2
>  Environment: Maven 1.0.2
> Windows XP
>     Reporter: Wim Deblauwe
>      Fix For: 1.1-beta-1
>  Attachments: pmdproblem.zip
>
>
> All my projects extend from a master project.xml. Along this is a
> project.properties file. Normally these values are being used, the
> same as they where in a project.properties file along the "real"
> project.xml. But I have a problem with the PMD plugin. It seems that
> this rule is not being followed.
> I created a test with this structure:
> + moduleA
>    |
>   + project.xml
>   + project.properties
> + rootProject
>   |
>   + project.xml
>   + project.properties
> In my project.xml I <extend>..\rootproject\project.xml</extend>
> In project.properties I have:
> maven.jar.override=on
> maven.jar.pmd=3.1
> When running "maven pmd" from the moduleA directory with these
> properties in the project.properties of moduleA, I get an error from
> pmd that I should specify the 'targetjdk' value, which is good(!)
> because that way I'm sure I'm using the new version 3.1.
> However when I move these properties to the project.properties of
> rootproject, pmd does not give an error, meaning that he is not using
> the new jar.
> I have attached a setup that demonstrates the problem.

-- 
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
-
For more information on JIRA, 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


[jira] Closed: (MAVEN-1610) failing inheritance for project.properties

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MAVEN-1610?page=all ]
     
Brett Porter closed MAVEN-1610:
-------------------------------

    Fix Version:     (was: 1.1-beta-2)
     Resolution: Duplicate

> failing inheritance for project.properties
> ------------------------------------------
>
>          Key: MAVEN-1610
>          URL: http://jira.codehaus.org/browse/MAVEN-1610
>      Project: maven
>         Type: Bug
>     Versions: 1.0.2
>  Environment: Maven 1.0.2
> Windows XP
>     Reporter: Wim Deblauwe
>  Attachments: pmdproblem.zip
>
>
> All my projects extend from a master project.xml. Along this is a
> project.properties file. Normally these values are being used, the
> same as they where in a project.properties file along the "real"
> project.xml. But I have a problem with the PMD plugin. It seems that
> this rule is not being followed.
> I created a test with this structure:
> + moduleA
>    |
>   + project.xml
>   + project.properties
> + rootProject
>   |
>   + project.xml
>   + project.properties
> In my project.xml I <extend>..\rootproject\project.xml</extend>
> In project.properties I have:
> maven.jar.override=on
> maven.jar.pmd=3.1
> When running "maven pmd" from the moduleA directory with these
> properties in the project.properties of moduleA, I get an error from
> pmd that I should specify the 'targetjdk' value, which is good(!)
> because that way I'm sure I'm using the new version 3.1.
> However when I move these properties to the project.properties of
> rootproject, pmd does not give an error, meaning that he is not using
> the new jar.
> I have attached a setup that demonstrates the problem.

-- 
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
-
For more information on JIRA, 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


[jira] Updated: (MAVEN-1610) failing inheritance for project.properties

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MAVEN-1610?page=all ]

Brett Porter updated MAVEN-1610:
--------------------------------

    Fix Version:     (was: 1.1-beta-1)
                 1.1-beta-2

verified its existence

> failing inheritance for project.properties
> ------------------------------------------
>
>          Key: MAVEN-1610
>          URL: http://jira.codehaus.org/browse/MAVEN-1610
>      Project: maven
>         Type: Bug
>     Versions: 1.0.2
>  Environment: Maven 1.0.2
> Windows XP
>     Reporter: Wim Deblauwe
>      Fix For: 1.1-beta-2
>  Attachments: pmdproblem.zip
>
>
> All my projects extend from a master project.xml. Along this is a
> project.properties file. Normally these values are being used, the
> same as they where in a project.properties file along the "real"
> project.xml. But I have a problem with the PMD plugin. It seems that
> this rule is not being followed.
> I created a test with this structure:
> + moduleA
>    |
>   + project.xml
>   + project.properties
> + rootProject
>   |
>   + project.xml
>   + project.properties
> In my project.xml I <extend>..\rootproject\project.xml</extend>
> In project.properties I have:
> maven.jar.override=on
> maven.jar.pmd=3.1
> When running "maven pmd" from the moduleA directory with these
> properties in the project.properties of moduleA, I get an error from
> pmd that I should specify the 'targetjdk' value, which is good(!)
> because that way I'm sure I'm using the new version 3.1.
> However when I move these properties to the project.properties of
> rootproject, pmd does not give an error, meaning that he is not using
> the new jar.
> I have attached a setup that demonstrates the problem.

-- 
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
-
For more information on JIRA, 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