flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject Re: [FlexJS][Maven] Missing assets in target folder
Date Fri, 04 Nov 2016 09:29:00 GMT
Hi Carlos,

just to be complete with my suggestion. Maven style would be to have sources, which are compiled
in „src/main/flex“ and resources which are simply copied to the output in „src/main/resources“


Am 04.11.16, 10:13 schrieb "carlos.rovira@gmail.com im Auftrag von Carlos Rovira" <carlos.rovira@gmail.com
im Auftrag von carlos.rovira@codeoscopic.com>:

    I think Chris is on the track on this issue.
    As a user, If I have a resource on a folder, is because I want it on final
    output, so I'll expect to be copied, since output folder is what I'll be
    putting on server (and not any source code related resource).
    btw, I think this should be IDE agnostic, and it scares me if we think it
    should depend on that. people should be able to use it from command line,
    so I think this is in the flexjs sdk domain.
    In traditional flex development:
    *  I used a path like this "/assets/image.jpg" and that would work as an
    absolute path.
    * The other way is relative to the resource, without the first slash, and
    you can up and down the hierarchy starting from the source file in which
    you write that code.
    I use a maven style folder structure (so src/main/flex/App.mxml and so on),
    other will use src/App.mxml... we need to support all of this in a easy
    way, since this is basic.
    I think If users start to be kept in this basic things, is what could make
    them to not continue trying flexjs.
    2016-11-04 8:04 GMT+01:00 Christofer Dutz <christofer.dutz@c-ware.de>:
    > Hi Carlos,
    > I’m glad you are having this problem ☺ ... don’t get me wrong, but it
    > points out a problem I noticed when working on cleaning up the
    > MXMLFlexJSPublisher.
    > The problem is that only png, gif, jpg and json resources are copied. This
    > is hard coded and I don’t like that approach. I would prefer something more
    > Maven style in which you have sources and resources.
    > This way everything in the resources could be copied instead of this hack
    > with hard-coded filters. A short fix would be to name your image „jpg“
    > instead of „jpeg“.
    > The second thing is the „relativity to the main class“. It seems all
    > resources are addressed relative to the main class:
    >         File imageSrcDir = new File(configuration.getTargetFile()).
    > getAbsoluteFile().getParentFile();
    > This sort of works as long as the Main class is in the root of the
    > project. This restriction however only seems to apply if you are using
    > Flash Builder. In my IntelliJ and Maven applications I usually put my Main
    > classes in packages.
    > You can have a look at the code I’m talking about in MXMLFlexJSPublisher
    > (Lines 177-201 in my closure-classpath-sources branch or 149-152,407-421 in
    > the develop branch)
    > Chris
    > Am 03.11.16, 23:10 schrieb "carlos.rovira@gmail.com im Auftrag von Carlos
    > Rovira" <carlos.rovira@gmail.com im Auftrag von carlosrovira@apache.org>:
    >     Hi Chris,
    >     I'm trying to test a simple <js:Image> in MDLExample without luck,
    >     something like:
    >     <js:Image url="main/resources/Unknown.jpeg" width="220" height="140"/>
    >     is not working.
    >     I think the problem is maven is not copying the image asset to to
    > target
    >     folder.
    >     I get it working with something like this:
    >     <js:Image url="../../../../src/main/resources/Unknown.jpeg"
    > width="220"
    >     height="140"/>
    >     (reaching it from outside target and from the source project)
    >     Maybe I'm doing something wrong?
    >     --
    >     Carlos Rovira
    >     http://about.me/carlosrovira
    Carlos Rovira
    Director General
    M: +34 607 22 60 05
    Este mensaje se dirige exclusivamente a su destinatario y puede contener
    información privilegiada o confidencial. Si ha recibido este mensaje por
    error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
    proceda a su destrucción.
    De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
    que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
    S.A. La finalidad de dicho tratamiento es facilitar la prestación del
    servicio o información solicitados, teniendo usted derecho de acceso,
    rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
    oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación

View raw message