[
https://issues.jboss.org/browse/DROOLS-1572?page=com.atlassian.jira.plugi...
]
Matteo Mortari commented on DROOLS-1572:
----------------------------------------
Concerning Eclipse, this is normal behaviour of Maven-based project managed from the
Eclipse IDE: normally all maven-plugin shall have a corresponding m2e eclipse
lifecycle-mapping plugin configuration. This is demonstrated when creating a new project
using the Kie archertype, when setting the IDE related flag. The lifecycle-mapping
configuration can be left as ignore which is the default, or changed to execution
depending on the preferred use case. When the proper Maven build is triggered from the
Eclipse IDE, then the Maven build process will use the kie-maven-plugin as expected
anyway.
Figure 4.2. Example POM shows old maven group/artifactId
--------------------------------------------------------
Key: DROOLS-1572
URL:
https://issues.jboss.org/browse/DROOLS-1572
Project: Drools
Issue Type: Enhancement
Components: docs
Affects Versions: 6.5.0.Final, 7.0.0.CR3
Environment: Google Chrome
Reporter: Russell Morrisey
Assignee: Mario Fusco
In the Drools documentation, figure 4.2 (*Example project layout and Maven POM*) shows
the wrong groupId and artifactId. The correct artifact is:
{code:java}
org.kie:kie-maven-plugin:${runtime.version}
{code}
In addition, the new plugin causes an error in Eclipse unless a section is added to the
POM for the eclipse lifecycle-mapping plugin.
https://docs.jboss.org/drools/release/latest/drools-docs/html_single/#_bu...
https://stackoverflow.com/questions/26122801/m2e-connector-for-kie-maven-...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)