| Is SVN coherent (for Eclipse 3.5) [message #28044] |
Wed, 17 June 2009 02:02  |
Eclipse User |
|
|
|
Hi
I'm trying to check out IMP from SVN under Eclipse 3.5RC5 and getting a variety
of errors, no doubt some of them of my own making, but (amongst many others):
LEGCompiler complains that functionDeclaration cannot be found. Seems reasonable since only
IFunctionDeclaration , functionDeclaration0 and functionDeclaration1 are available.
IMPWizardPage complains that TypeSelectionDialog2 from a jdt internal package does
not exist.
The first looks like an SVN incoherency, the latter like an Eclipse 3.5 incompatibility.
Any clues?
Regards
Ed Willink
|
|
|
| Re: Is SVN coherent (for Eclipse 3.5) [message #28979 is a reply to message #28044] |
Tue, 14 July 2009 12:17  |
| Eclipse User |
|
|
|
Ed Willink wrote:
> Hi
>
> I'm trying to check out IMP from SVN under Eclipse 3.5RC5 and getting a
> variety
> of errors, no doubt some of them of my own making, but (amongst many
> others):
>
> LEGCompiler complains that functionDeclaration cannot be found. Seems
> reasonable since only
> IFunctionDeclaration , functionDeclaration0 and functionDeclaration1 are
> available.
I'll have to look at this, but I suspect that some errors in the LEG
project and/or templates may have crept in in recent months (just before
or after the EclipseCon tutorial). These shouldn't be show-stoppers, but
I can see where they'd be annoying and/or confusing.
> IMPWizardPage complains that TypeSelectionDialog2 from a jdt internal
> package does
> not exist.
I did some work recently to address two issues (I reported on this work
in a message to the imp-dev mailing list last month):
1) Reduce IMP's dependencies on internal (non-API) classes, like the
abovementioned TypeSelectionDialog2.
2) Remove the IMP runtime feature's dependence on the JDT.
The 1st issue has been partially addressed.
The 2nd issue has been addressed by:
- rewriting the offending classes to use API where possible
- copying a few bits of utility code from the JDT, and
- moving the remaining classes to a couple of new plugins, namely,
org.eclipse.imp.java.hosted and org.eclipse.imp.ui.explorer.
The changes have been checked into SVN HEAD, but have not been formally
released yet.
> The first looks like an SVN incoherency, the latter like an Eclipse 3.5
> incompatibility.
--
Cheers,
-- Bob
--------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center
IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
X10: Productive High-Performance Parallel Programming (http://x10.sf.net)
|
|
|
| Re: Is SVN coherent (for Eclipse 3.5) [message #575911 is a reply to message #28044] |
Tue, 14 July 2009 12:17 |
| Eclipse User |
|
|
|
Ed Willink wrote:
> Hi
>
> I'm trying to check out IMP from SVN under Eclipse 3.5RC5 and getting a
> variety
> of errors, no doubt some of them of my own making, but (amongst many
> others):
>
> LEGCompiler complains that functionDeclaration cannot be found. Seems
> reasonable since only
> IFunctionDeclaration , functionDeclaration0 and functionDeclaration1 are
> available.
I'll have to look at this, but I suspect that some errors in the LEG
project and/or templates may have crept in in recent months (just before
or after the EclipseCon tutorial). These shouldn't be show-stoppers, but
I can see where they'd be annoying and/or confusing.
> IMPWizardPage complains that TypeSelectionDialog2 from a jdt internal
> package does
> not exist.
I did some work recently to address two issues (I reported on this work
in a message to the imp-dev mailing list last month):
1) Reduce IMP's dependencies on internal (non-API) classes, like the
abovementioned TypeSelectionDialog2.
2) Remove the IMP runtime feature's dependence on the JDT.
The 1st issue has been partially addressed.
The 2nd issue has been addressed by:
- rewriting the offending classes to use API where possible
- copying a few bits of utility code from the JDT, and
- moving the remaining classes to a couple of new plugins, namely,
org.eclipse.imp.java.hosted and org.eclipse.imp.ui.explorer.
The changes have been checked into SVN HEAD, but have not been formally
released yet.
> The first looks like an SVN incoherency, the latter like an Eclipse 3.5
> incompatibility.
--
Cheers,
-- Bob
--------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center
IDE Meta-tooling Platform Project Lead (http://www.eclipse.org/imp)
X10: Productive High-Performance Parallel Programming (http://x10.sf.net)
|
|
|
Powered by
FUDForum. Page generated in 0.03635 seconds
Home