Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353778 - Jar file refs do not resolve in a non-EE project.
Summary: Jar file refs do not resolve in a non-EE project.
Status: NEW
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Paul Fullbright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 10:40 EDT by Paul Fullbright CLA
Modified: 2013-09-06 16:50 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Fullbright CLA 2011-08-03 10:40:36 EDT 
Create an SE JPA project (no EE module).  There is no way to get a jar file ref to resolve to a jar file within your project.

The resolution mechanism uses the virtual file API, which is added with the module core project nature, which is only added with EE modules.

That said, I'm not even sure *how* an SE project should use jar file refs.  I need a good use case for creating an SE application with external jar refs.
Comment 1 Neil Hauge CLA 2011-10-07 12:52:24 EDT 
Targeting to Juno release.
Comment 2 Neil Hauge CLA 2012-04-23 17:23:05 EDT 
I would guess this is a regression from the removal of utility project in Indigo?
Comment 3 Paul Fullbright CLA 2012-04-23 17:25:01 EDT 
It could be considered a regression if there *were* SE use cases before.  I'd like to see an SE use case with jar refs before I'd say that for sure, though.