Hi all,
would it be possible to make the transfer to the Maven repository a step in the ECF release process?
In the meantime, can someone update the repository at
http://download.ecf-project.org/
and fill it with ECF 3.5.6?
At least to me it seems, that the latest library versions should be from v20120610-1946 or newer, but currently are v20120319-0616 or older.
Thanks,
Johannes
In Reply to Markus Alexander Kuppe
On 03/15/2012 06:00 PM, Scott Lewis wrote:
> Hi Folks,
>
> On the p2 dev mailing list we've (ECF) recently received a request to
> provide access to a maven repo of recent ECF versions. I had thought
> that maven repos were automatically being created for every nightly
> build, but when I go to:
>
> http://download.ecf-project.org/
>
> I see that the maven repo is pretty old. For Markus K and/or Wim, I
> guess: Is there something explicit about the build that has to be done
> to create a maven repo? If so, what is that (e.g. release build...or
> something else?)
Hi,
we have never had automatically generated Maven repos for nightly
builds. We only have a manual aggregator build [1] based on b3 (and some
XML munging) to create a Maven repo out of an existing p2 repository. It
just hasn't been executed regularly continuously and thus has gone sour.
It's fixed now though (by removing outdated Orbit references).
Markus
[1] https://build.ecf-project.org/jenkins/job/zB3-aggregator
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message
in error, please notify the sender immediately and delete all copies of this message.
