Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/485
After refactoring in #576 (thanks @aledsage) this PR contains _only_ the
REST call. As for the principal suggestions on the REST API, responding both
to @geomacy and @neykov :
Requiring a `MANIFEST.MF` makes the input strongly java-centric; I'd like
to appeal to people who write YAML blueprints with co-bundled scripts and
images. They'd wonder why they can't simply make and upload a ZIP. They could
probably be persuaded to supply a name and optional version on a CLI or UI, and
understand why it is needed (hence supporting those args) but it would not be
idiomatic to anyone but a java programmer to create a `META-INF/` dir with a
`MANIFEST.MF` and its syntax. Meanwhile it is very easy for us to convert the
ZIP to a JAR on the server. Feels like uncontroversial good UX.
OTOH for a java programmer a `MANIFEST.MF` is natural, and they'd want to
drop the name/version args if they are in that file, and I see no reason to
forbid that pattern.
Can this merge once above agreed?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
