Jboss version in camunda-archetype-ejb-war-7.10.0

Camunda 7 Topics Discussion & Questions
1

Hi,

So far I’m builing process applications based on Maven “camunda-archetype-ejb-war-7.8.0”
In the pom.xml file there I see that the used jboss version is 7.2.1.Final.

  <name>Camunda BPM Process Application</name>
  <description>A Process Application for [Camunda BPM](http://docs.camunda.org). [The project has been generated by the Maven archetype 'camunda-archetype-ejb-war-7.8.0']</description>

  <properties>
    <camunda.version>7.8.0</camunda.version>
    <arquillian.version>1.1.2.Final</arquillian.version>
    <jboss.version>**7.2.1.Final**</jboss.version>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <failOnMissingWebXml>false</failOnMissingWebXml>
  </properties>

I’m trying now to build a process application based on Maven camunda-archetype-ejb-war-7.10.0.
The generated pom.xml file has a earlier(?) jboss version!

  <name>Camunda BPM Process Application</name>
  <description>A Process Application for [Camunda BPM](http://docs.camunda.org). [The project has been generated by the Maven archetype 'camunda-archetype-ejb-war-7.10.0']</description>
      <properties>
        <camunda.version>7.10.0</camunda.version>
        <!--
        Adjust if you want to use Camunda Enterprise Edition (EE):
        <camunda.version>7.10.0-ee</camunda.version>
        Make sure you also switch to EE repository below
        -->
        <arquillian.version>1.4.0.Final</arquillian.version>
        <jboss.version>**7.2.0.Final**</jboss.version>
        <maven.compiler.source>1.8</maven.compiler.source>
        <maven.compiler.target>1.8</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <failOnMissingWebXml>false</failOnMissingWebXml>
      </properties>

Is that possible? Shall I change it? Will I have any issues?

Thanks!

2

Hi @kontrag
Archetypes are used as a quickstart for developing process applications.
Yes, you can change the value of jboss.version or any other properties.

In below docs, step 4 of maven project creation shows that you can change archetypes properties from the creation wizard too.
https://docs.camunda.org/manual/latest/user-guide/process-applications/maven-archetypes/

1 Like
3

Thanks @hassang!

So, to which value should I change it?
In the full distribution I downloaded, the folder of the server is wildfly-14.0.1.Final.
Does it really matter actually?

4

Hi @kontrag,

the property jboss.version is used only in the build.properties.example file.

If you deploy your project with mvn clean wildfly:deploy, you don’t need this property.

Cheers, Ingo

1 Like
5