At a minimum, the mojo should:
foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
So... we may wish to check transitive dependencies only in the same repo. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
- is related to
-
JBIDE-23397 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [server]
- Closed
-
JBIDE-23391 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
- Closed
-
JBIDE-23393 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [cdi, batch, seam]
- Closed
-
JBIDE-23410 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]
- Closed
-
JBIDE-23394 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [visual-page-editor-core]
- Closed
-
JBIDE-23395 UI dependencies from Core plugins [hibernate]
- Open
-
JBIDE-23396 UI dependencies from Core plugins [webservices]
- Open
-
JBIDE-23392 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common]
- Reopened