[ http://issues.apache.org/struts/browse/WW-1392?page=comments#action_38691 ] Ted Husted commented on WW-1392: --------------------------------
Recap: We moved all of the Struts 2 build over the Maven, except for the taglib generation. I experimented with the Maven taglib plugin (with the ActionComponents and ActionErrors classes), but I've gone cold on going this way. The plugin would encourage us to put everything back in the TLD, which would make it huge, and JSP 2.0 seems to be phasing out TLDs anyway. The original WW2 approach that uses XDocLet/Confluence/Snippet approach is a great way to go, we just need to get that working again. The problem seems to be that we can't call the standard XDoclet release from the Maven 2 build, because XDoclet doesn't support J5 -- though there are patches that are suppose to bring XDoclet up to date. See the end of this thread * http://forums.opensymphony.com/thread.jspa?threadID=37887&tstart=15 Of course, getting everyone who needs to build a Struts 2 assembly to install a patched XDoclet is problematic. And all we really need XDoclet to do is generate the TLD. I doubt that the taglibs are using any J5 features that would confuse XDoclet. A leg-up might be to create a simple Ant build script that does nothing but invoke XDoclet to generate the TLD. Once we have that,we could run from the Maven build. > Generate Taglib TLD from annotations/xdoclet tags > ------------------------------------------------- > > Key: WW-1392 > URL: http://issues.apache.org/struts/browse/WW-1392 > Project: Struts 2 > Issue Type: Improvement > Components: Views > Reporter: Don Brown > Priority: Minor > Fix For: 2.0.2 > > > Previously in WebWork 2, the taglib TLD was generated using XDoclet from > XDoclet tags in the source code. With the move to Maven 2 and Java 5, the > ant tasks that performed this task have been removed and XDoclet doesn't work > with Java 5 source. Therefore, either we should migrate the process to a new > XDoclet 2 plugin or using some Java 5 annotation processing tool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
