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/
