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 195034 - Files are transferred twice to remote host when building a dependent project
Summary: Files are transferred twice to remote host when building a dependent project
Status: RESOLVED WONTFIX
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-03 16:14 UTC by Vladimir Kvashin
Modified: 2012-10-30 21:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2011-02-03 16:14:20 UTC 
Consider the following situation:
there is a project App that depend on another project - Lib,
and in App properties "build" checkbox is set for Lib.

If I build Lib once, all necessary files are transferred to remote host.
If I build it once more without changing it, no files are transferred (and there will be no compilation on remote host as well).

But if after that I build App, IDE will invalidate these files once again and send them once more and build Lib once more too.

That's incorrect. There is a complain from users on cnd user forum in this respect.
Comment 1 Vladimir Kvashin 2011-02-03 16:17:11 UTC 
Each project stores info about all controlled files and their states in its own location, this is the root cause of the issue.
Comment 2 Leonid Lenyashin 2012-10-30 21:09:40 UTC 
There was no activity on this issue for quite a long time. We apologize that the issue was not addressed so far due to lack of development resources. We might not have time in near future to fix this problem, so it is closed as WONTFIX.
If the issue is still critical for you please do not hesitate to REOPEN it.
Thank you for using our product and reporting bugs. We are really sorry that we were not able to fix this issue timely.

Regards,
CND team.