The jar for all modules is built and "should" work. I was stuck at the samples build the last time I take a look. I'll spend some time tonight to make the sample build work. Then it will remains correct cleanup and distribution build. I would say that saturday, everything should be ok. Vincent
----- Original Message ----- From: "Ara Abrahamian" <[EMAIL PROTECTED]> To: "'Vincent Harcq'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, May 01, 2002 10:12 PM Subject: RE: [Xdoclet-devel] RE: [Xdoclet-user] Xdoclet cvs issues Btw, Vincent what's the status of build files for modules? Usable? Done? Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Vincent Harcq > Sent: Monday, April 29, 2002 10:50 PM > To: Aslak Helles�y; Hani Suleiman > Cc: [EMAIL PROTECTED] > Subject: Re: [Xdoclet-devel] RE: [Xdoclet-user] Xdoclet cvs issues > > Yes! > This idea should also become a good practice for other complex tasks that > use new Erik's feature. > > Maybe a bit more ant compliant: > > <module> > <fileset dir="flat" includes="*.*" excludes=> > or > <fileset> > <include name ="xdoclet-*.jar" /> > <exclude name =... /> > </fileset> > </module> > > So we could also load from directories with classes in them. > Is this possible? > > Vincent > > ----- Original Message ----- > From: "Aslak Helles�y" <[EMAIL PROTECTED]> > To: "Hani Suleiman" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, April 29, 2002 2:38 PM > Subject: [Xdoclet-devel] RE: [Xdoclet-user] Xdoclet cvs issues > > > > First, Bootstrapper is gone (on the MODULE_REFACTROING_BRANCH). > > I like your idea. What if we pass in an array of File objects to > > ModuleFinder.findModules(File[] moduleDirs)? > > This would default to the location of ant.jar, but can be overridden in > > build.xml with a dirset (new Ant feature I think). > > > > You would get something like this: > > > > <ejbdoclet ...> > > <!-- optional if module jars are in a different place than ant.jar -- > > > > <moduledirs> > > <include name="${standard.modules.dir}"/> > > <include name="${myown.modules.dir}"/> > > </moduledirs> > > > > ... > > > > <ejbdoclet> > > > > What do you others think? > > > > /Aslak > > > > > -----Original Message----- > > > From: www-data [mailto:[EMAIL PROTECTED]]On Behalf Of Hani > Suleiman > > > Sent: 29. april 2002 14:22 > > > To: Aslak Hellesoy > > > Cc: [EMAIL PROTECTED] > > > Subject: RE: [Xdoclet-user] Xdoclet cvs issues > > > > > > > > > I'll try and find the time to sort out the ant issue, by talking to > > > them/submitting a patch or whatever. However, I still think the way > that > > > xdoclet has been changed is not an ideal design. > > > > > > Why not, for example, allow for a plugin directory set to be > > > supplied to the > > > bootstrap task? Right now it just assumes that plugins will be > > > all jar files > > > alongside xdoclet.jar, which while covering the most common > > > usage, does not > > > cover the case where your module jars might be in different > > > places (eg, say > > > you're testing a new jar, that is in another build tree, and you > > > want to link > > > that in), just allowing for a 'module-dir' attribute would > > > achieve the same > > > effect I think, as well as bypassing the ant classloader bug. > > > > > > Quoting Aslak Hellesoy <[EMAIL PROTECTED]>: > > > > > > > > > _______________________________________________ > > 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 _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
