From: n.hoffmann Date: Mon, 15 Nov 2010 16:00:58 +0000 (+0000) Subject: added some site content X-Git-Tag: rcp.ss-first-working-version~254 X-Git-Url: https://dev.e-taxonomy.eu/gitweb/taxeditor.git/commitdiff_plain/00ae55e51c7fa4bbb0b5378eef9a907a980801c6 added some site content --- diff --git a/.gitattributes b/.gitattributes index 286ee2e3c..641224c7f 100644 --- a/.gitattributes +++ b/.gitattributes @@ -5,10 +5,13 @@ src/changes/changes.xml -text src/site/apt/download.apt -text src/site/apt/getting-started.apt -text src/site/apt/index.apt -text +src/site/apt/manual.apt -text src/site/apt/modules.apt -text src/site/apt/screenshots.apt -text src/site/fml/faq.fml -text src/site/fml/troubleshooting.fml -text +src/site/resources/css/site.css -text +src/site/resources/images/taxeditor_transformed.png -text src/site/site.xml -text taxeditor-annotatedlineeditor/META-INF/MANIFEST.MF -text taxeditor-annotatedlineeditor/build.properties -text diff --git a/pom.xml b/pom.xml index 621fda0a2..f04ee0c33 100644 --- a/pom.xml +++ b/pom.xml @@ -11,9 +11,10 @@ pom UTF-8 - 2.5 + 3.0 + taxeditor-cdmlib taxeditor-store taxeditor-navigation taxeditor-editor diff --git a/src/site/apt/getting-started.apt b/src/site/apt/getting-started.apt index eaffe2a66..93fccca54 100644 --- a/src/site/apt/getting-started.apt +++ b/src/site/apt/getting-started.apt @@ -16,11 +16,7 @@ Setting up a Taxonomic Editor development environment * Requirements - Please make sure that you have met the following requirements. - - * CDM Library development environment set up on your machine (please follow the instructions on {{{http://wp5.e-taxonomy.eu/cdmlib/getting-started.html#Developing_the_CDM_Library}how to install a CDM Library development environment}}) - - * Eclipse PDE Version >= 3.6 + The current version of the EDIT Taxonomic Editor is developed against Eclipse PDE Version 3.6. Your PDE or at least your target platform have to have the same version. * Checking out the sources @@ -54,24 +50,7 @@ $ mvn eclipse:eclipse * Click in the dialog and confirm. After a rebuild of your entire workspace all errors should be gone and you are ready to go. + The package exporer should show a bunch of projects. To get rid of the errors, you have to update the classpaths of all plugin projects. To do this right-click any of the projects and choose Update Classpath...>. Click