RE: required MetaClass attributes to be a Component

Thanks for the information Peter and Mauro.

Okay, I used the MetaClass ant task to generate the tags with
spice-metaclass-20031005.002435.jar. It generated a bunch of .binary files
that I included in my sar where I would normally include the .xinfo.

Unfortunately, I got the same error.

Right now, I cannot use the maven-sar plug-in so I would like to make the
ant task work on machine. Are .binary files normal instead of .xinfo?

I could not find any difference in the .xinfo information on the loom web
site in comparaison with the phoenix .xinfo information. It sounds masochist
but as I have already coded my .xinfo by hand for phoenix, I could just
modify them by hand to fit the .xinfo loom version if I can get the new
specs.

I include an example of my pheonix tags and an exemple of the ant task I
used.

Lastly, some of my components have both avalon and phoenix tags (I reused
some components made for fortress), will this cause a problem with the
MetaClass ant task?

I am quite sorry if this information is already available on the web site
and I missed it. If so, just point me to the right place and I'll manage on
my own 8)

Thank you very much,
Jean-Francois Heon

Pheonix tags:
 * @phoenix:block
 * @phoenix:service
name="com.gemplus.tracker.phonetracker.PhoneTrackerService"
 * @phoenix:dependency name="com.gemplus.gsa.blocks.network.NetworkProvider"
 * @phoenix:dependency name="com.gemplus.gsa.components.audit.AuditService"

build.xml:
    <target name="metagenerate">
        <taskdef name="metaclassGen"

classname="org.realityforge.metaclass.tools.tasks.GenerateClassDescriptorsTa
sk">
            <classpath refid="tools.class.path"/>
        </taskdef>

        <metaclassGen destDir="${build.classes}">
            <fileset dir="${java.dir}"/>
        </metaclassGen>
    </target>