135180 – Can't use jdt with MANAGED-ONLY policy

Bug 135180 - Can't use jdt with MANAGED-ONLY policy

Summary: Can't use jdt with MANAGED-ONLY policy

Status:	RESOLVED FIXED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version:	3.2
Hardware:	PC Windows XP

Importance:	P3 critical (vote)
Target Milestone:	---
Assignee:	Branko Tripkovic
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-04-05 20:45 EDT by James D. Miles
Modified:	2006-05-07 00:31 EDT (History)
CC List:	14 users (show)

See Also:

Attachments
test bundle (3.78 KB, application/octet-stream) 2006-05-05 10:47 EDT, Thomas Watson	no flags	Details
Patch to use the algorithm (2.19 KB, patch) 2006-05-05 11:02 EDT, Pascal Rapicault	no flags	Details \| Diff
Patch getting rid of the need to parse (2.28 KB, patch) 2006-05-05 11:27 EDT, Pascal Rapicault	no flags	Details \| Diff
regex based parser for symbolic name, version (2.27 KB, text/plain) 2006-05-05 11:34 EDT, David Williams	no flags	Details
Show Obsolete (1) View All 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 James D. Miles

2006-04-05 20:45:48 EDT

It is critical that this environment work with 1.42 and the update policy MANAGED-only.
Once the platform has been launched once and the platform.xml created, modify the platform.xml as follows

<config date="1144282934719" transient="true" version="3.0">
<site enabled="true" policy="MANAGED-ONLY" updateable="true" url="platform:/base/">

Change transient to "true" and policy to "MANAGED-ONLY"

!MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: J2SE-1.5
for bundles 
org.eclipse.jdt.apt.ui_3.2.0.v200600401-0050.jar 
org.eclipse.jdt.apt.core_3.2.0.v200600401-0050.jar 

Also
The version number does not work for
org.eclipse.jdt.core_3.2.0.v_653
The _653 causes the plugin to not resolve.

Comment 1 James D. Miles

2006-04-05 20:46:39 EDT

I am using eclipse 3.2 M6

Comment 2 Jerome Lanneluc

2006-04-06 03:37:00 EDT

Moving to Platform Update

Comment 3 James D. Miles

2006-04-06 07:05:10 EDT

Why are you moving to platform update? 2 problems are in the plugin manifest when you specify the bundle environment J2SE-1.5.
The last problem is that you have an incompatible version number on a plugin.

Comment 4 Darin Wright

2006-04-06 10:43:04 EDT

Moving to runtime. Not sure if this is runtime or PDE issue.

Comment 5 Pascal Rapicault

2006-04-07 10:01:19 EDT

James, the apt plug-ins are written using 1.5 features therefore they will not run on 1.4 VMs. This is a design decision of the APT team and removing the execution environment header of there manifest that will not help. You should talk to them.

I have never seen this "The _653 causes the plugin to not resolve".

Comment 6 James D. Miles

2006-04-07 11:46:22 EDT

First let me say the apt requirement problem was probably a mistake to mention. However I was just trying to get my platform working and they were the first 2 problems that appeared. 

But when using JVM 1.5 I still have the problem so I will attempt to document it here.

Check this bug 89428
I reported this to the update group back in M5. And when I found this bug I thought it would be taken care of. So please work with whoever you need and fix this. Here is debug information with incorrect versioning and with it fixed.

ICON launch arguments
C:\32work\eclipse32M6nomod\eclipse\eclipse.exe  -data C:\temp\workspaces32\32work\32M6nomod\workspace -configuration  C:\temp\workspaces32\32work\32M6nomod\configuration -console -consoleLog -debug -clean

Everything worked error free with JVM 1.5
Then I changed the platform.xml to MANAGED-ONLY and transient="true"
<?xml version="1.0" encoding="UTF-8"?>
<config date="1144274046529" transient="true" version="3.0">
<site enabled="true" policy="MANAGED-ONLY" updateable="true" url="platform:/base/">
<feature id="org.eclipse.platform" url="features/org.eclipse.platform_3.2.0.v20060324-yOAYN1hK7ff_yJX/" version="3.2.0.v20060324-yOAYN1hK7ff_yJX">
</feature>
<feature id="org.eclipse.rcp" url="features/org.eclipse.rcp_3.2.0.v20060317-RI9KSe6UHHoUcOM/" version="3.2.0.v20060317-RI9KSe6UHHoUcOM">
</feature>
<feature id="org.eclipse.platform.source" url="features/org.eclipse.platform.source_3.2.0.v20060324-yOAYN1hK7ff_yJX/" version="3.2.0.v20060324-yOAYN1hK7ff_yJX">
</feature>
<feature id="org.eclipse.jdt" url="features/org.eclipse.jdt_3.2.0.v20060329-1600-znkkvc87raMsMW5/" version="3.2.0.v20060329-1600-znkkvc87raMsMW5">
</feature>
<feature id="org.eclipse.jdt.source" url="features/org.eclipse.jdt.source_3.2.0.v20060329-1600-znkkvc87raMsMW5/" version="3.2.0.v20060329-1600-znkkvc87raMsMW5">
</feature>
<feature id="org.eclipse.pde" url="features/org.eclipse.pde_3.2.0.v20060314-6zXJJzJeZroKRDD/" version="3.2.0.v20060314-6zXJJzJeZroKRDD">
</feature>
<feature id="org.eclipse.sdk" url="features/org.eclipse.sdk_3.2.0.v20060324-85_JhIwpYpsFJg7/" version="3.2.0.v20060324-85_JhIwpYpsFJg7">
</feature>
<feature id="org.eclipse.pde.source" url="features/org.eclipse.pde.source_3.2.0.v20060314-6zXJJzJeZroKRDD/" version="3.2.0.v20060314-6zXJJzJeZroKRDD">
</feature>
<feature id="org.eclipse.rcp.source" url="features/org.eclipse.rcp.source_3.2.0.v20060317-RI9KSe6UHHoUcOM/" version="3.2.0.v20060317-RI9KSe6UHHoUcOM">
</feature>
</site>
</config>

A relaunch give the following errors. jdt is not available.

Configuration location:
    file:/C:/temp/workspaces32/32work/32M6nomod/configuration/
Configuration file:
    file:/C:/temp/workspaces32/32work/32M6nomod/configuration/config.ini not found or not read
Install location:
    file:/c:/32work/eclipse32M6nomod/eclipse/
Configuration file:
    file:/c:/32work/eclipse32M6nomod/eclipse/configuration/config.ini loaded
Shared configuration location:
    file:/c:/32work/eclipse32M6nomod/eclipse/configuration/
Framework located:
    file:/c:/32work/eclipse32M6nomod/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060328.jar
Framework classpath:
    file:/c:/32work/eclipse32M6nomod/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060328.jar
Splash location:
    c:\32work\eclipse32M6nomod\eclipse\plugins\org.eclipse.platform_3.2.0.v20060329\splash.bmp
runCommand:
    <C:\32work\eclipse32M6nomod\eclipse\eclipse.exe><-name><Eclipse><-showsplash><600><c:\32work\eclipse32M6nomod\eclipse\plugins\org.eclipse.platform_3.2.0.v20060329\splash.bmp>
Debug options:
    file:/C:/temp/workspaces32/32work/32M6nomod/.options not found

osgi> Time to load bundles: 90
!SESSION 2006-04-07 10:15:26.610 -----------------------------------------------
eclipse.buildId=I20060331-2000
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -data C:\temp\workspaces32\32work\32M6nomod\workspace -console -consoleLog -debug -clean

!ENTRY org.eclipse.osgi 2 0 2006-04-07 10:15:28.763
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.763
!MESSAGE Bundle update@plugins/org.eclipse.jdt.core.manipulation_1.0.0.v20060329-1600.jar was not resolved.
!SUBENTRY 2 org.eclipse.jdt.core.manipulation 2 0 2006-04-07 10:15:28.763
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.763
!MESSAGE Bundle update@plugins/org.eclipse.jdt.junit_3.2.0.v20060329-1600/ was not resolved.
!SUBENTRY 2 org.eclipse.jdt.junit 2 0 2006-04-07 10:15:28.763
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.763
!MESSAGE Bundle update@plugins/org.eclipse.pde.ui_3.2.0.v20060330-2000.jar was not resolved.
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:28.763
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.763
!MESSAGE Bundle update@plugins/org.eclipse.jdt.debug_3.2.0.v20060329b/ was not resolved.
!SUBENTRY 2 org.eclipse.jdt.debug 2 0 2006-04-07 10:15:28.763
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.773
!MESSAGE Bundle update@plugins/org.eclipse.ant.ui_3.2.0.v20060330.jar was not resolved.
!SUBENTRY 2 org.eclipse.ant.ui 2 0 2006-04-07 10:15:28.773
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.773
!MESSAGE Bundle update@plugins/org.eclipse.jdt.debug.ui_3.2.0.v20060329a.jar was not resolved.
!SUBENTRY 2 org.eclipse.jdt.debug.ui 2 0 2006-04-07 10:15:28.773
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.773
!MESSAGE Bundle update@plugins/org.eclipse.jdt.apt.ui_3.2.0.v200600401-0050.jar was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.ui 2 0 2006-04-07 10:15:28.773
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.773
!MESSAGE Bundle update@plugins/org.eclipse.pde.core_3.2.0.v20060330-2000.jar was not resolved.
!SUBENTRY 2 org.eclipse.pde.core 2 0 2006-04-07 10:15:28.773
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.783
!MESSAGE Bundle update@plugins/org.eclipse.jdt.ui_3.2.0.v20060330-1200.jar was not resolved.
!SUBENTRY 2 org.eclipse.jdt.ui 2 0 2006-04-07 10:15:28.783
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.783
!MESSAGE Bundle update@plugins/org.eclipse.jdt.launching_3.2.0.v20060327b.jar was not resolved.
!SUBENTRY 2 org.eclipse.jdt.launching 2 0 2006-04-07 10:15:28.783
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.783
!MESSAGE Bundle update@plugins/org.eclipse.jdt.apt.core_3.2.0.v200600401-0050.jar was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.core 2 0 2006-04-07 10:15:28.783
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.

!ENTRY org.eclipse.osgi 2 0 2006-04-07 10:15:28.813
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.813
!MESSAGE Bundle update@plugins/org.eclipse.ant.ui_3.2.0.v20060330.jar [83] was not resolved.
!SUBENTRY 2 org.eclipse.ant.ui 2 0 2006-04-07 10:15:28.833
!MESSAGE Missing required bundle org.eclipse.jdt.ui_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.ant.ui 2 0 2006-04-07 10:15:28.833
!MESSAGE Missing required bundle org.eclipse.jdt.debug.ui_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.ant.ui 2 0 2006-04-07 10:15:28.833
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.ant.ui 2 0 2006-04-07 10:15:28.833
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.863
!MESSAGE Bundle update@plugins/org.eclipse.jdt.apt.core_3.2.0.v200600401-0050.jar [84] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.core 2 0 2006-04-07 10:15:28.863
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:28.863
!MESSAGE Bundle update@plugins/org.eclipse.jdt.apt.ui_3.2.0.v200600401-0050.jar [85] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.ui 2 0 2006-04-07 10:15:29.013
!MESSAGE Missing required bundle org.eclipse.jdt.apt.core_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.ui 2 0 2006-04-07 10:15:29.023
!MESSAGE Missing required bundle org.eclipse.jdt.ui_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.ui 2 0 2006-04-07 10:15:29.023
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.023
!MESSAGE Bundle update@plugins/org.eclipse.jdt.core.manipulation_1.0.0.v20060329-1600.jar [86] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.core.manipulation 2 0 2006-04-07 10:15:29.023
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.023
!MESSAGE Bundle update@plugins/org.eclipse.jdt.debug.ui_3.2.0.v20060329a.jar [87] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.debug.ui 2 0 2006-04-07 10:15:29.023
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.debug.ui 2 0 2006-04-07 10:15:29.023
!MESSAGE Missing required bundle org.eclipse.jdt.debug_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.debug.ui 2 0 2006-04-07 10:15:29.023
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.debug.ui 2 0 2006-04-07 10:15:29.033
!MESSAGE Missing required bundle org.eclipse.jdt.ui_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.debug.ui 2 0 2006-04-07 10:15:29.033
!MESSAGE Missing required bundle org.eclipse.jdt.core.manipulation_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.033
!MESSAGE Bundle update@plugins/org.eclipse.jdt.debug_3.2.0.v20060329b/ [88] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.debug 2 0 2006-04-07 10:15:29.033
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.033
!MESSAGE Bundle update@plugins/org.eclipse.jdt.junit_3.2.0.v20060329-1600/ [89] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.junit 2 0 2006-04-07 10:15:29.033
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.junit 2 0 2006-04-07 10:15:29.043
!MESSAGE Missing required bundle org.eclipse.jdt.ui_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.junit 2 0 2006-04-07 10:15:29.043
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.junit 2 0 2006-04-07 10:15:29.053
!MESSAGE Missing required bundle org.eclipse.jdt.debug.ui_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.084
!MESSAGE Bundle update@plugins/org.eclipse.jdt.launching_3.2.0.v20060327b.jar [91] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.launching 2 0 2006-04-07 10:15:29.084
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jdt.launching 2 0 2006-04-07 10:15:29.084
!MESSAGE Missing required bundle org.eclipse.jdt.debug_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.084
!MESSAGE Bundle update@plugins/org.eclipse.jdt.ui_3.2.0.v20060330-1200.jar [92] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.ui 2 0 2006-04-07 10:15:29.114
!MESSAGE Missing required bundle org.eclipse.jdt.core_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.ui 2 0 2006-04-07 10:15:29.114
!MESSAGE Missing required bundle org.eclipse.jdt.launching_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.ui 2 0 2006-04-07 10:15:29.114
!MESSAGE Missing required bundle org.eclipse.jdt.core.manipulation_[1.0.0,2.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.154
!MESSAGE Bundle update@plugins/org.eclipse.pde.core_3.2.0.v20060330-2000.jar [99] was not resolved.
!SUBENTRY 2 org.eclipse.pde.core 2 0 2006-04-07 10:15:29.154
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.core 2 0 2006-04-07 10:15:29.154
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2006-04-07 10:15:29.154
!MESSAGE Bundle update@plugins/org.eclipse.pde.ui_3.2.0.v20060330-2000.jar [102] was not resolved.
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.184
!MESSAGE Missing required bundle org.eclipse.pde.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.184
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.194
!MESSAGE Missing required bundle org.eclipse.jdt.debug.ui_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.224
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.224
!MESSAGE Missing required bundle org.eclipse.jdt.ui_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.224
!MESSAGE Missing required bundle org.eclipse.ant.ui_[3.1.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.224
!MESSAGE Missing required bundle org.eclipse.jdt.junit_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.ui 2 0 2006-04-07 10:15:29.254
!MESSAGE Missing imported package org.eclipse.jdt.debug.core_0.0.0.
Starting application: 2654
Application Started: 7300
ss

Framework is launched.

id      State       Bundle
0       ACTIVE      system.bundle_3.2.0.v20060328
1       ACTIVE      org.eclipse.equinox.common_3.2.0.v20060329
2       ACTIVE      org.eclipse.update.configurator_3.1.100.v20060329
3       ACTIVE      org.eclipse.core.runtime_3.2.0.v20060327-1200
4       RESOLVED    com.jcraft.jsch_0.1.26
5       RESOLVED    org.apache.ant_1.6.5
6       RESOLVED    org.apache.lucene_1.4.103.v20060320
7       RESOLVED    org.eclipse.ant.core_3.1.100.v20060330
8       RESOLVED    org.eclipse.compare_3.2.0.v20060330
9       RESOLVED    org.eclipse.core.boot_3.1.100.v20060313
10      RESOLVED    org.eclipse.core.filebuffers_3.2.0.v20060329-1600
11      RESOLVED    org.eclipse.core.filesystem_1.0.0.v20060317
                    Fragments=56
12      ACTIVE      org.eclipse.core.resources_3.2.0.v20060328
                    Fragments=13, 57
13      RESOLVED    org.eclipse.core.resources.compatibility_3.2.0.v20060313
                    Master=12
14      ACTIVE      org.eclipse.core.runtime.compatibility_3.1.100.v20060313
15      RESOLVED    org.eclipse.osgi.services_3.1.100.v20060109
16      RESOLVED    org.eclipse.osgi.util_3.1.100.v20060109
17      RESOLVED    org.eclipse.core.variables_3.1.100.v20060227
18      ACTIVE      org.eclipse.debug.core_3.2.0.v20060329b
19      ACTIVE      org.eclipse.debug.ui_3.2.0.v20060329b
20      RESOLVED    org.eclipse.help.webapp_3.2.0.v20060327a
21      RESOLVED    org.eclipse.help.base_3.2.0.v20060328
22      RESOLVED    org.eclipse.help.ui_3.2.0.v20060327a
23      RESOLVED    org.eclipse.help.appserver_3.1.100.v20060223
24      RESOLVED    org.eclipse.ltk.core.refactoring_3.2.0.v20060329-1600
25      RESOLVED    org.eclipse.ltk.ui.refactoring_3.2.0.v20060329-1600
26      RESOLVED    org.eclipse.platform_3.2.0.v20060329
27      RESOLVED    org.eclipse.platform.doc.user_3.2.0.v20060327
28      RESOLVED    org.eclipse.search_3.2.0.v20060329-1600
29      RESOLVED    org.eclipse.team.core_3.2.0.I200603301205
30      RESOLVED    org.eclipse.team.cvs.core_3.2.0.I20060330
31      RESOLVED    org.eclipse.team.cvs.ssh_3.2.0.I200603291800
32      RESOLVED    org.eclipse.team.cvs.ssh2_3.2.0.I200603291800
33      RESOLVED    org.eclipse.team.cvs.ui_3.2.0.I200603301200
34      RESOLVED    org.eclipse.team.ui_3.2.0.I200603301200
35      RESOLVED    org.eclipse.tomcat_4.1.130.v20060303
36      RESOLVED    org.eclipse.text_3.2.0.v20060329-1600
37      RESOLVED    org.eclipse.jface.text_3.2.0.v20060329-1600
38      RESOLVED    org.eclipse.ui.console_3.1.100.v20060318
39      RESOLVED    org.eclipse.ui.presentations.r21_3.2.0.I20060307-0800
40      RESOLVED    org.eclipse.ui.intro_3.2.0.v20060327
41      RESOLVED    org.eclipse.ui.intro.universal_3.2.0.v20060329
42      RESOLVED    org.eclipse.ui.cheatsheets_3.2.0.v20060328
43      RESOLVED    org.eclipse.ui.browser_3.2.0.v20060317
44      RESOLVED    org.eclipse.ui.navigator_3.2.0.I20060330-2000
45      RESOLVED    org.eclipse.ui.navigator.resources_3.2.0.I20060329-20000
46      RESOLVED    org.eclipse.ui.workbench.texteditor_3.2.0.v20060329-1600
47      ACTIVE      org.eclipse.ui.views_3.2.0.I20060321-0800
48      RESOLVED    org.eclipse.ui.editors_3.2.0.v20060329-1600
49      RESOLVED    org.eclipse.ui.forms_3.2.0.v20060315
50      ACTIVE      org.eclipse.ui.externaltools_3.1.100.v20060326
51      ACTIVE      org.eclipse.ui.ide_3.2.0.I20060327-1600
                    Fragments=58
52      ACTIVE      org.eclipse.update.core_3.1.100.v20060329a
                    Fragments=59
53      ACTIVE      org.eclipse.update.scheduler_3.1.100
54      RESOLVED    org.eclipse.update.ui_3.1.100.v20060329
55      RESOLVED    org.eclipse.ui.workbench.compatibility_3.2.0.I20060207-0800
                    Master=74
56      RESOLVED    org.eclipse.core.filesystem.win32.x86_1.0.0.v20051114
                    Master=11
57      RESOLVED    org.eclipse.core.resources.win32_3.2.0.v20060130
                    Master=12
58      RESOLVED    org.eclipse.ui.win32_3.2.0.I20060330-1200
                    Master=51
59      RESOLVED    org.eclipse.update.core.win32_3.1.100.v20051205
                    Master=52
60      RESOLVED    org.eclipse.ui.views.properties.tabbed_3.2.0.I20060228-0800
61      RESOLVED    org.eclipse.core.runtime.compatibility.registry_3.2.0.v20060215a
                    Master=81
62      RESOLVED    org.eclipse.platform.doc.isv_3.2.0.v20060330-1600
63      RESOLVED    com.ibm.icu_3.4.3
64      RESOLVED    org.eclipse.core.commands_3.2.0.I20060327-0010
65      ACTIVE      org.eclipse.core.jobs_3.2.0.v20060327
66      ACTIVE      org.eclipse.core.expressions_3.2.0.v20060329-1600
69      ACTIVE      org.eclipse.help_3.2.0.v20060327a
70      RESOLVED    org.eclipse.swt_3.2.0.v3229j
                    Fragments=76
71      RESOLVED    org.eclipse.jface_3.2.0.I20060329-0010
72      RESOLVED    org.eclipse.jface.databinding_1.0.0.I20060330-1600
73      ACTIVE      org.eclipse.ui_3.2.0.I20060330-2000
74      ACTIVE      org.eclipse.ui.workbench_3.2.0.I20060330-2000
                    Fragments=55
76      RESOLVED    org.eclipse.swt.win32.win32.x86_3.2.0.v3229c
                    Master=70
77      RESOLVED    org.eclipse.rcp_3.2.0.v20051206
78      ACTIVE      org.eclipse.core.contenttype_3.2.0.v20060327
80      ACTIVE      org.eclipse.equinox.preferences_3.2.0.v20060327-1200
81      ACTIVE      org.eclipse.equinox.registry_3.2.0.v20060327
                    Fragments=61
82      RESOLVED    org.eclipse.jdt_3.2.0.v20060329-1600
83      INSTALLED   org.eclipse.ant.ui_3.2.0.v20060330
84      INSTALLED   org.eclipse.jdt.apt.core_3.2.0.v200600401-0050
85      INSTALLED   org.eclipse.jdt.apt.ui_3.2.0.v200600401-0050
86      INSTALLED   org.eclipse.jdt.core.manipulation_1.0.0.v20060329-1600
87      INSTALLED   org.eclipse.jdt.debug.ui_3.2.0.v20060329a
88      INSTALLED   org.eclipse.jdt.debug_3.2.0.v20060329b
89      INSTALLED   org.eclipse.jdt.junit_3.2.0.v20060329-1600
90      RESOLVED    org.eclipse.jdt.junit.runtime_3.2.0.v20060329-1600
91      INSTALLED   org.eclipse.jdt.launching_3.2.0.v20060327b
92      INSTALLED   org.eclipse.jdt.ui_3.2.0.v20060330-1200
93      RESOLVED    org.junit_3.8.1
94      RESOLVED    org.eclipse.jdt.doc.user_3.2.0.v20060329-1600
95      RESOLVED    org.eclipse.jdt.doc.isv_3.2.0.v20060329-1600
96      RESOLVED    org.eclipse.jdt.source_3.2.0.v20060329-1600-znkkvc87raMsMW5
97      RESOLVED    org.eclipse.pde_3.2.0.v20060317
98      RESOLVED    org.eclipse.pde.build_3.2.0.v20060329a
99      INSTALLED   org.eclipse.pde.core_3.2.0.v20060330-2000
100     RESOLVED    org.eclipse.pde.junit.runtime_3.2.0.v20060330-1200
101     RESOLVED    org.eclipse.pde.runtime_3.2.0.v20060329-1600
102     INSTALLED   org.eclipse.pde.ui_3.2.0.v20060330-2000
103     RESOLVED    org.eclipse.pde.doc.user_3.2.0.v20060329-1600
104     RESOLVED    org.eclipse.pde.source_3.2.0.v20060314-6zXJJzJeZroKRDD
105     RESOLVED    org.eclipse.sdk_3.2.0.v20060329
106     RESOLVED    com.ibm.icu.source_3.4.3
107     RESOLVED    org.eclipse.rcp.source_3.2.0.v20060317-RI9KSe6UHHoUcOM
                    Fragments=108
108     RESOLVED    org.eclipse.rcp.source.win32.win32.x86_3.2.0.v20060317-RI9KSe6UHHoUcOM
                    Master=107

osgi>

Only mod I did at this point is to rename org.eclipse.jdt.core version from v_653 to v653 in plugin and feature reference
Configuration location:
    file:/C:/temp/workspaces32/32work/32M6nomod/configuration/
Configuration file:
    file:/C:/temp/workspaces32/32work/32M6nomod/configuration/config.ini not found or not read
Install location:
    file:/c:/32work/eclipse32M6nomod/eclipse/
Configuration file:
    file:/c:/32work/eclipse32M6nomod/eclipse/configuration/config.ini loaded
Shared configuration location:
    file:/c:/32work/eclipse32M6nomod/eclipse/configuration/
Framework located:
    file:/c:/32work/eclipse32M6nomod/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060328.jar
Framework classpath:
    file:/c:/32work/eclipse32M6nomod/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060328.jar
Splash location:
    c:\32work\eclipse32M6nomod\eclipse\plugins\org.eclipse.platform_3.2.0.v20060329\splash.bmp
runCommand:
    <C:\32work\eclipse32M6nomod\eclipse\eclipse.exe><-name><Eclipse><-showsplash><600><c:\32work\eclipse32M6nomod\eclipse\plugins\org.eclipse.platform_3.2.0.v20060329\splash.bmp>
Debug options:
    file:/C:/temp/workspaces32/32work/32M6nomod/.options not found

osgi> Time to load bundles: 90
Starting application: 2243
Application Started: 6519
ss

Framework is launched.

id      State       Bundle
0       ACTIVE      system.bundle_3.2.0.v20060328
1       ACTIVE      org.eclipse.equinox.common_3.2.0.v20060329
2       ACTIVE      org.eclipse.update.configurator_3.1.100.v20060329
3       ACTIVE      org.eclipse.core.runtime_3.2.0.v20060327-1200
4       RESOLVED    com.jcraft.jsch_0.1.26
5       RESOLVED    org.apache.ant_1.6.5
6       RESOLVED    org.apache.lucene_1.4.103.v20060320
7       RESOLVED    org.eclipse.ant.core_3.1.100.v20060330
8       RESOLVED    org.eclipse.compare_3.2.0.v20060330
9       RESOLVED    org.eclipse.core.boot_3.1.100.v20060313
10      RESOLVED    org.eclipse.core.filebuffers_3.2.0.v20060329-1600
11      RESOLVED    org.eclipse.core.filesystem_1.0.0.v20060317
                    Fragments=56
12      ACTIVE      org.eclipse.core.resources_3.2.0.v20060328
                    Fragments=13, 57
13      RESOLVED    org.eclipse.core.resources.compatibility_3.2.0.v20060313
                    Master=12
14      ACTIVE      org.eclipse.core.runtime.compatibility_3.1.100.v20060313
15      RESOLVED    org.eclipse.osgi.services_3.1.100.v20060109
16      RESOLVED    org.eclipse.osgi.util_3.1.100.v20060109
17      RESOLVED    org.eclipse.core.variables_3.1.100.v20060227
18      ACTIVE      org.eclipse.debug.core_3.2.0.v20060329b
19      ACTIVE      org.eclipse.debug.ui_3.2.0.v20060329b
20      RESOLVED    org.eclipse.help.webapp_3.2.0.v20060327a
21      RESOLVED    org.eclipse.help.base_3.2.0.v20060328
22      RESOLVED    org.eclipse.help.ui_3.2.0.v20060327a
23      RESOLVED    org.eclipse.help.appserver_3.1.100.v20060223
24      RESOLVED    org.eclipse.ltk.core.refactoring_3.2.0.v20060329-1600
25      RESOLVED    org.eclipse.ltk.ui.refactoring_3.2.0.v20060329-1600
26      RESOLVED    org.eclipse.platform_3.2.0.v20060329
27      RESOLVED    org.eclipse.platform.doc.user_3.2.0.v20060327
28      RESOLVED    org.eclipse.search_3.2.0.v20060329-1600
29      RESOLVED    org.eclipse.team.core_3.2.0.I200603301205
30      RESOLVED    org.eclipse.team.cvs.core_3.2.0.I20060330
31      RESOLVED    org.eclipse.team.cvs.ssh_3.2.0.I200603291800
32      RESOLVED    org.eclipse.team.cvs.ssh2_3.2.0.I200603291800
33      RESOLVED    org.eclipse.team.cvs.ui_3.2.0.I200603301200
34      RESOLVED    org.eclipse.team.ui_3.2.0.I200603301200
35      RESOLVED    org.eclipse.tomcat_4.1.130.v20060303
36      RESOLVED    org.eclipse.text_3.2.0.v20060329-1600
37      RESOLVED    org.eclipse.jface.text_3.2.0.v20060329-1600
38      RESOLVED    org.eclipse.ui.console_3.1.100.v20060318
39      RESOLVED    org.eclipse.ui.presentations.r21_3.2.0.I20060307-0800
40      RESOLVED    org.eclipse.ui.intro_3.2.0.v20060327
41      RESOLVED    org.eclipse.ui.intro.universal_3.2.0.v20060329
42      RESOLVED    org.eclipse.ui.cheatsheets_3.2.0.v20060328
43      RESOLVED    org.eclipse.ui.browser_3.2.0.v20060317
44      RESOLVED    org.eclipse.ui.navigator_3.2.0.I20060330-2000
45      RESOLVED    org.eclipse.ui.navigator.resources_3.2.0.I20060329-20000
46      RESOLVED    org.eclipse.ui.workbench.texteditor_3.2.0.v20060329-1600
47      ACTIVE      org.eclipse.ui.views_3.2.0.I20060321-0800
48      RESOLVED    org.eclipse.ui.editors_3.2.0.v20060329-1600
49      RESOLVED    org.eclipse.ui.forms_3.2.0.v20060315
50      ACTIVE      org.eclipse.ui.externaltools_3.1.100.v20060326
51      ACTIVE      org.eclipse.ui.ide_3.2.0.I20060327-1600
                    Fragments=58
52      ACTIVE      org.eclipse.update.core_3.1.100.v20060329a
                    Fragments=59
53      ACTIVE      org.eclipse.update.scheduler_3.1.100
54      RESOLVED    org.eclipse.update.ui_3.1.100.v20060329
55      RESOLVED    org.eclipse.ui.workbench.compatibility_3.2.0.I20060207-0800
                    Master=74
56      RESOLVED    org.eclipse.core.filesystem.win32.x86_1.0.0.v20051114
                    Master=11
57      RESOLVED    org.eclipse.core.resources.win32_3.2.0.v20060130
                    Master=12
58      RESOLVED    org.eclipse.ui.win32_3.2.0.I20060330-1200
                    Master=51
59      RESOLVED    org.eclipse.update.core.win32_3.1.100.v20051205
                    Master=52
60      RESOLVED    org.eclipse.ui.views.properties.tabbed_3.2.0.I20060228-0800
61      RESOLVED    org.eclipse.core.runtime.compatibility.registry_3.2.0.v20060215a
                    Master=81
62      RESOLVED    org.eclipse.platform.doc.isv_3.2.0.v20060330-1600
63      RESOLVED    com.ibm.icu_3.4.3
64      RESOLVED    org.eclipse.core.commands_3.2.0.I20060327-0010
65      ACTIVE      org.eclipse.core.jobs_3.2.0.v20060327
66      ACTIVE      org.eclipse.core.expressions_3.2.0.v20060329-1600
69      ACTIVE      org.eclipse.help_3.2.0.v20060327a
70      RESOLVED    org.eclipse.swt_3.2.0.v3229j
                    Fragments=76
71      RESOLVED    org.eclipse.jface_3.2.0.I20060329-0010
72      RESOLVED    org.eclipse.jface.databinding_1.0.0.I20060330-1600
73      ACTIVE      org.eclipse.ui_3.2.0.I20060330-2000
74      ACTIVE      org.eclipse.ui.workbench_3.2.0.I20060330-2000
                    Fragments=55
76      RESOLVED    org.eclipse.swt.win32.win32.x86_3.2.0.v3229c
                    Master=70
77      RESOLVED    org.eclipse.rcp_3.2.0.v20051206
78      ACTIVE      org.eclipse.core.contenttype_3.2.0.v20060327
80      ACTIVE      org.eclipse.equinox.preferences_3.2.0.v20060327-1200
81      ACTIVE      org.eclipse.equinox.registry_3.2.0.v20060327
                    Fragments=61
82      RESOLVED    org.eclipse.jdt_3.2.0.v20060329-1600
83      RESOLVED    org.eclipse.ant.ui_3.2.0.v20060330
84      RESOLVED    org.eclipse.jdt.apt.core_3.2.0.v200600401-0050
85      RESOLVED    org.eclipse.jdt.apt.ui_3.2.0.v200600401-0050
86      RESOLVED    org.eclipse.jdt.core_3.2.0.v653
87      RESOLVED    org.eclipse.jdt.core.manipulation_1.0.0.v20060329-1600
88      RESOLVED    org.eclipse.jdt.debug.ui_3.2.0.v20060329a
89      RESOLVED    org.eclipse.jdt.debug_3.2.0.v20060329b
90      RESOLVED    org.eclipse.jdt.junit_3.2.0.v20060329-1600
91      RESOLVED    org.eclipse.jdt.junit.runtime_3.2.0.v20060329-1600
92      RESOLVED    org.eclipse.jdt.launching_3.2.0.v20060327b
93      RESOLVED    org.eclipse.jdt.ui_3.2.0.v20060330-1200
94      RESOLVED    org.junit_3.8.1
95      RESOLVED    org.eclipse.jdt.doc.user_3.2.0.v20060329-1600
96      RESOLVED    org.eclipse.jdt.doc.isv_3.2.0.v20060329-1600
97      RESOLVED    org.eclipse.jdt.source_3.2.0.v20060329-1600-znkkvc87raMsMW5
98      RESOLVED    org.eclipse.pde_3.2.0.v20060317
99      RESOLVED    org.eclipse.pde.build_3.2.0.v20060329a
100     RESOLVED    org.eclipse.pde.core_3.2.0.v20060330-2000
101     RESOLVED    org.eclipse.pde.junit.runtime_3.2.0.v20060330-1200
102     RESOLVED    org.eclipse.pde.runtime_3.2.0.v20060329-1600
103     RESOLVED    org.eclipse.pde.ui_3.2.0.v20060330-2000
104     RESOLVED    org.eclipse.pde.doc.user_3.2.0.v20060329-1600
105     RESOLVED    org.eclipse.pde.source_3.2.0.v20060314-6zXJJzJeZroKRDD
106     RESOLVED    org.eclipse.sdk_3.2.0.v20060329
107     RESOLVED    com.ibm.icu.source_3.4.3
108     RESOLVED    org.eclipse.rcp.source_3.2.0.v20060317-RI9KSe6UHHoUcOM
                    Fragments=109
109     RESOLVED    org.eclipse.rcp.source.win32.win32.x86_3.2.0.v20060317-RI9KSe6UHHoUcOM
                    Master=108

osgi>
Everything works now.

Comment 7 Steven Wasleski

2006-05-01 13:42:34 EDT

What is the outlook for this bug getting fixed for 3.2?

Comment 8 Steven Wasleski

2006-05-02 09:06:58 EDT

James, can you clarify the behavior you see on the latest build that you believe is broken?  The state of this bug is rather confusing.

Comment 9 James D. Miles

2006-05-02 10:49:30 EDT

org.eclipse.jdt.core_3.2.0.v_661 does not load when the policy is MANAGED-ONLY.
Steps to reproduce using 32RC2 and java 1.5:
1. Setup eclipse SDK and run. exit
2. Go to the configuration dir
3. Go to org.eclipse.update directory
4. Modify the platform.xml. Change the USER-EXCLUDE to MANAGED-ONLY
5. Restart sdk.
6. Attempt to perform debug on a program. jdt is not available.

The "_" in the plugin ID is causing the problem. If the "_" is removed from the
manifest and the feature.xml, the jdt will load.

Comment 10 Jeff McAffer

2006-05-02 15:47:55 EDT

We need to look at this for 3.2.  There is something in Update that behaves differently wrt '_' in the qualifiers.  If using MANAGED-ONLY, plugins with _ in the qualifier are not even installed (see the listings in comment 6

Comment 11 Dejan Glozic

2006-05-02 16:04:10 EDT

Branko, please investigate and assess for 3.2

Comment 12 Dejan Glozic

2006-05-03 10:51:38 EDT

I think the problem is in double underscore. We use id_version format for plug-in folders of plug-in JARs. It is possible that the following form:

org.eclipse.jdt.core_3.2.0.v_661 

confuses Update because it assumes that version is 661 and id is org.eclipse.jdt.core_3.2.0.v. 

Please try not to use underscore and let us know. Branko remembers another problem with a similar resolution (i.e. avoid using '_').

Comment 13 Jeff McAffer

2006-05-04 00:07:00 EDT

comment 6 details that removeing the '_' from the qualifier makes it work.  I can see how this is a problem.  '_' is allowed in bundle symbolic names.  If it is also part of a qualifier then any attempt to reverse engineer the file name is doomed.  this is not likley something we can fix for 3.2 in the code.  We can however change our qualifier conventions where necessary.  

I suggest opening a bug with JDT in this case as it is their version naming convention that includes _.

Someone should also take this up with the Callisto crowd to ensure that other projects are not similarly affected.

Comment 14 Pascal Rapicault

2006-05-04 17:13:36 EDT

Is the same kind of parsing based on '_' is done on features?

Comment 15 Olivier Thomann

2006-05-04 17:14:26 EDT

I enter bug 140262 for the JDT/Core counter-part.

Comment 16 David Williams

2006-05-04 17:40:21 EDT

If it helps ... we've had tons of problems with this in WTP! .... glad its finally getting some attention. :) 

Don't forget that the feature version suffix (if set to true) can cause underscores to get put in feature version numbers, and I think some of these get "translated" down to feature source plugins. 

And, btw, I've learn (the hard way) there's some pretty simple rules in parsing version names/ID's .. 1) periods first, 2) the rest second. :) 

Hope this helps.

Comment 17 Olivier Thomann

2006-05-04 18:11:42 EDT

Dropping the '_' is not enough since v_631 > v632.
We want to make sure that v_631 < newVersion. So x632 should be good enough.
I'll release bug 140262 for 20060504-2000 build.

Comment 18 Pascal Rapicault

2006-05-04 20:19:06 EDT

Dejan could you point me at the code that makes those assumptions about the shape of _? Is this in platform configuration?

Comment 19 Jeff McAffer

2006-05-04 21:55:01 EDT

We really need to have a readme about this.

Comment 20 Philipe Mulet

2006-05-05 05:50:58 EDT

I am not keen on making extra requirement to remove '_' from version names, as it cannot be retrofitted in history of a plugin. So it is more a workaround than anything else. It seems a pure PDE limitation in its parsing algorithm, rather than an OSGi limitation. Changing the version name strategy is impacting dev teams, i.e. once we make this change, we cannot go back since history of versions is sorted per name, not per date... so there is no way to return to old story later on.

So when parsing: 
org.eclipse.jdt.core_3.2.0.v_661 

First underscore always separate the ID from the version; it seems like the parsing algo should use 'indexOf' instead of 'lastIndexOf'...

Comment 21 Jeff McAffer

2006-05-05 09:47:18 EDT

bundle symbolic names can have '_' too.  So looking for '_' is bogus no matter how you cut it.

Comment 22 Dejan Glozic

2006-05-05 10:37:40 EDT

Adding Dorian to the wild party.

Comment 23 Pascal Rapicault

2006-05-05 10:45:05 EDT

The problematic code seems to be in VersionedIdentifier in platform configurator.
I will look into creating a fix.

Comment 24 Thomas Watson

2006-05-05 10:47:23 EDT

Created attachment 40483 [details]
test bundle

Here is a test bundle which advances the approach put forward by Philippe in comment 20 but also takes into account that '_' may be part of the BSN.

Here is the meat of the algorithm:

private void testUnderScores(String fileName) {
	System.out.println("Testing: " + fileName);
	String bsn = null;
	Version version = null;
	int underScore = fileName.indexOf('_');
	while (underScore >= 0) {
		bsn = fileName.substring(0, underScore);
		try {
			version = Version.parseVersion(
				fileName.substring(underScore + 1));
		} catch (IllegalArgumentException iae) {
			// continue to next underscore
			underScore = fileName.indexOf('_', underScore + 1);
			continue;
		}
		break;
	}
	System.out.println("  Found BSN: " + bsn);
	System.out.println("  Found version: " + version);
}

This algorithm makes an assumption that every bundle file name will have a version string at the end even if the version is unspecified in the bundle manifest (in this case it would default to 0.0.0).

Comment 25 Pascal Rapicault

2006-05-05 10:51:27 EDT

I'm integrating this algorithm the code base to see what happens.

Comment 26 Pascal Rapicault

2006-05-05 11:02:52 EDT

Created attachment 40486 [details]
Patch to use the algorithm 

This patch makes use of the provided algorithm to parse the version string in VersionedIdentifier.

Comment 27 Dorian Birsan

2006-05-05 11:05:03 EDT

This constructor seems a bit odd:

public VersionedIdentifier(String id, String version) {
	this(id+ID_SEPARATOR+ (version==null?"0.0.0":version) ); //$NON-NLS-1$
		this.version = version;
}

and it is the only one being used in the configurator.
For this particular bug, I would fix this constructor not to delegate to the other one, as the id and versions are already known.

Comment 28 Pascal Rapicault

2006-05-05 11:14:57 EDT

I agree that we could you this, but since we are at it, we should fix the constructor that takes a String.

Comment 29 Pascal Rapicault

2006-05-05 11:19:24 EDT

or simply get rid of it since it is never used and is not API.

Comment 30 Pascal Rapicault

2006-05-05 11:27:00 EDT

Created attachment 40490 [details]
Patch getting rid of the need to parse

Comment 31 David Williams

2006-05-05 11:34:57 EDT

Created attachment 40492 [details]
regex based parser for symbolic name, version 

Just FYI ... I'm sure if your patch fixes this one problem, then you are likely done, but, if people find examples that don't work well with it, I've found it useful to use a utility like the attached to which specifies the expected "grammar rule" and then finds the best match, if a possible. 

I am not sure this approach can be used here for this bug ... that is if this "configurator" level has access to "regx" packages, but I'm posting here in the interest of open development, if it helps others, or, if others see some fault with this approach.

Comment 32 Thomas Watson

2006-05-05 11:41:18 EDT

+1 on comment 30 patch

There is no reason to parse the version at all in this class.

Comment 33 John Arthorne

2006-05-05 11:55:38 EDT

Re comment #31 - regex is not an option at this level because we need to run on Foundation class libraries.

Comment 34 Dejan Glozic

2006-05-05 12:00:31 EDT

+1 for Pascal's patch - will release.

Comment 35 Wassim Melhem

2006-05-05 12:08:58 EDT

+1 for RC3

Comment 36 Philipe Mulet

2006-05-05 14:41:00 EDT

Nice outcome, thanks for addressing it.

Comment 37 Dejan Glozic

2006-05-05 14:53:45 EDT

James, can you pick the latest build and see if it happens again? It is difficult for us to quickly set up the test that would verify the fix.

Comment 38 Olivier Thomann

2006-05-05 14:58:18 EDT

According to what I can see, it works:

46      RESOLVED    org.eclipse.jdt.core_3.2.0.v_665

using build I20060505-1306.

Comment 39 Branko Tripkovic

2006-05-05 15:09:05 EDT

i did it too, and it looks like it is working fine now

Comment 40 Dejan Glozic

2006-05-05 15:25:52 EDT

James, as we were trying to reproduce the problem with the last night's build, it cought our attention that you are setting 'transient' to 'true'. Why? This mode is reserved for PDE when platform.xml is dynamically created by PDE and passed to runtime. You are not supposed to test Update in this mode - Update needs to be 'in control' in order to do any meaningful tests with regards to the feature life cycle (see http://help.eclipse.org/help31/topic/org.eclipse.pde.doc.user/tips/pde_tips.htm for instructions on how to do it).

I am bringing this up because we took last night's build (without the fix) and we cannot reproduce this problem.

Comment 41 Branko Tripkovic

2006-05-05 16:05:21 EDT

JD Miles pls reopen if you can still reproduce this bug with rc3

Comment 42 James D. Miles

2006-05-05 20:03:34 EDT

I am reopening this bug because we need to discuss a little more. The claim is that no fix has been applied and it works. Not quite true.
I tried I20060505-1306 and it worked. So I backed up to I20060504-0010 and it worked also. Upon further investigation I find that we have applied my workaround to the plugin. The version number for M6 was v_653. The version number for the integration builds is N20060505-1306, etc. We don't see the problem because we don't have the "_" in the version number anymore.

Comment 43 James D. Miles

2006-05-05 20:21:03 EDT

This is a response to comment #40.
In comment #9 I gave the simplest test case. In it is not required to set transient to true. All that is required is to change the update policy to MANAGED-ONLY.

As far transient set to true: I guesss you link is referring to self-hosting. I am not interested in doing that. I find remote debug works well for update testing. I see exactly the behavior as it is.

For managed only policy it is necessary to set transient to true. Without settting this, the configurator will attempt to resolve date codes between the platform.xml and the features. And if the feature is newer it will get loaded. This is not desirable behavior for managed-only. I have ran many test configurations this way and I get exactly the behavior that I need. When transient=true it also doesn't read the links directory. This is also desirable behavior for managed-only. All of this is explained in bug 53858 in the 11th comment.

Comment 44 Thomas Watson

2006-05-06 10:02:24 EDT

James, 

The patch from comment 30 got released.  Did you try the fix?  I tried your steps in comment 9 and it all works.  I even tried setting transient="true" and it works also.  It is unclear why you reopened this bug.  Did you try the latest build and did it *really* fail for you?

Comment 45 James D. Miles

2006-05-06 11:39:52 EDT

I will try the patch later today. Go ahead and close this bug if you would like to. I was objecting to second paragraph of comment 40 that said it worked without the patch.

Comment 46 James D. Miles

2006-05-07 00:31:24 EDT

I verified that the problem described in this bug is fixed with RC3.