Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329886 - Provide maven virgo:run command
Summary: Provide maven virgo:run command
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-10 06:19 EST by Alex Blewitt CLA
Modified: 2010-11-21 03:14 EST (History)
2 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 Alex Blewitt CLA 2010-11-10 06:19:38 EST 
Build Identifier: 2.1.0.RELEASE

Maven has jetty:run and tomcat:run, which can be used to bootstrap a runtime environment from a Maven project, and in the case of WAR files, load them into the container.

Having an ability to fire up a Virgo installation and be able to deploy a WAR, WAB or PAR into Virgo would greatly simplify its use. (This depends on Virgo to be accessible from some Maven site, so that it could be used in such a way.)

A problem for non-PARs is the acquisition of non-direct dependencies. However, being able to launch WAR and PARs into Virgo would not be a problem; it's really only WABs that would need some kind of extra support. (Perhaps a Maven 'runtime' dependency would be sufficient to include transitive dependencies)

Reproducible: Always
Comment 1 Glyn Normington CLA 2010-11-10 08:49:29 EST 
A good suggestion. Thanks Alex.
Comment 2 AA CLA 2010-11-21 03:14:19 EST 
Does that mean that we will be able to deploy bundles to Virgo server via Maven; similar to the tomcat:deploy Mojo.