Fwd: [Carbon-dev] Building "add-on" packs for WSAS, ESB and Registry

[Senaka Fernando]

This point might be valuable for us too. As we need to figure out how to deploy our solution on WSO2 ESB.

Regards,
Senaka

---------- Forwarded message ----------
From: Paul Fremantle <pa...@wso2.com>
Date: Sun, Dec 14, 2008 at 1:36 PM
Subject: [Carbon-dev] Building "add-on" packs for WSAS, ESB and Registry
To: carbo...@wso2.org


A few weeks ago, we figured out how to "add" the ESB to WSAS. I'd really
like to automate the builds required, so that we can have a ZIP/TGZ file
that we unpack into an existing product to add the new function.

In future releases, I'd really like to have a nice UI for this, but for
January I'd be really happy if we can just create a component ZIP that
needs to be unzipped into CARBON_HOME.

I think this needs to be part of the maven build so that its repeatable.

So what I expect is that for each product we create two ZIP files:

wso2xxxx-y.0.zip
wso2xxxx-component-y.0.zip

We will also need to update OT to explain the component files.

The next step is to figure out how to use Maven or OSGi dependencies to
automate the downloading of a component from the component repository,
but that can *definitely* wait.

Paul

PS if you guys have already susses this out, forgive me!

--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse

Office: +44 844 484 8143
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
pa...@wso2.com

"Oxygenating the Web Service Platform", www.wso2.co

_______________________________________________
Carbon-dev mailing list
Carbo...@wso2.org
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev