| commit | d8692aed4c4a66fbe87ddb4241694d6efc6f5c3e | [log] [tgz] |
|---|---|---|
| author | Peter Nehrer <pnehrer@eclipticalsoftware.com> | Tue Mar 21 12:59:28 2017 -0400 |
| committer | Peter Nehrer <pnehrer@eclipticalsoftware.com> | Thu Mar 23 23:21:17 2017 -0400 |
| tree | f160dbdfd14ab5ef7011f87f12c539e9409b6302 | |
| parent | 760003fb1e4dc49a29e5777d7a377c7220c096ee [diff] |
Bug 513867 - Properties generation sometimes incorrect - to support empty strings and arrays, generate property value attribute if body content absent, and vice-versa - for empty array members, generate empty property element (no value attribute) By spec, if a property element has a value attribute, then it's a single-value property; otherwise it's a multi-value (array) property where each non-empty line in its body, trimmed, represents an array element. DSEditor considers empty value and content the same as no value/content. The annotation processor, on the other hand, actually removes the value attribute and/or body content node to distinguish between single and multi-value properties. Thus, when writing out the property element XML, we must write the value attribute or body content node if it's defined, even when empty. Change-Id: I4a0eb93240124e1a11cb5816e96af1357df78b92 Signed-off-by: Peter Nehrer <pnehrer@eclipticalsoftware.com>
Thanks for your interest in this project.
The PDE project the Eclipse tooling to develop plug-ins and OSGI bundles.
Website: https://www.eclipse.org/pde/
Contributions to PDE are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [How to Contribute] 1 page on the team wiki.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.