Re: [GUMP@brutus]: Project mx4j-tools-from-packaged-jetty (in module mx4j) failed

On Wed, 16 Feb 2005, Simone Bordet <[email protected]> wrote:

>      [rmic] 295 errors

> BUILD FAILED
> /home/gump/workspaces2/public/workspace/mx4j/build/build.xml:318: Rmic failed; see the compiler error output for details.

Here is what happens in Gump:

Gump runs the release target, which means the property releasing gets
set.

      <rmic base="${tools.classes.dir}" classpathref="classpath" debug="yes" stubversion="1.2">
         <include name="mx4j/tools/adaptor/rmi/RMIAdaptor.*" unless="releasing"/>
         <include name="mx4j/tools/connector/rmi/RemoteNotificationListenerImpl.*" unless="releasing"/>
         <include name="mx4j/tools/connector/rmi/RemoteNotificationFilterImpl.*" unless="releasing"/>
      </rmic>

gets run and none of the <include>s applies.  This in turn leads to
<rmic> using the default, which is includes="**".  The same would
happen with the next <rmic> task.

I know this behaviour of Ant is non-intuitive, but it is far (about
four and a half years) too late to fix it.

There are a couple of solutions to this:

One would be to farm the rmic tasks out into a separate target that
has an unless="releasing" attribute on it.  This means you'd have to
split the compile.tools target into three.

The other one involves setting the verify attribute on the <rmic>
tasks to true.  This makes Ant look into each class and only pass
those to the rmic compiler that are really Remote classes.  The
drawback here is that loading and checking all classes may cost time.

Cheers

        Stefan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click