Summary

• Page properties (2 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.cds
	1	+XWiki.nbw

Content

...	...	@@ -25,10 +25,10 @@
25	25
26	26	== Importing Existing Plug-ins ==
27	27
28		-1. [[Download >>url:https://git.rtsys.informatik.uni-kiel.de/plugins/servlet/archive/projects/MISC/repos/tutorials?at=refs%2Fheads%2Fplugins||shape="rect"]]the zip file with an example plug-in from our Stash. Unzip the file.
	28	+1. [[Download >>url:https://git.rtsys.informatik.uni-kiel.de/rest/archive/latest/projects/MISC/repos/tutorials/archive?at=refs%252Fheads%252Fplugins&format=zip||shape="rect"]]the zip file with an example plug-in from our Stash. Unzip the file.
29	29	1. Open the context menu within the //Package-Explorer// (on the very left, right-click the empty space).
30	30	1. Select //Import//. Then chose //General > Existing Projects into Workspace//.
31		-1. Browse to the location where you unzipped the downloaded plug-in. Check the checkbox in front of the {{code language="none"}}de.cau.cs.kieler.tutorials.plugins.shouter{{/code}} plug-in and press //Finish.
	31	+1. Browse to the location where you unzipped the downloaded plug-in. Click open. Check the checkbox in front of the {{code language="none"}}de.cau.cs.kieler.tutorials.plugins.shouter{{/code}} plug-in and press //Finish.
32	32	[[image:attach:import.jpg]]//
33	33
34	34	== Running Eclipse ==
...	...	@@ -35,7 +35,7 @@
35	35
36	36	In Eclipse, we develop plug-ins that extend the basic functionality of Eclipse itself. As we do not always want to run Eclipse with all the functionality there is, we can use //Run Configurations// to precisely specify the functionality we want.
37	37
38		-1. Click //Debug// > //Debug Configurations...//
	38	+1. Click //Run// > //Run Configurations...//
39	39	1. Right-click //Eclipse Application// and click //New//. Set the configuration's name to {{code language="none"}}Eclipse Test{{/code}}.
40	40	1. On the //Plug-ins// tab, set //Launch with// to //plug-ins selected below only//.\\
41	41	11. Click //Deselect All//.
...	...	@@ -42,10 +42,12 @@
42	42	11. Check the //Workspace// item in the tree.
43	43	11. Check the{{code language="none"}} org.eclipse.ui.ide.application{{/code}} plugins under //Target Platform//
44	44	11. Click //Add Required Plug-ins//. Press it twice (just to be sure!).
45		-1. Click //Apply// to save your changes and then //Debug// to start an Eclipse instance to test with.
	45	+1. Click //Apply// to save your changes and then //Run// to start an Eclipse instance to test with.
46	46	1. In the newly started Eclipse, open the context menu of the Project Explorer.
47	47	1. You should see a //Hello Shouter// entry which shouts out //Hello// if you press it.
48	48
	49	+Note that you can run your configuration also by using the debug button in the main menu. In that case you will be able to use debug features and code changes will be directly active in your Eclipse instance after saving. In the rather rare cases where this is impossible you will be notified.
	50	+
49	49	== Creating Your First Plug-in ==
50	50
51	51	1. Open the context menu within the //Package-Explorer// (on the very left, right-click the empty space).
...	...	@@ -75,6 +75,6 @@
75	75	1. Give it a name and using the //Browse// button select your previously created class implementing the {{code language="none"}}IShouter{{/code}} interface.
76	76	1. Start your Eclipse instance again using the created run configuration and test your very own shouter.
77	77
78		-
	80	+\\
79	79
80		-
	82	+\\

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-10751712
	1	+28672100

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/TUT/pages/10751712/Eclipse Plug-ins and Extension Points
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/TUT/pages/28672100/Eclipse Plug-ins and Extension Points