[...]
> Yep, but isn't this exactly what the caller plugin does? Again, I do
> agree that it would be better written in java and inside Maven core.
> I've defined a "merge point" as a WKG (Well-Known Goal).
>
I agree.
Just to explain myslef
I tried to explain ( I am sick today :( so it's not going well)
That in goal "war:init":
<goal name="war:init"
description="Initialize the file system and attain any necessary goals">
<ant:available property="webSourcesPresent" type="dir"
file="${maven.war.src}"/>
<j:if test="${sourcesPresent == 'true'}">
<caller:call goalInterface="compile-java"/>
<attainGoal name="test:test"/>
</j:if>
<ant:property name="maven.war.final.name"
value="${pom.artifactId}.war"/>
</goal>
There should be no call to caller plugin
just something like
<j:if test="${sourcesPresent == 'true'}">
<atainGoal name="xxxxx:compile"/> (e.g xxxxx:compile=java:compile)
<attainGoal name="test:test"/>
</j:if>
and it should be up to (just an example - I am not imposing anything) "java"
plugin to handle this call (In place of WKG there will be WKG in Well Know
Plugin).
It's like you are looking up "well know" service (interface) and call it
while with caller plugin it's like you are looking up the name of the
service before calling it.
(I hope that difference is clear)
So as a consequnce (as I see it) war plugin should not depend on "caller
plugin" and we should put inside "java" plugin a logic which binds a call to
"compile"
goal to particual executor.
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
