[JBoss JIRA] (JBIDE-13690) Detect future EAP 6 based server like SOA-P
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-13690:
-------------------------------------------
Summary: Detect future EAP 6 based server like SOA-P
Key: JBIDE-13690
URL: https://issues.jboss.org/browse/JBIDE-13690
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers, runtime-detection
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.1.Final, 4.1.0.Alpha2
To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13687) Project wizard from central: requirements should be recommendations
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13687?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13687:
----------------------------------------
Fix Version/s: (was: 4.0.1.Final)
> Project wizard from central: requirements should be recommendations
> -------------------------------------------------------------------
>
> Key: JBIDE-13687
> URL: https://issues.jboss.org/browse/JBIDE-13687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: no-server.png
>
>
> In the new project wizard in Central, there is the table with required plugins and runtimes. In fact these are recommendations - even if you don't have the required server, the project can be created and if you have a compatible server, you can deploy the project to it.
> So the table's title should be changed to Recommendations.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13628) Only one JBoss Central Configurator is selected for display
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13628?page=com.atlassian.jira.plugi... ]
Paul Richardson commented on JBIDE-13628:
-----------------------------------------
Though I understand the reasoning against adding wizards from plugins, I am still concerned:
* there is an extension point available that can modify the configurator;
* the current code still does not correctly handle the possibility that multiple configurators are available.
> Only one JBoss Central Configurator is selected for display
> -----------------------------------------------------------
>
> Key: JBIDE-13628
> URL: https://issues.jboss.org/browse/JBIDE-13628
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Reporter: Paul Richardson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.1.0.Alpha1
>
>
> I wanted to contribute Teiid Designer's 'new model project' wizard as a link in the 'Create Projects' section of JBoss Central. [link|http://www.phantomjinx.co.uk/stuff/jboss-central.png]
> However, I found that the list of project wizards is hard-coded in the default configurator [1]. Thus, the only way I can contribute this link is by extending the default configurator and using the configurators extension point[2] to load my configurator.
> This works correctly but if another project decides to do the same thing then their configurator 'could' be loaded instead of mine due to the following logic in [3]:
> {code:title=ProjectExamplesActivator.java|borderStyle=solid}
> // ... ~ Line 1163
> IExtension extension = extensions[0];
> IConfigurationElement[] configurationElements = extension.getConfigurationElements();
> for (int j = 0; j < configurationElements.length; j++) {
> IConfigurationElement configurationElement = configurationElements[j];
> if (CONFIGURATOR.equals(configurationElement.getName())) {
> try {
> configurator = (IJBossCentralConfigurator) configurationElement.createExecutableExtension("class");
> } catch (CoreException e) {
> ProjectExamplesActivator.log(e);
> continue;
> }
> break;
> }
> }
> // ...
> {code}
>
> Thought an alternative configurator that aggregates all extension-pointed configurators and displays the content of each accordingly.
> Happy to provide a patch if required.
> [1] org.jboss.tools.project.examples.configurators.DefaultJBossCentralConfigurator
> [2] org.jboss.tools.project.examples.configurators
> [3] org.jboss.tools.project.examples.ProjectExamplesActivator.java
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13631:
-------------------------------------------------
Wei Sun <wsun(a)redhat.com> made a comment on [bug 916268|https://bugzilla.redhat.com/show_bug.cgi?id=916268]
Test this bug on STG
curl -H "Accept: application/json;version=1.0" --user "wsun@redhat.com:changeme" https://stg.openshift.redhat.com/broker/rest/domains/bmengstgw/applicatio... python -mjson.tool
"embedded": {
"jenkins-client-1.4": {
"info": "Job URL: https://jk1-bmengstgw.stg.rhcloud.com/job/ruby18-build/",
"job_url": "https://jk1-bmengstgw.stg.rhcloud.com/job/ruby18-build/"
},
"mongodb-2.2": {
"connection_url": "mongodb://127.6.121.1:27017/",
"database_name": "ruby18",
"info": "Connection URL: mongodb://127.6.121.1:27017/",
"password": "_E9PFuxbtR3g",
"username": "admin"
},
"mysql-5.1": {
"connection_url": "mysql://127.6.121.1:3306/",
"database_name": "ruby18",
"info": "Connection URL: mysql://127.6.121.1:3306/",
"password": "hlJGD2MXSLtJ",
"username": "adminnDvSUmL"
},
"phpmyadmin-3.4": {
"connection_url": "https://ruby18-bmengstgw.stg.rhcloud.com/phpmyadmin/",
"info": "Connection URL: https://ruby18-bmengstgw.stg.rhcloud.com/phpmyadmin/"
},
"rockmongo-1.1": {
"connection_url": "https://ruby18-bmengstgw.stg.rhcloud.com/rockmongo/",
"info": "Connection URL: https://ruby18-bmengstgw.stg.rhcloud.com/rockmongo/"
}
},
> URL for embedded cartridges is empty
> ------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
--
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
13 years, 1 month