Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » This compilation unit is not on the build path of a Java Project error
This compilation unit is not on the build path of a Java Project error [message #75032] Wed, 08 June 2005 00:15 Go to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
I created a project from CVS checkout. I went to a class file and opened. I
began to change the imports statment when this message appears. I assumed
that I needed to update the build path. The problem is that I do not have a
Java Build Path properties page in the project properties. What am I doing
wrong?
Re: This compilation unit is not on the build path of a Java Project error [message #75042 is a reply to message #75032] Wed, 08 June 2005 01:15 Go to previous messageGo to next message
Adam Kiezun is currently offline Adam KiezunFriend
Messages: 219
Registered: July 2009
Senior Member
Rick Kirch wrote:
> I created a project from CVS checkout. I went to a class file and opened. I
> began to change the imports statment when this message appears. I assumed
> that I needed to update the build path. The problem is that I do not have a
> Java Build Path properties page in the project properties. What am I doing
> wrong?
>
>

is it a java project? I guess not. Try checking out again, as Java project.

/adam
Re: This compilation unit is not on the build path of a Java Project error [message #75086 is a reply to message #75042] Wed, 08 June 2005 05:01 Go to previous messageGo to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
Yes it is a Java project.

"Adam Kiezun" <akiezun@mit.edu> wrote in message
news:d85gs4$fqn$1@news.eclipse.org...
> Rick Kirch wrote:
>> I created a project from CVS checkout. I went to a class file and opened.
>> I began to change the imports statment when this message appears. I
>> assumed that I needed to update the build path. The problem is that I do
>> not have a Java Build Path properties page in the project properties.
>> What am I doing wrong?
>
> is it a java project? I guess not. Try checking out again, as Java
> project.
>
> /adam
Re: This compilation unit is not on the build path of a Java Project error [message #75259 is a reply to message #75086] Wed, 08 June 2005 11:52 Go to previous messageGo to next message
Adam Kiezun is currently offline Adam KiezunFriend
Messages: 219
Registered: July 2009
Senior Member
hmm, a Java project with no build path properties page. that's bizarre.
do you have .classpath and .project files in there? what do they say?

/adam

Rick Kirch wrote:
> Yes it is a Java project.
>
> "Adam Kiezun" <akiezun@mit.edu> wrote in message
> news:d85gs4$fqn$1@news.eclipse.org...
>
>>Rick Kirch wrote:
>>
>>>I created a project from CVS checkout. I went to a class file and opened.
>>>I began to change the imports statment when this message appears. I
>>>assumed that I needed to update the build path. The problem is that I do
>>>not have a Java Build Path properties page in the project properties.
>>>What am I doing wrong?
>>
>>is it a java project? I guess not. Try checking out again, as Java
>>project.
>>
>>/adam
>
>
>
Re: This compilation unit is not on the build path of a Java Project error [message #75379 is a reply to message #75032] Wed, 08 June 2005 15:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipse.rizzoweb.com

Rick Kirch wrote:
> I created a project from CVS checkout. I went to a class file and opened. I
> began to change the imports statment when this message appears. I assumed
> that I needed to update the build path. The problem is that I do not have a
> Java Build Path properties page in the project properties. What am I doing
> wrong?

Do you really mean to say that you tried to edit the .class file, or was
that a typo? You an not edit .class files, you edit the source .java files.

HTH,
Eric
Re: This compilation unit is not on the build path of a Java Project error [message #75514 is a reply to message #75259] Wed, 08 June 2005 17:21 Go to previous messageGo to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
I have four pages in the project properties: Info, Builders, CVS, and
Project References.

"Adam Kiezun" <akiezun@mit.edu> wrote in message
news:d86m6i$nvi$1@news.eclipse.org...
> hmm, a Java project with no build path properties page. that's bizarre.
> do you have .classpath and .project files in there? what do they say?
>
> /adam
>
> Rick Kirch wrote:
>> Yes it is a Java project.
>>
>> "Adam Kiezun" <akiezun@mit.edu> wrote in message
>> news:d85gs4$fqn$1@news.eclipse.org...
>>
>>>Rick Kirch wrote:
>>>
>>>>I created a project from CVS checkout. I went to a class file and
>>>>opened. I began to change the imports statment when this message
>>>>appears. I assumed that I needed to update the build path. The problem
>>>>is that I do not have a Java Build Path properties page in the project
>>>>properties. What am I doing wrong?
>>>
>>>is it a java project? I guess not. Try checking out again, as Java
>>>project.
>>>
>>>/adam
>>
>>
Re: This compilation unit is not on the build path of a Java Project error [message #75530 is a reply to message #75514] Wed, 08 June 2005 17:23 Go to previous messageGo to next message
Adam Kiezun is currently offline Adam KiezunFriend
Messages: 219
Registered: July 2009
Senior Member
Rick Kirch wrote:
> I have four pages in the project properties: Info, Builders, CVS, and
> Project References.

it looks like it's not a Java Project.

Does your .project file contain the following line:
<nature>org.eclipse.jdt.core.javanature</nature>
?

/adam
Re: This compilation unit is not on the build path of a Java Project error [message #75547 is a reply to message #75530] Wed, 08 June 2005 17:28 Go to previous messageGo to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
There is a .project file under the main CVS/Workspace folder that contains
the following:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>java</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>

"Adam Kiezun" <akiezun@mit.edu> wrote in message
news:d879j3$jg0$1@news.eclipse.org...
> Rick Kirch wrote:
>> I have four pages in the project properties: Info, Builders, CVS, and
>> Project References.
>
> it looks like it's not a Java Project.
>
> Does your .project file contain the following line:
> <nature>org.eclipse.jdt.core.javanature</nature>
> ?
>
> /adam
Re: This compilation unit is not on the build path of a Java Project error [message #75563 is a reply to message #75547] Wed, 08 June 2005 17:45 Go to previous messageGo to next message
Adam Kiezun is currently offline Adam KiezunFriend
Messages: 219
Registered: July 2009
Senior Member
so like I said, not a Java Project (in the eclipse sense). So I assume
this project was not created by eclipse, for eclipse development. It's
easy to fix.
Check it out again, and this time select "Check Out As...", select the
"check out as project configured using the New Project Wizard" and then
select Java Project and you're done.

If the .project file *is* in CVS and does not contain the line I
mentioned, then try using the procedure described in
thread "Converting normal project to a java project" from 5/31/2005

BTW, how do compile the code now? ANT? Make?
/adam
Re: This compilation unit is not on the build path of a Java Project error [message #75597 is a reply to message #75563] Wed, 08 June 2005 18:12 Go to previous messageGo to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
That worked, so thanks. But now another error has come up. I navigate to
the class file I want to edit in the Package Explorer, double click on the
file and get the following error:
Cannot open default editor on <filename>. Editor could not be initialized.

Then if I click the + next to the file I get :
A virtual machine error has occurred. < more standard verbiage about
shutting down or you will get more errors>

Now, if I start Eclipse back up and just click the + sign on my .java file,
I get the following:
An internal error occurred during: "Decoration Calculation".
java.lang.InternalError: jzentry == 0,
jzfile = 8536880,
total = 12919,
name = C:\Program Files\Java\jre1.5.0_03\lib\rt.jar,
i = 7285,
message = invalid LOC header (bad signature)
java.util.zip.ZipFile$3.nextElement(Unknown Source)
java.util.zip.ZipFile$3.nextElement(Unknown Source)
org.eclipse.jdt.internal.core.JarPackageFragmentRoot.compute Children(JarPackageFragmentRoot.java:84)
org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStruc ture(PackageFragmentRoot.java:173)
org.eclipse.jdt.internal.core.Openable.generateInfos(Openabl e.java:183)
org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(Jav aElement.java:572)
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(Jav aElement.java:309)
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(Jav aElement.java:295)
org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaEl ement.java:250)
org.eclipse.jdt.internal.core.JavaProjectElementInfo.getPack ageFragmentsInRoots(JavaProjectElementInfo.java:224)
org.eclipse.jdt.internal.core.JavaProjectElementInfo.getAllP ackageFragments(JavaProjectElementInfo.java:180)
org.eclipse.jdt.internal.core.JavaProject.newNameLookup(Java Project.java:2209)
org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:53)
org.eclipse.jdt.internal.core.JavaProject.newSearchableNameE nvironment(JavaProject.java:2227)
org.eclipse.jdt.internal.core.hierarchy.HierarchyBuilder.<init >(HierarchyBuilder.java:81)
org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyB uilder. <init>(IndexBasedHierarchyBuilder.java:96)
org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.comput e(TypeHierarchy.java:316)
org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refres h(TypeHierarchy.java:1242)
org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.e xecuteOperation(CreateTypeHierarchyOperation.java:90)
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaMod elOperation.java:700)
org.eclipse.jdt.internal.core.JavaModelOperation.runOperatio n(JavaModelOperation.java:739)
org.eclipse.jdt.internal.core.SourceType.newSupertypeHierarc hy(SourceType.java:604)
org.eclipse.jdt.internal.core.SourceType.newSupertypeHierarc hy(SourceType.java:556)
org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache .getTypeHierarchy(SuperTypeHierarchyCache.java:95)
org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache .getTypeHierarchy(SuperTypeHierarchyCache.java:81)
org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.getOverri deIndicators(OverrideIndicatorLabelDecorator.java:159)
org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.computeAd ornmentFlags(OverrideIndicatorLabelDecorator.java:127)
org.eclipse.jdt.ui.OverrideIndicatorLabelDecorator.decorate( OverrideIndicatorLabelDecorator.java:238)
org.eclipse.ui.internal.decorators.LightweightDecoratorDefin ition.decorate(LightweightDecoratorDefinition.java:155)
org.eclipse.ui.internal.decorators.LightweightDecoratorManag er$LightweightRunnable.run(LightweightDecoratorManager.java: 60)
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:616)
org.eclipse.core.runtime.Platform.run(Platform.java:747)
org.eclipse.ui.internal.decorators.LightweightDecoratorManag er.decorate(LightweightDecoratorManager.java:258)
org.eclipse.ui.internal.decorators.LightweightDecoratorManag er.getDecorations(LightweightDecoratorManager.java:241)
org.eclipse.ui.internal.decorators.DecorationScheduler$1.run (DecorationScheduler.java:285)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)




"Adam Kiezun" <akiezun@mit.edu> wrote in message
news:d87are$lgj$1@news.eclipse.org...
> so like I said, not a Java Project (in the eclipse sense). So I assume
> this project was not created by eclipse, for eclipse development. It's
> easy to fix.
> Check it out again, and this time select "Check Out As...", select the
> "check out as project configured using the New Project Wizard" and then
> select Java Project and you're done.
>
> If the .project file *is* in CVS and does not contain the line I
> mentioned, then try using the procedure described in
> thread "Converting normal project to a java project" from 5/31/2005
>
> BTW, how do compile the code now? ANT? Make?
> /adam
Re: This compilation unit is not on the build path of a Java Project error [message #75632 is a reply to message #75597] Wed, 08 June 2005 19:01 Go to previous messageGo to next message
Adam Kiezun is currently offline Adam KiezunFriend
Messages: 219
Registered: July 2009
Senior Member
never seen this. Did you just hack the .project file? If so, errors like
that can happen because it's not the proper way :)

what's in your .classpath file?
can you send me the project?

/adam
Re: This compilation unit is not on the build path of a Java Project error [message #75687 is a reply to message #75632] Wed, 08 June 2005 19:28 Go to previous messageGo to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
I did not do anything with the .project file

classpath contents as follows:

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path=""/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="output" path=""/>
</classpath>

If you are referring to source code when you ask for the project...I cannot
even begin to tell you the horrors that would happen to me if I did that.
;-)


"Adam Kiezun" <akiezun@mit.edu> wrote in message
news:d87f9j$r4e$1@news.eclipse.org...
> never seen this. Did you just hack the .project file? If so, errors like
> that can happen because it's not the proper way :)
>
> what's in your .classpath file?
> can you send me the project?
>
> /adam
Re: This compilation unit is not on the build path of a Java Project error [message #75720 is a reply to message #75687] Wed, 08 June 2005 19:33 Go to previous messageGo to next message
Rick Kirch is currently offline Rick KirchFriend
Messages: 7
Registered: July 2009
Junior Member
One more thing. This is the .log entry for the crash on clicking on the +:

!SESSION Jun 08, 2005
11:18:49.775 ---------------------------------------------
eclipse.buildId=M200503110845
java.version=1.5.0_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.jdt.core 4 4 Jun 08, 2005 11:18:49.775
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.InternalError: jzentry == 0,
jzfile = 8536880,
total = 12919,
name = C:\Program Files\Java\jre1.5.0_03\lib\rt.jar,
i = 7285,
message = invalid LOC header (bad signature)
at java.util.zip.ZipFile$3.nextElement(Unknown Source)
at java.util.zip.ZipFile$3.nextElement(Unknown Source)
at
org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIn dex.execute(AddJarFileToIndex.java:175)
at
org.eclipse.jdt.internal.core.search.processing.JobManager.r un(JobManager.java:363)
at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.ui 4 4 Jun 08, 2005 11:19:42.571
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 Jun 08, 2005 11:19:42.571
!MESSAGE jzentry == 0,
jzfile = 8536880,
total = 12919,
name = C:\Program Files\Java\jre1.5.0_03\lib\rt.jar,
i = 7285,
message = invalid LOC header (bad signature)
!STACK 0
java.lang.InternalError: jzentry == 0,
jzfile = 8536880,
total = 12919,
name = C:\Program Files\Java\jre1.5.0_03\lib\rt.jar,
i = 7285,
message = invalid LOC header (bad signature)
at java.util.zip.ZipFile$3.nextElement(Unknown Source)
at java.util.zip.ZipFile$3.nextElement(Unknown Source)
at
org.eclipse.jdt.internal.core.JarPackageFragmentRoot.compute Children(JarPackageFragmentRoot.java:84)
at
org.eclipse.jdt.internal.core.PackageFragmentRoot.buildStruc ture(PackageFragmentRoot.java:173)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openabl e.java:183)
at
org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(Jav aElement.java:572)
at
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(Jav aElement.java:309)
at
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(Jav aElement.java:295)
at
org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaEl ement.java:250)
at
org.eclipse.jdt.internal.core.JavaProjectElementInfo.getPack ageFragmentsInRoots(JavaProjectElementInfo.java:224)
at
org.eclipse.jdt.internal.core.JavaProjectElementInfo.getAllP ackageFragments(JavaProjectElementInfo.java:180)
at
org.eclipse.jdt.internal.core.JavaProject.newNameLookup(Java Project.java:2209)
at
org.eclipse.jdt.internal.core.JavaProject.newNameLookup(Java Project.java:2220)
at
org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:64)
at
org.eclipse.jdt.internal.core.JavaProject.newSearchableNameE nvironment(JavaProject.java:2235)
at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.p rocess(CompilationUnitProblemFinder.java:149)
at
org.eclipse.jdt.internal.core.CompilationUnit.buildStructure (CompilationUnit.java:146)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openabl e.java:183)
at
org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(Jav aElement.java:572)
at
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(Jav aElement.java:309)
at
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(Jav aElement.java:295)
at
org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaEl ement.java:250)
at
org.eclipse.jdt.ui.StandardJavaElementContentProvider.getChi ldren(StandardJavaElementContentProvider.java:179)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerConte ntProvider.getChildren(PackageExplorerContentProvider.java:1 30)
at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$ PackageExplorerProblemTreeViewer.getFilteredChildren(Package ExplorerPart.java:239)
at
org.eclipse.jface.viewers.StructuredViewer.getSortedChildren (StructuredViewer.java:585)
at
org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractT reeViewer.java:359)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.jface.viewers.AbstractTreeViewer.createChildren( AbstractTreeViewer.java:342)
at
org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpan d(AbstractTreeViewer.java:754)
at
org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded( AbstractTreeViewer.java:765)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:179)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:820)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:805)
at org.eclipse.swt.widgets.Tree.wmNotifyChild(Tree.java:2074)
at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4002)
at org.eclipse.swt.widgets.Composite.WM_NOTIFY(Composite.java:7 22)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3019 )
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3339 )
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:139 7)
at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:170)
at org.eclipse.swt.widgets.Tree.WM_LBUTTONDOWN(Tree.java:1668)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3001 )
at org.eclipse.swt.widgets.Display.windowProc(Display.java:3339 )
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:14 73)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2430)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:335)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
at org.eclipse.core.launcher.Main.run(Main.java:704)
at org.eclipse.core.launcher.Main.main(Main.java:688)

"Rick Kirch" <Rick.Kirch@Ticketmaster.com> wrote in message
news:d87gsr$t67$1@news.eclipse.org...
>I did not do anything with the .project file
>
> classpath contents as follows:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> <classpathentry kind="src" path=""/>
> <classpathentry kind="con"
> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="output" path=""/>
> </classpath>
>
> If you are referring to source code when you ask for the project...I
> cannot even begin to tell you the horrors that would happen to me if I did
> that. ;-)
>
>
> "Adam Kiezun" <akiezun@mit.edu> wrote in message
> news:d87f9j$r4e$1@news.eclipse.org...
>> never seen this. Did you just hack the .project file? If so, errors like
>> that can happen because it's not the proper way :)
>>
>> what's in your .classpath file?
>> can you send me the project?
>>
>> /adam
>
>
Re: This compilation unit is not on the build path of a Java Project error [message #75753 is a reply to message #75687] Wed, 08 June 2005 19:36 Go to previous message
Adam Kiezun is currently offline Adam KiezunFriend
Messages: 219
Registered: July 2009
Senior Member
> If you are referring to source code when you ask for the project...I
cannot
> even begin to tell you the horrors that would happen to me if I did
that.
> ;-)

:)
i give up, i don't know what can be causing the problem you're seeing.

this https://bugs.eclipse.org/bugs/show_bug.cgi?id=78913
would indicate you have a corrupted zip somehow.
I'd reinstall eclipse and try again.
/adam

Rick Kirch wrote:
> I did not do anything with the .project file
>
> classpath contents as follows:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> <classpathentry kind="src" path=""/>
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="output" path=""/>
> </classpath>
>
> If you are referring to source code when you ask for the project...I cannot
> even begin to tell you the horrors that would happen to me if I did that.
> ;-)
>
>
> "Adam Kiezun" <akiezun@mit.edu> wrote in message
> news:d87f9j$r4e$1@news.eclipse.org...
>
>>never seen this. Did you just hack the .project file? If so, errors like
>>that can happen because it's not the proper way :)
>>
>>what's in your .classpath file?
>>can you send me the project?
>>
>>/adam
>
>
>
Previous Topic:Working Remotely
Next Topic:Problems in building a project
Goto Forum:
  


Current Time: Wed Nov 26 03:33:50 GMT 2014

Powered by FUDForum. Page generated in 0.02206 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software