[
https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-5636:
-------------------------------
Attachment: JBIDE-5636.patch
While technically I agree with Max, I could see the point of view from a user who works
with autobuild off and just likes to "Full Publish" after making some changes.
In these cases, I could see wanting an incremental build on changed projects done before
publishing to the server to save a few keys etc.
I've made a patch for this issue here, but unfortunately this cannot be fixed due to
an upstream bug causing a race-condition and overwriting of the module publish state.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=310608
Basically, the build kicks off some resource change events, and the resource change events
end up setting the module publish state to incremental, EVEN if it was already set to
FULL. Which totally is annoying.
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: Optional
Fix For: 3.2.next
Attachments: JBIDE-5636.patch, 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