At this point I'm inclined to think we should commit these changes to our Ant task. While I'm not entirely sure about the way it will be used (perhaps we can find some other options for dealing with this use scenario) the exportRefs feature is useful and could potentially clean up some of the internal workings of maven, and facilitates the use of only parts of maven from and existing build.
So here is my (shaky) +1. -- jt On Fri, 2002-05-24 at 09:37, James Strachan wrote: > It works, but, its completely the wrong way around. It means that maven's > compile task calls back the projects' build to run the hello world example, > while compiling. Thats just plain wierd :-) > > I want to have a bunch of different targets in the projects build.xml that a > developer can use, whenever they wish (that are independent from the > maven:compile target) to run various example programs, run specific test > cases and so forth. Each of these targets in the projects build.xml will > want to reuse the classpath that Maven creates. The callback approach above > only lets me have 1 target that Maven calls when I compile. > > So in other words I don't want a compile callback. I just want maven/ant to > output the classpath it uses when its compiled the code. The patch I sent > does exactly this. The callback approach, while it works for 1 target only, > isn't really what I want. > > James > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
