Hm, I have done a checkout of the git repository, but I'm already running into problems with resolving dependencies when making a standard Maven build of the project. Unfortunately, I don't have that much time at my hands to make this run and fix the bugs, since this is not for a private project, but a project for my employer.
I would create a workaround for the documentation generation with Ant scripts. I will set up a couple of tickets, though, so that all this won't get lost. On Dec 7, 12:43 pm, Marvin Froeder <[email protected]> wrote: > I suggest you grab sources and start debugging =D > > But I still do not understand how the parent pom can be built after > it's children... > > On Dec 7, 9:21 am, PeeAeMKay <[email protected]> wrote: > > > > > > > > > Okay, I've set the classifier tag in the modules POM files as well, > > but it has no effect. > > When aggregating the documentation of the module components, asdoc > > seems to simply ignore the classifiers when looking up the components. > > > On Dec 7, 11:56 am, Marvin Froeder <[email protected]> wrote: > > > > Parent pom has no > > > classifier....http://maven.apache.org/pom.html#Inheritance > > > (o.0) > > > > On Dec 7, 8:31 am, PeeAeMKay <[email protected]> wrote: > > > > > Okay, another hint I've just stumbled upon: > > > > I'm using classifiers in order to build both the parent POM and the > > > > modules. -- 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/
