On Sat, 2003-03-29 at 03:50, Jeffrey D. Brekke wrote:
>
> Right, I understand that. I was wondering if you had a project
> dependency and a jar dependency to the same project defined if eclipse
> would use the project classes before going to the jar. It was a real
> quick and ugly way of maybe making it work.
I guess you could make that work if the classpath ordering was correct,
but you might run into problems if files from the jar version showed
through - for example, classes you've deleted recently but which are
still in the jar file.
> There was some talk awhile back, around the time jar override
> functionality was added to maven, that we could depend on the classes
> of other projects, not just the artifacts. I don't think anything but
> talking about happened though.
I wasn't around when that was discussed (so excuse me if I'm rehashing
old stuff), but had thought about that in the context of my quick hack.
The problem (I think) is that maven would need a fair amount of extra
infrastructure to track the locations of projects' source trees in the
local file system in order to resolve dependencies. It's not that
unreasonable - each time you build a project it would dump some
information about the compiled classes directory into a
$MAVEN_HOME/repository directory instead of installing a jar file. But I
wasn't about to start hacking something like that when I don't know
whether there's an existing design for how people expect this to work in
the future.
My hack depends on Eclipse tying a project name to a classes directory,
which takes the information out of maven's hands. On the other hand, it
doesn't require maven to think about more than one project at once.
> > 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?
>
> The jar dependencies are there now in the reactor. Maybe we need pom
> dependencies between reactor'd projects.
Does this require each reactor'd build to install a copy of the jar into
the repository? i.e. if A depends on B, would the reactor need to be
told to do
compile B
build B.jar
install B.jar in maven repo
compile A with B.jar from maven repo on classpath
build A.jar
or can it manage
compile B
compile A with B/target/classes on classpath
? Or is that what you're suggesting would need pom dependencies?
-Mark.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
