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

Bug 137068

Summary:	Optional dependencies are considered mandatory by the updater
Product:	[Eclipse Project] Platform	Reporter:	Hubert Leung <hkyleung>
Component:	Update (deprecated - use Eclipse>Equinox>p2)	Assignee:	Platform-Update-Inbox <platform-update-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	david_williams, mober.at+eclipse
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	obsolete

Description Hubert Leung

2006-04-17 16:01:11 EDT

This problem is found in the staging of Callisto M6.
update site: http://download.eclipse.org/callisto/staging

The TPTP Platform Project and TPTP Monitoring Tools Project only have an optional dependency on WTP. However, the updater requires WTP and all of its dependencies be selected in order to proceed with update.  One objective of making the WTP an optional dependency of TPTP is to let users use TPTP without necessarily installing WTP, although they may not be able to use some features that require WTP.  Since WTP has a lot of dependencies, making WTP optional has the benefit of reducing the footprint and install time of TPTP for people who don't need WTP related features.  The updater is not looking at the optional flag, and requires all dependencies to be installed.  

Here are some suggestions on how to solve the problem:
The "Select Required" button can select the optional dependencies.  However, the updater should let update proceed if optional dependencies are not selected. Better yet, the updater can use some visual flags to indicate which dependency is optional.

Comment 1 Branko Tripkovic

2006-04-18 23:36:51 EDT

I saw this feature:
features/org.eclipse.tptp.monitoring.runtime_4.2.0.v200604131758.jar
and there are no requires defined only imports and they are not optional:

<?xml version="1.0" encoding="UTF-8"?>
<feature
      id="org.eclipse.tptp.monitoring.runtime"
      label="%featureName"
      version="4.2.0.v200604131758"
      provider-name="%providerName">
   <install-handler/>

   <description>
      %description
   </description>

   <copyright>
      (c) Copyright Eclipse contributors and others 2005.  All rights reserved.
   </copyright>

   <license url="%licenseURL">
      %license
   </license>

   <url>
      <update label="TPTP Update Site" url="http://eclipse.org/tptp/updates/"/>
      <discovery label="TPTP Update Site" url="http://eclipse.org/tptp/updates/"/>
   </url>

   <includes
         id="org.eclipse.tptp.monitoring"
         version="4.2.0.v200604131758"/>

   <includes
         id="org.eclipse.tptp.monitoring.profile.server"
         version="4.1.100.v200604131758"/>

   <includes
         id="org.eclipse.tptp.monitoring.report.birt"
         version="4.2.0.v200604131758"/>

   <includes
         id="org.eclipse.tptp.monitoring.examples"
         version="4.2.0.v200604131758"/>

   <includes
         id="org.eclipse.tptp.monitoring.doc.user"
         version="4.2.0.v200604131758"/>

</feature>

Do i have a wrong feature? org.eclipse.tptp.platform.runtime also did not have any optionally included stuff.

Comment 2 DJ Houghton

2006-09-21 08:19:24 EDT

branko, is this a dup of bug 146869?

Comment 3 John Arthorne

2012-07-24 10:22:23 EDT

The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2.