[JBoss JIRA] (DROOLS-500) KIE API does not recognize proxy configuration if it's not in ${user.home}/.m2/settings.xml
by Rares Vernica (JIRA)
[ https://issues.jboss.org/browse/DROOLS-500?page=com.atlassian.jira.plugin... ]
Rares Vernica commented on DROOLS-500:
--------------------------------------
Using the -Dhttp.proxyHost= -Dhttp.proxyPort= properties on the command line might work.
> KIE API does not recognize proxy configuration if it's not in ${user.home}/.m2/settings.xml
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-500
> URL: https://issues.jboss.org/browse/DROOLS-500
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.0.1.Final
> Reporter: Ronak Patel
> Assignee: Mark Proctor
>
> The KIE API, specifically kie-ci, does not recognize proxy settings in
> {{settings.xml}} if the version of this file that contains the proxy settings is not located in {{$\{user.home\}/.m2}}. In other words, if the proxy settings are in {{$M2_HOME/conf/settings.xml}} or the file specified by the system property {{kie.maven.settings.custom}}, kie-ci will not use them.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFCORE-553) ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-553?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-553:
-----------------------------------------
The WFLY-3225 fix is what introduced WFCORE-553. Prior to that fix the pool was scoped to the factory service, not the handler.
> ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-553
> URL: https://issues.jboss.org/browse/WFCORE-553
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha18
> Reporter: Brian Stansberry
>
> ModelControllerClientOperationHandler's constructor creates a ThreadPoolExecutor for handling client requests and then the class doesn't clean it up.
> In addition, an instance of ModelControllerClientOperationHandler is created per channel, not one per ModelControllerClientOperationHandlerFactoryService. I know I at least thought of the thread pool as being per remote management interface, not per channel.
> Making it be per ModelControllerClientOperationHandlerFactoryService and cleaning it up in that service's stop would be the easiest fix, but the pool settings may not be appropriate if we do that, so tread carefully.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFCORE-553) ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-553:
---------------------------------------
Summary: ModelControllerClientOperationHandler doesn't manage the clientRequestExecutor properly
Key: WFCORE-553
URL: https://issues.jboss.org/browse/WFCORE-553
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.Alpha18, 1.0.0.Alpha1
Reporter: Brian Stansberry
ModelControllerClientOperationHandler's constructor creates a ThreadPoolExecutor for handling client requests and then the class doesn't clean it up.
In addition, an instance of ModelControllerClientOperationHandler is created per channel, not one per ModelControllerClientOperationHandlerFactoryService. I know I at least thought of the thread pool as being per remote management interface, not per channel.
Making it be per ModelControllerClientOperationHandlerFactoryService and cleaning it up in that service's stop would be the easiest fix, but the pool settings may not be appropriate if we do that, so tread carefully.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (WFCORE-552) SaslResource and SaslPolicyResource don't deal with the parent resource correctly
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-552:
---------------------------------------
Summary: SaslResource and SaslPolicyResource don't deal with the parent resource correctly
Key: WFCORE-552
URL: https://issues.jboss.org/browse/WFCORE-552
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Remoting
Affects Versions: 1.0.0.Alpha18, 1.0.0.Alpha1
Reporter: Brian Stansberry
Assignee: Tomaz Cerar
SaslResource and SaslPolicyResource represent child configuration under a parent connector or http-connector resource. But their handlers (particularly add and remove) do not reflect this. They simply store config changes to the model and return without making runtime changes. So only if they are executed at boot or in a composite with the connector add op is their configuration data properly included in the runtime.
PropertyResource is a similar child of the connector resources, but it uses RestartParentResourceAddHandler, RestartParentWriteAttributeHandler and RestartParentResourceRemoveHandler.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-686) Documentation build: Upgrade pressgang-tools from 2 to 3
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-686?page=com.atlassian.jira.plugin... ]
Petr Široký commented on DROOLS-686:
------------------------------------
I sent e-mail to Steve and Strong asking them if they could do the jdocbook-core release. I will comment here once I know more.
> Documentation build: Upgrade pressgang-tools from 2 to 3
> --------------------------------------------------------
>
> Key: DROOLS-686
> URL: https://issues.jboss.org/browse/DROOLS-686
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Petr Široký
>
> We're still using pressgang-tools 2:
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom....
> but some years ago pressgang-tools 3.x was build and released (by Steve Ebersole), which fixes some issues and enables some new features (such as topics in docbook):
> https://github.com/pressgang/pressgang-tools
> However, pressgang-tools 3.x has an important regression in combination with the maven-docbook-plugin 2.3.8, which prevents building offline, which is a blocker for us:
> https://issues.jboss.org/browse/PRESSGANG-79
> The interesting note is that the gradle-docbook-plugin does build offline, and that both plugins (maven and gradle) use the same jdocbook-core:
> https://github.com/pressgang
> Goal: Fix that jira in maven-docbook-plugin and/or pressgang-tools, so droolsjbpm can upgrade to pressgang-tools 3.x. This is probably not easy.
> The reason that it doesn't build offline, is because the xslt's contain full-url imports, so it reaches out to download those, but the jdocbook-core is able to intercepts to calls and reroute them to the local resources in the pressgang-tools jar (instead of downloading them from the internet). For some reason that works (probably configured correctly) for the gradle plugin, but not for the maven plugin. It's also strange that the maven plugin does work correctly with pressgang 2 jars.
> In any case, the build should work offline (and doing "mvn -o" alone doesn't suffice to prove it, because the -o is ignored for the xslt stuff), plug out the network cable to verify it builds offline.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-686) Documentation build: Upgrade pressgang-tools from 2 to 3
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-686?page=com.atlassian.jira.plugin... ]
Petr Široký commented on DROOLS-686:
------------------------------------
After some minor tweaks I managed to get this working.
This is what I did (just locally to verify everything is working as expected):
* updated {{maven-jdocbook-plugin:2.3.9-SNAPSHOT}} to use {{jdocbook-core-1.1.1-SNAPSHOT}}
* in {{kie-parent-metadata}} upgraded the jdockbook-plugin to {{2.3.9-SNAPSHOT}} + upgraded {{pressgang-xslt-ns}} to {{3.0.0}}
* fixed paths for xslt resources (in plugin config), e.g. {{xslt/org/jboss/xhtml-single.xsl}} to {{xslt/org/jboss/pressgang/xhtml-single.xsl}}
* built the {{kie-docs}} + {{optaplanner-docs}} modules. Some minor tweaks for {{kie-docs}} needed (with disabled networking to verify the offline build works)
So now we need new releases of {{jbocbook-core}} and {{maven-jdocbook-plugin}}
> Documentation build: Upgrade pressgang-tools from 2 to 3
> --------------------------------------------------------
>
> Key: DROOLS-686
> URL: https://issues.jboss.org/browse/DROOLS-686
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Petr Široký
>
> We're still using pressgang-tools 2:
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom....
> but some years ago pressgang-tools 3.x was build and released (by Steve Ebersole), which fixes some issues and enables some new features (such as topics in docbook):
> https://github.com/pressgang/pressgang-tools
> However, pressgang-tools 3.x has an important regression in combination with the maven-docbook-plugin 2.3.8, which prevents building offline, which is a blocker for us:
> https://issues.jboss.org/browse/PRESSGANG-79
> The interesting note is that the gradle-docbook-plugin does build offline, and that both plugins (maven and gradle) use the same jdocbook-core:
> https://github.com/pressgang
> Goal: Fix that jira in maven-docbook-plugin and/or pressgang-tools, so droolsjbpm can upgrade to pressgang-tools 3.x. This is probably not easy.
> The reason that it doesn't build offline, is because the xslt's contain full-url imports, so it reaches out to download those, but the jdocbook-core is able to intercepts to calls and reroute them to the local resources in the pressgang-tools jar (instead of downloading them from the internet). For some reason that works (probably configured correctly) for the gradle plugin, but not for the maven plugin. It's also strange that the maven plugin does work correctly with pressgang 2 jars.
> In any case, the build should work offline (and doing "mvn -o" alone doesn't suffice to prove it, because the -o is ignored for the xslt stuff), plug out the network cable to verify it builds offline.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-686) Documentation build: Upgrade pressgang-tools from 2 to 3
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-686?page=com.atlassian.jira.plugin... ]
Petr Široký edited comment on DROOLS-686 at 2/18/15 2:17 PM:
-------------------------------------------------------------
After some minor tweaks I managed to get this working.
This is what I did (just locally to verify everything is working as expected):
* updated {{maven-jdocbook-plugin:2.3.9-SNAPSHOT}} to use {{jdocbook-core1.1.1-SNAPSHOT}}
* in {{kie-parent-metadata}} upgraded the jdockbook-plugin to {{2.3.9-SNAPSHOT}} + upgraded {{pressgang-xslt-ns}} to {{3.0.0}}
* fixed paths for xslt resources (in plugin config), e.g. {{xslt/org/jboss/xhtml-single.xsl}} to {{xslt/org/jboss/pressgang/xhtml-single.xsl}}
* built the {{kie-docs}} + {{optaplanner-docs}} modules. Some minor tweaks for {{kie-docs}} needed (with disabled networking to verify the offline build works)
So now we need new releases of {{jbocbook-core}} and {{maven-jdocbook-plugin}}
was (Author: psiroky-redhat.com):
After some minor tweaks I managed to get this working.
This is what I did (just locally to verify everything is working as expected):
* updated {{maven-jdocbook-plugin:2.3.9-SNAPSHOT}} to use {{jdocbook-core-1.1.1-SNAPSHOT}}
* in {{kie-parent-metadata}} upgraded the jdockbook-plugin to {{2.3.9-SNAPSHOT}} + upgraded {{pressgang-xslt-ns}} to {{3.0.0}}
* fixed paths for xslt resources (in plugin config), e.g. {{xslt/org/jboss/xhtml-single.xsl}} to {{xslt/org/jboss/pressgang/xhtml-single.xsl}}
* built the {{kie-docs}} + {{optaplanner-docs}} modules. Some minor tweaks for {{kie-docs}} needed (with disabled networking to verify the offline build works)
So now we need new releases of {{jbocbook-core}} and {{maven-jdocbook-plugin}}
> Documentation build: Upgrade pressgang-tools from 2 to 3
> --------------------------------------------------------
>
> Key: DROOLS-686
> URL: https://issues.jboss.org/browse/DROOLS-686
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Petr Široký
>
> We're still using pressgang-tools 2:
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom....
> but some years ago pressgang-tools 3.x was build and released (by Steve Ebersole), which fixes some issues and enables some new features (such as topics in docbook):
> https://github.com/pressgang/pressgang-tools
> However, pressgang-tools 3.x has an important regression in combination with the maven-docbook-plugin 2.3.8, which prevents building offline, which is a blocker for us:
> https://issues.jboss.org/browse/PRESSGANG-79
> The interesting note is that the gradle-docbook-plugin does build offline, and that both plugins (maven and gradle) use the same jdocbook-core:
> https://github.com/pressgang
> Goal: Fix that jira in maven-docbook-plugin and/or pressgang-tools, so droolsjbpm can upgrade to pressgang-tools 3.x. This is probably not easy.
> The reason that it doesn't build offline, is because the xslt's contain full-url imports, so it reaches out to download those, but the jdocbook-core is able to intercepts to calls and reroute them to the local resources in the pressgang-tools jar (instead of downloading them from the internet). For some reason that works (probably configured correctly) for the gradle plugin, but not for the maven plugin. It's also strange that the maven plugin does work correctly with pressgang 2 jars.
> In any case, the build should work offline (and doing "mvn -o" alone doesn't suffice to prove it, because the -o is ignored for the xslt stuff), plug out the network cable to verify it builds offline.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (DROOLS-686) Documentation build: Upgrade pressgang-tools from 2 to 3
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-686?page=com.atlassian.jira.plugin... ]
Petr Široký edited comment on DROOLS-686 at 2/18/15 2:17 PM:
-------------------------------------------------------------
After some minor tweaks I managed to get this working.
This is what I did (just locally to verify everything is working as expected):
* updated {{maven-jdocbook-plugin:2.3.9-SNAPSHOT}} to use {{jdocbook-core:1.1.1-SNAPSHOT}}
* in {{kie-parent-metadata}} upgraded the jdockbook-plugin to {{2.3.9-SNAPSHOT}} + upgraded {{pressgang-xslt-ns}} to {{3.0.0}}
* fixed paths for xslt resources (in plugin config), e.g. {{xslt/org/jboss/xhtml-single.xsl}} to {{xslt/org/jboss/pressgang/xhtml-single.xsl}}
* built the {{kie-docs}} + {{optaplanner-docs}} modules. Some minor tweaks for {{kie-docs}} needed (with disabled networking to verify the offline build works)
So now we need new releases of {{jbocbook-core}} and {{maven-jdocbook-plugin}}
was (Author: psiroky-redhat.com):
After some minor tweaks I managed to get this working.
This is what I did (just locally to verify everything is working as expected):
* updated {{maven-jdocbook-plugin:2.3.9-SNAPSHOT}} to use {{jdocbook-core1.1.1-SNAPSHOT}}
* in {{kie-parent-metadata}} upgraded the jdockbook-plugin to {{2.3.9-SNAPSHOT}} + upgraded {{pressgang-xslt-ns}} to {{3.0.0}}
* fixed paths for xslt resources (in plugin config), e.g. {{xslt/org/jboss/xhtml-single.xsl}} to {{xslt/org/jboss/pressgang/xhtml-single.xsl}}
* built the {{kie-docs}} + {{optaplanner-docs}} modules. Some minor tweaks for {{kie-docs}} needed (with disabled networking to verify the offline build works)
So now we need new releases of {{jbocbook-core}} and {{maven-jdocbook-plugin}}
> Documentation build: Upgrade pressgang-tools from 2 to 3
> --------------------------------------------------------
>
> Key: DROOLS-686
> URL: https://issues.jboss.org/browse/DROOLS-686
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Petr Široký
>
> We're still using pressgang-tools 2:
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom....
> but some years ago pressgang-tools 3.x was build and released (by Steve Ebersole), which fixes some issues and enables some new features (such as topics in docbook):
> https://github.com/pressgang/pressgang-tools
> However, pressgang-tools 3.x has an important regression in combination with the maven-docbook-plugin 2.3.8, which prevents building offline, which is a blocker for us:
> https://issues.jboss.org/browse/PRESSGANG-79
> The interesting note is that the gradle-docbook-plugin does build offline, and that both plugins (maven and gradle) use the same jdocbook-core:
> https://github.com/pressgang
> Goal: Fix that jira in maven-docbook-plugin and/or pressgang-tools, so droolsjbpm can upgrade to pressgang-tools 3.x. This is probably not easy.
> The reason that it doesn't build offline, is because the xslt's contain full-url imports, so it reaches out to download those, but the jdocbook-core is able to intercepts to calls and reroute them to the local resources in the pressgang-tools jar (instead of downloading them from the internet). For some reason that works (probably configured correctly) for the gradle plugin, but not for the maven plugin. It's also strange that the maven plugin does work correctly with pressgang 2 jars.
> In any case, the build should work offline (and doing "mvn -o" alone doesn't suffice to prove it, because the -o is ignored for the xslt stuff), plug out the network cable to verify it builds offline.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months