blog. generateReleasePoms is one such feature but it's broken
by SCM bug 323. So, a new release would be great!
brettporter wrote:
>
> Anyone think a 1.0.1 release with the current fixes might be in order?
>
> - Brett
>
> On 05/01/2008, at 4:42 AM, brewk9 wrote:
>
>>
>> I
I see this is fixed - how can I get it in a release?
--
View this message in context:
http://www.nabble.com/When-will-SCM-bug-323-be-released--tp14622415s177p14622415.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---
I see this is fixed - just wondering how/when it would be available in a
release?
--
View this message in context:
http://www.nabble.com/When-will-SCM-bug-323-be-released--tp14621616s177p14621616.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
I am using -DgenerateReleasePoms=true. When I run release:prepare, maven
creates and adds the release-pom.xml to perforce. Then, when I run
release:perform, maven deletes release-pom.xml from perforce. Then, when I
run release:prepare for a subsequent release, maven fails to readd
release-pom.xml
