[JBoss JIRA] (WFCORE-4603) [GSS](7.2.x) Replace Deployment --runtime-name option not working
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFCORE-4603?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet moved JBEAP-17388 to WFCORE-4603:
---------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4603 (was: JBEAP-17388)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Affects Version/s: 10.0.0.Beta4
(was: 7.2.2.GA)
> [GSS](7.2.x) Replace Deployment --runtime-name option not working
> -----------------------------------------------------------------
>
> Key: WFCORE-4603
> URL: https://issues.jboss.org/browse/WFCORE-4603
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 10.0.0.Beta4
> Environment: Red Hat JBoss Enterprise Application Platform (EAP) 7.2 CP 3.
> Reporter: Emmanuel Hugonnet
> Assignee: Yeray Borges
> Priority: Major
>
> The scenario is that, if you have a deployment to be switched by a new one, the runtime-name property doesn't work the way it should. See the sequence of the commands bellow:
> [standalone@localhost:9990 /] deploy helloworld-rs.war
> [standalone@localhost:9990 /] deploy helloworld-rs-second.war —disabled
> [standalone@localhost:9990 /] :replace-deployment(name=helloworld-rs-second.war,to-replace=helloworld-rs.war,runtime-name=foo.war)
> [standalone@localhost:9990 /] /deployment=helloworld-rs-second.war:read-resource
> {
> "outcome" => "success",
> "result" => {
> "content" => [{"hash" => bytes {
> 0xfe, 0x24, 0x1f, 0xd3, 0x19, 0xa3, 0x72, 0xd4,
> 0xc6, 0xa4, 0x48, 0xe7, 0x8b, 0x9c, 0xc1, 0xd4,
> 0xc7, 0x17, 0xdf, 0xaa
> }}],
> "enabled" => false,
> "name" => "helloworld-rs-second.war",
> "owner" => undefined,
> "persistent" => true,
> "runtime-name" => "helloworld-rs-second.war",
> "subdeployment" => undefined,
> "subsystem" => {
> "undertow" => undefined,
> "ejb3" => undefined,
> "logging" => undefined
> }
> }
> }
> Foo.war is not applied. Looks like it was ignored.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4603) [GSS](7.2.x) Replace Deployment --runtime-name option not working
by Emmanuel Hugonnet (Jira)
[ https://issues.jboss.org/browse/WFCORE-4603?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet reassigned WFCORE-4603:
-----------------------------------------
Assignee: Emmanuel Hugonnet (was: Yeray Borges)
> [GSS](7.2.x) Replace Deployment --runtime-name option not working
> -----------------------------------------------------------------
>
> Key: WFCORE-4603
> URL: https://issues.jboss.org/browse/WFCORE-4603
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 10.0.0.Beta4
> Environment: Red Hat JBoss Enterprise Application Platform (EAP) 7.2 CP 3.
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> The scenario is that, if you have a deployment to be switched by a new one, the runtime-name property doesn't work the way it should. See the sequence of the commands bellow:
> [standalone@localhost:9990 /] deploy helloworld-rs.war
> [standalone@localhost:9990 /] deploy helloworld-rs-second.war —disabled
> [standalone@localhost:9990 /] :replace-deployment(name=helloworld-rs-second.war,to-replace=helloworld-rs.war,runtime-name=foo.war)
> [standalone@localhost:9990 /] /deployment=helloworld-rs-second.war:read-resource
> {
> "outcome" => "success",
> "result" => {
> "content" => [{"hash" => bytes {
> 0xfe, 0x24, 0x1f, 0xd3, 0x19, 0xa3, 0x72, 0xd4,
> 0xc6, 0xa4, 0x48, 0xe7, 0x8b, 0x9c, 0xc1, 0xd4,
> 0xc7, 0x17, 0xdf, 0xaa
> }}],
> "enabled" => false,
> "name" => "helloworld-rs-second.war",
> "owner" => undefined,
> "persistent" => true,
> "runtime-name" => "helloworld-rs-second.war",
> "subdeployment" => undefined,
> "subsystem" => {
> "undertow" => undefined,
> "ejb3" => undefined,
> "logging" => undefined
> }
> }
> }
> Foo.war is not applied. Looks like it was ignored.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-4245:
------------------------------------------
[~tirelli], I believe we went with the KIE logo rather than Drools because was parallel with Red Hat. That is, KIE and Red Hat or Drools and RHDM. But now that we're not co-branding and instead just saying "supported by Red Hat", I suppose it could be the Drools logo. However, this is all a very new approach in the product and in Red Hat deliverables, so I'm eager to hear what the branding team says to Brian.
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: RedHat_KIE_logo.eps, RedHat_KIE_logo.png, RedHat_KIE_logo.svg, doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months