[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Galder Zamarreno updated JBIDE-3825: ------------------------------------ Summary: Full Publish not doing full build archive (was: Full Publish not doing build archive fully) Fix Version/s: 3.0.0.GA -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3825: ------------------------------------ Full Publish asks the module to publish itself. Currently the archives module mimics the information in the project archives cache. If you do not have automatic building enabled, then the project archives model is blank or out of date, which means the module is also similarly out of date. Try as a workaround doing a full build, then a full publish and get back to me. (I realize that's annoying but it'd be a workaround until we can see what's going on). -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3825: -------------------------------------------- Use Project Build and then deploy. that is 2 clicks which is natural cause of you disabling automatic build... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3825: ------------------------------------ It's not really a "bug"... its the lack of a clearly defined spec of behavior. (but still yields less than great behavior) Full publish just took the archives model and publsihed it. This used to work fine since incremental building of the jar / model was always enabled (even if the user didn't have build automatically enabled) Now incremental building of the jar / model depends on whether workspace incremental building is enabled Therefore, "full publish" just reads the (un-updated) model and publishes it... ie... publishes the outdated crap. So yes, full publish should check the build prefernece and if it's turned off, launch an archive build (model update) before the publish. I'll look into fixing this. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-3825. -------------------------------- Resolution: Done 1) Full publish should now also initiate a full build *on that archive*. It will not initiate a full build on that project or any other one. 2) incremental building (when user does ctrl+b) has been fixed to incrementally build the archive. This was a regression. This fix means that you may no longer *need* to do a full publish and can use the incremental publish after you ctrl+b. This is obviously quicker vs a full publish. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3825: ----------------------------------------- Just updated to latest nightly. This is working like a charm now!!! Thanks Rob :) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3825?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-3825. -------------------------------- Fix Version/s: 3.1.0 (was: 3.0.0.GA) Resolution: Done Committed the fix with a test case to verify how it should work. Case 1: automatic build turned off, automatic publish off - If you change a source file, only that file changes. - bin doesn't change. - archive output doesn't change. - deploy folder doesn't change - Then you do ctrl+b - bin changes - If the builder is enabled, the archive changes - The deploy folder does not change - Then in either the archives view you publish to server (or in servers view, do full publish) - The deploy folder finally changes Case 2: automatic build turned off, automatic publish is on (right-click on the archive in the archives view, select edit publish properties, set a server to autodeploy on and have it publish after every build) - If you change a source file, nothing changes - Then you do ctrl+b, and: - bin changes - archives output is changed - archive is deployed Case 3: automatic build is on, automatic publish is on: - If you change a source file: - bin changes - archives output is changed - archive is deployed Case 4: automatic build is on, automatic publish is off - If you change a source file: - bin changes - archives output is changed - Then if you right-click in archives view and do publish (or in servers view -> full publish): - archive is deployed. -- 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