RE: [Clirr-devel] maven plugin

[Vincent M. <vma...@pi...>]

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Simon Kitching
> Sent: lundi 5 juillet 2004 01:09
> To: cli...@li...
> Subject: Re: [Clirr-devel] maven plugin
>=20
> On Sun, 2004-07-04 at 18:29, Lars K=FChne wrote:
> > Vincent Massol wrote:
> > >>>
> > >>>I've tried 3 times to garner interest in refactoring the clirr
> directory
> > >>>structure in order to support integration modules such as Ant,
> Eclipse
> > >>>plugin, Maven plugin, Cli, etc. I've even spent time showing what =
it
> > >
> [stuff removed]
>=20
> I'm also keen to see a Maven plugin, and agree Clirr is the best place
> to host it.

cool

>=20
> I have only one (minor) reservation about your original proposal. I =
did
> raise this by email, but didn't see any response. It is the matter of
> moving the "cli" stuff into a subpackage. I think the command
>   java net.sf.clirr.cli.Clirr
> is already quite long enough without moving the cli stuff into a
> subpackage :-).

Fine. This doesn't impact the directory structure.

>=20
> Still, if (for some reason) moving the cli "main" class is absolutely
> necessary to implement a Maven plugin, I could live with it.
>=20
> Apart from that, I'm all for integrating the maven code as soon as
> possible.
>=20
>=20
> > The simplest thing is to create a module 'core' and simply move
> > everything we have now (including cli and ant) into that module. You =
can
> > then start committing the Maven plugin into a different module, so =
we
> > end up with two multiproject modules, 'core' and 'maven'.
>=20
> That would make the start command for the cli into this?
>   java net.sf.clirr.core.cli.Clirr
>=20
> >
> > I'm not convinced anyway that it makes sense to have cli and ant in
> > different packages: the jar would basically consist of one class =
file...
> > If someone disagrees we can do further split-up later.
>=20
> I tend to agree.

Sure. Let's do TSTTCPW ;-)

>=20
> >
> > Simon, do you have uncommitted changes on your hard drive?
>=20
> There's nothing I can't modify fairly easily. Don't let this stop you
> from getting started...
>=20
> >
> > >>    * the Maven plugin should be hosted by Clirr itself, because =
that
> > >>      would improve the user experience (one-stop shopping) a lot!
> > >>
> > >>
> > >
> > >Cool. I also think so.
>=20
> Me too. If only the UN could agree so easily :-)
>=20
>=20
> > I can understand your frustration, and I think we should start using
> > multiproject next weekend (or earlier if everyone agrees - Simon, =
please
> > speak up).
>=20
> Fine by me. Don't worry about causing any problems for code I've got
> outstanding; I can deal with any problems that turn up.
>=20
> > >On a positive note, I'd really like to try using Clirr on my =
project at
> > >work. I've convinced other people that we should try it. As we're =
using
> > >Maven, I'd like to have a Maven plugin working quickly.
>=20
> I've been thinking it's about time for a 0.4 release. If you're
> interested in getting others to use clirr then it might be a good idea
> to get this new release out the door.
>=20
> > >
> > >>I suggest we meet on IRC right now or (if you
> > >>want to give Simon a chance to participate) Sunday morning, 9:30 =
AM
> CEST.
>=20
> I don't think that it's necessary to get me involved. You guys just go
> ahead.
>=20

Cool. Thanks Simon.

-Vincent