ServiceBuilder: make location of service.properties configurable

• Type: Feature Request
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 5.2.3
• Fix Version/s: None
• Component/s: Legacy, Legacy > Extension Environment
• Labels: None
• Environment: maven plugin for service-builder (http://code.google.com/p/maven-lifeay-servicebuilder-plugin)
• Branch Version/s:
  5.2.x
• Similar Issues: Show 5 results ; ;

  LPS-9551	Make ResourceActionsUtil available to ServiceBuilder
  LPS-16554	Maven ServiceBuilder plugin generates service.properties in src/main/java instead of src/main/resources
  LPS-28654	LPS-28654 Make JavaScriptCompressor OPTIONS configurable in portal.properties
  LPS-16583	Maven: Make ServiceBuilder automatically invoke goals on dependent modules
  LPS-3067	Plugins can choose to disable auto upgrade of ServiceBuilder generated tables

The ServiceBuilder modifies a file service.properties. its location is hardcoded to the same path as the implementation classes. I wrote a maven plugin for the service builder (http://code.google.com/p/maven-lifeay-servicebuilder-plugin) . Maven expects non-java resource files such as service.property in src/main/resources. It would be nice if the ServiceBuilder could be configured to read/write the servcie.properties file from/to a configurable path.

[Tamás Sallai]

The problem with the service.properties file not inculded in the war is that the sql scripts won't run. Although maven can be told to include the file:
<build>
...
<resources>
<resource>
<directory>src/main/java</directory>
<includes>
<include>service.properties</include>
</includes>
</resource>
<resource>
<directory>src/main/resources</directory>
</resource>
</resources>
...
</build>

You need to specify the resources directory too, because if you don't, then it won't be included in the war.

Until the default place where the service.properties is generated is set, then the portlet archetype should inculde this fragment in the pom.xml, because it is not usable at the moment.

[Randy Zhu]

In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.