| Summary: | Build gerritfs plugin as part of the Maven Orion server build | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Bogdan Gheorghe <gheorghe> |
| Component: | Releng | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ryehle, simon_kaegi |
| Version: | 6.0 | ||
| Target Milestone: | 6.0 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Bogdan Gheorghe
I am not seeing any easy way to do this yet. There is no common way for the server build to get to the client build bits, since the paths are different depending on whether you are running a local build or a hudson build. I can see any easy workaround though. The gerritfs plugin can be moved to the client repo. It is standalone plugin anyway. We can then build the jar as is now with the gerritfs pom.xml and then fix the jar with the additions in either the parent or the repository pom.xml Can we refactor the plugin as org.eclipse.orion.gerritfs and move to the client repo? (In reply to Anthony Hunter from comment #1) > Can we refactor the plugin as org.eclipse.orion.gerritfs and move to the > client repo? Since the answer is no, we have to build this in the server repo build. The only way to do this is to take the built client p2 repo, copy the client core and ui jars, extract the files we need out of these jars and then add these files to the gerrit jar. The Hudson build has the property ORION_CLIENT_REPOSITORY where we can locate the the client core and ui jars. The gerritfs.jar is available on the downloads page starting with build I20140506-2205. Final jar needs one small tweak. Dir structure in the jar needs to be: META-INF org static orion plugins requirejs orion, plugins and requirejs folders all need to go under a top level "static" folder. |