Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365980 - Import range for org.eclipse.jst.jsp.core needs to be widened
Summary: Import range for org.eclipse.jst.jsp.core needs to be widened
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 blocker (vote)
Target Milestone: 3.4 M4   Edit
Assignee: David Williams CLA
QA Contact: Nick Sandonato CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 19:29 EST by Carl Anderson CLA
Modified: 2011-12-08 00:40 EST (History)
2 users (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 Carl Anderson CLA 2011-12-07 19:29:15 EST 
The WTP 3.4.0 build is now failing with:

Processing inclusion from feature org.eclipse.jst.web_core.feature: Bundle org.eclipse.jst.jsp.core_1.2.500.v201112071854 failed to resolve.:[build-wtp4x-jst4x-sdk]         
Unsatisfied import package javax.servlet.jsp.tagext_[2.0.0,2.2.0).
Comment 1 Carl Anderson CLA 2011-12-08 00:16:11 EST 
It would appear that simply widening the range to

javax.servlet.jsp.tagext;version="[2.0.0,2.3.0)"

solves the issue.
Comment 2 David Williams CLA 2011-12-08 00:40:01 EST 
Seeing as this was blocking builds (of which there will likely need to be several others) Carl ask if I could apply fix. Which I did. little after midnight. 

But, I really widened range [2.0,3.0) ... from what I could tell, we didn't use much complicated ("internal") looking from there and while they do not necessarily strictly follow OSGi semantics, unlikely a wide range for package import would hurt any thing. Feel free to make tighter, if a core JSP committer has a different opinion. I would not be offended ... no questions asked :)