On 5/8/2010 2:55 AM, Bengt Rodehav wrote: > No one has any ideas? >
Here's an idea - Maven 3 has been doing more class loader isolation stuff. Perhaps an <extensions> element is needed? See https://cwiki.apache.org/MAVEN/maven-3x-class-loading.html -Marshall > I'm thinking along the lines that something that wasn't bundled with > maven alpha is now bundled with maven beta. Something that takes > precedence over what's need for customised url handlers to work. Does > anyone know if something has changed in that respect from the alpha to > the beta version that could break url handlers. > > /Bengt > > 2010/5/7 Bengt Rodehav <[email protected]>: > >> I'm using the features-maven-plugin included in Apache Felix. It in >> turn uses "pax-url-mvn" (version 1.1.2) to enable the protocol "mvn:". >> >> This works fine in maven 2.2.1 and also in maven 3.0-alpha-7. However, >> with everything else the same, it fails under maven 3.0-beta-1. I get >> >> "java.net.MalformedURLException: unknown protocol: null" >> >> This happens in a call to "uri.toURL()" where the uri is created from >> the string: >> "mvn:org.apache.felix.karaf/apache-felix-karaf/1.4.0/xml/features" >> >> It seems that the combination of pax-url-mvn and and maven 3.0-beta-1 >> does not work. Has anyone got any ideas as to what is wrong and >> possibly a workaround? >> >> /Bengt >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
