| Summary: | Configure Orion Hudson build to use minification | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Szymon Brandys <Szymon.Brandys> |
| Component: | Releng | Assignee: | Szymon Brandys <Szymon.Brandys> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne, mamacdon, matthias.sohn, thanh.ha |
| Version: | 3.0 | ||
| Target Milestone: | 3.0 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 399023 | ||
|
Description
Szymon Brandys
Gabriel suggested to script getting required stuff like r.js, js.jar etc. in the Hudson/Jenkins job. We should publish the r.js package (which include closure I believe) as a maven artifact. Then our pom.xml can just specify a dependency on that and maven will take care of fetching and installing it. That makes our build much cleaner and more reproducible, instead of a bunch of wget's in the hudson script Thanh or Matthias, do you know the process of publishing a maven artifact, and is repo.eclipse.org the right place for this? Basically there is a software package that our build process needs (r.js minifier) and we want to package that so anyone can make consistently reproducible builds of Orion. (In reply to comment #2) > We should publish the r.js package (which include closure I believe) as a > maven artifact. Then our pom.xml can just specify a dependency on that and > maven will take care of fetching and installing it. That makes our build > much cleaner and more reproducible, instead of a bunch of wget's in the > hudson script I think we have to publish closure and rhino (if not already published) too. In the meantime I am ok with having a bunch of wget's to test minified builds at orionhub or orion.eclipse.org. When new maven artifacts are published, the Hudson build can be updated. I added rhino and closure compiler as maven dependencies. Unfortunately there is no such for r.js. So till we have it published as maven artifact somewhere, it will be in our client repo. In which format would you like to package the libraries ? We could add a Maven module to create that and e.g. deploy it to repo.eclipse.org. Or should this rather be handled in Orbit since it's 3rd party ? (In reply to comment #5) We have the discussion in bug 410717 about handling r.js dependency. |