On Fri, 2003-03-28 at 19:12, Jeffrey D. Brekke wrote: > This is very interesting. We have 36 projects, all with > interdependencies ( some build, some test, some runtime ) and to have > the reactor/maven maintain the eclipse projects like this would be > cool. Is there a dep heirarchy in eclipse where like a project dep is > used if present before a jar dep? Then we could just put both deps in > the project.
In Eclipse if you have a number of separate projects open in your workspace you can specify dependencies between them, so you can say that project 'foo' depends on project 'bar' in the same workspace. This results in bar being on the classpath when foo is compiled. It also helps to tie together the internal model that Eclipse uses - you can click on a symbol in the foo project and it'll take you to the source in the bar project or show you the javadoc for example. If you were depending on a jar file you'd have to associate a source directory with the jar file to get this to work. What I tend to do is break a system down into modules, each of which is a separate project with (typically) one source tree in each project. I would then use Eclipse's classpath editor to specify for each project which other projects were required. At the moment there doesn't seem to be a way to model this kind of dependency in the maven project model - dependencies are more-or-less assumed to be versioned jar files. I think it would be useful to have a way to model this kind of dependency hierarchy, if only so project files for IDEs work more cleanly. I don't know whether this kind of dependency information would be of use when building multiple projects under reactor - presumably that can work with jar file dependencies? -Mark. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
