[kepler-dev] [Bug 5538] New: Eclipse uses different .class files from ant run

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Sat Nov 12 18:56:25 PST 2011


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5538

             Bug #: 5538
           Summary: Eclipse uses different .class files from ant run
    Classification: Unclassified
           Product: Kepler
           Version: trunk
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: build system
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: cxh at eecs.berkeley.edu
         QAContact: kepler-dev at kepler-project.org


Kepler creates a separate target directory for .class files that are built
using ant and yet another target directory for .class files that are built
using Eclipse.  

Below are a series of problems with having .class files separate from the
.java files:
1) Since we look in the classpath for .java files, there is a chance that
the .java file that is returned will not correspond with the .java file
that was used to create the .class file.  For example, if there are two
implementations of Const actor, then there could be two Const.java files.
How do we know which one is the correct .java file?

2) The user is running two very different versions of Kepler when
they run "ant run" and when they invoke Kepler via Eclipse.

3) "Open Actor" fails in an Eclipse build. (I'll submit a separate bug
for this)

In my mind, the right thing to do is to generate the .class files in
one location, which would be in the src/ folder.

That would avoid the above problems.

I looked at changing the Eclipse .classpath file so that ptolemy/src
was included in the path, but adding the src folder via
Java Build Path -> Libraries -> Add Class Folder yields:
"Build path contains duplicate entry: 'src' for project 'ptolemy'"

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.


More information about the Kepler-dev mailing list