April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19550: ------------------------------------ Issue Type: Bug (was: Feature Request) > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Assignee: George Gastaldi > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-19550: --------------------------------------- Assignee: George Gastaldi > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Assignee: George Gastaldi > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19550: ------------------------------------ Fix Version/s: 4.3.0.Alpha2 > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19550?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19550: ------------------------------------ Affects Version/s: 4.2.3.Final > Fully export the Proxy interface package from forge > --------------------------------------------------- > > Key: JBIDE-19550 > URL: https://issues.jboss.org/browse/JBIDE-19550 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Jess Sightler > Fix For: 4.3.0.Alpha2 > > > This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19550) Fully export the Proxy interface package from forge

by Jess Sightler (JIRA)

Jess Sightler created JBIDE-19550: ------------------------------------- Summary: Fully export the Proxy interface package from forge Key: JBIDE-19550 URL: https://issues.jboss.org/browse/JBIDE-19550 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Jess Sightler This is needed for https://issues.jboss.org/browse/WINDUP-547 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- Now i'm back I can give full stacktrace: java.lang.RuntimeException: Current Eclipse instance doesn't support software installation. at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:101) at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.runInUIThread(JBossCentralEditor.java:574) All looks like something that can just be gracefully logged to error log instead of having a full modal dialog popup to all developers using PDE. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3394: ------------------------------------ a) I do not know about examples (not even sure what examples we are referring to ) but we are not dropping the support for building/running engines older than 3.5.0. We are basically synching the list of downloadable engines with Cordova CLI. Also Cordova CLI did not have engine pinning supported until a month ago and we handle our own pinning (see b for details) so I am not sure what would be updated. b) If the project is referring to an earlier than 3.5.0 engine and you have the engine available locally nothing will happen. We support running those engines. If the engine is not present locally, we will prompt that the selected engine is not present and ask users to select one. In this case user either needs to download manually and install or select a 3.5.0 or later platform. > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3394: ------------------------------------------- moved from jbide to jbds to get it ack'ed. The two only concerns I have is: a) do we have any examples that uses pre-3.5.0 versions that we need to get updated ? b) what happens if importing old/existing projects referring to these "overall" versions, will we gracefully convert them to use individual versions or how will that work ? > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3394: -------------------------------------- Fix Version/s: 9.0.0.Alpha2 > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3394: -------------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3394 (was: JBIDE-19547) Workflow: CDW v1 (was: GIT Pull Request workflow ) Affects Version/s: (was: 4.2.3.Final) Component/s: aerogear-hybrid (was: aerogear-hybrid) Docs QE Status: NEW > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19548: ------------------------------------------ Ok, I can reproduce this using binaries from the update site. The OpenShift v3 authentication form is not found in the binaries, there must be some buggy build configurations. > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: 3.0.0.Alpha2-v20150401-1037-B749 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19009: --------------------------------------- removed 'from source' option > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19010) As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19010?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19010: ---------------------------------- Description: https://trello.com/c/HyTyFlHw This is the usecase where we want to deploy an image that most likely does not include a buildconfig, i.e. a database image. > As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19010 > URL: https://issues.jboss.org/browse/JBIDE-19010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > https://trello.com/c/HyTyFlHw > This is the usecase where we want to deploy an image that most likely does not include a buildconfig, i.e. a database image. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19009: ------------------------------------- Assignee: Jeff Cantrill > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- Michael, this is a regression no matter how you twist it. Why should it make things different if we don't show a dialog when central can't use p2 metadata ? > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- Request to have PDE enabling the Software installations by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=463774 > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- p2 is not supported in Dev Mode unless you tick the "Support Software Installation..." checkbox in PDE Launcher. Just tick this checkbox. And if you don't like to have to tick a checkbox, open a bug to PDE asking to turn it on by default. It's not a regression, it's just that the feature of checking for earlyaccess has requires availability of p2 earlier than it used to, which is a valid requirement for real usage scenario. What you're asking is just "please disable this feature in dev-mode when p2 is not enalbed". I don't think it's a good thing as it makes tests behave differently from real delivery, then it strongly reduces the ability to spot issues. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov commented on JBDS-3263: ---------------------------------------------- Attached PRs are all PRs which should be applied to resolve this issue. The only one problem is that I don't know how to build installer, so I cannot be 100% sure that PR for jbdevstudio-product is fine. [~dgolovin], please verify this PRs and give me a lesson of building installer. > Remove JSF Visual/Source and Preview Tabs > ----------------------------------------- > > Key: JBDS-3263 > URL: https://issues.jboss.org/browse/JBDS-3263 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 9.0.0.Beta2 > > > Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs. > http://www.screencast.com/t/wettTf6s6cU > http://www.screencast.com/t/zur1sCXmZ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- I hope you are just kidding. Currently Im forced to disable central manually or live with slow startup and a modal dialog every time I start eclipse in Dev mode. This did not happen in previous versions of central, Thus this is a regression. Please fix that or explain why we cannot just fix it with a simple if statement to check if p2 is actually available in this install. Thank you. . > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- Please provide steps to reproduce for *regular* user. The fact that p2 not enabled for product causes issues is far from being something we want to spend time on. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19548: ------------------------------------- Environment: 3.0.0.Alpha2-v20150401-1037-B749 > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: 3.0.0.Alpha2-v20150401-1037-B749 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19548: ------------------------------------------ [~deshuai] ok so you installed v2 and v3. Let me try with binaries then. > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Ma Deshuai commented on JBIDE-19548: ------------------------------------ [~adietish]When I install the jbt use the latest url, I have selected all the component and installed. > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19548: ------------------------------------------ [~deshuai] did you install v3 only? > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Ma Deshuai updated JBIDE-19548: ------------------------------- Attachment: openshift-v3.png The openshift version is: 3.0.0.Alpha2-v20150401-1037-B749 eclipse version: Mars (4.5.0) system version: win8 > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19548: ------------------------------------- Summary: Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication (was: CoCan't connect to openshift v3 , no place to enter username and password in authentication) > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19548: ------------------------------------- Labels: connection_wizard (was: ) > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) CoCan't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19548: ------------------------------------- Summary: CoCan't connect to openshift v3 , no place to enter username and password in authentication (was: Can't connect to openshift v3 , no place to enter username and password in authentication) > CoCan't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Attachments: v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19549) Connection wizard: v3 connection should store tokens and passwords to the secure storage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19549?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19549: ------------------------------------- Description: Currently v3 connections store the authentication tokens in plaintext into some configuration file. We should store them to the secure storage. Passwords are not stored at all, we should make sure that if a user is editing his v3 connection he does not have to retype his password and have it provided from secure storage (was: Currently v3 connections store the authentication tokens in plaintext into some configuration file. We should store them to the secure storage.) > Connection wizard: v3 connection should store tokens and passwords to the secure storage > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19549 > URL: https://issues.jboss.org/browse/JBIDE-19549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > > Currently v3 connections store the authentication tokens in plaintext into some configuration file. We should store them to the secure storage. Passwords are not stored at all, we should make sure that if a user is editing his v3 connection he does not have to retype his password and have it provided from secure storage -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19549) Connection wizard: v3 connection should store tokens and passwords to the secure storage

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19549: ---------------------------------------- Summary: Connection wizard: v3 connection should store tokens and passwords to the secure storage Key: JBIDE-19549 URL: https://issues.jboss.org/browse/JBIDE-19549 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Andre Dietisheim Currently v3 connections store the authentication tokens in plaintext into some configuration file. We should store them to the secure storage. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19548: ------------------------------------------ What build did you try? Did you only install the v3 plugins? When I try the steps above locally I get the authentication form: !v3-auth-form.png! > Can't connect to openshift v3 , no place to enter username and password in authentication > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Attachments: v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19548: ------------------------------------- Attachment: v3-auth-form.png > Can't connect to openshift v3 , no place to enter username and password in authentication > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Attachments: v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19548: ---------------------------------------- Assignee: Andre Dietisheim > Can't connect to openshift v3 , no place to enter username and password in authentication > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Attachments: v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3386) add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3386?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3386: -------------------------------------- I don't think so. Final bits were staged, approved and pushed without this being fixed. However, target-platforms contain the feature patch. and the catalog is on server-side only. It can be fixed after the fact. I'll work on submitting the PR ASAP, and rebuild a catalog for QE to test it. > add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3386 > URL: https://issues.jboss.org/browse/JBDS-3386 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 8.1.0.GA > > > When we release JBT 4.2.3 and JBDS 8.1.0, we need to remember to add 1 new feature, org.eclipse.wst.jsdt.feature.patch, into both the JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19521) Connection wizard: should show authentication form as soon as server type is selected

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19521?page=com.atlassian.jira.plugi... ] Ma Deshuai commented on JBIDE-19521: ------------------------------------ Could you help handle the bug about v3 connection wizard? > Connection wizard: should show authentication form as soon as server type is selected > ------------------------------------------------------------------------------------- > > Key: JBIDE-19521 > URL: https://issues.jboss.org/browse/JBIDE-19521 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > # ASSERT: make sure you have only v3 plugins installed (only v3 OpenShift has no default server so that the wizard comes up with an empty server url) > # EXEC: launch connection wizard (in Explorer, hit "New Connection") > # ASSERT: wizard comes up with "OpenShift v3" preselected in Server Type > # ASSERT: wizard comes up with empty Server url > Result: > No authentication form is show, the pane is empty > Expected result: > We should have the authentication form for OpenShift v3 and be able to provide credentials. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Can't connect to openshift v3 , no place to enter username and password in authentication

by Ma Deshuai (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Ma Deshuai updated JBIDE-19548: ------------------------------- Attachment: v3-error.png > Can't connect to openshift v3 , no place to enter username and password in authentication > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Ma Deshuai > Attachments: v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Can't connect to openshift v3 , no place to enter username and password in authentication

by Ma Deshuai (JIRA)

Ma Deshuai created JBIDE-19548: ---------------------------------- Summary: Can't connect to openshift v3 , no place to enter username and password in authentication Key: JBIDE-19548 URL: https://issues.jboss.org/browse/JBIDE-19548 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Ma Deshuai 1. Open connection wizard 2. Select the server type to OpenShift 3 3. Input the server url 4. Click the finish button to connect the v3 server Result: 2. In the authentication, there is no place to input the username and password. 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19522) Snapshot wizard: Snapshot restore app from different type archive does not pop up with failure info .

by Yanping Zhang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19522?page=com.atlassian.jira.plugi... ] Yanping Zhang commented on JBIDE-19522: --------------------------------------- Try "rhc snapshot save" and "rhc snapshot restore" in client with different type archive , it would prompt info "Error in trying to restore snapshot.". And restart app, access url successfully with origin deployment. > Snapshot wizard: Snapshot restore app from different type archive does not pop up with failure info . > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-19522 > URL: https://issues.jboss.org/browse/JBIDE-19522 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.CR1 > Environment: JBoss Developer Studio 8.1.0 Beta1 > Reporter: Yanping Zhang > Labels: snapshot_wizard > Fix For: 4.3.x > > > [~yanpzhan] if you get the info in the console that the snapshot could be restored (the server is reporting in the console, not the tooling), so I would think that this is a bug in the server? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3200: --------------------------------- Fix Version/s: (was: 8.1.0.GA) Seems not to happen for 8.1.0. Moving to JBDS 9. > Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning > -------------------------------------------------------------------------------------------- > > Key: JBDS-3200 > URL: https://issues.jboss.org/browse/JBDS-3200 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 8.0.0.GA > Environment: Mac OS X 10.10, JDK 1.8.0 > Reporter: Manuel Blechschmidt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 9.0.0.Alpha2 > > Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png > > > Hello, > I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here: > https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014... > Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store. > {panel} > "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer. > Your security preferences allow installation of only app from the Mac App Store and identified developers. > {panel} > Right click on the file and then selecting open gives me the opportunity to ignore this warning. > Nevertheless it might happen that users don't know this solution. > Hope that helps > Manuel -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3329) Update support matrix for JBDS 8.1 with latest Linux distros

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3329?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3329. -------------------------------- Resolution: Done As far as I can see the matrix has been updated. Closing (I can't just resolve it). [~mmalina] please reopen if I missed something. > Update support matrix for JBDS 8.1 with latest Linux distros > ------------------------------------------------------------ > > Key: JBDS-3329 > URL: https://issues.jboss.org/browse/JBDS-3329 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 8.1.0.GA > > > We should add support for Fedora 21. > Also, we should add Ubuntu 14.04 LTS. > The support matrix doc is here: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3329) Update support matrix for JBDS 8.1 with latest Linux distros

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3329?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3329: ------------------------------------ Assignee: Alexey Kazakov > Update support matrix for JBDS 8.1 with latest Linux distros > ------------------------------------------------------------ > > Key: JBDS-3329 > URL: https://issues.jboss.org/browse/JBDS-3329 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Reporter: Martin Malina > Assignee: Alexey Kazakov > Fix For: 8.1.0.GA > > > We should add support for Fedora 21. > Also, we should add Ubuntu 14.04 LTS. > The support matrix doc is here: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3329) Update support matrix for JBDS 8.1 with latest Linux distros

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3329?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3329: ------------------------------------ Assignee: Martin Malina (was: Alexey Kazakov) > Update support matrix for JBDS 8.1 with latest Linux distros > ------------------------------------------------------------ > > Key: JBDS-3329 > URL: https://issues.jboss.org/browse/JBDS-3329 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 8.1.0.GA > > > We should add support for Fedora 21. > Also, we should add Ubuntu 14.04 LTS. > The support matrix doc is here: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2705) update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2705?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-2705: --------------------------------- Fix Version/s: 8.x 9.0.0.GA (was: 8.1.0.GA) > update "JBoss Developer Studio X in 5 Minutes" to use JBDS 8 - http://vimeo.com/60064715 > ---------------------------------------------------------------------------------------- > > Key: JBDS-2705 > URL: https://issues.jboss.org/browse/JBDS-2705 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 8.x, 9.0.0.GA > > > Need to update "JBoss Developer Studio 6 in 5 Minutes" [0] to feature JBDS 98 > Purpose is to be able to link to a "quick overview" video of JBDS 8 from its Eclipse Marketplace page [1]. > For now, I've linked this video [2] as follows: > {quote} > For a quick overview, see JBoss Developer Studio 7: jQuery Mobile [2]. More videos here: http://docs.jboss.org/tools/movies/ > {quote} > [0] http://vimeo.com/60064715 > [1] https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-ke... > [2] http://vimeo.com/67480300 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3376) Wrong version info in installer and JBDS splash/about screen

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3376?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3376. -------------------------------- Resolution: Done I can't resolve the issue. So I'm closing as done. [~rawagner] please reopen if you still see some problems with wrong version on the splash. > Wrong version info in installer and JBDS splash/about screen > ------------------------------------------------------------ > > Key: JBDS-3376 > URL: https://issues.jboss.org/browse/JBDS-3376 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, ui/branding > Affects Versions: 8.1.0.CR1 > Environment: Installer file jboss-devstudio-8.1.0.CR1-v20150314-0010-B443-installer-standalone > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Priority: Blocker > Fix For: 8.1.0.GA > > Attachments: 810cr1-redux-installer1.png, 810cr1-redux-installer2.png, 810cr1-redux-installer3.png, 810cr1-redux-plugins.png, 810cr1-redux-plugins2.png, 810cr1-redux.png, versions_1.png, versions_2.png, versions_3.png, version_mismatch.png > > > Installer, splash screen and Help-> About says that version is 8.1.0.Beta1 and Build id: Beta1-v20150314-0010-B443 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3324) Test the new installer for JBDS 8.1.0

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3324?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3324: --------------------------------- Fix Version/s: 9.0.0.GA (was: 8.1.0.GA) The new installer is planned for JBDS 9. Not for 8.1.0. So, moving to JBDS 9.0.0. > Test the new installer for JBDS 8.1.0 > ------------------------------------- > > Key: JBDS-3324 > URL: https://issues.jboss.org/browse/JBDS-3324 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 9.0.0.GA > > > The 8.1.0 release will include an updated installer for JBDS - for EAP and standalone. The installers must be tested and released along with the update sites. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3311) Target Platform Requirements for JBDS 8.1.0.GA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3311?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3311. ---------------------------------- Resolution: Done > Target Platform Requirements for JBDS 8.1.0.GA > ---------------------------------------------- > > Key: JBDS-3311 > URL: https://issues.jboss.org/browse/JBDS-3311 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform > Affects Versions: 8.0.0.GA > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.1.0.GA > > > For JBDS 8.1.0.GA, track changes since JBDS-3310 (8.0.2.GA release). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3386) add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3386?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3386: ------------------------------------ Assignee: Mickael Istria (was: Nick Boldt) [~mickael_istria] has og.eclipse.wst.jsdt.feature.patch been added to JBT 4.2 and JBDS 9 marketplace connectors? > add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3386 > URL: https://issues.jboss.org/browse/JBDS-3386 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 8.1.0.GA > > > When we release JBT 4.2.3 and JBDS 8.1.0, we need to remember to add 1 new feature, org.eclipse.wst.jsdt.feature.patch, into both the JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19503) Explorer, Connection wizard: Connection without stored password is not connected after providing password

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19503?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19503: ------------------------------------------ merged and pushed to upstream/master > Explorer, Connection wizard: Connection without stored password is not connected after providing password > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19503 > URL: https://issues.jboss.org/browse/JBIDE-19503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, explorer > Fix For: 4.3.0.Alpha2 > > Attachments: connection-loading.png, connection-not-connected.png, password-not-stored.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19503) Explorer, Connection wizard: Connection without stored password is not connected after providing password

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19503?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19503: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Explorer, Connection wizard: Connection without stored password is not connected after providing password > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19503 > URL: https://issues.jboss.org/browse/JBIDE-19503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, explorer > Fix For: 4.3.0.Alpha2 > > Attachments: connection-loading.png, connection-not-connected.png, password-not-stored.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19503) Explorer, Connection wizard: Connection without stored password is not connected after providing password

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19503?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19503: ---------------------------------------- Assignee: Andre Dietisheim > Explorer, Connection wizard: Connection without stored password is not connected after providing password > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19503 > URL: https://issues.jboss.org/browse/JBIDE-19503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, explorer > Fix For: 4.3.0.Alpha2 > > Attachments: connection-loading.png, connection-not-connected.png, password-not-stored.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-403) Update JBTIS TP for B*MS production release

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-403?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-403. ------------------------------ Fix Version/s: 4.2.2.Final-TP Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/commit/92463ef... > Update JBTIS TP for B*MS production release > ------------------------------------------- > > Key: JBTIS-403 > URL: https://issues.jboss.org/browse/JBTIS-403 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.2.1.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.2.Final-TP > > > *Reason:* Move B*MS TP dependencies from EA to release. Update TP dependencies to latest .Final/CR1 core components. Update to Eclipse Luna Sr2 > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.2.CR1b/ > Synopsis: > 1. Moved B*MS-specific and SOA-5x-specific target dependencies from early access to the release/final JBTIS TP. > 2. Updated to 4.42.0.Final-SNAPSHOT JBT core base target dependencies. > 3. Updated to jbosstools-4.2.3.CR1-updatesite-core and coretests > 4. Updated to Eclipse Luna SR2 RC4 201502190900-SR2-RC4 > 5. Updated orbit dependencies S20150202203538 > *Project page/sources:* > *Version:* 4.2.2.CR1b > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror.* > *Include Sources:* Yes > *Affected projects:* JBDSIS/ JBTIS > *Include in JBDS:* Yes - JBDSIS > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > target-platform.target.repo > < org.eclipse.birt.data.oda.mongodb [4.4.0.v201405191524] > < org.jboss.tools.community.central [1.3.0.Final-v20141016-1914-B105] > < org.eclipse.birt.report.data.oda.jdbc [4.4.0.v201405191524] > < org.jboss.tools.community.central.feature.feature.jar [1.3.0.Final-v20141016-1914-B105] > < org.jboss.tools.community.central.feature.feature.group [1.3.0.Final-v20141016-1914-B105] > < org.jboss.tools.community.project.examples.feature.feature.jar [2.0.0.Final-v20141016-1914-B105] > < org.jboss.tools.community.project.examples [2.0.0.Final-v20141016-1914-B105] > < org.eclipse.birt.report.data.oda.jdbc.ui [4.4.0.v201405191524] > < org.eclipse.birt.core [4.4.0.v201405191524] > < org.jboss.tools.birt.oda [1.7.0.Final-v20141016-1529-B14] > < org.jboss.tools.birt.feature.feature.jar [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.birt.report.data.oda.hive [4.4.0.v201405191524] > < org.jboss.tools.birt.feature.feature.group [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.birt.data.oda.mongodb.ui [4.4.0.v201405191524] > < org.jboss.tools.as.test.core [3.0.0.Final-v20141016-1911-B95] > < org.jboss.tools.common.test [3.6.0.Final-v20141016-2021-B66] > < org.jboss.tools.community.project.examples.feature.feature.group [2.0.0.Final-v20141016-1914-B105] > < org.eclipse.birt.report.data.bidi.utils.ui [4.4.0.v201405191524] > < org.jboss.tools.birt.oda.ui [1.7.0.Final-v20141016-1529-B14] > < org.jboss.tools.jmx.core.test [1.6.0.Final-v20141016-1911-B95] > < org.jboss.tools.common.base.test [3.6.0.Final-v20141016-2021-B66] > < org.jboss.tools.birt.core [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.birt.report.data.oda.hive.ui [4.4.0.v201405191524] > < org.eclipse.birt.report.data.bidi.utils [4.4.0.v201405191524] > < org.jboss.tools.tests [3.5.0.Final-v20141016-2021-B66] > > org.junit [4.11.0.v201303080030] > > org.eclipse.emf.compare.feature.jar [3.0.2.201501201328] > > org.eclipse.graphiti.feature.feature.jar [0.11.2.v20150204-0954] > > org.eclipse.bpel.apache.ode.runtime [1.0.4.v201412041949] > > org.eclipse.emf.transaction.feature.jar [1.8.0.201405281451] > > org.eclipse.bpel.apache.ode.deploy.ui [1.0.4.v201412041949] > > org.eclipse.emf.query.ocl.feature.jar [1.8.0.201405281426] > > org.eclipse.bpel.common.model [1.0.4.v201412041949] > > org.eclipse.emf.transaction [1.8.0.201405281451] > > org.w3c.css.sac [1.3.1.v200903091627] > > org.eclipse.ocl.ecore [3.3.100.v20140610-0641] > > org.eclipse.uml2.common.feature.group [2.0.1.v20150202-0947] > > org.eclipse.bpel.apache.ode.runtime.feature.source.feature.group [1.0.4.v201412041949] > > org.apache.batik.dom [1.6.0.v201011041432] > > org.eclipse.bpel.model.source [1.0.4.v201412041949] > > org.eclipse.bpel.common.wsdl [1.0.4.v201412041949] > > org.eclipse.bpel.common.feature.feature.group [1.0.4.v201412041949] > > javax.xml [1.3.4.v201005080400] > > org.eclipse.bpel.ui.source [1.0.4.v201412041949] > > org.eclipse.uml2.feature.group [5.0.2.v20150202-0947] > > org.eclipse.graphiti.ui [0.11.2.v20150204-0954] > > org.eclipse.emf.transaction.feature.group [1.8.0.201405281451] > > org.eclipse.equinox.simpleconfigurator.manipulator [2.0.0.v20131217-1203] > > org.eclipse.bpel.ui [1.0.4.v201412041949] > > org.eclipse.graphiti.pattern [0.11.2.v20150204-0954] > > org.eclipse.bpel.xpath10 [1.0.4.v201412041949] > > org.eclipse.graphiti.export.feature.feature.group [0.11.2.v20150204-0954] > > javax.ws.rs [1.1.1.v20130318-1750] > > org.eclipse.bpel.common.feature.source.feature.group [1.0.4.v201412041949] > > org.apache.batik.ext.awt [1.6.0.v201011041432] > > org.eclipse.bpel.wsil.model.source [1.0.4.v201412041949] > > org.eclipse.emf.compare.ide.ui.feature.group [3.0.2.201501201328] > > org.jboss.tools.common.test [3.6.2.CR1-v20150312-0213-B97] > > org.eclipse.emf.query.feature.jar [1.8.0.201405281426] > > org.apache.batik.xml [1.6.0.v201011041432] > > org.eclipse.emf.validation.ocl.feature.group [1.8.0.201405281429] > > org.jboss.tools.community.central [1.3.3.CR1-v20150312-1720-B119] > > com.google.guava [15.0.0.v201403281430] > > org.eclipse.uml2.types [2.0.0.v20150202-0947] > > org.eclipse.emf.validation.ocl.feature.jar [1.8.0.201405281429] > > org.jboss.tools.common.base.test [3.6.2.CR1-v20150312-0213-B97] > > org.eclipse.uml2.uml.edit.feature.jar [5.0.2.v20150202-0947] > > org.eclipse.uml2.uml.feature.jar [5.0.2.v20150202-0947] > > org.eclipse.uml2.uml.edit.feature.group [5.0.2.v20150202-0947] > > org.eclipse.bpel.feature.feature.group [1.0.4.v201412041949] > > org.eclipse.uml2.common.feature.jar [2.0.1.v20150202-0947] > > org.eclipse.bpel.help [1.0.4.v201412041949] > > org.eclipse.bpel.apache.ode.deploy.model.source [1.0.4.v201412041949] > > org.eclipse.bpel.runtimes.source [1.0.4.v201412041949] > > org.eclipse.emf.compare.feature.group [3.0.2.201501201328] > > org.eclipse.emf.compare.ide.ui.feature.jar [3.0.2.201501201328] > > org.eclipse.emf.query.feature.group [1.8.0.201405281426] > > org.eclipse.uml2.common.edit [2.0.0.v20150202-0947] > > org.eclipse.birt.report.data.oda.hive.ui [4.4.2.v201410272105] > > org.eclipse.birt.data.oda.mongodb [4.4.2.v201410272105] > > org.eclipse.birt.core [4.4.2.v201410272105] > > org.eclipse.emf.validation [1.8.0.201405281429] > > org.eclipse.bpel.apache.ode.deploy.model [1.0.4.v201412041949] > > org.eclipse.uml2.feature.jar [5.0.2.v20150202-0947] > > org.eclipse.uml2.uml.validation [5.0.0.v20150202-0947] > > org.eclipse.uml2.uml.resources [5.0.2.v20150202-0947] > > org.eclipse.equinox.security [1.2.0.v20130424-1801] > > org.eclipse.bpel.feature.feature.jar [1.0.4.v201412041949] > > org.apache.commons.logging [1.1.1.v201101211721] > > org.apache.batik.svggen [1.6.0.v201011041432] > > org.eclipse.bpel.common.feature.feature.jar [1.0.4.v201412041949] > > org.eclipse.bpel.apache.ode.deploy.ui.source [1.0.4.v201412041949] > > org.apache.ant [1.9.2.v201404171502] > > org.eclipse.uml2.uml.editor [5.0.1.v20150202-0947] > > org.eclipse.bpel.validator [1.0.4.v201412041949] > > org.eclipse.bpel.apache.ode.runtime.feature.feature.jar [1.0.4.v201412041949] > > org.eclipse.uml2.uml.profile.standard [1.0.0.v20150202-0947] > > org.eclipse.ocl.all.feature.jar [5.0.2.v20140725-2242] > > org.apache.commons.httpclient [3.1.0.v201012070820] > > org.eclipse.emf.transaction.ui [1.4.0.201405281451] > > org.jboss.tools.birt.feature.feature.jar [1.7.0.Final-v20141209-0111-B18] > > org.jsoup [1.7.2.v201304221138] > > org.eclipse.graphiti [0.11.2.v20150204-0954] > > org.eclipse.birt.report.data.oda.jdbc [4.4.2.v201410272105] > > org.eclipse.ocl.uml [5.0.0.v20140610-0641] > > org.eclipse.emf.compare.edit [4.0.0.201501201328] > > org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20150202-0947] > > org.eclipse.ocl.feature.jar [3.4.2.v20140725-2242] > > org.eclipse.uml2.uml.feature.group [5.0.2.v20150202-0947] > > org.eclipse.emf.compare.ide [3.1.2.201501201328] > > com.ibm.icu [52.1.1.v201501240615] > > org.eclipse.uml2.common.edit.feature.group [2.0.0.v20150202-0947] > > org.apache.commons.logging [1.0.4.v201101211617] > > org.eclipse.emf.workspace [1.5.1.201405281451] > > org.eclipse.bpel.common.feature.source.feature.jar [1.0.4.v201412041949] > > org.eclipse.uml2.codegen.ecore.ui [2.0.0.v20150202-0947] > > org.w3c.dom.smil [1.0.0.v200806040011] > > org.eclipse.bpel.feature.source.feature.jar [1.0.4.v201412041949] > > org.eclipse.emf.workspace.feature.group [1.8.0.201405281451] > > org.eclipse.bpel.model [1.0.4.v201412041949] > > org.eclipse.emf.validation.ui.ide [1.3.0.201405281429] > > org.eclipse.bpel.apache.ode.runtime.feature.feature.group [1.0.4.v201412041949] > > org.eclipse.emf.compare.rcp.ui [4.0.1.201501201328] > > org.hamcrest.core [1.3.0.v201303031735] > > org.eclipse.bpel.cheatsheet [1.0.4.v201412041949] > > org.jboss.tools.birt.oda.ui [1.7.0.Final-v20141209-0111-B18] > > org.eclipse.ocl.feature.group [3.4.2.v20140725-2242] > > org.eclipse.ocl.all.feature.group [5.0.2.v20140725-2242] > > org.eclipse.emf.validation.feature.group [1.8.0.201405281429] > > org.jboss.tools.jmx.core.test [1.6.3.CR1-v20150312-0240-B128] > > org.eclipse.birt.report.data.bidi.utils [4.4.2.v201410272105] > > org.jboss.tools.community.project.examples.feature.feature.jar [2.0.2.CR1-v20150312-1720-B119] > > org.eclipse.uml2.common.edit.feature.jar [2.0.0.v20150202-0947] > > org.jboss.tools.tests [3.5.1.CR1-v20150312-0213-B97] > > org.eclipse.graphiti.feature.feature.group [0.11.2.v20150204-0954] > > org.eclipse.core.net [1.2.200.v20140124-2013] > > org.eclipse.emf.validation.ui [1.7.0.201405281429] > > org.eclipse.bpel.help.source [1.0.4.v201412041949] > > org.eclipse.bpel.common.wsdl.source [1.0.4.v201412041949] > > org.eclipse.birt.report.data.oda.hive [4.4.2.v201410272105] > > org.jboss.tools.community.project.examples.feature.feature.group [2.0.2.CR1-v20150312-1720-B119] > > org.w3c.dom.svg [1.1.0.v201011041433] > > org.apache.batik.util.gui [1.6.0.v201011041432] > > org.eclipse.birt.report.data.bidi.utils.ui [4.4.2.v201410272105] > > org.eclipse.bpel.common.model.source [1.0.4.v201412041949] > > org.apache.batik.css [1.6.0.v201011041432] > > org.eclipse.ocl.common [1.2.0.v20140610-0641] > > org.eclipse.bpel.common.ui.source [1.0.4.v201412041949] > > org.eclipse.emf.compare [3.1.2.201501201328] > > org.eclipse.emf.workspace.ui [1.3.0.201405281451] > > org.eclipse.graphiti.export.batik [0.11.2.v20150204-0954] > > org.eclipse.bpel.runtimes [1.0.4.v201412041949] > > org.eclipse.bpel.apache.ode.runtime.source [1.0.4.v201412041949] > > org.eclipse.bpel.xpath10.source [1.0.4.v201412041949] > > org.eclipse.jdt.junit.core [3.7.300.v20140409-1618] > > org.eclipse.emf.compare.ide.ui [4.0.2.201501201328] > > org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.0.2.v20150202-0947] > > org.eclipse.graphiti.export.feature.feature.jar [0.11.2.v20150204-0954] > > org.eclipse.emf.compare.rcp [2.2.1.201501201328] > > org.jboss.tools.community.central.feature.feature.jar [1.3.3.CR1-v20150312-1720-B119] > > org.eclipse.ocl [3.4.2.v20140725-2242] > > org.jboss.tools.community.central.feature.feature.group [1.3.3.CR1-v20150312-1720-B119] > > org.eclipse.bpel.wsil.model [1.0.4.v201412041949] > > org.eclipse.emf.compare.doc [3.1.1.201501201328] > > org.jboss.tools.birt.oda [1.7.0.Final-v20141209-0111-B18] > > org.eclipse.uml2.uml [5.0.2.v20150202-0947] > > org.eclipse.ocl.uml.feature.group [5.0.2.v20140725-2242] > > org.eclipse.draw2d [3.9.101.201408150207] > > org.eclipse.bpel.validator.source [1.0.4.v201412041949] > > org.eclipse.bpel.feature.source.feature.group [1.0.4.v201412041949] > > org.eclipse.uml2.uml.ecore.importer [3.0.0.v20150202-0947] > > org.eclipse.uml2 [5.0.0.v20150202-0947] > > org.eclipse.bpel.cheatsheet.source [1.0.4.v201412041949] > > org.eclipse.emf.query.ocl.feature.group [1.8.0.201405281426] > > org.eclipse.ocl.uml.feature.jar [5.0.2.v20140725-2242] > > org.jboss.tools.birt.core [1.7.0.Final-v20141209-0111-B18] > > lpg.runtime.java [2.0.17.v201004271640] > > org.eclipse.emf.validation.ocl [1.4.0.201405281429] > > org.eclipse.uml2.uml.edit [5.0.2.v20150202-0947] > > org.eclipse.birt.report.data.oda.jdbc.ui [4.4.2.v201410272105] > > org.eclipse.emf.query [1.7.0.201405281426] > > org.apache.batik.util [1.6.0.v201011041432] > > org.eclipse.bpel.common.ui [1.0.4.v201412041949] > > org.eclipse.emf.validation.feature.jar [1.8.0.201405281429] > > org.eclipse.bpel.apache.ode.runtime.feature.source.feature.jar [1.0.4.v201412041949] > > org.eclipse.emf.workspace.feature.jar [1.8.0.201405281451] > > org.eclipse.uml2.codegen.ecore [2.0.2.v20150202-0947] > > org.eclipse.equinox.cm [1.1.0.v20131021-1936] > > org.eclipse.graphiti.mm [0.11.2.v20150204-0954] > > org.eclipse.birt.data.oda.mongodb.ui [4.4.2.v201410272105] > > org.eclipse.emf.query.ocl [2.0.0.201405281426] > > org.jboss.tools.as.test.core [3.0.3.CR1-v20150312-0240-B128] > > org.jboss.tools.birt.feature.feature.group [1.7.0.Final-v20141209-0111-B18] > > org.eclipse.uml2.common [2.0.1.v20150202-0947] > > org.eclipse.uml2.ant [1.0.0.v20150202-0947] > > org.apache.commons.codec [1.6.0.v201305230611] > > org.jboss.tools.community.project.examples [2.0.2.CR1-v20150312-1720-B119] > > org.eclipse.uml2.codegen.ecore.ui.feature.group [2.0.2.v20150202-0947] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 25 unique IUs > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 173 unique IUs > target-platform-ea.target.repo > < org.eclipse.bpel.apache.ode.runtime [1.0.4.v201412041949] > < org.eclipse.bpel.apache.ode.deploy.ui [1.0.4.v201412041949] > < org.eclipse.emf.query.ocl.feature.jar [1.8.0.201405281426] > < org.eclipse.emf.transaction [1.8.0.201405281451] > < org.eclipse.orbit.mongodb [2.10.1.v20130422-1135] > < org.w3c.css.sac [1.3.1.v200903091627] > < org.eclipse.bpel.apache.ode.runtime.feature.source.feature.group [1.0.4.v201412041949] > < javax.xml [1.3.4.v201005080400] > < org.eclipse.ocl.feature.group [3.4.0.v20140528-1458] > < org.eclipse.uml2.uml.edit.feature.group [5.0.0.v20140602-0749] > < org.eclipse.bpel.ui [1.0.4.v201412041949] > < org.eclipse.equinox.simpleconfigurator.manipulator [2.0.0.v20131217-1203] > < org.eclipse.emf.transaction.feature.group [1.8.0.201405281451] > < org.eclipse.bpel.xpath10 [1.0.4.v201412041949] > < org.apache.batik.ext.awt [1.6.0.v201011041432] > < org.eclipse.ocl.all.feature.group [5.0.0.v20140528-1458] > < org.eclipse.graphiti [0.11.0.v20140528-0646] > < org.eclipse.emf.query.feature.jar [1.8.0.201405281426] > < org.apache.batik.xml [1.6.0.v201011041432] > < org.eclipse.emf.compare.ide.ui.feature.group [3.0.0.201406111328] > < org.eclipse.bpmn2.modeler.help [1.1.1.201501081320] > < org.eclipse.uml2.uml.feature.jar [5.0.0.v20140602-0749] > < org.jboss.tools.tests [3.5.0.Final-v20141016-2021-B66] > < org.eclipse.uml2.codegen.ecore.ui.feature.group [2.0.0.v20140602-0749] > < org.eclipse.emf.validation [1.8.0.201405281429] > < org.eclipse.bpel.apache.ode.deploy.model [1.0.4.v201412041949] > < org.apache.servicemix.bundles.aopalliance [1.0.0.3] > < org.eclipse.graphiti.export.feature.feature.jar [0.11.0.v20140528-0646] > < org.jboss.tools.community.central.feature.feature.group [1.3.0.Final-v20141016-1914-B105] > < org.apache.batik.svggen [1.6.0.v201011041432] > < org.eclipse.emf.compare.ide.ui.feature.jar [3.0.0.201406111328] > < org.eclipse.ocl.all.feature.jar [5.0.0.v20140528-1458] > < org.eclipse.bpel.apache.ode.runtime.feature.feature.jar [1.0.4.v201412041949] > < org.eclipse.graphiti.export.batik [0.11.0.v20140528-0646] > < org.eclipse.uml2.uml.edit [5.0.0.v20140602-0749] > < org.jsoup [1.7.2.v201304221138] > < org.jboss.tools.jmx.core.test [1.6.0.Final-v20141016-1911-B95] > < org.eclipse.uml2.uml.ecore.importer [3.0.0.v20140602-0749] > < org.eclipse.emf.workspace [1.5.1.201405281451] > < org.apache.commons.logging [1.0.4.v201101211617] > < org.eclipse.emf.workspace.feature.group [1.8.0.201405281451] > < org.eclipse.uml2.ant [1.0.0.v20140602-0749] > < org.eclipse.bpel.cheatsheet [1.0.4.v201412041949] > < org.eclipse.emf.validation.feature.group [1.8.0.201405281429] > < org.eclipse.graphiti.export.feature.feature.group [0.11.0.v20140528-0646] > < org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20140602-0749] > < javax.ws.rs [1.1.1.v20101004-1200] > < org.eclipse.emf.validation.ui [1.7.0.201405281429] > < org.eclipse.uml2.uml.editor [5.0.0.v20140602-0749] > < org.eclipse.graphiti.feature.feature.jar [0.11.0.v20140528-0646] > < org.eclipse.bpel.common.model.source [1.0.4.v201412041949] > < org.apache.batik.css [1.6.0.v201011041432] > < org.jboss.tools.birt.feature.feature.jar [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.bpel.common.ui.source [1.0.4.v201412041949] > < org.eclipse.bpmn2 [1.0.0.201412192138] > < org.eclipse.bpel.runtimes [1.0.4.v201412041949] > < org.eclipse.bpel.xpath10.source [1.0.4.v201412041949] > < org.eclipse.uml2.types [2.0.0.v20140602-0749] > < org.eclipse.jdt.junit.core [3.7.300.v20140409-1618] > < org.springframework.aspects [3.1.4.RELEASE] > < org.eclipse.birt.report.data.bidi.utils.ui [4.4.0.v201405191524] > < org.eclipse.ocl.feature.jar [3.4.0.v20140528-1458] > < org.eclipse.uml2.uml.edit.feature.jar [5.0.0.v20140602-0749] > < org.eclipse.emf.compare.doc [3.1.0.201406111328] > < org.eclipse.emf.compare [3.1.0.201406111328] > < org.eclipse.bpel.feature.source.feature.group [1.0.4.v201412041949] > < org.eclipse.emf.query.ocl.feature.group [1.8.0.201405281426] > < org.eclipse.bpel.cheatsheet.source [1.0.4.v201412041949] > < com.ibm.icu [52.1.0.v201404241930] > < org.apache.poi [3.9.0.v201303080712] > < org.eclipse.emf.validation.ocl [1.4.0.201405281429] > < org.eclipse.emf.query [1.7.0.201405281426] > < org.apache.batik.util [1.6.0.v201011041432] > < org.eclipse.bpel.common.ui [1.0.4.v201412041949] > < org.eclipse.emf.validation.feature.jar [1.8.0.201405281429] > < org.eclipse.bpel.apache.ode.runtime.feature.source.feature.jar [1.0.4.v201412041949] > < org.eclipse.emf.workspace.feature.jar [1.8.0.201405281451] > < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201501081320] > < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201501081320] > < org.eclipse.equinox.cm [1.1.0.v20131021-1936] > < org.jboss.tools.common.test [3.6.0.Final-v20141016-2021-B66] > < org.jboss.tools.community.project.examples.feature.feature.group [2.0.0.Final-v20141016-1914-B105] > < org.eclipse.graphiti.feature.feature.group [0.11.0.v20140528-0646] > < org.springframework.osgi.io [1.2.1] > < org.eclipse.graphiti.pattern [0.11.0.v20140528-0646] > < org.eclipse.emf.compare.rcp [2.2.0.201406111328] > < org.jboss.tools.common.base.test [3.6.0.Final-v20141016-2021-B66] > < org.eclipse.ocl.common [1.2.0.v20140528-1458] > < org.eclipse.ocl.uml.feature.group [5.0.0.v20140524-1436] > < org.codehaus.jackson.mapper [1.6.0.v20101005-0925] > < org.junit [4.11.0.v201303080030] > < org.eclipse.bpmn2.editor [1.0.0.201412192138] > < org.eclipse.uml2.feature.jar [5.0.0.v20140602-0749] > < org.eclipse.emf.compare.feature.group [3.0.0.201406111328] > < org.eclipse.emf.transaction.feature.jar [1.8.0.201405281451] > < org.eclipse.bpel.common.model [1.0.4.v201412041949] > < org.eclipse.uml2.common.feature.group [2.0.0.v20140602-0749] > < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201501081320] > < org.eclipse.ocl.ecore [3.3.100.v20140524-1358] > < org.apache.batik.dom [1.6.0.v201011041432] > < org.eclipse.bpel.model.source [1.0.4.v201412041949] > < org.eclipse.bpel.common.wsdl [1.0.4.v201412041949] > < org.eclipse.uml2 [5.0.0.v20140602-0749] > < org.eclipse.bpel.common.feature.feature.group [1.0.4.v201412041949] > < org.eclipse.uml2.feature.group [5.0.0.v20140602-0749] > < org.eclipse.bpel.ui.source [1.0.4.v201412041949] > < org.eclipse.emf.compare.feature.jar [3.0.0.201406111328] > < org.springframework.osgi.extender [1.2.1] > < org.eclipse.uml2.uml.feature.group [5.0.0.v20140602-0749] > < org.eclipse.bpel.common.feature.source.feature.group [1.0.4.v201412041949] > < org.eclipse.uml2.common.edit.feature.jar [2.0.0.v20140602-0749] > < org.eclipse.bpel.wsil.model.source [1.0.4.v201412041949] > < org.jboss.tools.as.test.core [3.0.0.Final-v20141016-1911-B95] > < org.eclipse.uml2.codegen.ecore.ui [2.0.0.v20140602-0749] > < org.springframework.osgi.extensions.annotations [1.2.1] > < org.eclipse.emf.validation.ocl.feature.group [1.8.0.201405281429] > < com.google.guava [15.0.0.v201403281430] > < org.eclipse.emf.validation.ocl.feature.jar [1.8.0.201405281429] > < org.eclipse.uml2.common.edit.feature.group [2.0.0.v20140602-0749] > < org.eclipse.bpmn2.modeler.ui [1.1.1.201501081320] > < org.eclipse.bpel.feature.feature.group [1.0.4.v201412041949] > < org.eclipse.bpel.help [1.0.4.v201412041949] > < org.jboss.tools.locus.sf.saxon [9.2.1.5j-Final-v20131024-0922-B58] > < org.eclipse.bpel.apache.ode.deploy.model.source [1.0.4.v201412041949] > < org.eclipse.bpel.runtimes.source [1.0.4.v201412041949] > < org.eclipse.emf.query.feature.group [1.8.0.201405281426] > < org.eclipse.uml2.uml.profile.standard [1.0.0.v20140602-0749] > < org.eclipse.equinox.security [1.2.0.v20130424-1801] > < javax.xml.soap [1.3.0.v201105210645] > < org.eclipse.bpel.feature.feature.jar [1.0.4.v201412041949] > < org.eclipse.emf.compare.rcp.ui [4.0.0.201406111328] > < org.jboss.tools.community.project.examples [2.0.0.Final-v20141016-1914-B105] > < org.apache.commons.logging [1.1.1.v201101211721] > < org.eclipse.bpel.common.feature.feature.jar [1.0.4.v201412041949] > < org.eclipse.bpel.apache.ode.deploy.ui.source [1.0.4.v201412041949] > < org.apache.ant [1.9.2.v201404171502] > < org.eclipse.birt.core [4.4.0.v201405191524] > < org.eclipse.bpel.validator [1.0.4.v201412041949] > < org.apache.commons.httpclient [3.1.0.v201012070820] > < javax.xml.bind [2.1.9.v201005080401] > < org.eclipse.emf.transaction.ui [1.4.0.201405281451] > < org.eclipse.birt.report.data.oda.hive [4.4.0.v201405191524] > < org.jboss.tools.birt.oda.ui [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.graphiti.ui [0.11.0.v20140528-0646] > < org.eclipse.birt.report.data.oda.hive.ui [4.4.0.v201405191524] > < org.eclipse.birt.report.data.bidi.utils [4.4.0.v201405191524] > < org.eclipse.bpel.common.feature.source.feature.jar [1.0.4.v201412041949] > < org.eclipse.bpel.feature.source.feature.jar [1.0.4.v201412041949] > < org.w3c.dom.smil [1.0.0.v200806040011] > < org.eclipse.bpel.apache.ode.runtime.feature.feature.group [1.0.4.v201412041949] > < org.eclipse.emf.validation.ui.ide [1.3.0.201405281429] > < org.eclipse.bpel.model [1.0.4.v201412041949] > < org.eclipse.draw2d [3.9.100.201405261516] > < org.hamcrest.core [1.3.0.v201303031735] > < org.eclipse.birt.data.oda.mongodb [4.4.0.v201405191524] > < org.jboss.tools.community.central [1.3.0.Final-v20141016-1914-B105] > < org.eclipse.uml2.common.edit [2.0.0.v20140602-0749] > < org.eclipse.emf.compare.edit [4.0.0.201406111328] > < org.eclipse.birt.report.data.oda.jdbc [4.4.0.v201405191524] > < org.eclipse.uml2.codegen.ecore [2.0.0.v20140602-0749] > < org.jboss.tools.community.central.feature.feature.jar [1.3.0.Final-v20141016-1914-B105] > < org.eclipse.uml2.uml.resources [5.0.0.v20140602-0749] > < org.eclipse.core.net [1.2.200.v20140124-2013] > < org.eclipse.bpel.help.source [1.0.4.v201412041949] > < org.eclipse.uml2.common.feature.jar [2.0.0.v20140602-0749] > < org.eclipse.bpel.common.wsdl.source [1.0.4.v201412041949] > < org.codehaus.jackson.core [1.6.0.v20101005-0925] > < org.eclipse.uml2.common [2.0.0.v20140602-0749] > < org.jboss.tools.birt.oda [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.emf.compare.ide.ui [4.0.0.201406111328] > < org.eclipse.bpmn2.modeler.core [1.1.1.201501081320] > < org.w3c.dom.svg [1.1.0.v201011041433] > < org.eclipse.bpmn2.edit [1.0.0.201412192138] > < org.apache.batik.util.gui [1.6.0.v201011041432] > < org.eclipse.emf.workspace.ui [1.3.0.201405281451] > < org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.0.0.v20140602-0749] > < org.eclipse.bpel.apache.ode.runtime.source [1.0.4.v201412041949] > < org.jboss.tools.locus.mockito [1.9.5.Final_patched_TEIIDDES-1681-v20131024-0922-B58] > < org.eclipse.uml2.uml [5.0.0.v20140602-0749] > < org.jboss.tools.birt.core [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.bpel.wsil.model [1.0.4.v201412041949] > < org.eclipse.bpmn2.feature.jar [1.0.0.201412192138] > < org.eclipse.ocl.uml [5.0.0.v20140520-1401] > < org.eclipse.emf.compare.ide [3.1.0.201406111328] > < org.eclipse.bpel.validator.source [1.0.4.v201412041949] > < org.springframework.osgi.core [1.2.1] > < org.jboss.tools.locus.jcip.annotations [1.0.0.Final-v20131024-0922-B58] > < org.jboss.tools.community.project.examples.feature.feature.jar [2.0.0.Final-v20141016-1914-B105] > < org.eclipse.birt.report.data.oda.jdbc.ui [4.4.0.v201405191524] > < lpg.runtime.java [2.0.17.v201004271640] > < org.eclipse.bpmn2.feature.group [1.0.0.201412192138] > < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201501081320] > < org.jboss.tools.birt.feature.feature.group [1.7.0.Final-v20141016-1529-B14] > < org.eclipse.birt.data.oda.mongodb.ui [4.4.0.v201405191524] > < org.eclipse.emf.query.ocl [2.0.0.201405281426] > < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201501081320] > < org.eclipse.ocl [3.4.0.v20140524-1358] > < org.apache.commons.codec [1.6.0.v201305230611] > < org.eclipse.ocl.uml.feature.jar [5.0.0.v20140524-1436] > < org.eclipse.graphiti.mm [0.11.0.v20140528-0646] > < org.eclipse.uml2.uml.validation [5.0.0.v20140602-0749] > > org.jboss.tools.community.project.examples.feature.feature.group [2.0.2.CR1-v20150312-1720-B119] > > org.jboss.tools.birt.oda [1.7.0.Final-v20141209-0111-B18] > > org.jboss.tools.birt.oda.ui [1.7.0.Final-v20141209-0111-B18] > > org.jboss.tools.birt.feature.feature.jar [1.7.0.Final-v20141209-0111-B18] > > org.jboss.tools.community.project.examples.feature.feature.jar [2.0.2.CR1-v20150312-1720-B119] > > org.jboss.tools.community.central [1.3.3.CR1-v20150312-1720-B119] > > org.jboss.tools.birt.feature.feature.group [1.7.0.Final-v20141209-0111-B18] > > org.jboss.tools.birt.core [1.7.0.Final-v20141209-0111-B18] > > org.jboss.tools.community.central.feature.feature.jar [1.3.3.CR1-v20150312-1720-B119] > > org.jboss.tools.community.central.feature.feature.group [1.3.3.CR1-v20150312-1720-B119] > > org.jboss.tools.community.project.examples [2.0.2.CR1-v20150312-1720-B119] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 201 unique IUs > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 11 unique IUs -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ] Debbie Steigner commented on JBIDE-12161: ----------------------------------------- Any update on when/if domain deployment will be supported for JBDS? > Deploy application to JBoss AS 7 in domain mode > ----------------------------------------------- > > Key: JBIDE-12161 > URL: https://issues.jboss.org/browse/JBIDE-12161 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.CR1 > Environment: Any. > Reporter: Humberto Ferreira da Luz Jr. > Assignee: Rob Stryker > Labels: f2f2012 > Fix For: 4.2.x > > > I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode. > We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-3393: ---------------------------------- Ahh - I think that explains it. I really can't change https://devstudio.redhat.com/updates/8.0/devstudio-earlyaccess.properties until I'm ready to go live - I'm at QE handoff of the CR1 build now. So as features make their way from EA to released, the QE handoff build will always have this issue. My QE test instructions indicate which jboss.discovery.directory.url and jboss.discovery.site.integration-stack.url to use but they rely on the JBDS 8.0.2 EA props file as defined by ide-config.properties. I guess I'll wait until after QE has sanctioned the bits and then fix this when it goes live. Thanks for looking into it Fred and Xavier. > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19545) Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19545?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19545: ------------------------------------- Labels: connection_wizard (was: ) > Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19545 > URL: https://issues.jboss.org/browse/JBIDE-19545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: save-password-checked.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19545) Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19545?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19545: ---------------------------------------- Assignee: Andre Dietisheim Resolution: Done > Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19545 > URL: https://issues.jboss.org/browse/JBIDE-19545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: save-password-checked.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19545) Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19545?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19545: ------------------------------------------ merged and pushed to upstream/master > Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19545 > URL: https://issues.jboss.org/browse/JBIDE-19545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: save-password-checked.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3393: -------------------------------------- The list of Early Access artifacts is maintained in the earlyaccess.properties file. For 8.0.2, it's https://devstudio.redhat.com/updates/8.0/devstudio-earlyaccess.properties (the file to use is specified in http://download.jboss.org/jbosstools/configuration/ide-config.properties ). Please provide a PR against the jbosstools-download.jboss.org repository to fix this file. > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Mickael Istria reassigned JBDS-3393: ------------------------------------ Assignee: Paul Leacu (was: Mickael Istria) > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3393: ----------------------------------- {quote} *fbricon* pleacu: but why does SOA appear in both categories in the first place? *fbricon* pleacu: once it graduated out of EA, it should not be available as EA anymore *pleacu* fbricon: half of the features are released and half are still EA {quote} > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3393: --------------------------------- Assignee: Mickael Istria > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Mickael Istria > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19545) Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19545?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19545: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19545 > URL: https://issues.jboss.org/browse/JBIDE-19545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: save-password-checked.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBDS-3393: ----------------------------- Attachment: ss1.png ss2.png > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Paul Leacu (JIRA)

Paul Leacu created JBDS-3393: -------------------------------- Summary: Early Access Enabled banner appears w/out EA content installed Key: JBDS-3393 URL: https://issues.jboss.org/browse/JBDS-3393 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central Affects Versions: 8.1.0.CR1 Reporter: Paul Leacu 1. Start w/ Eclipse JEE Luna SR2 2. Install JBDS 8.0.2 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't yet enabled early access. ref ss2.png. The plugin.xmls are here: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19038. ------------------------------------ Resolution: Done This is actually working on JBT 4.2.3 (the glitch about the Arquillian icon is a seprate Jira) > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > Attachments: JBDS_810_GA.png > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19547) Use cordova platform downloads from npm

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19547?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-19547: ------------------------------------ Assignee: Gorkem Ercan > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBIDE-19547 > URL: https://issues.jboss.org/browse/JBIDE-19547 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.2.3.Final > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19547) Use cordova platform downloads from npm

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-19547: ------------------------------------ Summary: Use cordova platform downloads from npm Key: JBIDE-19547 URL: https://issues.jboss.org/browse/JBIDE-19547 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Affects Versions: 4.2.3.Final Reporter: Gorkem Ercan Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. cordova-ios ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] cordova-android [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] cordova-wp8 [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- yes, so please just have central not try and load p2 metadata if it is not available. right now it just makes you not want to have central loaded when developing. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19546?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19546: ------------------------------------------- Steps to Reproduce: 1. Go to Hybrid Mobile Engines Preferences/Project Properties 2. Click download button and select version which is not already installed 3. Click OK, and after that click Cancel ASAP 4. See Error log {quote} !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4477) at org.eclipse.swt.SWT.error(SWT.java:4392) at org.eclipse.swt.SWT.error(SWT.java:4363) at org.eclipse.swt.widgets.Widget.error(Widget.java:476) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348) at org.eclipse.swt.widgets.Control.setEnabled(Control.java:3303) at org.eclipse.jface.wizard.ProgressMonitorPart$1.handleEvent(ProgressMonitorPart.java:81) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:338) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) {quote} was: Steps to reproduce: 1. Go to Hybrid Mobile Engines Preferences/Project Properties 2. Click download button and select version which is not already installed 3. Click OK, and after that click Cancel ASAP 4. See Error log {quote} !MESSAGE Unhandled event loop exception during blocked modal context. !STACK 0 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4477) at org.eclipse.swt.SWT.error(SWT.java:4392) at org.eclipse.swt.SWT.error(SWT.java:4363) at org.eclipse.swt.widgets.Widget.error(Widget.java:476) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348) at org.eclipse.swt.widgets.Control.setEnabled(Control.java:3303) at org.eclipse.jface.wizard.ProgressMonitorPart$1.handleEvent(ProgressMonitorPart.java:81) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:338) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4354) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.run(EngineDownloadDialog.java:347) at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.okPressed(EngineDownloadDialog.java:324) {quote} > Unhandled event loop exception when downloading Android engine > -------------------------------------------------------------- > > Key: JBIDE-19546 > URL: https://issues.jboss.org/browse/JBIDE-19546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: Win 7, thym 0.2.0 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Priority: Minor > > It smells like jface bug, but anyway it will be good to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-420) Enable support for a remote SAP tooling update site URL

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-420?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-420. ------------------------------ Resolution: Done Modified the ide-config.properties to create a property that may be used to identify the IS extras URL: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/71b629... https://github.com/jbosstools/jbosstools-download.jboss.org/commit/26c879... Also established IS composites to hold the "extras" URLs (currently only component is SAP tooling): http://download.jboss.org/jbosstools/updates/development/luna/integration... http://download.jboss.org/jbosstools/updates/development/luna/integration... http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > Enable support for a remote SAP tooling update site URL > ------------------------------------------------------- > > Key: JBTIS-420 > URL: https://issues.jboss.org/browse/JBTIS-420 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update the ide-config properties to establish the following: > jboss.site.integration-stack-extras.url|jbosstools|4.2=http://download.jb... > jboss.site.integration-stack-extras.url|devstudio|8=https://devstudio.red... > Also update the SAP POM accordingly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19546?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19546: ------------------------------------------- Description: It smells like jface bug, but anyway it will be good to handle this exception (was: This is jface bug, but please add catch block to handle this exception) > Unhandled event loop exception when downloading Android engine > -------------------------------------------------------------- > > Key: JBIDE-19546 > URL: https://issues.jboss.org/browse/JBIDE-19546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: Win 7, thym 0.2.0 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Priority: Minor > > It smells like jface bug, but anyway it will be good to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3392?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3392: ----------------------------------- This is the exact same problem that was fixed in master with JBIDE-19330 > Arquillian icon is missing in JBDS 8.1.0 Central > ------------------------------------------------ > > Key: JBDS-3392 > URL: https://issues.jboss.org/browse/JBDS-3392 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: JBDS_810_GA.png > > > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-19546: ---------------------------------------------- Summary: Unhandled event loop exception when downloading Android engine Key: JBIDE-19546 URL: https://issues.jboss.org/browse/JBIDE-19546 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha1 Environment: Win 7, thym 0.2.0 Reporter: Konstantin Marmalyukov Assignee: Gorkem Ercan Priority: Minor This is jface bug, but please add catch block to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3392?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3392: ------------------------------- Attachment: JBDS_810_GA.png > Arquillian icon is missing in JBDS 8.1.0 Central > ------------------------------------------------ > > Key: JBDS-3392 > URL: https://issues.jboss.org/browse/JBDS-3392 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: JBDS_810_GA.png > > > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3392: ---------------------------------- Summary: Arquillian icon is missing in JBDS 8.1.0 Central Key: JBDS-3392 URL: https://issues.jboss.org/browse/JBDS-3392 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central Affects Versions: 8.1.0.GA Reporter: Len DiMaggio Assignee: Mickael Istria See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- {quote}untick support software installation and you get the dialog box.{quote} Eclipse applications without p2 is definitely not a case we can/want to support. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- untick support software installation and you get the dialog box. without having central open the dialog box does not show up thus it is triggered by central IMO. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19038: ------------------------------------ [~mickael_istria] The image just wasnt moved from EA discovery plugin to central discovery plugin. I've created PR against jbosstools-discovery. > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > Attachments: JBDS_810_GA.png > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19411) Install from Central has no cancel button for p2 remediation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19411?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19411: ----------------------------------- Summary: Install from Central has no cancel button for p2 remediation (was: early access install has no cancel button for p2 remediation) > Install from Central has no cancel button for p2 remediation > ------------------------------------------------------------ > > Key: JBIDE-19411 > URL: https://issues.jboss.org/browse/JBIDE-19411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > installing angularjs from earlyaccess from nightly build currently results in p2 remediation - which then just blocks all UI and cannot be cancelled. > normal p2 remediation UI can be cancelled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19545) Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19545: ---------------------------------------- Summary: Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked Key: JBIDE-19545 URL: https://issues.jboss.org/browse/JBIDE-19545 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Andre Dietisheim Attachments: save-password-checked.png -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19545) Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19545?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19545: ------------------------------------- Attachment: save-password-checked.png > Connection wizard: if I edit a connection and ucheck "Save Password" and then edit it again, "Save Password" is still checked > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19545 > URL: https://issues.jboss.org/browse/JBIDE-19545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Attachments: save-password-checked.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- By the way, when using PDE, you can go the the Configuration page for you Lauch/Debug config, and tick the "Support software installation..." checkbox. It will allow you to test Central correctly. Given the lack of steps to reproduce and the lack of details about stacktrace/messages, there is nothing that makes it clear that this report is related to earlyaccess. It could be plain Central or p2 issue. I gave a few tries without internet connection and couldn't see an unexpected popup. Catalog fails to load and shows that it may be a connection issue, which seems to be a correct behaviour. I'm in favor of closing this as can't reproduce. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19512) version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19512?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19512: ---------------------------------------- With move to Mars M6, RSE feature will have version 3.7.0.201503181723 and TM ones 4.0.0.201503181723 > version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2 > --------------------------------------------------------------------------- > > Key: JBIDE-19512 > URL: https://issues.jboss.org/browse/JBIDE-19512 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa, target-platform, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > These plugins versions dropped from these versions in JBDS 8.1.0... > {code} > org.eclipse.rse.dstore_3.7.0.201502160819 > org.eclipse.tm.terminal_3.7.0.201502160819 > org.eclipse.rse_3.7.0.201502160819 > org.eclipse.rse.ssh_3.7.0.201502160819 > org.eclipse.rse.telnet_3.7.0.201502160819 > org.eclipse.rse.ftp_3.7.0.201502160819 > org.eclipse.rse.terminals_3.7.0.201502160819 > org.eclipse.rse.local_3.7.0.201502160819 > org.eclipse.rse.core_3.7.0.201502160819 > org.eclipse.rse.terminals.ui_1.2.200.201412161015 > org.eclipse.tm.terminal_3.3.0.201501281007 {code} > to older versions in JBDS 9.0. > This could be an upstream problem (plugins not correctly upversioned at Eclipse) or it could be something that's been fixed in the latest Mars M6. Something we definitely need to investigate and report upstream if not fixed there already. > See detailed reports here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19512) version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19512?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19512: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 > version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2 > --------------------------------------------------------------------------- > > Key: JBIDE-19512 > URL: https://issues.jboss.org/browse/JBIDE-19512 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa, target-platform, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > These plugins versions dropped from these versions in JBDS 8.1.0... > {code} > org.eclipse.rse.dstore_3.7.0.201502160819 > org.eclipse.tm.terminal_3.7.0.201502160819 > org.eclipse.rse_3.7.0.201502160819 > org.eclipse.rse.ssh_3.7.0.201502160819 > org.eclipse.rse.telnet_3.7.0.201502160819 > org.eclipse.rse.ftp_3.7.0.201502160819 > org.eclipse.rse.terminals_3.7.0.201502160819 > org.eclipse.rse.local_3.7.0.201502160819 > org.eclipse.rse.core_3.7.0.201502160819 > org.eclipse.rse.terminals.ui_1.2.200.201412161015 > org.eclipse.tm.terminal_3.3.0.201501281007 {code} > to older versions in JBDS 9.0. > This could be an upstream problem (plugins not correctly upversioned at Eclipse) or it could be something that's been fixed in the latest Mars M6. Something we definitely need to investigate and report upstream if not fixed there already. > See detailed reports here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19544) Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19544?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19544. ------------------------------------ nothing for QE to verify > Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19544 > URL: https://issues.jboss.org/browse/JBIDE-19544 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The naming scheme in current code base where we have support for OpenShift v2 and v3 is: > * v3 = OpenShift > * v2 = Express > Accordingly we should rename > * OpenShiftExpressUIMessages -> ExpressUIMessages > * OpenShiftExpressCoreMessages -> ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19497?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19497: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 > Use Jetty 9 in TP > ----------------- > > Key: JBIDE-19497 > URL: https://issues.jboss.org/browse/JBIDE-19497 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha2 > > > *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles > *Project page/sources:* https://www.eclipse.org/jetty/ > *Version:* 9.2.5.v20141112 > *License and owner:* Eclipse.org > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.2.5.v20... > *Include Sources:* Yes > *Affected projects:* Livereload, Cordovasim, BrowserSim > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO: suggested diff on the .target files/p2diff > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19544) Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19544?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19544: ------------------------------------------ merged and pushed to upstream/master > Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19544 > URL: https://issues.jboss.org/browse/JBIDE-19544 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The naming scheme in current code base where we have support for OpenShift v2 and v3 is: > * v3 = OpenShift > * v2 = Express > Accordingly we should rename > * OpenShiftExpressUIMessages -> ExpressUIMessages > * OpenShiftExpressCoreMessages -> ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19544) Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19544: ---------------------------------------- Summary: Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages Key: JBIDE-19544 URL: https://issues.jboss.org/browse/JBIDE-19544 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Alpha2 Reporter: Andre Dietisheim The naming scheme in current code base where we have support for OpenShift v2 and v3 is: * v3 = OpenShift * v2 = Express Accordingly we should rename * OpenShiftExpressUIMessages -> ExpressUIMessages * OpenShiftExpressCoreMessages -> ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19544) Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19544?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19544: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19544 > URL: https://issues.jboss.org/browse/JBIDE-19544 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The naming scheme in current code base where we have support for OpenShift v2 and v3 is: > * v3 = OpenShift > * v2 = Express > Accordingly we should rename > * OpenShiftExpressUIMessages -> ExpressUIMessages > * OpenShiftExpressCoreMessages -> ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19544) Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19544?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19544: ---------------------------------------- Assignee: Andre Dietisheim > Cleanup: Rename OpenShiftExpressUIMessages, OpenShiftExpressCoreMessages -> ExpressUI-/ExpressCoreMessages > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19544 > URL: https://issues.jboss.org/browse/JBIDE-19544 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > The naming scheme in current code base where we have support for OpenShift v2 and v3 is: > * v3 = OpenShift > * v2 = Express > Accordingly we should rename > * OpenShiftExpressUIMessages -> ExpressUIMessages > * OpenShiftExpressCoreMessages -> ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19503) Explorer, Connection wizard: Connection without stored password is not connected after providing password

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19503?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19503: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have an OpenShift v2 connection where you didnt store the password !password-not-stored.png! # EXEC: restart Eclipse # EXEC: Unfold your connection # ASSERT: the connection shows a child "Loading" !connection-loading.png! # ASSERT: connection dialog shows up so that you can provide the password # EXEC: provide the password and hit "Finish" Result: "Loading" is replaced by "<User is not connected>" !connection-not-connected.png! was: # ASSERT: make sure that you have a connection where you didnt store the password !password-not-stored.png! # EXEC: restart Eclipse # EXEC: Unfold your connection # ASSERT: the connection shows a child "Loading" !connection-loading.png! # ASSERT: connection dialog shows up so that you can provide the password # EXEC: provide the password and hit "Finish" Result: "Loading" is replaced by "<User is not connected>" !connection-not-connected.png! > Explorer, Connection wizard: Connection without stored password is not connected after providing password > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19503 > URL: https://issues.jboss.org/browse/JBIDE-19503 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, explorer > Attachments: connection-loading.png, connection-not-connected.png, password-not-stored.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19038) Arquillian should not be in JBT EA catalog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19038?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19038: ------------------------------------ [~ldimaggio]There must be something wrong on your side. I tried it again with JBDS 8.1.0.GA and the icon IS there. Your screenshot looks more like from JBT (because Arquillian is EA in JBDS and thus it shoud have yellow background) > Arquillian should not be in JBT EA catalog > ------------------------------------------ > > Key: JBIDE-19038 > URL: https://issues.jboss.org/browse/JBIDE-19038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.2.Final > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.2.3.Final > > Attachments: JBDS_810_GA.png > > > In JBIDE-18995 Arquillian was removed from EA (by removing it from jbosstools-earlyaccess.properties), but on Software/Update page it is still displayed under EA features. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Vlado Pakan closed JBDS-3262. ----------------------------- Deprecation of Visual JSF Preview is properly described in Release Notes therefore closing > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 8.1.0.GA > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Vlado Pakan resolved JBDS-3262. ------------------------------- Resolution: Done > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 8.1.0.GA > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-617) Update CSP for JBDS 8.1 GA Release

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-617?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-617. -------------------------------- Resolution: Done Done and can be viewed here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > Update CSP for JBDS 8.1 GA Release > ---------------------------------- > > Key: TOOLSDOC-617 > URL: https://issues.jboss.org/browse/TOOLSDOC-617 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.2.3.Final > > > * Remove CR1 Release Notes > * Publish GA Release Notes > * Request docs refresh from gss-lab -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-617) Update CSP for JBDS 8.1 GA Release

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-617?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-617: ------------------------------------ Tagged and pushed changes. Requested gss-labs refresh the site after the changes appear on CSP. Pushed the supported configuration pages public. > Update CSP for JBDS 8.1 GA Release > ---------------------------------- > > Key: TOOLSDOC-617 > URL: https://issues.jboss.org/browse/TOOLSDOC-617 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.2.3.Final > > > * Remove CR1 Release Notes > * Publish GA Release Notes > * Request docs refresh from gss-lab -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015