December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2400) org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2400?page=com.atlassian.jira.plugin.... ] Frank Langelage edited comment on WFLY-2400 at 12/9/13 3:15 PM: ---------------------------------------------------------------- It seems that problems went away. I ran smoke testsuite today a few times with and without -DnoWebProfile. Always successful. So I think we can close this one and 2399 and 2398. was (Author: lafr): It seems that problems went away. I ran smoke testsuite today a few times with and without -DnoWebProfile. Always successful. So I think we can close this one and 2401, 2399, 2398. > org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails > --------------------------------------------------------------------- > > Key: WFLY-2400 > URL: https://issues.jboss.org/browse/WFLY-2400 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server, Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Jeff Zhang > Attachments: org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase-output.txt, org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2400) org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2400?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2400: --------------------------------------- It seems that problems went away. I ran smoke testsuite today a few times with and without -DnoWebProfile. Always successful. So I think we can close this one and 2401, 2399, 2398. > org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase fails > --------------------------------------------------------------------- > > Key: WFLY-2400 > URL: https://issues.jboss.org/browse/WFLY-2400 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server, Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Jeff Zhang > Attachments: org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase-output.txt, org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-705) Implement a User Agent and Remote Address Filter for the HTTP Management Interface

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-705?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim commented on WFLY-705: --------------------------------------- I am wondering if one should be able to customize the response for a non-allowed useragent. I currently only have them 403'ed? > Implement a User Agent and Remote Address Filter for the HTTP Management Interface > ---------------------------------------------------------------------------------- > > Key: WFLY-705 > URL: https://issues.jboss.org/browse/WFLY-705 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Andre Dietisheim > Fix For: Awaiting Volunteers > > > The HTTP Management interface provides access to manage the domain model, this interface is partly dependent on the protection supplied by an end users web browser. > This feature request is to optionally filter inbound requests based on a configurable list of supported user agents and or remote addresses - this will mean buggy browser versions can be excluded and remote clients restricted. > Anyone interested in contributing please feel free to ping darranl in #jboss-as7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-373) Kie Maven plugin don't use the project classpath

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-373?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-373: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1039676 > Kie Maven plugin don't use the project classpath > ------------------------------------------------ > > Key: DROOLS-373 > URL: https://issues.jboss.org/browse/DROOLS-373 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > When compiling drls the kie maven plugin uses the plugin classpath instead of the project one. This imply that it is necessary to duplicate the dependencies used by the kie project also inside the plugin declaration, as reported by this email: http://drools.46999.n3.nabble.com/rules-users-Drool-6-0-0-Final-2-questio... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-373) Kie Maven plugin don't use the project classpath

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-373?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-373: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1039676|https://bugzilla.redhat.com/show_bug.cgi?id=1039676] from NEW to ASSIGNED > Kie Maven plugin don't use the project classpath > ------------------------------------------------ > > Key: DROOLS-373 > URL: https://issues.jboss.org/browse/DROOLS-373 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > When compiling drls the kie maven plugin uses the plugin classpath instead of the project one. This imply that it is necessary to duplicate the dependencies used by the kie project also inside the plugin declaration, as reported by this email: http://drools.46999.n3.nabble.com/rules-users-Drool-6-0-0-Final-2-questio... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-373) Kie Maven plugin don't use the project classpath

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-373?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-373. -------------------------------- Fix Version/s: 6.0.1.Final Resolution: Done > Kie Maven plugin don't use the project classpath > ------------------------------------------------ > > Key: DROOLS-373 > URL: https://issues.jboss.org/browse/DROOLS-373 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > When compiling drls the kie maven plugin uses the plugin classpath instead of the project one. This imply that it is necessary to duplicate the dependencies used by the kie project also inside the plugin declaration, as reported by this email: http://drools.46999.n3.nabble.com/rules-users-Drool-6-0-0-Final-2-questio... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-373) Kie Maven plugin don't use the project classpath

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-373: ---------------------------------- Summary: Kie Maven plugin don't use the project classpath Key: DROOLS-373 URL: https://issues.jboss.org/browse/DROOLS-373 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When compiling drls the kie maven plugin uses the plugin classpath instead of the project one. This imply that it is necessary to duplicate the dependencies used by the kie project also inside the plugin declaration, as reported by this email: http://drools.46999.n3.nabble.com/rules-users-Drool-6-0-0-Final-2-questio... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-705) Implement a User Agent and Remote Address Filter for the HTTP Management Interface

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-705?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim edited comment on WFLY-705 at 12/9/13 12:01 PM: ----------------------------------------------------------------- [~ctomc] Thanks for the precision, I know, I discussed the basic requirements with [~darranl] on irc. I'm doing handlers for undertow and filters in the wildfly/undertow subsystem was (Author: adietish): [~ctomc] I know, discussed the basic requirements with [~darranl] on irc. Thanks for the precision. > Implement a User Agent and Remote Address Filter for the HTTP Management Interface > ---------------------------------------------------------------------------------- > > Key: WFLY-705 > URL: https://issues.jboss.org/browse/WFLY-705 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Andre Dietisheim > Fix For: Awaiting Volunteers > > > The HTTP Management interface provides access to manage the domain model, this interface is partly dependent on the protection supplied by an end users web browser. > This feature request is to optionally filter inbound requests based on a configurable list of supported user agents and or remote addresses - this will mean buggy browser versions can be excluded and remote clients restricted. > Anyone interested in contributing please feel free to ping darranl in #jboss-as7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-705) Implement a User Agent and Remote Address Filter for the HTTP Management Interface

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-705?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim edited comment on WFLY-705 at 12/9/13 12:00 PM: ----------------------------------------------------------------- [~ctomc] I know, discussed the basic requirements with [~darranl] on irc. Thanks for the precision. was (Author: adietish): [~ctomc] I know, discussed the basic requirements with [~darranl] in irc. Thanks for the precision. > Implement a User Agent and Remote Address Filter for the HTTP Management Interface > ---------------------------------------------------------------------------------- > > Key: WFLY-705 > URL: https://issues.jboss.org/browse/WFLY-705 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Andre Dietisheim > Fix For: Awaiting Volunteers > > > The HTTP Management interface provides access to manage the domain model, this interface is partly dependent on the protection supplied by an end users web browser. > This feature request is to optionally filter inbound requests based on a configurable list of supported user agents and or remote addresses - this will mean buggy browser versions can be excluded and remote clients restricted. > Anyone interested in contributing please feel free to ping darranl in #jboss-as7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-705) Implement a User Agent and Remote Address Filter for the HTTP Management Interface

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/WFLY-705?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim commented on WFLY-705: --------------------------------------- [~ctomc] I know, discussed the basic requirements with [~darranl] in irc. Thanks for the precision. > Implement a User Agent and Remote Address Filter for the HTTP Management Interface > ---------------------------------------------------------------------------------- > > Key: WFLY-705 > URL: https://issues.jboss.org/browse/WFLY-705 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Andre Dietisheim > Fix For: Awaiting Volunteers > > > The HTTP Management interface provides access to manage the domain model, this interface is partly dependent on the protection supplied by an end users web browser. > This feature request is to optionally filter inbound requests based on a configurable list of supported user agents and or remote addresses - this will mean buggy browser versions can be excluded and remote clients restricted. > Anyone interested in contributing please feel free to ping darranl in #jboss-as7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2013