On Tue, Nov 17, 2009 at 12:02, Peter Kawiak <[email protected]> wrote:
> My two cents: if you set M2_REPO for the first time, eclipse sometimes
> won't notice it for previously created projects. In case it's still
> complaining after you introduced the variable, just delete and import
> your project again.
>
Even without experience it here, I believe you! :P Eclipse is sometimes so
crazy..
@All
Sorry for my mistake, M2_HOME really should point to maven installation
directory. But would be more intuitive if the variable used by flex mojos is
M2_REPO. In the java variables, M2_REPO points to ~/.m2/repository, so the
generated library entries doesn't need to be modified (sorry again :( ).
@Darren
I Tried what Logan said now, and things seem better.
There is a weird thing:
The -include-sources in additionalCompilerArguments put an absolute path.
Here in my company we commit the configs to VCS, because everyone uses the
same eclipse customization and it brings some facilities to us. This
absolute path avoid us to do that, so i tried to use the ${DOCUMENTS} to
that (which we already use to server, compile and services config). After do
that, other error:
nothing was specified to be included in the library
The flexbuilder mojo generates a empty include classes tag on
.flexLibProperties. So I had to manually add all the classes again.
I will try to use the flexbuilder integration this way by now.
Even without flexbuilder integration, flex-mojos gives me ability to use
maven release plugin and it enough for me by now. I had only mavenized my
libs, not my web projects. It will be the next step here.
Thanks for all for the help!
--------
BrunoJCM
--
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?hl=en?hl=en
http://blog.flex-mojos.info/
