[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jakartaee-platform-dev] Transitioning Jakarta EE to the jakarta namespace
- From: Martijn Dashorst <martijn.dashorst@xxxxxxxxx>
- Date: Tue, 7 May 2019 11:33:40 +0200
- Delivered-to: firstname.lastname@example.org
At my company we have a couple of million lines of code in apps
written to JavaEE specifications. Discussing it with our developers we
think the best way forward is to immediately rename all packages to
jakarta.*, and to do so in Jakarta EE 8.
Java EE 8 is available for folks to use. Jakarta EE 8 is not (yet).
Make the distinction between Java EE and Jakarta EE the fact that all
the package names have been modified, and that the future of the EE
platform lies with Jakarta.
Don't add marketable features, don't do fancy new integrations like
merging microprofile, don't add modularity or delay the package
rename. The marketable feature of Jakarta EE 8 is that you move to the
future of the platform when you move to Jakarta EE.
Just get it done, ensure all projects that implement these specs are
on board and do a mass migration. It will be painful, but as an old
saying in dutch states: Gentle healers make stinking wounds (Zachte
heelmeesters maken stinkende wonden, "It is better to treat a problem
thoroughly even if the treatment is painful, otherwise it may get
Having Java EE 8 and Jakarta EE 8 living next to each other with the
only difference package names would be ideal and marketable. Jakarta
EE 9 is then freed to integrate microprofile, do fancy module stuff
and more, making it clear that the future is Jakarta.