[JBoss JIRA] (JBTIS-385) Browse button in ESB project creation wizard is too narrow
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-385?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky edited comment on JBTIS-385 at 2/2/15 6:41 AM:
-----------------------------------------------------------------
Hey [~bfitzpat], you were right, the problem is in Eclipse since I can also see this problem in Static Web Project creation wizard.
Note that this issue occurs only on linux (tested with Fedora 19-21, Ubuntu 14, RHEL 6/7).
was (Author: apodhrad):
Hey [~bfitzpat], you were right, the problem is in Eclipse since I can also see this problem in Static Web Project creation wizard.
Note that this only on linux (tested with Fedora 19-21, Ubuntu 14, RHEL 6/7).
> Browse button in ESB project creation wizard is too narrow
> ----------------------------------------------------------
>
> Key: JBTIS-385
> URL: https://issues.jboss.org/browse/JBTIS-385
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: ESB
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.2.GA + JBDS-IS 8.0.0.CR1 (contains ESB Tools 1.5.520.Final-v20141209-1859-B53)
> Reporter: Andrej Podhradsky
> Assignee: Brian Fitzpatrick
> Attachments: esb_wizard.png
>
>
> Browse button in ESB project creation wizard is too narrow, see the attachment. Note that the button works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBTIS-385) Browse button in ESB project creation wizard is too narrow
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-385?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-385:
-----------------------------------------
Hey [~bfitzpat], you were right, the problem is in Eclipse since I can also see this problem in Static Web Project creation wizard.
Note that this only on linux (tested with Fedora 19-21, Ubuntu 14, RHEL 6/7).
> Browse button in ESB project creation wizard is too narrow
> ----------------------------------------------------------
>
> Key: JBTIS-385
> URL: https://issues.jboss.org/browse/JBTIS-385
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: ESB
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.2.GA + JBDS-IS 8.0.0.CR1 (contains ESB Tools 1.5.520.Final-v20141209-1859-B53)
> Reporter: Andrej Podhradsky
> Assignee: Brian Fitzpatrick
> Attachments: esb_wizard.png
>
>
> Browse button in ESB project creation wizard is too narrow, see the attachment. Note that the button works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19096:
------------------------------------------
We still need the basic infrastructure for this (basic connection wizard in common, extensions in v2 and v3 ui). In a first step we should have username/pw for v2 and the suggested, raw pasting approach for v3.
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19132) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19132?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19132:
------------------------------------------
What's the difference of this and JBDIE-19122? To me it looks like this was already done in JBIDE-19122?
> For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [OpenShift]
> ---------------------------------------------------------------------
>
> Key: JBIDE-19132
> URL: https://issues.jboss.org/browse/JBIDE-19132
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.2.3.Beta1
>
>
> For JBIDE 4.2.3.Beta1 [OpenShift]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3.
> Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.3.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version:
> {code}
> mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19110) Add Mockito to Target platform 4.50.0
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19110?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-19110 at 2/2/15 5:05 AM:
------------------------------------------------------------------
JBIDE-18053 (powermock) would be a nice add-on but I grok the imcompatibilities make this impossible for now.
IMHO Mockito as-is from Locus is what we should be thriving for right now. I don't see any need for specific customisations right now and I guess that we should restrain from doing such. We could restart the discussions if it turns out we cannot get along without those.
was (Author: adietish):
JBIDE-18053 (powermock) would be a nice add-on but I grok the imcompatibilities make this impossible for now.
IMHO that Mockito as-is from Locus is what we should be thriving for right now. I dont see any need for specific customizations right now and I guess that we should restrain from doing such. We could restart the discussions if it turns out we cannot get along without those.
> Add Mockito to Target platform 4.50.0
> -------------------------------------
>
> Key: JBIDE-19110
> URL: https://issues.jboss.org/browse/JBIDE-19110
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Matej Gagyi
> Priority: Optional
> Fix For: 4.3.0.Final
>
>
> *Reason:* Needed to simplify testing of jbosstools-openshift
> *Project page/sources:* https://github.com/mockito/mockito
> *Version:* 1.9.5
> *License and owner:* MIT
> *Original p2 repo:* http://download.eclipse.org/tools/orbit/downloads/drops/R20140525021250/r...
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/orbit/S20141129...
> *Include Sources:* Yes
> *Affected projects:*
> *Include in JBDS:* No
> *Type of dependency:* testing
> *List of bundles added/removed:*
> {code}
> diff --git a/jbosstools/multiple/jbosstools-multiple.target b/jbosstools/multiple/jbosstools-multiple.ta
> index c17fb92..51f6076 100644
> --- a/jbosstools/multiple/jbosstools-multiple.target
> +++ b/jbosstools/multiple/jbosstools-multiple.target
> @@ -10,8 +10,6 @@
> <!-- JBIDE-12815 JBoss Tools Locus bundles: not quite ready to be included -->
> <!-- <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSourc
> <repository location="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/
> - <!-- JBIDE-12971 Mockito
> - <unit id="org.jboss.tools.locus.mockito" version="1.9.5.Final_patched_TEIIDDES-1681-v20130507-202
> <!-- JBIDE-12972 Fest Assert
> <unit id="org.jboss.tools.locus.easytesting.fest-assert" version="1.4.0.Final-v20130507-2028-B7"/
> <!-- </location> -->
> @@ -86,6 +84,10 @@
> <unit id="org.apache.jasper.glassfish" version="2.2.2.v201205150955"/>
> <!-- <unit id="ch.qos.logback.slf4j" version="1.0.7.v20121108-1250"/> -->
> <unit id="org.slf4j.api" version="1.7.2.v20121108-1250"/>
> +
> + <!-- Testing -->
> + <unit id="org.mockito" version="1.9.5.v201311280930"/>
> + <unit id="org.objenesis" version="1.0.0.v201105211943"/>
> </location>
>
> <!-- TODO: make sure these versions match up across JBT/JBDS/Central target platforms (JBIDE-17429)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19110) Add Mockito to Target platform 4.50.0
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19110?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19110:
------------------------------------------
JBIDE-18053 (powermock) would be a nice add-on but I grok the imcompatibilities make this impossible for now.
IMHO that Mockito as-is from Locus is what we should be thriving for right now. I dont see any need for specific customizations right now and I guess that we should restrain from doing such. We could restart the discussions if it turns out we cannot get along without those.
> Add Mockito to Target platform 4.50.0
> -------------------------------------
>
> Key: JBIDE-19110
> URL: https://issues.jboss.org/browse/JBIDE-19110
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Matej Gagyi
> Priority: Optional
> Fix For: 4.3.0.Final
>
>
> *Reason:* Needed to simplify testing of jbosstools-openshift
> *Project page/sources:* https://github.com/mockito/mockito
> *Version:* 1.9.5
> *License and owner:* MIT
> *Original p2 repo:* http://download.eclipse.org/tools/orbit/downloads/drops/R20140525021250/r...
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/orbit/S20141129...
> *Include Sources:* Yes
> *Affected projects:*
> *Include in JBDS:* No
> *Type of dependency:* testing
> *List of bundles added/removed:*
> {code}
> diff --git a/jbosstools/multiple/jbosstools-multiple.target b/jbosstools/multiple/jbosstools-multiple.ta
> index c17fb92..51f6076 100644
> --- a/jbosstools/multiple/jbosstools-multiple.target
> +++ b/jbosstools/multiple/jbosstools-multiple.target
> @@ -10,8 +10,6 @@
> <!-- JBIDE-12815 JBoss Tools Locus bundles: not quite ready to be included -->
> <!-- <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSourc
> <repository location="http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/
> - <!-- JBIDE-12971 Mockito
> - <unit id="org.jboss.tools.locus.mockito" version="1.9.5.Final_patched_TEIIDDES-1681-v20130507-202
> <!-- JBIDE-12972 Fest Assert
> <unit id="org.jboss.tools.locus.easytesting.fest-assert" version="1.4.0.Final-v20130507-2028-B7"/
> <!-- </location> -->
> @@ -86,6 +84,10 @@
> <unit id="org.apache.jasper.glassfish" version="2.2.2.v201205150955"/>
> <!-- <unit id="ch.qos.logback.slf4j" version="1.0.7.v20121108-1250"/> -->
> <unit id="org.slf4j.api" version="1.7.2.v20121108-1250"/>
> +
> + <!-- Testing -->
> + <unit id="org.mockito" version="1.9.5.v201311280930"/>
> + <unit id="org.objenesis" version="1.0.0.v201105211943"/>
> </location>
>
> <!-- TODO: make sure these versions match up across JBT/JBDS/Central target platforms (JBIDE-17429)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------
"but I wouldn't allow that to hold up completion of this feature." - i'm not sure what "this feature" is if its not to handle different types of logins ?
if OSv3 still just support username/password then I agree we are fine and can move forward on that just fine, but dont see what is missing ?
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months