You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2007/03/13 23:37:34 UTC
[jira] Closed: (MECLIPSE-157) xdoclet facet for xdoclet-enabled
ejb/web projects
[ http://jira.codehaus.org/browse/MECLIPSE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MECLIPSE-157.
-----------------------------------
Assignee: Carlos Sanchez
Resolution: Duplicate
> xdoclet facet for xdoclet-enabled ejb/web projects
> --------------------------------------------------
>
> Key: MECLIPSE-157
> URL: http://jira.codehaus.org/browse/MECLIPSE-157
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: WTP support
> Reporter: christian heinzer
> Assigned To: Carlos Sanchez
>
> A way to generate ebj/web projects with XDoclet (=additional jst.ejb.xdoclet/jst.web.xdoclet facet) would be appreciated.
> For ebj/web projects org.apache.maven.plugin.eclipse.writers.EclipseWtpFacetsWriter already adds jst.java and jst.ejb/jst.web facets in .settings/org.eclipse.wst.common.project.facet.core.xml.
> XDoclet authoring can be enabled by adding:
> <installed facet="jst.ejb.xdoclet" version="1.2.3"/> or
> <installed facet="jst.web.xdoclet" version="1.2.3"/>
> inside element <faceted-project>.
> It would probably be best to make this additional facet optional and the version configurable. Or perhaps you can even include it based on the maven-xdoclet plugin used in build (and correct xdoclet version extracted from there)? But for a start even a dummy version resolver as found in resolveEjbVersion would be better than no xdoclet support at all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira