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 10901 - [Win2K NB 3.2.16] Changing properties of Ant-file undoes changes since last commit.
Summary: [Win2K NB 3.2.16] Changing properties of Ant-file undoes changes since last c...
Status: CLOSED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-01 06:26 UTC by javaiware
Modified: 2003-06-30 14:46 UTC (History)
0 users

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 javaiware 2001-04-01 06:26:17 UTC
Hi,

When changing the properties of an Ant-file that is in a CVS filesystem, the 
file is retrieved from CVS and the changes are made in that version of the 
file, meanwhile overwriting all changes that were not yet committed to CVS.

I've got a local CVS repository.

Iwan
Comment 1 Jesse Glick 2001-04-02 15:30:51 UTC
If true this is serious. Does this only happen in conjunction with CVS? Could
you give me a precise sequence of steps to try? Also please mention build
number, and of course attach your ide.log if there is anything in it. Also for
Ant bugs, I highly recommend running the IDE with this switch:

-J-Dorg.apache.tools.ant.module=0

and then attaching your ide.log. This will greatly assist debugging.
Comment 2 javaiware 2001-04-03 16:01:51 UTC
I didn't see this problem yesterday while I was working with NB 3.2.18, and not 
sofar today, as I am working with NB 3.2.19, but before I switched to 18, I had 
a couple of times that when I opened a file, the latest version from CVS was 
displayed, instead of the working copy. This might be related to the fact that 
the CVS module has a hard time adding multiple files at once. I filed a bug for 
that as well (10911).
I will try to remember what I did, if it happens again, but sofar it didn't 
with 18 and 19.
Comment 3 Jesse Glick 2001-04-05 17:18:51 UTC
OK, marking unreproducible--naturally if it happens again in a current build,
reopen it.
Comment 4 Jesse Glick 2001-04-27 18:02:15 UTC
This is probably duplicate of a P1 which was fixed for release32--scripts do not
listen to changes after close & reopen.
Comment 5 Quality Engineering 2003-06-30 14:43:45 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.

Comment 6 Quality Engineering 2003-06-30 14:46:05 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.