|
|
|
Re: Including another projects jars [message #492539 is a reply to message #492482] |
Tue, 20 October 2009 16:49 |
Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
"Tom Eugelink" <tbee@tbee.org> wrote in message
news:hbkjtj$sqb$1@build.eclipse.org...
> Brian de Alwis wrote on Tue, 20 October 2009 10:55
> > Project Properties -> Java Build Path -> Order & Export?
> > Brian.
>
>
> With that I can determine the sequence in which the jars and projects are
placed on the classpath, not prevent indirect jars.
>
> It is not that I do not know how to configure it correctly, it is that too
often I find Eclipse suddenly picks a wrong JAR and I waste a lot of time
figuring it out. (Today it was an old version of Eclipselink in some obscure
util project.)
>
> As said; including a project is IMHO like including that project's
deviverable; one single jar.
Order and Export is used to set which jars are seen by dependent projects.
If the jar is checked, it is exported and dependent projects will see it.
If it is unchecked, it is not exported and it won't be seen by dependent
projects.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02640 seconds