[ http://jira.codehaus.org/browse/MEAR-37?page=comments#action_73637 ] 
            
Stephane Nicoll commented on MEAR-37:
-------------------------------------

This is not an ear plugin bug IMO. It's a maven core related thing. We're 
discussing this subject on the dev list for the past few weeks. As soon as I 
have more details, i'll keep you posted.

> Parameters ignored when set on the command line
> -----------------------------------------------
>
>                 Key: MEAR-37
>                 URL: http://jira.codehaus.org/browse/MEAR-37
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>         Environment: Win XP
>            Reporter: Shelley L
>
> Several maven2 ear plugin configuration options seem to be ignored when set 
> through the command line.  The parameters outputDirectory, earName, 
> workDirectory, and applicationXml are honored when set in the POM, but 
> ignored when set on the command line.
> For example:
>   After setting the workDirectory in the POM, and executing "mvn ear:ear," 
> the outputDirectory is "test" as expected.
>          <configuration>
>                   <outputDirectory>test</outputDirectory>
>          </configuration>
>   Other configuration options are honored as expected as well.
>   However, when executing the ear goal from the command line, passing the 
> configuration options using their expressions, the parameters are ignored.  
> After executing the following:
>          mvn clean ear:ear -Dproject.build.directory=test
>   The outputDirectory remains the default "target," or whatever has been 
> defined in the POM.

-- 
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

        

Reply via email to