|
| Re: PDE's Export Target Wizard [message #526595 is a reply to message #526563] |
Mon, 12 April 2010 11:45   |
|
Hi Johannes,
I saw that blog too. I think it definitely deserves an enhancement request in our bugzilla. The only thing I can see
that would prevent integration is if PDE didn't maintain the headless/UI separation for this new function. I think
that's unlikely though. The target definition stuff has been well designed so far.
- thomas
On 04/12/2010 12:00 PM, Johannes Utzig wrote:
> Hi,
>
> I was just reading Chris' Blog entry about the new PDE's export target
> wizard that allows the user to export a target definition to a certain
> location.
> http://aniszczyk.org/2010/04/09/pdes-export-target-wizard/
> Would it be possible to reuse that headlessly in Buckminster?
> That would go great with the Hudson integration.
> The plugin already implements a 'Target Platform Publisher' that lets
> you archive a directory that contains plugins and features.
> The user names this Target Platform and is then able to reuse it
> declarative in other build jobs.
>
> Currently people already use target definition files to create a TP for
> other build jobs (simply more convinient than mspecs), but so far it's
> only possible with a hack:
> 1. Invoke buckminster with importtargetdefinition -A some.target
> 2. archive .metadata/org.eclipse.pde.core/.bundle-pool
>
> This isn't exactly clean since it's fishing internal stuff from the
> metadata.
> So with this new export wizard available the hudson plugin could offer
> much better support for the user. To create a target platform for other
> build jobs, simply point to a *.target file and name the output. The
> rest can be done automatically.
>
> So, does anybody know if this functionality could be used in a headless
> environment and integrated into buckminster?
>
> Best regards,
> Johannes
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02740 seconds
] 
Search
Help
Register
Login
Home
