Odd...  I do recall on some bug, but I thought it was fixed....

On Tue, Jul 5, 2011 at 4:01 PM, Carsten Schlipf
<[email protected]>wrote:

> Hi Velo,
>
> no, that did not work for me using Flex Mojos 4-beta 7 - always got
> encoding errors. But that was also my assumption.In Flex Mojos 3.8
> there was a source-path entry for the resources directory, which is no
> longer the case. As soon as I added the resources folder as additional
> source directory it started to work again after the upgrade.
>
> Carsten
>
> On Jul 5, 8:52 pm, Marvin Froeder <[email protected]> wrote:
> > If you are only accessing resources (png, wav, gif, embed stuff) on
> > resources dir you don't need to add it as souce folder.
> >
> > VELO
> >
> > On Tue, Jul 5, 2011 at 3:49 PM, Carsten Schlipf
> > <[email protected]>wrote:
> >
> >
> >
> >
> >
> >
> >
> > > Exactly. I just place my images into src/main/resources/images/
> > > myimage.png and embedd it using
> > >    [Embed(source="/images/myimage.png")]
> > >    public static const MyImage:Class;
> > > Just add the plugin configuration like posted below and make sure,
> > > that it is not just in the pluginManagement section, but also active.
> >
> > > On Jul 5, 9:54 am, Simon Morvan <[email protected]> wrote:
> > > > So you confirm it works now ?
> >
> > > > Here, we're use to point embedded source files by that kind of pathes
> :
> > > > ../../../../../resources/path/to/resource
> >
> > > > You confirm that by adding src/main/resource as a source folder, a
> > > > foo.bar.Class can embedd a file located at
> > > > src/main/resources/foo/bar/<filename> ?
> >
> > > > Le 05/07/2011 09:45, Carsten Schlipf a écrit :
> >
> > > > > PEBKAC -
> > >http://www.thinkgeek.com/tshirts-apparel/unisex/itdepartment/6692/
> >
> > > > > I've added this plugin section to the pluginManagement section by
> > > > > accident and did not activate it.
> >
> > > > > Sorry!
> >
> > > > > On Jul 5, 8:44 am, Carsten Schlipf<[email protected]>
>  wrote:
> > > > >> As you can see from my posting I've already tried that - maybe not
> > > > >> careful enough. This is what I've did:
> >
> > > > >>          <plugin>
> > > > >>            <groupId>org.codehaus.mojo</groupId>
> > > > >>            <artifactId>build-helper-maven-plugin</artifactId>
> > > > >>            <executions>
> > > > >>              <execution>
> > > > >>                <id>add-flex-resource-source-path</id>
> > > > >>                <phase>generate-sources</phase>
> > > > >>                <goals><goal>add-source</goal></goals>
> > > > >>                <configuration>
> > > > >>                  <sources>
> > > > >>                    <source>src/main/resources</source>
> > > > >>                  </sources>
> > > > >>                </configuration>
> > > > >>              </execution>
> > > > >>            </executions>
> > > > >>          </plugin>
> >
> > > > >> On Jul 4, 11:10 pm, Simon Morvan<[email protected]>  wrote:
> >
> > > > >>> You can solve your issue by (carefully) using the build helper
> plugin
> > > > >>> from CodeHaus :
> >
> > >http://mojo.codehaus.org/build-helper-maven-plugin/add-source-mojo.html
> > > > >>> --
> > > > >>> Simon
> > > > >>> Le 04/07/2011 18:05, Carsten Schlipf a écrit :
> > > > >>>> Hi Velo,
> > > > >>>> I have a follow up question on this old thread:
> > > > >>>> "Missing source paths after switching to use flexmojos
> 4.0-alpha4
> > > from
> > > > >>>> flexmojos 3.6.1"
> >
> > >https://groups.google.com/group/flex-mojos/browse_thread/thread/740e6.
> ..
> > > > >>>> Sorry to have to bother you on this old issue. I've read various
> > > > >>>> threads here and I've read your last comment on
> > > > >>>>https://issues.sonatype.org/browse/FLEXMOJOS-327, where you've
> wrote
> > > > >>>> "So, flexmojos 4 won't allow you to tamper with sourcePaths
> anymore,
> > > > >>>> that does cause problems and it isn't maven way.
> > > > >>>> You need to include the extra sourceRoots to maven. Like you
> would
> > > do
> > > > >>>> to any java project."
> > > > >>>> Well, I understand you one one side, but on the other placing
> > > > >>>> resources like images into the resources folder and embedding
> them
> > > > >>>> form Flex sources using the EMBED directive is a fairly standard
> use
> > > > >>>> case. So quite a lot developers will have to tamper with
> > > sourcePaths.
> > > > >>>> I've tried to add additional source paths using the build-
> > > > >>>> helper=maven-
> > > > >>>> plugin like described here:
> > >http://www.redstream.nl/2009/03/03/adding-extra-source-path-to-your-m.
> ..
> > > > >>>> However in FlexMojos 4.0-beta-3 this has no effect on the
> generated
> > > > >>>> compiler configuration. The directive soure-path still only
> contains
> > > > >>>> the src/main/flex folder. So maybe I am just too stupid to find
> how
> > > to
> > > > >>>> properly add sourceRoots like you've said. So it would be great,
> if
> > > > >>>> you could explain how to do this with Maven 3 properly. I
> believe
> > > that
> > > > >>>> would be of great help also to others and avoid more questions.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "Flex Mojos" group.
> > > To post to this group, send email to [email protected]
> > > To unsubscribe from this group, send email to
> > > [email protected]
> > > For more options, visit this group at
> > >http://groups.google.com/group/flex-mojos
> >
> > >http://flexmojos.sonatype.org/
>
> --
> You received this message because you are subscribed to the Google
> Groups "Flex Mojos" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos
>
> http://flexmojos.sonatype.org/
>

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to