[CONF] Apache Tapestry > Loading the Project Into Eclipse

2011-11-22 Thread confluence







Loading the Project Into Eclipse
Page edited by Howard M. Lewis Ship


Comment:
Update for 5.3 and newer version of RunJettyRun


 Changes (7)
 




...
!eclipse-launch.png|thumbnail!  
Make sure you clear the field labeled *HTTPS*. 
You will need to click the "Show advanced Options" checkbox, then uncheck "SSL" and "Enable Scanner".   
 
You can then click *Run* and Jetty will launch (it takes only a few seconds): 
Tapestry runs best with a couple of additional options; click the "Arguments" tab and enter the following VM Arguments: {{-XX:MaxPermSize=256M -Xmx600m -Dtapestry.execution-mode=development}} 
 
Once you click Run, Jetty will start up and launch (it should take about two seconds). 
!eclipse-launch-vmargs.png|thumbnail! 
 
Tapestry uses more PermGen space (the part of Java memory used for loading classes) than a typical application, and uses more heap memory than the default; the above settings are good for a medium-to-large size Tapestry application, and will keep Java from running the Garbage Collector too often. The setting of tapestry.execution mode tells Tapestry to run in development mode, where runtime exceptions are reported more exhaustively.  With those settings in place, you can then click *Run* and Jetty will launch (it takes only a few seconds):  Once you click Run, Jetty will start up and launch (it should take a second or two).  
!eclipse-jetty.png|thumbnail!  
...


Full Content

Creating The Skeleton Application Tapestry Tutorial Exploring the Project

The first step is to ask Maven to generate the Eclipse control files (.classpath and .project) for us:


$ mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1.1/maven-war-plugin-2.1.1.pom
Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1.1/maven-war-plugin-2.1.1.pom (7 KB at 7.1 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1.1/maven-war-plugin-2.1.1.jar
Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.1.1/maven-war-plugin-2.1.1.jar (76 KB at 83.4 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml
Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml (680 B at 1.9 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/2.8/maven-eclipse-plugin-2.8.pom
Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/2.8/maven-eclipse-plugin-2.8.pom (12 KB at 22.9 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/17/maven-plugins-17.pom
Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/17/maven-plugins-17.pom (13 KB at 25.6 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/2.8/maven-eclipse-plugin-2.8.jar
Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/2.8/maven-eclipse-plugin-2.8.jar (202 KB at 237.8 KB/sec)
[INFO] 
[INFO] 
[INFO] Building tutorial1 Tapestry 5 Application 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ tutorial1 >>>
[INFO] 
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ tutorial1 <<<
[INFO] 
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ tutorial1 ---
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.pom
Downloaded: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.pom (2 KB at 2.3 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.6/plexus-components-1.1.6.pom
Downloaded: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-components/1.1.6/plexus-components-1.1.6.pom (2 KB at 3.7 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.2/plexus-utils-1.2.pom
Downloaded: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.2/plexus-utils-1.2.pom (767 B at 1.5 KB/sec)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.5/plexus-1.0.5.pom
Downloaded: http:/

[CONF] Apache Tapestry > Loading the Project Into Eclipse

2011-11-22 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-jetty.png
(139 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2011-11-22 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-launch-vmargs.png
(70 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2011-11-22 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-launch.png
(95 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-12-06 Thread confluence







Loading the Project Into Eclipse
Page edited by Howard M. Lewis Ship


 Changes (3)
 



...
{noformat}  
At this point, Maven has created the Eclipse {{.project}} and {{.classpath}} files, and we can import the project. In addition, since we specified {{-DdownloadSources}}, it has downloaded the sources to Tapestry and its dependencies and linked the library JAR files to those source JARs; that means we can see the sources for any Tapestry classes right into Eclipse, which is very useful when debugging or exploring. 
At this point, Maven has created the Eclipse {{.project}} and {{.classpath}} files, and we can import the project. In addition, since we specified {{-DdownloadSources=true}}, Maven has also downloaded the sources of each library and linked to the source JAR; that means we can see the sources for any Tapestry classes right inside Eclipse, which is very useful when debugging or exploring. 
 
At this point, we are ready to import the project created by Maven into Eclipse so we can start working with it. Launch Eclipse and switch over to the Java Perspective. 
 Right click inside the Package Explorer view and select *Import ...*  
!eclipse-java-persp.png|thumbnail!  
Choose the "existing projects" option:  
...
When you click the Finish button, the project will be imported into the Eclipse workspace.  
!eclipse-project-errors.png|thumbnail!  
...

Full Content

Creating The Skeleton Application Tapestry Tutorial Exploring the Project

The first step is to ask Maven to generate the Eclipse control files (.classpath and .project) for us:


$ mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] org.apache.maven.plugins: checking for updates from apache-snapshots
[INFO] org.codehaus.mojo: checking for updates from apache-snapshots
[INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from apache-snapshots
[INFO] snapshot org.apache.maven.plugins:maven-eclipse-plugin:2.9-SNAPSHOT: checking for updates from apache-snapshots
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.pom
11K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.pom)
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.jar
194K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.jar)
[INFO] 
[INFO] Building tutorial1 Tapestry 5 Application
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse {execution: default-cli}]
[INFO] Using Eclipse Workspace: /Users/Howard/Documents/workspace
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /Users/Howard/Documents/workspace/tutorial1/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "tutorial1" to /Users/Howard/Documents/workspace/tutorial1.
[INFO] 
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 5 seconds
[INFO] Finished at: Wed Nov 17 17:13:11 PST 2010
[INFO] Final Memory: 21M/81M
[INFO] 
~/Documents/workspace/tutorial1
$ 



At this point, Maven has created the Eclipse .project and .classpath files, and we can import the project. In addition, since we specified -DdownloadSources=true, Maven has also downloaded the sources of each library and linked to the source JAR; that means we can see the sources for any Tapestry classes right inside Eclipse, which is very useful when debugging or exploring.

At this point, we are ready to import the project created by Maven into Eclipse so we can start working with it. Launch Eclipse and switch over to the Java Perspective.

Right click inside the Package Explorer view and select Import ...



Choose the "existing projects" option:



Now select the folder created by Maven:



When you click the Finish button, the project will be imported into the Eclipse workspace.



However; there are many errors.  Maven expects that you will configure a classpath variable, M2_REPO, that points at your local repository; a directory in your home directory that stor

[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-12-06 Thread confluence







Loading the Project Into Eclipse
Page edited by Howard M. Lewis Ship


 Changes (10)
 



...
{noformat}  
At this point, Maven has created the Eclipse {{.project}} and {{.classpath}} files, and we can import the project. In addition, since we specified {{-DdownloadSources}}, it has downloaded the sources to Tapestry and its dependencies and linked the library JAR files to those source JARs; that means we can see the sources for any Tapestry classes right into Eclipse, which is very useful when debugging or exploring. 
 Launch Eclipse and switch over to the Java Perspective. 
...
  
!eclipse-java-persp.png|align=center,thumbnail! !eclipse-java-persp.png|thumbnail! 
  Choose the "existing projects" option:  
!eclipse-import.png|align=center,thumbnail! !eclipse-import.png|thumbnail! 
 Now select the folder created by Maven:  
!eclipse-import-folder.png|align=center,thumbnail! !eclipse-import-folder.png|thumbnail! 
 When you click the Finish button, the project will be imported into the Eclipse workspace.   
!eclipse-project-errors.png|align=center,thumbnail! !eclipse-project-errors.png|thumbnail! 
 However; there are many errors.  Maven expects that you will configure a classpath variable, {{M2_REPO}}, that points at your local repository; a directory in your home directory that stores all those downloaded JARs and other files.  Open Eclipse's preferences panel and navigate to *Java > Build Path > Classpath Variables*:  
!eclipse-classpath-vars.png|align=center,thumbnail! !eclipse-classpath-vars.png|thumbnail! 
 Click the *New* button, and enter the new variable (you'll have to adjust this for your operating system and local paths):  
!eclipse-new-var.png|align=center,thumbnail! !eclipse-new-var.png|thumbnail! 
 Eclipse will ask to perform a clean build, and the errors will be gone once it has done so. 
...
Choose the *Run ...* item from the Eclipse *Run* menu to get the launch configuration dialog:  
!eclipse-run.png|align=center,thumbnail! !eclipse-run.png|thumbnail! 
 Select *Jetty Webapp* and click the *New* button, then fill in a few values:  
!eclipse-launch.png|align=center,thumbnail! !eclipse-launch.png|thumbnail! 
 Make sure you clear the field labeled *HTTPS*. 
...
Once you click Run, Jetty will start up and launch (it should take about two seconds).  
!eclipse-jetty.png|align=center,thumbnail! !eclipse-jetty.png|thumbnail! 
 You may now start the application with the URL [http://localhost:8080/tutorial1/] 
...

Full Content

Creating The Skeleton Application Tapestry Tutorial Exploring the Project

The first step is to ask Maven to generate the Eclipse control files (.classpath and .project) for us:


$ mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] org.apache.maven.plugins: checking for updates from apache-snapshots
[INFO] org.codehaus.mojo: checking for updates from apache-snapshots
[INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from apache-snapshots
[INFO] snapshot org.apache.maven.plugins:maven-eclipse-plugin:2.9-SNAPSHOT: checking for updates from apache-snapshots
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.pom
11K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.pom)
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.jar
194K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.jar)
[INFO] 
[INFO] Building tutorial1 Tapestry 5 Application
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse {execution: default-cli}]
[INFO] Using Eclipse Workspace: /Users/Howard/Documents/workspace
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /Users/Howard/Documents/workspace/tutorial1/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "tutorial1" to /Users/Howard/Documents/workspace/tutorial1.
[INFO] 
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 

[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-12-01 Thread confluence







Loading the Project Into Eclipse
Page edited by Howard M. Lewis Ship


 Changes (2)
 



{tutorialnav} {scrollbar} 
 The first step is to ask Maven to generate the Eclipse control files ({{.classpath}} and {{.project}}) for us: 
...
 You may now start the application with the URL [http://localhost:8080/tutorial1/] 
{tutorialnav} {scrollbar} 

Full Content

Creating The Skeleton Application Tapestry Tutorial Exploring the Project

The first step is to ask Maven to generate the Eclipse control files (.classpath and .project) for us:


$ mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] org.apache.maven.plugins: checking for updates from apache-snapshots
[INFO] org.codehaus.mojo: checking for updates from apache-snapshots
[INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from apache-snapshots
[INFO] snapshot org.apache.maven.plugins:maven-eclipse-plugin:2.9-SNAPSHOT: checking for updates from apache-snapshots
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.pom
11K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.pom)
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.jar
194K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.jar)
[INFO] 
[INFO] Building tutorial1 Tapestry 5 Application
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse {execution: default-cli}]
[INFO] Using Eclipse Workspace: /Users/Howard/Documents/workspace
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /Users/Howard/Documents/workspace/tutorial1/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "tutorial1" to /Users/Howard/Documents/workspace/tutorial1.
[INFO] 
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 5 seconds
[INFO] Finished at: Wed Nov 17 17:13:11 PST 2010
[INFO] Final Memory: 21M/81M
[INFO] 
~/Documents/workspace/tutorial1
$ 



At this point, Maven has created the Eclipse .project and .classpath files, and we can import the project.

Launch Eclipse and switch over to the Java Perspective.

Right click inside the Package Explorer view and select Import ...





Choose the "existing projects" option:



Now select the folder created by Maven:



When you click the Finish button, the project will be imported into the Eclipse workspace.




However; there are many errors.  Maven expects that you will configure a classpath variable, M2_REPO, that points at your local repository; a directory in your home directory that stores all those downloaded JARs and other files.  Open Eclipse's preferences panel and navigate to Java > Build Path > Classpath Variables:



Click the New button, and enter the new variable (you'll have to adjust this for your operating system and local paths):



Eclipse will ask to perform a clean build, and the errors will be gone once it has done so.


Running the Application inside Eclipse

The task is to set up Jetty to run our application directly out of our Eclipse workspace. This is a great way to develop web applications, since we don't want to have to use Maven to compile and run the application ... or worse yet, use Maven to package and deploy the application. That's for later, when we want to put the application into production. For development, we want a fast, agile environment that can keep up with our changes, and that means we can't wait for redeploys and restarts.

Choose the Run ... item from the Eclipse Run menu to get the launch configuration dialog:



Select Jetty Webapp and click the New button, then fill in a few values:



Make sure you clear the field labeled HTTPS.

You can then click Run and Jetty will launch (it takes only a few seconds):

Once you click Run, Jetty will start up and launch (it should take about two seconds).



You may now start the application with the URL http://localhost:8080/tutorial1/
Creating The Skeleton Application Tapestry Tutorial Exploring the Project



Change Notification Preferences

 

[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-launch.png
(72 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-run.png
(57 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-jetty.png
(53 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-jetty.png
(53 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
Page edited by Howard M. Lewis Ship


 Changes (1)
 



...
  
h1. Running the Application inside Eclipse  The task is to set up Jetty to run our application directly out of our Eclipse workspace. This is a great way to develop web applications, since we don't want to have to use Maven to compile and run the application ... or worse yet, use Maven to package and deploy the application. That's for later, when we want to put the application into production. For development, we want a fast, agile environment that can keep up with our changes, and that means we can't wait for redeploys and restarts.  Choose the *Run ...* item from the Eclipse *Run* menu to get the launch configuration dialog:  !eclipse-run.png|align=center,thumbnail!  Select *Jetty Webapp* and click the *New* button, then fill in a few values:  !eclipse-launch.png|align=center,thumbnail!  Make sure you clear the field labeled *HTTPS*.  You can then click *Run* and Jetty will launch (it takes only a few seconds):  Once you click Run, Jetty will start up and launch (it should take about two seconds).  !eclipse-jetty.png|align=center,thumbnail!  You may now start the application with the URL [http://localhost:8080/tutorial1/] 
{tutorialnav} 

Full Content



Tapestry Tutorial
Dependencies, Tools and PluginsCreating The Skeleton ApplicationLoading the Project Into EclipseHiloFormsForms2





The first step is to ask Maven to generate the Eclipse control files (.classpath and .project) for us:


$ mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] org.apache.maven.plugins: checking for updates from apache-snapshots
[INFO] org.codehaus.mojo: checking for updates from apache-snapshots
[INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from apache-snapshots
[INFO] snapshot org.apache.maven.plugins:maven-eclipse-plugin:2.9-SNAPSHOT: checking for updates from apache-snapshots
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.pom
11K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.pom)
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.jar
194K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.jar)
[INFO] 
[INFO] Building tutorial1 Tapestry 5 Application
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse {execution: default-cli}]
[INFO] Using Eclipse Workspace: /Users/Howard/Documents/workspace
[INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Wrote settings to /Users/Howard/Documents/workspace/tutorial1/.settings/org.eclipse.jdt.core.prefs
[INFO] Wrote Eclipse project for "tutorial1" to /Users/Howard/Documents/workspace/tutorial1.
[INFO] 
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 5 seconds
[INFO] Finished at: Wed Nov 17 17:13:11 PST 2010
[INFO] Final Memory: 21M/81M
[INFO] 
~/Documents/workspace/tutorial1
$ 



At this point, Maven has created the Eclipse .project and .classpath files, and we can import the project.

Launch Eclipse and switch over to the Java Perspective.

Right click inside the Package Explorer view and select Import ...





Choose the "existing projects" option:



Now select the folder created by Maven:



When you click the Finish button, the project will be imported into the Eclipse workspace.




However; there are many errors.  Maven expects that you will configure a classpath variable, M2_REPO, that points at your local repository; a directory in your home directory that stores all those downloaded JARs and other files.  Open Eclipse's preferences panel and navigate to Java > Build Path > Classpath Variables:



Click the New button, and enter the new variable (you'll have to adjust this for your operating system and local paths):



Eclipse will ask to perform a clean build, and the errors will be gone once it has done so.


Running the Application inside Eclipse

The task is to set up Jetty to run our application directly out of our Eclipse workspace. This is a great way to develop web applications, since we don't 

[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-new-var.png
(14 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-java-persp.png
(77 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-import.png
(34 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-import-folder.png
(50 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-classpath-vars.png
(82 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
File attached by  Howard M. Lewis Ship




eclipse-project-errors.png
(138 kB image/png)



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
Page edited by Howard M. Lewis Ship


 Changes (2)
 



{tutorialnav} 
 
The first step is to ask Maven to generate the Eclipse control files ({{.classpath}} and {{.project}}) for us:  {noformat} $ mvn eclipse:eclipse -DdownloadSources=true [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'eclipse'. [INFO] org.apache.maven.plugins: checking for updates from apache-snapshots [INFO] org.codehaus.mojo: checking for updates from apache-snapshots [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from apache-snapshots [INFO] snapshot org.apache.maven.plugins:maven-eclipse-plugin:2.9-SNAPSHOT: checking for updates from apache-snapshots Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.pom 11K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.pom) Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.jar 194K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.jar) [INFO]  [INFO] Building tutorial1 Tapestry 5 Application [INFO]task-segment: [eclipse:eclipse] [INFO]  [INFO] Preparing eclipse:eclipse [INFO] No goals needed for project - skipping [INFO] [eclipse:eclipse {execution: default-cli}] [INFO] Using Eclipse Workspace: /Users/Howard/Documents/workspace [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER [INFO] Wrote settings to /Users/Howard/Documents/workspace/tutorial1/.settings/org.eclipse.jdt.core.prefs [INFO] Wrote Eclipse project for "tutorial1" to /Users/Howard/Documents/workspace/tutorial1. [INFO]  [INFO]  [INFO] BUILD SUCCESSFUL [INFO]  [INFO] Total time: 5 seconds [INFO] Finished at: Wed Nov 17 17:13:11 PST 2010 [INFO] Final Memory: 21M/81M [INFO]  ~/Documents/workspace/tutorial1 $  {noformat}  At this point, Maven has created the Eclipse {{.project}} and {{.classpath}} files, and we can import the project.  Launch Eclipse and switch over to the Java Perspective.  Right click inside the Package Explorer view and select *Import ...*   !eclipse-java-persp.png|align=center,thumbnail!   Choose the "existing projects" option:  !eclipse-import.png|align=center,thumbnail!  Now select the folder created by Maven:  !eclipse-import-folder.png|align=center,thumbnail!  When you click the Finish button, the project will be imported into the Eclipse workspace.   !eclipse-project-errors.png|align=center,thumbnail!  However; there are many errors.  Maven expects that you will configure a classpath variable, {{M2_REPO}}, that points at your local repository; a directory in your home directory that stores all those downloaded JARs and other files.  Open Eclipse's preferences panel and navigate to *Java > Build Path > Classpath Variables*:  !eclipse-classpath-vars.png|align=center,thumbnail!  Click the *New* button, and enter the new variable (you'll have to adjust this for your operating system and local paths):  !eclipse-new-var.png|align=center,thumbnail!  Eclipse will ask to perform a clean build, and the errors will be gone once it has done so.   {tutorialnav} 

Full Content



Tapestry Tutorial
Dependencies, Tools and PluginsCreating The Skeleton ApplicationLoading the Project Into EclipseHiloFormsForms2





The first step is to ask Maven to generate the Eclipse control files (.classpath and .project) for us:


$ mvn eclipse:eclipse -DdownloadSources=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO] org.apache.maven.plugins: checking for updates from apache-snapshots
[INFO] org.codehaus.mojo: checking for updates from apache-snapshots
[INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from apache-snapshots
[INFO] snapshot org.apache.maven.plugins:maven-eclipse-plugin:2.9-SNAPSHOT: checking for updates from apache-snapshots
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.pom
11K downloaded  (maven-eclipse-plugin-2.9-20101117.070458-148.pom)
Downloading: http://repository.apache.org/snapshots//org/apache/maven/plugins/maven-eclipse-plugin/2.9-SNAPSHOT/maven-eclipse-plugin-2.9-20101117.070458-148.jar
194K

[CONF] Apache Tapestry > Loading the Project Into Eclipse

2010-11-29 Thread confluence







Loading the Project Into Eclipse
Page  added by Howard M. Lewis Ship

 

 


   
Change Notification Preferences
   
   View Online