Community
Participate
Working Groups
Now to support "tracking of third-party sources" as defined in Cederqvist cvs manual there is the need of external tools like wincvs or similar that support cvs import command. Eclipse should provide such support so that projects that need "tracking of third-party sources" function can be supported entirely within it.
This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if you feel this is still an important issue.
Michael, who was supposed to touch it? I'm sorry i'm really busy with my job and i have no time to contribute other than testing eclipse during my duty. For us it is still an issue, we have contractors working for us and we have to track third party sources during our normal work, and we still need to use wincvs to perform this function. Am i the only one to have this need? I hoped it would find its way through 3.1 schedule, would it now be possible to include it in 3.2 schedule? Thanks, Gabriele.
No one was supposed to touch it. The problem is that the number of Team/CVS bugs has reached an unmanageable level so I closed any bug that haddened been touched in two years since it was an easy metric to use. As for this particular bug, although I agree that it is an important issue, there is currently no plan to address it. The workaround, of course, is to perform what I assume is a relatively infrequent import using the comand line tool.
I would like to reopen this enhancement request. Tracking eclipse sources is a bummer with command lines. Support for CVS import and vendor branch is an impotant CVS feature. I may be able to contribute a patch sometimes. Thanks!
RESOLVED LATER does not imply that the enhancement is closed. It's just a means of bookkeeping to indicate that the component maintainers do not plan to address this item. It will be reopened if this changes (and supplying a patch is the best way to change this).
Any hope for 3.2 for this? Thanks, Gabriele
There's two main reasons why this bug has not been addressed. The first is that we just don't have the manpower to address every issue. The second is that we don't work with third party sources in the traditional CVS way so we don't really have a good feel for how to surface this functionality in Eclipse. If you want to see this bug addressed, a good start would be to describe how you work with third party sources and how you would expect the functionality to be sirfaced in Eclipse. Of course, if you provided a patch, that would really increase the chances of this getting into 3.2;-) I'm reopeing this issue since it is a valuable feature. However, I can't guarantee that it will make it into 3.2. for the reasons stated.
Hi Michael, here we have different types of projects. 1- Those completely developed in our site for which eclipse behaviour of adding the resources to an empty cvs project when sharing an already populated project is enough. 2- Those developed outside by contactors that give us the sources when there is a new release and that we track using the cvs 'Import' command. This gives the added benefit that source is automatically imported in a vendor branch and allows to merge with no pain any local changes, still keeping vendor releases history clean of any local mod. For the second case we need to use line command or a graphical tool like wincvs because eclipse miss that function. As for how eclipse should handle this, i have few suggestions. Normally for eclipse sources must be first part of an opened project before going to repository. For Import it is different, third party sources belongs to a project, but they can become part of an opened project only after they are imported FIRST in repository and then merged back to the opened project itself. This means that eclipse should be able to handle those sources to be imported as an external entity not yet part of a project. (I don't even understand myself what i wrote, but my english doesn't allow me to express better the concept. I hope that your english will be sufficiently better than mine :) to grasp a sense from the above mess) Regards, Gabriele
I put my vote for this issue, but I also like to describe how I do it now. Context: development of PHP web software, partly based on existing third-party sources. Initial: I make a separate branch for the third-party code, so that the original code lives on its own branch. Upgrades: I make a new project for the updated sources, and get a local copy of the new sources (can be a CVS/SVN download, then "disconnect" it from the source). I then set the default keyword expansion in Eclipse to "no expansion" (-ko), and use "Share project, CVS, to add the source to the existing module and branch. In the last part of the wizard, I uncheck "Launch the Commit wizard". I then have a project in Eclipse with the changes in the third-party sources marked. I go through them, add new files to version control, and eventually do an "Override and commit" to get the new sources in, then place a tag for the new version. (The compare function in Eclipse doesn't handle these compares very well, so I use a different tool for that, to compare with another checked out version of the vendor branch) Next, upgrading my own version of things is a matter of a normal Eclipse "merge" operation, with the vendor branch as the source, and the previous vendor version tag as the starting point. Not sure if this is *The Way*, but it seems to work for me :-) (In reply to comment #0) > Now to support "tracking of third-party sources" as defined in Cederqvist cvs > manual there is the need of external tools like wincvs or similar that support > cvs import command. > Eclipse should provide such support so that projects that need "tracking of > third-party sources" function can be supported entirely within it. (In reply to comment #0) > Now to support "tracking of third-party sources" as defined in Cederqvist cvs > manual there is the need of external tools like wincvs or similar that support > cvs import command. > Eclipse should provide such support so that projects that need "tracking of > third-party sources" function can be supported entirely within it. (In reply to comment #8) > Hi Michael, > here we have different types of projects. > 1- Those completely developed in our site for which eclipse behaviour of adding > the resources to an empty cvs project when sharing an already populated project > is enough. > 2- Those developed outside by contactors that give us the sources when there is > a new release and that we track using the cvs 'Import' command. This gives the > added benefit that source is automatically imported in a vendor branch and > allows to merge with no pain any local changes, still keeping vendor releases > history clean of any local mod. > > For the second case we need to use line command or a graphical tool like wincvs > because eclipse miss that function. > > As for how eclipse should handle this, i have few suggestions. Normally for > eclipse sources must be first part of an opened project before going to > repository. > For Import it is different, third party sources belongs to a project, but they > can become part of an opened project only after they are imported FIRST in > repository and then merged back to the opened project itself. > This means that eclipse should be able to handle those sources to be imported > as an external entity not yet part of a project. > > (I don't even understand myself what i wrote, but my english doesn't allow me > to express better the concept. I hope that your english will be sufficiently > better than mine :) to grasp a sense from the above mess) > > Regards, Gabriele >
From an earlier comment: ------- Comment #9 From Rolf Kleef 2006-05-07 09:14 [reply] ------- Thank you very much, Rolf, for the exellent discription of a workaround. I too would like to see this feature. I am a developer on some open source projects, and many times I can just submit a fix back into the project itself. But we also have code that we add that is specific to our project and wouldn't go back into the community project, so this would be a very welcome feature to eclipse. I can voluteer to help on this. I have lots of programming experience, but I will gladly help in testing too.
There is currently no plan to address this item. Patches will be accepted.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
