| Calls to ClasspathHelper in JPA facet install delegate [message #815521] |
Wed, 07 March 2012 14:24  |
Eclipse User |
|
|
|
Hi team, wanted to ask about a problem we're seeing in an adopter product based on WTP 3.3+ (eclipse 3.7+ based). Given that the JPA facet is no longer tied to the utility facet, when standalone JPA projects are created targeted to a runtime, the project's classpath no longer gets updated with the runtime classpath container.
It appears that the JPA facet install delegate does not explicitly call ClasspathHelper.removeClasspathEntries(project, fv) and ClasspathHelper.addClasspathEntries(project, fv) .. beforehand this was being handled in the utility facet.
Is this by design? Should the JPA facet install delegate call the classpath helper or should adopter products implement their own listeners to call the classpath helpers and update the project's classpath for the runtime?
Thanks.
|
|
|
| Re: Calls to ClasspathHelper in JPA facet install delegate [message #815560 is a reply to message #815521] |
Wed, 07 March 2012 15:22  |
| Eclipse User |
|
|
|
I believe this is all intentional. There are many who do not want the entire runtime plastered on to their classpath every time. The library provider for the JPA facet handles adding the proper items to the project classpath. If the user chooses a "runtime" library provider, then the library provider adds only the entries from the runtime that are appropriate for the facet chosen, and it is up to the runtime implementation to know which entries are appropriate for each facet.
We don't have any runtime implementations that do this, so this is somewhat theorycraft, but it's pretty much what I've been told by the library provider framework guys.
|
|
|
Powered by
FUDForum. Page generated in 0.23462 seconds
Home