[jboss-jira] [JBoss JIRA] (DROOLS-3654) Use custom gwt-helper-maven-plugin to simplify pom configuration

[Gabriele Cardosi (Jira)]

     [ https://issues.jboss.org/browse/DROOLS-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriele Cardosi updated DROOLS-3654:
-------------------------------------
    Description: 
The main scope is to allow editing/debugging/hot-reload client-code (GWT) of modules external of drools-wb while working with drools-webapp. This should be configurable on a per-developer basis, modifying personal .m2/settings.xml, without touching the versioned pom.xml
The current solution is based on the build-helper-maven-plugin, but it has two limitations
1) it is needed to statically define every external source inside the plugin configuration
2) it is not possible to override that configuration with the user' .m2/settings.xml.

The _gwt-help-maven-plugin_ (https://github.com/gitgabrio/gwt-helper-maven-plugin) has been designed to overcome this limitations

1) it uses a pattern matching to (recursively) find external sources
2) it uses a list of directories to define the path to read for external sources
3) it may use such pattern/directories defined as properties in the pom, and since properties are overridable with m2./settings.xml profile, it is possible for each user to define its own profile and its own pattern, to match the setting s/he has/needs on its machine 

  was:
The main scope is to allow editing/debugging/hot-reload client-code (GWT) of modules external of drools-wb while working with drools-webapp. This should be configurable on a per-developer basis, modifying personal .m2/settings.xml, without touching the versioned pom.xml
The current solution is based on the build-helper-maven-plugin, but it has two limitations
1) it is needed to statically define every external source inside the plugin configuration
2) it is not possible to override that configuration with the user' .m2/settings.xml.

The gwt.-help-maven-plugin (https://gitgabrio.github.io/gwt-helper-maven-plugin/) has been designed to overcome this limitations

1) it use a pattern matching to (recursively) find external sources from a given directory
2) it may use such patterns defined as properties in the pom, and since properties are overridable with m2./settings.xml profile, it is possible for each user to define its own profile and its own pattern, to match the setting s/he has/needs on its machine 



> Use custom gwt-helper-maven-plugin to simplify pom configuration
> ----------------------------------------------------------------
>
>                 Key: DROOLS-3654
>                 URL: https://issues.jboss.org/browse/DROOLS-3654
>             Project: Drools
>          Issue Type: Enhancement
>            Reporter: Gabriele Cardosi
>            Assignee: Gabriele Cardosi
>            Priority: Minor
>
> The main scope is to allow editing/debugging/hot-reload client-code (GWT) of modules external of drools-wb while working with drools-webapp. This should be configurable on a per-developer basis, modifying personal .m2/settings.xml, without touching the versioned pom.xml
> The current solution is based on the build-helper-maven-plugin, but it has two limitations
> 1) it is needed to statically define every external source inside the plugin configuration
> 2) it is not possible to override that configuration with the user' .m2/settings.xml.
> The _gwt-help-maven-plugin_ (https://github.com/gitgabrio/gwt-helper-maven-plugin) has been designed to overcome this limitations
> 1) it uses a pattern matching to (recursively) find external sources
> 2) it uses a list of directories to define the path to read for external sources
> 3) it may use such pattern/directories defined as properties in the pom, and since properties are overridable with m2./settings.xml profile, it is possible for each user to define its own profile and its own pattern, to match the setting s/he has/needs on its machine 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)