Skip to Content
From version 1.2
edited by awa
on 25.02.2022, 13:47
Change comment: There is no comment for this version
To version 1.4
edited by awa
on 23.03.2022, 19:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -96,7 +96,7 @@
96 96  :; plugin-ident=manifest
97 97  :: //plugin-identifier// must contain the name of the manifest property and its value, in the format //Attribute-Name=value//. For example, if this property is set to //Implementation-Title=com.example.fc.plugin:my-plugin//, this will search for a plugin with a manifest entry //Implementation-Title// set to //com.example.fc.plugin:my-plugin//.
98 98  :; plugin-ident=id
99 -:: //plugin-identifier// must contain the data base ID of the target plugin, such as //53// or /893//.//
99 +:: //plugin-identifier// must contain the data base ID of the target plugin, such as //53// or //893//.
100 100  :; plugin-ident=name
101 101  :: //plugin-identifier// must contain the name of the target plugin, such as //my-plugin.jar// or //foobar.jar//.
102 102  :; plugin-ident=uuid
... ... @@ -442,19 +442,12 @@
442 442  While the Maven plugin offers a wide variety of options, the default settings are usually sufficient. We recommend the following steps for your plugin:
443 443  
444 444  Add this code snippet to the profile section of the //pom.xml//:
445 +
445 445  {{code language="xml"}}
446 - <properties>
447 - <fc-deploy-plugin-maven-plugin.version>1.1.0</fc-deploy-plugin-maven-plugin.version>
448 - </properties>
447 + <properties>
448 + <fc-deploy-plugin-maven-plugin.version>1.1.0</fc-deploy-plugin-maven-plugin.version>
449 + </properties>
449 449  
450 - <profiles>
451 - <profile>
452 - <id>fc-deploy</id>
453 - <activation>
454 - <property>
455 - <name>fcDeployUrl</name>
456 - </property>
457 - </activation>
458 458   <build>
459 459   <plugins>
460 460   <plugin>
... ... @@ -461,18 +461,9 @@
461 461   <groupId>de.xima.fc.maven.plugin</groupId>
462 462   <artifactId>fc-deploy-plugin-maven-plugin</artifactId>
463 463   <version>${fc-deploy-plugin-maven-plugin.version}</version>
464 - <executions>
465 - <execution>
466 - <goals>
467 - <goal>deploy</goal>
468 - </goals>
469 - </execution>
470 - </executions>
471 471   </plugin>
472 472   </plugins>
473 473   </build>
474 - </profile>
475 - </profiles>
476 476  {{/code}}
477 477  
478 478  The plugin is identified based on the entry //Implementation-Title// in its //Manifest.MF// file. For this to work, you need to prepare the manifest correctly. You can do so either with the //maven-jar-plugin// or with the //maven-assembly-plugin//, depending on which plugin your project uses.
... ... @@ -550,7 +550,7 @@
550 550  Now you can build the plugin via Maven and upload it to a {{formcycle}} server. The URL, the client ID and the token (password) can be passed to Maven via command line parameters:
551 551  
552 552  {{code language="bash"}}
553 -mvn clean install -DfcDeployUrl="http://localhost:8080/xima-formcycle" -DfcDeployClientId="1" -DfcDeployToken="admin"
537 +mvn package fc-deploy:deploy -DfcDeployUrl="http://localhost:8080/xima-formcycle" -DfcDeployClientId="1" -DfcDeployToken="admin"
554 554  {{/code}}
555 555  
556 556  If you do not pass these parameters, the deploy plugin is not executed and the plugin is not uploaded.