I also couldn't find any reference to where something like this is prescribed. I feel tempted to simply remove the hardcoded uses clauses here as it's a maintenance nightmare and very error-prone...
BTW the version is picked up from the packageinfo files that sit in the package directories. Cheers, David On 4 January 2012 07:36, Felix Meschberger <[email protected]> wrote: > Hi, > > Am 03.01.2012 um 18:44 schrieb Alasdair Nottingham: > >> Hi, >> >> I bet it is because the spec says it needs to look exactly like that, with >> those uses clauses. > > Where would that be mentioned. I quickly scanned the spec and could not find > such a thing. Also, I would not remember having seen it in other parts of the > specs. IMHO it would be highly unusual. Otherwise the version would probably > also have to be stated explicitly... > > Regards > Felix > >> >> Alasdair Nottingham >> >> On 3 Jan 2012, at 14:35, David Bosschaert <[email protected]> wrote: >> >>> Hi all, >>> >>> While looking at the jmx-bundle project I came across the following in >>> the pom.xml >>> >>> <aries.osgi.export> >>> org.osgi.jmx;uses:="javax.management.openmbean", >>> org.osgi.jmx.framework;uses:="org.osgi.jmx,javax.management.openmbean", >>> org.osgi.jmx.service.cm;uses:="javax.management.openmbean", >>> org.osgi.jmx.service.permissionadmin;uses:="org.osgi.jmx", >>> org.osgi.jmx.service.provisioning;uses:="javax.management.openmbean", >>> >>> org.osgi.jmx.service.useradmin;uses:="org.osgi.jmx,javax.management.openmbean", >>> org.apache.aries.jmx.codec >>> </aries.osgi.export> >>> >>> I'm wondering why the uses clauses are explicitly listed here. I mean >>> the Maven Bundle Plugin/BND do a pretty good job of computing this and >>> I would say it's very error-prone to list these manually. Anyone know >>> the reason why it's done here? >>> >>> Cheers, >>> >>> David >
