-
Migrating the Ant-based BaseX build system to maven has a lot of advantages: BaseX dependencies (such as JUnit or XQJ) do no longer need to be placed into the Subversion repository, their management is simplified to a mere declaration in the project file. Maven plugins exist for generating Eclipse and IDEA projects, and the NetBeans IDE can even handle Maven projects natively. As a consequence...
2010-01-03 21:53:28 UTC in BaseX
-
The XQJ classes are part of the BaseX source tree and are consequently compiled and packaged with the rest of the BaseX classes. However, this can cause problems in applications developed against the XQJ classes, since these applications typically deploy them as a dependency. As a result, the XQJ classes will be present twice: on the one hand those compiled and packaged with BaseX and on the...
2010-01-03 21:43:39 UTC in BaseX
-
The XQJ API should not be part of the eXist source base, because it is an ordinary dependency that can be downloaded from the JCP website at http://jcp.org/aboutJava/communityprocess/final/jsr225/index.html. Having the XQJ classes delivered as part of the eXist binary causes trouble in environments with several class loaders, such as OSGi and NetBeans RCP. There, the XQJ API will be a separate...
2009-12-16 13:01:42 UTC in eXist
-
Ever since eXist has been migrated to Java 5 there is no need to provide the source for javax.xml.namespace.NamespaceContext, because it is included in the Java runtime. The attached patch against trunk removes this class from the source tree.
2009-12-16 10:43:42 UTC in eXist
