]
George Gastaldi commented on FORGE-2328:
----------------------------------------
+1 to move them to ui package. I don't remember why I created the setup sub-package,
but that doesn't really matter since this is just an implementation detail.
Move the Setup commands under a setup package or leave them under ui
?
----------------------------------------------------------------------
Key: FORGE-2328
URL:
https://issues.jboss.org/browse/FORGE-2328
Project: Forge
Issue Type: Sub-task
Components: Java EE
Affects Versions: 2.16.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
In the Java EE addon, all the commands are under a {{ui}} package (eg. {{javaee.cdi.ui}},
{{javaee.ejb.ui}}).
The problem is that some {{setup}} commands are under the sub-package {{setup}} (eg.
{{javaee.jpa.ui.setup.JPASetupWizard}}, {{javaee.jaxws.ui.setup.JAXWSSetupWizard}}) and
others aren't ({{javaee.faces.ui.FacesSetupWizard}}).
It would be nice to opt for one (under {{setup}}) or the other (under {{ui}}) and make
them all the same. The pb is that some APIs might be broken. The best choice (less
breaking APIs) is to move them under {{ui}} : only JPA has an API under {{setup}}, some
commands only have the impl under {{setup}}