Bugzilla – Full Text Bug Listing
| Summary: | Inject upstream update site URLs into BPMN2 Editor's update site | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [SOA] BPMN2Modeler | Reporter: | Nick Boldt <nboldt> | ||||
| Component: | Core | Assignee: | Robert Brodt <bbrodt> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | Keywords: | contributed | ||||
| Version: | unspecified | Flags: | bbrodt:
iplog+
|
||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Fixed - thanks Nick! Patch contributed by nboldt@redhat.com |
Created attachment 205762 [details] two new files and one edited pom.xml Installing BPMN2 Editor is tricky as there are a number of upstream dependencies. You can provide instructions to people or use associate sites xml files, or insert <discovery> URLs into your feature.xml, but a p2 metadata solution is better because the sites are added in an enabled state, requiring that users not then find and enable them. Attached is a zip w/ an ant script you can call from your update site's pom.xml which injects some p2 properties into your content.xml and repacks it.