Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] P2 sites for maps

1.  I would assume that you would be building against Indigo only.

2.  The /eclipse/updates/3.7milestones repository is the one we use to submit to the Indigo build.  Just before the release is ready, I'll move the release build to the  /eclipse/updates/3.7 repo. So I'd continue to use  /eclipse/updates/3.7milestones for your builds.


From:        Miles Parker <milesparker@xxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        06/07/2011 03:01 PM
Subject:        [cross-project-issues-dev] P2 sites for maps
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

Two questions regarding update site dependencies.

1. I had assumed that we were to be building against the current Indigo train build dependencies only, but looking at other project's rmaps I'm seeing that folks are still using Helios and other project specific dependencies. So did I assume wrong on requirement for building against the Indigo train only?

2. On the assumption above I've been using {0}/releases/staging?importType=binary and {0}/eclipse/updates/3.7milestones" exclusively for o.e. Should I stick with these for final build or should I be flipping them to something else?


cross-project-issues-dev mailing list

Back to the top