[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-13905 at 4/5/13 9:50 AM: --------------------------------------------------------------- {quote} The existing hardcodings are equally broken. {quote} I know that isn't the best option. We can use a better solution for JBoss servers when it is found. {quote} EAP 6.1 has a different module layout structure so don't assume that will work if you are hardcoding this. {quote} {quote} [~mstruk] says that in JPP 6.1 (which will be based on EAP 6.1), portlet-api.jar module should be located at modules/system/add-ons/gatein/javax/portlet/api/main/ {quote} I have included this directory when searching portlet-api.jar. was (Author: snjeza): {quote} The existing hardcodings are equally broken. {quote} I know that isn't the best option. We can use a better solution for JBoss servers when it is found. {quote} EAP 6.1 has a different module layout structure so don't assume that will work if you are hardcoding this. {quote} {quote} Marko Strukelj says that in JPP 6.1 (which will be based on EAP 6.1), portlet-api.jar module should be located at modules/system/add-ons/gatein/javax/portlet/api/main/ {quote} I have included this directory when searching portlet-api.jar. -- 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