Closed GoogleCodeExporter closed 8 years ago
A combined module is preferrable I think. This makes maintenance easier, and if
the configurations are defined well it doesn't preclude anyone from picking and
choosing the same way as they would be able to with distinct modules.
Original comment by archie.c...@gmail.com
on 29 Jul 2013 at 2:04
If we make this a single module, it'd have the following features:
Org: org.glassfish
Mod: hk2
Rev: 2.2.0-b10
Confs:
* Utils
* API [extends Utils]
* Locator [extends Utils, API]
* Core [extends Locator, Utils]
* Config [extends Core]
* RunLevel [extends API, Locator]
Original comment by steven.n...@gmail.com
on 29 Jul 2013 at 2:13
Actually, I'm not so sure about the group name now I think about it. The
osgi-resource-locator should really be in the org.glassfish.hk2 group as that
is it's package name. So that means that the rest should be in the same group
too. So, I'm going to go with:
Org: org.glassfish.hk2
Mod: hk2
Rev: 2.2.0-b10
Org: org.glassfish.hk2
Mod: osgi-resource-locator
Rev: 1.0.1
Original comment by steven.n...@gmail.com
on 29 Jul 2013 at 2:21
[ Grrrr, I've only gone and committed the sin of "It's" / "Its" ]
Original comment by steven.n...@gmail.com
on 29 Jul 2013 at 2:22
New, single module version attached.
Original comment by steven.n...@gmail.com
on 29 Jul 2013 at 3:21
Attachments:
Looks good, added in r2769.
Original comment by archie.c...@gmail.com
on 29 Jul 2013 at 3:32
Original issue reported on code.google.com by
steven.n...@gmail.com
on 29 Jul 2013 at 2:01