David H Nebinger 4 Years Ago Actually the Target Platform does offer a way to identify what Liferay provides vs what it doesn't. If you leave version off of your dependencies, a build will succeed when Liferay has the dependency as an export, but you'll get an error for those that are not provided. In this way you can kind of tell if something was exposed or not without having to track them down in the portal manually. I do like the idea of using the web console in Liferay. Gogo is fine once you learn the commands, but sometimes having a nice GUI to help navigate all of the various OSGi information can be tough. Please sign in to reply. Reply as... Cancel
Sarath Chandra 4 Years Ago - Edited I'm migrating portlets from 6.x to 7.x. IMO it'll be a tough one to do without knowing what all packages Liferay is exporting out of box. Especially, I need to convert my service builders to OSGI, and they use a lot of third-party libraries. Please sign in to reply. Reply as... Cancel