search

qickrooms / flex-mojos

Automatically exported from code.google.com/p/flex-mojos
0 stars 0 forks source link

Manifest file issue #100

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm trying to compile a simple flex library. It has two independent
classes: HelloWorld1.as and HelloWorld2.as

I've created the following manifest file:
<componentPackage>
    <component 
        id="HelloWorld1" 
        class="HelloWorld1" />
</componentPackage>

If I compile the library using a simple pom like this:
<project>
       <modelVersion>4.0.0</modelVersion>
    <parent>
        <groupId>my.example</groupId>
        <artifactId>flex-super-pom</artifactId>
        <version>2.0M5</version>
    </parent>
    <groupId>info.rvin.itest</groupId>
    <artifactId>simple-flex-library</artifactId>
    <version>1.0-SNAPSHOT</version>
    <name>Simple Flex Library</name>
    <packaging>swc</packaging>
</project>

The two classes are compiled into the library. However, if I include a
reference to the above manifest in this pom.xml, using <namespaces> &
<includeNamespaces> in the plugin's <configuration> tag, only HelloWorld1
class is compiled into the library.

Is this behaviour correct?

I haven't included HelloWorld2 in the manifest file because I don't want it
to be used as an MXML tag, but I want it to be in the library because you
should be able to use HelloWorld2 in ActionScript code by importing the class.

I've attached the exmaple project.

Thanks for your time and congratulations for this amazing plug-in!

Original issue reported on code.google.com by joser...@gmail.com on 3 Sep 2008 at 2:22

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi,

for questions about how to use flex-mojos or how it work, use google group and 
I will 
answer you there.
http://groups.google.com/group/flex-mojos

VELO

Original comment by velo...@gmail.com on 3 Sep 2008 at 3:05