|
Re: Cannot access Action in CSPEX [message #725162 is a reply to message #725149] |
Wed, 14 September 2011 06:24 |
|
Hi Jacob,
The AbstractResolutionBuilder has a method named applyExtensions(). It should be called just right after the cspec has
been generated. Are you doing that?
HTH,
Thomas Hallgren
On 2011-09-14 07:33, Jakob Braeuchi wrote:
> hi,
>
> we have defined our own ComponentType for EAR-Files. To build the CSPEC of the EAR-Type there is a EarResolutionBuilder
> class extending from AbstractResolutionBuilder. This solution works as expected: i can view the CSPEC of an EAR and i
> can also invoke the defined action "pack.ear".
>
> The problems shows up as soon as i create a CSPEX for an EAR-Component. I want to define a new action "pack.ear.ext"
> which uses the "pack.ear" action as a prerequisite:
>
>
> Problem during meta-data refresh: CSpec ch.rtc.zpv.application:osgi.bundle$1.0.0.qualifier has no action, group, or
> local artifact named pack.ear
>
>
> Do i have to add some "magic" to our EarResolutionBuilder to make it work or ist it a bug in Buckminster ?
>
> thanks jakob
|
|
|
|
|
|
Re: Cannot access Action in CSPEX [givenCtypeId is null] [message #725565 is a reply to message #725550] |
Thu, 15 September 2011 08:17 |
|
On 2011-09-15 08:56, Jakob Braeuchi wrote:
> hi thomas,
>
> after some debugging i found the cause for the problem.
>
> in the method LocalResolver#fromPath
>
> public static Resolution fromPath(IPath productPath, String name, String givenCtypeId, IProgressMonitor monitor) throws
> CoreException {
>
> the parameter givenCtypeId is null, so Buckminster looks for the possible types. It finds two types for my component:
> our own EAR-Type and osgi.bundle.
>
> further down in LocalResolver#fromPath the resolution is created for the type
>
> BOMNode node = ctype.getResolution(pm, MonitorUtils.subMonitor(monitor, 100));
>
> this works for the EAR-Type (our ResolutionBuilder is called), but it fails for the osgi.bundle with a
> MissingAttributeException.
>
> how can i fix this problem ?
>
Sounds like a bug in Buckminster. It shouldn't fail unless all possible types fail. Please report this as a bug and I'll
see to that it gets fixed.
- thomas
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04335 seconds