Petals Distribution

Petals executable should be runnable easily after their compilation

View this issue in another formatViewView
- XML
- Word
- Printable

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

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Wed, 16 Dec 2015 - 10:48:03 +0100

Updated:

Wed, 16 Dec 2015 - 11:37:04 +0100

Resolved:

Wed, 16 Dec 2015 - 11:37:04 +0100