Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[buckminster-dev] Different builds using Buckminster

Hi.

Let's assume such situation: I have some Eclipse plugins in SVN in source form. I need to gather them together to compose a working project.

I can easily get them all in my workspace using simple CQUERY. It will be perfect for our developers team, as they need to see all the sources and need to modify them often.

But we also have customization team, which don't need all of the source projects in the workspace - it would be preferable for them to pack each project into jar, include sources in it (for debugging purposes, but not for modification) and put all this jars somewhere together, so the project will be composed properly, but there will be minimal set of subprojects in the workspace.

Is it possible to complete with Buckminster? I've read Buckminster documentation, but only way to partially complete this seems to add action to each Eclipse plugin (using CSPEX), which will create .jar from plugin (and include sources in it). I have two questions then:
1) How can I call this action automatically? I think maybe "pre-bind" action will work there?
1) How can I gather this jars together or make Eclipse understand where to look for them? Is there any standart implementation for this?

Thanks.

Back to the top