Community
Participate
Working Groups
The p2 bug #345497 revealed a change in the behaviour when it comes to contacting an URI that can't be dealt with. In 3.1.0 (see list of bundles below) the code use to throw a org.eclipse.ecf.filetransfer.identity.FileCreateException: Exception in createFileID and now it throws java.net.MalformedURLException: unknown protocol. At this point we've done a quick change in p2 but I think we need to review if this is change in ECF was intentional and if it is react to it accordingly in p2. 51 ACTIVE org.eclipse.ecf_3.1.0.v20100906-1425 Fragments=58 52 ACTIVE org.eclipse.ecf.filetransfer_4.0.0.v20100906-1425 53 ACTIVE org.eclipse.ecf.identity_3.1.0.v20100906-1425 54 ACTIVE org.eclipse.ecf.provider.filetransfer_3.1.0.v20100906-1425 Fragments=57 55 ACTIVE org.eclipse.ecf.provider.filetransfer.httpclient_4.0.0.v20100906-1425 Fragments=56 56 RESOLVED org.eclipse.ecf.provider.filetransfer.httpclient.ssl_1.0.0.v20100906-1425 Master=55 57 RESOLVED org.eclipse.ecf.provider.filetransfer.ssl_1.0.0.v20100906-1425 Master=54 58 RESOLVED org.eclipse.ecf.ssl_1.0.100.v20100906-1425 Master=51 106 ACTIVE org.eclipse.equinox.p2.transport.ecf_1.0.0.qualifier
This change in exception behavior was intentional. It was done quite a long time ago in order to address bug 268440.
Pascal...I'm inclined to close this as invalid or worksforme...as I don't see anything to do (in ECF filetransfer, at least).
Resolving as worksforme.