[jboss-jira] [JBoss JIRA] (WFCORE-865) Patching regression between WFCore 2.0.0.Alpha9 and Alpha11

[Ladislav Thon (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095688#comment-13095688 ] 

Ladislav Thon edited comment on WFCORE-865 at 8/5/15 5:55 AM:
--------------------------------------------------------------

Hmm, this seems to be missing in {{patch --help}}.

I would probably expect that without a {{\-\-patch-stream}} argument, all patch streams would be printed, but maybe that's just me. Is there a way to achieve that manually? Something like {{\-\-patch-stream=*}}?


was (Author: lthon):
Hmm, this seems to be missing in {{patch --help}}.

I would probably expect that without a {{--patch-stream}} argument, all patch streams would be printed, but maybe that's just me. Is there a way to achieve that manually? Something like {{--patch-stream=*}}?

> Patching regression between WFCore 2.0.0.Alpha9 and Alpha11
> -----------------------------------------------------------
>
>                 Key: WFCORE-865
>                 URL: https://issues.jboss.org/browse/WFCORE-865
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Patching 
>    Affects Versions: 2.0.0.Alpha11
>            Reporter: Ladislav Thon
>            Assignee: Alexey Loubyansky
>         Attachments: test-patch-10.0.0.Alpha5.zip, test-patch-10.0.0.Alpha6.zip
>
>
> With WildFly 10.0.0.Alpha5 (Core 2.0.0.Alpha9):
> {code}
> ./wildfly-10.0.0.Alpha5/bin/jboss-cli.sh --command="patch apply test-patch-10.0.0.Alpha5.zip"
> {
>     "outcome" : "success",
>     "result" : {}
> }
> ./wildfly-10.0.0.Alpha5/bin/jboss-cli.sh --command="patch history"
> {
>     "outcome" : "success",
>     "result" : [{
>         "patch-id" : "test-patch",
>         "type" : "cumulative",
>         "applied-at" : "8/4/15 9:07 AM"
>     }]
> }
> ./wildfly-10.0.0.Alpha5/bin/jboss-cli.sh --command="patch info"
> Version:             undefined  
> Cumulative patch ID: test-patch 
> One-off patches:     none       
> {code}
> With WildFly 10.0.0.Alpha6 (Core 2.0.0.Alpha11):
> {code}
> ./wildfly-10.0.0.Alpha6/bin/jboss-cli.sh --command="patch apply test-patch-10.0.0.Alpha6.zip"
> {
>     "outcome" : "success",
>     "result" : {}
> }
> ./wildfly-10.0.0.Alpha6/bin/jboss-cli.sh --command="patch history"
> {
>     "outcome" : "success",
>     "result" : []
> }
> ./wildfly-10.0.0.Alpha6/bin/jboss-cli.sh --command="patch info"
> Version:             undefined 
> Cumulative patch ID: base      
> One-off patches:     none      
> {code}
> With WildFly 10.0.0.Alpha6, based on {{patch history}} and {{patch info}}, it looks like the patch doesn't even apply, but that's not actually true, because trying to apply the patch once again results in
> {code}
> WFLYPAT0039: Requested WildFly version 10.0.0.Alpha6 did not match the installed version 10.0.0.Alpha6_PATCHED
> {code}
> So the patch in fact _is_ installed, it's just that neither {{patch history}} nor {{patch info}} doesn't show it like it used to.
> The only reason I could come up with is that I use {{EAP}} as the {{<upgrade name="...">}}:
> {code}
> <upgrade name="EAP" version="10.0.0.Alpha6" to-version="10.0.0.Alpha6_PATCHED"/>
> {code}
> However:
> 1. This used to work just fine in WildFly 10.0.0.Alpha5 and before.
> 2. If this is now considered wrong, the patch shouldn't even apply in the first place.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)