> Second, you said "I have uploaded a build to DTP downloads area"... the build is at
> http://download.eclipse.org/datatools/1.12.1.201510141301/ , I was expecting it to be something like
> http://download.eclipse.org/datatools/downloads/1.12.1.201510141301/ (in the datatools/downloads area).
That’s intentional. I am not a fan of how DTP has previously organized its downloads area. It splits the online repository (updates) and offline repository (downloads), which makes it more difficult than necessary to maintain the downloads area. The new approach is to put the release or build version number first, then artifacts within. That makes it easy to nuke a build when it’s no longer needed.
> And, is there any chance that there will be a http://download.eclipse.org/datatools/updates/1.12.1
> (or 2.0 or whatever?) Having a static repository location that points to the latest build in a stream really
> helps projects that prereq one of your streams.
This will definitely be provided. I’d like to defer this for a bit, though, until the version question is settled.
Thanks,
- Konstantin
From: Carl Anderson
Sent: Wednesday, October 14, 2015 12:17 PM
To: DTP development mailing list
Subject: Re: [dtp-dev] Working DTP build at eclipse.org
Konstantin,
First, thanks! WTP is going to try to build with that (and the Platform M2). Second, you said "I have uploaded a build to DTP downloads area"... the build is at http://download.eclipse.org/datatools/1.12.1.201510141301/ , I was expecting it to be something like http://download.eclipse.org/datatools/downloads/1.12.1.201510141301/ (in the datatools/downloads area). Can you modify things so that your next build goes there? And, is there any chance that there will be a http://download.eclipse.org/datatools/updates/1.12.1 (or 2.0 or whatever?) Having a static repository location that points to the latest build in a stream really helps projects that prereq one of your streams.
Once again, thanks for the progress that you have made with this.
FWIW,
- Carl Anderson
WTP Releng project lead
Konstantin Komissarchik ---10/14/2015 02:41:24 PM---I have completed the work to get DTP building again. https://hudson.eclipse.org/datatools/job/master
From: Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx>
To: DTP development mailing list <dtp-dev@xxxxxxxxxxx>
Date: 10/14/2015 02:41 PM
Subject: Re: [dtp-dev] Working DTP build at eclipse.org
Sent by: dtp-dev-bounces@xxxxxxxxxxx
I have completed the work to get DTP building again.
https://hudson.eclipse.org/datatools/job/master/
I have updated the version to 1.12.1, but I don’t think that this is the version that we should use for Neon. More on that in another thread.
I have uploaded a build to DTP downloads area and updated the downloads page. Search for 1.12.1 and you will find the link.
https://www.eclipse.org/datatools/downloads.php
I have updated Neon aggregation to reference this build, which should unblock folks waiting on DTP to act.
Thanks,
- Konstantin
From: Konstantin Komissarchik
Sent: Saturday, October 3, 2015 9:41 AM
To: DTP development mailing list
Subject: [dtp-dev] Working DTP build at eclipse.org
I spent a day yesterday working on getting DTP build going again. I initially started by looking at the existing build system. It’s the old-school tag and map files approach, which is quite complex and it doesn’t appear to be compatible with Windows.
In the interest of quickly getting a DTP build up and running, I chose to leverage Sapphire build system that I wrote and maintain. It is a drop-in-replacement for any PDE Build based system and is very easy to use both on Hudson and on a developer’s machine. This build system is used to build Sapphire and Oracle’s Eclipse tools. It is known to work on Windows, Linux and Mac.
Perhaps the biggest difference from the current build system is that the qualifier is always the time stamp of the build, rather than a Git label. This removes a lot of complexity from the build and also makes it easier for committers to push changes as there is no map files to update.
The DTP build is now up-n-running. I temporarily used Sapphire HIPP instance since I don’t have access to the DTP one.
https://hudson.eclipse.org/sapphire/job/dtp/
I have verified the following:
1. The number of artifacts and repository size matches DTP 1.12 release
2. Can install DTP into Mars.1
3. Can install DTP into Neon M1
To try the build yourself on your dev machine, follow these instructions:
1. Start with a clean folder, which we will call ROOT
2. Clone all DTP Git repos into ROOT, such that each repo has it’s own sub-folder named using the repository name
3. Extract the attached zip file into ROOT
4. Ensure that you have Ant installed and it’s on the path (I tested with Ant 1.9.4)
5. Ensure that you have JDK 8 installed and it’s on the path to run the build
6. Set JDK_5_HOME, JDK_6_HOME, JDK_7_HOME and JDK_8_HOME environment variables. You may be able to cheat and set 6 and 7 to the same path as 8, but the build will definitely need a correct 5 and a correct 8. This can be simplified by moving all DTP plugins to require Java 8 for Neon, since that’s what’s required by the platform anyway.
7. Ensure that you have a network connection as the build will need to download items to build the target platform
8. Run “ant clean-start” from ROOT
Once the build completes, you will have the following artifacts:
1. ROOT/build/repository – the p2 repo
2. ROOT/build/packages – the zipped copy of the p2 repo
3. ROOT/dev-eclipse – an Eclipse install with everything necessary to work on DTP
4. ROOT/dev-target – an Eclipse install with DTP and source bundles for everything
The artifacts in the built repository are conditioned, signed (if built on eclipse.org Hudson) and packed. The repository includes a welcome page and index files.
Sapphire build system includes other facilities that are currently disabled in the DTP build, such as automatic computation and setting of dependency version ranges.
This message is getting long enough... If you want to move forward with this approach and want to make me a committer on DTP, I can have the build running on DTP HIPP very quickly and will continue to maintain DTP build for as long as it uses this build system.
Thanks,
- Konstantin
_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dtp-dev
