diff options
| author | Alex Blewitt <alex.blewitt@gs.com> | 2013-05-02 14:44:40 +0100 |
|---|---|---|
| committer | Alex Blewitt <alex.blewitt@gs.com> | 2013-05-03 17:07:40 +0100 |
| commit | 90d0a58276a5e7bb267ec0a46b49426ef08a76da (patch) | |
| tree | dbf44a44f488a2e6536467943fa629e8e98d190e | |
| parent | 737680a0261497f902cc8bfb80c6398de65a27b7 (diff) | |
Fix issues with Prolog files in Eclipse
Because the Eclipse runtime doesn't have the generated sources,
it doesn't know about the generated classes. To fix this problem,
adding the generated sources as a project folder in Eclipse gives
it the visibility of the classes, including when they are rebuilt,
and so running/debugging in the Prolog runtime should not have
negative affects from an Eclipse perspective.
Since the Prolog runtime uses a separate ClassLoader for hosting
the classes, and it's not clear where those classes are subsequently
used, there may be bugs in which Prolog classes are leaked. This
change does not affect the existence of those failure modes.
Change-Id: Id8f89f28ee9660e39717b15f5c2910d6a5930e30
| -rw-r--r-- | pom.xml | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -421,7 +421,10 @@ limitations under the License. </goals> </pluginExecutionFilter> <action> - <ignore/> + <execute> + <runOnIncremental>false</runOnIncremental> + <runOnConfiguration>true</runOnConfiguration> + </execute> </action> </pluginExecution> <pluginExecution> @@ -434,7 +437,10 @@ limitations under the License. </goals> </pluginExecutionFilter> <action> - <ignore/> + <execute> + <runOnIncremental>false</runOnIncremental> + <runOnConfiguration>true</runOnConfiguration> + </execute> </action> </pluginExecution> </pluginExecutions> |