I looked again at a clean checkout and found the reference. The assembly POM in my usual working copy was missing the XWork stanza. I'm not sure when I did that or why.
The other thing is why do we get the Embedded error: C:\projects\Apache\struts2-clean\assembly\..\target\site isn't a directory. prompt on a clean build. Every artifact in the assembly seems to generate this error. Creating the directory cures the problem, but only until the next clean build. Is it a Windows issue? -Ted. On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote:
I can't even find the XWork reference in the POM assembly. :) Why don't you go ahead and fix the parent POM, and then we'll tag it. -Ted. On 12/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 12/31/06, Ted Husted <[EMAIL PROTECTED]> wrote: > > On 12/30/06, Ted Husted <[EMAIL PROTECTED]> wrote: > > > OK, I'll get ready to roll another release then. > > > > I've updated the release notes with the latest changes, and I'm > > preparing to tag and roll Struts 2.0.2 against XWork 2.0 RC 1. > > Just FYI, the assembly module's pom has the wrong XWork version number > in it, so the build fails. > > (That should be controlled with a property in the parent pom; I'll fix > it after you tag 2.0.2.)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
