Community
Participate
Working Groups
Check Out As.. operation is a two-step process. Firstly it creates something using New Wizard, then checks out repositary stuff into the new container. There is no way (at least, easy way) to do any adjustment of checked out resources. It would be nice to be notified about that to let cusom code to do some extra work which is maybe needed because New Wizard at the moment of the new container creation does not have any idea about the components from the repository that are going to be checked out.
I'm not 100% sure what you are asking for here. Are you asking for API that allows you to participate in the CVS Checkout process? If so, then perhaps it would be better to describe in some detail what you are trying to do. From that, we can try to come up with poetential solutions.
Yes, you are right. My problem is that when Eclipse invokes my New Wizard, the last one does not know anything about the context. User is also may be not well informed about the content of the project she checks out. So wizard can perform just some generic work. In my case this is a New Project wizard. Besides other work it has to create in the project some specific resourses-components. In many cases I have a collision of these new created resources and those that are checked out at the next step. I would like to correct the final result to make new project consistent, but I do not have a chance to partisipate in this process. Or, in theory I can do it by listening all workspace events and detecting those that should be correct. But this is quite expensive and not simple to implement. Would it be a sort of notificator that lets me know that check out operation has been finished, it could solve the described problem.
This is a known issue (I thought we already had a bug for it but I couldn't find it). As of yet, we have not been able to come up with a good solution.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
