[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipselink-dev] adding support for creation of column indices
|
Hi Tom,
Does the Eclipse version you have installed include the Plug-in
Development functionality? Our core projects are PDE projects - for
OSGi development.
I had just installed Eclipse Galileo (JavaEE). I have a Plug-in
Development Perspective, so I suppose yes. Do I need to work from this
perspective? (I've never used it, not sure what it can do).
I tried connecting to Orbit and initially was getting connection
errors, but that was because my proxy was not properly setup in Eclipse.
(Window-Preferences-General-Network Connections). Do you have a proxy
server that could be getting in the way?
No, I've tried from home, no proxy server here. I can successfully
access EclipseLink and GF repositories.
Here are the properties I use to connect (in the Eclipse CVS
Repositories view)
ConnectionType: pserver
User: anonymous
Password: <my email address>
Host: dev.eclipse.org
Repository path: /cvsroot/tools
Use Default Port
[...]
dependencies. Let's see if we can get the projects checked out for
you. What error message are you getting?
A few seconds after pressing Finish on the wizard I get a pop-up with:
Error validation connection: "Could not connect to
:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/tools: Cannot connect to
host: Connection timed out: connect"
I have sever Proxy entries in Eclipse's Network Connections but they are
all disabled, and the Active Provider is set to Direct.
IE is also set to "Direct" and I have no problems browsing the Internet
through it.
Same using cvs command line btw:
D:\>cvs -d :pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/tools login
Logging in to :pserver:anonymous@xxxxxxxxxxxxxxx:2401/cvsroot/tools
CVS password:
cvs [login aborted]: connect to dev.eclipse.org(206.191.52.50):2401
failed: Connection timed out
The core and jpa components of EclipseLink target JDK 5. They are
compiled on JDK 6 with a JDK 5 target. There is no plan to change to
JDK 6 in any of the currently scheduled releases.
One of the reasons I ask is that Symfoware JDBC driver has a different
jar for JDK5 and JDK6 (JDBC 3.0 vs 4.0). I'd better test on both.
Thanks,
Dies
Dies Koper wrote:
Hi Tom,
I still haven't been able to run any tests from Eclipse.
I have done the following:
- Upgraded to Eclipse Galileo
- Replaced javax.xml.bind, etc. with their jar files and removed the
project from the dependency list. It resolves one error but gives the
same error for the next project. I repeated this for about four
projects but no end was in sight. Is it supposed to be so much work?
- Tried downloading things from the Orbit cvs repository. Although the
wiki does not give much information about what I can expect in that
repository, it would not let me connect to it (server down?).
I have 100 failures and 900 errors. I would like to just right-click
on the test method name in Eclipse and run the JUnit test in the
debugger from there, so that I can go into the code to see where it
bombs out.
Could you give me the exact steps to do that?
(I don't mind downloading extra projects if that saves me the manual
trial and error process of replacing projects with jars.
On a side note, is my understanding correct that EclipseLink 2.0 is
targeted to be run on JDK6 (and higher)? Or will JDK5 still be supported?
Thanks,
Dies
Tom Ware wrote:
Hi Dies,
They run successfully for me in Eclipse.
Some comments inline:
Dies Koper wrote:
Hi Tom,
The JPA test suite is completely JUnit based. Here is a getting
started page for running the tests:
http://wiki.eclipse.org/EclipseLink/Development/Testing/JPA
I recommend choosing to run the tests either in Ant or in
Eclipse. There are instructions on the page above indicating how
to do either.
So far I've been running them from Ant (the full set).
Now that I've completed a full run, I'd like to run single tests, so
running them from Eclipse would be great.
Do they work for you in Eclipse?
I get the following errors:
- The working directory for FullRegressionTestSuite is set to
${workspace_loc:eclipselink.jpa.test/run}. I suppose that should
have been ${workspace_loc:eclipselink.jpa.test}/run.
The ${workspace_loc:eclipselink.jpa.test/run} works for me in
Eclipse. (I am running Eclipse Galileo, but prior to Galileo, it was
running on Ganymede). One thing that potentially causes an issue
here is the lack of an actual "run" directory. That directory is
created by our ant build, or you can explicitly create it. Do you
have that directory?
When I run a single test, I make a copy of the
FullRegressionTestSuite Launch file with the Eclipse copy
functionality and them make any required changes. Usually I just need
to change the test class.
- Project javax.xml.bind cannot be found. I haven't been able to
resolve this one yet.
Take a look at the "plugins" section here:
http://wiki.eclipse.org/EclipseLink/Building
Your options are to either get the project from orbit as explained on
the page above, or to remove the project-dependency and, instead use
the jar file that is found in our repository. Look in
<home>\trunk\plugins for that file. Each component also has a
plugins directory if there are other libraries you cannot find.
-Tom
This is on Eclipse Ganymede.
I'll try setting up the JUnit runner myself tomorrow (i.e. not using
the included launch files), see if that works.
Cheers,
Dies