> FWIW, I've long since stopped using the flexmojos-flex-super-pom, not
> because I've had any problems with it, just at some point I found it
> was unnecessary. I started declaring things as dependencies instead,
> perhaps pushing those up to my own parent-pom where/when possible.
> Lukas, if you are still experimenting, try this approach, that is,
> don't use the flexmojos-flex-super-pom, drag in the flex-framework pom
> dependency and see if the flexmojos behaves differently?
I've confirmed that this works as well, with the super pom as a
dependency, instead of as the parent.
<dependency>
<groupId>org.sonatype.flexmojos</groupId>
<artifactId>flexmojos-flex-super-pom</artifactId>
<version>3.4.2</version>
<type>pom</type>
</dependency>
HOWEVER-- it must be run as "mvn clean install". Using "mvn
flexmojos:generate" will not load the configuration.
This is the main reason I picked up this thread. I feel as if the
documentation is ambiguous as to what should EXACTLY be done.
Following the WIKI and docs to the letter, then running "mvn
flexmojos:generate" would not work. It has been alluded that the
problem is with Maven itself, which may be the case.
However, to save headaches of this group, and of the users who are
trying to get this to work, I'd recommend the WIKI page be clarified.
If you guys don't have a problem with me doing the editing, I'd be
happy to.
--
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/
