[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [e4-dev] Resolver Problem with guava and e4 (javax.annotation)

I don't know if this problem was solved ... or worked around .... but didn't want the issue to get lost, so I opened a bug in Orbit,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=437470
to make sure the issue isn't "lost" (thought not sure it's a true "Orbit Bug" ... seemed as good a place as any).

Thanks,




From:        David M Williams/Raleigh/IBM@IBMUS
To:        E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,
Cc:        orbit-dev@xxxxxxxxxxx, Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date:        06/11/2014 02:55 AM
Subject:        Re: [equinox-dev] [e4-dev] Resolver Problem with guava and        e4        (javax.annotation)
Sent by:        equinox-dev-bounces@xxxxxxxxxxx




> I don't think so because from their point of view they are requireing
> JavaSE-1.6 and so they can wire to javax.annotation without packages.
>
> They could remove the javax.annotation import completely because they
> anyways require JavaSE-1.6


Well, not quite.


javax.annotation 1.0.0 has a BREE of 1.5  (but is "native" to only 1.6, according to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=422981#c5  )
javax.annotation 1.1.0 has a BREE of 1.5  (but is "native" to only 1.7, according to '')

javax.annotation 1.2.0 has a BREE of 1.6  (but is "native" to only 1.8, according to '' -- I think -- assuming it "made it in", but I do not know for sure)


The idea being that projects could use annotations, as the specs came out, even on an "older" VM, rather than have to wait for the JRE that first contained it.

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev