| exporting existing jars [message #201870] |
Thu, 11 October 2007 10:24  |
 Zohar Amir
Messages: 419
Registered: July 2009 |
Senior Member |
|
|
Hello,
I have a web project which depends on a utility java project. The utility
project exports a jar file that it uses. It happened to be that the web
project also uses (and includes) the same exported jar. The utility project
is also used by another web project, which does not include the jar.
What should I do?
Thanks,
Zohar.
|
|
|
|
| Re: exporting existing jars [message #201895 is a reply to message #201879] |
Thu, 11 October 2007 13:15  |
Larry Isaacs
Messages: 1261
Registered: July 2009 |
Senior Member |
|
|
I think it is up to you to choose how to achieve consistency when your
current use case creates conflicts. In the context of your use case,
you would decide if the utility project does or doesn't publish/export
and the web projects would need to adapt to that decision. It may be
normal that your solution can't get rid of all the "Classpath entry..."
problem items. Worst case, you can use the J2EE Module Dependencies to
directly add jar dependencies that can't be handled any other way.
Cheers,
Larry
zohar wrote:
> Same question when more than one utility classes export the same jar.
>
> "zohar" <david_fire4@hotmail.com> wrote in message
> news:felbll$6mr$1@build.eclipse.org...
>> Hello,
>> I have a web project which depends on a utility java project. The
>> utility project exports a jar file that it uses. It happened to be
>> that the web project also uses (and includes) the same exported jar.
>> The utility project is also used by another web project, which does
>> not include the jar.
>> What should I do?
>> Thanks,
>> Zohar.
>
|
|
|
Powered by
FUDForum. Page generated in 0.11528 seconds
] 
Search
Help
Register
Login
Home
