Giacomo Pati wrote: > > > [EMAIL PROTECTED] wrote: >> Author: lgawron >> Date: Thu Nov 23 01:08:16 2006 >> New Revision: 478517 > >> URL: http://svn.apache.org/viewvc?view=rev&rev=478517 >> Log: >> invalid build order > >> Modified: >> cocoon/trunk/blocks/cocoon-fop/pom.xml > >> Modified: cocoon/trunk/blocks/cocoon-fop/pom.xml >> URL: >> http://svn.apache.org/viewvc/cocoon/trunk/blocks/cocoon-fop/pom.xml?view=diff&rev=478517&r1=478516&r2=478517 >> ============================================================================== >> --- cocoon/trunk/blocks/cocoon-fop/pom.xml (original) >> +++ cocoon/trunk/blocks/cocoon-fop/pom.xml Thu Nov 23 01:08:16 2006 >> @@ -35,8 +35,8 @@ >> <name>FOP Block [modules]</name> >> <description/> >> <modules> >> - <module>cocoon-fop-sample</module> >> <module>cocoon-fop-impl</module> >> + <module>cocoon-fop-sample</module> >> <module>cocoon-fop-ng-sample</module> >> <module>cocoon-fop-ng-impl</module> >> </modules> > > Is this really important? Shouldn't Maven build the order from the > dependencies a module has?
Yes it is. The modules are built in the order provided. So in the case I corrected cocoon-fop-sample will get built using old version of cocoon-fop-impl (from your local repository). If you have no such artifact in repository alread and error raises. > Doesn't the cocoon-fop-sample module define a dependency on the > cocoon-fop-impl module? If you use maven embedder (for example by using m2eclipse plugin) you will notice that previous configuration will cause cocoon-fop-impl.jar put on the classpath along with cocoon-fop-impl/src/main/java|resources folder. I've run through this kind of problems several months ago in my private project. Maybe current maven version is handles module building order automatically regardles of the actual order in xml file (I doubt it). -- Leszek Gawron CTO at MobileBox Ltd.
