Bugzilla – Full Text Bug Listing
| Summary: | Provide bundles in Maven consumable format | ||
|---|---|---|---|
| Product: | [RT] Gemini.Web | Reporter: | Alex Blewitt <alex.blewitt> |
| Component: | unknown | Assignee: | Project Inbox <gemini.web-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | eclipse, fotis, glyn.normington |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 357763 | ||
| Bug Blocks: | |||
|
Description
Alex Blewitt
Hmmm. I can see the web core bundle (using S3Fox) under /zodiac.springsource.com/maven/bundles/release/org/eclipse/gemini/web/org.eclipse.gemini.web.core/1.1.0.RELEASE/ Perhaps you simply need to replace zygote.springsource.org with zodiac.springsource.com? All I see if I navigate to: http://zodiac.springsource.com/maven/bundles/release/org/eclipse/gemini/web/org.eclipse.gemini.web.core/1.1.0.RELEASE/ is a downloaded, zero byte file. bigmac[tmp] curl -D - http://zodiac.springsource.com/maven/bundles/release/org/eclipse/gemini/web/org.eclipse.gemini.web.core/1.1.0.RELEASE/ HTTP/1.1 200 OK x-amz-id-2: tLMc8oxfZkLTLON5/0JCN2a1V/kfgK9lTscKMkLVBAlumbH8LfTO4VFDqkAwQ5/C x-amz-request-id: 2AE9B0F40638EB21 Date: Tue, 09 Nov 2010 18:22:41 GMT Last-Modified: Tue, 02 Nov 2010 16:00:52 GMT ETag: "d41d8cd98f00b204e9800998ecf8427e" Accept-Ranges: bytes Content-Type: application/octet-stream Content-Length: 0 Server: AmazonS3 If I go to: http://zodiac.springsource.com/maven/ I get the error message "NoSuchKey": <?xml version="1.0" encoding="UTF-8"?> <Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>maven/</Key><RequestId>1B9FB15D2D739674</RequestId><HostId>Wst1fz82B+LWm2uw/pqJL7vdgddtA3X9+8cQmJwKhk+QYaF+IeOfIdpfltJdMFHG</HostId></Error> (I meant zodiac first time, the zygote was a mis-memory step ;-) I think those errors are because that repository is not browseable. Have you tried specifying it in a Maven build and hit errors? No, but then again, there's no spec of what to put in a maven dependency artifact so it's a bit difficult to get to that step :) We don't actually publicise the SpringSource maven repos for Virgo and Gemini Web but they can be addressed using the following repository URLs: http://zodiac.springsource.com/maven/bundles/release http://zodiac.springsource.com/maven/libraries/release Please note that these repositories are not browseable. We don't want to publicise these repositories because we'll need to move off Amazon S3 before long so non-SpringSource committers will be able to publish builds, do releases, etc. without needing the SpringSource S3 keys. Note that Virgo and Gemini Web publish their artifacts to Ivy repositories in Amazon S3 *and* on build.eclipse.org. We may publish to Maven repositories on build.eclipse.org (or elsewhere in the Eclipse infrastructure) in the fulness of time as we move away from S3. I'm tempted to close this enhancement, but perhaps it would be better to change the summary to something like"Document how to consume Gemini Web bundles from a Maven repo" and leave it on the books as a record of the requirement. Chris: please would you take a look at this when you have a few minutes. I think Gemini Web should be available in the Maven repo at http://zodiac.springsource.com/maven/bundles/release. (I'm not sure where "zygote" came from, but let's assume that's a typo.) The problem is not, not having the repositories browsable, it is the fact that we have to guess the maven coordinates for the artifacts! I have to magically guess the coordinates of each bundle Maven artifacts will now be pubished for Gemini.Web for all future milestones and releases. I have also published them retrospectivly for the 2.0.1 release. You can fine them here. http://build.eclipse.org/rt/virgo/maven/bundles/release/ |