[#PETALSDISTRIB-199] Petals executable should be runnable easily after their compilation - Petals Link JIRA

Details

Type: Task
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 5.0.0-M1
Fix Version/s: 5.0.0-RC-1
Component/s: Clients, Container, Registry Overlay
Security Level: Public

Description:

Hide

Nowadays, after to have compiled and packaged Petals executable from their source code directory, we must move to a directory as target/petals-esb-default-zip-5.0.1-SNAPSHOT/bin and execute the right script. If the source code is cleaned and recompiled, we must removed to this directory (because the target was destroyed, and its inode has changed).

Please, provide a way to start Petals executable from the root of their source code, for example through Maven !

Show
Nowadays, after to have compiled and packaged Petals executable from their source code directory, we must move to a directory as target/petals-esb-default-zip-5.0.1-SNAPSHOT/bin and execute the right script. If the source code is cleaned and recompiled, we must removed to this directory (because the target was destroyed, and its inode has changed). Please, provide a way to start Petals executable from the root of their source code, for example through Maven !

Environment:

-

Issue Links

Depends

This issue depends on:
~~PETALSESBCONT-375~~ Petals ESB container should be runnable easily after their compilation
~~PETALSREGOVER-9~~ Petals Registry Overlay should be runnable easily after their compilation
~~PETALSESBCLI-130~~ Petals ESB CLI should be runnable easily after their compilation
~~PETALSREGCLI-6~~ Petals Registry CLI should be runnable easily after their compilation

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Christophe DENEUX added a comment - Wed, 16 Dec 2015 - 10:50:19 +0100 - edited

Perhaps can we use the Maven plugin: exec-maven-plugin.

For exemple for the Petals ESB minimal, we can add something as following in its POM:

<plugin>
   <groupId>org.codehaus.mojo</groupId>
   <artifactId>exec-maven-plugin</artifactId>
   <configuration>
      <executable>petals-esb.sh</executable>
      <workingDirectory>${project.build.directory}/${project.build.finalName}/bin</workingDirectory>
      <arguments>
         <argument>-u</argument>
         <argument>file://${project.build.directory}/${project.build.finalName}/conf/server.properties</argument>
      </arguments>
      <environmentVariables>
         <JAVA_OPTS>-Dpetals.log.dir=${project.build.directory}/${project.build.finalName}/logs</JAVA_OPTS>
      </environmentVariables>
   </configuration>
</plugin>

I don't know why the arguments and env variables are required. Perhaps a problem with the classpath defined in the script 'petals-esb.sh'

Show

Christophe DENEUX added a comment - Wed, 16 Dec 2015 - 10:50:19 +0100 - edited Perhaps can we use the Maven plugin: exec-maven-plugin. For exemple for the Petals ESB minimal, we can add something as following in its POM:

<plugin>
   <groupId>org.codehaus.mojo</groupId>
   <artifactId>exec-maven-plugin</artifactId>
   <configuration>
      <executable>petals-esb.sh</executable>
      <workingDirectory>${project.build.directory}/${project.build.finalName}/bin</workingDirectory>
      <arguments>
         <argument>-u</argument>
         <argument>file://${project.build.directory}/${project.build.finalName}/conf/server.properties</argument>
      </arguments>
      <environmentVariables>
         <JAVA_OPTS>-Dpetals.log.dir=${project.build.directory}/${project.build.finalName}/logs</JAVA_OPTS>
      </environmentVariables>
   </configuration>
</plugin>

I don't know why the arguments and env variables are required. Perhaps a problem with the classpath defined in the script 'petals-esb.sh'

Hide

Permalink

Christophe DENEUX added a comment - Wed, 16 Dec 2015 - 11:19:14 +0100

The problem was due to the directory missing in the executable definition. Using the following settings work fine:

<plugin>
   <groupId>org.codehaus.mojo</groupId>
   <artifactId>exec-maven-plugin</artifactId>
   <configuration>
      <executable>${project.build.directory}/${project.build.finalName}/bin/petals-esb.sh</executable>
      <workingDirectory>${project.build.directory}/${project.build.finalName}/bin</workingDirectory>
   </configuration>
</plugin>

Show

Christophe DENEUX added a comment - Wed, 16 Dec 2015 - 11:19:14 +0100 The problem was due to the directory missing in the executable definition. Using the following settings work fine:

<plugin>
   <groupId>org.codehaus.mojo</groupId>
   <artifactId>exec-maven-plugin</artifactId>
   <configuration>
      <executable>${project.build.directory}/${project.build.finalName}/bin/petals-esb.sh</executable>
      <workingDirectory>${project.build.directory}/${project.build.finalName}/bin</workingDirectory>
   </configuration>
</plugin>

Hide

Permalink

Christophe DENEUX added a comment - Wed, 16 Dec 2015 - 11:37:04 +0100

Petals executables are now easily runnable using Maven from their source code directory: mvn exec:exec

Show

Christophe DENEUX added a comment - Wed, 16 Dec 2015 - 11:37:04 +0100 Petals executables are now easily runnable using Maven from their source code directory: mvn exec:exec

Petals Distribution

Petals executable should be runnable easily after their compilation

Details

Issue Links

Activity

People

Dates