Gregory Kick wrote:
>> Oh, yes. Yeah, that would be a good enough hack. Although it would
>> be fun and the right thing to write Maven plugins for some of those
>> codegen tasks --- for example, the annotation writer compiler in
>> codemodel is something useful outside the JAXB RI, so it makes
>> sense to write a maven plugin for that. I thought it's supposed to
>> be not too hard to write a maven plugin.
>
> You're right. They're pretty easy. So, if there's human bandwidth,
> I'm all for it, but copying and pasting ant tasks would be a quick
> transition.
Sounds good to me.
>> There are other codegen that are quickly put together just for the
>> JAXB RI, and those thing could be done by maven-antrun-plugin.
>>
>> The other concern that I have is the packaging. We have a rather
>> complicated re-jaring scheme and I really don't want to change it
>> to avoid affecting our users.
>
> Well, on the one hand, complicated re-jaring is never something I
> want to hold on to. :-)
OK, you can leave that to me. You can do the fun part and I'll do the
dirty work. After all, I'm paid to do this, and sometimes there're
downsides :-)
> But, I think that the assembly plugin (I've
> never used it, but I know it can re-jar things) can accomplish
> whatever tasks are lurking in the build files.
Thanks. I'll check what it is.
>> Would you be interested in becoming a committer and drive this
>> effort? We can work on Maven build configurations while we still
>> retain Ant ones for a while. When everything looks good, we can
>> make a switch and be happier :-)
>
> Sure. This aligns itself perfectly with the work I'm doing with the
> maven2-repository and maven-archetypes projects.
Cool! I sent you a private e-mail on this.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com