qickrooms / flex-mojos

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

Wrong path for output file #159

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. set the output filename in configuration section for flex-compiler-mojo

What is the expected output? What do you see instead?
File is placed in base directory instead of "target" directory as it was in
version 2.0M10.

What version of the product are you using? On what operating system?
2.0.1 Windows XP

Please provide any additional information below.
<plugin>
    <groupId>info.flex-mojos</groupId>
    <artifactId>flex-compiler-mojo</artifactId>
    <version>2.0.1</version>
    <extensions>true</extensions>

    <dependencies>
        <dependency>
            <groupId>com.adobe.flex</groupId>
            <artifactId>compiler</artifactId>
            <version>3.2.0.3958</version>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>com.adobe.flex</groupId>
            <artifactId>license</artifactId>
            <version>3.2.0.3958</version>
            <type>jar</type>
        </dependency>
    </dependencies>
    <configuration>
        <sourceFile>sourceFile.mxml</sourceFile>

        <!-- in version 2.0M10 that was ok -->
        <output>outputFile.swf</output> 
        <!-- workaround for version 2.0.1 -->
        <output>${project.build.directory}/outputFile.swf</output>

    </configuration>
</plugin>

Original issue reported on code.google.com by szczepanski.jaroslaw on 16 Jan 2009 at 11:18

GoogleCodeExporter commented 9 years ago
That is the expected behavior.

If you wanna to change just the name of the compiled file, change finalName on 
build
section.

Output is intent to be used when you wanna the compiled file saved in some other
place then target folder. So need to declare ${project.build.directory} if you 
wanna
change the output folder to the original value (which doesn't make much sense).

VELO

Original comment by velo...@gmail.com on 21 Jan 2009 at 7:35