the WTP milestone build download did it. I did not wanted to work on past versions, sorry for the confusion.
I have only one compile error now, it is in org.eclipse.jpt.jaxb.eclipselink.ui project, class ELJaxbPersistentAttributeItemLabelProvider: The type org.eclipse.jpt.common.ui.internal.jface.AbstractItemLabelProvider cannot be resolved. It is indirectly referenced from required .class files.
According to CVS, AbstractItemLabelProvider was deleted 10.2.2012 9:48 with comment "rework JpaProjectManager".
All 4372 tests that do not depend on that pass on green. This project is bigger than I through. I think I have to spend some time learning whats in first.
2. Graphiti (and EasyMock, which is required for the JPA Diagram
Editor tests) is to be found in a P2 repository which is not
simply unzipped to the target workspace. Again, read the
instructions. They are very explicit. :-)
Best of luck.
Brian
On 2/15/2012 9:00 AM, Mária Jurčovičová wrote:
Hi,
I found EclipseLink SDK only at marketplace. It is not available
on the update site. However, the target platform (Eclipse SDK)
does not have Marketplace menu option. So I can install it only to
the host platform, but not to the target.
Then I tried to download JDT SDK, so I can at least look around
that API. I could not find it neither on the marketplace nor on
the update site.
Am I missing something fundamental? I did some eclipse plugins few
years ago (they used JDT and EMF) and do not remember it to be
that hard. If I recall right, everything used to be available in
the update site.
thank you for taking time to answer, that wiki is what I was
looking for.
I downloaded all packages except Eclipse SDK from build 3.1.1.
Eclipse SDK was not linked, so I took it from 3.3.0. I hope it
is not a problem.
I'm using Eclipse for RCP, Helios release (host platform).
Most projects compile, thirteen have problem:
org.eclipse.jpt.common.ui
org.eclipse.jpt.common.ui.tests
org.eclipse.jpt.dbws.eclipselink.ui
org.eclipse.jpt.jaxb.eclipselink.ui
org.eclipse.jpt.jaxb.ui
org.eclipse.jpt.jpa.core
org.eclipse.jpt.jpa.db.ui
org.eclipse.jpt.jpa.eclipselink.core
org.eclipse.jpt.jpa.eclipselink.ui
org.eclipse.jpt.jpa.ui
org.eclipse.jpt.jpadiagrameditor.ui
org.eclipse.jpt.jpadiagrameditor.ui.tests
org.eclipse.wst.common.modulecore.ui
The most common problem is missing class in package
org.eclipse.persistence . It should be part of eclipselink (I
think), but I do not know where to get it.
I tried:
1.) randomly search through cvs repository,
2.) download eclipselink OSGI bundle zip from http://www.eclipse.org/eclipselink/downloads/index.php
and copy it to the target platform. It did not help.
3.) update my eclipse to install 'EclipseLink Target
Components ' into my eclipse, the update was impossible:
An error occurred while collecting items to be installed
session context was:(profile=""
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect,
operand=, action="">
No repository found containing:
osgi.bundle,commonj.sdo,2.1.1.v200905221342
No repository found containing:
osgi.bundle,javax.activation,1.1.0.v201005080500
...
Some projects require graphity, but my default target platform
does not have that. According to dev page, Graphity should be
in different target platform then the rest. I guess that I
have to switch between them depending on what I'm doing. Is
that right?
Thanks for your comments and interest in Dali. I
will respond to your questions in-line.
Neil
On 2/12/2012 4:11 AM, Mária Jurčovičová wrote:
Hi,
I recently started to use Dali sub-project and
found it neat and useful. Thanks for the good
work.
I would like to see the source code of JPA
related part and maybe contribute something.
Finding out how to start was more difficult than
I expected. Hopefully, someone can answer my
questions.
It sounds like we have some more work to do to ease
the getting started process. Luckily there are
many here who can help you get started. This is
jumping ahead, but there are many on the dali-dev
list who would be able to help. There isn't a lot
of traffic on that list, but it is well monitored.
Theoretical questions:
* Is there an interest for outside
contributions?
Absolutely. It can be tough to get started with
Dali contributions giving the underlying complexity
of the technology itself, but we have had many
successful contributions over the years.
* Do you have some
documents I should read before starting?
* Is this the right
mailing list? I found also dali-dev mailing
list, but it has only weekly status reports in
it. Plus, Dali web page has a link on this one.
dali-dev would be the best mailing list to use. It
will have the specific Dali community you are
looking for. It looks like when the web page was
refactored we lost our specific mailing list link.
I'll look into that.
Practical questions:
* Is there a document that describes what should
I download and how to build that?
There is one set of unneeded projects that are
currently only serving as a shell for maintenance
builds. In the "jpa" component, you will only need
plugins that begin with org.eclipse.jpt.jpa. All of
the others are unnecessary for head development. As
to whether you need all the remaining plugins
probably depends on what you are interested in
doing. Generally speaking, committers on the
project have all of the "plugins" plugins and
"tests" plugins in their workspace. A separate Dali
workspace is probably a good idea. : )
* The above repo depends
on missing bundles, where do I get them? Do I
really need them all?
All of these external dependencies will be a part of
your target platform when developing Dali. When you
build a target platform all of these bundles will be
included, so there is nothing specific you will need
to do to get them. And yes, Dali has many external
dependencies, most of which are Eclipse and some of
which that are not. See http://wiki.eclipse.org/Dali_Developer_Documentation
for information on how to build your target
platform.
