Home » Archived » Buckminster » Selectively hide some source features in the update site
| | |
Re: Selectively hide some source features in the update site [message #943144 is a reply to message #938919] |
Sun, 14 October 2012 07:26 |
|
On 10/10/2012 11:18 AM, Alan Underwood wrote:
> I don't think so. As source features are automatically generated, I
> think they always contain 'source' entries for every feature and plug-in
> in the non-source feature. Therefore if you include an sdk feature,
> Buckminster may be trying to create an sdk.source feature - and if the
> sdk contains com.google.guice but no com.google.guice.source,
> Buckminster may have added com.google.guice.source to the the sdk.source
> feature.
>
> Tom would have to confirm that, though.
>
> I wonder if including an 'sdk' is the right thing to do. I've not seen
> other eclipse features include an sdk. A product that is built from the
> feature, and would normally only contain binaries would also then
> contain .source plug-ins from that sdk feature...a bit weird.
Well, the context where I need to include sdk features is when I need to
build a product which is a custom eclipse distribution (say with
org.eclipse.sdk feature and other sdk features like xtext.sdk for
instance)...
cheers
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
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
|
|
| |
Re: Selectively hide some source features in the update site [message #946465 is a reply to message #945639] |
Tue, 16 October 2012 08:09 |
|
On 10/15/2012 03:50 PM, Alan Underwood wrote:
> If an sdk feature requires a .source plug-in but does not provide it
> itself, and you do not provide it in another feature somewhere, then you
> would not be able to build an eclipse distribution, with that feature.
> Director will complain about the missing dependency. You would have to
> point Director to your feature's p2.site and also a p2.site containing
> the guice.source plug-in. i.e. you need to have com.google.guice.source
> somewhere if you are going to use that sdk feature in your product.
I think that the sdk feature does not require com.google.guice.source in
fact, if I build the site excluding sources completely (i.e., using
cbi.include.source=false ) the site builds fine... that's why I'd need
to selectively exclude only some sources...
this seems not to be possible...
so is there some way to provide a fake component, like
com.google.guice.source ? in a CSPEX?
thanks in advance
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
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
|
|
|
Goto Forum:
Current Time: Mon Oct 07 17:41:01 GMT 2024
Powered by FUDForum. Page generated in 0.04252 seconds
|