Quantcast

Go To Type and Project Groups

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Go To Type and Project Groups

Mitch Claborn-2
I recently did a code fork, and am now working on two almost identical
sets of code for different clients. I am using Net Beans Project Groups
to separate the two sets of code.  When I do a Navigate -> Go to Type
(ctrl + o) and type in the name of a class that exists in both sets of
code, the dialog lists both of them, even though one of them resides in
a project that is not open in the current Project Group.

This is confusing to me, and a bit dangerous, as it would be fairly easy
to select the wrong one and work on the wrong set of code. Is this a
bug, or the intended behavior.  For my vote, I'd rather Go to Type only
show classes from projects in the current Project Group.


--

Mitch

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Go To Type and Project Groups

wadechandler
Administrator
My opinion a bug unless it is in a dependency they share. If a bug, you should file one, and I agree with your initial assessment.

Wade

On Jan 13, 2017 10:43 AM, "Mitch Claborn" <[hidden email]> wrote:
I recently did a code fork, and am now working on two almost identical sets of code for different clients. I am using Net Beans Project Groups to separate the two sets of code.  When I do a Navigate -> Go to Type (ctrl + o) and type in the name of a class that exists in both sets of code, the dialog lists both of them, even though one of them resides in a project that is not open in the current Project Group.

This is confusing to me, and a bit dangerous, as it would be fairly easy to select the wrong one and work on the wrong set of code. Is this a bug, or the intended behavior.  For my vote, I'd rather Go to Type only show classes from projects in the current Project Group.


--

Mitch


====================
Wade Chandler

Software Engineer
NetBeans and Open Source Contributor
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Go To Type and Project Groups

wadechandler
Administrator
My opinion a bug unless it is in a dependency they share. If a bug, you should file one, and I agree with your initial assessment.

Wade

On Jan 13, 2017 10:43 AM, "Mitch Claborn" <[hidden email]> wrote:
I recently did a code fork, and am now working on two almost identical sets of code for different clients. I am using Net Beans Project Groups to separate the two sets of code.  When I do a Navigate -> Go to Type (ctrl + o) and type in the name of a class that exists in both sets of code, the dialog lists both of them, even though one of them resides in a project that is not open in the current Project Group.

This is confusing to me, and a bit dangerous, as it would be fairly easy to select the wrong one and work on the wrong set of code. Is this a bug, or the intended behavior.  For my vote, I'd rather Go to Type only show classes from projects in the current Project Group.


--

Mitch



====================
Wade Chandler

Software Engineer
NetBeans and Open Source Contributor
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Go To Type and Project Groups

Mitch Claborn-2

https://netbeans.org/bugzilla/show_bug.cgi?id=269574


Mitch
On 01/15/2017 10:31 AM, Wade Chandler wrote:
My opinion a bug unless it is in a dependency they share. If a bug, you should file one, and I agree with your initial assessment.

Wade

On Jan 13, 2017 10:43 AM, "Mitch Claborn" <[hidden email]> wrote:
I recently did a code fork, and am now working on two almost identical sets of code for different clients. I am using Net Beans Project Groups to separate the two sets of code.  When I do a Navigate -> Go to Type (ctrl + o) and type in the name of a class that exists in both sets of code, the dialog lists both of them, even though one of them resides in a project that is not open in the current Project Group.

This is confusing to me, and a bit dangerous, as it would be fairly easy to select the wrong one and work on the wrong set of code. Is this a bug, or the intended behavior.  For my vote, I'd rather Go to Type only show classes from projects in the current Project Group.


--

Mitch



Loading...