July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19810) easymport is slow and wrong compared to basic import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19810. ------------------------------------ Resolution: Done I believe recent changes (giving priority to .project and using multiple threads) actually fixed this issue > easymport is slow and wrong compared to basic import > ---------------------------------------------------- > > Key: JBIDE-19810 > URL: https://issues.jboss.org/browse/JBIDE-19810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta2 > > > when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml. Resulting in slow and eventually wrong imported projects. > This import is *really* slow with easyimport vs just using plain file import. > Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ? > If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19846) Remove generated files after user decides to delete imported unuseful root

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19846?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19846: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Remove generated files after user decides to delete imported unuseful root > -------------------------------------------------------------------------- > > Key: JBIDE-19846 > URL: https://issues.jboss.org/browse/JBIDE-19846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Fix For: 4.3.0.CR1 > > > When user selects folder root that contains no real data (e.g. workspace root) importer asks if he wants to delete the project after import. However, even if the project is deleted from workspace, the generated files (e.g .settings, .project) still remain on the filesystem. These should be deleted as they are clearly not needed nor desired. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19810) easymport is slow and wrong compared to basic import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19810: -------------------------------------- Assignee: Mickael Istria > easymport is slow and wrong compared to basic import > ---------------------------------------------------- > > Key: JBIDE-19810 > URL: https://issues.jboss.org/browse/JBIDE-19810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta2 > > > when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml. Resulting in slow and eventually wrong imported projects. > This import is *really* slow with easyimport vs just using plain file import. > Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ? > If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3465) Consider using SpringIDE 3.7 (or 3.6.4?)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3465: ------------------------------------- I cannot tell users preferences, but I would say, we move forward with SpringIDE 3.7.0, because 3.6.0. is out for over 1 year and it miss many new features and price for a bit less buggy 3rd plugin over new features from 3.7.0. is not worth of it. Let's switch to 3.7.0. > Consider using SpringIDE 3.7 (or 3.6.4?) > ---------------------------------------- > > Key: JBDS-3465 > URL: https://issues.jboss.org/browse/JBDS-3465 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Marián Labuda > Fix For: 9.0.0.CR1 > > Attachments: install-spring-all-features.png, install-spring-sites.png > > > There are new versions of SpringIDE available: > {code:title=http://dist.springsource.com/release/TOOLS/update/e4.5} > org.springframework.ide.eclipse.feature.feature.group 3.6.4.201503051146-RELEASE{code} > {code:title=http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5} > org.springframework.ide.eclipse.feature.feature.group 3.7.0.201506181755-CI-B262{code} > Which would we like to include in Central? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20294) Cannot create OpenShift v3 connection with basic authentization

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20294?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20294: ---------------------------------- Labels: connection (was: ) > Cannot create OpenShift v3 connection with basic authentization > --------------------------------------------------------------- > > Key: JBIDE-20294 > URL: https://issues.jboss.org/browse/JBIDE-20294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Marián Labuda > Priority: Blocker > Labels: connection > > Affected is nightly build, specifically OpenShift plugin with ID 20150715-2039-B879. > When I am trying to create a new OpenShift v3 connection with Basic authentization protocol (username and password) I get following error: > {code} > User "demo" cannot "get" on "/oapi" > com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot "get" on "/oapi" > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:418) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:264) > at com.openshift.internal.restclient.DefaultClient.getCurrentUser(DefaultClient.java:434) > at com.openshift.internal.restclient.authorization.OpenShiftAuthorizationRedirectStrategy.isRedirected(OpenShiftAuthorizationRedirectStrategy.java:63) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:439) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:209) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:199) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:263) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:335) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20294) Cannot create OpenShift v3 connection with basic authentization

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-20294: ------------------------------------- Summary: Cannot create OpenShift v3 connection with basic authentization Key: JBIDE-20294 URL: https://issues.jboss.org/browse/JBIDE-20294 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Marián Labuda Priority: Blocker Affected is nightly build, specifically OpenShift plugin with ID 20150715-2039-B879. When I am trying to create a new OpenShift v3 connection with Basic authentization protocol (username and password) I get following error: {code} User "demo" cannot "get" on "/oapi" com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot "get" on "/oapi" at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:418) at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:264) at com.openshift.internal.restclient.DefaultClient.getCurrentUser(DefaultClient.java:434) at com.openshift.internal.restclient.authorization.OpenShiftAuthorizationRedirectStrategy.isRedirected(OpenShiftAuthorizationRedirectStrategy.java:63) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:439) at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:209) at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:199) at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:263) at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:335) at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20158) migrate devstudio.product to use mojo instead of direct calls to rsync

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20158?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20158. ------------------------------ Done in Beta2x too. > migrate devstudio.product to use mojo instead of direct calls to rsync > ---------------------------------------------------------------------- > > Key: JBIDE-20158 > URL: https://issues.jboss.org/browse/JBIDE-20158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > Remaining TODO from JBIDE-18772: > * devstudio.product : rename / move, then 5 x rsync -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBDS-3384: -------------------------------------- >From Fuse side it looks fine. Waiting for Rob to resolve this issue. > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Beta2 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20158) migrate devstudio.product to use mojo instead of direct calls to rsync

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20158?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20158: ------------------------------------ Note to QE: src zip filename no longer contains "installer" as it contains ALL the upstream JBT sources too. Dir structure for installer jars has changed; no longer in an "installer" folder since it contains more than just installers (also update sites and sources zips). https://devstudio.redhat.com/9.0/snapshots/builds/devstudio.product_maste... http://www.qa.jboss.com/binaries/RHDS/9.0/snapshots/builds/devstudio.prod... Update site content is the same, but process to build it has been simplified. https://devstudio.redhat.com/9.0/snapshots/updates/core/master/ > migrate devstudio.product to use mojo instead of direct calls to rsync > ---------------------------------------------------------------------- > > Key: JBIDE-20158 > URL: https://issues.jboss.org/browse/JBIDE-20158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > Remaining TODO from JBIDE-18772: > * devstudio.product : rename / move, then 5 x rsync -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20261) Need to create features for JavaScript tools (org.jboss.tools.jst.js)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20261?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20261: ------------------------------------ Related to addition of Bower support in JBT: JBIDE-19795 and associated N&N: JBIDE-20253. > Need to create features for JavaScript tools (org.jboss.tools.jst.js) > --------------------------------------------------------------------- > > Key: JBIDE-20261 > URL: https://issues.jboss.org/browse/JBIDE-20261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.Beta1 > Reporter: Ilya Buziuk > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > > There is no proper feature infrastructure for JavaScript Tools (org.jboss.tools.jst.js plugin) in jbosstools-jst -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

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 July 2015