Re: [Clirr-devel] maven plugin

[Simon K. <si...@ec...>]

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 direc=
tory
> >>>structure in order to support integration modules such as Ant, Eclip=
se
> >>>plugin, Maven plugin, Cli, etc. I've even spent time showing what it
> >
[stuff removed]

I'm also keen to see a Maven plugin, and agree Clirr is the best place
to host it.

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 :-).

Still, if (for some reason) moving the cli "main" class is absolutely
necessary to implement a Maven plugin, I could live with it.

Apart from that, I'm all for integrating the maven code as soon as
possible.


> The simplest thing is to create a module 'core' and simply move=20
> everything we have now (including cli and ant) into that module. You ca=
n=20
> then start committing the Maven plugin into a different module, so we=20
> end up with two multiproject modules, 'core' and 'maven'.

That would make the start command for the cli into this?
  java net.sf.clirr.core.cli.Clirr=20

>=20
> I'm not convinced anyway that it makes sense to have cli and ant in=20
> different packages: the jar would basically consist of one class file..=
.=20
> If someone disagrees we can do further split-up later.

I tend to agree.

>=20
> Simon, do you have uncommitted changes on your hard drive?

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!
> >>   =20
> >>
> >
> >Cool. I also think so.

Me too. If only the UN could agree so easily :-)


> I can understand your frustration, and I think we should start using=20
> multiproject next weekend (or earlier if everyone agrees - Simon, pleas=
e=20
> speak up).

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.

> >On a positive note, I'd really like to try using Clirr on my project a=
t
> >work. I've convinced other people that we should try it. As we're usin=
g
> >Maven, I'd like to have a Maven plugin working quickly.

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.

> >
> >>I suggest we meet on IRC right now or (if you
> >>want to give Simon a chance to participate) Sunday morning, 9:30 AM C=
EST.

I don't think that it's necessary to get me involved. You guys just go
ahead.


Cheers,

Simon