[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6879) BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12550972#action_12550972 ] 

Rob Stryker commented on JBIDE-6879:
------------------------------------

I would not use the standard wtp package for this. The standard wtp instance only supports local deployment, not remote. It also does not allow certain logging of exceptions and errors. It's a very simple utility class in the standard package. This one is a bit better.

I'm also quite sure I never put the API message in the class, and it was in whatever upstream file I copied and modified. I don't believe it's relevant at all. 

Also, since this is regarding publishing to JBoss AS servers, it only makes sense that it uses a utility class specifically geared to publishing to jboss servers in the jboss AS-Tools plugin ;) 

Basically, the API is pretty solid, I don't expect it to change, and I'll make a note in the class that people are actually using it ;) 

> BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-6879
>                 URL: https://jira.jboss.org/browse/JBIDE-6879
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: bpel
>    Affects Versions: 3.2.0.M2
>            Reporter: Robert (Bob) Brodt
>            Assignee: Robert (Bob) Brodt
>             Fix For: 3.2.0.Beta
>
>
> Like the comments in PublishCopyUtili say: 
>  * This class/interface is part of an interim API that is still under development and expected to
>  * change significantly before reaching stability. It is being made available at this early stage to solicit feedback
>  * from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken
>  * (repeatedly) as the API evolves.
> the bpel deployer package probably shouldn't be using this class, but should be using the standard WTP API instead.
> I've made a quick fix for now to get us through M2, but this needs to be addressed before final release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira