Hi Stefan,
the "build-script" job doesn't copy resources, try the appropriately
named "build-resources" instead:
"build-cms" :
{
"extend" : ["build-resources"],
"copy-resources" :
{
"target" : "../../script/qooxdoo/resource/"
}
}
Regards,
Daniel
Stefan Andersson schrieb:
> I have changed the traditional build script to this because I need a
> different resource uri in the ready built package:
>
> "build-cms" :
> {
> "extend" : ["build-script"],
>
> "compile-options" : {
> "uris" : {
> "resource" : "../../script/qooxdoo/resource/"
> }
> }
> },
>
> I do extend the traditional build-script, but the resources of the
> contributed packages are NOT copied into build/resource where they
> should go.
>
> If I run
>
> ../generate.py build
>
> it works!
>
> What is wrong here? For me it seems natural that the resources of the
> contribution packages should be copied.
>
> Stefan
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
