This situation was discussed once before. The author of this pom, as I
recall, had pretty strong feelings about it.
You can work with it by making your own profile named apache_release
that has the additional stuff you want, or by overriding the execution
configuration in your pom to use your preferred <arguments/>.
On Thu, Dec 29, 2011 at 10:18 PM, David Blevins <david.blev...@gmail.com> wrote:
> On Tue, Sep 27, 2011 at 1:09 PM, David Blevins <david.blev...@gmail.com>
> wrote:
>> Did some more digging and it seems the issue is in the apache-10 parent pom.
>> If you alter it like so, the arguments are passed as expected:
>>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-release-plugin</artifactId>
>> <version>2.1</version>
>> <configuration>
>> <useReleaseProfile>false</useReleaseProfile>
>> <goals>deploy</goals>
>> <!--<arguments>-Papache-release</arguments>-->
>> <arguments>-Papache-release ${arguments}</arguments>
>> </configuration>
>> </plugin>
>>
>> Seems this is just a mistake as the full config as reported via -X contains
>> quite a bit of <foo>${foo}</foo> style declarations. We likely just missed
>> it here.
>>
>> Going to use a hacked parent pom for the moment but it would be great if we
>> could get an apache-11 pom out soonish.
>
> This came up again. Posting so I don't forget to deal with it when I
> have time. Will file an issue with a patch tomorrow unless someone
> beats me to it.
>
>
> -David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
