jazz-community/jazz-plugin-maven-archetype

Maven archetype to generate a jazz plugin project.

jazz-plugin-maven-archetype's Issues

Tycho builds fail with Maven 3.6.1

Builds depending on OSGI dependencies will fail when using Maven 3.6.1.

This bug and its duplicate address this issue. A fix will be available with the release of Maven 3.6.2.

add .jazzignore files where necessary

Publish to Maven Central

Get rid of configuration files

The archetype automatically generates the following files:

conf/
- log4j.properties
- scr.xml
- services.xml
- teamserver.properties

In case of where you use the Jazz Debug Environment, the configuration files listed above are integrated into this version specific environment. Therefore, there is no need to deliver this Jazz version specific files with a plugin. I suggest to completely remove them from being auto-generated

Plugin section name should be dynamic

jazz-plugin-maven-archetype/src/main/resources/archetype-resources/plugin/plugin.xml

Line 14 in ef281db

name="REST Service"

Service usage examples

It would be nice to have some examples on how to consume the services / interact with the deployed service. Maybe as a console application or a small web site.

Add instructions how / where to copy application configuration

When not using the jazz development environment / another jetty configuration, you have to supply plugin configuration files.

log4j.properties
scr.xml
services.xml
teamserver.properties

I'll show how and where to get these, and where you have to copy them.

Add Build Automation using Travis

Tycho version 1.1.0

A new version of tycho was released a while ago, and we should update to the new version on the archetype (as well as our projects). The most important change for us probably is this:

Added new goal mvn org.eclipse.tycho:tycho-versions-plugin:update-eclipse-metadata (bug 342893) which will update MANIFEST/feature.xml/product versions based on their respective pom versions. This is useful e.g. if you changed pom versions using maven-release-plugin. For more details about using the maven release plugin with Tycho see Tycho/Release_Workflow.

This should resolve the problem of having to manually adjust the test manifest after changing versions in the pom. Further, I hope it works on all dependencies, so that no manual adjustments have to made in manifest files.

Add resources folder to archetype

A new project should include a resources folder in the plugin/src/main directory. Maybe some sensible example content could be used.

Build fails depending on maven-assembly-plugin version

As we have no version of the maven-assembly-plugin fixed in the update-site pom, packaging can throw errors when a user's maven-assembly-plugin has versions above 2.4. Most probable fix to this is defining an assembly-id which is not appended to the finished build.

Setup script for linux

Port the setup powershell script to bash with the same functionality.

Custom named setup results in default setup

Running the following command:

.\setup.ps1 -group org.jazz-community.example -version 0.0.1-SNAPSHOT -serviceName HelloCommunityService

I would expect it to be named as defined. But instead, the default name com.siemens.example is being used

Support multiple extension types

The current archetype is limited to producing RTC services. It would be nice if it could also produce Advisors and Participants. One option would be to let the user select (single or multiple choice) what he wants. Another option is to add an example for all extension types.

Include deployment information in update-site pom

For deploying on our jbe, additional deployment information in the update-site pom is required. I will think about adding this to the archetype.

add parent project dependency to test project pom

Sanitize input and arguments

Prevent from using other parameters (e.g. if someone types -grou instead of -group by accident)