Hey Scarletake,

I'm not sure that I am totally following what it is you want to do, but if the goal is to try to have a library globally available through the TOMCAT_HOME/lib/ext folder then you can still do this in 7.x, but it requires a couple of extra steps. 

1. Place the library in the /lib/ext directory of course

2. In your portal-ext.properties file you need to add the property module.framework.system.packages.extra which should include the values that the portal provides and the jar you are looking to include (I believe you have to provide both and you can't just specify your jar)

3. Restart your portal

You sitll have to include a reference to the library in your build.gradle or POM files of course but once you have done this you should be able to change the inclusions to be "compile" instead of including them in the final package. 

NOTE though that sometimes the library that you want to use is "OSGI ready" in which case all you have to do is copy the jar to the LIFERAY_HOME/osgi/modules location and the container will take care of the rest for you. I use this approach with a handful of libraries including gson, stripe and a few others and it works great. 

Let us know how it goes!

Hi Scarletake,

If I am following what you are saying then it sounds like the better solution. The idea in the 7 series is to have things broken up anyway rather than everything all bundled together into a single module. If you are using Service Builder and the idea of "fake entities" (also common place to have a standard pattern for development), and you are on 7.2, AND you don't need to persist the entity data, then make sure you add persistence="false" to the <entity/> definitions. That will eliminate all the persistence level code from being generated. No point if generating it and having it lying around if you aren't planning to use it :)