[jbosstools-issues] [JBoss JIRA] (JBDS-2701) Runtime detection problems with Portlet helloworld example in Central

[Peter Palaga (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Palaga resolved JBDS-2701.
--------------------------------

    Resolution: Won't Fix


Once again: (fbricon agreed with this solution) I had to put the old JPP 6.0 quickstart descriptor in place of the current JPP 6.1 Beta descriptor because our productization is late with delivering a wolf repo for JPP 6.1 Beta. See https://issues.jboss.org/browse/JBIDE-15009?focusedCommentId=12789338&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12789338

The real fix for all of the JBDS-2695, JBIDE-15009 and your newest JBDS-2701 is that productization delivers the JPP 6.1 maven repo and I'll be able to provide a proper descriptor which solves all these problems.

The productization is late with the maven repo by 9 days now.
                
> Runtime detection problems with Portlet helloworld example in Central
> ---------------------------------------------------------------------
>
>                 Key: JBDS-2701
>                 URL: https://issues.jboss.org/browse/JBDS-2701
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Central, servers
>    Affects Versions: 7.0.0.GA
>         Environment: jbdevstudio-product-universal-7.0.0.GA-v20130717-1700-B362
> RHEL6
>            Reporter: Len DiMaggio
>            Assignee: Peter Palaga
>             Fix For: 7.0.0.GA
>
>         Attachments: Screenshot-2.png, Screenshot-3.png
>
>
> Installing the helloworld portal quickstart raises these runtime detection errors:
> * The quickstart runtime detection looks for JBoss AS, does not recognize EAP 6
> * But - it does not look for/require a portal server

--
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