Thanks. That is what I did. (That is the way I used to do it, back when I
remembered this stuff better) However, if I want the “new wonder project”
template to work, I will need to install the built wonder frameworks in one of
the directories chuck listed. That is what I had forgotten (this
On 2015-06-23, 11:55 AM, "Andrew Kinnie" wrote:
Yes, It was clearly my issue, as I have not touched this in a while. In any
event, by pointing me to the wolips.properties file, I assume you mean that for
WOLips to know how to create a new wonder project using the template, the
wonder framewo
That is one valid approach. Another is to clone Wonder in eGit, then import all
the frameworks into the workspace and put them in their own working set so as
not to clutter up your WO Explorer tab. This way if you find a bug in wonder,
it’s easier to find/fix/submit.
On Jun 23, 2015, at 12:15 P
To work with Wonder the easy path is to clone the GitHub repository and
then build Wonder from the command line. It will create a Roots dir in
your home dir and then copy all the frameworks and jars to the proper
places. Don't forget to read BUILD.txt.
Good luck
PS: it is worth the effort, Wo
Yes, It was clearly my issue, as I have not touched this in a while. In any
event, by pointing me to the wolips.properties file, I assume you mean that for
WOLips to know how to create a new wonder project using the template, the
wonder frameworks need to be installed in the user frameworks dir
On 2015-06-23, 11:36 AM, "Andrew Kinnie" wrote:
Yes, I was starting to get the impression that Java was the issue, so I
re-downloaded the Java 8 jdk (evidently when googling how to install java I
ended up with the link that downloaded the jre and not the jdk. As I said, it
has been a while)
Yes, I was starting to get the impression that Java was the issue, so I
re-downloaded the Java 8 jdk (evidently when googling how to install java I
ended up with the link that downloaded the jre and not the jdk. As I said, it
has been a while)
Now I can access the properties and edit them. Ma
Unsupported major.minor version 51.0
Means you need to be running at least Java 1.7.
Chuck
On 2015-06-23, 9:59 AM, "Andrew Kinnie" wrote:
OK, when I do that precisely nothing happens. The only window is the welcome
view that opens when it starts. Thus far I have tried to create my own
work
My steps are
0. Install Java 8
1. Install Eclipse IDE for committers
2. Install WebObjects using WOInstaller.jar
3. Install wolips plugin from jenkins.wocommunity.org
4. make sure wolips.properties is okay either by editing it directly or setting
paths in the preferences dialog
Looking at buildi
OK, when I do that precisely nothing happens. The only window is the welcome
view that opens when it starts. Thus far I have tried to create my own
workspace directory, and have tried using the default ~/Documents/workspace
directory. All I get is the “welcome” view.
If I try and create a te
Try Window - Show View - Other - General - Error Log
Are there spaces in the path to Eclipse, the workspace, or your project?
Chuck
On 2015-06-23, 8:41 AM, "Andrew Kinnie" wrote:
Yeah, I tried that too. Does not seem to change anything. I don't know where
the file is that it is trying to lo
Yeah, I tried that too. Does not seem to change anything. I don’t know where
the file is that it is trying to load, but it seems like the file with the
issue is the one setting up the form itself. It does not appear to load the
properties file itself, or even know where it is.
Trying to look
Hi Andrew, I manually installed Luna 4.4.2, WOLips Eclipse plugin from
https://jenkins.wocommunity.org/job/WOLips44/lastSuccessfulBuild/artifact/temp/dist/
and WO from Apple's installer. Then setup the WO and Eclipse properties
without the WO versions as stated in the wiki (the versioning with
Greetings all…again.
It has been about a zillion years (ok, so I rounded up after I hit 3) since I
have done anything with webobjects, and thus I need to install fresh on my new
computer. I saw the install docs on the community list, but they seem pretty
out of date. I tried golipse but it se
Ute:
I think you're confusing "carbon" with "ppc." Carbon is still in Snow Leopard -
Rosetta (PPC interpreter) has to be explicitly installed. The latter has no
bearing on which version of Eclipse you run.
Tim Worman
UCLA GSE&IS
On Nov 27, 2009, at 1:42 AM, David Avendasora wrote:
> Ute,
>
Ute,
I don't think it's a carbon problem as lots of apps still use Carbon - iTunes
for example. I have a 3-month-old MacBook Pro and I can run Carbon Eclipse on
it.
Are you getting an error message when you try to launch Eclipse?
Dave
On Nov 27, 2009, at 3:46 AM, ute Hoffmann wrote:
> Hi
> I
Hi
I tried the turnkey installer, but eclipse does not come up.
So I looked for eclipse 3.4.2 to install it myself and found,
that I seem to need to use the carbon version.
Now: As I recall arbon is no longer by default installed/running on
new macs -
I may be wrong, but I remember one had to a
I had the same experience today installing the current stable WOLips
into a fresh Eclipse 3.4.1 installation (with an existing workspace
that I used in 3.3.2 before).
I had to create the wolips.properties file in the
~/Library/Application Support/WOLips folder (copied the content from
an example f
Hi,You probably need to check if ~/Library/Application Support/WOLips/wolips.properties exists and is correct. I think you miss it.If this is the case, you can either create a new working space and then create a new project so that WOLips plugin creates it for you,or get the attached one, change th
Hi,
I recently installed eclipse latest version and installed 'wolips'
plugins. After that I started eclipse and selected the previous
workspace that I used before.
But now eclipse gives error such as 'The import com.webobjects cannot be
resolved' etc. Previously (before install new eclipse an
Hi,
I recently installed eclipse latest version and installed 'wolips'
plugins. After that I started eclipse and selected the previous
workspace that I used before.
But now eclipse gives error such as 'The import com.webobjects cannot be
resolved' etc. Previously (before install new eclipse an
dates->Manage Configuration
you will find under Eclipse Platform that the Eclipse PLatform is
Eclipse Plaform 3.3.2.R33x_v20071022_[Lots of characters]
That's what I see. Odd that the Platform version starts with 3.3.2
rather than 3.3.1.1.
So which version are we talking about?
It s
acters]
That's what I see. Odd that the Platform version starts with 3.3.2
rather than 3.3.1.1.
So which version are we talking about?
It seems that the Eclipse version that I have is identical to the one
that you have. Of course, we likely have a different set of plugins.
On 17 nov 2007, at 11:35, Ken Ishimoto wrote:
Hi,
I am using Leo 10.5.1 with Eclipse 3.3.1.1 last WOLips nightly, no
crash here to.
Thanks for the nice Command-Shift-T , I didn't know that.
Ken
Perhaps the confusion is crated by the version number on the app
versus the version number
Where do you get Eclipse 3.3.2 for Leopard? Link please?
http://download.eclipse.org/eclipse/downloads/ -- 3.3.2 Stream Build
What is the difference between: Eclipse IDE for Java Developers ,
Eclipse IDE for Java EE Developers, and Eclipse Classic?
It's the Eclipse Foundation making something
Hi,
I am using Leo 10.5.1 with Eclipse 3.3.1.1 last WOLips nightly, no
crash here to.
Thanks for the nice Command-Shift-T , I didn't know that.
Ken
On 2007/11/17, at 2:46, Art Isbell wrote:
On Nov 16, 2007, at 3:37 PM, Guido Neitzer wrote:
Can you try "Command-Shift-R" and select somethi
Hi Mike et al.,
Where do you get Eclipse 3.3.2 for Leopard? Link please?
What is the difference between: Eclipse IDE for Java Developers ,
Eclipse IDE for Java EE Developers, and Eclipse Classic?
Which one most closely resembles XCode?
Can you do a mass find/replace in Eclipse like in XCode?
I've tried both Command-Shift-R and Command-Shift-T, entered text
in both, selected a hit using either the mouse or arrow keys, and
pressed Return. Nothing has crashed Eclipse.
However, as complex as Eclipse is, maybe my loaded plugins differs
from yours making my configuration less like
OK -
I just got my new MacBookPro... have spent hours getting all my data,
applications, databases, and of course Eclipse and all of its
permutations.
I installed 3.3.1.1 with Leopard and is seems to be working great.
So where do I get 3.3.2 because I might as well do it now.
What little
On Nov 16, 2007, at 3:37 PM, Guido Neitzer wrote:
Can you try "Command-Shift-R" and select something from there and
hit return?
I've tried both Command-Shift-R and Command-Shift-T, entered text in
both, selected a hit using either the mouse or arrow keys, and pressed
Return. Nothing ha
I can't make Eclipse crash even when I press Enter (after at least
20 attempts). I guess I should continue using 3.3.1.1 under Leopard
until it causes problems.
If 3.3.1.1 doesn't crash for you, you're just plain lucky. As long as
it isn't an issue for you, 3.3.1.1 should be fine -- that's
On 16.11.2007, at 18:11, Art Isbell wrote:
On Nov 16, 2007, at 2:51 PM, Mike Schrag wrote:
If you click OK with the mouse, it will always work. If you type
and press enter to select, there's 50% (or so) chance that you'll
crash Eclipse.
I can't make Eclipse crash even when I press Enter
On Nov 16, 2007, at 2:51 PM, Mike Schrag wrote:
If you click OK with the mouse, it will always work. If you type
and press enter to select, there's 50% (or so) chance that you'll
crash Eclipse.
I can't make Eclipse crash even when I press Enter (after at least 20
attempts). I guess I s
On 16.11.2007, at 17:05, Art Isbell wrote:
I've been running 3.3.1.1 under Leopard and WO 5.4 for a couple of
weeks and have never experienced an Eclipse crash. I must not have
done whatever triggers the crash.
Try Command-Shift-T. Type something, hit return, try it again if it
doesn't
I just opened both of these dialogs, entered text, and clicked the
OK button without crashing Eclipse 3.3.1.1 under OS X 10.5.1. Maybe
I'm just lucky :-) Or maybe some change in 10.5.1 fixed the problem.
If you click OK with the mouse, it will always work. If you type and
press enter to s
On Nov 16, 2007, at 2:27 PM, Mike Schrag wrote:
I've been running 3.3.1.1 under Leopard and WO 5.4 for a couple of
weeks and have never experienced an Eclipse crash. I must not have
done whatever triggers the crash.
Then you're not using the Open Type (cmd-shift-t) dialog or the Open
Reso
I've been running 3.3.1.1 under Leopard and WO 5.4 for a couple of
weeks and have never experienced an Eclipse crash. I must not have
done whatever triggers the crash.
Then you're not using the Open Type (cmd-shift-t) dialog or the Open
Resource (cmd-shift-r) dialog, which really should be
On Nov 16, 2007, at 11:13 AM, Mike Schrag wrote:
The stable build based on 3.3 has not switched over, yet. I think
it will be tonight, but I might want until the end of the weekend.
Eclipse 3.3.2 is actually NOT finalized as I original thought it was
(a misleading comment on a bug in Ecli
I don't know yet ... I was under the impression that 3.3.2 was out,
but it looks like it actually isn't, just a stream maintenance build
of 3.3.2.
On Nov 14, 2007, at 9:08 PM, Gaastra Dennis - WO Lists wrote:
Hi Mike,
So as of Friday, we can start with:
eclipse-java-europa-fall2-macosx-ca
Hi Mike,
So as of Friday, we can start with:
eclipse-java-europa-fall2-macosx-carbon.tar.gz
or
eclipse-jee-europa-fall2-macosx-carbon.tar.gz
With Kind Regards,
Dennis Gaastra, M.B.A.[sfu.ca], B.Sc.[ubc.ca]
Chief Technology Officer,
WEBAPPZ Systems, Inc.
HQ: (+1) 604.921.1333
Fax: (+1) 604
40 matches
Mail list logo
