[
https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-5636.
--------------------------------
Fix Version/s: (was: 3.1.1)
Resolution: Partially Completed
See JBIDE-5690 for the remaining (UI) portion. There is now a command for full publish.
It is ctrl+shift+M.
Currently the hotkey will only take the first module it finds, and from that, it will take
the first server it finds that this item is already deployed to.
So if you have 5 servers, but the module is deployed on *none* of them, this action will
do nothing. If however, the module is already deployed to server1, this action will full
publish the module to server1.
If it is already deployed to several servers, it will full-publish it to the first server
that is returned in the list.
A UI must be added to allow selection of which server you'd like to send it to.
Should FULL PUBLISH menu item automatically build project first?
-----------------------------------------------------------------
Key: JBIDE-5636
URL:
https://jira.jboss.org/jira/browse/JBIDE-5636
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: JBDS 3.0 CR1
Reporter: Aaron Pestel
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.1.0.GA
Attachments: LabWebService.zip
1.) Create an ESB project
2.) Add a Java Action to the "src" directory
3.) Add a Generic Action to the esb.xml and point it at the Java class just created
4.) Add project to SOA-P 5 server
5.) Notice ClassNotFound exception in server console
If you look in the server deploy directory, their is no .class file for the .java file
created in step #2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira