[
https://issues.jboss.org/browse/DROOLS-1394?page=com.atlassian.jira.plugi...
]
Toni Rikkola commented on DROOLS-1394:
--------------------------------------
Some additional information about this ticket. We already had the possibility to do any
Maven build in the guvnor webapp. Now that the webapp has been removed the code is most
likely gone, but should exist in git history.
How this used to work, was it dumped the git repo to the server hard drive and fired
Maven. Maven had to be installed for this to work.
The issues with this approach:
* Code is duplicated to two locations
* Anyone who has access to the server can see the source code
* Harder setup, since you need to install Maven
I imagine there is a better way.
Use Maven for compiling the workbench projects
----------------------------------------------
Key: DROOLS-1394
URL:
https://issues.jboss.org/browse/DROOLS-1394
Project: Drools
Issue Type: Feature Request
Reporter: Toni Rikkola
Assignee: Mario Fusco
We currently use the kie-maven-plugin internally to compile the kjar's and only use
Maven to provide the information about parent projects and dependencies for the project.
Yet we have the power of Maven underneath and we do not use it. It is impossible to use
simple features like ignoring folders or moving code. Or more complicated, for example if
you have your own rule asset format and need a Maven plugin to generate the DRL out of
it.
However it is possible to set this functionality up. This causes problems:
* Same git tag built in the workbench produce different results depending on the
Workbench version that is being used. This means that if you want to rebuild a lost kjar,
you need to install the same workbench version that was originally used to create the
first one
* Projects build in command line/build server can produce different kjars than the ones
built with the workbench
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)