[JBoss JIRA] (WFCORE-2811) Remove JBoss Local User Quiet setting from ProtocolConnectionUtil
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFCORE-2811:
----------------------------------------
Summary: Remove JBoss Local User Quiet setting from ProtocolConnectionUtil
Key: WFCORE-2811
URL: https://issues.jboss.org/browse/WFCORE-2811
Project: WildFly Core
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 3.0.0.Beta22
The current implementation overrides any properties previously set on the AuthenticationConfiguration whether resolved from a wildfly-config.xml or from one programatically established by the calling client.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1158) Make JBoss Local User quiet by default.
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-1158:
-------------------------------------
Summary: Make JBoss Local User quiet by default.
Key: ELY-1158
URL: https://issues.jboss.org/browse/ELY-1158
Project: WildFly Elytron
Issue Type: Task
Components: SASL
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 1.1.0.Beta43
This mechanism in all management cases has previously been hard coded to be quiet by default, the is the predominant usage of the mechanism.
For a couple of EJB edge cases which have been found in the test suite we are putting in a lot of effort to keep it interactive by default.
If we don't make it quiet by default we are going to require either a wildfly-config.xml for each management client which is something we are trying to avoid or each management client is going to require access to the mechanism properties from the authentication configuration so they can be safely manipulated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2768) There is ConcurrentModificationException when we write new aliases to one credential store resource through multiple threads (management clients)
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2768?page=com.atlassian.jira.plugi... ]
Yeray Borges edited comment on WFCORE-2768 at 5/16/17 3:54 AM:
---------------------------------------------------------------
The issue has been discussed getting following conclusions:
* The use of context.getServiceRegistry(true) is to prevent concurrent management writes, since this issue is related to how internal structures of CredentialStore are being managed concurrently, we must use a different approach to avoid the concurrency problems.
* Credential store aliases are going to be exposed as operations instead of resources in WFCORE-2777, so maybe this issue is fixed due to that change. Once WFCORE-2777 will be merged, we will test against new code to check if we can hit the bug again.
* Anyway since CredentialStore service is modifying internal data, it must be retrieved with getServiceRegistry(true). This will be reviewed after WFCORE-2777 too.
was (Author: yersan):
The issue has been discussed getting following conclusions:
* The use of context.getServiceRegistry(true) is to prevent concurrent management writes, since this issue is related to how internal structures of CredentialStore are being managed concurrently, we must use a different approach to avoid the concurrency problems.
* Credential store aliases are going to be exposed as operations instead of resources in WFCORE-2777, so maybe this issue is fixed due to that change. Once WFCORE-2777 will be merged, we will test aginst new code to check if we can hit the bug again.
* Anyway since CredentialStore service is modifying internal data, it must be retrieved with getServiceRegistry(true)
> There is ConcurrentModificationException when we write new aliases to one credential store resource through multiple threads (management clients)
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2768
> URL: https://issues.jboss.org/browse/WFCORE-2768
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Yeray Borges
> Priority: Critical
>
> There is ConcurrentModificationException when
> we write new aliases to one credential store resource through multiple threads (management clients)
> *Use case:*
> More users are connected through CLI to same application server and work parallel with same credential store resource.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-783) alias-filter from Elytron key-store does not work for non-lower-case alias with JKS
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/ELY-783?page=com.atlassian.jira.plugin.sy... ]
Yeray Borges commented on ELY-783:
----------------------------------
Verified using Bouncy Castle as security provider, which allows aliases in uppercase. SSL works fine using this provider. That means alias-filter is case sensitive and that was the intention since alias case sensitivity is dependent of the provider implementation.
Issue should be managed as documentation in this case.
> alias-filter from Elytron key-store does not work for non-lower-case alias with JKS
> -----------------------------------------------------------------------------------
>
> Key: ELY-783
> URL: https://issues.jboss.org/browse/ELY-783
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta13
> Reporter: Ondrej Lukas
> Assignee: Yeray Borges
>
> In case when {{alias-filter}} attribute from Elytron {{key-store}} references non-lower-case alias (e.g. elytronAppServer) then SSL is not working. In case when this alias is set to lower-case in alias-filter (e.g. elytronappserver), then SSL works correctly.
> It seems JKS always transforms aliases to lower-case (even if they are created with some upper-case characters). However legacy security solution was able to use alias filter with non-lower-case characters to assign key from JKS keystore (probably through some internal {{.toLowerCase()}}).
> In case it is intended to do not use alias-filter with some upper-case for JKS then this issue can be changed to documentation issue. This is different behavior than was provided by legacy solution.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1036) CS tool, There is possibility define same option parameter more times.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-1036?page=com.atlassian.jira.plugin.s... ]
Hynek Švábek updated ELY-1036:
------------------------------
Description:
There is possibility define same option parameter more times. It doesn't matter if some short/long form or combination there is used first occurrence in command.
Command with two option "add" and "secret".
{code}
[hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --password mycspassword --summary --salt 12345678 --iteration 230 --add alias2 --secret secretValue2 -create
Alias "myalias" has been successfully stored
Credential store command summary:
--------------------------------------
/subsystem=elytron/credential-store=test:add(uri="cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="MASK-uNWeyrmbByBEjgZM1FAPQW==;12345678;230"})
{code}
*Same for "mask" command.*
was:
There is possibility define same option parameter more times. It doesn't matter if some short/long form or combination there is used first occurrence in command.
Command with two option "add" and "secret".
{code}
[hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary --salt 12345678 --iteration 230 --add alias2 --secret secretValue2
Alias "myalias" has been successfully stored
Credential store command summary:
--------------------------------------
/subsystem=elytron/credential-store=test:add(uri="cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="MASK-uNWeyrmbByBEjgZM1FAPQW==;12345678;230"})
{code}
*Same for "mask" command.*
> CS tool, There is possibility define same option parameter more times.
> -----------------------------------------------------------------------
>
> Key: ELY-1036
> URL: https://issues.jboss.org/browse/ELY-1036
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Command-Line Tool
> Reporter: Hynek Švábek
> Assignee: Ingo Weiss
>
> There is possibility define same option parameter more times. It doesn't matter if some short/long form or combination there is used first occurrence in command.
> Command with two option "add" and "secret".
> {code}
> [hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --password mycspassword --summary --salt 12345678 --iteration 230 --add alias2 --secret secretValue2 -create
> Alias "myalias" has been successfully stored
> Credential store command summary:
> --------------------------------------
> /subsystem=elytron/credential-store=test:add(uri="cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="MASK-uNWeyrmbByBEjgZM1FAPQW==;12345678;230"})
> {code}
> *Same for "mask" command.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ]
Tomas David commented on DROOLS-1511:
-------------------------------------
It seem to be a compatibility problem of Drools runtime version 7.x with any Drools plugin.
Workaround is to use Drools runtime 6 or use maven project.
> NullPointerException when running sample projects
> -------------------------------------------------
>
> Key: DROOLS-1511
> URL: https://issues.jboss.org/browse/DROOLS-1511
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: DevStudio 10 + IS 10.3.0.CR2
> Eclipse Neon + Drools plugin 7.0.0.CR3
> Drools Runtime 7.x
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Labels: reported-by-qe
>
> NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created.
> Eclipse log:
> !SESSION 2017-04-04 12:39:38.638 -----------------------------------------------
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737
> !MESSAGE Internal error in Drools Plugin:
> !STACK 1
> Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject']
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112)
> at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122)
> at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739
> !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-1511:
--------------------------------
Environment:
DevStudio 10 + IS 10.3.0.CR2
Eclipse Neon + Drools plugin 7.0.0.CR3
Drools Runtime 7.x
was:
DevStudio 10 + IS 10.3.0.CR2
Eclipse Neon + Drools plugin 7.0.0.CR3
> NullPointerException when running sample projects
> -------------------------------------------------
>
> Key: DROOLS-1511
> URL: https://issues.jboss.org/browse/DROOLS-1511
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: DevStudio 10 + IS 10.3.0.CR2
> Eclipse Neon + Drools plugin 7.0.0.CR3
> Drools Runtime 7.x
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Labels: reported-by-qe
>
> NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created.
> Eclipse log:
> !SESSION 2017-04-04 12:39:38.638 -----------------------------------------------
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737
> !MESSAGE Internal error in Drools Plugin:
> !STACK 1
> Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject']
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112)
> at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122)
> at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739
> !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-1511:
--------------------------------
Environment:
DevStudio 10 + IS 10.3.0.CR2
Eclipse Neon + Drools plugin 7.0.0.CR3
was:
DevStudio 10 + IS 10.3.0.CR2
Eclipse Neon + Drools plugin 7.0.0-SNAPSHOT
> NullPointerException when running sample projects
> -------------------------------------------------
>
> Key: DROOLS-1511
> URL: https://issues.jboss.org/browse/DROOLS-1511
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: DevStudio 10 + IS 10.3.0.CR2
> Eclipse Neon + Drools plugin 7.0.0.CR3
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Labels: reported-by-qe
>
> NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created.
> Eclipse log:
> !SESSION 2017-04-04 12:39:38.638 -----------------------------------------------
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737
> !MESSAGE Internal error in Drools Plugin:
> !STACK 1
> Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject']
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112)
> at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122)
> at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739
> !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month