Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Restrictive version dependencies in WTP

Michael, no, few require such restrictive dependancies, but a handful do, and since we added these late in the cycle, we
put in the conservative range by default, and I think few components had time to really think through
if it was safe to widen. And, as I describe when I announced this strategy on this list, I think the error of being  
overly restrictive has less costly than the error of not being restrictive enough.

Michael Valenta <Michael_Valenta@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

06/26/2006 12:06 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
[cross-project-issues-dev] Restrictive version dependencies in WTP

Being a Platform developer, I have moved up to 3.3 integration builds. On the latest 3.3 integration build, WTP will not load. It appears the reason is that most (All?) of the WTP plugins state that they are only compatible with 3.2.x and some of the platrform plugins (JFace, UI and a few others) have changed their versions to 3.3. Is it really the case that all WTP plugins require such a restrictive version dependency?

cross-project-issues-dev mailing list

Back to the top