anonymous wrote :
| I don't really understand the point you're making or what you are asking (did
you read or understand my other comments in this thread ?)
|
Yes - but i'm simply trying to figure out why I don't see this issue and how many
other deployers will have this issue.
I fully understand what you are saying about how Tomcat (and as far as I understand other
WTP deployers apparently perform).
I just can't reproduce this error and thus I'm asking you if
a) this occurs with other deployers too
b) did you see leftover artifacts when using our jboss deployer
If a and b then this is most likely limited only to possible issues in jstpublisher, if a
and not b or not and b then it is some issue specific to our tooling.
anonymous wrote :
| So my suggestion is to allow the temporary directory where that file copy is performed
to be a configurable thing, this way JBossTools-AS can still use PublishUtil class and can
instruct it to use a directory like /opt/jboss-4.2.1.GA/server/default/tmp/jbosstools-as/
this making the temporary path
./opt/jboss-4.2.1.GA/server/default/tmp/jbosstools-as/tmp12345.tmp in the above
hypothetical situation.
And we can't perform that change since it won't be ready in a WTP release in time;
so we probably need to fork PublishUtil to make it work.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094971#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...