Thilo Goetz wrote:
Marshall Schor wrote:
Work-around:
Until a better resolution happens, you can get around this problem by
going to your local .m2 repository, editing the file
...org\apache\maven\plugins\maven-antrun-plugin\1.1\maven-antrun-plugin-1.1.pom
and changing the lines:
Is this really a good time to be making all these changes to
the build? We're supposed to be releasing soon, and we don't
have a reliable build for testing. I'd suggest we try to
stabilize the build now and wait with further improvements
until early in the next release cycle.
I agree these kinds of changes are best made early in the release
cycle. I think what we're seeing is the tail end of consequences from
doing that. This particular issue (with Ant level) was driven by
changes made early in the release cycle to how the Eclipse update site
was being built. Part of that change was the need to launch an Eclipse
service to do the build, and the launcher had a suffix which changed
with every small Eclipse release. Googling suggested a way to fix this,
using an Ant copy task. That all worked fine until one day when Michael
B. had a configuration which had multiple versions of this in his
Eclipse installation. To get around that, I did a fix which uses some
features of Ant 1.7.0, and it worked for me. But didn't work for
Michael, due to this ant level problem. In "digging down" to find out
why, I started this thread, because the "fix" Michael got to work for
him at some point stopped working for me...
The only other "build" issue I know of to work on at this point is some
kind of automation for our changing the build version information. I'd
like to get that automated if possible, because it's quite error prone -
in that it's easy to leave out something.
-Marshall
