[JBoss JIRA] (TOOLSDOC-311) Review: Devs to review OpenShift Tools chapter for JBDS 7.0
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-311?page=com.atlassian.jira.plug... ]
Max Rydahl Andersen commented on TOOLSDOC-311:
----------------------------------------------
even better - the actual PR to the openshift docbook docs.
> Review: Devs to review OpenShift Tools chapter for JBDS 7.0
> -----------------------------------------------------------
>
> Key: TOOLSDOC-311
> URL: https://issues.jboss.org/browse/TOOLSDOC-311
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
> Attachments: instant-apps.png
>
>
> Please review the content of the OpenShift chapter from a technical viewpoint:
> 1) Are features correctly documented?
> 2) Are there any features that are missing?
> The chapter has been sent to you by email as pdf. Please let me know if you would prefer an alternative format or delivery point for reviewing.
> Screenshots are currently missing and will be added closer to GA.
> Please give feedback as comments in this JIRA.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14000) OpenShift incorrectly listed under JBoss Community in New Server wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14000?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-14000:
-------------------------------------------
Assignee: Andre Dietisheim (was: Rob Stryker)
it is the "vendor" attribute on runtimeType that decides this.
Why that is using hardcode providerName property I don't grok.
But set vendor to a property from plugin.properties and you should be fine.
> OpenShift incorrectly listed under JBoss Community in New Server wizard
> -----------------------------------------------------------------------
>
> Key: JBIDE-14000
> URL: https://issues.jboss.org/browse/JBIDE-14000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
> Attachments: OpenShift_JBossCommunity.png
>
>
> When creating a new server, OpenShift is listed under JBoss Community. Screen capture attached.
> As far as I know, OpenShift is not a JBoss product - it is marketed solely as Red Hat. And OpenShift is not community - it is maintained by Red Hat and they make money from it.
> So OpenShift doesn't fit under JBoss Community or JBoss Enterprise Middleware. I guess it needs a separate entry.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14074) Duplicated toolbar in Forge Console tab
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14074?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-14074:
-----------------------------------
I have seen the same behaviour in the Data Source Explorer view (see screenshot), so not sure if it's anything Forge related or something more general.
> Duplicated toolbar in Forge Console tab
> ---------------------------------------
>
> Key: JBIDE-14074
> URL: https://issues.jboss.org/browse/JBIDE-14074
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta1
>
> Attachments: data source explorer.png, Forge_twomenubars.png, Forge_twomenubars2.png
>
>
> The toolbar in the Forge Console tab is duplicated - there are two of each button. See attached screen capture.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14124) Preference 'Start Forge when Eclipse starts.' should have neutral text
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14124?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-14124.
-------------------------------
Resolution: Done
> Preference 'Start Forge when Eclipse starts.' should have neutral text
> ----------------------------------------------------------------------
>
> Key: JBIDE-14124
> URL: https://issues.jboss.org/browse/JBIDE-14124
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta1
>
>
> Click Window > Preferences > Forge. One of the check boxes reads 'Start Forge when Eclipse starts.' The name of this is JBT centric. For JBDS it should read 'Start Forge when JBDS starts.'
> I realise it is difficult and not particularly desirable to have two different check box names for JBT and JBDS. How about making the name more neutral? For example, 'Start Forge when IDE starts.'
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14118) Should org.jboss.tools.forge.runtime be version 1.2.200 or 1.3.0?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14118?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14118:
---------------------------------------------
Both - at least I don't see much difference in these two for this problem.
example of "contribute" is about providing hibernatetools forge add outofthebox - a requirement since many users (especially in training rooms) does not necessarily have internet access.
> Should org.jboss.tools.forge.runtime be version 1.2.200 or 1.3.0?
> -----------------------------------------------------------------
>
> Key: JBIDE-14118
> URL: https://issues.jboss.org/browse/JBIDE-14118
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge, updatesite
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
>
> In JBT 4.0.1:
> org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar
> In JBT 4.1.0.Alpha2b:
> org.jboss.tools.forge.runtime_1.2.2.Alpha2-v20130419-1639-B54.jar
> So timestamp goes up, but service does not?
> Should this plugin be versioned 1.2.200? Or should it be 1.3.0? Also, if you're moving up this *one* plugin, [~maxandersen] will probably want you to bump the feature/plugin versions for the whole project to the same value, 1.2.200 or 1.3.0.
> The big concern here is that we don't want Eclipse to see org.jboss.tools.forge.runtime_1.2.2.Final-v20130327-0622-B107.jar (from JBT 4.0 / Juno) as a "newer" plugin than org.jboss.tools.forge.runtime_1.2.2.Alpha2-v20130419-1639-B54.jar (from JBT 4.1 / Kepler) because of the way osgi view "Final" as newer than "Alpha".
> If both work equally well in Juno *and* in Kepler, this isn't a showstopper unless one of them prevents installation of something else in JBoss Tools due to platform conflicts.
> You can bump all poms/manifests/feature.xml files in one operation like this:
> {code:title=https://gist.github.com/nickboldt/4548933/raw/ec20825dbe7a3f07a9d388015564d2ced0f79885/upversion.sh}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=x.y.z-SNAPSHOT
> {code}
> See also: http://machydra.brq.redhat.com:8080/job/devstudio.versionwatch-windows/ws...
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14342 at 5/2/13 4:39 AM:
------------------------------------------------------------------
I filed a feature request for the client library (JBIDE-14366) to offer method overloads with timeouts so that a user of the library can use specific timeouts for specific operations
was (Author: adietish):
I filed a feature request for the client library to offer method overloads with timeouts so that a user of the library can use specific timeouts for specific operations
> I dont get credentials reported when I create a jenkins
> -------------------------------------------------------
>
> Key: JBIDE-14342
> URL: https://issues.jboss.org/browse/JBIDE-14342
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
> Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png
>
>
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14366) openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-14366:
----------------------------------------
Summary: openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations
Key: JBIDE-14366
URL: https://issues.jboss.org/browse/JBIDE-14366
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.1.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.x
We need to have means for users to provide specific timeouts for specific operations. Ex. to create an application we'd call
{code}
domain.createApplication(name, cartridge, scale, gear)
{code}
If we want to increase timeouts for this specific operation, we cannot. We have to increase the url connection timeouts via the system properties. We should therefore offer
{code}
domain.createApplication(name, cartridge, scale, gear, TIMEOUT)
{code}
--
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
12 years, 11 months