I'm Jitendra Rajput (Senior Consultant @ CIGNEX Datamatics) , A Programmer , Blogger ,Liferay Top Contributor for Year 2014 Q4, Liferay 6.1 Certified Professional , Technology Enthusiast and apart from this interested in making new friends , love music and love to play CHESS. Expressing my thoughts using blog.
private static final Configuration _configuration = ConfigurationFactoryUtil
.getConfiguration(ReportUtil.class.getClassLoader(), "portlet");
String fromEmailAddress = _configuration.get("report.form.emailaddress");
Web-ContextPath: /my-custom-portlet
repositories {
maven {
url "https://cdn.lfrs.sl/repository.liferay.com/nexus/content/groups/public"
}
mavenLocal()
}
compileOnly project(":modules:test-module-a")
#
# Set this to true to index all article versions. Set this to false to index
# only the last indexable version.
#
journal.articles.index.all.versions=false
As you know development approach has been completely changed with Liferay DXP. In older version of Liferay it was easy to include static resource like CSS , JS and Images as part of portlet but with Liferay DXP you have to do few additional changes to include them.
You can include out of box as well as custom portlet inside theme in Liferay dxp but way has been changed.
While doing development in Liferay DXP your module may depends on external jar files . If required jar file is available in Liferay Nexus Repository then you can include them by using BND and Gradle file.
Best advantages of using OSGi is that you can divide your components in small micro services and as when required module's can use each other's services.