[ https://issues.jboss.org/browse/JBIDE-10514?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10514 at 12/16/11 12:22 PM: --------------------------------------------------------------------- @Rob: I experienced this today with a local jboss as7.1, too, when I imported a cloned as7 quickstart from github. It did not occour on the examples that were created with the links in Central. Any idea what the reason could be? was (Author: adietish): @Rob: I experienced this today with a local jboss as7.1, too, when imported a cloned as7 quickstart from github. It did not occour on the examples that were created with the links in Central. Any idea what the reason could be? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10514?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10514: ---------------------------------------- Fix Version/s: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10514?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-10514: ------------------------------------- Perhaps a solution here is that on creation of a new app, it changes the context root to "/" ? For imported ones that already exist, keep them the same? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10514?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-10514: -------------------------------- Fix Version/s: 3.3.x There is no clear solution here. Unfortunately the issues are as follows: 1) m2e-wtp does not use the <warName>ROOT</warName> portion of the pom.xml 2) m2e-wtp always overrides the wtp value for context root using its own logic 3) adding a <m2eclipse.wtp.contextRoot>/</m2eclipse.wtp.contextRoot> to the pom.xml upstream would make it work for remote, but not if deployed to a local app-server 4) if we choose to use the run-on-server client to do this, it will need to return different values for local vs remote server 5) There is no guarantee to know how the user intends to deploy it remotely without a setting somewhere 6) This setting should be somewhere public and not too hard to find Current ideas are to add a component property, such as openshift.remote.contextroot, to the virtualcomponent / settings.xml file. However if the user then changes the pom, he will also have to go dig through and change this property. Attempting the same, but for local, is not any better. I can't see a clear solution for this now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10514?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-10514. --------------------------------- Fix Version/s: (was: 3.3.x) Resolution: Done The actual behaviour here seems to be on the server object. This made this much much easier. A setting has been added, the default for openshift source folders is now "/" (ignore the context root), but I have not yet added any setting UI to allow to set this. Adding a setting UI is still waiting for a comprehensive solution to organizing all of our settings in the UI. Otherwise everything is just going to get more and more cluttered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10514?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-10514. --------------------------------- Resolution: Done Currently, no code sets this attribute / property, so the value is null. The current 'getter' returns a 'true' on a null setting, though this can be changed at will with no backwards compat issues. Default behaviour can change if we want. Yes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira