[JBoss JIRA] (ERT-172) Need to find a better solution for bower dependencies content assistant [EBZ#492191]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-172:
---------------------------------------
Summary: Need to find a better solution for bower dependencies content assistant [EBZ#492191]
Key: ERT-172
URL: https://issues.jboss.org/browse/ERT-172
Project: Eclipse Release Train
Issue Type: Task
Components: WTP Source Editing
Reporter: Friendly Jira Robot
In order to show content assist proposals for bower dependencies a 2rd party web service was used. It was a really problematic due to its unstable work, slowness and a tendency to change an URL for requests and formats of response.
I do believe, we should not provide any content assist for dependencies in case no search pattern is provided (typed in) by a user because of really huge memory requirements and network overload in such case:
- Native "bower search" command also takes a couple of minutes to complete and returns ~3.2MB of data (which means even more amount of network transfers).
Given this, IMHO, we have not to show *all* available packages in content assistant, but show package list only if at least first letter (or a couple of beginning letters) of package name is typed in by a user.
Also the way to get the proposals itself is also a question: we cannot rely on 3rd party services as they are not enough stable and fast.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ERT-169) support for search/pull/push operations on third-party registries [EBZ#471661]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-169:
---------------------------------------
Summary: support for search/pull/push operations on third-party registries [EBZ#471661]
Key: ERT-169
URL: https://issues.jboss.org/browse/ERT-169
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Priority: Trivial
Fix For: Neon (4.6)
We could reuse the nested Search dialog in the "Run Image" wizard for this.
* minimal: have set of registries we can search via
* optimal: use docker demon native search api (without setup) : client.searchImages(term)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21118?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21118:
-------------------------------
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21118
> URL: https://issues.jboss.org/browse/JBIDE-21118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560
> {quote}
> So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21283) Update Central to Spring IDE 3.7.3 release when available (replaces CI build)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21283?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21283:
-------------------------------
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> Update Central to Spring IDE 3.7.3 release when available (replaces CI build)
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21283
> URL: https://issues.jboss.org/browse/JBIDE-21283
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> [~mlippert] said: {quote}
> Sorry for the inconvenience regarding the weaving hook versions, the AJDT build uses a specific self-built version of that instead of the one that is included in the Mars and Neon repos. However, this will change in the near future. We are switching to a new build and had to made a few additional changes (as a heads-up):
> org.eclipse.equinox.weaving.aspectj(.source) will be moved to the AJDT project, therefore no longer in Neon (from M5 on, I think)
> org.eclipse.equinox.weaving.sdk(.feature.group) will be moved to the AJDT project as well, also no longer in the Neon repo (from M5 on as well)
> Both will have higher version numbers and being distributed as part of the AJDT build (instead of Equinox).
> I think this will affect the AJDT versions for Eclipse 4.5 + 4.6, so you might come across a similar situation with the Mars repositories (two different versions of the weaving.sdk feature, two different versions of the weaving.hook bundle).
> {quote}
> Then [~dgolovin] said: {quote}Didn't test it, but it seems good to be applied and get Spring IDE back to Central. But it is a nightly build, isn't it? We should remember to update it to released version at some point. Could you create issue for that?{quote}
> So here's that tracker issue, to ensure we get a working SpringIDE 3.7.3 for Neon once it's released, along with a working version of AJDT. May require TWO mirrors instead of one, as we used to have for Mars.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21439:
-------------------------------
Sprint: devex #114 May 2017 (was: devex #113 April 2016)
> Add JSON Editor to JBDS/JBT Target Platform
> -------------------------------------------
>
> Key: JBIDE-21439
> URL: https://issues.jboss.org/browse/JBIDE-21439
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Missing description. Need update site from which to fetch IUs, and a list of which IUs to add.
> Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-22248:
-----------------------------------
Story Points: 2
> Some CI jobs fail at deploying to Nexus
> ---------------------------------------
>
> Key: JBIDE-22248
> URL: https://issues.jboss.org/browse/JBIDE-22248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Nick, can you take a look why mvn deploy fails here?
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> It worked for us in the past.
> It says:
> {code}
> [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 04:49 min
> [INFO] Finished at: 2016-04-26T09:42:02-04:00
> [INFO] Final Memory: 19M/612M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team?
> Cc: [~rawagner]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-22248:
-----------------------------------
Summary: Some CI jobs fail at deploying to Nexus (was: RedDeer master job cannot deploy archetype to nexus)
> Some CI jobs fail at deploying to Nexus
> ---------------------------------------
>
> Key: JBIDE-22248
> URL: https://issues.jboss.org/browse/JBIDE-22248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> Nick, can you take a look why mvn deploy fails here?
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> It worked for us in the past.
> It says:
> {code}
> [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 04:49 min
> [INFO] Finished at: 2016-04-26T09:42:02-04:00
> [INFO] Final Memory: 19M/612M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team?
> Cc: [~rawagner]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-22248:
-----------------------------------
Priority: Blocker (was: Major)
> Some CI jobs fail at deploying to Nexus
> ---------------------------------------
>
> Key: JBIDE-22248
> URL: https://issues.jboss.org/browse/JBIDE-22248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Nick, can you take a look why mvn deploy fails here?
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> It worked for us in the past.
> It says:
> {code}
> [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 04:49 min
> [INFO] Finished at: 2016-04-26T09:42:02-04:00
> [INFO] Final Memory: 19M/612M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team?
> Cc: [~rawagner]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months