Home » Language IDEs » ServerTools (WTP) » new integration build
| new integration build [message #53538] |
Tue, 16 November 2004 16:42  |
Eclipse User |
|
|
|
Originally posted by: alexsmr.NOJUNK.sympatico.ca
Guys,
When are you plan for next integration build? We plan to integrate with
WTP for the next Pollinate milestone (M3). However last WTP integration
build (I20041015) is not Eclipse 3.1 compliant (right?). And last night
builds have compilation problems.
Alex Smirnoff
Pollinate Project.
|
|
| | |
| Re: new integration build [message #53919 is a reply to message #53898] |
Mon, 22 November 2004 14:56  |
| Eclipse User |
|
|
|
On Mon, 22 Nov 2004 10:43:06 -0500, Alexander Smirnoff <alexsmr@NOJUNK.sympatico.ca> wrote:
> David,
>
> Can you send me a Project Set File of the latest JST/WST dev
> environment? I'm kind of confused what should and what shouldn't
> I have in the project...
>
> Thanks,
> Alex.
>
I'll suggest some alternatives so you can better tell at anytime, without
need of master Project Set File. Those are best used for a particular team,
for a subset of projects. Though if following don't work for you, let me know.
1. Use PDE Target.
Ideally (typically easiest), you can simply create a target to point PDE at, and anything that
was in the integration build you'd "automatically" have access to. Since only features
and plugins are actually in the download, you have to create the main part of the target
youself, out of main Eclipse download, and other pre-req projects which are linked off
of build page. (I know there was an issues with runtime vs. SDK builds ... but haven't checked
lately to see if source is being included in I-builds ... it will be eventually.
2. use "Load Released Projects"
If '1' doesn't work for you, I think the best way to pull what ever is going
into an integration build is to get the releng tool (from the main Eclipse Download
page ... you should get the one that "matches" your development environment version).
Once you have that installed as part of your development environemnt, you can load
the org.eclipse.wtp.releng plugin from the wtp repository (like a normal project).
One of the directories in that wtp.releng project is "maps". The *.map files in there
basically reflect the projects and version of project that is used for integration
build.
Anyway, with the eclipse releng plugin in dev. env., you'll notice a some new context menu items ... one of them, under Team, is "Load Released Projects". If you pick that, with a given
map file selected, it will load the projects from that map file, according to the version in the
build. From there, if you actually wanted to instead see the HEAD version, you can simply
"replace with latest from branch ... HEAD".
[Note: technically, to know exactly what goes into a build, you'd have to trace through the
PDE features that control the build ... but typcially the map files match up pretty close.]
|
|
|
| Re: new integration build [message #54268 is a reply to message #53919] |
Tue, 23 November 2004 10:07 |
| Eclipse User |
|
|
|
Originally posted by: alexsmr.NOJUNK.sympatico.ca
David Williams wrote:
> On Mon, 22 Nov 2004 10:43:06 -0500, Alexander Smirnoff
> <alexsmr@NOJUNK.sympatico.ca> wrote:
>
>> David,
>>
>> Can you send me a Project Set File of the latest JST/WST dev
>> environment? I'm kind of confused what should and what shouldn't
>> I have in the project...
>>
>> Thanks,
>> Alex.
>>
>
> I'll suggest some alternatives so you can better tell at anytime, without
> need of master Project Set File. Those are best used for a particular team,
> for a subset of projects. Though if following don't work for you, let me
> know.
>
> 1. Use PDE Target.
> Ideally (typically easiest), you can simply create a target to point PDE
> at, and anything that
> was in the integration build you'd "automatically" have access to. Since
> only features
> and plugins are actually in the download, you have to create the main
> part of the target
> youself, out of main Eclipse download, and other pre-req projects which
> are linked off
> of build page. (I know there was an issues with runtime vs. SDK builds
> ... but haven't checked
> lately to see if source is being included in I-builds ... it will be
> eventually.
Yes the sources are not there yet and I prefer to have more control and
ability to update from CVS. So I guess this is not good for me.
> 2. use "Load Released Projects"
> If '1' doesn't work for you, I think the best way to pull what ever is
> going
> into an integration build is to get the releng tool (from the main
> Eclipse Download
> page ... you should get the one that "matches" your development
> environment version).
> Once you have that installed as part of your development environemnt,
> you can load
> the org.eclipse.wtp.releng plugin from the wtp repository (like a normal
> project).
> One of the directories in that wtp.releng project is "maps". The *.map
> files in there
> basically reflect the projects and version of project that is used for
> integration
> build.
>
> Anyway, with the eclipse releng plugin in dev. env., you'll notice a
> some new context menu items ... one of them, under Team, is "Load
> Released Projects". If you pick that, with a given
> map file selected, it will load the projects from that map file,
> according to the version in the
> build. From there, if you actually wanted to instead see the HEAD
> version, you can simply
> "replace with latest from branch ... HEAD".
>
> [Note: technically, to know exactly what goes into a build, you'd have
> to trace through the
> PDE features that control the build ... but typcially the map files
> match up pretty close.]
Wow. That exactly what I've needed. I missed somehow the whole story
about Eclipse releng plugin... Now it looks like the best approximation
to the released version is directory.txt map that is published on the
download website (am I correct?)
Thank you very much for the tip.
Alex Smirnoff.
|
|
|
| Re: new integration build [message #54292 is a reply to message #54268] |
Tue, 23 November 2004 10:43 |
| Eclipse User |
|
|
|
On Tue, 23 Nov 2004 10:07:16 -0500, Alexander Smirnoff <alexsmr@NOJUNK.sympatico.ca> wrote:
>
> Wow. That exactly what I've needed. I missed somehow the whole story
> about Eclipse releng plugin... Now it looks like the best approximation
> to the released version is directory.txt map that is published on the
> download website (am I correct?)
>
Yes, that's correct. Technically it is an approximation. Here's how it works, the features
(also listed in the directory.txt file) is what determines *which* projects are included
in the build, and (rest of) the map file determines which *version* is used. Thus, technically,
the map files are a superset, but typically matches pretty well (and eventually will match
exactly).
|
|
|
Goto Forum:
Current Time: Fri May 09 08:25:55 EDT 2025
Powered by FUDForum. Page generated in 0.04699 seconds |
Home