RE: [corona-dev] Custom Build Targets

["O'Flynn, Dennis" <Dennis.OFlynn@xxxxxxxxxxxxx>]

Pawel – can you please provide some guidance on this?

 

This is the problem I would like solved…

Corona provides a plugin that is dependent upon 3^rd party libraries.  While waiting for IP approval of the libraries, the build process should be able to proceed by fetching those libraries from a non-Eclipse location.  This will allow the plugin to be built, tested and used while waiting for approval of the IP request

 

Specific example: Plugin for Apache Derby

Corona will use Apache Derby as a repository used by its exemplary implementation.  Initial approval for Derby was given by the PMC and is pending by the EMO.

 

I would like to commit the Corona Derby plugin to our CVS repository, without the Derby libraries.  This will require the build process to fetch the appropriate libraries and populate the plugin’s “lib” folder so that the plugin can be built properly.

 

I have briefly investigated both “customTargets.xml” and “customBuildCallbacks.xml”.  It appears that “customTargets.xml” is probably what is needed.

 

 

---

From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Tuesday, October 10, 2006 4:15 PM
To: Corona development
Subject: [corona-dev] Custom Build Targets

 

Pawel,

 

There are at least two ways to provide some custom build steps: customerTargets.xml and customBuildCallbacks.xml.  We may need to use one (or both?) of these to build some plugins that require 3^rd party libraries that are pending IP approval.

 

Can you recommend how this should be handled to ensure compatibility with Corona’s build process.

 

Thanks,

-Dennis

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.