| suppress documentation [message #881815] |
Tue, 05 June 2012 05:46  |
 Martin Taal
Messages: 5049
Registered: July 2009 |
Senior Member |
|
|
Hi,
I am generating EMF code from an xsd (eclipselink orm) which contains invalid documentation. Meaning if the
documentation from the xsd is included in the java code I get compile errors.
Is there a way to suppress documentation generation in the java code? Or to prevent it being transferred from the xsd to
the ecore model?
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxx - mtaal@xxxxxxxx
Web: www.springsite.com - www.elver.org
|
|
|
|
|
| Re: suppress documentation [message #881928 is a reply to message #881905] |
Tue, 05 June 2012 10:05  |
Ed Merks
Messages: 24540
Registered: July 2009 |
Senior Member |
|
|
Martin,
We should probably handle that someone in the conversion process or in
the generator...
On 05/06/2012 3:18 PM, Martin Taal wrote:
> The documentation in the xsd contains javadoc start and end tags (/*
> and */) so these are placed in the javadoc
> resulting in an early end of the comment.
>
> gr. Martin
>
> On 06/05/2012 02:51 PM, Ed Merks wrote:
>> Martin,
>>
>> No, there's no way to exclude that. What does it look like?
>>
>>
>> On 05/06/2012 11:46 AM, Martin Taal wrote:
>>> Hi,
>>> I am generating EMF code from an xsd (eclipselink orm) which
>>> contains invalid documentation. Meaning if the
>>> documentation from the xsd is included in the java code I get
>>> compile errors.
>>>
>>> Is there a way to suppress documentation generation in the java
>>> code? Or to prevent it being transferred from the xsd
>>> to the ecore model?
>>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.01819 seconds
] 
Search
Help
Register
Login
Home
