Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: geomacy <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-485-brooklyn-server@git.apache.org>
In-Reply-To: <git-pr-485-brooklyn-server@git.apache.org>
Subject: [GitHub] brooklyn-server issue #485: `BundleMaker` REST call allowing to add ZIP/JAR ...
Content-Type: text/plain
Message-Id: <20170302094108.1EA49DFDAE@git1-us-west.apache.org>
Date: Thu,  2 Mar 2017 09:41:08 +0000 (UTC)
archived-at: Thu, 02 Mar 2017 09:41:10 -0000

Github user geomacy commented on the issue:

    https://github.com/apache/brooklyn-server/pull/485
  
    @ahgittin I take your point [above](https://github.com/apache/brooklyn-server/pull/485#issuecomment-283280366) about a manifest being java centric.  That's persuaded me to not insist on it (I agree it would be nice to support it if the developer supplies one).
    
    At the same time I think we should insist that they _somehow_ provide an explicit symbolic name and version.  I would have thought that the version should be mandatory?  How would we treat the bundle if it just had a name?  Do we treat it as a version 0.0.0-SNAPSHOT, so to speak? (i.e. lower than anything with an explicitly supplied version?) 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---