Go for it. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
Ralph Apel <[EMAIL PROTECTED]> wrote on 19/09/2003 04:38:30 PM: > Hi Dion, > > I think, I should stop testing and extending right now and send a "New > Feature" with attached jar to JIRA. > I would be very glad if you could have a special look at it, because I'm > new in here. > Most of all, an example set seems to be urgently needed. I'll do some of > this in the coming days. > > Regards > Ralph > > On Tue, 2003-09-16 at 08:13, [EMAIL PROTECTED] wrote: > > Sounds great. > > > > How can I help??? > > -- > > dIon Gillard, Multitask Consulting > > Blog: http://blogs.codehaus.org/people/dion/ > > > > > > Ralph Apel <[EMAIL PROTECTED]> wrote on 16/09/2003 03:46:08 PM: > > > > > Date: Thu, 28 Aug 2003 12:31:06 +0300 > > > From: Diomidis Spinellis <[EMAIL PROTECTED]> > > > Organization: Athens University of Ecomomics and Business > > > To: Ralph Apel <[EMAIL PROTECTED]> > > > Subject: Re: UmlGraph as a Maven Plugin ? > > > > > > Ralph Apel wrote: > > > > recently I suggested to use your UmlGraph Doclet within the new Apache > > > > Geronimo J2EE Project and I have been told to organize it as a Maven > > > > plugin. > > > Nice to hear that. > > > > > > > 1) Leaving the Doclet.jar as an external dependency and defining a > > bare > > > > bone plugin, without any Java code included. Within the Maven context, > > > > this would mean a large number auf repreated snapshot downloads from > > > > your site. > > > I do not think this is a problem if we are talking about a download for > > > every installation. On the other hand, a download every time someone > > > *uses* the plugin would be a problem, if it proves popular. > > > > > > > 2) Including the doclet as such within the plugin's jar file. In this > > > > case, the plugin and the doclet would be released as part of the Maven > > > > release. In this case, at least 2 issues arise > > > > a) Your code would need to be adapted to a org.apache.maven package > > > > hierarchy > > > I have no problem with that. Currently there is no package declaration > > > (I know, this is bad practice), so org.apache.maven is as good as any. > > > > > > > b) Some kind of copyright compatibility would need to be achieved. > > > The license I am using is BSD, which I think is compatible with > > > apache's I am sure we can work this out. > > > > > > Whatever we do, the two important issues for me are > > > > > > 1) code divergance: I would really like to maintain one code base > > > 2) time: sadly I do not have enough time to get deeply involved into the > > > plugin development (e.g. following mailing list traffic or committing > > > many changes via CVS) > > > > > > MfG, > > > > > > Diomidis > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
