|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I am obviously still trying to figure out this new Jira UI -
Steps to reproduce issue:
1) User builds an app (New CDI Web Project - check Maven facet)
2) Adds some code
3) Uses Run As -> Run on Server to test their application on EAP 6
4) Test the app
5) Make a change to a CDI component (as JSF changes are published automatically)
6) Run As -> Run on Server - change is not seen
7) Full Publish is require by right-click on the project on the Servers Tab
Run As -> Run on Server could detect that a Publish is required and cause it, now the end-user is confused when they do not see their changes. No activity in the server log/console tab.