[jboss-jira] [JBoss JIRA] (DROOLS-599) kjar archertype

[Matteo Mortari (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13342295#comment-13342295 ] 

Matteo Mortari commented on DROOLS-599:
---------------------------------------

Hi [~mbiarnes] , in reference to my previous comment above, and now discussing with [~mfusco] , we would like to highlight the availability of the Kie Archetype to end users.

However, [since this archetype was first proposed|https://github.com/droolsjbpm/droolsjbpm-knowledge/pull/74/files#diff-ae073dbf7d2d212e8ef79caab795cb87], now [License file-headers are attached to all files|https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/7172a50c4989800a8cda029b1e5efaec9c1d7dcb#diff-42a73ec3fc7beda342f8c8ad2bddec31]; with the actual consequence that once you use the archetype, as a user, your files are containing the Red Hat file-header license; and I believe this could be very confusing for the end-users, and also I believe is wrong.

My proposal is to remove License file-headers, at least from all files which are serving as a template-generation.

I have two question, please?
# Do you agree with me reverting your change?
# Did you notice the License file-headers are missing thanks to some automatic tool? Is there a way to manage exclusion, either in the tool or by adding a special header to the file itself?

Thank you in advance for your feedback.

> kjar archertype
> ---------------
>
>                 Key: DROOLS-599
>                 URL: https://issues.jboss.org/browse/DROOLS-599
>             Project: Drools
>          Issue Type: Feature Request
>    Affects Versions: 6.1.0.Final
>            Reporter: Matteo Mortari
>            Assignee: Mario Fusco
>             Fix For: 6.2.0.CR1
>
>
> I'm opening this JIRA as I will later open PR related to https://groups.google.com/d/msg/drools-development/uO17-kC4mvc/aBRunEcZ_b4J
> The version of the archetype defaults for non-CEP, non-Eclipse plugin in pom. There are property which user can change default value to have CEP, and Eclipse plug-in.
> For reference,
> * Set-up the new project's pom:
> ** Change Java version to 1.6 or greater, by including the maven-compiler-plugin
> ** Add Drools dependencies
> ** Change JUnit dependencies to version 4
> ** Add kie-maven-plugin
> ** [option] Add plug-in org.eclipse.m2e/lifecycle-mapping settings, to avoid Eclipse ERROR at the pom.xml line defining the kie-maven-plugin
> ** Set packaging to 'kjar'
> * ( ALT + F5 in betweens )
> * Creation of an initial .drl file in src/main/resources
> * Creation of minimal kmodule.xml in src/main/resources/META-INF directory
> * Create a simple JUnit test for:
> ** Creation of KieBase [option ->] with STREAM option for CEP features
> ** Creation of KieSession [option ->] with pseudo-clock
> ** [option: Advance] / Insert / Fire template
> ** ... and other verification/output patterns
> * Include SLF4J and LOG4J binding for logging, including a log4j.properties file in src/test/resources



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)