Multiple users using different NetBeans versions on same project.

[pjdevries]

Hi,

I'm working on a project with a colleague. My colleague is also the project manager. For various reasons, he wants to stick to NB 6.7. For various other reasons, he does not want to use a version control system.

I want to start using Git. Git is supported in NB 7.1. Suppose I upgrade to NB 7.1 and my colleague keeps using NB 6.7. What kind of problems can we expect when we start exchanging projects?

[javydreamercsw]

I don't want to start arguing about why he's not using version control but if both are developing at the same time on the same files is just a matter of time before hell breaks loose.

I mean, it can be done but I bet you'll spend more time doing manual merges than actually coding, been there done that.

Stuff like the following I used to see:

1. "His" code not compiling with yours
2. Unable to reproduce build reliably
3. Track changes and perform peer reviews will be burdensome to say the least
   

[pjdevries]

Thanks for your reply.

No use arguing. Unfortunately that's the way it is. He's the boss and he decides not to use it. We've been working without a vcs for about 4 years now and I haven't been able to convince him. I'm currently using BeyondCompare to facilitate the merges.

I want to move ahead and at least use Git on my local system. For each new release, I will have to add his version as a separate branch in my Git repo and then merge my development branch and his into HEAD. But I need to be sure I don't get into all kinds of problems, when using the resulting version in two different NB versions again. I guess most important is that we use the same JDK. But other than that, do you (or anyone else for that matter) think I can expect serious problems?

[Javier Ortiz]

Using the same JDK will help for sure. Most of the problems will come due to logistics, i.e. last minute changes that work on his but not on yours or vice versa or a big amount of changes to merge manually. Until he sees the amount of work and time wasted he won't change his mind.

Do you guys have requirements to track changes and versions? Need to rebuild the code in a certain state for debugging or something like that?

Is hard to visualize a programmer without VCS unless it is a really small project with small amount of developers (2). If that's the case when that increases your amount of issues will also.

IMHO is better to build on solid ground for the future. Just my 2 cents...



Senior Software Quality Engineer
ArthroCare Corporation
7000 William Cannon Drive
Austin, TX 78735
Phone: 512-358-5996
email: address-removed


-----Original Message-----
From: pjdevries [mailto:address-removed]
Sent: Tuesday, November 29, 2011 3:43 AM
To: address-removed
Subject: [nbusers] Multiple users using different NetBeans versions on same project.

Thanks for your reply.

No use arguing. Unfortunately that's the way it is. He's the boss and he decides not to use it. We've been working without a vcs for about 4 years now and I haven't been able to convince him. I'm currently using BeyondCompare to facilitate the merges.

I want to move ahead and at least use Git on my local system. For each new release, I will have to add his version as a separate branch in my Git repo and then merge my development branch and his into HEAD. But I need to be sure I don't get into all kinds of problems, when using the resulting version in two different NB versions again. I guess most important is that we use the same JDK. But other than that, do you (or anyone else for that matter) think I can expect serious problems?




**********

The information contained in this e-mail message, together with any
attachments thereto, is intended only for the personal and confidential
use of the addressee named above. The message and the attachments
are or may be privileged or protected communication. If you are not the
intended recipient of this message, or authorized to receive it for the
intended recipient, you have received this message in error, and you
are not to review, use, disseminate, distribute or copy this message,
any attachments thereto, or their contents. If you have received this
message in error, please immediately notify us by return e-mail
message, and delete the original message.

Pursuant to Circular 230 issued by the United States Treasury
Department and relating to practice before the Internal Revenue
Services, any comment or opinion in this communication relating to a
federal tax issue is not intended to be used, and cannot be used, by a
taxpayer for the purpose of avoiding tax-related penalties that may be
imposed on the taxpayer.

[pjdevries]

Thanks for your 2 cents Javier.

Let me emphasize once more that using a VCS is not an option. For me yes, but not for the team. I am very much aware of all the advantages of using one and the disadvantages of doing without. But unfortunately it's not my call.

Although it is quite a big project, we are working on it with just the two of us. And even though merging development branches without a VCS is cumbersome, we managed to do that for almost 4 years, without any serious problems yet.

Maybe I just gave too much information when starting this topic The issue is not whether to use a VCS or not. The question is: can I exchange projects between different NB versions (6.7 and 7.1 in my particular case), without running into all kinds of trouble.

[Javier Ortiz]

Potentially no, there are changes done in the background when you open projects in different versions. Also I can't guarantee that a project done on 7.1 is backwards compatible with 6.7. Both need to use the same IDE and JDK for starters, if not you are asking for trouble from the start.



Senior Software Quality Engineer
ArthroCare Corporation
7000 William Cannon Drive
Austin, TX 78735
Phone: 512-358-5996
email: address-removed


-----Original Message-----
From: pjdevries [mailto:address-removed]
Sent: Wednesday, November 30, 2011 1:43 AM
To: address-removed
Subject: [nbusers] Multiple users using different NetBeans versions on same project.

Thanks for your 2 cents Javier.

Let me emphasize once more that using a VCS is not an option. For me yes, but not for the team. I am very much aware of all the advantages of using one and the disadvantages of doing without. But unfortunately it's not my call.

Although it is quite a big project, we are working on it with just the two of us. And even though merging development branches without a VCS is cumbersome, we managed to do that for almost 4 years, without any serious problems yet.

Maybe I just gave too much information when starting this topic The issue is not whether to use a VCS or not. The question is: can I exchange projects between different NB versions (6.7 and 7.1 in my particular case), without running into all kinds of trouble.




**********

The information contained in this e-mail message, together with any
attachments thereto, is intended only for the personal and confidential
use of the addressee named above. The message and the attachments
are or may be privileged or protected communication. If you are not the
intended recipient of this message, or authorized to receive it for the
intended recipient, you have received this message in error, and you
are not to review, use, disseminate, distribute or copy this message,
any attachments thereto, or their contents. If you have received this
message in error, please immediately notify us by return e-mail
message, and delete the original message.

Pursuant to Circular 230 issued by the United States Treasury
Department and relating to practice before the Internal Revenue
Services, any comment or opinion in this communication relating to a
federal tax issue is not intended to be used, and cannot be used, by a
taxpayer for the purpose of avoiding tax-related penalties that may be
imposed on the taxpayer.

[pjdevries]

Thanx again Javier.

I guess it's better not to take any chances I'll stick to 6.7.