[XDoclet-JIRA] Commented: (XDT-1505) You cannot use the same doclet twice

"Fiann O'Hagan (JIRA)" <[email protected]>
Newsgroups gmane.comp.java.xdoclet.devel
Message-ID <[email protected]>
    [ http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1505?page=comments#action_17291 ] 

Fiann O'Hagan commented on XDT-1505:
------------------------------------

We have found this issue with the <jmxdoclet> task too.

		<jmxdoclet destdir="${output1}" excludedtags="@version,@author,@todo">
			<fileset dir="${build.src}">
				<include name="**/common/*" />
			</fileset>
			<mbeaninterface/>
			<mx4jdescription/>
		</jmxdoclet>
     <!-- Next task also generates to output1! -->
		<jmxdoclet destdir="${output2}" excludedtags="@version,@author,@todo">
			<fileset dir="${build.src}">
				<include name="**/server/*" />
			</fileset>
			<mbeaninterface/>
			<mx4jdescription/>
		</jmxdoclet>

> You cannot use the same doclet twice
> ------------------------------------
>
>          Key: XDT-1505
>          URL: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1505
>      Project: XDoclet
>         Type: Bug
>   Components: Core
>     Versions: 1.2.3
>     Reporter: Kenney Westerhof
>     Assignee: xdoclet-devel (Use for new issues)
>     Priority: Critical

>
>
> When you use the same doclet task twice (in a build.xml file,
> or 'embedded'),  SubTasks shared between the two definitions
> will always be the same. I.e.:
> <target>
>   <!-- will create sessoin beans in dir A. -->
>   <ejbdoclet destDir="A">
>     <session/>
>   </ejbdoclet>
>   <!-- will create session beans in dir A also! -->
>   <ejbdoclet destDir="B">
>     <session/>
>   </ejbdoclet>
>   <!-- will create session beans in dir C -->
>   <ejbdoclet destDir="C">
>     <session destDir="C"/>
>   </ejbdoclet>
> SubTask.init() checks for null values (for destDir e.a.).
> If they're null, it inherits them from the parent DocletTask.
> If they're not null (the second time it gets called), they don't
> get reconfigured.
> Having a flag in SubTask doesn't solve this - the subtaskmap should
> be reset, so all fields are properly reconfigured, or after execute
> is finished, the fields should be set to null.
> I know there are some related issues that are solved too by this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.