Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:[EMAIL PROTECTED])
-
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-676
Here is an overvie
Message:
A new issue has been created in JIRA.
-
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-676
Here is an overview of the issue:
Message:
The following issue has been closed.
Resolver: Andrew Stevens
Date: Wed, 15 Oct 2003 3:28 PM
That's not an error. {0} is used for all per-class merge files, in all modules.
However, the merge files need to go in the same package/directory hierarchy *below*
your specifie
On Wed, 2003-10-15 at 19:44, [EMAIL PROTECTED] wrote:
> All - am just porting to websphere, and despite my disappointment /w
> their db-vendor-specific backends/*xmi files, have found it is not
> implemented in xdoclet either.
>
> Just curious if anyone has used xdoclet successfully /w websphere -
All - am just porting to websphere, and despite my disappointment /w
their db-vendor-specific backends/*xmi files, have found it is not
implemented in xdoclet either.
Just curious if anyone has used xdoclet successfully /w websphere - can
you confirm that you have to manually maintain the *xmi fi
I wrote a tutorial for extending XDoclet, including adding new modules.
It's now on the web at
http://www.vecna.com/whatWeDo/techNotes/xdoclet-new-module.html
Constructive feedback welcome.
-- Bill
---
This SF.net email is sponsored by: S
