>
> 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.
I think it definitely has potential to clean up the internal workings of
maven. I haven't put together a patch yet, but I think I could take the
time if people like the idea.
Instead of having this huge build.init.target file that verifies the POM
anytime another ant file is called, I think the build.init.target should
only deal with outputting the various callback targets for each plugin.
Move the update/verify project stuff to the core build.xml, and then in
each plugin file (and perhaps including each project's build file) could
contain:
<target name="init" unless="maven.is.initialized">
<maven-ant antfile="...core/build.xml" target="init"/>
<!-- exportRefs and exportAll is defaulted to true in maven-ant,
so now everyone has access to these properties -->
</target>
The init target in the build.xml would do all of the routine parsing the
project.xml, making sure everything is up-to-date, then sets the
maven.is.initialized property so that it never needs to happen again.
I maybe misunderstanding the way maven currently works, but it was my
impression that this happens in every update/verify process plugin file.
There is some comment about with an unless="pomLoaded" which looks to be
the functionality I'd like, but says it can't be done until Ant 1.5. I'm
not quite sure how forwarding references relates to it, but pomLoaded is
never set regardless.
- Stephen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
