Home » Eclipse Projects » Eclipse Platform » vss plugin with eclipse 3.3
| vss plugin with eclipse 3.3 [message #315354] |
Wed, 09 May 2007 03:27  |
 Zohar Amir
Messages: 419
Registered: July 2009 |
Senior Member |
|
|
Hi,
I've been using the VSS plugin for a while now - no major complaints. I just
installed eclipse 3.3. (M7) and now I have problems - I get the following
message:
Unable to create view: Plug-in "org.vssplugin" was unable to instantiate
class "org.vssplugin.ui.view.CheckOutView".
(class: org/vssplugin/ui/view/CheckOutView, method: <init> signature: ()V)
Incompatible argument to function
Can anyone help me with this please?
Thanks,
Zohar.
|
|
|
| Re: vss plugin with eclipse 3.3 [message #315356 is a reply to message #315354] |
Wed, 09 May 2007 03:40  |
|
Originally posted by: krzysztofHMMMMdaniel.gmail.com
Hi Zohar
Migrating from one milestone to another always is a bit risky.
M version, although are meant to be stable, do not have to be compliant
which each other. You should check if there is VSS plugin version that
supports eclipse 3.3M7, then try with dev version of VSS.
If nothing works, than you have consider rolling back to 3.3M6.
HTH
Chris
|
|
| |
| Re: vss plugin with eclipse 3.3 [message #315364 is a reply to message #315358] |
Wed, 09 May 2007 05:38 |
|
Originally posted by: krzysztofHMMMMdaniel.gmail.com
Zohar,
this is not a problem of eclipse, but of VSS plugin. And if it has been
abandoned, I do not see any chances, that it will work.
Regards,
Chris
|
|
|
| Re: vss plugin with eclipse 3.3 [message #315607 is a reply to message #315364] |
Tue, 15 May 2007 16:43 |
|
Originally posted by: Jim.Cooper.sas.com
Seriously, this is probably a good time to move from VSS to something else.
You wouldn't want to read through the complete list of problems we found
with VSS here at work, but let's just say there are more than a few. We
haven't used VSS for several years due to the problems we found (which have
still never been fixed, to my knowledge... though I admit I stopped keeping
close track of it when we stopped using it).
CVS is free, and it's easy enough to switch over... just use google to find
an ancient script named "vss2cvs".
"Krzysztof Daniel" <krzysztofHMMMMdaniel@gmail.com> wrote in message
news:f1s4r9$2kd$2@build.eclipse.org...
> Zohar,
>
> this is not a problem of eclipse, but of VSS plugin. And if it has been
> abandoned, I do not see any chances, that it will work.
>
> Regards,
> Chris
|
|
| |
| Re: vss plugin with eclipse 3.3 [message #315803 is a reply to message #315783] |
Wed, 23 May 2007 09:14 |
|
Jeff Barcalow wrote:
> The stack trace is:
> java.lang.VerifyError: (class: org/vssplugin/ui/view/CheckOutView,
> method: <init> signature: ()V) Incompatible argument to function
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
> at java.lang.Class.getConstructor0(Unknown Source)
> at java.lang.Class.newInstance0(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at
> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:170)
That is an odd error from the vssplugin ...
RegistryStrategyOSGI.createExecutableExtension(*) always create the
no-arg constructor, and I'm sure CheckOutView has always provided one.
Is it complaining about the binary compatibility of the vss
CheckOutView? If CheckOutView didn't have a no-arg constructor I'd
expect that it was some kind of no method found error.
After M6 only PMC approved API changes were allowed. That's very small
number. Which API do you think has changed?
PW
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
|
|
| |
| Re: vss plugin with eclipse 3.3 [message #315853 is a reply to message #315607] |
Thu, 24 May 2007 03:47 |
Zohar Amir
Messages: 419
Registered: July 2009 |
Senior Member |
|
|
This decision is not mine to take. I would have moved to Subversion a long
time ago, but...
Bottom line is - I need to use VSS and the plugin stopped functioning in M7,
so it's either working with the VSS client separately from eclipse, or
finding someone who can fix the plugin.
"Jim Cooper" <Jim.Cooper@sas.com> wrote in message
news:f2d61d$vfr$1@build.eclipse.org...
> Seriously, this is probably a good time to move from VSS to something
> else.
>
> You wouldn't want to read through the complete list of problems we found
> with VSS here at work, but let's just say there are more than a few. We
> haven't used VSS for several years due to the problems we found (which
> have still never been fixed, to my knowledge... though I admit I stopped
> keeping close track of it when we stopped using it).
>
> CVS is free, and it's easy enough to switch over... just use google to
> find an ancient script named "vss2cvs".
>
> "Krzysztof Daniel" <krzysztofHMMMMdaniel@gmail.com> wrote in message
> news:f1s4r9$2kd$2@build.eclipse.org...
>> Zohar,
>>
>> this is not a problem of eclipse, but of VSS plugin. And if it has been
>> abandoned, I do not see any chances, that it will work.
>>
>> Regards,
>> Chris
>
>
|
|
| | | |
| Re: vss plugin with eclipse 3.3 [message #316052 is a reply to message #315960] |
Wed, 30 May 2007 01:19 |
Jeff Barcalow
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
1. make sure CVS and PDE plugins are in eclipse
2. use eclipse 3.3M7 or later, create a new eclipse project for the vssplugin
3. Right click on project, Team -> Share Project...
4. CVS. Next> Create New Repository Location. Next>
5. Host: vssplugin.cvs.sourceforge.net
Repository path: /cvsroot/vssplugin
User: anonymous
Connection type: pserver
Use port: 2401
Use an existing module...
vssplugin-core
Next>
Select Tag: HEAD
Next>
6. This will download all of the files.
After getting the files, you will see compile errors. You may fix them yourself (they are pretty
straight forward) or may overlay the patch.
Patch the .class files from the vssplugin/bin directory into the vssplugin.jar.
If you fix some of the deprecated warnings, you may also be able to get rid of the "begin rule"
exceptions.
-Jeff
Zohar wrote:
> Thanks Jeff,
> Can you explain how I can get a working plugin? I'll be glad to help you
> test it...
>
> Thanks,
> Zohar.
>
> "Jeff Barcalow" <barcalow@xnet.com> wrote in message
> news:f35nr4$d9s$1@build.eclipse.org...
>> Jeff Barcalow wrote:
>>> Paul Webster wrote:
>>>> Jeff Barcalow wrote:
>>>>> The stack trace is:
>>>>> java.lang.VerifyError: (class: org/vssplugin/ui/view/CheckOutView,
>>>>> method: <init> signature: ()V) Incompatible argument to function
>>>>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>>>>> at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
>>>>> at java.lang.Class.getConstructor0(Unknown Source)
>>>>> at java.lang.Class.newInstance0(Unknown Source)
>>>>> at java.lang.Class.newInstance(Unknown Source)
>>>>> at
>>>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:170)
>>>>>
>>>>
>>>>
>>>>
>>>> That is an odd error from the vssplugin ...
>>>> RegistryStrategyOSGI.createExecutableExtension(*) always create the
>>>> no-arg constructor, and I'm sure CheckOutView has always provided
>>>> one. Is it complaining about the binary compatibility of the vss
>>>> CheckOutView? If CheckOutView didn't have a no-arg constructor I'd
>>>> expect that it was some kind of no method found error.
>>>>
>>>> After M6 only PMC approved API changes were allowed. That's very
>>>> small number. Which API do you think has changed?
>>>>
>>>> PW
>>>
>>> I am not familiar with the vssplugin code, but I just grabbed
>>> part of it from sourceforge. It compiles with 3.3M6, but with
>>> 3.3.M7 it has 32 compile errors. The VerifyError is because
>>> CheckOutView has data members that inherit from eclipse objects,
>>> but no longer have a consistent class hierarchy.
>>>
>>> Most look errors like they are related to vssplugin classes that
>>> inherited from
>>> org.eclipse.team.internal.ui.actions.TeamAction
>>> Maybe the vssplugin should not have inherited from a class in an
>>> "internal" package.
>>>
>>> It looks like in M6 TeamAction extends ActionDelegate while M7
>>> extends AbstractHandler.
>>>
>>> - 13 of the errors are because TeamAction added an abstract method
>>> executed(IAction).
>>>
>>> - 6 of the errors are because of a thrown exception change with
>>> isEnabled()
>>>
>>> - 4 of the errors are "cannot reduce the visibility of inherited method"
>>> AbstractHandler.isEnabled()
>>>
>>> - 9 of the errors are because ActionDelegate objects are now
>>> IActionDelegate.
>>>
>>> It is relatively easy to fix the compile errors, but that does not
>>> mean the
>>> plug-in is working correctly.
>>>
>>>
>>> -Jeff
>>
>>
>> I've posted a "potential" source code patch at:
>> http://sourceforge.net/tracker/?group_id=54205&atid=4730 13
>>
>> I could not post the jar because of an attachment size limit.
>> Anyone interested in using this would have to get the rest
>> of the project from the CVS and then apply the changes.
>>
>> I'm still testing the modified JAR myself.
>>
>> -Jeff
>
|
|
|
| Re: vss plugin with eclipse 3.3 [message #316125 is a reply to message #316052] |
Thu, 31 May 2007 09:15 |
Zohar Amir
Messages: 419
Registered: July 2009 |
Senior Member |
|
|
It tries to import org.eclipse.core.runtime.IProgressMonitor - where do I
get it from?
"Jeff Barcalow" <barcalow@xnet.com> wrote in message
news:f3j1ho$lco$1@build.eclipse.org...
> 1. make sure CVS and PDE plugins are in eclipse
> 2. use eclipse 3.3M7 or later, create a new eclipse project for the
> vssplugin
> 3. Right click on project, Team -> Share Project...
> 4. CVS. Next> Create New Repository Location. Next>
> 5. Host: vssplugin.cvs.sourceforge.net
> Repository path: /cvsroot/vssplugin
> User: anonymous
> Connection type: pserver
> Use port: 2401
> Use an existing module...
> vssplugin-core
> Next>
> Select Tag: HEAD
> Next>
>
> 6. This will download all of the files.
>
>
> After getting the files, you will see compile errors. You may fix them
> yourself (they are pretty straight forward) or may overlay the patch.
>
> Patch the .class files from the vssplugin/bin directory into the
> vssplugin.jar.
>
> If you fix some of the deprecated warnings, you may also be able to get
> rid of the "begin rule" exceptions.
>
> -Jeff
>
>
> Zohar wrote:
>> Thanks Jeff,
>> Can you explain how I can get a working plugin? I'll be glad to help you
>> test it...
>>
>> Thanks,
>> Zohar.
>>
>> "Jeff Barcalow" <barcalow@xnet.com> wrote in message
>> news:f35nr4$d9s$1@build.eclipse.org...
>>> Jeff Barcalow wrote:
>>>> Paul Webster wrote:
>>>>> Jeff Barcalow wrote:
>>>>>> The stack trace is:
>>>>>> java.lang.VerifyError: (class: org/vssplugin/ui/view/CheckOutView,
>>>>>> method: <init> signature: ()V) Incompatible argument to function
>>>>>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>>>>>> at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
>>>>>> at java.lang.Class.getConstructor0(Unknown Source)
>>>>>> at java.lang.Class.newInstance0(Unknown Source)
>>>>>> at java.lang.Class.newInstance(Unknown Source)
>>>>>> at
>>>>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:170)
>>>>>
>>>>>
>>>>>
>>>>> That is an odd error from the vssplugin ...
>>>>> RegistryStrategyOSGI.createExecutableExtension(*) always create the
>>>>> no-arg constructor, and I'm sure CheckOutView has always provided one.
>>>>> Is it complaining about the binary compatibility of the vss
>>>>> CheckOutView? If CheckOutView didn't have a no-arg constructor I'd
>>>>> expect that it was some kind of no method found error.
>>>>>
>>>>> After M6 only PMC approved API changes were allowed. That's very
>>>>> small number. Which API do you think has changed?
>>>>>
>>>>> PW
>>>>
>>>> I am not familiar with the vssplugin code, but I just grabbed
>>>> part of it from sourceforge. It compiles with 3.3M6, but with
>>>> 3.3.M7 it has 32 compile errors. The VerifyError is because
>>>> CheckOutView has data members that inherit from eclipse objects,
>>>> but no longer have a consistent class hierarchy.
>>>>
>>>> Most look errors like they are related to vssplugin classes that
>>>> inherited from
>>>> org.eclipse.team.internal.ui.actions.TeamAction
>>>> Maybe the vssplugin should not have inherited from a class in an
>>>> "internal" package.
>>>>
>>>> It looks like in M6 TeamAction extends ActionDelegate while M7
>>>> extends AbstractHandler.
>>>>
>>>> - 13 of the errors are because TeamAction added an abstract method
>>>> executed(IAction).
>>>>
>>>> - 6 of the errors are because of a thrown exception change with
>>>> isEnabled()
>>>>
>>>> - 4 of the errors are "cannot reduce the visibility of inherited
>>>> method"
>>>> AbstractHandler.isEnabled()
>>>>
>>>> - 9 of the errors are because ActionDelegate objects are now
>>>> IActionDelegate.
>>>>
>>>> It is relatively easy to fix the compile errors, but that does not mean
>>>> the
>>>> plug-in is working correctly.
>>>>
>>>>
>>>> -Jeff
>>>
>>>
>>> I've posted a "potential" source code patch at:
>>> http://sourceforge.net/tracker/?group_id=54205&atid=4730 13
>>>
>>> I could not post the jar because of an attachment size limit.
>>> Anyone interested in using this would have to get the rest
>>> of the project from the CVS and then apply the changes.
>>>
>>> I'm still testing the modified JAR myself.
>>>
>>> -Jeff
>>
|
|
|
| Re: vss plugin with eclipse 3.3 [message #316235 is a reply to message #316125] |
Sat, 02 June 2007 17:39 |
Jeff Barcalow
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
org.eclipse.equinox.common_*.jar
For me it is in the "Plug-in Dependencies" grouping of JARs. Maybe you need the SDK versions of
eclipse, PDE, and CVS.
I did not have to do anything special pull in that dependency. I believe eclipse picked it up from
the .classpath at
http://vssplugin.cvs.sourceforge.net/vssplugin/vssplugin_ole /.classpath
-Jeff
Zohar wrote:
> It tries to import org.eclipse.core.runtime.IProgressMonitor - where do
> I get it from?
>
> "Jeff Barcalow" <barcalow@xnet.com> wrote in message
> news:f3j1ho$lco$1@build.eclipse.org...
>> 1. make sure CVS and PDE plugins are in eclipse
>> 2. use eclipse 3.3M7 or later, create a new eclipse project for the
>> vssplugin
>> 3. Right click on project, Team -> Share Project...
>> 4. CVS. Next> Create New Repository Location. Next>
>> 5. Host: vssplugin.cvs.sourceforge.net
>> Repository path: /cvsroot/vssplugin
>> User: anonymous
>> Connection type: pserver
>> Use port: 2401
>> Use an existing module...
>> vssplugin-core
>> Next>
>> Select Tag: HEAD
>> Next>
>>
>> 6. This will download all of the files.
>>
>>
>> After getting the files, you will see compile errors. You may fix
>> them yourself (they are pretty straight forward) or may overlay the
>> patch.
>>
>> Patch the .class files from the vssplugin/bin directory into the
>> vssplugin.jar.
>>
>> If you fix some of the deprecated warnings, you may also be able to
>> get rid of the "begin rule" exceptions.
>>
>> -Jeff
>>
>>
>> Zohar wrote:
>>> Thanks Jeff,
>>> Can you explain how I can get a working plugin? I'll be glad to help
>>> you test it...
>>>
>>> Thanks,
>>> Zohar.
>>>
>>> "Jeff Barcalow" <barcalow@xnet.com> wrote in message
>>> news:f35nr4$d9s$1@build.eclipse.org...
>>>> Jeff Barcalow wrote:
>>>>> Paul Webster wrote:
>>>>>> Jeff Barcalow wrote:
>>>>>>> The stack trace is:
>>>>>>> java.lang.VerifyError: (class:
>>>>>>> org/vssplugin/ui/view/CheckOutView, method: <init> signature:
>>>>>>> ()V) Incompatible argument to function
>>>>>>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>>>>>>> at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
>>>>>>> at java.lang.Class.getConstructor0(Unknown Source)
>>>>>>> at java.lang.Class.newInstance0(Unknown Source)
>>>>>>> at java.lang.Class.newInstance(Unknown Source)
>>>>>>> at
>>>>>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:170)
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> That is an odd error from the vssplugin ...
>>>>>> RegistryStrategyOSGI.createExecutableExtension(*) always create
>>>>>> the no-arg constructor, and I'm sure CheckOutView has always
>>>>>> provided one. Is it complaining about the binary compatibility of
>>>>>> the vss CheckOutView? If CheckOutView didn't have a no-arg
>>>>>> constructor I'd expect that it was some kind of no method found
>>>>>> error.
>>>>>>
>>>>>> After M6 only PMC approved API changes were allowed. That's very
>>>>>> small number. Which API do you think has changed?
>>>>>>
>>>>>> PW
>>>>>
>>>>> I am not familiar with the vssplugin code, but I just grabbed
>>>>> part of it from sourceforge. It compiles with 3.3M6, but with
>>>>> 3.3.M7 it has 32 compile errors. The VerifyError is because
>>>>> CheckOutView has data members that inherit from eclipse objects,
>>>>> but no longer have a consistent class hierarchy.
>>>>>
>>>>> Most look errors like they are related to vssplugin classes that
>>>>> inherited from
>>>>> org.eclipse.team.internal.ui.actions.TeamAction
>>>>> Maybe the vssplugin should not have inherited from a class in an
>>>>> "internal" package.
>>>>>
>>>>> It looks like in M6 TeamAction extends ActionDelegate while M7
>>>>> extends AbstractHandler.
>>>>>
>>>>> - 13 of the errors are because TeamAction added an abstract method
>>>>> executed(IAction).
>>>>>
>>>>> - 6 of the errors are because of a thrown exception change with
>>>>> isEnabled()
>>>>>
>>>>> - 4 of the errors are "cannot reduce the visibility of inherited
>>>>> method"
>>>>> AbstractHandler.isEnabled()
>>>>>
>>>>> - 9 of the errors are because ActionDelegate objects are now
>>>>> IActionDelegate.
>>>>>
>>>>> It is relatively easy to fix the compile errors, but that does not
>>>>> mean the
>>>>> plug-in is working correctly.
>>>>>
>>>>>
>>>>> -Jeff
>>>>
>>>>
>>>> I've posted a "potential" source code patch at:
>>>> http://sourceforge.net/tracker/?group_id=54205&atid=4730 13
>>>>
>>>> I could not post the jar because of an attachment size limit.
>>>> Anyone interested in using this would have to get the rest
>>>> of the project from the CVS and then apply the changes.
>>>>
>>>> I'm still testing the modified JAR myself.
>>>>
>>>> -Jeff
>>>
|
|
|
| Re: vss plugin with eclipse 3.3 [message #316318 is a reply to message #316235] |
Wed, 06 June 2007 01:49 |
Zohar Amir
Messages: 419
Registered: July 2009 |
Senior Member |
|
|
I seem to have trouble creating the plugin.
Do you have a built plugin I can use? Are you planning on submitting this
fix to the sourcrforge project somehow (maybe as 1.7.0)?
Thanks,
Zohar.
"Jeff Barcalow" <barcalow@xnet.com> wrote in message
news:4661E38A.20507@xnet.com...
> org.eclipse.equinox.common_*.jar
>
> For me it is in the "Plug-in Dependencies" grouping of JARs. Maybe you
> need the SDK versions of eclipse, PDE, and CVS.
>
> I did not have to do anything special pull in that dependency. I believe
> eclipse picked it up from the .classpath at
> http://vssplugin.cvs.sourceforge.net/vssplugin/vssplugin_ole /.classpath
>
> -Jeff
>
> Zohar wrote:
>> It tries to import org.eclipse.core.runtime.IProgressMonitor - where do I
>> get it from?
>>
>> "Jeff Barcalow" <barcalow@xnet.com> wrote in message
>> news:f3j1ho$lco$1@build.eclipse.org...
>>> 1. make sure CVS and PDE plugins are in eclipse
>>> 2. use eclipse 3.3M7 or later, create a new eclipse project for the
>>> vssplugin
>>> 3. Right click on project, Team -> Share Project...
>>> 4. CVS. Next> Create New Repository Location. Next>
>>> 5. Host: vssplugin.cvs.sourceforge.net
>>> Repository path: /cvsroot/vssplugin
>>> User: anonymous
>>> Connection type: pserver
>>> Use port: 2401
>>> Use an existing module...
>>> vssplugin-core
>>> Next>
>>> Select Tag: HEAD
>>> Next>
>>>
>>> 6. This will download all of the files.
>>>
>>>
>>> After getting the files, you will see compile errors. You may fix them
>>> yourself (they are pretty straight forward) or may overlay the patch.
>>>
>>> Patch the .class files from the vssplugin/bin directory into the
>>> vssplugin.jar.
>>>
>>> If you fix some of the deprecated warnings, you may also be able to get
>>> rid of the "begin rule" exceptions.
>>>
>>> -Jeff
>>>
>>>
>>> Zohar wrote:
>>>> Thanks Jeff,
>>>> Can you explain how I can get a working plugin? I'll be glad to help
>>>> you test it...
>>>>
>>>> Thanks,
>>>> Zohar.
>>>>
>>>> "Jeff Barcalow" <barcalow@xnet.com> wrote in message
>>>> news:f35nr4$d9s$1@build.eclipse.org...
>>>>> Jeff Barcalow wrote:
>>>>>> Paul Webster wrote:
>>>>>>> Jeff Barcalow wrote:
>>>>>>>> The stack trace is:
>>>>>>>> java.lang.VerifyError: (class: org/vssplugin/ui/view/CheckOutView,
>>>>>>>> method: <init> signature: ()V) Incompatible argument to function
>>>>>>>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>>>>>>>> at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
>>>>>>>> at java.lang.Class.getConstructor0(Unknown Source)
>>>>>>>> at java.lang.Class.newInstance0(Unknown Source)
>>>>>>>> at java.lang.Class.newInstance(Unknown Source)
>>>>>>>> at
>>>>>>>> org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:170)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> That is an odd error from the vssplugin ...
>>>>>>> RegistryStrategyOSGI.createExecutableExtension(*) always create the
>>>>>>> no-arg constructor, and I'm sure CheckOutView has always provided
>>>>>>> one. Is it complaining about the binary compatibility of the vss
>>>>>>> CheckOutView? If CheckOutView didn't have a no-arg constructor I'd
>>>>>>> expect that it was some kind of no method found error.
>>>>>>>
>>>>>>> After M6 only PMC approved API changes were allowed. That's very
>>>>>>> small number. Which API do you think has changed?
>>>>>>>
>>>>>>> PW
>>>>>>
>>>>>> I am not familiar with the vssplugin code, but I just grabbed
>>>>>> part of it from sourceforge. It compiles with 3.3M6, but with
>>>>>> 3.3.M7 it has 32 compile errors. The VerifyError is because
>>>>>> CheckOutView has data members that inherit from eclipse objects,
>>>>>> but no longer have a consistent class hierarchy.
>>>>>>
>>>>>> Most look errors like they are related to vssplugin classes that
>>>>>> inherited from
>>>>>> org.eclipse.team.internal.ui.actions.TeamAction
>>>>>> Maybe the vssplugin should not have inherited from a class in an
>>>>>> "internal" package.
>>>>>>
>>>>>> It looks like in M6 TeamAction extends ActionDelegate while M7
>>>>>> extends AbstractHandler.
>>>>>>
>>>>>> - 13 of the errors are because TeamAction added an abstract method
>>>>>> executed(IAction).
>>>>>>
>>>>>> - 6 of the errors are because of a thrown exception change with
>>>>>> isEnabled()
>>>>>>
>>>>>> - 4 of the errors are "cannot reduce the visibility of inherited
>>>>>> method"
>>>>>> AbstractHandler.isEnabled()
>>>>>>
>>>>>> - 9 of the errors are because ActionDelegate objects are now
>>>>>> IActionDelegate.
>>>>>>
>>>>>> It is relatively easy to fix the compile errors, but that does not
>>>>>> mean the
>>>>>> plug-in is working correctly.
>>>>>>
>>>>>>
>>>>>> -Jeff
>>>>>
>>>>>
>>>>> I've posted a "potential" source code patch at:
>>>>> http://sourceforge.net/tracker/?group_id=54205&atid=4730 13
>>>>>
>>>>> I could not post the jar because of an attachment size limit.
>>>>> Anyone interested in using this would have to get the rest
>>>>> of the project from the CVS and then apply the changes.
>>>>>
>>>>> I'm still testing the modified JAR myself.
>>>>>
>>>>> -Jeff
>>>>
|
|
|
| Re: vss plugin with eclipse 3.3 [message #317354 is a reply to message #316318] |
Tue, 03 July 2007 03:34 |
|
Originally posted by: nicolasa.twinsoft.fr
Hello,
Eclipse 3.3 is release now, nobody can make a new release of VSS plugin with a Eclipse 3.3 compability ?
Or, if the plugin works well for someone, can he upload it somewhere please ?
Thanks.
|
|
| |
| Re: vss plugin with eclipse 3.3 [message #317529 is a reply to message #317382] |
Fri, 06 July 2007 04:54 |
|
Originally posted by: mike.recantha.co.uk
You're an absolute star - it was driving me nuts not being able to use the latest version of Eclipse!
The only thing that's not happening now is that it's not asking me to add a VSS comment when I check-in. This could be a configuration issue on my part, however, so if anyone has any idea what I'm doing wrong, please let me know!
Very well done Jeff and Peter.
--
Michael Horne
|
|
| | |
Goto Forum:
Current Time: Tue Oct 08 08:13:59 EDT 2013
Powered by FUDForum. Page generated in 0.06974 seconds
|
] 
Search
Help
Register
Login
Home
