| Problems with generating CSpec [message #381626] |
Thu, 11 December 2008 02:49  |
Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Have a RCP product consisting of several feature and plugin projects
that I wish to Buckminsterize.
I am getting the following errors on my Buckminster console:
Project refresh on com.verticon.tracker.editor failed: CSpec
com.verticon.tracker.editor:osgi.bundle$0.3.1#OSGi has no action,
group, or local artifact named feature.exports
And in the error log:
eclipse.buildId=M20080911-1700
java.version=1.6.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments: -ignoreApp
Command-line arguments: -os linux -ws gtk -arch x86 -ignoreApp -console
Error
Wed Dec 10 18:30:23 CST 2008
CSpec com.verticon.tracker.editor:osgi.bundle$0.3.1#OSGi has no action,
group, or local artifact named feature.exports
Besides the errors in the console and the log, I see that my
com.verticon.tracker.editor plugin project has no CSpec viewable like
all my other projects. (thus the error?)
The com.verticon.tracker.editor is also referenced as a Branding Plugin
by a feature project named
com.verticon.tracker.feature.
This feature project (com.verticon.tracker.feature) has a feature id of
com.verticon.tracker.editor.
One other thing that I can think of that is unique is that I also have a
product file defined in this plugin.
I have other plugin projects that are also named as Branding Plugins by
feature projects but these don't seem to be a problem.
Any thoughts?
thanks,
John
|
|
|
| Re: Problems with generating CSpec [message #381629 is a reply to message #381626] |
Fri, 12 December 2008 08:54  |
|
John E. Conlon wrote:
> Have a RCP product consisting of several feature and plugin projects
> that I wish to Buckminsterize.
>
>
> I am getting the following errors on my Buckminster console:
> Project refresh on com.verticon.tracker.editor failed: CSpec
> com.verticon.tracker.editor:osgi.bundle$0.3.1#OSGi has no action,
> group, or local artifact named feature.exports
>
There seems to be some mixup between features and plug-ins. Where do you
declare your product configuration? Is it feature or plug-in based?
> Besides the errors in the console and the log, I see that my
> com.verticon.tracker.editor plugin project has no CSpec viewable like
> all my other projects. (thus the error?)
>
That could be the cause. Does it have a META-INF/MANIFEST.MF file?
Perhaps a corrupt plugin.xml? Does it by any chance have a feature.xml
in the root although it's a plug-in?
Regards,
Thomas Hallgren
|
|
|
| Re: Problems with generating CSpec [message #381632 is a reply to message #381629] |
Fri, 12 December 2008 16:11 |
| Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Thomas Hallgren wrote:
> John E. Conlon wrote:
>> Have a RCP product consisting of several feature and plugin projects
>> that I wish to Buckminsterize.
>>
>>
>> I am getting the following errors on my Buckminster console:
>> Project refresh on com.verticon.tracker.editor failed: CSpec
>> com.verticon.tracker.editor:osgi.bundle$0.3.1#OSGi has no action,
>> group, or local artifact named feature.exports
>>
> There seems to be some mixup between features and plug-ins. Where do you
> declare your product configuration?
I declare the product a file named tracker_features.product within the
com.verticon.tracker.editor plugin project.
Is it feature or plug-in based?
Feature based.
>
>
>> Besides the errors in the console and the log, I see that my
>> com.verticon.tracker.editor plugin project has no CSpec viewable like
>> all my other projects. (thus the error?)
>>
> That could be the cause. Does it have a META-INF/MANIFEST.MF file?
Yes it does.
> Perhaps a corrupt plugin.xml?
This appears ok.
Does it by any chance have a feature.xml
> in the root although it's a plug-in?
No feature.xml, but as noted above it does have a
tracker_features.product file in the root.
thanks for helping,
John
|
|
|
| Re: Problems with generating CSpec [message #381633 is a reply to message #381632] |
Fri, 12 December 2008 22:52 |
|
John E. Conlon wrote:
> I declare the product a file named tracker_features.product within the
> com.verticon.tracker.editor plugin project.
>
> Is it feature or plug-in based?
> Feature based.
>
Aha. Then the problem is probably that this will introduce a dependency
from the plug-in project to the feature. A dependency that very likely
becomes circular since the feature in turn will be dependent on the plug-in.
Could you try moving the product definition to the feature instead? That
will result in a "product component" defined by the feature and extended
by the product definition. That's actually the setup that I'd recommend.
I wrote a blog post about that a while back.
http://thhal.blogspot.com/2008/01/product-configurations.htm l
Hope that helps.
Regards,
Thomas Hallgren
|
|
|
| Re: Problems with generating CSpec [message #381636 is a reply to message #381633] |
Sat, 13 December 2008 18:18 |
| Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Hi Thomas,
That was it. I removed the old product file from the plugin and now I
have a generated CSpec!
> I wrote a blog post about that a while back.
>
> http://thhal.blogspot.com/2008/01/product-configurations.htm l
As a matter of fact, I had previously saw your blog and have been using
that technique to define my product (The old one was my backup which I
planed to delete;-) This is indeed an improved way to spec products.
Since my product also bundles in BIRT (and moving Birt components to my
local build machine is such a hassle), I am hoping to further improve
the process by Virtualizing the distro with Buckminster.
Although I am still learning, I am very enthusiastic about the potential
for Buckminster!
Thanks for the help.
John
Thomas Hallgren wrote:
> John E. Conlon wrote:
>> I declare the product a file named tracker_features.product within the
>> com.verticon.tracker.editor plugin project.
>>
>> Is it feature or plug-in based?
>> Feature based.
>>
> Aha. Then the problem is probably that this will introduce a dependency
> from the plug-in project to the feature. A dependency that very likely
> becomes circular since the feature in turn will be dependent on the
> plug-in.
>
> Could you try moving the product definition to the feature instead? That
> will result in a "product component" defined by the feature and extended
> by the product definition. That's actually the setup that I'd recommend.
> I wrote a blog post about that a while back.
>
> http://thhal.blogspot.com/2008/01/product-configurations.htm l
>
> Hope that helps.
>
> Regards,
> Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.02059 seconds
] 
Search
Help
Register
Login
Home
