From version < 18.5 >
edited by awa
on 17.10.2019, 10:19
To version < 18.6
edited by gru
on 28.04.2020, 11:22
<
Change comment: Code Makro angepasst

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.awa
1 +XWiki.gru
Content
... ... @@ -10,9 +10,9 @@
10 10  
11 11  == Project setup ==
12 12  
13 -Setup a new Java project with the IDE of your choice. {{formcycle/}} uses the build management system [[Apache Maven>>url:https://maven.apache.org/]]) to resolve dependencies. Dependencies are provided by our public artifactory {{code}}http://artifactory.xima-services.de/artifactory/fc-plugin-dev{{/code}}. It contains all components needed for developing plugins. The main artifact you will need is the artifact [[fc-plugin-common>>url:http://artifactory.xima-services.de/artifactory/fc-plugin-dev/de/xima/fc/fc-plugin-common/]], containing all Java interfaces available for plugins.
13 +Setup a new Java project with the IDE of your choice. {{formcycle/}} uses the build management system [[Apache Maven>>url:https://maven.apache.org/]]) to resolve dependencies. Dependencies are provided by our public artifactory {{code language="none"}}http://artifactory.xima-services.de/artifactory/fc-plugin-dev{{/code}}. It contains all components needed for developing plugins. The main artifact you will need is the artifact [[fc-plugin-common>>url:http://artifactory.xima-services.de/artifactory/fc-plugin-dev/de/xima/fc/fc-plugin-common/]], containing all Java interfaces available for plugins.
14 14  
15 -Maven uses configuration files named {{code}}pom.xml{{/code}} (project object model). A pom for plugin development might look as follows:
15 +Maven uses configuration files named {{code language="none"}}pom.xml{{/code}} (project object model). A pom for plugin development might look as follows:
16 16  
17 17  {{panel title="Example for a pom.xml" initial="hidden" triggerable="true" fullwidth="true"}}
18 18  {{code language="xml"}}
Copyright 2000-2025