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 143190 - "could not find file xxx to copy" on build
Summary: "could not find file xxx to copy" on build
Status: VERIFIED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-07 14:55 UTC by ymajoros
Modified: 2008-12-14 10:53 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 ymajoros 2008-08-07 14:55:07 UTC
When trying to "clean and build" project, in some cases, we get this message (on various computers, mostly for
EclipseLink library but sometimes for other libs):

D:\netbeans\workspace\Culture\Culture-ejb\nbproject\build-impl.xml:282: Warning: Could not find file
D:\netbeans\workspace\Culture\Culture-ejb\${libs.EclipseLink.classpath.libfile.2} to copy. 

Removing and re-adding the lib from the project seems to (temporarily) fix it.
Comment 1 Dusan Balek 2008-08-08 10:01:38 UTC
Not a javac problem. Reassigning to ejb project for evaluation.
Comment 2 David Konecny 2008-08-11 02:09:56 UTC
For 6.5 this was resolved and properties libs.<name>.classpath.libfile.<index> are not used anymore.

For 6.1 there can be several reasons for that. If you know more concrete scenario when does it happen I would be happy
to check it and give an advice on how to avoid it. Sounds like you are sharing project between different computers? Are
you using a Libraries Folder (project properties: libraries panel). Doing so should in general resolve the problem as
all binary jars are stored in libraries folder. Are all members of your team using the same version of NB?
Hypothetically if a library has different number of jars on classpath in different versions of NB that could result in
issue you are describing.
Comment 3 David Konecny 2008-08-26 03:27:47 UTC
Let me know if you need a help to resolve the problem in NB6.1.
Comment 4 ymajoros 2008-08-26 09:09:01 UTC
Yes, it would be useful. I does happen on at least a project which isn't shared across computers. We don't put lib files
in the project itself: there is a central libs repository, with sources and javadoc, shared by a lot of projects
Comment 5 David Konecny 2008-08-27 04:09:58 UTC
ymajoros, as I said I'm happy to help but I need to get as concrete scenario/problem description as possible.
Comment 6 ymajoros 2008-08-27 10:00:21 UTC
I can't reproduce it, sorry. It just happens sometimes, I can't say what the reason is. And it is on big projects with
many dependencies, I don't know how to reduce it to a simple test case. But I wouldn't say the issue is "resolved
fixed", it definitely happens, and quite often.
Comment 7 ymajoros 2008-08-27 10:01:41 UTC
I should add that just opening the project properties and clicking on "ok" does resolve the problem... until the next time.
Comment 8 David Konecny 2008-08-27 23:27:21 UTC
It was fixed in NB6.5 - the concept of copying files was completely removed from IDE and is done by Ant script which
simplified it. Because that change was not trivial (code change and build script change) I'm not sure it will be ever
backported to a patch release of 6.1
Comment 9 mvanek 2008-12-14 10:53:25 UTC
verified.
NetBeans IDE Dev (Build 200812080201)