[jbosstools-issues] [JBoss JIRA] (JBIDE-23274) Rename of batch artefact should affect batch.xml file

[Jeff MAURY (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-23274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff MAURY updated JBIDE-23274:
-------------------------------
    Fix Version/s: 4.6.x
                       (was: 4.5.x)


> Rename of batch artefact should affect batch.xml file
> -----------------------------------------------------
>
>                 Key: JBIDE-23274
>                 URL: https://issues.jboss.org/browse/JBIDE-23274
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: batch
>    Affects Versions: 4.4.2.AM1
>            Reporter: Lukáš Valach
>            Assignee: Jeff MAURY
>             Fix For: 4.6.x
>
>         Attachments: BatchRenameManualTest.zip
>
>
> There are three ways how to refer batch artefact in job.xml file. 
> * Using @Name annotation
> * Using fully qualified class name
> * Using batch.xml
> I noticed that the class name is not changed in batch.xml file during refactoring and the job.xml file become invalid for this reason.
> There is a way how to avoid this problem. User can check the "Update fully qualified names in non-Java text files" option in Rename window, but this solution is not intuitive/is not user friendly I think.
> In another case, when I don't use batch.xml and use the name comming from @Named annotation. The artefact is renamed in job.xml file even if the "Update fully qualified names in non-Java text files" option aren't selected. Non-Java text file (job.xml) is updated automatically in this case.
> There is attached project that you can use to reproduce this problem.
> [^BatchRenameManualTest.zip]. Just try to rename Writer class.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)