[
http://jira.codehaus.org/browse/CARGO-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180240#action_180240 ]
Robert Herschke commented on CARGO-449:
---------------------------------------
Hi Matt,
the question is not, if there is an AS-Provider but how is the IT-Infrastructure organized in a company.
Most often Developers and IT-Services contend a huge fight about IT ressources and so on. The need about servers (esp. webservers) are heavilly discussed and it is hard to win IT Services around and to get another server.
So, most often (in case we do maven build) a company already intruduced a Maven Repository or a Maven Repository Proxy. It is very easy to use the maven repository also for distributing installation archives of an application server by simply mvn install:install-file the zip. On the other hand it is hard to get a new or an additional intranet-"web"-server to do the job: Host the AS-Installation Zip.
Next, it is more common, that the architects modify the installation zip's for the needs of the project and not distribute the original instalation zip. Think about Datasources and Realms aso.... Not all AS (and their corresponding cargo container plugin) are ready to accept the cargo.container.datasource or cargo.container.resource properties!
Well... short meaning: For me a clear vote to apply the (well, updated (if so)) patch!
> Allow a container distribution to be installed from a Maven artifact definition
> -------------------------------------------------------------------------------
>
> Key: CARGO-449
> URL:
http://jira.codehaus.org/browse/CARGO-449> Project: Cargo
> Issue Type: New Feature
> Components: Maven2
> Affects Versions: 0.2-maven2
> Reporter: Tom Huybrechts
> Assignee: Matt Wringe
> Priority: Minor
> Attachments: ArtifactInstaller.diff
>
>
> Attaching a patch that allows you to:
> - put/find a server as an artifact in a maven repository
> - use this artifact as the source for an Installer
> Use configuration like this where you would normally specify a ZipUrlInstaller (you'll need to install the jboss artifact locally)
> <artifactInstaller>
> <groupId>jboss</groupId>
> <artifactId>jboss</artifactId>
> <version>4.0.4.GA</version>
> <type>jar</type>
> </artifactInstaller>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
