|Re: Exported jars from utility module... [message #196806 is a reply to message #196742]
||Thu, 19 July 2007 21:08
| Larry Isaacs
Registered: July 2009
I'm not sure if having a ".component" file instead of a |
"org.eclipse.wst.common.component" file matters, but what's new in WTP
2.0 is that in your scenario, you should see warnings for the utility
project in the Problems view with respect to the jars its using.
Classpath entry <some.jar> will not be exported or published. Runtime
ClassNotFoundExceptions may result.
If you invoke the Quick Fix for that warning, the ".classpath" file in
the utility project will be modified to flag that the jar should be
included in the dependant web project's WEB-INF/lib when exported or
published. If the jar hasn't been exported in the utility project yet,
the warning doesn't go away but becomes an error until the jar is
exported. Do you see such warnings in your Problems view for the older
and new utility projects?
Nathan Wilhelmi wrote:
> Hi - Still stuck on this, hoping it would be fixed by now. Just upgraded
> to the latest 3.3 and Europa release. JST tools show version 2. We have
> a java project with utility facet enabled, this was created in an
> earlier version so it still uses the .component file. All the jars in
> the utility project are exported on the build path. The utility project
> is listed as J2EE dependency in the Dynamic Web project, however when
> the app is started the jars are not visible from the utility project. Is
> this still a bug or do I need upgrade the utility project somehow? I did
> create new utility project, and it has the attribute
> `project-version="1.5.0"` could this be part of the problem?
Powered by FUDForum
. Page generated in 0.02134 seconds