[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26180:
-------------------------------
Attachment: p2diff.am2.am3.all.ignoreVersions.txt
p2diff.am2.am3.all.txt
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt, p2diff.am2.am3.all.ignoreVersions.txt, p2diff.am2.am3.all.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26299) [Red Hat Central] Update to latest Sonarlint 3.6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26299?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26299 at 8/30/18 9:35 PM:
-------------------------------------------------------------
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 5, 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 3, 107, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 107, 132, 10 issues
So that actually made things worse. So much for "new is better". :(
Seems to be a change in *sonar-php-plugin-2.13.0.3107.jar* vs. *sonar-php-plugin-2.11.0.2485.jar*
was (Author: nickboldt):
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 5, 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 3, 107, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 107, 132, 10 issues
So that actually made things worse. So much for "new is better". :(
> [Red Hat Central] Update to latest Sonarlint 3.6
> ------------------------------------------------
>
> Key: JBIDE-26299
> URL: https://issues.jboss.org/browse/JBIDE-26299
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM3
>
>
> Pull 3.6.0 from https://eclipse-uc.sonarlint.org/
> Check if we have fewer CVEs after update:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26299) [Red Hat Central] Update to latest Sonarlint 3.6
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26299?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26299:
------------------------------------
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 5, 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 3, 107, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 142, 132, 10 issues
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ... 107, 132, 10 issues
So that actually made things worse. So much for "new is better". :(
> [Red Hat Central] Update to latest Sonarlint 3.6
> ------------------------------------------------
>
> Key: JBIDE-26299
> URL: https://issues.jboss.org/browse/JBIDE-26299
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM3
>
>
> Pull 3.6.0 from https://eclipse-uc.sonarlint.org/
> Check if we have fewer CVEs after update:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22138:
-------------------------------------
Description:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
steps:
# EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
# EXEC: import the app into your Eclipse workspace
# EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
# EXEC: create a server adapter and start it
# ASSERT: adapter starts syncing, verify what war is used
Result:
The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
Expected result:
If you start the server adapter the maven profile "openshift" should be activated and the war that's published should be "ROOT.war". If you stop the server adapter the "openshift" maven profile should be deactivated for the "hello" project.
was:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
steps:
# EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
# EXEC: import the app into your Eclipse workspace
# EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
# EXEC: create a server adapter and start it
# ASSERT: adapter starts syncing, verify what war is used
Result:
The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
> Expected result:
> If you start the server adapter the maven profile "openshift" should be activated and the war that's published should be "ROOT.war". If you stop the server adapter the "openshift" maven profile should be deactivated for the "hello" project.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26331) Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26331?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26331:
-------------------------------------
Labels: maven_profile server_adapter war (was: )
> Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26331
> URL: https://issues.jboss.org/browse/JBIDE-26331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
> Labels: maven_profile, server_adapter, war
> Fix For: 4.9.x
>
>
> steps:
> # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
> # EXEC: import the "hello" maven project into your Eclipse
> # EXEC: create a server adapter and start it
> # ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
> # ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
> # ASSERT: Console output for oc rsync shows that a war *"hello.war"* was published
> Result:
> A new war *hello.war* was published but not deployed - no .dodeploy marker was created - , the old war *ROOT.war* was *NOT* removed and is still deployed.
> In the pod log you see the following output for wildfly/eap that confirms this:
> {code}
> [0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy
> {code}
> {code}
> [0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22138:
------------------------------------------
The OpenShift server adapter now activates an "openshift" maven profile that it finds in the project that it publishes to OpenShift. Stopping the server adapter will deactivate the "openshift" maven profile. The implemtation was done in [PR #1785|https://github.com/jbosstools/jbosstools-openshift/pull/1785] and fixes this issue and JBIDE-26175.
The upstream bug in Eclipse WTP was file together with a suggested fix to [Eclipse bugzilla 538367|https://bugs.eclipse.org/bugs/show_bug.cgi?id=538367]. In the meantime We have a workaround in place in our OpenShift tooling.
Issues that remain were filed to the following JIRAs:
* Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project (JBIDE-26330)
* Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one (JBIDE-26331)
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26331) Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26331?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26331:
-------------------------------------
Fix Version/s: 4.9.x
> Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26331
> URL: https://issues.jboss.org/browse/JBIDE-26331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
> Labels: maven_profile, server_adapter, war
> Fix For: 4.9.x
>
>
> steps:
> # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
> # EXEC: import the "hello" maven project into your Eclipse
> # EXEC: create a server adapter and start it
> # ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
> # ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
> # ASSERT: Console output for oc rsync shows that a war *"hello.war"* was published
> Result:
> A new war *hello.war* was published but not deployed - no .dodeploy marker was created - , the old war *ROOT.war* was *NOT* removed and is still deployed.
> In the pod log you see the following output for wildfly/eap that confirms this:
> {code}
> [0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy
> {code}
> {code}
> [0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26331) Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26331?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26331:
-------------------------------------
Description:
steps:
# EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
# EXEC: import the "hello" maven project into your Eclipse
# EXEC: create a server adapter and start it
# ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
# ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
# EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
# ASSERT: Console output for oc rsync shows that a war *"hello.war"* was published
Result:
A new war *hello.war* was published but not deployed - no .dodeploy marker was created - , the old war *ROOT.war* was *NOT* removed and is still deployed.
In the pod log you see the following output for wildfly/eap that confirms this:
{code}
[0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy
{code}
{code}
[0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
{code}
was:
steps:
# EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
# EXEC: import the "hello" maven project into your Eclipse
# EXEC: create a server adapter and start it
# ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
# ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
# EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
# ASSERT: Console output for oc rsync shows that a war "hello.war" was deployed
Result:
A new war "hello.war" was published but not deployed - no .dodeploy marker was created - , the old war "ROOT.war" was *NOT* removed and is still deployed.
In the Pod log you see the following output for wildfly/eap
{code}
[0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy
{code}
{code}
[0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
{code}
> Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26331
> URL: https://issues.jboss.org/browse/JBIDE-26331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
>
> steps:
> # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
> # EXEC: import the "hello" maven project into your Eclipse
> # EXEC: create a server adapter and start it
> # ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
> # ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
> # ASSERT: Console output for oc rsync shows that a war *"hello.war"* was published
> Result:
> A new war *hello.war* was published but not deployed - no .dodeploy marker was created - , the old war *ROOT.war* was *NOT* removed and is still deployed.
> In the pod log you see the following output for wildfly/eap that confirms this:
> {code}
> [0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy
> {code}
> {code}
> [0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26331) Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26331?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26331:
-------------------------------------
Summary: Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one (was: Server adapter: switching maven profile (which determines the war name) won't undeploy the old war)
> Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26331
> URL: https://issues.jboss.org/browse/JBIDE-26331
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
>
> steps:
> # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
> # EXEC: import the "hello" maven project into your Eclipse
> # EXEC: create a server adapter and start it
> # ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
> # ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
> # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
> # ASSERT: Console output for oc rsync shows that a war "hello.war" was deployed
> Result:
> A new war "hello.war" was published but not deployed - no .dodeploy marker was created - , the old war "ROOT.war" was *NOT* removed and is still deployed.
> In the Pod log you see the following output for wildfly/eap
> {code}
> [0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy
> {code}
> {code}
> [0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months