finally beat it ! :). Note for later : don't do eclipse bigs renaming when svn offline. git-svn-id: https://svn.apache.org/repos/asf/incubator/stanbol/branches/cameltrial@1351537 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/DISCLAIMER b/DISCLAIMER deleted file mode 100644 index a9a4729..0000000 --- a/DISCLAIMER +++ /dev/null
@@ -1,6 +0,0 @@ -Apache Stanbol is an effort undergoing incubation at The Apache Software Foundation (ASF), -sponsored by the Incubator PMC. Incubation is required of all newly accepted projects -until a further review indicates that the infrastructure, communications, and decision -making process have stabilized in a manner consistent with other successful ASF projects. -While incubation status is not necessarily a reflection of the completeness or stability -of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
diff --git a/PLAYGROUND.txt b/PLAYGROUND.txt deleted file mode 100644 index aafd02b..0000000 --- a/PLAYGROUND.txt +++ /dev/null
@@ -1,7 +0,0 @@ -Feel free to modify and commit this file to test your commit rights. -- tommaso can play in the playground -- works for wkasper -- enridaga is here -- fchrist is able to play -- sfermigier is able to play -- cihan is able to play
diff --git a/README.md b/README.md index d474eeb..b3516aa 100644 --- a/README.md +++ b/README.md
@@ -15,166 +15,37 @@ limitations under the License. --> -# Apache Stanbol +# Building Flow endpoint -Apache Stanbol is a modular set of components and HTTP services for -semantic content management. + $ cd flow/ ; mvn clean install; + $ cd launchers/fullflow ; mvn clean install; -## Building Stanbol +# Starting Stanbol -To build Stanbol you need a JDK 1.6 and Maven 2.2.1 installed. You probably -need + $ cd flow/fullflow/target ; java -jar org.apache.stanbol.launchers.fullflow-0.9.0-incubating.jar; - $ export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M" +# Testing Flow : -The Stanbol build system consists of the following profiles: +## Pool flow feature - - 'stack' - to build the Stanbol Stack - - 'framework' - to build the Stanbol Framework only - - 'kres' - to build additional Reasoning components that - are not yet in a stable state +By default a file endpoint will fetch all files in /tmp/chaininput folder, process it with the langId engine and then write the xml-rdf result in /tmp/chainoutput folder. -If you build Stanbol from a source tree that contains the whole Stanbol -project, the 'stack' profile is activated by default. If you whish to activate -another profile use the Maven -P command line switch. +## On demand flow feature -If you build Stanbol from a source tree that just contains the Stanbol -Framework, e.g. after downloading a Stanbol Framework source release, the -'framework' profile will be activated by default. +The flow endpoint offer sub-ressource that allow you to directly call some predefined particular flow. -If you want to skip the tests for any build profile, add `-DskipTests` to the -Maven command. +Template for this request is : + $ curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" --data "Here comes a little test with Paris as content and also Berlin but why not detect city as Boston and some well know people like Bob Marley." http://localhost:8080/flow/{{flowName}} -## Building the Stanbol Stack +Where {{flowName}} can have the values : -This builds the Stanbol Framework plus available Enhancement Engines and a -default set of linked open data for the EntityHub. If you want to have a ready -to use version of Stanbol, this is the way to go. + - default : default chain : all registred engines sorted by weight + - tika : only call tika engine, no visible result (as the engine don't create enhancements) + - tika2 : tika then langID then NER then save the result in /tmp/chainoutput folder + - tika-default : tika then default flow -In the Stanbol source directory type +Flow/Route definition for default can be find here : https://svn.apache.org/repos/asf/incubator/stanbol/branches/cameltrial/flow/weightedgraphflow/src/main/java/org/apache/stanbol/flow/weightedgraphflow/WeightedChain.java - $ mvn install - -### Launching the Stanbol server - -The recommended lanchers are packaged under the `launchers/` folder. For -instance: - - $ java -Xmx1g -jar launchers/full/target/org.apache.stanbol.launchers.full-0.9.0-incubating-SNAPSHOT.jar - -Your instance is then available on <http://localhost:8080>. You can change the -default port number by passing a `-p 9090` options to the commandline launcher. - -Upon first startup, a folder named `sling/` is created in the current folder. -This folder will hold the files for any database used by Stanbol, deployment -configuration and logs. - -If Stanbol is launched with a FactStore a folder named `factstore` is created -in the current folder. This folder holds the FactStore database (Apache Derby). - - -## Building the Stanbol Framework only - -This build is used to build the Stanbol Framework only. That is without any -Enhancement Engines or prepared linked open data indexes for the EntityHub. - -In the Stanbol source directory type - - $ mvn install -Pframework - -If you build Stanbol from a source tree that just contains the Stanbol -Framework, e.g. after downloading a Stanbol Framework source release, the -'framework' is activated automatically and it is enough to type - - $ mvn install - - -## Preloading the Entity Hub cache with a DBpedia index - -TODO: write me! - - -## Importing the source code as Eclipse projects - -Eclipse is the most popular IDE among Stanbol developers. Here are -instructions to get you started with this IDE. For other IDEs / editors, -please refer to their documentation and maven integration plugins. - -To generate the Eclipse project definition files, go to Stanbol source -directory and type: - - $ mvn eclipse:eclipse - -If you want to recreate already existing Eclipse projects, you have to delete -the old ones first by using `eclipse:clean`. - -Then in Eclipse, right click on the `Project Explorer` panel and select -your source folder from the following menu / import wizard: - - > Import... > General > Import Existing Projects into Workspace - -You will also need to setup the build path variable `M2_REPO` pointing to -`~/.m2/repository` (where `~` stands for the path to your home folder). To set -up this variable go to: - - > Window > Preferences > Java > Build Path > Classpath Variables > New... - -If you plan to contribute patches to the project, please ensure that your style -follow the official sun java guidelines with 4 space indents (no tabs). To -ensure that your files follow the guidelines you can import the formatter -definitions avaiable in the `conventions/` folder: - - > Window > Preferences > Java > Code Style > Formatter > Import... - -You can then apply the formatter to a selected area of a Java source code files -by pressing `Shift+Ctrl+F`. - - -## Debugging a Stanbol instance from Eclipse - -To debug a locally running Stanbol instance from eclipse, run the stanbol -launcher with:: - - $ java -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ - -jar org.apache.stanbol.some.launcher.0.9-SNAPSHOT.jar -p 8080 - -In eclipse, you can then create a new "Debug Configuration" with type "Remote -Java Application" and connect it to localhost on port 8787. - -## License check via the Apache's Release Audit Tool (RAT) - -To check for license headers within the source code Stanbol uses the RAT Maven -plugin [1]. You can activate a 'rat:check' by using the 'rat' Maven profile. - -For example to check the licenses in the Stanbol Framework use - - $ mvn install -Prat - -## Release Apache Stanbol - -You should read [1,2] before doing any release related actions. - -To do a release test build, you have to activate the 'apache-release' profile. -For building the framework plus signing the artifacts as it would be done during -a release you can use - - $ mvn install -Pframework,apache-release - -The 'apache-release' profile will be automatically activated when the Maven -release plugin [3] is used. For doing official release you start with - - $ mvn release:prepare - -[1] http://www.apache.org/dev/#releases -[2] http://incubator.apache.org/guides/releasemanagement.html -[3] http://maven.apache.org/plugins/maven-release-plugin/ - -## Useful links - - - Documentation will be published and mailing lists info on [the official - Stanbol page](http://incubator.apache.org/stanbol/) - - - Please report bugs on the [Apache issue tracker]( - https://issues.apache.org/jira/browse/STANBOL) +Others Flow/routes definition resides here : https://svn.apache.org/repos/asf/incubator/stanbol/branches/cameltrial/flow/filepoolgraphflow/src/main/java/org/apache/stanbol/flow/filepoolgraphflow/FileRoute.java
diff --git a/flow/bundlelist/src/main/bundles/list.xml b/flow/bundlelist/src/main/bundles/list.xml index 354ca8e..e52d4b2 100644 --- a/flow/bundlelist/src/main/bundles/list.xml +++ b/flow/bundlelist/src/main/bundles/list.xml
@@ -11,7 +11,7 @@ language governing permissions and limitations under the License. --> <bundles> - <!-- Stanbol Chain job manager required libs --> + <!-- Stanbol Chain infrastructure and required libraries --> <startLevel level="20"> <!-- Camel dependencies --> @@ -35,90 +35,29 @@ <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.servicesapi</artifactId> + <artifactId>org.apache.stanbol.flow.servicesapi</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> </bundle> - <!-- <bundle> <groupId>org.apache.stanbol</groupId> <artifactId>org.apache.stanbol.entityhub.site.linkeddata</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> </bundle> <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.entityhub.yard.clerezza</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> <bundle> <groupId>org.apache.stanbol</groupId> <artifactId>org.apache.stanbol.entityhub.yard.solr</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> </bundle> <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.entityhub.core</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> --> + </startLevel> <!-- Web Fragment --> <startLevel level="21"> <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.jersey</artifactId> + <artifactId>org.apache.stanbol.flow.web</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> </bundle> </startLevel> <!-- Benchmarks for the Stanbol Enhancer --> <startLevel level="21"> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.benchmark</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> + </startLevel> <!-- Stanbol Enhancer plug-ins (the Enhancement Engines) --> <startLevel level="25"> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engines.langid</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engines.metaxa</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engines.opencalais</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engines.zemanta</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engines.opennlp.ner</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <!-- - The geonames.org LocationEnhancement Engines needs two additional bundles 1) jettyjson 2) commons-io. - Both of them are already present in the bundle list. - --> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engines.geonames</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <!-- Entity Tagging Engine (depends on the Entityhub) --> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engine.entitytagging</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> - <!-- Taxonomy Linking Engine (depends on the Entityhub) Deprecated - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engine.taxonomy</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> --> - <!-- Keyword Extraction Engine (depends on the Entityhub) --> - <bundle> - <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.engine.keywordextraction</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - </bundle> + </startLevel> <!-- StartLevel for the chainjobmanager : after engines (level 25 to 26) @@ -126,8 +65,7 @@ <startLevel level="28"> <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.jobmanager.chainjobmanager - </artifactId> + <artifactId>org.apache.stanbol.flow.cameljobmanager</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> </bundle> </startLevel> @@ -137,14 +75,12 @@ <!-- filepool chain to activate after --> <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.jobmanager.chainjobmanager.filepoolchain - </artifactId> + <artifactId>org.apache.stanbol.flow.filepoolgraphflow</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> </bundle> <bundle> <groupId>org.apache.stanbol</groupId> - <artifactId>org.apache.stanbol.enhancer.jobmanager.chainjobmanager.weightedchain - </artifactId> + <artifactId>org.apache.stanbol.flow.weightedgraphflow</artifactId> <version>0.9.0-incubating-SNAPSHOT</version> </bundle> </startLevel>
diff --git a/pom.xml b/pom.xml deleted file mode 100644 index f469215..0000000 --- a/pom.xml +++ /dev/null
@@ -1,209 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!-- - Licensed to the Apache Software Foundation (ASF) under one or more - contributor license agreements. See the NOTICE file distributed with - this work for additional information regarding copyright ownership. - The ASF licenses this file to You under the Apache License, Version 2.0 - (the "License"); you may not use this file except in compliance with - the License. You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. ---> -<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> - - <modelVersion>4.0.0</modelVersion> - <parent> - <groupId>org.apache.stanbol</groupId> - <artifactId>stanbol-parent</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - <relativePath>parent</relativePath> - </parent> - - <groupId>org.apache.stanbol</groupId> - <artifactId>stanbol-reactor</artifactId> - <version>0.9.0-incubating-SNAPSHOT</version> - <packaging>pom</packaging> - - <name>Apache Stanbol Reactor</name> - <description> - Pseudo project to build the complete stanbol project - </description> - - <inceptionYear>2010</inceptionYear> - - <scm> - <connection> - scm:svn:http://svn.apache.org/repos/asf/incubator/stanbol/trunk/ - </connection> - <developerConnection> - scm:svn:https://svn.apache.org/repos/asf/incubator/stanbol/trunk/ - </developerConnection> - <url>http://incubator.apache.org/stanbol/</url> - </scm> - - <!-- These modules form the Stanbol Framework --> - <modules> - <module>parent</module> - <module>commons</module> - <module>data</module> - <module>frameworkfragment</module> - - <module>enhancer/parent</module> - <module>enhancer/generic/servicesapi</module> - <module>enhancer/jobmanager</module> - <module>enhancer/jersey</module> - <module>enhancer/benchmark</module> - <module>enhancer/bundlelist</module> - - <module>cmsadapter</module> - <module>contenthub</module> - <module>entityhub</module> - <module>factstore</module> - - <module>ontologymanager/ontonet</module> - <module>ontologymanager/registry</module> - <module>ontologymanager/web</module> - <module>ontologymanager/bundlelist</module> - <module>owl</module> - <module>rules</module> - </modules> - - <profiles> - <profile> - <id>stack</id> - <activation> - <activeByDefault>true</activeByDefault> - </activation> - <properties> - <sourceReleaseAssemblyDescriptor> - stack-source-release-zip-tar - </sourceReleaseAssemblyDescriptor> - </properties> - <build> - <finalName>stanbol-stack-${project.version}</finalName> - </build> - <modules> - <module>commons/web/webvie</module> - - <module>enhancer/engines</module> - - <module>launchers/bundlelists/osgiframework</module> - <module>launchers/bundlelists/stanbolcommons</module> - <module>launchers/stable</module> - <module>launchers/stateless</module> - <module>launchers/full</module> - <module>launchers/full-war</module> - <module>integration-tests</module> - </modules> - </profile> - <profile> - <id>framework</id> - <activation> - <activeByDefault>false</activeByDefault> - <!-- The framework profile is activated automatically if the - full launcher is missing. This is used for framework releases - where the full launcher is not packaged. --> - <file> - <missing>launchers/full</missing> - </file> - </activation> - <properties> - <sourceReleaseAssemblyDescriptor> - framework-source-release-zip-tar - </sourceReleaseAssemblyDescriptor> - </properties> - <build> - <finalName>stanbol-framework-${project.version}</finalName> - </build> - <modules> - <module>launchers/framework</module> - </modules> - </profile> - <profile> - <id>rat</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.apache.rat</groupId> - <artifactId>apache-rat-plugin</artifactId> - <configuration> - <excludeSubProjects>false</excludeSubProjects> - <excludes> - <!-- AL20 files without header by file type --> - <exclude>**/*.config</exclude> - <exclude>**/*.cfg</exclude> - <exclude>**/*.ref</exclude> - <exclude>**/*.txt</exclude> - <exclude>**/*.tsv</exclude> - <exclude>**/*.sem</exclude> - <exclude>**/test/**/*.eml</exclude> - <exclude>**/test/**/*.nt</exclude> - - <!-- approved licenses, see modules' POMs for details --> - <exclude>contenthub/web/src/main/resources/org/apache/stanbol/contenthub/web/static/scripts/jit.js</exclude> - <exclude>enhancer/jersey/src/main/resources/org/apache/stanbol/enhancer/jersey/static/openlayers-2.9/**</exclude> - <exclude>owl/**</exclude> - - <!-- unstable and not release relevant stuff --> - <exclude>PLAYGROUND.txt</exclude> - <exclude>conventions/**</exclude> - <exclude>enhancer/data/text-examples/**</exclude> - <exclude>enhancer/query-rendering/**</exclude> - <exclude>enhancer/stores/**</exclude> - <exclude>explanation/**</exclude> - <exclude>demos/**</exclude> - <exclude>launchers/kres/**</exclude> - <exclude>reasoners/**</exclude> - <exclude>reengineer/**</exclude> - - <!-- exclude hidden files --> - <exclude>**/.*</exclude> - <exclude>**/.*/*</exclude> - <exclude>**/.*/**/*</exclude> - - <!-- exclude generated files --> - <exclude>*/**/target/**</exclude> - </excludes> - </configuration> - </plugin> - </plugins> - </build> - </profile> - <profile> - <id>apache-release</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <modules> - <module>releasing/framework/stanbol-framework-source-release-assembly-descriptor</module> - <module>releasing/stack/stanbol-stack-source-release-assembly-descriptor</module> - </modules> - </profile> - - <!-- One day the KReS profile will disappear --> - <profile> - <id>kres</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <modules> - <module>ontologymanager/store</module> - <module>reasoners</module> - <module>reengineer</module> - <module>explanation</module> - <module>launchers/kres</module> - </modules> - </profile> - </profiles> - -</project>