[ http://jira.codehaus.org/browse/MPCLOVER-34?page=comments#action_31324 ]
     
Vincent Massol commented on MPCLOVER-34:
----------------------------------------

hmm... Are you sure? :-)

I mean here's the code we have in plugin.jelly:

    <j:if test="${!empty(context.getVariable('maven.clover.license.path'))}">
      <j:invokeStatic className="java.lang.System" method="setProperty">
        <j:arg type="java.lang.String" value="clover.license.path"/>
        <j:arg type="java.lang.String" value="${maven.clover.license.path}"/>
      </j:invokeStatic>
    </j:if>

The context is inherited from the parent project so everything there should 
work. Any idea on how to fix this (if it's really a problem)?

Thanks

> Specifying the license file should only be done once
> ----------------------------------------------------
>
>          Key: MPCLOVER-34
>          URL: http://jira.codehaus.org/browse/MPCLOVER-34
>      Project: maven-clover-plugin
>         Type: Bug
>  Environment: Maven 1.0.2
>     Reporter: Wim Deblauwe

>
>
> In Maven, when your project.xml extends from a root project.xml (in a 
> different directory), then the project.properties that goes with that root 
> project.xml is also read by Maven. However when I specifiy the 
> 'maven.clover.license.path' in that project.properties file, it is not picked 
> up by the real project. It searches in the default location.
> This might clear this a bit up:
> root
> + rootproject.xml
> + project.properties (I want to specify the license location once here!)
> + somemodule
>      + project.xml (extends rootproject.xml)
> + someothermodule
>      + project.xml (extends rootproject.xml)

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to