Commits

Rich Manalang [Atlassian] committed dc085d0

p3->connect

  • Participants
  • Parent commits 45e1ac2

Comments (0)

Files changed (1)

-# Atlassian P3 Development Environment
+# Atlassian Connect Development Environment
 
-This is a set of Vagrant / Puppet provisioning scripts for provisioning a local Atlassian Plugins 3 development environment. To build Plugins 3 Add-ons, you have two choices:
+This is a set of Vagrant / Puppet provisioning scripts for provisioning a local Atlassian Plugins 3 development environment. To build an Atlassian Connect Add-ons, you have two choices:
 
 1. You can build your add-on locally and then register it in an OnDemand instance to test it.
 2. You can build your add-on locally and then register it inside a local version JIRA or Confluence.
 
     http://localhost:2990/jira (admin/admin)
 
-### Registering your P3 Add-on
+### Registering your Atlassian Connect Add-on
 
 Once your JIRA server is up and running, you can register your add-on by posting to installer resource:
 
     curl -v -u admin -X POST -d url=http://machine_hostname/path/to/your/atlassian-plugin.xml http://localhost:2990/jira/rest/remotable-plugins/latest/installer
 
-Notice the URL we're posting to the P3 installer (http://machine_hostname/path/to/your/atlassian-plugin.xml). The `machine_hostname` used here refers to your local machine's hostname. If you're on OSX, this typically will be your `machine_name.local`. You'll need to use the same hostname in your `atlassian-plugin.xml`:
+Notice the URL we're posting to the Atlassian Connect installer (http://machine_hostname/path/to/your/atlassian-plugin.xml). The `machine_hostname` used here refers to your local machine's hostname. If you're on OSX, this typically will be your `machine_name.local`. You'll need to use the same hostname in your `atlassian-plugin.xml`:
 
     <remote-plugin-container key="container" display-url="http://machine_name.local:{port}">