On 02/07/2013 08:47 AM, Alexey Kazakov wrote:

On 02/06/2013 11:31 PM, Mickael Istria wrote:

I have the opposite feeling: some people will be happy to see them working on Juno. Why updating MANIFEST and block that? What is the added value?

IMO we just don't know if the stuff works on Juno if we don't test it on Juno and even don't build it against Juno. Right now (we moved to Kepler just a week ago) it should work but I won't be sure about it in a month.
And probably there will be plenty of users who will try to install JBT on Juno without understanding that they are doing it on their own risk.

Enabling API Tools in your IDE will help you to detect when you use recent API, and will suggest you to update your MANIFEST accordingly.
If you prefer updating poms, that's not bad and we won't care while it works on Kepler. IMO, It's just sad to not benefit from modularity provided by OSGi that makes that one can pick up some subsets of the application if he wants to make a custom package of his own. But providing this ability to our users is not something we care that much.
So in the end; do what you want, it just has to work with Kepler.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets