Bugzilla – Full Text Bug Listing
| Summary: | Plan schema does not support plans with a 2+ digit version components | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Kyle Smith <kylesm> |
| Component: | unknown | Assignee: | Steve Powell <zteve.powell> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | glyn.normington |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 311155 | ||
|
Description
Kyle Smith
Yup, that is clear. How could we not have spotted that? Thank you -- this will go in as soon as we figure out how to change the schema!!! Incidentally, a really nice bugzilla. I wish all bug descriptions were so clear and complete (and included the fix!!). Change pushed to git : org.eclipse.virgo.kernel.git. SHA: 85b496ed8734229fa11fcf788ef534c6d319ac68 Author: Steve Powell <spowell@vmware.com> Date: Wed Aug 04 2010 15:17:27 GMT+0100 (BST) Subject: [Bug 321634] Fix version pattern in plan schema. It will be a short time before the public schema (at http://www.springsource.org/schema/dm-server/plan) is updated. See previous post. I updated the public schema. Not sure how long it will take to propagate out through the various caches. Kyle: can you verify here that you don't see this problem anymore? (In reply to comment #5) > Kyle: can you verify here that you don't see this problem anymore? Deploying the plan is still resulting in that exception, but it looks like the XSD on springsource.org either hasn't gotten updated yet or some proxy along the way is caching it (flushed my own browser cache and still doesn't have the fix). Does one of the Virgo JARs have an embedded copy it might be using? Kyle, The schema is sourced from org.eclipse.virgo.kernel.artifact/src/main/resources/org/eclipse/virgo/kernel/artifact/plan/springsource-dm-server-plan.xsd and that is updated in the latest build of the kernel. There should be no other version anywhere except in the public address you are using. Can you look at the address you're using in the header of the plan xml file to see which version that appears to be? Thank you for taking the time to look at this for us. We'll do a few experiments here also. Steve Powell Tests here with the latest Kernel work fine: [2010-08-12 11:15:18.789] fs-watcher <DE0000I> Installing plan 'test' version '29.19.90'. [2010-08-12 11:15:18.796] fs-watcher <DE0000I> Installing configuration 'test' version '0.0.0'. [2010-08-12 11:15:18.803] fs-watcher <DE0001I> Installed configuration 'test' version '0.0.0'. [2010-08-12 11:15:18.807] fs-watcher <DE0001I> Installed plan 'test' version '29.19.90'. [2010-08-12 11:15:18.813] fs-watcher <DE0004I> Starting plan 'test' version '29.19.90'. [2010-08-12 11:15:18.817] fs-watcher <DE0004I> Starting configuration 'test' version '0.0.0'. [2010-08-12 11:15:18.827] fs-watcher <DE0005I> Started configuration 'test' version '0.0.0'. [2010-08-12 11:15:18.831] fs-watcher <DE0005I> Started plan 'test' version '29.19.90'. with a simple plan that references a configuration artefact. Closing this. |