frascati issueshttps://gitlab.ow2.org/frascati/frascati/-/issues2018-02-06T10:32:18Zhttps://gitlab.ow2.org/frascati/frascati/-/issues/85mvn sonar:sonar failed2018-02-06T10:32:18ZPhilippe Merlemvn sonar:sonar failedRunning 'mvn sonar:sonar' failed.
Running 'mvn sonar:sonar' failed.
https://gitlab.ow2.org/frascati/frascati/-/issues/84implementation-bpel and implementation-xquery incompatibility 2018-02-06T09:58:42ZMunilla Christopheimplementation-bpel and implementation-xquery incompatibility implementation-bpel and implementation-xquery use incompatible libraries because implementing a wide range of same classes (not all), but not in the same version (net.sourceforge.saxon:saxon:9.1.0.8 for xquery and net.sf.saxon:saxonhe:9....implementation-bpel and implementation-xquery use incompatible libraries because implementing a wide range of same classes (not all), but not in the same version (net.sourceforge.saxon:saxon:9.1.0.8 for xquery and net.sf.saxon:saxonhe:9.2.0.6 for bpel)
Reproduce the error :
add the implementation-xquery dependency to the factorial-bpel example
<dependency>
<groupId>org.ow2.frascati</groupId>
<artifactId>frascati-implementation-script-xquery</artifactId>
<version>${project.version}</version>
</dependency>
then try to execute the maven installation process of the factorial-bpel example,an exception is thrown :
java.lang.NoSuchMethodError: net.sf.saxon.Configuration.newConfiguration()Lnet/sf/saxon/Configuration;
at net.sf.saxon.xpath.XPathFactoryImpl.<init>(XPathFactoryImpl.java:26)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at javax.xml.xpath.XPathFactoryFinder.loadFromService(XPathFactoryFinder.java:370)
at javax.xml.xpath.XPathFactoryFinder._newFactory(XPathFactoryFinder.java:222)
at javax.xml.xpath.XPathFactoryFinder.newFactory(XPathFactoryFinder.java:143)
at javax.xml.xpath.XPathFactory.newInstance(XPathFactory.java:185)
at javax.xml.xpath.XPathFactory.newInstance(XPathFactory.java:99)
at com.ebmwebsourcing.easybox.impl.JaxbSchemaBinding.<clinit>(JaxbSchemaBinding.java:50)
at com.ebmwebsourcing.easybox.impl.AbstractXmlObjectSchemaBindingImpl.<init>(AbstractXmlObjectSchemaBindingImpl.java:28)
at com.ebmwebsourcing.easyschema10.impl.XmlObjectSchemaBindingImpl.<init>(XmlObjectSchemaBindingImpl.java:15)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:345)
A simple substitution of library in an implementation or an other does not work.https://gitlab.ow2.org/frascati/frascati/-/issues/18Support Maven 32018-09-10T23:26:45ZPhilippe MerleSupport Maven 3Add support to build and run FraSCAti with Apache Maven 3.
Add support to build and run FraSCAti with Apache Maven 3.
1.4https://gitlab.ow2.org/frascati/frascati/-/issues/15Reflecting FraSCAti modules as OSGi bundles2018-09-10T23:26:45ZRomain RouvoyReflecting FraSCAti modules as OSGi bundlesOSGi defines a standard packaging mechanism, which can be used to better isolate the loading of
software modules within a standard Java Runtime Environment. FraSCAti «à la carte» could benefit from
this mechanism to better control the ...OSGi defines a standard packaging mechanism, which can be used to better isolate the loading of
software modules within a standard Java Runtime Environment. FraSCAti «à la carte» could benefit from
this mechanism to better control the loaded modules as well as their dependencies.
It would therefore be nice to consider the definition of OSGi-compliant manifest files for the module of
the platform. Existing tools, such as BND [1] or Tycho [2] could facilitate this task by generating the
manifest file from the Maven configuration file.
References
1. BND. http://www.aqute.biz/Code/Bnd
2. Tycho. http://tycho.sonatype.org
Romain Rouvoy