Return-Path: 
 <dev-return-13307-apmail-brooklyn-dev-archive=brooklyn.apache.org@brooklyn.apache.org>
X-Original-To: apmail-brooklyn-dev-archive@minotaur.apache.org
Delivered-To: apmail-brooklyn-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8F936182BC
	for <apmail-brooklyn-dev-archive@minotaur.apache.org>;
 Tue, 19 Jan 2016 14:20:04 +0000 (UTC)
Received: (qmail 4921 invoked by uid 500); 19 Jan 2016 14:20:04 -0000
Delivered-To: apmail-brooklyn-dev-archive@brooklyn.apache.org
Received: (qmail 4883 invoked by uid 500); 19 Jan 2016 14:20:04 -0000
Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@brooklyn.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@brooklyn.apache.org>
List-Post: <mailto:dev@brooklyn.apache.org>
List-Id: <dev.brooklyn.apache.org>
Reply-To: dev@brooklyn.apache.org
Delivered-To: mailing list dev@brooklyn.apache.org
Received: (qmail 4866 invoked by uid 99); 19 Jan 2016 14:20:04 -0000
Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 14:20:04 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org)
 with ESMTP id B4C721804FC
	for <dev@brooklyn.apache.org>; Tue, 19 Jan 2016 14:20:03 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 0.447
X-Spam-Level: 
X-Spam-Status: No, score=0.447 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.554,
	URIBL_BLOCKED=0.001] autolearn=disabled
Received: from mx1-eu-west.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new,
 port 10024)
	with ESMTP id xrVZOAsgLPhf for <dev@brooklyn.apache.org>;
	Tue, 19 Jan 2016 14:19:51 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with
 SMTP id 1C75220BC2
	for <dev@brooklyn.incubator.apache.org>;
 Tue, 19 Jan 2016 14:19:50 +0000 (UTC)
Received: (qmail 4784 invoked by uid 99); 19 Jan 2016 14:19:50 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org)
 (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 14:19:50 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at
 git1-us-west.apache.org, from userid 33)
	id 3A2EADFCB5; Tue, 19 Jan 2016 14:19:50 +0000 (UTC)
From: ahgittin <git@git.apache.org>
To: dev@brooklyn.incubator.apache.org
Reply-To: dev@brooklyn.incubator.apache.org
References: <git-pr-1144-incubator-brooklyn@git.apache.org>
In-Reply-To: <git-pr-1144-incubator-brooklyn@git.apache.org>
Subject: [GitHub] incubator-brooklyn pull request: Getting Started with
 Vagrant upda...
Content-Type: text/plain
Message-Id: <20160119141950.3A2EADFCB5@git1-us-west.apache.org>
Date: Tue, 19 Jan 2016 14:19:50 +0000 (UTC)

Github user ahgittin commented on a diff in the pull request:

    https://github.com/apache/incubator-brooklyn/pull/1144#discussion_r50116411
  
    --- Diff: brooklyn-docs/guide/start/blueprints.md ---
    @@ -6,44 +6,83 @@ children:
     - { section: Launching from a Blueprint, title: Blueprint } 
     ---
     
    -<div style="width: 100%; display: block; background-color: #CC9966; margin-bottom: 2px;  padding: 50px 30px 50px 80px;" >
    -  <h3>NOTE</h3>
    -  <div>
    -  The structure of Brooklyn's repositories is changing at present (Jan 2016). Until this is complete 
    -  please obtain the "br" command line tool from <a href="https://github.com/brooklyncentral/brooklyn-cli">Brooklyn Central</a>
    -  </div>
    -</div>
    +Blueprints are descriptors or patterns which describe how Apache Brooklyn should deploy applications. Blueprints are written in [YAML](https://en.wikipedia.org/wiki/YAML){:target="_blank"} and all of the entities available are defined in the __[Brooklyn Catalog](../../learnmore/catalog/)__.
     
     ## Launching from a Blueprint
     
    -We'll start by deploying an application with a simple YAML blueprint containing a Tomcat server.
    +We'll start by deploying an application with a simple YAML blueprint containing an [Apache Tomcat](https://tomcat.apache.org/){:target="_blank"} server.
     
    -Copy the blueprint below into a text file, "myapp.yaml", in your workspace, but *before* you create an application with 
    -it, modify the YAML to specify the location where the application will be deployed.  (Note, to copy the file you can
    -hover your mouse over the right side of the text box below to get a Javascript "copy" button.)
    +Copy the blueprint below into a text file, "myapp.yaml", in your workspace (Note, to copy the file you can
    +hover your mouse over the right side of the text box below to get a Javascript "copy" button).
     
     {% highlight yaml %}
     name: Tomcat
     location:
    -  jclouds:aws-ec2:
    -    identity: ABCDEFGHIJKLMNOPQRST
    -    credential: s3cr3tsq1rr3ls3cr3tsq1rr3ls3cr3tsq1rr3l
     services:
     - serviceType: brooklyn.entity.webapp.tomcat.TomcatServer
    --- End diff --
    
    also this class is no longer valid, it should be `org.apache.brooklyn.entity.webapp.tomcat.TomcatServer`


---
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.
---