Re: Re[2]: [equinox-dev] OBR2

[Thomas Watson <tjwatson@xxxxxxxxxx>]

Can we use SCR's component XML definition
for service dependancies?  Even if the bundle does not use SCR directly
can we still use this schema to define service dependancies?  I would
not want to define a whole new schema for this.

Richard, are you subsribed the the equinox-dev
mailing list?  If not, please do so we don't have to keep cc'ing you
on the mails :)

Thomas Watson
Pervasive Development
Phone: 512-838-4533 Tie: 678-4533
tjwatson@xxxxxxxxxx


equinox-dev-bounces@xxxxxxxxxxx wrote on 09/23/2005
08:34:11 AM:

> Agree ... if it is not in the manifest, we can't generate it. But
it
> is nice to populate a repo with only the data from the manifests and
> get reasonable results.
> 
> Kind regards,
> 
>      Peter Kriens
>      
> RSH> Peter Kriens wrote:
> 
> >>It absolutely MUST be possible to generate the metadata from
the
> >>manifest.
> >>  
> >>
> 
> RSH> Well, it is not possible given the current state of bundle
manifests to
> RSH> generate all repository metadata. For example, there is no
way to
> RSH> generate service dependencies.
> 
> RSH> If someone invents a new capability/requirement pair, there
will be no
> RSH> way to generate it either.
> 
> RSH> For the standard package/module-related stuff, we can generate
them from
> RSH> the manifest.
> 
> ->> richard
> 
> RSH> _______________________________________________
> RSH> equinox-dev mailing list
> RSH> equinox-dev@xxxxxxxxxxx
> RSH> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> 
> 
> -- 
> Peter Kriens                
             Mob +33633746480
> 9C, Avenue St. Drézéry              
     Tel +33467542167
> 34160 Beaulieu, France              
     Tel +15123514821
>                    
                     
Tel +33870447986
> AOL,Yahoo, Skype pkriens            
     ICQ 255570717
> 
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev