Sorry... copied the wrong section
--
It is the responsibility of the EMO to ensure that for each
Submission which is accepted
for redistribution as Distributed
Content that:
a) sufficient controls are in place to ensure that for each such
Submission the
Content is placed in the Repository by a Committer;
b) sufficient license grants are obtained as to allow the
redistribution of such Content
as described below in Section III; and
c) the due diligence and record keeping described in Section IV be
performe
--
Wayne
On 02/08/2012 12:27 PM, Wayne Beaton wrote:
This is covered by the Eclipse IP Policy [1]:
--
It is the responsibility of the EMO to ensure that for each
Submission which is to be
made available as Hosted Content that:
a) sufficient controls are in place to ensure that for each such
Submission which is
Code Content that such Code Content is placed in the Hosted
Repository by a
Committer;
b) sufficient license grants are obtained as to allow the hosting
of such Content as
described below in Section III;
c) the limited due diligence and record keeping described in
Section IV (D) for
Hosted Content be performed; and
d) such Hosted Content will only be made available through a
Hosted Repository.
--
HTH,
Wayne
[1] http://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
On 02/08/2012 12:14 PM, Igor Fedorenko wrote:
Can
you point me at specific section of eclipse development process
or
any other documentation that specifically requires resolution of
all
project dependencies from eclipse.org sources?
--
Regards,
Igor
On 12-02-08 11:59 AM, Wayne Beaton wrote:
Eclipse project builds must resolve
third-party dependencies through
eclipse.org sources. Sorry, but obtaining dependencies for
distributable
Eclipse content from Maven central is a no-no.
maven.eclipse.org is still a work-in-progress. If improvements
are
needed, please open bugs against Dash/Maven.
I'm hopeful that our new release engineer will be able to
spend some
cycles helping the Dash committers make maven.eclipse.org do
what we
need it to do.
Wayne
On 02/08/2012 08:59 AM, Herbert.Neureiter@xxxxxxxxxxx
wrote:
Hi All,
I am a committer on project Stardust and we are currently
working on
the setup of the build process for our sources. Our build is
heavily
based on Ivy and Maven, hence we need to consume our
dependencies via
maven.
For the largest part of our dependencies we already have CQs
in
“approved” state and especially we have got approval to
reuse quite a
bit of stuff from Orbit.
Looking at the documents
http://wiki.eclipse.org/Common_Build_Infrastructure#Maven
and
http://wiki.eclipse.org/Maven
we were hoping to find most of what we
need in the “orbit” repository on
http://maven.eclipse.org/nexus/index.html#view-repositories
.
Furthermore, we were hoping that we could consume approved
dependencies available from Maven central in the “central”
repository
of http://maven.eclipse.org/nexus/index.html#view-repositories
.
Is this how the repositories are intended to be used? It
seems that
currently the orbit repository is empty and the “central”
repository
does not provide most of what we need. What would be the
process to
get approved Orbit and “central” dependencies made available
via the
nexus repository?
As a side-note: It appears that we can get some of our
requested
dependencies only approved as Subsets by removing
problematic content.
? If modifications to the original dependency are mandated
for legal
reasons, we will need a dedicated repository to hold the
modified
artifacts. I assume in these cases a good approach might be
to
contribute them to orbit where possible and then consume
them via the
Nexus repository?
Thanks for any help on how to proceed.
Regards
Herbert
-----------------------------------------------
Description: Ions_FINAL_380w <http://www.sungard.com/ten>
Dr. Herbert Neureiter•Vice President Product Management
Infinity
Process Platform •Infinity•Global Technology
•SunGard•Solmsstr. 18,
60486 Frankfurt am Main, Germany•Tel +49 69 70768 566•Mobile
+49 176
1111 0180•herbert.neureiter@xxxxxxxxxxx
<mailto:herbert.neureiter@xxxxxxxxxxx>•www.sungard.com
<http://www.sungard.com>
P*Think before you print**
*CONFIDENTIALITY: This e-mail (including any attachments)
may contain
confidential, proprietary and privileged information, and
unauthorized
disclosure or use is prohibited. If you receive this e-mail
in error,
please notify the sender and delete this e-mail from your
system.
SunGard Systeme GmbH * Registered: Frankfurt am Main,
Handelsregister
Frankfurt HRB 56839 * Geschäftsführer: Harold Finders,
Christian U.
Haas, Thorsten Heissel, Richard J. Obetz, Victoria E. Silbey
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
EclipseCon 2012 <http://www.eclipsecon.org/2012>AGILEALM
2012
<http://www.eclipsecon.org/2012>
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
 
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
  |
