Re: war plugin : [maven.caller.call.compile-java] is not defined

[Michal Maczka]

Vincent Massol wrote:

Hi Eric,

No. It's because you seem not to have installed the caller plugin... My
guess is that you have only taken the war plugin from HEAD without
taking it's dependencies. Actually, thinking about it, we should add a
dependency in the war plugin on the caller plugin so that it gets
automatically downloaded.
-Vincent
 

Vincent! 
I really like your idea of Well Know Goals which  is implemented in 
Caller Plugin but I think ... that this plugin should be dropped.

In particular case of java:compile goal - it's java plugin which is 
badly written.

I don't think we need a central point for "wiring" goals.

Existence of caller plugin just shows that  we need to have a well 
defined and *extendable* workflow.

Lets's concentrate on java plugin:
java:compile process can be divided into 3 steps:
 a) generation of java classes (with plugin  xdoclet, jaxb, castor)
 b) compilation with e.g javac/aspectj compiler
 c) applictaion of bytecode ehancers (like kodo, ascpectj )
a)
foreach codeGenerator in codeGenerator do:
  <attainGoal name="${codeGenerator}:generate"/>
end;
b)
java:compile (calls javac:compile or aspectj:compile or 
eclipse-compiler:compile)

c)
foreach byteCodeEnhancer in byteCodeEnhancers do:
  <attainGoal name="$byteCodeEnhancer}:enhace"/>
end;


IMHO the best solution will be to

a) rename  java:compile goal to javac:compile

add java:compile which does what you have tried to do with caller plugin.

regards

Michal



  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]