2.6.0 from 10-November lacking refactor?

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

2.6.0 from 10-November lacking refactor?

John Bito
Just wondering if it's me: I wanted to rename a method and clicking Refactor->Rename did nothing. I've had it fail before, but I don't remember it just closing the menu without invoking a dialog.

I thought this was working in the version I was using before yesterday, but I hadn't tried exactly what I did this morning.

Reply | Threaded
Open this post in threaded view
|

Re: 2.6.0 from 10-November lacking refactor?

Andrew Eisenberg
I just tried a few different ways to invoke rename-refactor on a
method and all of them have been successful.  Can you be a bit more
specific on the way you are invoking it?  (eg- from package explorer,
from editor, from menu, etc).  Also, have a look at the error log and
send over any errors that might be relevant.

On Fri, Nov 11, 2011 at 9:42 AM, John Bito <[hidden email]> wrote:
> Just wondering if it's me: I wanted to rename a method and clicking
> Refactor->Rename did nothing. I've had it fail before, but I don't remember
> it just closing the menu without invoking a dialog.
>
> I thought this was working in the version I was using before yesterday, but
> I hadn't tried exactly what I did this morning.
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: 2.6.0 from 10-November lacking refactor?

John Bito
After another restart of Eclipse, it started reporting errors: a problem with the build path left me with an unresolved, indirect dependency. There were no problem markers for it, but the error log is full of complaints about it. I've included one of the stack traces from the error log in case it's helpful. After adding beanutils to the build path, refactor is working as expected.

org.eclipse.jdt.internal.compiler.problem.AbortCompilation: Pb(324) The type org.apache.commons.beanutils.DynaBean cannot be resolved. It is indirectly referenced from required .class files
    at org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:122)
    at org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:187)
    at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.handle(ProblemReporter.java:1991)
    at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.isClassPathCorrect(ProblemReporter.java:3915)
    at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:54)
    at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:126)
    at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveTypesFor(BinaryTypeBinding.java:1080)
    at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.methods(BinaryTypeBinding.java:1052)
    at org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.initializeMembers(JDTClassNode.java:254)
    at org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.initialize(JDTClassNode.java:231)
    at org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.lazyClassInit(JDTClassNode.java:155)
    at org.codehaus.groovy.ast.ClassNode.getAnnotations(ClassNode.java:1549)
    at org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.getAnnotations(JDTClassNode.java:496)
    at org.codehaus.groovy.ast.ClassNode.getAnnotations(ClassNode.java:1548)
    at org.codehaus.groovy.eclipse.dsl.pointcuts.impl.FindAnnotationPointcut.explodeObject(FindAnnotationPointcut.java:57)
    at org.codehaus.groovy.eclipse.dsl.pointcuts.impl.FilteringPointcut.matches(FilteringPointcut.java:48)
    at org.codehaus.groovy.eclipse.dsl.pointcuts.AbstractPointcut.matchOnPointcutArgument(AbstractPointcut.java:118)
    at org.codehaus.groovy.eclipse.dsl.pointcuts.impl.CurrentTypePointcut.matches(CurrentTypePointcut.java:61)
    at org.codehaus.groovy.eclipse.dsl.DSLDStore.findContributions(DSLDStore.java:129)
    at org.codehaus.groovy.eclipse.dsl.lookup.DSLDTypeLookup.lookupTypeAndDeclaration(DSLDTypeLookup.java:68)
    at org.eclipse.jdt.groovy.search.AbstractSimplifiedTypeLookup.lookupType(AbstractSimplifiedTypeLookup.java:94)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.handleExpression(TypeInferencingVisitorWithRequestor.java:772)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitConstantExpression(TypeInferencingVisitorWithRequestor.java:1330)
    at org.codehaus.groovy.ast.expr.ConstantExpression.visit(ConstantExpression.java:75)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitMethodCallExpression(TypeInferencingVisitorWithRequestor.java:1415)
    at org.codehaus.groovy.ast.expr.MethodCallExpression.visit(MethodCallExpression.java:75)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitReturnStatement(CodeVisitorSupport.java:73)
    at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitReturnStatement(ClassCodeVisitorSupport.java:224)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitReturnStatement(TypeInferencingVisitorWithRequestor.java:1276)
    at org.codehaus.groovy.ast.stmt.ReturnStatement.visit(ReturnStatement.java:47)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitBlockStatement(CodeVisitorSupport.java:35)
    at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitBlockStatement(ClassCodeVisitorSupport.java:179)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitBlockStatement(TypeInferencingVisitorWithRequestor.java:1261)
    at org.codehaus.groovy.ast.stmt.BlockStatement.visit(BlockStatement.java:69)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitClosureExpression(CodeVisitorSupport.java:174)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitClosureExpression(TypeInferencingVisitorWithRequestor.java:1094)
    at org.codehaus.groovy.ast.expr.ClosureExpression.visit(ClosureExpression.java:43)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitListOfExpressions(CodeVisitorSupport.java:276)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitTupleExpression(CodeVisitorSupport.java:178)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitTupleExpression(TypeInferencingVisitorWithRequestor.java:1629)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitArgumentlistExpression(CodeVisitorSupport.java:286)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitArgumentlistExpression(TypeInferencingVisitorWithRequestor.java:916)
    at org.codehaus.groovy.ast.expr.ArgumentListExpression.visit(ArgumentListExpression.java:73)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitMethodCallExpression(TypeInferencingVisitorWithRequestor.java:1435)
    at org.codehaus.groovy.ast.expr.MethodCallExpression.visit(MethodCallExpression.java:75)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitExpressionStatement(CodeVisitorSupport.java:69)
    at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitExpressionStatement(ClassCodeVisitorSupport.java:209)
    at org.codehaus.groovy.ast.stmt.ExpressionStatement.visit(ExpressionStatement.java:40)
    at org.codehaus.groovy.ast.CodeVisitorSupport.visitBlockStatement(CodeVisitorSupport.java:35)
    at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitBlockStatement(ClassCodeVisitorSupport.java:179)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitBlockStatement(TypeInferencingVisitorWithRequestor.java:1261)
    at org.codehaus.groovy.ast.stmt.BlockStatement.visit(BlockStatement.java:69)
    at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitClassCodeContainer(ClassCodeVisitorSupport.java:102)
    at org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitConstructorOrMethod(ClassCodeVisitorSupport.java:113)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitConstructorOrMethod(TypeInferencingVisitorWithRequestor.java:655)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitJDT(TypeInferencingVisitorWithRequestor.java:399)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitJDT(TypeInferencingVisitorWithRequestor.java:245)
    at org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitCompilationUnit(TypeInferencingVisitorWithRequestor.java:200)
    at org.codehaus.groovy.eclipse.codebrowsing.requestor.CodeSelectHelper.select(CodeSelectHelper.java:57)
    at org.codehaus.jdt.groovy.model.GroovyCompilationUnit.codeSelect(GroovyCompilationUnit.java:503)
    at org.codehaus.jdt.groovy.model.GroovyCompilationUnit.codeSelect(GroovyCompilationUnit.java:495)
    at org.codehaus.jdt.groovy.model.GroovyCompilationUnit.codeSelect(GroovyCompilationUnit.java:490)
    at org.eclipse.jdt.internal.ui.text.java.hover.AbstractJavaEditorTextHover.getJavaElementsAt(AbstractJavaEditorTextHover.java:115)
    at org.codehaus.groovy.eclipse.editor.GroovyExtraInformationHover.getHoverInfo2(GroovyExtraInformationHover.java:85)
    at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:141)
    at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:82)
    at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)


On Fri, Nov 11, 2011 at 13:19, Andrew Eisenberg <[hidden email]> wrote:
I just tried a few different ways to invoke rename-refactor on a
method and all of them have been successful.  Can you be a bit more
specific on the way you are invoking it?  (eg- from package explorer,
from editor, from menu, etc).  Also, have a look at the error log and
send over any errors that might be relevant.

On Fri, Nov 11, 2011 at 9:42 AM, John Bito <[hidden email]> wrote:
> Just wondering if it's me: I wanted to rename a method and clicking
> Refactor->Rename did nothing. I've had it fail before, but I don't remember
> it just closing the menu without invoking a dialog.
>
> I thought this was working in the version I was using before yesterday, but
> I hadn't tried exactly what I did this morning.
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|

Re: 2.6.0 from 10-November lacking refactor?

Andrew Eisenberg
As you have realized, it looks like this problem is coming from an
incomplete classpath.  One of the binary classes that you reference in
one of your source files refers to another binary class that is not on
the classpath.  Therefore, when trying to parse the directly dependent
class file, there is a compilation problem due to the missing
transitive dependency.

Now the problem is that this compilation problem shouldn't be aborting
the entire compilation process.  Compilation should be able to
continue and fill in missing bindings for the pieces that come from
the missing dependency.  This is something to look into.

I guess that there's no chance you can share the project that is
giving you the problem?

On Sat, Nov 12, 2011 at 2:27 PM, John Bito <[hidden email]> wrote:

> After another restart of Eclipse, it started reporting errors: a problem
> with the build path left me with an unresolved, indirect dependency. There
> were no problem markers for it, but the error log is full of complaints
> about it. I've included one of the stack traces from the error log in case
> it's helpful. After adding beanutils to the build path, refactor is working
> as expected.
>
> org.eclipse.jdt.internal.compiler.problem.AbortCompilation: Pb(324) The type
> org.apache.commons.beanutils.DynaBean cannot be resolved. It is indirectly
> referenced from required .class files
>     at
> org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:122)
>     at
> org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:187)
>     at
> org.eclipse.jdt.internal.compiler.problem.ProblemReporter.handle(ProblemReporter.java:1991)
>     at
> org.eclipse.jdt.internal.compiler.problem.ProblemReporter.isClassPathCorrect(ProblemReporter.java:3915)
>     at
> org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:54)
>     at
> org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:126)
>     at
> org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveTypesFor(BinaryTypeBinding.java:1080)
>     at
> org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.methods(BinaryTypeBinding.java:1052)
>     at
> org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.initializeMembers(JDTClassNode.java:254)
>     at
> org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.initialize(JDTClassNode.java:231)
>     at
> org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.lazyClassInit(JDTClassNode.java:155)
>     at org.codehaus.groovy.ast.ClassNode.getAnnotations(ClassNode.java:1549)
>     at
> org.codehaus.jdt.groovy.internal.compiler.ast.JDTClassNode.getAnnotations(JDTClassNode.java:496)
>     at org.codehaus.groovy.ast.ClassNode.getAnnotations(ClassNode.java:1548)
>     at
> org.codehaus.groovy.eclipse.dsl.pointcuts.impl.FindAnnotationPointcut.explodeObject(FindAnnotationPointcut.java:57)
>     at
> org.codehaus.groovy.eclipse.dsl.pointcuts.impl.FilteringPointcut.matches(FilteringPointcut.java:48)
>     at
> org.codehaus.groovy.eclipse.dsl.pointcuts.AbstractPointcut.matchOnPointcutArgument(AbstractPointcut.java:118)
>     at
> org.codehaus.groovy.eclipse.dsl.pointcuts.impl.CurrentTypePointcut.matches(CurrentTypePointcut.java:61)
>     at
> org.codehaus.groovy.eclipse.dsl.DSLDStore.findContributions(DSLDStore.java:129)
>     at
> org.codehaus.groovy.eclipse.dsl.lookup.DSLDTypeLookup.lookupTypeAndDeclaration(DSLDTypeLookup.java:68)
>     at
> org.eclipse.jdt.groovy.search.AbstractSimplifiedTypeLookup.lookupType(AbstractSimplifiedTypeLookup.java:94)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.handleExpression(TypeInferencingVisitorWithRequestor.java:772)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitConstantExpression(TypeInferencingVisitorWithRequestor.java:1330)
>     at
> org.codehaus.groovy.ast.expr.ConstantExpression.visit(ConstantExpression.java:75)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitMethodCallExpression(TypeInferencingVisitorWithRequestor.java:1415)
>     at
> org.codehaus.groovy.ast.expr.MethodCallExpression.visit(MethodCallExpression.java:75)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitReturnStatement(CodeVisitorSupport.java:73)
>     at
> org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitReturnStatement(ClassCodeVisitorSupport.java:224)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitReturnStatement(TypeInferencingVisitorWithRequestor.java:1276)
>     at
> org.codehaus.groovy.ast.stmt.ReturnStatement.visit(ReturnStatement.java:47)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitBlockStatement(CodeVisitorSupport.java:35)
>     at
> org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitBlockStatement(ClassCodeVisitorSupport.java:179)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitBlockStatement(TypeInferencingVisitorWithRequestor.java:1261)
>     at
> org.codehaus.groovy.ast.stmt.BlockStatement.visit(BlockStatement.java:69)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitClosureExpression(CodeVisitorSupport.java:174)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitClosureExpression(TypeInferencingVisitorWithRequestor.java:1094)
>     at
> org.codehaus.groovy.ast.expr.ClosureExpression.visit(ClosureExpression.java:43)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitListOfExpressions(CodeVisitorSupport.java:276)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitTupleExpression(CodeVisitorSupport.java:178)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitTupleExpression(TypeInferencingVisitorWithRequestor.java:1629)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitArgumentlistExpression(CodeVisitorSupport.java:286)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitArgumentlistExpression(TypeInferencingVisitorWithRequestor.java:916)
>     at
> org.codehaus.groovy.ast.expr.ArgumentListExpression.visit(ArgumentListExpression.java:73)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitMethodCallExpression(TypeInferencingVisitorWithRequestor.java:1435)
>     at
> org.codehaus.groovy.ast.expr.MethodCallExpression.visit(MethodCallExpression.java:75)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitExpressionStatement(CodeVisitorSupport.java:69)
>     at
> org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitExpressionStatement(ClassCodeVisitorSupport.java:209)
>     at
> org.codehaus.groovy.ast.stmt.ExpressionStatement.visit(ExpressionStatement.java:40)
>     at
> org.codehaus.groovy.ast.CodeVisitorSupport.visitBlockStatement(CodeVisitorSupport.java:35)
>     at
> org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitBlockStatement(ClassCodeVisitorSupport.java:179)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitBlockStatement(TypeInferencingVisitorWithRequestor.java:1261)
>     at
> org.codehaus.groovy.ast.stmt.BlockStatement.visit(BlockStatement.java:69)
>     at
> org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitClassCodeContainer(ClassCodeVisitorSupport.java:102)
>     at
> org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitConstructorOrMethod(ClassCodeVisitorSupport.java:113)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitConstructorOrMethod(TypeInferencingVisitorWithRequestor.java:655)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitJDT(TypeInferencingVisitorWithRequestor.java:399)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitJDT(TypeInferencingVisitorWithRequestor.java:245)
>     at
> org.eclipse.jdt.groovy.search.TypeInferencingVisitorWithRequestor.visitCompilationUnit(TypeInferencingVisitorWithRequestor.java:200)
>     at
> org.codehaus.groovy.eclipse.codebrowsing.requestor.CodeSelectHelper.select(CodeSelectHelper.java:57)
>     at
> org.codehaus.jdt.groovy.model.GroovyCompilationUnit.codeSelect(GroovyCompilationUnit.java:503)
>     at
> org.codehaus.jdt.groovy.model.GroovyCompilationUnit.codeSelect(GroovyCompilationUnit.java:495)
>     at
> org.codehaus.jdt.groovy.model.GroovyCompilationUnit.codeSelect(GroovyCompilationUnit.java:490)
>     at
> org.eclipse.jdt.internal.ui.text.java.hover.AbstractJavaEditorTextHover.getJavaElementsAt(AbstractJavaEditorTextHover.java:115)
>     at
> org.codehaus.groovy.eclipse.editor.GroovyExtraInformationHover.getHoverInfo2(GroovyExtraInformationHover.java:85)
>     at
> org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:141)
>     at
> org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:82)
>     at
> org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)
>
>
> On Fri, Nov 11, 2011 at 13:19, Andrew Eisenberg <[hidden email]> wrote:
>>
>> I just tried a few different ways to invoke rename-refactor on a
>> method and all of them have been successful.  Can you be a bit more
>> specific on the way you are invoking it?  (eg- from package explorer,
>> from editor, from menu, etc).  Also, have a look at the error log and
>> send over any errors that might be relevant.
>>
>> On Fri, Nov 11, 2011 at 9:42 AM, John Bito <[hidden email]> wrote:
>> > Just wondering if it's me: I wanted to rename a method and clicking
>> > Refactor->Rename did nothing. I've had it fail before, but I don't
>> > remember
>> > it just closing the menu without invoking a dialog.
>> >
>> > I thought this was working in the version I was using before yesterday,
>> > but
>> > I hadn't tried exactly what I did this morning.
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Support for JDT Core 3.6.3?

Thomas Hofmann
In reply to this post by John Bito
Hi,
 
I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
 
Cannot complete the install because of a conflicting dependency.
  Software being installed: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110929-1700-e36)
  Only one of the following can be installed at once:
    Java Development Tools Core 3.6.2.xx-20110929-1700-e36 (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
    Java Development Tools Core 3.6.2.xx-20111107-1100-e36 (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
    Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x)
  Cannot satisfy dependency:
    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110929-1700-e36)
    To: org.codehaus.groovy.jdt.patch.feature.group [2.5.2.xx-20110929-1700-e36]
  Cannot satisfy dependency:
    From: JDT Core patch for Groovy-Eclipse plugin 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.jdt.patch.feature.group 2.5.2.xx-20110929-1700-e36)
    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
  Cannot satisfy dependency:
    From: Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A)
    To: org.eclipse.jdt.feature.group 3.4.0
  Cannot satisfy dependency:
    From: Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
  Cannot satisfy dependency:
    From: Eclipse Plug-in Development Environment 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL (org.eclipse.pde.feature.group 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
  Cannot satisfy dependency:
    From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
  Cannot satisfy dependency:
    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
  Optional dependency
 
I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
 
Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
 
Thanks, Thomas


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andy Clement
Hi,

> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.

There is no further work planned for 3.6. But as it appears to be an
RSA distribution that has the problem, that does perhaps increase the
importance of doing something here.  I'm not sure what fixes went in
that required a 3.6.3, but the cheapest feasible option is just to rev
our version numbers so that it will install into this environment - it
will effectively be downgrading JDT to 3.6.2 in the process but at
least it would install.  Perhaps raise a jira and let's see if it
attracts some votes.

cheers,
Andy

On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:

> Hi,
>
> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110929-1700-e36)
>  Only one of the following can be installed at once:
>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36 (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36 (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>    Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x)
>  Cannot satisfy dependency:
>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110929-1700-e36)
>    To: org.codehaus.groovy.jdt.patch.feature.group [2.5.2.xx-20110929-1700-e36]
>  Cannot satisfy dependency:
>    From: JDT Core patch for Groovy-Eclipse plugin 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.jdt.patch.feature.group 2.5.2.xx-20110929-1700-e36)
>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>  Cannot satisfy dependency:
>    From: Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A)
>    To: org.eclipse.jdt.feature.group 3.4.0
>  Cannot satisfy dependency:
>    From: Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>  Cannot satisfy dependency:
>    From: Eclipse Plug-in Development Environment 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL (org.eclipse.pde.feature.group 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>  Cannot satisfy dependency:
>    From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>  Cannot satisfy dependency:
>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>  Optional dependency
>
> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>
> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>
> Thanks, Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andrew Eisenberg
Unfortunately, it won't be that easy.

   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
Java Development Tools
3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
(org.eclipse.jdt.feature.group
3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)

This line implies that RSA ships with its own JDT core feature patch.
I don't know if it is possible to patch a feature patch.  But, if you
were to remove the  org.eclipse.jdt.R362patch.feature.group feature
patch, then I would imagine that the groovy-eclipse feature patch
would install.

However, of course, you would then lose any functionality and bug
fixes that the other feature patch adds for you.

I would first suggest that you play around with this and see if by
removing the other feature patch, you can get groovy-eclipse to
install.  You can try simply removing the other feature patch from the
features directory and then restart RSA with the -clean option.  You
may also need to remove the plugin from the plugins directory.  (I'd
recommend trying this out in a second instance of RSA so that you
don't disturb the instance you actually use).

Please let me know if you try this out and I can help you walk through
any other problems you may have.

On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:

> Hi,
>
>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>
> There is no further work planned for 3.6. But as it appears to be an
> RSA distribution that has the problem, that does perhaps increase the
> importance of doing something here.  I'm not sure what fixes went in
> that required a 3.6.3, but the cheapest feasible option is just to rev
> our version numbers so that it will install into this environment - it
> will effectively be downgrading JDT to 3.6.2 in the process but at
> least it would install.  Perhaps raise a jira and let's see if it
> attracts some votes.
>
> cheers,
> Andy
>
> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>> Hi,
>>
>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>
>> Cannot complete the install because of a conflicting dependency.
>>  Software being installed: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110929-1700-e36)
>>  Only one of the following can be installed at once:
>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36 (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36 (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>    Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x)
>>  Cannot satisfy dependency:
>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.eclipse.feature.feature.group 2.5.2.xx-20110929-1700-e36)
>>    To: org.codehaus.groovy.jdt.patch.feature.group [2.5.2.xx-20110929-1700-e36]
>>  Cannot satisfy dependency:
>>    From: JDT Core patch for Groovy-Eclipse plugin 2.5.2.xx-20110929-1700-e36 (org.codehaus.groovy.jdt.patch.feature.group 2.5.2.xx-20110929-1700-e36)
>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>  Cannot satisfy dependency:
>>    From: Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A)
>>    To: org.eclipse.jdt.feature.group 3.4.0
>>  Cannot satisfy dependency:
>>    From: Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>  Cannot satisfy dependency:
>>    From: Eclipse Plug-in Development Environment 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL (org.eclipse.pde.feature.group 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>  Cannot satisfy dependency:
>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>  Cannot satisfy dependency:
>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F (org.eclipse.jdt.feature.group 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>  Optional dependency
>>
>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>
>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>
>> Thanks, Thomas
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
Hi Andy,

I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.

I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.

This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.

If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.

Do you have any idea on how else this could be solved?

What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?

In my current installation which has the Groovy Plug-In installed I find the following:

Features:
org.eclipse.jdt.R342patch_1.0.15
org.eclipse.jdt.R342patch_1.0.19
org.eclipse.jdt.R361patch_1.0.0

Plug-ins:
org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar

So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.

When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.

Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.

As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.

Thomas


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
Sent: Montag, 21. November 2011 17:43
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

Unfortunately, it won't be that easy.

   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
(org.eclipse.jdt.feature.group
3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)

This line implies that RSA ships with its own JDT core feature patch.
I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.

However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.

I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).

Please let me know if you try this out and I can help you walk through any other problems you may have.

On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:

> Hi,
>
>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>
> There is no further work planned for 3.6. But as it appears to be an
> RSA distribution that has the problem, that does perhaps increase the
> importance of doing something here.  I'm not sure what fixes went in
> that required a 3.6.3, but the cheapest feasible option is just to rev
> our version numbers so that it will install into this environment - it
> will effectively be downgrading JDT to 3.6.2 in the process but at
> least it would install.  Perhaps raise a jira and let's see if it
> attracts some votes.
>
> cheers,
> Andy
>
> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>> Hi,
>>
>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>
>> Cannot complete the install because of a conflicting dependency.
>>  Software being installed: Groovy-Eclipse Feature
>> 2.5.2.xx-20110929-1700-e36
>> (org.codehaus.groovy.eclipse.feature.feature.group
>> 2.5.2.xx-20110929-1700-e36)
>>  Only one of the following can be installed at once:
>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>    Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core
>> 3.6.3.v_A77_R36x)
>>  Cannot satisfy dependency:
>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>> (org.codehaus.groovy.eclipse.feature.feature.group
>> 2.5.2.xx-20110929-1700-e36)
>>    To: org.codehaus.groovy.jdt.patch.feature.group
>> [2.5.2.xx-20110929-1700-e36]
>>  Cannot satisfy dependency:
>>    From: JDT Core patch for Groovy-Eclipse plugin
>> 2.5.2.xx-20110929-1700-e36
>> (org.codehaus.groovy.jdt.patch.feature.group
>> 2.5.2.xx-20110929-1700-e36)
>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>  Cannot satisfy dependency:
>>    From: Data Tools Platform JDT Enablement
>> 1.8.2.v201010181125-2-07w31211518181A
>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>> 1.8.2.v201010181125-2-07w31211518181A)
>>    To: org.eclipse.jdt.feature.group 3.4.0
>>  Cannot satisfy dependency:
>>    From: Eclipse Java Development Tools
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>> (org.eclipse.jdt.feature.group
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>  Cannot satisfy dependency:
>>    From: Eclipse Plug-in Development Environment
>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>> (org.eclipse.pde.feature.group
>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>  Cannot satisfy dependency:
>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>> (org.eclipse.jdt.feature.group
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>  Cannot satisfy dependency:
>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>> Java Development Tools
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>> (org.eclipse.jdt.feature.group
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>  Optional dependency
>>
>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>
>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>
>> Thanks, Thomas
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andrew Eisenberg
Hi Thomas,

OTDT uses a feature patch as well, so it would not be installable into
RSA either.  The JDT Weaving approach is not feasible for
Groovy-Eclipse because of the kinds of changes we need to make to JDT.
 JDT weaving (because it uses aspectj) requires well-defined pointcuts
to work, but these are not available for the places we need to plug in
to groovy-eclipse.

So, I really can't think of any easy fixes here.  Is there a 3.7-based
version of RSA that you can use?  Another possibility is that you can
manually change the platform.xml so that it points to the
groovy-eclipse version of JDT instead of the RSA version (you would
also need to download the groovy-eclipse udpate site as a zip).  As I
said, I'm not familiar with RSA, so I don't know how they manage their
artifacts and if you do change things manually, you may make it harder
to upgrade later, but this may be your only chance to get it working.

I wish I had a better answer for you.



On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann
<[hidden email]> wrote:

> Hi Andy,
>
> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>
> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>
> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>
> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>
> Do you have any idea on how else this could be solved?
>
> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>
> In my current installation which has the Groovy Plug-In installed I find the following:
>
> Features:
> org.eclipse.jdt.R342patch_1.0.15
> org.eclipse.jdt.R342patch_1.0.19
> org.eclipse.jdt.R361patch_1.0.0
>
> Plug-ins:
> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>
> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>
> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>
> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>
> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>
> Thomas
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
> Sent: Montag, 21. November 2011 17:43
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> Unfortunately, it won't be that easy.
>
>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse Java Development Tools 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
> (org.eclipse.jdt.feature.group
> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>
> This line implies that RSA ships with its own JDT core feature patch.
> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>
> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>
> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>
> Please let me know if you try this out and I can help you walk through any other problems you may have.
>
> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>> Hi,
>>
>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>
>> There is no further work planned for 3.6. But as it appears to be an
>> RSA distribution that has the problem, that does perhaps increase the
>> importance of doing something here.  I'm not sure what fixes went in
>> that required a 3.6.3, but the cheapest feasible option is just to rev
>> our version numbers so that it will install into this environment - it
>> will effectively be downgrading JDT to 3.6.2 in the process but at
>> least it would install.  Perhaps raise a jira and let's see if it
>> attracts some votes.
>>
>> cheers,
>> Andy
>>
>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>> Hi,
>>>
>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>
>>> Cannot complete the install because of a conflicting dependency.
>>>  Software being installed: Groovy-Eclipse Feature
>>> 2.5.2.xx-20110929-1700-e36
>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>> 2.5.2.xx-20110929-1700-e36)
>>>  Only one of the following can be installed at once:
>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>    Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core
>>> 3.6.3.v_A77_R36x)
>>>  Cannot satisfy dependency:
>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>> 2.5.2.xx-20110929-1700-e36)
>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>> [2.5.2.xx-20110929-1700-e36]
>>>  Cannot satisfy dependency:
>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>> 2.5.2.xx-20110929-1700-e36
>>> (org.codehaus.groovy.jdt.patch.feature.group
>>> 2.5.2.xx-20110929-1700-e36)
>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>  Cannot satisfy dependency:
>>>    From: Data Tools Platform JDT Enablement
>>> 1.8.2.v201010181125-2-07w31211518181A
>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>  Cannot satisfy dependency:
>>>    From: Eclipse Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>  Cannot satisfy dependency:
>>>    From: Eclipse Plug-in Development Environment
>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>> (org.eclipse.pde.feature.group
>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>  Cannot satisfy dependency:
>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>  Cannot satisfy dependency:
>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>> Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>  Optional dependency
>>>
>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>
>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>
>>> Thanks, Thomas
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
Hi Andy,

I am not aware of any version using Eclipse 3.7. Future version will certainly do.

I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?

Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.

I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.

In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?

This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.

During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.

Thomas

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
Sent: Dienstag, 22. November 2011 17:25
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

Hi Thomas,

OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
 JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.

So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.

I wish I had a better answer for you.



On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:

> Hi Andy,
>
> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>
> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>
> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>
> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>
> Do you have any idea on how else this could be solved?
>
> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>
> In my current installation which has the Groovy Plug-In installed I find the following:
>
> Features:
> org.eclipse.jdt.R342patch_1.0.15
> org.eclipse.jdt.R342patch_1.0.19
> org.eclipse.jdt.R361patch_1.0.0
>
> Plug-ins:
> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>
> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>
> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>
> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>
> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>
> Thomas
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Andrew Eisenberg
> Sent: Montag, 21. November 2011 17:43
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> Unfortunately, it won't be that easy.
>
>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
> Java Development Tools
> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
> (org.eclipse.jdt.feature.group
> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>
> This line implies that RSA ships with its own JDT core feature patch.
> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>
> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>
> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>
> Please let me know if you try this out and I can help you walk through any other problems you may have.
>
> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>> Hi,
>>
>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>
>> There is no further work planned for 3.6. But as it appears to be an
>> RSA distribution that has the problem, that does perhaps increase the
>> importance of doing something here.  I'm not sure what fixes went in
>> that required a 3.6.3, but the cheapest feasible option is just to
>> rev our version numbers so that it will install into this environment
>> - it will effectively be downgrading JDT to 3.6.2 in the process but
>> at least it would install.  Perhaps raise a jira and let's see if it
>> attracts some votes.
>>
>> cheers,
>> Andy
>>
>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>> Hi,
>>>
>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>
>>> Cannot complete the install because of a conflicting dependency.
>>>  Software being installed: Groovy-Eclipse Feature
>>> 2.5.2.xx-20110929-1700-e36
>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>> 2.5.2.xx-20110929-1700-e36)
>>>  Only one of the following can be installed at once:
>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>> (org.eclipse.jdt.core
>>> 3.6.3.v_A77_R36x)
>>>  Cannot satisfy dependency:
>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>> 2.5.2.xx-20110929-1700-e36)
>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>> [2.5.2.xx-20110929-1700-e36]
>>>  Cannot satisfy dependency:
>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>> 2.5.2.xx-20110929-1700-e36
>>> (org.codehaus.groovy.jdt.patch.feature.group
>>> 2.5.2.xx-20110929-1700-e36)
>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>  Cannot satisfy dependency:
>>>    From: Data Tools Platform JDT Enablement
>>> 1.8.2.v201010181125-2-07w31211518181A
>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>  Cannot satisfy dependency:
>>>    From: Eclipse Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>  Cannot satisfy dependency:
>>>    From: Eclipse Plug-in Development Environment
>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>> (org.eclipse.pde.feature.group
>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>  Cannot satisfy dependency:
>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>  Cannot satisfy dependency:
>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>> Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>  Optional dependency
>>>
>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>
>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>
>>> Thanks, Thomas
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andrew Eisenberg
On the new and noteworthy pages for each release, there are links to
the zipped archive:
http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-20110929-1700-e36.zip

The bundles.info file contains the information for the OSGi runtime as
to what bundles are installed and whether or not they should be
autostarted.  The update.xml is used by the update manager to
determine what is currently installed in your system.

I would think that you would need to edit both of these.  In the
platform.xml, remove the line about the RSA jdt core patch.  In the
bundles.info file, change the line on jdt.core to point to the
unpatched version of the bundle (I think it is
org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA
feature patch and associated jar from your system.  And finally, try
installing Groovy-Eclipse.  This *may* work.


On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:

> Hi Andy,
>
> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>
> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>
> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>
> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>
> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>
> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>
> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>
> Thomas
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
> Sent: Dienstag, 22. November 2011 17:25
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> Hi Thomas,
>
> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>
> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>
> I wish I had a better answer for you.
>
>
>
> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andy,
>>
>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>
>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>
>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>
>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>
>> Do you have any idea on how else this could be solved?
>>
>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>
>> In my current installation which has the Groovy Plug-In installed I find the following:
>>
>> Features:
>> org.eclipse.jdt.R342patch_1.0.15
>> org.eclipse.jdt.R342patch_1.0.19
>> org.eclipse.jdt.R361patch_1.0.0
>>
>> Plug-ins:
>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>
>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>
>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>
>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>
>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>
>> Thomas
>>
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Montag, 21. November 2011 17:43
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> Unfortunately, it won't be that easy.
>>
>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>> Java Development Tools
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>> (org.eclipse.jdt.feature.group
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>
>> This line implies that RSA ships with its own JDT core feature patch.
>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>
>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>
>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>
>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>
>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>> Hi,
>>>
>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>
>>> There is no further work planned for 3.6. But as it appears to be an
>>> RSA distribution that has the problem, that does perhaps increase the
>>> importance of doing something here.  I'm not sure what fixes went in
>>> that required a 3.6.3, but the cheapest feasible option is just to
>>> rev our version numbers so that it will install into this environment
>>> - it will effectively be downgrading JDT to 3.6.2 in the process but
>>> at least it would install.  Perhaps raise a jira and let's see if it
>>> attracts some votes.
>>>
>>> cheers,
>>> Andy
>>>
>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi,
>>>>
>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>
>>>> Cannot complete the install because of a conflicting dependency.
>>>>  Software being installed: Groovy-Eclipse Feature
>>>> 2.5.2.xx-20110929-1700-e36
>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>> 2.5.2.xx-20110929-1700-e36)
>>>>  Only one of the following can be installed at once:
>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>> (org.eclipse.jdt.core
>>>> 3.6.3.v_A77_R36x)
>>>>  Cannot satisfy dependency:
>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>> 2.5.2.xx-20110929-1700-e36)
>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>> [2.5.2.xx-20110929-1700-e36]
>>>>  Cannot satisfy dependency:
>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>> 2.5.2.xx-20110929-1700-e36
>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>> 2.5.2.xx-20110929-1700-e36)
>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>  Cannot satisfy dependency:
>>>>    From: Data Tools Platform JDT Enablement
>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>  Cannot satisfy dependency:
>>>>    From: Eclipse Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>  Cannot satisfy dependency:
>>>>    From: Eclipse Plug-in Development Environment
>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>> (org.eclipse.pde.feature.group
>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>  Cannot satisfy dependency:
>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>  Cannot satisfy dependency:
>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>>> Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>  Optional dependency
>>>>
>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>
>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>
>>>> Thanks, Thomas
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
Hi Andrew,

thanks for the link. I installed the version from the zip and I am getting errors with Enums:

Groovy:The class java.lang.Enum refers to the class java.lang.Enum and uses 1 parameters, but the referred class takes no parameters

In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.

Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.

My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.

Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.

Do you have any advice for me?

Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?

Thanks, Thomas

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
Sent: Mittwoch, 23. November 2011 18:06
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

On the new and noteworthy pages for each release, there are links to the zipped archive:
http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-20110929-1700-e36.zip

The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.

I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.


On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:

> Hi Andy,
>
> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>
> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>
> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>
> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>
> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>
> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>
> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>
> Thomas
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Andrew Eisenberg
> Sent: Dienstag, 22. November 2011 17:25
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> Hi Thomas,
>
> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>
> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>
> I wish I had a better answer for you.
>
>
>
> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andy,
>>
>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>
>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>
>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>
>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>
>> Do you have any idea on how else this could be solved?
>>
>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>
>> In my current installation which has the Groovy Plug-In installed I find the following:
>>
>> Features:
>> org.eclipse.jdt.R342patch_1.0.15
>> org.eclipse.jdt.R342patch_1.0.19
>> org.eclipse.jdt.R361patch_1.0.0
>>
>> Plug-ins:
>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>
>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>
>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>
>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>
>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>
>> Thomas
>>
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Montag, 21. November 2011 17:43
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> Unfortunately, it won't be that easy.
>>
>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>> Java Development Tools
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>> (org.eclipse.jdt.feature.group
>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>
>> This line implies that RSA ships with its own JDT core feature patch.
>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>
>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>
>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>
>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>
>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>> Hi,
>>>
>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>
>>> There is no further work planned for 3.6. But as it appears to be an
>>> RSA distribution that has the problem, that does perhaps increase
>>> the importance of doing something here.  I'm not sure what fixes
>>> went in that required a 3.6.3, but the cheapest feasible option is
>>> just to rev our version numbers so that it will install into this
>>> environment
>>> - it will effectively be downgrading JDT to 3.6.2 in the process but
>>> at least it would install.  Perhaps raise a jira and let's see if it
>>> attracts some votes.
>>>
>>> cheers,
>>> Andy
>>>
>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi,
>>>>
>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>
>>>> Cannot complete the install because of a conflicting dependency.
>>>>  Software being installed: Groovy-Eclipse Feature
>>>> 2.5.2.xx-20110929-1700-e36
>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>> 2.5.2.xx-20110929-1700-e36)
>>>>  Only one of the following can be installed at once:
>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>> (org.eclipse.jdt.core
>>>> 3.6.3.v_A77_R36x)
>>>>  Cannot satisfy dependency:
>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>> 2.5.2.xx-20110929-1700-e36)
>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>> [2.5.2.xx-20110929-1700-e36]
>>>>  Cannot satisfy dependency:
>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>> 2.5.2.xx-20110929-1700-e36
>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>> 2.5.2.xx-20110929-1700-e36)
>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>  Cannot satisfy dependency:
>>>>    From: Data Tools Platform JDT Enablement
>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>  Cannot satisfy dependency:
>>>>    From: Eclipse Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>  Cannot satisfy dependency:
>>>>    From: Eclipse Plug-in Development Environment
>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>> (org.eclipse.pde.feature.group
>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>  Cannot satisfy dependency:
>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>  Cannot satisfy dependency:
>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>> Eclipse Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>  Optional dependency
>>>>
>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>
>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>
>>>> Thanks, Thomas
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andrew Eisenberg
I'm not sure what that error was coming from.  Maybe Andy would have a
better idea...

It's great that you were able to do the install.  Can you let us know
the exact steps you took to get this working?  There may be other
people on this list who have the same problem. I will also update the
FAQ with this information.

On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:

> Hi Andrew,
>
> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>
> Groovy:The class java.lang.Enum refers to the class java.lang.Enum and uses 1 parameters, but the referred class takes no parameters
>
> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>
> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>
> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>
> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>
> Do you have any advice for me?
>
> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>
> Thanks, Thomas
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
> Sent: Mittwoch, 23. November 2011 18:06
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> On the new and noteworthy pages for each release, there are links to the zipped archive:
> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-20110929-1700-e36.zip
>
> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>
> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>
>
> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andy,
>>
>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>
>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>
>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>
>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>
>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>
>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>
>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>
>> Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Dienstag, 22. November 2011 17:25
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> Hi Thomas,
>>
>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>
>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>
>> I wish I had a better answer for you.
>>
>>
>>
>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andy,
>>>
>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>
>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>
>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>
>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>
>>> Do you have any idea on how else this could be solved?
>>>
>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>
>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>
>>> Features:
>>> org.eclipse.jdt.R342patch_1.0.15
>>> org.eclipse.jdt.R342patch_1.0.19
>>> org.eclipse.jdt.R361patch_1.0.0
>>>
>>> Plug-ins:
>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>
>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>
>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>
>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>
>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>
>>> Thomas
>>>
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Montag, 21. November 2011 17:43
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> Unfortunately, it won't be that easy.
>>>
>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>> Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>
>>> This line implies that RSA ships with its own JDT core feature patch.
>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>
>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>
>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>
>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>
>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>> Hi,
>>>>
>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>
>>>> There is no further work planned for 3.6. But as it appears to be an
>>>> RSA distribution that has the problem, that does perhaps increase
>>>> the importance of doing something here.  I'm not sure what fixes
>>>> went in that required a 3.6.3, but the cheapest feasible option is
>>>> just to rev our version numbers so that it will install into this
>>>> environment
>>>> - it will effectively be downgrading JDT to 3.6.2 in the process but
>>>> at least it would install.  Perhaps raise a jira and let's see if it
>>>> attracts some votes.
>>>>
>>>> cheers,
>>>> Andy
>>>>
>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>> Hi,
>>>>>
>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>
>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>> 2.5.2.xx-20110929-1700-e36
>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>  Only one of the following can be installed at once:
>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>> (org.eclipse.jdt.core
>>>>> 3.6.3.v_A77_R36x)
>>>>>  Cannot satisfy dependency:
>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>  Cannot satisfy dependency:
>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>> 2.5.2.xx-20110929-1700-e36
>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>  Cannot satisfy dependency:
>>>>>    From: Data Tools Platform JDT Enablement
>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>  Cannot satisfy dependency:
>>>>>    From: Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>  Cannot satisfy dependency:
>>>>>    From: Eclipse Plug-in Development Environment
>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>> (org.eclipse.pde.feature.group
>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>  Cannot satisfy dependency:
>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>  Cannot satisfy dependency:
>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>> Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>  Optional dependency
>>>>>
>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>
>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>
>>>>> Thanks, Thomas
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
Hi Andrew,

I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.

I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.

What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
So in summary:

RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36 which had the problem with the enum
I than updated to archive-2.6.0.xx-20111124-1300-e36 which solves the problem

On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.

Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.

One thing I will also try it to do the following:
1)Install old version of Rational product that does not contain the 3.6.3 JDT feature patch
2)Install groovy eclipse
3)Update Rational Product

Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?

Thomas

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
Sent: Freitag, 25. November 2011 17:25
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

I'm not sure what that error was coming from.  Maybe Andy would have a better idea...

It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.

On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:

> Hi Andrew,
>
> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>
> Groovy:The class java.lang.Enum refers to the class java.lang.Enum and
> uses 1 parameters, but the referred class takes no parameters
>
> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>
> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>
> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>
> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>
> Do you have any advice for me?
>
> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>
> Thanks, Thomas
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Andrew Eisenberg
> Sent: Mittwoch, 23. November 2011 18:06
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> On the new and noteworthy pages for each release, there are links to the zipped archive:
> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-2
> 0110929-1700-e36.zip
>
> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>
> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>
>
> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andy,
>>
>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>
>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>
>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>
>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>
>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>
>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>
>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>
>> Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Dienstag, 22. November 2011 17:25
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> Hi Thomas,
>>
>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>
>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>
>> I wish I had a better answer for you.
>>
>>
>>
>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andy,
>>>
>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>
>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>
>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>
>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>
>>> Do you have any idea on how else this could be solved?
>>>
>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>
>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>
>>> Features:
>>> org.eclipse.jdt.R342patch_1.0.15
>>> org.eclipse.jdt.R342patch_1.0.19
>>> org.eclipse.jdt.R361patch_1.0.0
>>>
>>> Plug-ins:
>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>
>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>
>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>
>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>
>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>
>>> Thomas
>>>
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Montag, 21. November 2011 17:43
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> Unfortunately, it won't be that easy.
>>>
>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>> Java Development Tools
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>> (org.eclipse.jdt.feature.group
>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>
>>> This line implies that RSA ships with its own JDT core feature patch.
>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>
>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>
>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>
>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>
>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>> Hi,
>>>>
>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>
>>>> There is no further work planned for 3.6. But as it appears to be
>>>> an RSA distribution that has the problem, that does perhaps
>>>> increase the importance of doing something here.  I'm not sure what
>>>> fixes went in that required a 3.6.3, but the cheapest feasible
>>>> option is just to rev our version numbers so that it will install
>>>> into this environment
>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>> but at least it would install.  Perhaps raise a jira and let's see
>>>> if it attracts some votes.
>>>>
>>>> cheers,
>>>> Andy
>>>>
>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>> Hi,
>>>>>
>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>
>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>> 2.5.2.xx-20110929-1700-e36
>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>  Only one of the following can be installed at once:
>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>> (org.eclipse.jdt.core
>>>>> 3.6.3.v_A77_R36x)
>>>>>  Cannot satisfy dependency:
>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>  Cannot satisfy dependency:
>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>> 2.5.2.xx-20110929-1700-e36
>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>  Cannot satisfy dependency:
>>>>>    From: Data Tools Platform JDT Enablement
>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>  Cannot satisfy dependency:
>>>>>    From: Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>  Cannot satisfy dependency:
>>>>>    From: Eclipse Plug-in Development Environment
>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>> (org.eclipse.pde.feature.group
>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>  Cannot satisfy dependency:
>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>  Cannot satisfy dependency:
>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>> Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>  Optional dependency
>>>>>
>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>
>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>
>>>>> Thanks, Thomas
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andrew Eisenberg
This is getting complicated!

We don't do extensive testing of the 3.6.x branch of Groovy-Eclipse.
We only run the automated tests against this branch and do all of our
manual testing on the 3.7 branch.

The 3.6 branch uses the same code base as the 3.7 branch (except for
the JDT patch) and it is of course compiled against e36 instead of
e37.  Our entire test suite has passed on both branches and no one
else has reported any problems, so I would be surprised if there is a
fundamental problem with that build.  If you are really concerned
about it, please raise a jira and I will have a look.

If you want to use an archived update site that is not the release
update site, then go to
http://ci.repository.codehaus.org/greclipse/snapshot/e36/old/ and
choose something.

I'm sure you know this, but when you do the install, make sure that
you don't simply unzip the archive file, you must point to the archive
file from the Eclipse install manager.

>
> Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?
>
Maybe.  A lot will depend on how the other JDT feature is constructed
and what its target range for the patched feature is.


On Fri, Nov 25, 2011 at 11:54 AM, Thomas Hofmann
<[hidden email]> wrote:

> Hi Andrew,
>
> I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.
>
> I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
> I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.
>
> What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
> So in summary:
>
> RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36 which had the problem with the enum
> I than updated to archive-2.6.0.xx-20111124-1300-e36 which solves the problem
>
> On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.
>
> Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.
>
> One thing I will also try it to do the following:
> 1)Install old version of Rational product that does not contain the 3.6.3 JDT feature patch
> 2)Install groovy eclipse
> 3)Update Rational Product
> Thomas
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
> Sent: Freitag, 25. November 2011 17:25
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> I'm not sure what that error was coming from.  Maybe Andy would have a better idea...
>
> It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.
>
> On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andrew,
>>
>> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>>
>> Groovy:The class java.lang.Enum refers to the class java.lang.Enum and
>> uses 1 parameters, but the referred class takes no parameters
>>
>> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>>
>> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>>
>> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>>
>> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>>
>> Do you have any advice for me?
>>
>> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>>
>> Thanks, Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Mittwoch, 23. November 2011 18:06
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> On the new and noteworthy pages for each release, there are links to the zipped archive:
>> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
>> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-2
>> 0110929-1700-e36.zip
>>
>> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>>
>> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>>
>>
>> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andy,
>>>
>>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>>
>>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>>
>>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>>
>>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>>
>>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>>
>>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>>
>>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>>
>>> Thomas
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Dienstag, 22. November 2011 17:25
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> Hi Thomas,
>>>
>>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>>
>>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>>
>>> I wish I had a better answer for you.
>>>
>>>
>>>
>>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi Andy,
>>>>
>>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>>
>>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>>
>>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>>
>>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>>
>>>> Do you have any idea on how else this could be solved?
>>>>
>>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>>
>>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>>
>>>> Features:
>>>> org.eclipse.jdt.R342patch_1.0.15
>>>> org.eclipse.jdt.R342patch_1.0.19
>>>> org.eclipse.jdt.R361patch_1.0.0
>>>>
>>>> Plug-ins:
>>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>>
>>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>>
>>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>>
>>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>>
>>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>>
>>>> Thomas
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: [hidden email] [mailto:[hidden email]]
>>>> On Behalf Of Andrew Eisenberg
>>>> Sent: Montag, 21. November 2011 17:43
>>>> To: [hidden email]
>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>
>>>> Unfortunately, it won't be that easy.
>>>>
>>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>>> Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>
>>>> This line implies that RSA ships with its own JDT core feature patch.
>>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>>
>>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>>
>>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>>
>>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>>
>>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>>> Hi,
>>>>>
>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>
>>>>> There is no further work planned for 3.6. But as it appears to be
>>>>> an RSA distribution that has the problem, that does perhaps
>>>>> increase the importance of doing something here.  I'm not sure what
>>>>> fixes went in that required a 3.6.3, but the cheapest feasible
>>>>> option is just to rev our version numbers so that it will install
>>>>> into this environment
>>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>>> but at least it would install.  Perhaps raise a jira and let's see
>>>>> if it attracts some votes.
>>>>>
>>>>> cheers,
>>>>> Andy
>>>>>
>>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>>
>>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>  Only one of the following can be installed at once:
>>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>>> (org.eclipse.jdt.core
>>>>>> 3.6.3.v_A77_R36x)
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Data Tools Platform JDT Enablement
>>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Eclipse Plug-in Development Environment
>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>>> (org.eclipse.pde.feature.group
>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>>  Cannot satisfy dependency:
>>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>>  Cannot satisfy dependency:
>>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>> Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>>  Optional dependency
>>>>>>
>>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>>
>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>
>>>>>> Thanks, Thomas
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
This is the link I used to download the archive. I could not find the one that I had installed on my dev machine so took the latest.
Yes I install without unzipping using the update manager.



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
Sent: Freitag, 25. November 2011 22:32
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

This is getting complicated!

We don't do extensive testing of the 3.6.x branch of Groovy-Eclipse.
We only run the automated tests against this branch and do all of our manual testing on the 3.7 branch.

The 3.6 branch uses the same code base as the 3.7 branch (except for the JDT patch) and it is of course compiled against e36 instead of e37.  Our entire test suite has passed on both branches and no one else has reported any problems, so I would be surprised if there is a fundamental problem with that build.  If you are really concerned about it, please raise a jira and I will have a look.

If you want to use an archived update site that is not the release update site, then go to http://ci.repository.codehaus.org/greclipse/snapshot/e36/old/ and choose something.

I'm sure you know this, but when you do the install, make sure that you don't simply unzip the archive file, you must point to the archive file from the Eclipse install manager.

>
> Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?
>
Maybe.  A lot will depend on how the other JDT feature is constructed and what its target range for the patched feature is.


On Fri, Nov 25, 2011 at 11:54 AM, Thomas Hofmann <[hidden email]> wrote:

> Hi Andrew,
>
> I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.
>
> I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
> I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.
>
> What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
> So in summary:
>
> RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36 which
> had the problem with the enum I than updated to
> archive-2.6.0.xx-20111124-1300-e36 which solves the problem
>
> On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.
>
> Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.
>
> One thing I will also try it to do the following:
> 1)Install old version of Rational product that does not contain the
> 3.6.3 JDT feature patch 2)Install groovy eclipse 3)Update Rational
> Product Thomas
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Andrew Eisenberg
> Sent: Freitag, 25. November 2011 17:25
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> I'm not sure what that error was coming from.  Maybe Andy would have a better idea...
>
> It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.
>
> On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andrew,
>>
>> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>>
>> Groovy:The class java.lang.Enum refers to the class java.lang.Enum
>> and uses 1 parameters, but the referred class takes no parameters
>>
>> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>>
>> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>>
>> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>>
>> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>>
>> Do you have any advice for me?
>>
>> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>>
>> Thanks, Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Mittwoch, 23. November 2011 18:06
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> On the new and noteworthy pages for each release, there are links to the zipped archive:
>> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
>> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-
>> 2
>> 0110929-1700-e36.zip
>>
>> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>>
>> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>>
>>
>> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andy,
>>>
>>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>>
>>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>>
>>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>>
>>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>>
>>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>>
>>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>>
>>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>>
>>> Thomas
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Dienstag, 22. November 2011 17:25
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> Hi Thomas,
>>>
>>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>>
>>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>>
>>> I wish I had a better answer for you.
>>>
>>>
>>>
>>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi Andy,
>>>>
>>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>>
>>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>>
>>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>>
>>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>>
>>>> Do you have any idea on how else this could be solved?
>>>>
>>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>>
>>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>>
>>>> Features:
>>>> org.eclipse.jdt.R342patch_1.0.15
>>>> org.eclipse.jdt.R342patch_1.0.19
>>>> org.eclipse.jdt.R361patch_1.0.0
>>>>
>>>> Plug-ins:
>>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>>
>>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>>
>>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>>
>>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>>
>>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>>
>>>> Thomas
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: [hidden email]
>>>> [mailto:[hidden email]]
>>>> On Behalf Of Andrew Eisenberg
>>>> Sent: Montag, 21. November 2011 17:43
>>>> To: [hidden email]
>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>
>>>> Unfortunately, it won't be that easy.
>>>>
>>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>>> Java Development Tools
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>> (org.eclipse.jdt.feature.group
>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>
>>>> This line implies that RSA ships with its own JDT core feature patch.
>>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>>
>>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>>
>>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>>
>>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>>
>>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>>> Hi,
>>>>>
>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>
>>>>> There is no further work planned for 3.6. But as it appears to be
>>>>> an RSA distribution that has the problem, that does perhaps
>>>>> increase the importance of doing something here.  I'm not sure
>>>>> what fixes went in that required a 3.6.3, but the cheapest
>>>>> feasible option is just to rev our version numbers so that it will
>>>>> install into this environment
>>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>>> but at least it would install.  Perhaps raise a jira and let's see
>>>>> if it attracts some votes.
>>>>>
>>>>> cheers,
>>>>> Andy
>>>>>
>>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>>
>>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>  Only one of the following can be installed at once:
>>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>>> (org.eclipse.jdt.core
>>>>>> 3.6.3.v_A77_R36x)
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Data Tools Platform JDT Enablement
>>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>>  Cannot satisfy dependency:
>>>>>>    From: Eclipse Plug-in Development Environment
>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>>> (org.eclipse.pde.feature.group
>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>>  Cannot satisfy dependency:
>>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>>  Cannot satisfy dependency:
>>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>> Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>>  Optional dependency
>>>>>>
>>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>>
>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>
>>>>>> Thanks, Thomas
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andy Clement
I do recall waiting for 2.5.2 to get released before I committed a
bunch of 'stuff' that I worried may have a destabilizing effect, as
for what it did, I don't recall - but sounds like it affected enums ;)
 That would explain the one day later fix.

Andy

On 25 November 2011 13:21, Thomas Hofmann <[hidden email]> wrote:

> This is the link I used to download the archive. I could not find the one that I had installed on my dev machine so took the latest.
> Yes I install without unzipping using the update manager.
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrew Eisenberg
> Sent: Freitag, 25. November 2011 22:32
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> This is getting complicated!
>
> We don't do extensive testing of the 3.6.x branch of Groovy-Eclipse.
> We only run the automated tests against this branch and do all of our manual testing on the 3.7 branch.
>
> The 3.6 branch uses the same code base as the 3.7 branch (except for the JDT patch) and it is of course compiled against e36 instead of e37.  Our entire test suite has passed on both branches and no one else has reported any problems, so I would be surprised if there is a fundamental problem with that build.  If you are really concerned about it, please raise a jira and I will have a look.
>
> If you want to use an archived update site that is not the release update site, then go to http://ci.repository.codehaus.org/greclipse/snapshot/e36/old/ and choose something.
>
> I'm sure you know this, but when you do the install, make sure that you don't simply unzip the archive file, you must point to the archive file from the Eclipse install manager.
>
>>
>> Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?
>>
> Maybe.  A lot will depend on how the other JDT feature is constructed and what its target range for the patched feature is.
>
>
> On Fri, Nov 25, 2011 at 11:54 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andrew,
>>
>> I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.
>>
>> I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
>> I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.
>>
>> What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
>> So in summary:
>>
>> RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36 which
>> had the problem with the enum I than updated to
>> archive-2.6.0.xx-20111124-1300-e36 which solves the problem
>>
>> On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.
>>
>> Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.
>>
>> One thing I will also try it to do the following:
>> 1)Install old version of Rational product that does not contain the
>> 3.6.3 JDT feature patch 2)Install groovy eclipse 3)Update Rational
>> Product Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Freitag, 25. November 2011 17:25
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> I'm not sure what that error was coming from.  Maybe Andy would have a better idea...
>>
>> It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.
>>
>> On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andrew,
>>>
>>> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>>>
>>> Groovy:The class java.lang.Enum refers to the class java.lang.Enum
>>> and uses 1 parameters, but the referred class takes no parameters
>>>
>>> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>>>
>>> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>>>
>>> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>>>
>>> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>>>
>>> Do you have any advice for me?
>>>
>>> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>>>
>>> Thanks, Thomas
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Mittwoch, 23. November 2011 18:06
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> On the new and noteworthy pages for each release, there are links to the zipped archive:
>>> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
>>> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx-
>>> 2
>>> 0110929-1700-e36.zip
>>>
>>> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>>>
>>> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>>>
>>>
>>> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi Andy,
>>>>
>>>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>>>
>>>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>>>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>>>
>>>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>>>
>>>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>>>
>>>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>>>
>>>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>>>
>>>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>>>
>>>> Thomas
>>>>
>>>> -----Original Message-----
>>>> From: [hidden email] [mailto:[hidden email]]
>>>> On Behalf Of Andrew Eisenberg
>>>> Sent: Dienstag, 22. November 2011 17:25
>>>> To: [hidden email]
>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>
>>>> Hi Thomas,
>>>>
>>>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>>>
>>>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>>>
>>>> I wish I had a better answer for you.
>>>>
>>>>
>>>>
>>>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>>>> Hi Andy,
>>>>>
>>>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>>>
>>>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>>>
>>>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>>>
>>>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>>>
>>>>> Do you have any idea on how else this could be solved?
>>>>>
>>>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>>>
>>>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>>>
>>>>> Features:
>>>>> org.eclipse.jdt.R342patch_1.0.15
>>>>> org.eclipse.jdt.R342patch_1.0.19
>>>>> org.eclipse.jdt.R361patch_1.0.0
>>>>>
>>>>> Plug-ins:
>>>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>>>
>>>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>>>
>>>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>>>
>>>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>>>
>>>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>>>
>>>>> Thomas
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: [hidden email]
>>>>> [mailto:[hidden email]]
>>>>> On Behalf Of Andrew Eisenberg
>>>>> Sent: Montag, 21. November 2011 17:43
>>>>> To: [hidden email]
>>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>>
>>>>> Unfortunately, it won't be that easy.
>>>>>
>>>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2 Eclipse
>>>>> Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>
>>>>> This line implies that RSA ships with its own JDT core feature patch.
>>>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>>>
>>>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>>>
>>>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>>>
>>>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>>>
>>>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>
>>>>>> There is no further work planned for 3.6. But as it appears to be
>>>>>> an RSA distribution that has the problem, that does perhaps
>>>>>> increase the importance of doing something here.  I'm not sure
>>>>>> what fixes went in that required a 3.6.3, but the cheapest
>>>>>> feasible option is just to rev our version numbers so that it will
>>>>>> install into this environment
>>>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>>>> but at least it would install.  Perhaps raise a jira and let's see
>>>>>> if it attracts some votes.
>>>>>>
>>>>>> cheers,
>>>>>> Andy
>>>>>>
>>>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>>>
>>>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>  Only one of the following can be installed at once:
>>>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>>>> (org.eclipse.jdt.core
>>>>>>> 3.6.3.v_A77_R36x)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Data Tools Platform JDT Enablement
>>>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Eclipse Plug-in Development Environment
>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>>>> (org.eclipse.pde.feature.group
>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>>> Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>>>  Optional dependency
>>>>>>>
>>>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>>>
>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>>
>>>>>>> Thanks, Thomas
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------
>>>>>>> -
>>>>>>> -
>>>>>>> -
>>>>>>> - To unsubscribe from this list, please visit:
>>>>>>>
>>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
For me it looks like enums are broken in 2.5.2 released version which I really doubt since that would have been reported I guess by other users. So it's really strange.

-----Original Message-----
From: Andy Clement [mailto:[hidden email]]
Sent: Freitag, 25. November 2011 22:52
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

I do recall waiting for 2.5.2 to get released before I committed a bunch of 'stuff' that I worried may have a destabilizing effect, as for what it did, I don't recall - but sounds like it affected enums ;)  That would explain the one day later fix.

Andy

On 25 November 2011 13:21, Thomas Hofmann <[hidden email]> wrote:

> This is the link I used to download the archive. I could not find the one that I had installed on my dev machine so took the latest.
> Yes I install without unzipping using the update manager.
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Andrew Eisenberg
> Sent: Freitag, 25. November 2011 22:32
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> This is getting complicated!
>
> We don't do extensive testing of the 3.6.x branch of Groovy-Eclipse.
> We only run the automated tests against this branch and do all of our manual testing on the 3.7 branch.
>
> The 3.6 branch uses the same code base as the 3.7 branch (except for the JDT patch) and it is of course compiled against e36 instead of e37.  Our entire test suite has passed on both branches and no one else has reported any problems, so I would be surprised if there is a fundamental problem with that build.  If you are really concerned about it, please raise a jira and I will have a look.
>
> If you want to use an archived update site that is not the release update site, then go to http://ci.repository.codehaus.org/greclipse/snapshot/e36/old/ and choose something.
>
> I'm sure you know this, but when you do the install, make sure that you don't simply unzip the archive file, you must point to the archive file from the Eclipse install manager.
>
>>
>> Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?
>>
> Maybe.  A lot will depend on how the other JDT feature is constructed and what its target range for the patched feature is.
>
>
> On Fri, Nov 25, 2011 at 11:54 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andrew,
>>
>> I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.
>>
>> I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
>> I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.
>>
>> What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
>> So in summary:
>>
>> RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36
>> which had the problem with the enum I than updated to
>> archive-2.6.0.xx-20111124-1300-e36 which solves the problem
>>
>> On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.
>>
>> Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.
>>
>> One thing I will also try it to do the following:
>> 1)Install old version of Rational product that does not contain the
>> 3.6.3 JDT feature patch 2)Install groovy eclipse 3)Update Rational
>> Product Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Freitag, 25. November 2011 17:25
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> I'm not sure what that error was coming from.  Maybe Andy would have a better idea...
>>
>> It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.
>>
>> On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andrew,
>>>
>>> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>>>
>>> Groovy:The class java.lang.Enum refers to the class java.lang.Enum
>>> and uses 1 parameters, but the referred class takes no parameters
>>>
>>> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>>>
>>> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>>>
>>> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>>>
>>> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>>>
>>> Do you have any advice for me?
>>>
>>> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>>>
>>> Thanks, Thomas
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Mittwoch, 23. November 2011 18:06
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> On the new and noteworthy pages for each release, there are links to the zipped archive:
>>> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
>>> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx
>>> -
>>> 2
>>> 0110929-1700-e36.zip
>>>
>>> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>>>
>>> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>>>
>>>
>>> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi Andy,
>>>>
>>>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>>>
>>>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>>>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>>>
>>>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>>>
>>>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>>>
>>>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>>>
>>>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>>>
>>>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>>>
>>>> Thomas
>>>>
>>>> -----Original Message-----
>>>> From: [hidden email]
>>>> [mailto:[hidden email]]
>>>> On Behalf Of Andrew Eisenberg
>>>> Sent: Dienstag, 22. November 2011 17:25
>>>> To: [hidden email]
>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>
>>>> Hi Thomas,
>>>>
>>>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>>>
>>>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>>>
>>>> I wish I had a better answer for you.
>>>>
>>>>
>>>>
>>>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>>>> Hi Andy,
>>>>>
>>>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>>>
>>>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>>>
>>>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>>>
>>>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>>>
>>>>> Do you have any idea on how else this could be solved?
>>>>>
>>>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>>>
>>>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>>>
>>>>> Features:
>>>>> org.eclipse.jdt.R342patch_1.0.15
>>>>> org.eclipse.jdt.R342patch_1.0.19
>>>>> org.eclipse.jdt.R361patch_1.0.0
>>>>>
>>>>> Plug-ins:
>>>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>>>
>>>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>>>
>>>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>>>
>>>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>>>
>>>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>>>
>>>>> Thomas
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: [hidden email]
>>>>> [mailto:[hidden email]]
>>>>> On Behalf Of Andrew Eisenberg
>>>>> Sent: Montag, 21. November 2011 17:43
>>>>> To: [hidden email]
>>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>>
>>>>> Unfortunately, it won't be that easy.
>>>>>
>>>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>> Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>
>>>>> This line implies that RSA ships with its own JDT core feature patch.
>>>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>>>
>>>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>>>
>>>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>>>
>>>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>>>
>>>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>
>>>>>> There is no further work planned for 3.6. But as it appears to be
>>>>>> an RSA distribution that has the problem, that does perhaps
>>>>>> increase the importance of doing something here.  I'm not sure
>>>>>> what fixes went in that required a 3.6.3, but the cheapest
>>>>>> feasible option is just to rev our version numbers so that it
>>>>>> will install into this environment
>>>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>>>> but at least it would install.  Perhaps raise a jira and let's
>>>>>> see if it attracts some votes.
>>>>>>
>>>>>> cheers,
>>>>>> Andy
>>>>>>
>>>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>>>
>>>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>  Only one of the following can be installed at once:
>>>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>>>> (org.eclipse.jdt.core
>>>>>>> 3.6.3.v_A77_R36x)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Data Tools Platform JDT Enablement
>>>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Eclipse Plug-in Development Environment
>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>>>> (org.eclipse.pde.feature.group
>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>>> Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>>>  Optional dependency
>>>>>>>
>>>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>>>
>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>>
>>>>>>> Thanks, Thomas
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> -
>>>>>>> -
>>>>>>> -
>>>>>>> -
>>>>>>> - To unsubscribe from this list, please visit:
>>>>>>>
>>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Support for JDT Core 3.6.3?

Andrew Eisenberg
Raised this issue:
http://jira.codehaus.org/browse/GRECLIPSE-1263
To track the potential e36 problem.

On Fri, Nov 25, 2011 at 1:39 PM, Thomas Hofmann <[hidden email]> wrote:

> For me it looks like enums are broken in 2.5.2 released version which I really doubt since that would have been reported I guess by other users. So it's really strange.
>
> -----Original Message-----
> From: Andy Clement [mailto:[hidden email]]
> Sent: Freitag, 25. November 2011 22:52
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> I do recall waiting for 2.5.2 to get released before I committed a bunch of 'stuff' that I worried may have a destabilizing effect, as for what it did, I don't recall - but sounds like it affected enums ;)  That would explain the one day later fix.
>
> Andy
>
> On 25 November 2011 13:21, Thomas Hofmann <[hidden email]> wrote:
>> This is the link I used to download the archive. I could not find the one that I had installed on my dev machine so took the latest.
>> Yes I install without unzipping using the update manager.
>>
>>
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Freitag, 25. November 2011 22:32
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> This is getting complicated!
>>
>> We don't do extensive testing of the 3.6.x branch of Groovy-Eclipse.
>> We only run the automated tests against this branch and do all of our manual testing on the 3.7 branch.
>>
>> The 3.6 branch uses the same code base as the 3.7 branch (except for the JDT patch) and it is of course compiled against e36 instead of e37.  Our entire test suite has passed on both branches and no one else has reported any problems, so I would be surprised if there is a fundamental problem with that build.  If you are really concerned about it, please raise a jira and I will have a look.
>>
>> If you want to use an archived update site that is not the release update site, then go to http://ci.repository.codehaus.org/greclipse/snapshot/e36/old/ and choose something.
>>
>> I'm sure you know this, but when you do the install, make sure that you don't simply unzip the archive file, you must point to the archive file from the Eclipse install manager.
>>
>>>
>>> Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?
>>>
>> Maybe.  A lot will depend on how the other JDT feature is constructed and what its target range for the patched feature is.
>>
>>
>> On Fri, Nov 25, 2011 at 11:54 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andrew,
>>>
>>> I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.
>>>
>>> I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
>>> I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.
>>>
>>> What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
>>> So in summary:
>>>
>>> RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36
>>> which had the problem with the enum I than updated to
>>> archive-2.6.0.xx-20111124-1300-e36 which solves the problem
>>>
>>> On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.
>>>
>>> Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.
>>>
>>> One thing I will also try it to do the following:
>>> 1)Install old version of Rational product that does not contain the
>>> 3.6.3 JDT feature patch 2)Install groovy eclipse 3)Update Rational
>>> Product Thomas
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Freitag, 25. November 2011 17:25
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> I'm not sure what that error was coming from.  Maybe Andy would have a better idea...
>>>
>>> It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.
>>>
>>> On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi Andrew,
>>>>
>>>> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>>>>
>>>> Groovy:The class java.lang.Enum refers to the class java.lang.Enum
>>>> and uses 1 parameters, but the referred class takes no parameters
>>>>
>>>> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>>>>
>>>> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>>>>
>>>> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>>>>
>>>> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>>>>
>>>> Do you have any advice for me?
>>>>
>>>> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>>>>
>>>> Thanks, Thomas
>>>>
>>>> -----Original Message-----
>>>> From: [hidden email] [mailto:[hidden email]]
>>>> On Behalf Of Andrew Eisenberg
>>>> Sent: Mittwoch, 23. November 2011 18:06
>>>> To: [hidden email]
>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>
>>>> On the new and noteworthy pages for each release, there are links to the zipped archive:
>>>> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
>>>> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx
>>>> -
>>>> 2
>>>> 0110929-1700-e36.zip
>>>>
>>>> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>>>>
>>>> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>>>>
>>>>
>>>> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>>>>> Hi Andy,
>>>>>
>>>>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>>>>
>>>>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>>>>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>>>>
>>>>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>>>>
>>>>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>>>>
>>>>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>>>>
>>>>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>>>>
>>>>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>>>>
>>>>> Thomas
>>>>>
>>>>> -----Original Message-----
>>>>> From: [hidden email]
>>>>> [mailto:[hidden email]]
>>>>> On Behalf Of Andrew Eisenberg
>>>>> Sent: Dienstag, 22. November 2011 17:25
>>>>> To: [hidden email]
>>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>>
>>>>> Hi Thomas,
>>>>>
>>>>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>>>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>>>>
>>>>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>>>>
>>>>> I wish I had a better answer for you.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>>>>> Hi Andy,
>>>>>>
>>>>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>>>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>>>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>>>>
>>>>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>>>>
>>>>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>>>>
>>>>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>>>>
>>>>>> Do you have any idea on how else this could be solved?
>>>>>>
>>>>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>>>>
>>>>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>>>>
>>>>>> Features:
>>>>>> org.eclipse.jdt.R342patch_1.0.15
>>>>>> org.eclipse.jdt.R342patch_1.0.19
>>>>>> org.eclipse.jdt.R361patch_1.0.0
>>>>>>
>>>>>> Plug-ins:
>>>>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>>>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>>>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>>>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>>>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>>>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>>>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>>>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>>>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>>>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>>>>
>>>>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>>>>
>>>>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>>>>
>>>>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>>>>
>>>>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>>>>
>>>>>> Thomas
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: [hidden email]
>>>>>> [mailto:[hidden email]]
>>>>>> On Behalf Of Andrew Eisenberg
>>>>>> Sent: Montag, 21. November 2011 17:43
>>>>>> To: [hidden email]
>>>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>>>
>>>>>> Unfortunately, it won't be that easy.
>>>>>>
>>>>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>> Eclipse Java Development Tools
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>> (org.eclipse.jdt.feature.group
>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>
>>>>>> This line implies that RSA ships with its own JDT core feature patch.
>>>>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>>>>
>>>>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>>>>
>>>>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>>>>
>>>>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>>>>
>>>>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>>
>>>>>>> There is no further work planned for 3.6. But as it appears to be
>>>>>>> an RSA distribution that has the problem, that does perhaps
>>>>>>> increase the importance of doing something here.  I'm not sure
>>>>>>> what fixes went in that required a 3.6.3, but the cheapest
>>>>>>> feasible option is just to rev our version numbers so that it
>>>>>>> will install into this environment
>>>>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>>>>> but at least it would install.  Perhaps raise a jira and let's
>>>>>>> see if it attracts some votes.
>>>>>>>
>>>>>>> cheers,
>>>>>>> Andy
>>>>>>>
>>>>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>>>>
>>>>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>>  Only one of the following can be installed at once:
>>>>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>>>>> (org.eclipse.jdt.core
>>>>>>>> 3.6.3.v_A77_R36x)
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From: Data Tools Platform JDT Enablement
>>>>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>>>>    To: org.eclipse.jdt.feature.group 3.4.0
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From: Eclipse Java Development Tools
>>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From: Eclipse Plug-in Development Environment
>>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>>>>> (org.eclipse.pde.feature.group
>>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]
>>>>>>>>  Cannot satisfy dependency:
>>>>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>>>> Eclipse Java Development Tools
>>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]
>>>>>>>>  Optional dependency
>>>>>>>>
>>>>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>>>>
>>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>>>
>>>>>>>> Thanks, Thomas
>>>>>>>>
>>>>>>>>
>>>>>>>> ----------------------------------------------------------------
>>>>>>>> -
>>>>>>>> -
>>>>>>>> -
>>>>>>>> -
>>>>>>>> - To unsubscribe from this list, please visit:
>>>>>>>>
>>>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------------------
>>>>>>> -
>>>>>>> -
>>>>>>> -
>>>>>>> - To unsubscribe from this list, please visit:
>>>>>>>
>>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

RE: Support for JDT Core 3.6.3?

Thomas Hofmann
In reply to this post by Thomas Hofmann
Hi Andrew,

In the meantime I tries some more installations. If I install the Rational product in a version that does not include the JDT feature patch from Rational yet I can install the Groovy eclipse plugin without problems. When I then update the product to a newer fixpack level that will include the JDT feature patch the installation works. Groovy still works but I'm not sure if the JDT feature patch that comes along with groovy is in use.
The problem begins when I then try to install anything using p2. I always geht an error about an invalid configuration. From that point on I cannot install or uninstall anything more. So this is not the way to go.

You mentioned that you are unsure if it is possible to patch a feature patch with yet another feature patch? I couldn't find any information about this. Do you have some further information on this? I Don't know if it would help with the invalid configuration but at least I could try to install the product in its most current version, then install the groovy plugin and see what happens. Maybe I could then uninstall the feature patch from groovy before upgrading the product.

Regards, Thomas

-----Original Message-----
From: Thomas Hofmann [mailto:[hidden email]]
Sent: Freitag, 25. November 2011 22:40
To: [hidden email]
Subject: RE: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

For me it looks like enums are broken in 2.5.2 released version which I really doubt since that would have been reported I guess by other users. So it's really strange.

-----Original Message-----
From: Andy Clement [mailto:[hidden email]]
Sent: Freitag, 25. November 2011 22:52
To: [hidden email]
Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?

I do recall waiting for 2.5.2 to get released before I committed a bunch of 'stuff' that I worried may have a destabilizing effect, as for what it did, I don't recall - but sounds like it affected enums ;)  That would explain the one day later fix.

Andy

On 25 November 2011 13:21, Thomas Hofmann <[hidden email]> wrote:

> This is the link I used to download the archive. I could not find the one that I had installed on my dev machine so took the latest.
> Yes I install without unzipping using the update manager.
>
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]]
> On Behalf Of Andrew Eisenberg
> Sent: Freitag, 25. November 2011 22:32
> To: [hidden email]
> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>
> This is getting complicated!
>
> We don't do extensive testing of the 3.6.x branch of Groovy-Eclipse.
> We only run the automated tests against this branch and do all of our manual testing on the 3.7 branch.
>
> The 3.6 branch uses the same code base as the 3.7 branch (except for the JDT patch) and it is of course compiled against e36 instead of e37.  Our entire test suite has passed on both branches and no one else has reported any problems, so I would be surprised if there is a fundamental problem with that build.  If you are really concerned about it, please raise a jira and I will have a look.
>
> If you want to use an archived update site that is not the release update site, then go to http://ci.repository.codehaus.org/greclipse/snapshot/e36/old/ and choose something.
>
> I'm sure you know this, but when you do the install, make sure that you don't simply unzip the archive file, you must point to the archive file from the Eclipse install manager.
>
>>
>> Maybe the update will not apply the 3.6.3 JDT feature patch if another patch is already applied. What do you think?
>>
> Maybe.  A lot will depend on how the other JDT feature is constructed and what its target range for the patched feature is.
>
>
> On Fri, Nov 25, 2011 at 11:54 AM, Thomas Hofmann <[hidden email]> wrote:
>> Hi Andrew,
>>
>> I just sent out a reply to RE: Re: [aspectj-users] Equinox waeving which explains my setup a bit in more detail. You should read it first.
>>
>> I did not have success installing the groovy eclipse plug-in into a version that uses the JDT 3.6.3 feature patch that got installed with the newer versions of the Rational products. The RFT version I know use in the VMWare image is an older one and does not contain this feature patch.
>> I just wanted to install from an archive file so that I do not need to rely on what's on the update site at some later point in time.
>>
>> What I noticed was that thr 2.5.2 version that you gave me the link to had problems with the enums. The snapshot that I installed now does not have the problem. The snapshot I installed into my dev machine also does not have the problem and is one day younger that the 2.5.2 build you gave me the link for.
>> So in summary:
>>
>> RFT in VMWare image contained archive-2.5.2.xx-20110929-1700-e36
>> which had the problem with the enum I than updated to
>> archive-2.6.0.xx-20111124-1300-e36 which solves the problem
>>
>> On my dev machine I have org.codehaus.groovy.eclipse.feature_2.5.2.xx-20110930-1300-e36 which works flawlessly. This is only one day difference so i wanted to know if there was a fix you now of that did not make it into the release version. I wouldn't expect it to be that way but as I've seen archive-2.5.2.xx-20110929-1700-e36 gave me the enum error. I would have tried to install the same version that I got on my dev machine but I was not able to find an archive for it so I took one of the newest snapshots.
>>
>> Regarding the problem with the JDT feature patch I would say that I will try the solution with patching the platform.xml and bundles.info at a later point in time. I am not forced to used the latest version right now but that might change and it is not a good perspective to basis for groovy development in RSA when you know that it suddenly won't work anymore with the latest updates.
>>
>> One thing I will also try it to do the following:
>> 1)Install old version of Rational product that does not contain the
>> 3.6.3 JDT feature patch 2)Install groovy eclipse 3)Update Rational
>> Product Thomas
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]]
>> On Behalf Of Andrew Eisenberg
>> Sent: Freitag, 25. November 2011 17:25
>> To: [hidden email]
>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>
>> I'm not sure what that error was coming from.  Maybe Andy would have a better idea...
>>
>> It's great that you were able to do the install.  Can you let us know the exact steps you took to get this working?  There may be other people on this list who have the same problem. I will also update the FAQ with this information.
>>
>> On Fri, Nov 25, 2011 at 3:22 AM, Thomas Hofmann <[hidden email]> wrote:
>>> Hi Andrew,
>>>
>>> thanks for the link. I installed the version from the zip and I am getting errors with Enums:
>>>
>>> Groovy:The class java.lang.Enum refers to the class java.lang.Enum
>>> and uses 1 parameters, but the referred class takes no parameters
>>>
>>> In my other installation I noticed that I am using version  2.5.2.xx-20110930-1300-e36 which I propapbly installed from the snapshot update site.
>>>
>>> Since I don't think that the release version has such an issue I would be interessted to know what could be the cause for this error.
>>>
>>> My workspace settings are set to Java Compliance Level 1.6 (the default). Still, I had problems with Java using the assert keyword. Somehow eclipse used level 1.4 I think. I switched to 1.5 and then back to 1.6 and the problems dissapeared. Maybe this has to do with the Enum problem to.
>>>
>>> Rebuilding and closing and reopening of the groovy does not help. Switching Java Compliance Level on the Groovy project does not help either.
>>>
>>> Do you have any advice for me?
>>>
>>> Edit: Just installed the dev build archive-2.6.0.xx-20111124-1300-e36 and it fixes the problem. Is it a know bug with 2.5.2?
>>>
>>> Thanks, Thomas
>>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]]
>>> On Behalf Of Andrew Eisenberg
>>> Sent: Mittwoch, 23. November 2011 18:06
>>> To: [hidden email]
>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>
>>> On the new and noteworthy pages for each release, there are links to the zipped archive:
>>> http://groovy.codehaus.org/Groovy-Eclipse+2.5.2+New+and+Noteworthy
>>> http://dist.springsource.org/release/GRECLIPSE/e3.6/archive-2.5.2.xx
>>> -
>>> 2
>>> 0110929-1700-e36.zip
>>>
>>> The bundles.info file contains the information for the OSGi runtime as to what bundles are installed and whether or not they should be autostarted.  The update.xml is used by the update manager to determine what is currently installed in your system.
>>>
>>> I would think that you would need to edit both of these.  In the platform.xml, remove the line about the RSA jdt core patch.  In the bundles.info file, change the line on jdt.core to point to the unpatched version of the bundle (I think it is org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar).  Then, delete the RSA feature patch and associated jar from your system.  And finally, try installing Groovy-Eclipse.  This *may* work.
>>>
>>>
>>> On Wed, Nov 23, 2011 at 3:02 AM, Thomas Hofmann <[hidden email]> wrote:
>>>> Hi Andy,
>>>>
>>>> I am not aware of any version using Eclipse 3.7. Future version will certainly do.
>>>>
>>>> I would also rather not touch the platform.xml but it might be a workaround that could be automated and rolled back before an upgrade.
>>>> Do you know how the platform.xml and the simpleconfigurator / bundles.info relate to each other?
>>>>
>>>> Is there any downloadable version of the stable groovy eclipse update site / repository archive? I already searched but could not find a reference to it.  I only saw archived dev builds available.
>>>>
>>>> I'm favoring having downloadable archives so that I am sure I can supply the necessary software when other developers need to do a fresh install with the versions that I am sure work together. For this, downloadable archives would be great to have.
>>>>
>>>> In your first post you mentioned that you are not sure whether a feature patch can patch another feature patch and would would be the consequences. Did you think about this idea some more?
>>>>
>>>> This situation effectively means that the Groovy Eclipse plug-in cannot be installed into the current version of I believe all Rational tools that use the JDT.
>>>>
>>>> During installation of the Rational product it is possible to install into an existing eclipse version. I never tried this option and I wonder what would happen to the JDT in this scenario. Probably the feature patch would also be applied. I might test this. Anyway I think this installation method will cause more update problems than the regular way to install.
>>>>
>>>> Thomas
>>>>
>>>> -----Original Message-----
>>>> From: [hidden email]
>>>> [mailto:[hidden email]]
>>>> On Behalf Of Andrew Eisenberg
>>>> Sent: Dienstag, 22. November 2011 17:25
>>>> To: [hidden email]
>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>
>>>> Hi Thomas,
>>>>
>>>> OTDT uses a feature patch as well, so it would not be installable into RSA either.  The JDT Weaving approach is not feasible for Groovy-Eclipse because of the kinds of changes we need to make to JDT.
>>>>  JDT weaving (because it uses aspectj) requires well-defined pointcuts to work, but these are not available for the places we need to plug in to groovy-eclipse.
>>>>
>>>> So, I really can't think of any easy fixes here.  Is there a 3.7-based version of RSA that you can use?  Another possibility is that you can manually change the platform.xml so that it points to the groovy-eclipse version of JDT instead of the RSA version (you would also need to download the groovy-eclipse udpate site as a zip).  As I said, I'm not familiar with RSA, so I don't know how they manage their artifacts and if you do change things manually, you may make it harder to upgrade later, but this may be your only chance to get it working.
>>>>
>>>> I wish I had a better answer for you.
>>>>
>>>>
>>>>
>>>> On Tue, Nov 22, 2011 at 12:46 AM, Thomas Hofmann <[hidden email]> wrote:
>>>>> Hi Andy,
>>>>>
>>>>> I'm not sure if removing the feature from the features directory would make any difference. RSA uses platform.xml to define which plug-ins make up the runtime. As far as I know platform.xml is written by the IBM Installation Manager when you install / update or change the installation of a product.
>>>>> The Rational tools all share there plug-ins in a shared directory. So almost all plug-ins and features are placed in a directory named SDPShared by default. Each product installation then has ist own config are where the platform.xml describes which plug-ins to pick from the shared directory. I'm not quite sure how the bundles.info is involved and how it gets poupulated.
>>>>> In addition, when features are installed through Eclipse's p2 installed the end up in SDPShared\plugins\plugins directory and SDPShared\plugins\features which is a little weird.
>>>>>
>>>>> I'm having the problem not only with Rational Software Architect but also with Rational Functional Tester. Rational Application Developer will certainly also be affected.
>>>>>
>>>>> This seems to be a real show stopper for using the Groovy plug-in with the latest version of Rational tools.
>>>>>
>>>>> If I stay with older versions of the products I am able to install the Groovy Eclipse Plug-in. It seems that the JDT patches were introduced only in recent updates of the Rational products.
>>>>>
>>>>> Do you have any idea on how else this could be solved?
>>>>>
>>>>> What are the changes being made to the JDT that the Groovy plug-in requires? Could they in theory be applied without patching the JDT by using JDT weaving or Object Teams or something similar?
>>>>>
>>>>> In my current installation which has the Groovy Plug-In installed I find the following:
>>>>>
>>>>> Features:
>>>>> org.eclipse.jdt.R342patch_1.0.15
>>>>> org.eclipse.jdt.R342patch_1.0.19
>>>>> org.eclipse.jdt.R361patch_1.0.0
>>>>>
>>>>> Plug-ins:
>>>>> org.eclipse.jdt.core_3.4.4.v_894_R34x.jar
>>>>> org.eclipse.jdt.core_3.4.13.v_903_R34x.jar
>>>>> org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar
>>>>> org.eclipse.jdt.core_3.6.1.xx-20101215-2100-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110329-1600-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110527-2000-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110719-1100-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110921-1500-e36.jar
>>>>> org.eclipse.jdt.core_3.6.2.xx-20110930-1300-e36.jar
>>>>>
>>>>> So it seams that 3.6.2 is not patched and that is why I was able to install the Groovy Plug-in.
>>>>>
>>>>> When I install an update for the Rational product I will get the patches for version 3.6.2 and 3.6.3 I guess.
>>>>>
>>>>> Staying at an outdated version is not really an option because usually you need to update to some later version to resolve some bugs.
>>>>>
>>>>> As long as the updates include JDT patches from Rational Groovy will no longer install if I understand correctly.
>>>>>
>>>>> Thomas
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: [hidden email]
>>>>> [mailto:[hidden email]]
>>>>> On Behalf Of Andrew Eisenberg
>>>>> Sent: Montag, 21. November 2011 17:43
>>>>> To: [hidden email]
>>>>> Subject: Re: [groovy-eclipse-plugin-user] Support for JDT Core 3.6.3?
>>>>>
>>>>> Unfortunately, it won't be that easy.
>>>>>
>>>>>   From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>> Eclipse Java Development Tools
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>> (org.eclipse.jdt.feature.group
>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>
>>>>> This line implies that RSA ships with its own JDT core feature patch.
>>>>> I don't know if it is possible to patch a feature patch.  But, if you were to remove the  org.eclipse.jdt.R362patch.feature.group feature patch, then I would imagine that the groovy-eclipse feature patch would install.
>>>>>
>>>>> However, of course, you would then lose any functionality and bug fixes that the other feature patch adds for you.
>>>>>
>>>>> I would first suggest that you play around with this and see if by removing the other feature patch, you can get groovy-eclipse to install.  You can try simply removing the other feature patch from the features directory and then restart RSA with the -clean option.  You may also need to remove the plugin from the plugins directory.  (I'd recommend trying this out in a second instance of RSA so that you don't disturb the instance you actually use).
>>>>>
>>>>> Please let me know if you try this out and I can help you walk through any other problems you may have.
>>>>>
>>>>> On Mon, Nov 21, 2011 at 8:11 AM, Andy Clement <[hidden email]> wrote:
>>>>>> Hi,
>>>>>>
>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>
>>>>>> There is no further work planned for 3.6. But as it appears to be
>>>>>> an RSA distribution that has the problem, that does perhaps
>>>>>> increase the importance of doing something here.  I'm not sure
>>>>>> what fixes went in that required a 3.6.3, but the cheapest
>>>>>> feasible option is just to rev our version numbers so that it
>>>>>> will install into this environment
>>>>>> - it will effectively be downgrading JDT to 3.6.2 in the process
>>>>>> but at least it would install.  Perhaps raise a jira and let's
>>>>>> see if it attracts some votes.
>>>>>>
>>>>>> cheers,
>>>>>> Andy
>>>>>>
>>>>>> On 21 November 2011 03:47, Thomas Hofmann <[hidden email]> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am trying to install the groovy eclipse plug-in into a version of Rational Software Architect and I get dependecy problems:
>>>>>>>
>>>>>>> Cannot complete the install because of a conflicting dependency.
>>>>>>>  Software being installed: Groovy-Eclipse Feature
>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>  Only one of the following can be installed at once:
>>>>>>>    Java Development Tools Core 3.6.2.xx-20110929-1700-e36
>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20110929-1700-e36)
>>>>>>>    Java Development Tools Core 3.6.2.xx-20111107-1100-e36
>>>>>>> (org.eclipse.jdt.core 3.6.2.xx-20111107-1100-e36)
>>>>>>>    Java Development Tools Core 3.6.3.v_A77_R36x
>>>>>>> (org.eclipse.jdt.core
>>>>>>> 3.6.3.v_A77_R36x)
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: Groovy-Eclipse Feature 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.eclipse.feature.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>    To: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> [2.5.2.xx-20110929-1700-e36]
>>>>>>>  Cannot satisfy dependency:
>>>>>>>    From: JDT Core patch for Groovy-Eclipse plugin
>>>>>>> 2.5.2.xx-20110929-1700-e36
>>>>>>> (org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36)
>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,3.7.0)  Cannot
>>>>>>> satisfy dependency:
>>>>>>>    From: Data Tools Platform JDT Enablement
>>>>>>> 1.8.2.v201010181125-2-07w31211518181A
>>>>>>> (org.eclipse.datatools.enablement.jdt.feature.feature.group
>>>>>>> 1.8.2.v201010181125-2-07w31211518181A)
>>>>>>>    To: org.eclipse.jdt.feature.group 3.4.0  Cannot satisfy
>>>>>>> dependency:
>>>>>>>    From: Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.ant.launching [1.0.1.v20101020_r362]  Cannot
>>>>>>> satisfy dependency:
>>>>>>>    From: Eclipse Plug-in Development Environment
>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL
>>>>>>> (org.eclipse.pde.feature.group
>>>>>>> 3.6.2.r362_v20110203-7b7mFL2FET3dhHalh1iNZtL)
>>>>>>>    To: org.eclipse.jdt.feature.group [3.6.0,4.0.0)  Cannot
>>>>>>> satisfy dependency:
>>>>>>>    From Patch: org.codehaus.groovy.jdt.patch.feature.group
>>>>>>> 2.5.2.xx-20110929-1700-e36 Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.jdt.core [3.6.2.xx-20110929-1700-e36]  Cannot
>>>>>>> satisfy dependency:
>>>>>>>    From Patch: org.eclipse.jdt.R362patch.feature.group 1.0.2
>>>>>>> Eclipse Java Development Tools
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
>>>>>>> (org.eclipse.jdt.feature.group
>>>>>>> 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F)
>>>>>>>    To: org.eclipse.jdt.core [3.6.3.v_A77_R36x]  Optional
>>>>>>> dependency
>>>>>>>
>>>>>>> I'm not sure if I understand it correctly but I think the problem is caused by the fact that some other plug-in requires Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) with which the groovy plu-in won't work. This might be related to  Data Tools Platform JDT Enablement 1.8.2.v201010181125-2-07w31211518181A (org.eclipse.datatools.enablement.jdt.feature.feature.group 1.8.2.v201010181125-2-07w31211518181A). Uninstalling the data tools did not have an effecto though.
>>>>>>>
>>>>>>> Now my question is if there is any support planned for Java Development Tools Core 3.6.3.v_A77_R36x (org.eclipse.jdt.core 3.6.3.v_A77_R36x) in groovy eclipse? I tried a dev build but had the same problems.
>>>>>>>
>>>>>>> Thanks, Thomas
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> -
>>>>>>> -
>>>>>>> -
>>>>>>> -
>>>>>>> - To unsubscribe from this list, please visit:
>>>>>>>
>>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> -
>>>>>> -
>>>>>> -
>>>>>> - To unsubscribe from this list, please visit:
>>>>>>
>>>>>>    http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> - To unsubscribe from this list, please visit:
>>>>>
>>>>>    http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe from this list, please visit:
>>>>
>>>>    http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe from this list, please visit:
>>>
>>>    http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


12