> A wise old hermit known only as =?us-ascii?Q?Aslak_Hellesoy?=
> <[EMAIL PROTECTED]> once said:
>
> > I still think we should add xdoclet/lib/xjavadoc.jar for simplicity.
> > People
> > shouldn't need to download and build xjavadoc in order to use XDoclet
> > (I'm talking about all the XDoclet CVS users here). Thoughts?
>
> I agree; we should include xjavadoc.jar in xdoclet/lib, copied/updated
> there during xjavadoc's build but versioned (i.e. update the CVS copy)
> when we do a release of xjavadoc. Since we currently have xdoclet and
> xdocletgui (and potentially other 3rd party programs) independently
> relying on xjavadoc, we should manage its versions/releases better (which
> means more work for me, dammit :-) ) As for how we then deal with
> changes/fixes to xdoclet that also require changes to xjavadoc, I suggest
> they should use a branch, and merge it back on the following release of
> xjavadoc containing it.
another option is
xdoclet-all/xjavadoc
/xdoclet
/xdoclet-gui
stolen straight from the jboss setup...
cheers
dim
>
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Ara
> > > Abrahamian
> > > Sent: 22. mars 2002 13:45
> > > To: 'Vincent Harcq'; [EMAIL PROTECTED]
> > > Subject: RE: [Xdoclet-devel] refactoring branch
> > >
> > >
> > > Imho it's better to copy xjavadoc.jar to xdoclet/lib dir when building
> > > xjavadoc. It's boring to upload a jar file each time. Assume xdoclet
> > > and xjavadoc are in the same folder/level.
> > >
> > > Ara.
>
> This would still be the case - you wouldn't upload a new xjavadoc.jar
> every time, I'd do it on each xjavadoc release. The xjavadoc build.xml
> would indeed assume the same folder level, and copy it over into
> xdoclet/lib after building it, so you can still develop xdoclet against
> the current cvs xjavadoc. The only restriction is that if your changes
> require the xjavadoc changes, and don't work against the current release
> xjavadoc.jar, it should use a branch so as not to break the GUMP builds.
>
> However, we should only worry about any of this once it's stable and
> there's no more integration changes.
>
> Like I said, just my opinion (but similar to what we do at work where we
> have framework sources and application sources maintained separately by
> different development teams).
>
>
> Andrew.
>
> > > > -----Original Message-----
> > > > From: Vincent Harcq [mailto:[EMAIL PROTECTED]]
> > > > Sent: Friday, March 22, 2002 10:39 AM
> > > > To: 'Aslak Hellesoy'; 'Ara Abrahamian'; xdoclet-
> > > > [EMAIL PROTECTED]
> > > > Subject: RE: [Xdoclet-devel] refactoring branch
> > > >
> > > > > -But I know one thing: If xdoclet.jar is regenerated, xdoclet
> > > > > doesn't regenerate sources as it used to do. We (you) should
> > > > > check xjavadoc.jar age too.
> > > >
> > > > Yep, I'll do that.
> > > > BTW we should cvs add xjavadoc.jar to xdoclet/lib no ?
> > > > I am also thinking of adding Version info in the Manifest of the
> > > > jars
> > > > (xdoclet and xjavadoc) just to know with wich version you work.
> > > > With a ant filter or something...
>
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
