Marko, The Eclipse Foundation
owns the Jakarta trademark. If Jakarta would ever become irrelevant
to Eclipse(heaven forbid), then I would assume they would be willing to
give it up -- just like the Apache Foundation gave the Jakarta rights to
the Eclipse Foundation since it was no longer used by Apache. Granted,
nobody can predict the future. But, the Eclipse Foundation is not
a commercial entity like Oracle. There would be no reason for the
Foundation to hold "Jakarta" hostage if it was no longer managing,
promoting, and developing Jakarta EE.
(I am not speaking
on behalf of the Foundation. I'm just expressing my views after working
for many years with the Foundation and associated Eclipse Projects.) --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Bekhta <marko.prykladna@xxxxxxxxx> To:
10:26 AM Subject:
Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the
jakarta namespace Sent
I was trying to catch up on this package
transitioning topic. And there's a question that was bugging me more and
more, deeper I was into the thread.
We are trying to decide which approach
to use to migrate the javax packages. But is there any guarantee that,
let's say in N years, we won't be in exactly the same situation, migrating
from jakarta to some other package?
I'm not great when it comes to legal/licensing
questions, but I think it would be great, if possible, to somehow ensure
that jakarta package stays open no matter what. This would make the platform
more attractive and safer to use. If that's already in place somewhere
I would be thankful if someone can point me in the right direction.