Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347096

Summary:	Vex (may) need a cq for org.w3c.css.sac_1.3.1.*.jar
Product:	z_Archived	Reporter:	David Williams <david_williams>
Component:	Mylyn	Assignee:	Florian Thienel <florian>
Status:	CLOSED FIXED	QA Contact:	David Williams <david_williams>
Severity:	normal
Priority:	P2	CC:	florian
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2011-05-24 20:26:58 EDT

It has come to my attention that vex is "distributing" org.w3c.css.sac_1.3.1.*.jar in its latest builds, apparently without a corresponding cq? Is there such a cq? 

I notice too that Orbit does have two version of this bundle 1.3.0 and 1.3.1, so you might just be "getting the latest" from Orbit ... but, still, you need a CQ. You should be able to "piggy back" on existing orbit cq so its relatively quick and easy. 

If for some reason, you need 1.3.0 specifically (and have a cq for it) there are ways to constrain your build to get only 1.3.0, but normally we encourage everyone to "use the latest" if possible, since might have important fixes, and easier to gain wide spread consistency across Eclipse. 

While you are not "releasing" right now, it is important to fix this soon, since according to dev. process, our "IP Logs" must always be accurate, not just at releases (even though, that is when IP logs are normally checked). 

Thanks,

Comment 1 Florian Thienel

2011-05-25 04:00:57 EDT

Thank you for the hint, David. My fault. I missed to put a version number in our target definition. 

Since we plan to replace org.w3c.css.sac with Batik CSS (bug 341961), I think we can specifically reference 1.3.0 for now and get around the additional CQ for 1.3.1. I will do this later today.

Comment 2 David Williams

2011-05-25 07:20:37 EDT

My advice is to file the CQ. Since you are re-using something from Orbit, it is really just documenting what you are doing ... you don't need to re-attach source, and all that ... and its quick and easy for IP team to approve, since they do not need to review any new code ... and ... the reason for this advice ... since you already have it in some downloads, you are already distributing it, in the strict sense of the word, so better to have the CQ, so it covers those already existing cases. Plus, it is normally best to use the highest version you can, just to have latests fixes, etc., Naturally, if you really needed to use the lower version, due to api or behavior change, that'd be a different matter. 

Let me know if questions,

Comment 3 Florian Thienel

2011-05-25 15:17:25 EDT

(In reply to comment #2)
> ... since you already have it in some downloads, you are already distributing
> it, in the strict sense of the word ...
This sounds reasonable. I filed CQ 5250.

Comment 4 Florian Thienel

2011-06-07 14:45:42 EDT

The CQ is approved.

Comment 5 Florian Thienel

2011-11-09 17:36:08 EST

Moved to Mylyn Docs Vex.