On Thu, Apr 29, 2010 at 9:10 AM, elane pereira
>> Note that customizing Subclipse should be a last resort. Eclipse
>> gives you a lot of ways to extend other plugins. You ought to be able
>> to isolate your customizations in your own plugin and then extend
>> Subclipse. That way you do not have to maintain customizations and do
>> your own builds.
> Do you refer to extensions points?
> I have problems with synchronization of trunks and branches. To publish a new release is necessary a manual job to merge changes into trunk and branch realized for long period. My goal is create a clone trunk and a clone branch and when realize any commit to trunk, automatically commit to clone trunk and clone branch. The same for commit to branch implies in commit to clone trunk and clone branch. In this case, to publish a new release will necessary to merge only clone trunk and clone branch, if we need a manual job this will be less. Is possible using extension point for this?
An extension point is something that enables you to insert extra
functionality. So an extension point would not do all this for you,
but one or more could be added that would allow that functionality to
be added. Frankly though, I am highly skeptical that what you want to
do can be done.
It is not going to be possible to customize Subclipse to commit to two
locations. Subversion cannot do that. You should be looking at a
script that would automate the merging for you and then figure out if
you can run that script from a post-commit hook or a scheduled job
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2010-04-29 15:28:41 CEST