Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Commit

Permalink
Update doc with TFS 2015 instruction.
Browse files Browse the repository at this point in the history
Explicitly call out to skip create service endpoint and enter credentials directly on the task.
  • Loading branch information
yacaovsnc committed Jan 24, 2017
1 parent b9d54fb commit 86a6d9a
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 5 deletions.
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ This extension installs the following components:

## Create a JBoss EAP / WildFly Connection
* Make sure the application server's management http interface is exposed and can be reached over the network.
* Skip this step if you are on Team Foundation Server 2015 and enter the credentials directly on the task.

1. Open the Services page in your Visual Studio Team Services Control Panel
1. In the New Service Endpoint list, choose "JBoss and WildFly"
Expand All @@ -25,7 +26,7 @@ This extension installs the following components:

![WildFly/Mangement task](Tasks/images/managementtask.png)

1. Select the "JBoss and WildFly" service endpoint you created previously.
1. Select the "JBoss and WildFly" service endpoint you created previously, or enter the credentials.
1. Enter commands to be executed, one command per line.

## Deploy applications to JBoss EAP 7 and WildFly 8 and above
Expand All @@ -34,7 +35,7 @@ This extension installs the following components:

![WildFly/Deployment task](Tasks/images/deploymenttask.png)

1. Select the "JBoss and WildFly" service endpoint you created previously.
1. Select the "JBoss and WildFly" service endpoint you created previously, or enter the credentials.
1. Enter the file to be deployed (a wildcard is allowed but it must resolve to exactly one file).
1. Select and enter other optional fields. Hover over the info icon at the end of each field for additional help.

Expand Down
2 changes: 1 addition & 1 deletion Tasks/extension-manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"manifestVersion": 1,
"id": "jboss-wildfly-management-extension",
"name": "JBoss and WildFly",
"version": "0.112.0",
"version": "0.112.1",
"publisher": "ms-vsts",
"description": "Manage and deploy your WAR and EAR files to JBoss EAP 7 and WildFly 8+ instance.",
"public": true,
Expand Down
5 changes: 3 additions & 2 deletions Tasks/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ This extension installs the following components:

## Create a JBoss EAP / WildFly Connection
* Make sure the application server's management http interface is exposed and can be reached over the network.
* Skip this step if you are on Team Foundation Server 2015 and enter the credentials directly on the task.

1. Open the Services page in your Visual Studio Team Services Control Panel
1. In the New Service Endpoint list, choose "JBoss and WildFly"
Expand All @@ -23,7 +24,7 @@ This extension installs the following components:

![WildFly/Mangement task](images/managementtask.png)

1. Select the "JBoss and WildFly" service endpoint you created previously.
1. Select the "JBoss and WildFly" service endpoint you created previously, or enter the credentials.
1. Enter commands to be executed, one command per line.

## Deploy applications to JBoss EAP 7 and WildFly 8 and above
Expand All @@ -32,7 +33,7 @@ This extension installs the following components:

![WildFly/Deployment task](images/deploymenttask.png)

1. Select the "JBoss and WildFly" service endpoint you created previously.
1. Select the "JBoss and WildFly" service endpoint you created previously, or enter the credentials.
1. Enter the file to be deployed (a wildcard is allowed but it must resolve to exactly one file).
1. Select and enter other optional fields. Hover over the info icon at the end of each field for additional help.

Expand Down

0 comments on commit 86a6d9a

Please sign in to comment.