Benoit Callebaut wrote:
>> I'm curious what your plugin really does. Is it that you run Jelly to
>> generate the source code fragment, then inject that to the generated
>> class by using the "direct" statements?
>
> That is how it works today. But I plan to expand it.
> Some of the ideas are :
> * Implement JAXB specific tag libraries
> * Be able to call a script from a "script registry". For example to
> automatically add indexing code or key generation code
> * Post process the code model using XSL like scripts
> * Insert Java code as XML tags
> * Parametrizable scripts through system properties,arguments or even
> better through tags inserted in the POM file.
Nice. I think this would be very interesting.
>> It would be really interesting if the Jelly script has access to the
>> object model inside the schema compiler. Then it can work like a
>> meta-plugin, in a way.
>
> I am currently trying this approach. I can already use classes declared
> as dependencies in my plugin. I have still to define a way tofor my
> plugin to detect the classes that are usable. (same approach as the JAXB
> plugins for example)
>
>>
>>> At the moment my plugin is only a proof of concept and is far from
>>> being fully tested but It can alredy do more than the code injector
>>> plugin.
>>>
>>> If somebody is interested, I am ready to put it on jaxb2-commons.
>>
>>
>> Definitely! Please tell me your java.net ID so that I can add you.
>
> Here is my login : bencal
I added you as a developer. Please take a look at
https://jaxb2-commons.dev.java.net/contribute.html
We need to decide the name of your plugin, then we can create a
directory, and then everything else is up to you!
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com