|
| Re: Component is not known to Buckminster [message #1004132 is a reply to message #1004054] |
Tue, 22 January 2013 16:19   |
|
Hi
please take the following with a grain of salt, since I don't know
whether this is your case: I had similar problems and they were due to
something wrong in the feature.xml; for instance, I had this problem
when in my feature.xml I included the same plugin or feature twice and
Buckminster stopped recognizing the feature project as a feature component.
If you right click on the feature project de.emsw.gosa.feature.kompman
and select "Buckminster" => "View CSPEC" are you getting an error or are
you able to see the CSPEC?
In my case, after fixing the feature.xml everything went back to normal.
This symptom also shows up if you modify the feature.xml in question and
press save: upon saving, if the feature.xml has some problems you should
see the "No component named..." in the Buckminster console.
hope this helps
cheers
Lorenzo
On 01/22/2013 03:04 PM, Christoph Keimel wrote:
> Hello
>
> while working on a build with buckminster I am now facing an issue that
> I have no idea on how to resolve. When I invoke the site.p2 action on a
> feature project, I get the error:
> No component named de.emsw.gosa.feature.kompman:eclipse.feature is known
> to Buckminster This feature is also not visible in the Component
> Explorer, but it is visible in the IDE (can be selected as part of a
> feature or product definition).
>
> This is the site feature:
> <feature
> id="de.emsw.gosa.releng"
> label="GO§A Update Site"
> version="1.8.0.qualifier"
> provider-name="EM Software GmbH">
>
> ... skipped ...
>
> <includes
> id="org.eclipse.equinox.executable"
> version="0.0.0"/>
> <includes
> id="de.emsw.gosa.feature.kompman.app"
> version="0.0.0"/>
> <includes
> id="de.emsw.gosa.feature.kompman.kompetenz"
> version="0.0.0"/>
> <includes
> id="de.emsw.gosa.feature.kompman"
> version="0.0.0"/>
> </feature>
>
> This is the main feature of the application (this is the missing feature!):
> <feature
> id="de.emsw.gosa.feature.kompman"
> label="GO§A Kompetenzmanager"
> version="1.8.0.qualifier"
> provider-name="EM Software">
>
> ... skipped ...
>
> <requires>
> <import feature="de.emsw.gosa.feature.kompman.app"
> version="1.8.0.qualifier" match="greaterOrEqual"/>
> <import feature="de.emsw.gosa.feature.kompman.kompetenz"
> version="1.8.0.qualifier" match="greaterOrEqual"/>
> </requires>
> </feature>
>
> The features de.emsw.gosa.feature.kompman.app and
> de.emsw.gosa.feature.kompman.kompetenz include the plugins.
>
> The strange thing is that it was visible before and "disapeared" after a
> restart of the IDE. At first I only had the de.emsw.gosa.feature.kompman
> which included all the plugins. I added the two new features as a
> requirement in order to build a product which can be updated with p2
> following this article:
> http://aniefer.blogspot.de/2009/07/adt-part-2-more-like-epp.html
> After the change, I could create the repository with site.p2 as
> expected. Since I restarted the IDE, the feature
> de.emsw.gosa.feature.kompman is missing.
>
> Any pointers on how to resolve this issue are highly appreciated!
>
> Greetings
> Christoph
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
|
Powered by
FUDForum. Page generated in 0.02264 seconds
] 
Search
Help
Register
Login
Home
. I started going through all the definitions one more time and found the problem. My feature project contained a .product definition which was based on plug-ins and not on features. After I removed this product buckminster recognized the feature again.