Bug 394465 - Make a Cargo container for deploying custom Virgo server zipped installation
Summary: Make a Cargo container for deploying custom Virgo server zipped installation
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-16 08:19 EST by Charlie Mordant CLA
Modified: 2012-12-03 03:08 EST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Mordant CLA 2012-11-16 08:19:28 EST 
Hi,

It would be good to have a Cargo container for Virgo.
It will ease the integration testing phase.

A simple cinematic for an entreprise would be:

* Putting a zipped Virgo server containing all the enterprise custom libraries (spring-integration, AMQ...) on a Nexus repository.

* Referencing this archive in the Maven-cargo-plugin starting the server during the pre-integration-tests phase

* Executing tests (with junit 4.7 and an integration tests custom annotation or failsafe) with the jacoco agent/maven-jacoco-plugin (capturing the tests results for Sonar for example).

* Another declaration of the maven-cargo-plugin to stop the server in the post-integration-tests phase.

It will reduce the usual Virgo integration-test configuration duplicating (but only partially) a complete Virgo configuration.

see forum post: http://www.eclipse.org/forums/index.php/t/427101/

Regards
Comment 1 Nobody - feel free to take it CLA 2012-11-16 09:41:14 EST 
Tooling is a reasonable component to raise this against, but currently it tends to refer to Virgo IDE and bundlor, so changing the component to "unknown" to avoid this enhancement being overlooked as requiring Virgo IDE or bundlor skills.