-
Not necessarily, building the OSGi jars from the ant buildfiles and deploying them to an intranet maven repository is sufficient. On the other hand, having the osgified jars in the central repository would be nice anyway (in case a developer using JUEL has no local maven infrastructure).
2009-06-08 05:10:24 UTC in Java Unified Expression Language
-
Following the naming conventions of the SpringSource Bundle Repository (http://www.springsource.com/repository/app/) the Bundle-SymbolicName for juel-api.jar could also be de.odysseus.javax.el (see http://www.springsource.com/repository/app/bundle/version/detail?name=com.springsource.javax.el&version=1.0.0&searchType=bundlesBySymbolicName&searchQuery=javax.el for example).
2009-06-02 08:06:54 UTC in Java Unified Expression Language
-
I just uploaded a patch for the build.xml and bnd instructions for the three artifacts created by the ant build. You need bnd.jar from http://www.aqute.biz/Code/Bnd in ${basedir}/lib to wrap the jars with OSGi manifest headers (the bnd.jar is to big to be uploaded). I used the directory src/bnd as the source directory for the bnd files, following the apache standard directory layout , but that's...
2009-06-02 07:50:50 UTC in Java Unified Expression Language
-
It would be nice if the artifacts (juel-impl.jar and juel.jar) are available as valid bundles, so that they can be used out of the box within in an OSGi environment. This can be done very easily by using the Felix-Maven-Plugin (http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html). I could post a diff for the pom if you like.
Greetings from Munich.
2009-05-28 05:51:25 UTC in Java Unified Expression Language
