Hi

Here is the bug that i fill, feel free to update it. There is surely
some type mistake.
http://bugzilla.qooxdoo.org/show_bug.cgi?id=4764

Regards

2011/3/11 Florin Jurcovici <[email protected]>:
> Hi.
>
> We do the maven integration by adding a specific profile, always
> active, in maven's settings.xml:
>
>    <profile>
>        <id>qooxdoo-integration</id>
>        <activation>
>            <activeByDefault>true</activeByDefault>
>        </activation>
>        <properties>
>            <qooxdoo.path>.../qooxdoo-<version>-sdk</qooxdoo.path>
>        </properties>
>    </profile>
>
> and then referring the path in an ant task run using the maven ant
> plugin which we use to run the generator:
>
>    <plugin>
>        <artifactId>maven-antrun-plugin</artifactId>
>        <executions>
>            <execution>
>                <phase>generate-resources</phase>
>                <configuration>
>                    <tasks>
>                        <exec executable=".../python.exe">
>                            <arg value="generate.py" />
>                            <arg value="-m" />
>                            <arg value="QOOXDOO_PATH:${qooxdoo.path}" />
>                            <arg value="build" />
>                        </exec>
>                    </tasks>
>                </configuration>
>                <goals>
>                    <goal>run</goal>
>                </goals>
>            </execution>
>        </executions>
>    </plugin>
>
> It's definitely not an ideal way to integrate the build - the maven
> build doesn't fail if the qooxdoo build fails, so you have to keep an
> eye on the build output, for one. Second, there's no incremental build
> step here - qooxdoo builds every time, even if no Javascript files
> were changed - which is something you definitely want to avoid when
> just running Java unit tests one by one in the debugger. We intend to
> clean up the project at some time in future, but right now we can't
> afford the time to do so. If we come up with a better integration
> solution, I might post it on the mailing list, provided I don't forget
> and we do get the time to do this (we developers definitely feel the
> need to do this, only we don't set priorities).
>
> br,
>
> flj
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>



-- 
Benjamin Dreux
Analyste-Programmeur
Chaire de logiciel libre-Finance Social et solidaire
UQAM
Montréal

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to