No. I have no idea why the caller plugin was added here without it being used everywhere, it makes it inconsistent.
Can you file a bug against the WAR plugin? This is a minor issue as java:compile should do little second time around. - Brett > -----Original Message----- > From: Sri Sankaran [mailto:[EMAIL PROTECTED] > Sent: Friday, 2 April 2004 5:54 AM > To: Maven Users List > Subject: war plugin invokes java:compile twice > > > Using: Maven 1.0 rc2 > > Problem: Invoking the "maven war" results in java:compile > being executed twice. > > Tracing the logic of the goal "war" in the war plugin, you > will find a call to "war:init". In "war:init" are the > following lines: > > <j:if test="${sourcesPresent == 'true'}"> > <caller:call goalInterface="compile-java"/> > <attainGoal name="test:test"/> > </j:if> > The caller plug-in invokes java:compile as instructed. That > is the first invocation of this goal. > > The call to "test:test" can then be traced to have > "java:compile" as a prerequisite. That is the second invocation. > > Any circumstance where this is necessary? > > Sri >
