That was quick. ;) Thanks a lot for your help. mvn install in deed solves my problem. But what I don't understand is that the mvn package task runs without problems. This indicates that the compile task could resolve the dependent artifacts without being deployed to local repo.
Cheers Tobias nhoj_p wrote: > >>mvn install > should solve your issue. > > package creates the artifact within the projects target directory, but > when > working on a multi module project you need to do install so it uploads the > artifacts into you local repository so they are avaliable to the rest of > the > modules. > > I hope that helps, > John > > On 10/05/07, Tobias Reese <[EMAIL PROTECTED]> wrote: >> >> Hi @All, >> >> I have a Multi Module Project as follows: >> >> main >> -> utils >> -> ejb (depends on utils) >> -> web (depends on ejb) >> -> ear (depends on utils, ejb, web) >> >> I can do "mvn package", which succesfully builds my artifacts. However, >> if i do "mvn javadoc:javadoc" the ejb project tries to download the >> utils package from the online repo. >> >> Dependency in ejb Project looks as follows: >> <dependencies> >> <dependency> >> <groupId>mypackage</groupId> >> <artifactId>utils</artifactId> >> <type>jar</type> >> <version>0.0.1</version> >> <scope></scope> >> </dependency> >> </dependencies> >> >> Any clues? I spent a whole day on it and the only thing which is left is >> to deploy the utils project to my local repo, which I really don't like. >> >> Cheers Tobias >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/Multi-Module-Project---Problems-Generating-Javadoc-tf3720774s177.html#a10410810 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
