I'm using Maven 3.0.3 and FlexMojos 4.1-beta. On Dec 7, 2:40 am, Marvin Froeder <[email protected]> wrote: > What is maven and FM versions involved? > > On Dec 6, 8:12 pm, PeeAeMKay <[email protected]> wrote: > > > > > > > > > Well, the current build order as executed by maven *is* first the > > three modules, and then the parent pom. > > But on the other hand, the three modules compile just fine, even > > though they reference the parent pom. > > > It seems it only falls apart in the asdoc goal of the parent pom > > project. > > > What can I do to make sure it behaves correctly? > > Maybe I'm missing something obvious, but I'm not sure what to look > > for. > > Are the goals maybe executed in the wrong order? > > > On 6 Dez., 22:00, Marvin Froeder <[email protected]> wrote: > > > > Something is wrong on your project... parent pom must be installed > > > before modules (since modules do depend, due to inherit, on parent > > > pom) > > > > VELO > > > > On Dec 6, 6:01 pm, PeeAeMKay <[email protected]> wrote: > > > > > Okay, maybe I can shed some more light on the whole issue: > > > > > I have looked at the debug output with the -X parameter and have found > > > > the following: > > > > > For each module, the <aggregate> parameter is correctly set to true in > > > > the configuration step. > > > > Then, the asdoc step is skipped as expected. > > > > > For the parent project, the <aggregate> parameter is suddenly set to $ > > > > {flex.asdoc.aggregate} instead of true. > > > > Since this property is not set explicitly, it defaults to false. > > > > > Because of this, the getSourcePath() function in the AsdocMojo class > > > > will look for the parent folders' source folder instead of collecting > > > > the source paths of the modules. > > > > > If I explicitly set the property to true with - > > > > Dflex.asdoc.aggregate=true, the behaviour will change. > > > > Then, flexmojos will start looking for "resolution tracking files" for > > > > the modules. > > > > However, it will fail after the first module, with a "Non-resolvable > > > > parent POM" error. > > > > > Of course, it can't find the parent POM, since it has not been > > > > deployed yet, since I can't get the build to work ;-) > > > > > Is this maybe a separate issue? Is there any way around this? > > > > Thanks for the quick answer! > > > > > On Dec 6, 8:45 pm, Marvin Froeder <[email protected]> wrote: > > > > > > > Maybe I misunderstand the mechanic? How do I get flexmojos to > > > > > > actually > > > > > > aggregate the documentations? Is there some working example I can > > > > > > take > > > > > > a look at? > > > > > > Now, seems you understood it correctly. Unless there is something > > > > > else, you hit a bug. > > > > > > VELO
-- 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/
