Download JAR files tagged by compile with all dependencies

Apache Empire-db is an Open Source relational data persistence component which allows database vendor independent dynamic query definition as well as safe and simple data retrieval and updating. Compared to most other solutions like e.g. Hibernate, TopLink, iBATIS or JPA implementations, Empire-db takes a considerably different approach, with a special focus on compile-time safety, reduced redundancies and improved developer productivity.

--------------------------------------------------------------------------- Version for VIVO 1.9 This uses the source and test code from the Version for VIVO 1.10, edited to make it compatible with VIVO 1.9. It also borrows some code from VIVO 1.10 itself, changes the package name to avoid conflicts, and adds it here. * Vitro 1.9 uses Jena 2, not Jena 3, and Commons Lang 2, not 3, so modify the "import" statements in the Data Distribution code accordingly. * Vitro 1.9 has an earlier version of "...webapp.utils.sparqlrunner" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this sparqlrunner package. * Vitro 1.9 has an earlier version of "...webapp.utils.configuration" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this configuration package. Make these modifications, compile, JAR it up, and deploy. ---------------------------------------------------------------------------

配置监控信息，在web.xml中添加 <filter> <description>拦截获取js与css过滤</description> <filter-name>MergeFilter</filter-name> <filter-class>com.njzxw.filter.MergeFilter</filter-class> <init-param> <!-- js合并输出路径 --> <param-name>jsDir</param-name> <param-value>${js.path}</param-value> </init-param> <init-param> <!-- css合并输出路径 --> <param-name>cssDir</param-name> <param-value>${css.path}</param-value> </init-param> </filter> 同时添加一个合并js\css对应一个merge.xml，最好放置在同级，如： <merge> <group name="sss" > <js path="js/common/common.js" /> <js path="js/common/index.js" /> <css path="css/common/animate.css" /> <css path="css/common/normalize.css" /> </group> </merge> 访问项目：xxx/sss.js xxx/sss.css 同时配合maven插件： compress-maven-plugin结合使用： <plugin> <groupId>com.github.eliayng</groupId> <artifactId>compress-maven-plugin</artifactId> <version>1.0.0</version> <executions> <execution> <phase>compile</phase> <goals> <goal>compress</goal> </goals> </execution> </executions> <configuration> <skip>${skipCompress}</skip> <poolNum>50</poolNum> <jsOutDir>${jsOutDir}</jsOutDir> <cssOutDir>${cssOutDir}</cssOutDir> <!--是否监控编译class文件--> <isCompressClass>true</isCompressClass> <!-- 是否复制资源文件 --> <isResourcesCopy>true</isResourcesCopy> </configuration> </plugin>

This component may be plugged into standard compile plugin of maven to compile JavaFX ( http://javafx.com/) sources. The component assumes that JavaFX SDK 1.2+ is installed on the machine were built process is run. Environment variable JFX_HOME should point to JavaFX installation directory (typically /usr/share/javafx-sdk1.2 for Linux machines). Version 0.3 is current one and is stable. Version 0.2 has deffect and compiles only basic code samples in all other cases it simply fail.

--------------------------------------------------------------------------- Version for VIVO 1.8 This uses the source and test code from the Version for VIVO 1.10, edited to make it compatible with VIVO 1.8. It also borrows some code from VIVO 1.10 itself, changes the package name to avoid conflicts, and adds it here. * Vitro 1.8 uses Jena 2, not Jena 3, and Commons Lang 2, not 3, so modify the "import" statements in the Data Distribution code accordingly. * Vitro 1.8 does not have a "...webapp.utils.sparqlrunner" package, so borrow the source from Vitro 1.10, move it to a different package (just for compatibility with the 1.9 version), modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this sparqlrunner package. * Vitro 1.9 has an earlier version of "...webapp.utils.configuration" package, so borrow the source from Vitro 1.10, move it to a different package so it won't conflict with the 1.9 version, modify it to use Jena 2 and Commons Lang 2, and modify the Data Distribution API code to use this configuration package. Make these modifications, compile, JAR it up, and deploy. --------------------------------------------------------------------------- Because VIVO 1.8 is not available as a Maven package, we have extracted the class files, JARed them up, and stored them in a file-based repository within this project. But that doesn't include any transitive dependencies, so any package that this code requires must be explicitly listed as a dependency. ---------------------------------------------------------------------------

All Gwt jre emulation code goes in this module, as well as any gwt-compiler overrides. xapi-gwt-api.jar must come before gwt-dev.jar on your compile classpath. A plugin is being built to automatically adjust maven runtime dependencies, but users of ant or IDEs will need to ensure the super jar comes before gwt-dev. We will petition gwt to accept our mods, but, until then, if you want bleeding edge features, you gotta do bleeding edge configuration. Code that ties directly into other modules, like java.lang.reflect for the reflection submodule, have their super-source here, and generators or other implementations in their own modules. This is to maintain consistency in what is or isn't whitelisted in XApi GWT. Some modules, like appengine, provide dependency-specific super-source in their own packages. This module is for jre, junit and core XApi services.