Author: taylor
Date: Tue Nov 28 14:54:23 2006
New Revision: 480261

URL: http://svn.apache.org/viewvc?view=rev&rev=480261
Log:
starting on some eclipse docs

Added:
    portals/jetspeed-2/trunk/xdocs/jetspeed-eclipse.xml
Modified:
    portals/jetspeed-2/trunk/xdocs/getting-started-binary.xml

Modified: portals/jetspeed-2/trunk/xdocs/getting-started-binary.xml
URL: 
http://svn.apache.org/viewvc/portals/jetspeed-2/trunk/xdocs/getting-started-binary.xml?view=diff&rev=480261&r1=480260&r2=480261
==============================================================================
--- portals/jetspeed-2/trunk/xdocs/getting-started-binary.xml (original)
+++ portals/jetspeed-2/trunk/xdocs/getting-started-binary.xml Tue Nov 28 
14:54:23 2006
@@ -232,7 +232,7 @@
                                If you want to setup a Jetspeed portal 
application using
                                Eclipse as your IDE, you should continue 
reading this
                                page for background material but refer to
-                               <a href="Portal-Development-with-Eclipse.html">
+                               <a href="jetspeed-eclipse.html">
                                        Building a Jetspeed Enterprise Portal 
with Eclipse
                                </a>
                                for the actual instructions on using Eclipse for

Added: portals/jetspeed-2/trunk/xdocs/jetspeed-eclipse.xml
URL: 
http://svn.apache.org/viewvc/portals/jetspeed-2/trunk/xdocs/jetspeed-eclipse.xml?view=auto&rev=480261
==============================================================================
--- portals/jetspeed-2/trunk/xdocs/jetspeed-eclipse.xml (added)
+++ portals/jetspeed-2/trunk/xdocs/jetspeed-eclipse.xml Tue Nov 28 14:54:23 2006
@@ -0,0 +1,63 @@
+<?xml version="1.0"?>
+<!--
+       Copyright 2004 The Apache Software Foundation
+       
+       Licensed 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.
+-->
+<document>
+       <properties>
+               <title>
+                       Developing Jetspeed with Eclipse
+               </title>
+               <subtitle>How-to for Building and Debugging Jetspeed with 
Eclipse</subtitle>
+               <authors>
+                       <person name="David Sean Taylor" email="[EMAIL 
PROTECTED]" />
+               </authors>
+       </properties>
+       <body>
+               <section name="Developing with Eclipse">
+                       <subsection name="The Eclipse Classpath">
+            <p>
+                Compiling, debugging, external dependencies, source code 
completion, searching, auto imports, all rely on a properly configured 
classpath. 
+                When you first create a project, a .classpath file is created 
in the projects root directory. 
+                With the Jetspeed source, we provide you with a ready-to-use 
Eclipse .classpath file.
+                We have already configured the relative source directories for 
you.
+                Eclipse provides a .classpath GUI editor from the 
Project->Properties menu option. 
+            </p>
+                       </subsection>
+                       <subsection name="JAR files and the Maven repository">
+                               <p>
+                  Jetspeed requires quite a few JAR files to be able to 
compile.
+                  The .classpath file that comes with Jetspeed is setup to get 
its JAR files out of a local Maven repository.
+                  You can see all the JAR file dependencies from Eclipse. Go 
to Project->Properties->Java Build Path->Libraries.
+                  Notice all the JAR files are configured as VARIABLE library 
entries.
+                  Take one example: 
+                                       <source>
+                    MAVEN_REPO/commons-lang/jars/commons-lang-2.0.jar          
                  
+                                       </source>                    
+                  The Variable is portion is MAVEN_REPO.
+                  The Extension portion is 
/commons-lang/jars/commons-lang-2.0.jar
+                  Eclipse locates the JAR dependency from a Variable location 
root.
+                  In order for this classpath to work correctly, the variable 
root is dependent on a Maven-1 local repository file structure.
+                               </p>
+                               <p>
+                    To configure the MAVEN_REPO variable, go to 
Window->Preferences->Java->Build Path->Classpath Variables,
+                    click on New, and define a new variable named MAVEN_REPO, 
pointing it out the root of your local Maven-1 repository,
+                    usually someplace like your $$HOME/.maven/repository
+                               </p>
+                       </subsection>
+               </section>
+               <section name="Debugging with Eclipse">
+        </section>
+       </body>
+</document>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to