The build server can pull the dependency from where-ever it lives.
You can just manually scp it to the build server if that's the best
way to make it happen. That dependency cannot then be redistributed
by the build server (e.g. as part of the Hudson output).
HTH,
Wayne
On 02/26/2014 04:21 PM, Wes Johnson
wrote:
Wayne,
Yes I think this makes sense and should work for us. When you
say 'but must not be reachable to the general population from
there' - can you clarify that for me? In order for it to be
pulled in to be built against, doesn't it have to be available
somewhere? I understand that it can't be hosted at any Eclipse
related server or in the main Kura Git repo itself.
Thanks,
Wes
On 2/26/14, 1:04 PM, Wayne Beaton
wrote:
Hi Wes.
Please confirm that you understand that workswith dependencies
cannot be distributed by the project; they cannot be published
on download.eclipse.org, nor can they be stored in the project's
Git repositories.
Users of the project software that exploits this dependency are
expected to download the dependency separately.
FWIW, the dependency can be pulled onto the build server as part
of the project build process (e.g. so you can compile against
it), but must not be reachable to the general population from
there.
Does the dependency make sense in this context?
Wayne
On 02/26/2014 03:30 PM, Wes Johnson
wrote:
Hi,
The Kura project would like to request the following
'workswith' dependency for:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=7851
Please vote/comment in this thread.
Thanks,
Wes Johnson
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
|
