Bugzilla – Full Text Bug Listing
| Summary: | Build artifacts cannot be consumed in p2/maven | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Markus Kuppe <bugs.eclipse.org> | ||||
| Component: | ecf.releng | Assignee: | Markus Kuppe <bugs.eclipse.org> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | harshana05, jeffmcaffer, pwebster, slewis, wayne.beaton | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 313477 | ||||||
| Bug Blocks: | 313481 | ||||||
| Attachments: |
|
||||||
|
Description
Markus Kuppe
http://build.ecf-project.org/repo acts as a composite repository now containing most of the C-HEAD-* build artifacts. Enhancement bug #313477 has been filed with b3 to add support to add/remove repos from the command line. That would allow us to aggregate the composite repo after each build. As a side effect we would be able to also produce maven repositories. http://download.ecf-project.org/maven/ and https://build.ecf-project.org/hudson/job/zB3-aggregator/ have been added to generate maven repos (manually). This currently only generates the repo for ECF 3.4 and needs manual update on 3.5, 3.4.1... get released. Created attachment 182984 [details]
mylyn/context/zip
Super. Are there any limitations that prevent such repos from being on eclipse.org? (In reply to comment #5) > Super. Are there any limitations that prevent such repos from being on > eclipse.org? No, but won't bug #283745 provide a Maven repository at some point anyway? (In reply to comment #6) > (In reply to comment #5) > > Super. Are there any limitations that prevent such repos from being on > > eclipse.org? > > No, but won't bug #283745 provide a Maven repository at some point anyway? It looks to me like we're still some distance away from consensus on that this repository is going to look like. I think it would helpful--at least psychologically--if the Maven repo is hosted on eclipse.org. It would be one necessary step in the right direction as we sort this out. (In reply to comment #7) > It looks to me like we're still some distance away from consensus on that this > repository is going to look like. > > I think it would helpful--at least psychologically--if the Maven repo is hosted > on eclipse.org. It would be one necessary step in the right direction as we > sort this out. I'd rather wait a few weeks for early adopters to comment on the repo before we make it an official eclipse.org repository. Additionally for ECF it makes it harder to integrate our non-EPL code (GPL providers, ...) with the rest of ECF. AFAIK Maven has no notion of a composite repository that spans across several different locations. And thus we would be forced to have two separate Maven repos. One for the fully EPL compliant parts, another second one for the rest. Hosting the Maven repo at OSU makes this distinction unnecessary. FWIW: - A maven repo is now also created for ECF's nightly build - .B3aggr gets transformed/generated from ecf.rmap on-the-fly (with XSL) - releng/org.eclipse.ecf.releng.bm/ecf.b3aggr has been subsequently purged from git (In reply to comment #9) > - A maven repo is now also created for ECF's nightly build http://download.ecf-project.org/maven/snapshots/ this has been dealt with with more recent releng enhancements. |