| [buckminster-dev] Exporting artifacts (such as WAR files?) [message #32837] |
Fri, 15 May 2009 12:43  |
Eclipse User |
|
|
|
Hi again!
Trying to ask a hopefully more intelligent question:
I can now successfully resolve a cquery in my headless Buckminster. So I
have Buckminster headless resolve
http://www.eclipse.org/buckminster/samples/queries/demo.cque ry
for example.
This will materialize to a workspace with three Eclipse projects in it:
org.demo.worlds - a java project producing a JAR file
org.demo.xml.provider - seems to a plugin project, though I cannot spot
a plugin.xml file ??
org.demo.hello.xml.world - a plugin project which depends on the other two
What would I have to do to make the plugin be exported to some directory
in JAR format?
The use case I have would be a web application which I want to build.
How would I make Buckminster export it as a WAR file automatically?
Or is exporting in Buckminster currently limited to Eclipse stuff such
as Plugins, Feature, RCP products and the like?
Regards,
Torsten
|
|
|
|
| Re: [buckminster-dev] Exporting artifacts (such as WAR files?) [message #32908 is a reply to message #32873] |
Wed, 20 May 2009 06:05  |
| Eclipse User |
|
|
|
Hi Thomas,
That's a coincidence; I was just about to post a question on the subject.
We used another approach on one of my projects: we wrote an actor which
did any packaging (including .war), using code based on the packaging
plug-in provided by the JBoss tools project. We wrote a lot of
Buckminster extensions, under the 'Fuller' moniker, including a
Buckminster actor which branded version numbers into the meta-data of
the final artefacts (sorely needed in real-life software development).
You might remember this, because I managed Thomas Spiessens to write
Subversive support for Buckminster. Those were the days!
I was about to upgrade everything, starting from the latest 'Project
Archives' packaging plug-in provided by JBoss tools (Nice! Even nicer
than the previous), yet this time I was keen to get p2 support in.
I want to publish an artefact to a p2 repository, e.g. after the
packaging step has been concluded.
Back to the original question: where are we in terms of p2+Buckminster?
I'm specifically looking for:
- a way to publish artefacts (created by Bucky actors) to p2 repo's
- a way to acquire artefacts from p2 repo's prior to construction (as
building material).
Best regards,
Dann
Thomas Hallgren wrote:
> Hi Torsten,
> Torsten Schlabach wrote:
>> org.demo.xml.provider - seems to a plugin project, though I cannot
>> spot a plugin.xml file ??
> >
> The plugin.xml is not mandatory. It's only needed when the bundle use
> Eclipse specific things such as extension points.
>
>> What would I have to do to make the plugin be exported to some
>> directory in JAR format?
>>
> Right click on the project, choose "Buckminster" -> "Invoke Action" ->
> "bundle.jar"
>
> The output ends up in ${buckminster.output.root}/<bundle name>_<bundle
> version>-osgi.bundle
>
> buckminster.output.root is set to ${user.temp}/buckminster/build by
> default. You can set it to any value by providing a property file to the
> perform command or by using -vmargs -Dxxx=yyyy. The "invoke action" in
> the UI will also allow you to provide a property file.
>
>> The use case I have would be a web application which I want to build.
>> How would I make Buckminster export it as a WAR file automatically?
>>
>> Or is exporting in Buckminster currently limited to Eclipse stuff such
>> as Plugins, Feature, RCP products and the like?
>>
> Buckminster will generate a lot of predefined actions for features and
> bundles but currently we don't have anything that will recognize
> projects that produce war files. The easiest way to accomplish it is to
> add a buckminster.cspec and an ant-script to your project. The cspec can
> contain actions with actor="ant" that calls on the targets in the ant
> script.
>
> - thomas
|
|
|
Powered by
FUDForum. Page generated in 0.04213 seconds
Home