| Summary: | [build] Create plugins for hudson integration | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Markus Knittig <markus> |
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | greensopinion, mik.kersten, shawn.minto, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | 0.7 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Knittig
As part of this I would also like to create plug-ins for the build framework and a feature. All plug-ins would initially be in the sandbox I am in favor of the following naming scheme: org.eclipse.mylyn.builds.core org.eclipse.mylyn.builds.ui To me singular sounds too much like release engineering or build tool (like b3 or maven). For hudson I would like to create these plug-ins following Markus' suggestion: org.eclipse.mylyn.hudson-feature org.eclipse.mylyn.hudson.core org.eclipse.mylyn.hudson.tests org.eclipse.mylyn.hudson.ui The feature id would be org.eclipse.mylyn.hudson. Thoughts? +1 +1 sounds good to me. I have created the following plug-ins in org.eclipse.mylyn/sandbox: org.eclipse.mylyn.builds.core org.eclipse.mylyn.builds.tests org.eclipse.mylyn.builds.ui org.eclipse.mylyn.hudson-feature org.eclipse.mylyn.hudson.core org.eclipse.mylyn.hudson.tests org.eclipse.mylyn.hudson.ui Markus, please go ahead and create bugs for implementing the client for the Hudson web service etc. Once we have some code in the plug-ins I'll add them to the build. |