Yep. That is a good idea! Feel free to update the plugin if you have some spare time. Otherwise, I will try to change it in the next couple of weeks:o. Thanks Emily
On Mon, Sep 15, 2014 at 11:02 AM, Felix Meschberger <[email protected]> wrote: > Hi Emily > > That makes perfect sense, yet: Could the bundle be a bit friendlier in > this situation and, e.g., nicely break the build indicating this situation > instead of throwing an NPE ? > > Regards > Felix > > Am 15.09.2014 um 11:47 schrieb Emily Jiang <[email protected]>: > > > As this is the first time you bring in Guava, you need to disable > semantic > > version as there is no base to check against as yet. I talked with Mark > > Nutall the other day regarding his new bundle. The solution is to set a > > property to disable the versioning check and reenable after you have had > > the first release. Mark, can you paste the example line here? > > Thanks > > Emily > > > > > > On Mon, Sep 15, 2014 at 10:19 AM, Felix Meschberger <[email protected]> > > wrote: > > > >> Hi > >> > >> We are currently considering using Guava in our application. Guava, > though > >> is really problematic in OSGi for various reasons: One of them is that > it > >> does not export packages with individual versions according to > OSGi-level > >> semantic versioning. See Guava Issue 1682 [1]. > >> > >> Now there’s a guy trying to come up with a patch to enable this but he > >> runs into ARIES-1159 [2]. Any clues on this from the community ? > >> > >> Thanks > >> Felix > >> > >> [1] https://code.google.com/p/guava-libraries/issues/detail?id=1682 > >> [2] https://issues.apache.org/jira/browse/ARIES-1159 > >> > >> > > > > > > -- > > Thanks > > Emily > > ================= > > Emily Jiang > > [email protected] > > -- Thanks Emily ================= Emily Jiang [email protected]
