I'm trying to build apache-commons-jexl 2.0.1 in rawhide and am getting:
Failed to resolve artifact. Missing: ---------- 1) org.apache.bsf:bsf-api:jar:3.0-beta3
It uses the javax.script API which as I understand it is included in Java 1.6. The jexl pom.xml has:
<!-- For JSR-223 API --> <dependency> <groupId>org.apache.bsf</groupId> <artifactId>bsf-api</artifactId> <version>3.0-beta3</version> <scope>provided</scope> </dependency>
Short of patching that out of the pom.xml file (which works), is there some way I (or something else) should express that bsf-api 3.0 is provided? Or is jexl upstream misguided in adding this dependency?
Thanks!
Hi Orion,
I'm trying to build apache-commons-jexl 2.0.1 in rawhide and am getting:
Failed to resolve artifact. Missing:
- org.apache.bsf:bsf-api:jar:3.0-beta3
It uses the javax.script API which as I understand it is included in Java 1.6. The jexl pom.xml has:
<!-- For JSR-223 API --> <dependency> <groupId>org.apache.bsf</groupId> <artifactId>bsf-api</artifactId> <version>3.0-beta3</version> <scope>provided</scope> </dependency>
Short of patching that out of the pom.xml file (which works), is there some way I (or something else) should express that bsf-api 3.0 is provided? Or is jexl upstream misguided in adding this dependency?
Pom and depmap should be added to the bsf. The pom you are looking for is at http://repo1.maven.org/maven2/org/apache/bsf/bsf-api/3.0-beta3/bsf-api-3.0- beta3.pom
One more thing we have bsf 2.4 in fedora now. repoquery --whatrequires bsf gives me: bsf-0:2.4.0-4.fc13.i686 xdoclet-0:1.2.3-11.4.fc12.i686 ant-apache-bsf-0:1.7.1-13.fc13.i686 bsh-0:1.3.0-15.2.fc13.noarch groovy-0:1.7.0-1.fc13.1.noarch
I hope that updating bsf would not break it.
Alex
Thanks!
On 05/26/2010 03:37 PM, Alexander Kurtakov wrote:
Hi Orion,
I'm trying to build apache-commons-jexl 2.0.1 in rawhide and am getting:
Failed to resolve artifact. Missing:
- org.apache.bsf:bsf-api:jar:3.0-beta3
It uses the javax.script API which as I understand it is included in Java 1.6. The jexl pom.xml has:
<!-- For JSR-223 API --> <dependency> <groupId>org.apache.bsf</groupId> <artifactId>bsf-api</artifactId> <version>3.0-beta3</version> <scope>provided</scope> </dependency>
Short of patching that out of the pom.xml file (which works), is there some way I (or something else) should express that bsf-api 3.0 is provided? Or is jexl upstream misguided in adding this dependency?
Pom and depmap should be added to the bsf. The pom you are looking for is at http://repo1.maven.org/maven2/org/apache/bsf/bsf-api/3.0-beta3/bsf-api-3.0- beta3.pom
One more thing we have bsf 2.4 in fedora now. repoquery --whatrequires bsf gives me: bsf-0:2.4.0-4.fc13.i686 xdoclet-0:1.2.3-11.4.fc12.i686 ant-apache-bsf-0:1.7.1-13.fc13.i686 bsh-0:1.3.0-15.2.fc13.noarch groovy-0:1.7.0-1.fc13.1.noarch
I hope that updating bsf would not break it.
I don't think that is quite correct. The package builds just fine without bsf 3.0 because the javax.script API (that bsf 3.0 is/provides) is in Java 1.6.
It seems to me that jexl should be requiring bsf-api 3.0 OR java 1.6 (don't know if a pom can express that), or maybe java-1.6.0-openjdk should provide bsf-api 3.0?
2010/5/27 Orion Poplawski orion@cora.nwra.com:
I don't think that is quite correct. The package builds just fine without bsf 3.0 because the javax.script API (that bsf 3.0 is/provides) is in Java 1.6.
It seems to me that jexl should be requiring bsf-api 3.0 OR java 1.6 (don't know if a pom can express that), or maybe java-1.6.0-openjdk should provide bsf-api 3.0?
Afaik, bsf-api is a module built along apache-bsf-3.0 which is intended to be used with jdks prior to 1.6.0 (it provides the JSR-223 api defined in 1.6 with javax.script).
If your package only needs the api and you dont mind requiring java >= 1.6.0, just strip away the dep from the pom. If you also need the implementation, you need to package bsf-3.0 and install its poms for maven (possible java package names clash if both javax.script from jdk *and* javax.script from bsf-api go into classhpath?) bsf 2.x wont do because it is based on a different api.
hope that helps
java-devel@lists.fedoraproject.org