Yes, we are planning on maintain our Hudson
build.
As for releasing the changes I will look into it
…
Stefan
You are either using Dali as a dependency,
or you are a part
of Dali. If you were using Dali as a dependency (as in the
past) then you
would integrate with Dali on the weekly WTP I-Buiild. The
latest WTP
I-Build would be your Dali dependency, and everything would
work just
fine. That however is not what you are trying to do now. As
a
part of Dali you will work with the latest Dali code from head
in your workspace.
After committing changes to your code you will the "release"
this
changes to the WTP PDE build. These changes will be submitted
to the
continuous build, which represents the closest thing to
building against Head
in WTP. More information on releasing changes to a build can
be found
here - http://www.eclipse.org/webtools/faq/CommitterFAQ.php#Build/CVS.
Before releasing changes, you need to understand the weekly
build schedule - http://wiki.eclipse.org/WTP/Build/WTP_Build_Rhythm_Schedule.
Are you planning on maintaining your Hudson build after you
have integrated
with the Dali/WTP build? It seems that you are interested in
doing so,
which is great, but just wanted to confirm before trying to
help with this.
Neil
On 2/17/2011 4:58 AM, Dimov, Stefan wrote:
But
we are trying to integrate the diagram editor with WTP PDE
build. How can do it
if our code is not buildable against the latest in HEAD?
Stefan
I
always tell people that if you are delivering to Indigo, you
should not build against
Indigo. As you have learned, you will always be behind. You
should build
against your prereqs originals. For webtools, each build
produces a
repository, either in archived format, or via HTTP by adding
'repository' to
the end of the download page's URL. EMF, GEF, DTP all do
something similar.
HTH
From:
"Dimov, Stefan" <stefan.dimov@xxxxxxx>
To:
"General Dali EJB ORM developer discussion." <dali-dev@xxxxxxxxxxx>
Date:
02/17/2011 03:54 AM
Subject:
Re: [dali-dev] Failing Diagram editor Hudson build job
Sent by:
dali-dev-bounces@xxxxxxxxxxx
Neil,
You are
correct – currently, the only suitable p2 repository is the
WTP p2 archive
file. The diagram editor builds successfully against it
(I’ve downloaded and
extracted it on my machine). The tests also pass
successfully, so I’m going to
submit the code in CVS. We’ll not have working Hudson build
job until there is
a proper p2 update repository available. I guess that would
be the staging
site, but I don’t know when. Do you have any idea and if it
wouldn’t be so soon
would you be able to boost the process a bit?
Stefan
From: dali-dev-bounces@xxxxxxxxxxx
[mailto:dali-dev-bounces@xxxxxxxxxxx] On Behalf
Of Neil
Hauge
Sent: Wednesday, February 16, 2011 7:13 PM
To: dali-dev@xxxxxxxxxxx
Subject: Re: [dali-dev] Failing Diagram editor Hudson
build job
Stefan,
This repository does not contain the latest Dali code. It
would contain
the Dali Indigo M5 code, which wouldn't contain the common.ui
plugin.
You could try the staging repository[1], but this is probably
still at M5 as
well. I think if you need a p2 repository, the only one that
is published
right now would be p2 archive file that is published with
every WTP build.
I would get the p2 archive that was produces for the 2-15
build that you
reference if that is something that could work for you.
[1]
http://download.eclipse.org/releases/staging
Neil
On 2/16/2011 9:50 AM, Dimov, Stefan wrote:
The
repository site I’m using for maven build is the same:
<repository>
<id>indigo</id>
<url>http://download.eclipse.org/releases/indigo/</url>
<layout>p2</layout>
</repository>
_______________________________________________
dali-dev mailing
list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
