This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 174379 - issues debugging mutli project scenarios
Summary: issues debugging mutli project scenarios
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-12 17:15 UTC by pbelbin
Modified: 2009-10-16 13:36 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pbelbin 2009-10-12 17:15:49 UTC
While debugging an app, I need to add a method.

the update button gets pressed, but the log shows that the update was not able to be pushed because the jvm does not 
allow signature changes while updating.

so, I go and use the 'deploy' on the project context menu.

now, the project has been updated, but, I am unable to place a breakpoint on some of the code.

it appears that the push of code via 'deploy' is different than that which gets pushed when using 'update' and now the 
two are out of sync, and the ide / jvm say that I am unable to put a debug statement on a line of code.

I have to restart the app server, undeploy the app, then redeploy afresh in order to clean the mess up so that 
everything is in sync.

note: yes, I'm using 'deploy' rather than 'debug' from the project menu.

I am working a situation where there are 6 web apps deployed, and I want to debug all of them, so I'm not just 
choosing 'debug' on a single app, since they all have to be present on the server.

I 'deploy' each of them to the server, then use the 'debug' menu option to 'connect' to the running app server.

bottom line:

deploy should clean out anything that the update button pushes out, so that the jvm sees only one definition of any 
given class.

as it is, the current solution is to restart the app server, do a 'clean and build' on the project that's affected, 
then 'deploy' it again.

it's a pain to have to do that, and, very time consuming.
Comment 1 Petr Jiricka 2009-10-15 13:47:01 UTC
Assigning to the deployment infrastructure for evaluation.
Comment 2 Petr Hejl 2009-10-16 13:36:51 UTC
I can't reproduce it. Please provide the exact steps to reproduce.

I tried:
1) create & deploy two web projects
2) run second one in debug mode
3) changed one method incompatibly and used "Apply code changes" - it fails
4) used deploy
5) put breakpoint on changed line
6) breakpoint ok