I was having the same problem last week. To fix it, what I did was pull xwork2 from SVN and build with maven (although in some cases, I had to disable the unit tests because one failed sometimes [probably my fault]). Then once it is built, maven will use it.
After that, make sure you have the latest trunk (at least as of this morning) and try to build with maven and most likely skip the unit tests since there were a lot more failures in the struts2 unit tests. Pseudo-sh code - svn co http://svn.opensymphony.com/svn/xwork/trunk xwork cd xwork mvn -Dmaven.test.skip=true -Pall cd .. svn co https://svn.apache.org/repos/asf/struts/current/ struts cd struts/struts2 mvn -Dmaven.test.skip=true -Pall -W > -----Original Message----- > From: Engelking, Nicholas > [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 25, 2007 10:15 AM > To: 'Struts Users Mailing List' > Subject: RE: struts 2.1 beta > > I am trying to build from the head but I am getting build > errors. I have changed my pom.xml in core to point to the new > xwork id as mentioned in the mailing list archives: > > <groupId>com.opensymphony.xwork</groupId> > to > <groupId>opensymphony</groupId> > > However I am getting build errors when I run maven due to > what appears to be missing xwork resources. > > C:\STRUTS2\struts\core\src\main\java\org\apache\struts2\views\ jsp\ui\OgnlTool.java:[27,36] package > com.opensymphony.xwork2.ognl does not exist > > C:\STRUTS2\struts\core\src\main\java\org\apache\struts2\dispat cher\ServletActionRedirectResult.java:[39,47] package > com.opensymphony.xwork2.util.reflection does not exist > > C:\STRUTS2\struts\core\src\main\java\org\apache\struts2\views\ util\ContextUtil.java:[65,70] cannot find symbol > > symbol : variable CONTAINER > location: class com.opensymphony.xwork2.ActionContext > > among many others. > > I built using maven from head last week and have tried > cleaning out my local maven repository. Any thoughts? It > seems the maven scripts may not be up to date or pointing to > the wrong dependencies. > > -----Original Message----- > From: Dave Newton [mailto:[EMAIL PROTECTED] > Sent: September 25, 2007 8:56 AM > To: Struts Users Mailing List > Subject: Re: struts 2.1 beta > > If you want a complete build of an un-released version then > AFAIK you need to build it from source. The repository > contains the dependent libraries. > > The nightly builds are just that, builds, not distributions > (again, AFAIK). > > --- [EMAIL PROTECTED] wrote: > > I just need to grab the nightly version WITH DEPENDANTS > LIBRAIRIES if > > it exist. > > the link below > > > http://struts.apache.org/2.x/docs/building-the-framework-from- > source.html > > drive me to that one > > > http://people.apache.org/builds/struts/nightlies/2.x/ > > > > No librairies. > > Meissa > > > > > > > > Dave Newton <[EMAIL PROTECTED]> > > 25/09/2007 14:28 > > Veuillez répondre à > > "Struts Users Mailing List" <user@struts.apache.org> > > > > > > A > > Struts Users Mailing List <user@struts.apache.org> cc > > > > Objet > > Re: struts 2.1 beta > > > > > > > > > > > > > > --- Oleg Mikheev <[EMAIL PROTECTED]> wrote: > > > Dave Newton wrote: > > > >> I have just renamed it to struts2-core.jar and replaced in my > > > >> application that was working > > with > > > >> 2.0.9 version. > > > > > > > > You can't just randomly replace libraries. > > > > > > You can replace 2.0.8 with 2.0.9, but you can't replace > 2.0.9 with > > > 2.1.0 > > > > You certainly *could*, but it would still make me nervous > w/o testing > > since XWork revved also... I guess I always think that > dropping in a > > new library revision w/o keeping track of library dependencies is > > risky. > > > > d. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > > L'integrite de ce message n'etant pas assuree sur internet, > Natixis ne > > peut etre tenu responsable de son contenu. Toute utilisation ou > > diffusion non autorisee est interdite. Si vous n'etes pas > destinataire > > de ce message, merci de le detruire et d'avertir l'expediteur. > > Ensemble, faisons un geste pour l'environnement : > > n'imprimons nos mails que si necessaire > > > > The integrity of this message cannot be guaranteed on the Internet. > > Natixis can not therefore be considered responsible for the > contents. > > Any unauthorized use or dissemination is prohibited. If you are not > > the intended recipient of this message, then please delete it and > > notify the sender. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ******************** > NOTICE OF CONFIDENTIALITY > This communication including any information transmitted with > it is intended only for the use of the addressees and is > confidential. > If you are not an intended recipient or responsible for > delivering the message to an intended recipient, any review, > disclosure, conversion to hard copy, dissemination, > reproduction or other use of any part of this communication > is strictly prohibited, as is the taking or omitting of any > action in reliance upon this communication. > If you receive this communication in error or without > authorization please notify us immediately by return e-mail > or otherwise and permanently delete the entire communication > from any computer, disk drive, or other storage medium. > > If the above disclaimer is not properly readable, it can be > found at www.td.com/legal > > AVERTISSEMENT DE CONFIDENTIALITE > Ce courriel, ainsi que tout renseignement ci-inclus, destiné > uniquement aux destinataires susmentionnés, est > confidentiel. Si vous n'êtes pas le destinataire prévu ou un > agent responsable de la livraison de ce courriel, tout > examen, divulgation, copie, impression, reproduction, > distribution, ou autre utilisation d'une partie de ce > courriel est strictement interdit de même que toute > intervention ou abstraction à cet égard. Si vous avez reçu > ce message par erreur ou sans autorisation, veuillez en > aviser immédiatement l'expéditeur par retour de courriel ou > par un autre moyen et supprimer immédiatement cette > communication entière de tout système électronique. > > Si l'avis de non-responsabilité ci-dessus n'est pas lisible, > vous pouvez le consulter à www.td.com/francais/legale > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]