[JBoss JIRA] Commented: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-1819:
------------------------------------
The problem with the quickstarts containing .project and .settings files (https://issues.jboss.org/browse/SOA-2954) is:
* Only a few of the 100+ quickstarts had these files
* Some of the affected quickstarts only included one of the files
* The quickstarts were not changed (to include client code that could be run in eclipse) from the generic SOA-P quickstarts - I'm guessing that the .project and/or .settings files were included unintentionally.
> Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2
> -----------------------------------------------------------------------
>
> Key: JBDS-1819
> URL: https://issues.jboss.org/browse/JBDS-1819
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: SOA Platform
> Affects Versions: 4.1.0.CR3
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.1.Final
>
> Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png
>
>
> Changed to:
> Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1
> Was:
> This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9343) JBoss7 Management Poller shows up for all server types
by Rob Stryker (JIRA)
JBoss7 Management Poller shows up for all server types
------------------------------------------------------
Key: JBIDE-9343
URL: https://issues.jboss.org/browse/JBIDE-9343
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Rob Stryker
Create a JBoss 6 server, double-click the server to open the server editor, and expand the list of startup pollers. You will see that the JBoss 7 management poller is available. This should not be there.
The remedy involves modifying the extension point to allow a list of server types the poller applies to, and making sure the as7 management poller ONLY applies to as7 (thus far).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-9190) no provider name for org.jboss.tools.forge.feature
by Nick Boldt (JIRA)
no provider name for org.jboss.tools.forge.feature
--------------------------------------------------
Key: JBIDE-9190
URL: https://issues.jboss.org/browse/JBIDE-9190
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 3.3.0.M2
Reporter: Nick Boldt
Fix For: 3.3.0.Beta1
Attachments: Screenshot-Forge-and-WS-JAXRS-missing-provider-names.png
Missing provider name. check your feature.xml and add one (see other feature.xml and feature.properties files to learn how. Provider should be "JBoss by Red Hat".
See also screenshot below:
!Screenshot-Forge-and-WS-JAXRS-missing-provider-names!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months