Ah crap .. Thanks Pierre ... Actually I had not used the new plugin
properly installed yet, only running it as an Eclipse application
(where those don't matter).
Thanks a lot!
ms
On Jun 26, 2006, at 9:10 PM, Pierre Frisch wrote:
> Hi Mike,
>
> I fixed it. I think you forgot to commit your build.xml -:).
>
> You need to add the include in the jar section of workspace/
> woproject/wolips/plugins/org.objectstyle.wolips.eogenerator.ui/
> build.xml
>
> <target name="jar">
> <patternset id="param.classes.patternset.refid">
> <include name="**/org/objectstyle/wolips/eogenerator/ui/**" />
> <include name="**/org/objectstyle/wolips/eogenerator/builder/**" />
> <include name="**/org/objectstyle/wolips/eogenerator/locate/**" />
> <include name="**/org/objectstyle/wolips/eogenerator/model/**" />
> </patternset>
>
> At least it fixed it for me.
>
> Thanks
>
> Pierre
>
> On 26-Jun-06, at 5:11 PM, Pierre Frisch wrote:
>
>> Hi Mike,
>>
>> I think this need urgent attention the new versions are broken. I
>> tried to update to the latest version and got and error in the
>> eogenerate action so I installed a clean copy of eclipse and
>> reinstalled and updated to the latest and greatest of all plug-ins
>> and feature and I get a NoClassDefFoundError exception when I try
>> to generate the classes.
>>
>> Thanks
>>
>> Pierre
>>
>> U ERROR
>> java.lang.NoClassDefFoundError: org/objectstyle/wolips/eogenerator/
>> model/EOGenerateWorkspaceJob
>> at
>> org.objectstyle.wolips.eogenerator.ui.actions.GenerateAction.run
>> (GenerateAction.java:78)
>> at org.eclipse.ui.internal.PluginAction.runWithEvent
>> (PluginAction.java:254)
>> at
>> org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
>> (ActionContributionItem.java:539)
>> at org.eclipse.jface.action.ActionContributionItem.access$2
>> (ActionContributionItem.java:488)
>> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent
>> (ActionContributionItem.java:400)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1496)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
>> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
>> 3312)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:
>> 2941)
>> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
>> 1914)
>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
>> (Workbench.java:419)
>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench
>> (PlatformUI.java:149)
>> at org.eclipse.ui.internal.ide.IDEApplication.run
>> (IDEApplication.java:95)
>> at org.eclipse.core.internal.runtime.PlatformActivator$1.run
>> (PlatformActivator.java:78)
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli
>> cation(EclipseAppLauncher.java:92)
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
>> (EclipseAppLauncher.java:68)
>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>> (EclipseStarter.java:400)
>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
>> (EclipseStarter.java:177)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>> at org.eclipse.core.launcher.Main.run(Main.java:977)
>> at org.eclipse.core.launcher.Main.main(Main.java:952)
>>
>> On 26-Jun-06, at 1:38 PM, Mike Schrag wrote:
>>
>>> I noticed this too ... I think it must be hardcoded in one of the
>>> plugin.xml files. I'll take a look and see.
>>>
>>> ms
>>>
>>> On Jun 26, 2006, at 4:34 PM, Marc Respass wrote:
>>>
>>>> Thanks Pierre,
>>>>
>>>> I did that and it didn't work but I figured out why. After
>>>> installing WOLips, I got a site added to my updates site. The
>>>> site is the old update site at (http://www.objectstyle.org/
>>>> woproject/update) instead of the new one at (http://
>>>> www.mdimension.com/~wolips/update/). After adding a new update
>>>> site at the correct address, I was able to force an update.
>>>>
>>>> Where does the old site come from? I can't delete it. I even
>>>> tried exporting and importing sites but I can't get rid of the
>>>> old update site.
>>>>
>>>> Marc
>>>>
>>>> On Jun 26, 2006, at 4:24 PM, Pierre Frisch wrote:
>>>>
>>>>> Hi Marc,
>>>>>
>>>>> Go into "Search for new features" instead of "Search for
>>>>> updates" select wolips and you will see the update. But it
>>>>> should work with the other option.
>>>>>
>>>>> Pierre
>>>>> On 26-Jun-06, at 11:24 AM, Marc Respass wrote:
>>>>>
>>>>>> I was going to ask about this. How do I manually force the
>>>>>> update? The only thing I found was a way to check for updates
>>>>>> but the check fails.
>>>>>>
>>>>>> Marc
>>>>>>
>>>>>> On Jun 26, 2006, at 2:17 PM, Pierre Frisch wrote:
>>>>>>
>>>>>>> I am not sure why it does not work but it look like Eclipse
>>>>>>> is not picking up the new updates from our Web site.
>>>>>>>
>>>>>>> I was running 137 and I have setup Eclipse to check for
>>>>>>> updates at launch. The Web site is now at 139 and it does not
>>>>>>> show any updates. I have to manually force the update as it
>>>>>>> does not detects it. There is something not quite right there.
>>>>>>>
>>>>>>> The strange thing is that I have seen it work before going
>>>>>>> from 136 to 137.
>>>>>>>
>>>>>>> Pierre
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Tue Jun 27 2006 - 08:05:55 EDT