On Tuesday 13 June 2006 20:10, Qasim Rasheed wrote:
Not to contradict the usefulness of SVN, there is a plugin for VSS that you
use within Eclipse which essentially gives you all the feature from VSS IDE
that you are accustomed to.
But only on Windows.
--
Tom Chiverton
Qasim Rasheed wrote:
Not to contradict the usefulness of SVN, there is a plugin for VSS that you
use within Eclipse which essentially gives you all the feature from VSS IDE
that you are accustomed to.
And in addition you get a few 'features' you are not accustomed too.
If you have VSS
LOL. I'm pushing to move away from VSS for many more reasons than the
availability of an Eclipse plugin, so sticking with VSS just isn't an
option. Regardless of the attractiveness of these features you've
so eloquently described.
On 6/14/06, Jochem van Dieten [EMAIL PROTECTED] wrote:
Qasim
On Monday 12 June 2006 18:25, Rob Wilkerson wrote:
customers. Ideally, I'd like to extract only the modified files from
the source control repository so I can then just roll them up in a
tarball without any additional weeding of what's in and what's out.
Should be easy enough, you ask SVN for
I just experimented with tagging just a handful of files (i tried three) and
then I replaced the project with the 'tag' and all I had was the necessary
folder tree and the files I had tagged!
This would then make a nice neat distribution.
(I suspect this is what the 'patch' wizard in eclipse may
On Tuesday 13 June 2006 09:43, Michael Traher wrote:
At the risk of crazy people joining the thread eclipse does have very nice
source control tools CVS built in and SVN as a plugin.
Heh :-)
(CVS support is a plugin too, just happens to ship with the base Eclipse
distribution).
--
Tom
Michael, it sounds like you tried exactly what I'm looking to do, but
I need to clarify since you used terminology that I'm not familiar
with (read: non-VSS terms). I assume tagging is labeling, but
what do you mean you replaced the project? I need to tag a few
selected files and then extract -
:-) yes, each of these source systems has a language all its own!
Fortunately CVS and SVN have the same root so thats one mercy.
The project is all stored in the repository (all versions since you first
created it there or committed your existing source files for the first
time).
In eclipse (and
I think it does and it means that SVN offers a capability that VSS is
fundamentally lacking. That will make selling this change much
easier. Thanks for your help.
On 6/13/06, Michael Traher [EMAIL PROTECTED] wrote:
:-) yes, each of these source systems has a language all its own!
Fortunately
I found the greatest aid to selling CVS/SVN was the price :-)
On 6/13/06, Rob Wilkerson [EMAIL PROTECTED] wrote:
I think it does and it means that SVN offers a capability that VSS is
fundamentally lacking. That will make selling this change much
easier. Thanks for your help.
On 6/13/06,
True, but in this case we already own VSS so cost is less of a factor.
I have to sell added value and less-than-absurd conversion costs. To
that end, any conversion resources anyone could offer would be great.
Also, any selling points on the value added side would be helpful.
On 6/13/06,
(At the further risk of crazy people) what IDE are you using, because I
found that easy of use for the development team is a key factor. That is
what prompted us to switch to eclipse. There are other clients, and good
ones, but for me having it integrated in the ide was key. With eclipse all
your
Most of my people use CFEclipse. I have one CFStudio/HS+ holdover.
The integration points via the SVN plugin were just one of the
attractions of moving to SVN from VSS.
On 6/13/06, Michael Traher [EMAIL PROTECTED] wrote:
(At the further risk of crazy people) what IDE are you using, because I
Not to contradict the usefulness of SVN, there is a plugin for VSS that you
use within Eclipse which essentially gives you all the feature from VSS IDE
that you are accustomed to.
HTH
Qasim
On 6/13/06, Rob Wilkerson [EMAIL PROTECTED] wrote:
Most of my people use CFEclipse. I have one
I actually have two questions, here. The first is fairly specific,
the second a general request for advice:
1. How do you all handle source code labels for hotfix files? Are
there any so-called best practices? I have a large application which
occasionally requires hotfixes (I know, I'm
If I understand #1 properly then what we do (using CVS but principals are
the same) is;
change n files to do the fix
test
apply a tag to entire project
checkout entire project using tag, to a temp folder
use rsync to update the production site - only n files will actually be
copied
I have
I think you understand what I'm trying to do, but the key difference
is that we have a product. The modified files must be distributed to
customers. Ideally, I'd like to extract only the modified files from
the source control repository so I can then just roll them up in a
tarball without any
On 6/12/06, Rob Wilkerson [EMAIL PROTECTED] wrote:
I think you understand what I'm trying to do, but the key difference
is that we have a product. The modified files must be distributed to
customers. Ideally, I'd like to extract only the modified files from
the source control repository so
Oh yeah, and SVN makes/applies patches as well, forgot to mention.
~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:243281
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription:
Oh yeah, and I think this was discussed earlier, but you could use
md5 hashes of the files, and a DB, to check for differences between
what was, and what is.
Totally bypasses the source control method, could still use a zip tho.
:den
On 6/12/06, Denny Valliant [EMAIL PROTECTED] wrote:
Oh yeah,
20 matches
Mail list logo
