Community
Participate
Working Groups
Extension location repos added in the ui validate but will not load correctly and throw a ProvisioningException because they can't find the backing repository. We should either fix validate to ensure that the backing repository is present or else have load create the repository.
I think the fix should be in load. We had to stop contacting the repositories for validation due to bug #225062.
We are changing the code so a load will actually load the extension location repository and if it doesn't exist, it will create one with default property values. As a result, we also will be changing the callers to explicitly calling #create first, failing, and then call #load.
Created attachment 98237 [details] patch Here are changes. Will release after more testing.
Created attachment 98264 [details] patch Updated patching, including changes to test suites.
Simon, we will test this tonight and potentially release tomorrow.
The patch needs to be updated again since there were some changes to PlatformXmlListener. I did manage to test using the previous version of it. I could add an extension location using p2 UI and install what was in there.
Created attachment 98282 [details] patch ok, here is an update.
Created attachment 98293 [details] patch Another update. This one builds on the previous patch and adds additional checks in the ExtensionLocation repos for a pre-existing underlying local repo. I've also brought the createExtensionLocationRepo logic together in the dropins Activator. Both the DropinsRepositoryListener and PlatformXMLListener now use this.
Simon, the changes to the test suites are missing from your latest patch. Are there any changes to them or should I grab my changes from the previous patch?
Created attachment 98310 [details] patch You're right. This adds back the tests.
Created attachment 98315 [details] patch Updated patch for review.
Modified patch released to HEAD. Closing.