CacheIDE M1 Version Update Site

[gurkanerdogdu]

Hi;
There are some prerequire plugins to run cache
plugins; these are

- emf-sdo-xsd-SDK-2.1.1
- GEF-SDK-3.1.1
- JEM-SDK-1.1.0.1
- wtp-0.7.1

Marshall could we applicable to create this M1
version update site? If so what can I do?

[maxandersen]

We could probably add this to the updatesite when we do the final release, but it would probably be a requirement that you verify that it works against WTP 1.0 since that is the version we are using in the 1.5 final.

can you make that work ?

marshall probably knows more about what stuff that is required for integrating it into the build - such as providing a feature and map files etc.

[gurkanerdogdu]

Yeap, I have just tried with WTP 1.0 , it works =:)

[maxandersen]

btw, what part of WTP do you actually use in the cacheIDE ? Last time I launched it I did not notice any wtp dependency ?

You need to identify the needed plugins and put in your feature.xml, is that done ?

The easiest way of getting cacheIDE available for download is to integrate it into our build system which should be easy - marshall knows the steps better than I.

but when it is added it should be part of the nightly builds and then at least downloadable in one bundle.

[gurkanerdogdu]

Actually it does not hard coding depend on WTP API's. I want to mean that it is required plugin to run cacheide. Because I am using "org.eclipse.wst.xml.ui.internal.tabletree.XMLMultiPageEditorPart" to edit cache configuration file to open in editor.

feature.xml is consists of all dependency that is ok;

[mculpepper]

Hi Gurkan.

We can get cache integrated into our automated build environment but it's going to take a little work.

I would recommend that you first take a look at the doc I created for setting up the build environment here:

http://docs.jboss.org/jbosside/releng-howto/howto.html

Once you've got a succesful nightly build running, you'll need to take a look at each of our seperate builders (right now we have 6), and mimic their functionality.

It basically boils down to creating a folder under the "builders" directory called "cache", and then enabling your builder by editing the global.properties.template (and then re-running the build customization script).

After that you will need to create a map file, a customTargets.xml under the cache builder directory as well as a build.properties.template that uses the same properties as all the other builders (and has specific properties as well for the cache's build).

The specifics of creating the map file and the customTargets.xml can be found if you search hard enough around the internet. Here's a good link I've used:

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng.basebuilder/readme.html?rev=HEAD#configs

Once you have your builder up and running inform us on this thread and I'll go ahead and let you perform your standalone component release (this will be out-of-sync with the rest of JBossIDE since your component is still in an "unstable" mode while we are just wrapping up a final release for the rest of JBossIDE).

After your M1 release is finished, you will need to upload the file to sourceforge and notify me so I can create the new release for you.

If you need any help setting up the build feel free to either ask me in this forum or pop me an IM =).

[gurkanerdogdu]

Hi;

As said by Marshall, I put jwsdp....exe to the directory. And run customizeBuild.xml.After specifying related params, I did run the given command build-integration.bat product

But I am getting the error build.xml file not found, what is the problem?

Thanks;