This sounds like a good solution to me. It would solve our "two phase build" problem very nicely. If nobody else steps up, I might make a start on this, but unfortunately I can't make any commitments :(
Tom > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 16 June 2000 01:47 > To: [EMAIL PROTECTED] > Subject: RE: [RFE] Richer Task Specification > > > > > I've thought about this a bit more, and was wondering what > people think > about the following idea. > > How about a new task which subclasses off of javac. Its init > method calls > super.init(), then super.execute(), then loads and generated > class files > and defines them as new tasks? > > Nested taskdef elements, with identical syntax to the current > taskdef task, > could be used to generate the necessary <include> statements > on the javac > and then to define the mapping between classname and task name. Users > could obviously add their own <include> statements if necessary. > > - Sam Ruby > >
