BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

"Build succeeded with 0 files built."

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> JBuilder IDE
View previous topic :: View next topic  
Author Message
Andrew n marshall
Guest





PostPosted: Sat Sep 13, 2003 6:19 pm    Post subject: "Build succeeded with 0 files built." Reply with quote



Yep... the above subject line is the status message I get when I try to
build a couple of files. I don't find "0 files" isn't very successful,
and right now it is incredibly annoying.


Here is the deal... the files in question are replacement classes for
one of the required libraries with the same package & class name (mostly
fixing scope modifiers so I can override them in another package, all
without mixing my changes with the original distribution). I'm guessing
it is finding the class in the library, a separate classpath than the
build classpath. Nonetheless, neither making nor rebuild the files will
produce any class files.


I've had this set up and working JBuilder for years now. Yesterday I
moved the project files into a new directory because of CVS changes. I
did not move the Classes directory (and related packages cache) thinking
it would rebuild in the new location No such luck.


Any ideas how to fix this?

Critical details:
JBuilder 8.0.140 Enterprise on both Mac OS X (new Java 1.4.1 release)
or Windows.
Gig of RAM, Multiple gigs free hard drive, yada yada...



Anm

Back to top
Lori M Olson (TeamB)
Guest





PostPosted: Sun Sep 14, 2003 8:43 pm    Post subject: Re: "Build succeeded with 0 files built." Reply with quote



Andrew n marshall wrote:
Quote:

Yep... the above subject line is the status message I get when I try to
build a couple of files. I don't find "0 files" isn't very successful,
and right now it is incredibly annoying.


Here is the deal... the files in question are replacement classes for
one of the required libraries with the same package & class name (mostly
fixing scope modifiers so I can override them in another package, all
without mixing my changes with the original distribution). I'm guessing
it is finding the class in the library, a separate classpath than the
build classpath. Nonetheless, neither making nor rebuild the files will
produce any class files.


I've had this set up and working JBuilder for years now. Yesterday I
moved the project files into a new directory because of CVS changes. I
did not move the Classes directory (and related packages cache) thinking
it would rebuild in the new location No such luck.


Any ideas how to fix this?

Critical details:
JBuilder 8.0.140 Enterprise on both Mac OS X (new Java 1.4.1 release)
or Windows.
Gig of RAM, Multiple gigs free hard drive, yada yada...



Anm


Are you talking about replacement "classes" or replacement "source files"?

If they are classes, then they should just be placed in the required
library you are talking about, but "ahead" of the jar file ("Add" it to
the Class tab of the Required Library, then use "Move Up").

If they are source files, and this isn't working...hmmm, weird. As a
work around, you could unroll your required library jar file into a
directory, point the required library at that directory, and delete the
classes you are "replacing".

--

Regards,

Lori Olson (TeamB)

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html



Back to top
Andrew n marshall
Guest





PostPosted: Tue Sep 16, 2003 4:24 pm    Post subject: Re: "Build succeeded with 0 files built." Reply with quote




Replacement source files, in your terms. Deleteing files is what I was
trying to avoid, but your suggestion did work. I'll use it for now, but
still open to solution that don't require dropping to Finder or command
line.

Anm


Lori M Olson (TeamB) wrote:

Quote:
Andrew n marshall wrote:


Yep... the above subject line is the status message I get when I try
to build a couple of files. I don't find "0 files" isn't very
successful, and right now it is incredibly annoying.


Here is the deal... the files in question are replacement classes for
one of the required libraries with the same package & class name
(mostly fixing scope modifiers so I can override them in another
package, all without mixing my changes with the original
distribution). I'm guessing it is finding the class in the library, a
separate classpath than the build classpath. Nonetheless, neither
making nor rebuild the files will produce any class files.


I've had this set up and working JBuilder for years now. Yesterday I
moved the project files into a new directory because of CVS changes.
I did not move the Classes directory (and related packages cache)
thinking it would rebuild in the new location No such luck.


Any ideas how to fix this?

Critical details:
JBuilder 8.0.140 Enterprise on both Mac OS X (new Java 1.4.1
release) or Windows.
Gig of RAM, Multiple gigs free hard drive, yada yada...



Anm


Are you talking about replacement "classes" or replacement "source files"?

If they are classes, then they should just be placed in the required
library you are talking about, but "ahead" of the jar file ("Add" it to
the Class tab of the Required Library, then use "Move Up").

If they are source files, and this isn't working...hmmm, weird. As a
work around, you could unroll your required library jar file into a
directory, point the required library at that directory, and delete the
classes you are "replacing".




Back to top
Andrew n marshall
Guest





PostPosted: Tue Sep 16, 2003 4:24 pm    Post subject: Re: "Build succeeded with 0 files built." Reply with quote


Replacement source files, in your terms. Deleteing files is what I was
trying to avoid, but your suggestion did work. I'll use it for now, but
still open to solution that don't require dropping to Finder or command
line.

Anm


Lori M Olson (TeamB) wrote:

Quote:
Andrew n marshall wrote:


Yep... the above subject line is the status message I get when I try
to build a couple of files. I don't find "0 files" isn't very
successful, and right now it is incredibly annoying.


Here is the deal... the files in question are replacement classes for
one of the required libraries with the same package & class name
(mostly fixing scope modifiers so I can override them in another
package, all without mixing my changes with the original
distribution). I'm guessing it is finding the class in the library, a
separate classpath than the build classpath. Nonetheless, neither
making nor rebuild the files will produce any class files.


I've had this set up and working JBuilder for years now. Yesterday I
moved the project files into a new directory because of CVS changes.
I did not move the Classes directory (and related packages cache)
thinking it would rebuild in the new location No such luck.


Any ideas how to fix this?

Critical details:
JBuilder 8.0.140 Enterprise on both Mac OS X (new Java 1.4.1
release) or Windows.
Gig of RAM, Multiple gigs free hard drive, yada yada...



Anm


Are you talking about replacement "classes" or replacement "source files"?

If they are classes, then they should just be placed in the required
library you are talking about, but "ahead" of the jar file ("Add" it to
the Class tab of the Required Library, then use "Move Up").

If they are source files, and this isn't working...hmmm, weird. As a
work around, you could unroll your required library jar file into a
directory, point the required library at that directory, and delete the
classes you are "replacing".




Back to top
Ryan Ackley
Guest





PostPosted: Tue Sep 16, 2003 7:49 pm    Post subject: Re: "Build succeeded with 0 files built." Reply with quote

This is a weird coincidence, because this just started to happen with me
with my upgrade to JBuilder 8 Enterprise. If I rebuild a class that I
haven't changed since my last rebuild, it deletes the class file in the
output path and I get the following meesage "Build succeeded with 0 files
built." Class file stays deleted.

We use a network drive that holds copies of the latest committed class
files. This network drive is in our classpath. Our sourcepath is a copy of
this network directory tree containing writable copies of the classes we are
working on. I think somehow the dependency checker is getting these mixed
up. This setup has worked since version 3.5 of JBuilder.

I re-installed JBuilder, I re-created my project from scratch. I still have
the same problem...


Back to top
Hans-Bernhard Broeker
Guest





PostPosted: Wed Sep 17, 2003 2:19 pm    Post subject: Re: "Build succeeded with 0 files built." Reply with quote

In borland.public.jbuilder.ide Ryan Ackley <sackley (AT) cfl (DOT) rr.com> wrote:

Quote:
We use a network drive that holds copies of the latest committed
class files. This network drive is in our classpath. Our sourcepath
is a copy of this network directory tree containing writable copies
of the classes we are working on. I think somehow the dependency
checker is getting these mixed up.

I wouldn't say that this really is a mixup. You *do* still have that
class file available, after all (on the network drive in the
classpath), and it's newer than its source file, right? So you don't
really need a freshly compiled copy, do you?

Seems to me like the new behaviour you judge incorrect makes more
sense than the one you had before.

--
Hans-Bernhard Broeker (broeker (AT) physik (DOT) rwth-aachen.de)
Even if all the snow were burnt, ashes would remain.

Back to top
Ryan Ackley
Guest





PostPosted: Wed Sep 17, 2003 5:43 pm    Post subject: Re: "Build succeeded with 0 files built." Reply with quote


Quote:
I wouldn't say that this really is a mixup. You *do* still have that
class file available, after all (on the network drive in the
classpath), and it's newer than its source file, right?

Wrong, it is not newer than its source file. This is the problem. The source
I am compiling is the newer version that is on my local drive. It does not
create a newer class, so the only class it finds is the old class from the
network drive.

BTW, I've discovered that this problem is confined to certain packages.



Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> JBuilder IDE All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.