Thanks. I had briefly considered it yesterday, but promptly forgot
about as I attempted to remember everything else I wanted to say.
I suppose this will be a chance to test out pluginManagement in the
parent POM, as the current configuration for this is in several
projects...
-Stephen
On 4/11/0
I don't know much about these assembly changes etc so I can't comment
on any of that. Perhaps search the dev@ list to find more details.
Here's another idea you might not have considered... You could find
out the version number for the old (working) assembly plugin and
specify it directly in your
I know I'm a bit slow here, as it appears these changes were released
quite a while ago. But still, I've just noticed today the issue
(discussed before, but since I didn't realize it was affecting ME, I
didn't pay attention!) regarding the assembly plugin forking the
lifecycle, causing my existing
