August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-752) JBDSIS 9.0.1 updates - only DV and Fuse

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-752?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-752. ----------------------------------- Resolution: Done Verified with JBDS-IS 9.0.1.GA > JBDSIS 9.0.1 updates - only DV and Fuse > --------------------------------------- > > Key: JBTIS-752 > URL: https://issues.jboss.org/browse/JBTIS-752 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > > The JBDSIS 9.0.1.GA release is now only for DV. This is for any infrastructure/ meta data associated with it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-752) JBDSIS 9.0.1 updates - only DV and Fuse

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-752?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-752: ------------------------------------ Summary: JBDSIS 9.0.1 updates - only DV and Fuse (was: JBDSIS 9.0.1 updates - DV only) > JBDSIS 9.0.1 updates - only DV and Fuse > --------------------------------------- > > Key: JBTIS-752 > URL: https://issues.jboss.org/browse/JBTIS-752 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > > The JBDSIS 9.0.1.GA release is now only for DV. This is for any infrastructure/ meta data associated with it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22965: ------------------------------------- [~mlabuda] do you have ITs for OpenShift vs proxys > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.Final > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22964) Fuse examples are found even though Fuse is not installed (and is not available in Central)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22964?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22964: ------------------------------------- Indeed, we check whether Integration Stack and EA are available before enabling the Camel, Fuse, BRMS examples (or if the proper plugins are installed): - https://github.com/jbosstools/jbosstools-central/blob/master/central/plug... - https://github.com/jbosstools/jbosstools-central-webpage/blob/master/src/... So the proper fix would be to check whether the features are available on the remote urls, but that would be time consuming. The easiest fix is to remove the jboss.discovery.site.integration-stack.url value if nothing is relevant there. > Fuse examples are found even though Fuse is not installed (and is not available in Central) > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22964 > URL: https://issues.jboss.org/browse/JBIDE-22964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM3 > Environment: Devstudio 10.1.0.AM3-v20160809-0722-B5729 > Reporter: Radim Hopp > > After turning Early Access on, camel, fuse, brms examples can be looked up in Central even though Integration stack is not on the Software/Update page. > That is probably because _jboss.discovery.site.integration-stack.url_ and _jboss.discovery.earlyaccess.site.integration-stack.url_ properties are configured in ide-config.properties. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22965: ---------------------------------------- [~fbricon], [~jeffmaury], [~adietish], what about OpenShift tooling? Do we currently support proxy there? If yes, does it require the proxy be set up via Eclipse preferences? [~xcoulon] what about docker tooling btw? We need to create separate issues for OpenShift and Docker tools if there are some issues. We should make sure if CDK (runtime) is properly set up to run with proxy then Eclipse side is also set up properly (at least if it's installed via devsuite installer). > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.Final > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3987) CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)

by Matthew Diamond (JIRA)

[ https://issues.jboss.org/browse/JBDS-3987?page=com.atlassian.jira.plugin.... ] Matthew Diamond commented on JBDS-3987: --------------------------------------- Early on I got a popup asking whether or not I wanted to report an error, and I assume it was this error (but I'm not positive.) I never got anything more intrusive than that. When I suggest JBoss could handle the error better, I just meant it could recognize the case where it is running with no internet access instead of throwing this exception and sending it to support channels. But the impact on my own development has been minimal. > CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap) > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3987 > URL: https://issues.jboss.org/browse/JBDS-3987 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central-update > Affects Versions: 9.1.0.GA > Reporter: Automated Error Reporting Bot > Assignee: Nick Boldt > Fix For: 9.1.0.GA > > Attachments: Screen Shot 2016-08-08 at 9.51.05 AM.png > > > The following problem was reported via the automated error reporting: > Message: Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.1...: null > {noformat} > org.eclipse.core.runtime.CoreException: > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.wrap(RepositoryStatusHelper.java:177) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:504) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:435) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:358) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(null:-1) > at java.util.concurrent.ThreadPoolExecutor.runWorker(null:-1) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(null:-1) > at java.lang.Thread.run(null:-1) > {noformat} > Bundles: > | org.eclipse.equinox.p2.transport.ecf | 1.1.100.v20150521-1342 | 1.1.200.v20160606-1311 | > | org.eclipse.mylyn.discovery.core | 3.7.1.v20120425-0100 | 3.20.2.v20160630-1640 | > | org.eclipse.oomph.p2.core | 1.1.0.v20150610-1534 | 1.4.0.v20160606-0856 | > | org.jboss.tools.discovery.core | 1.0.1.Final-v20160401-1059-B103 | 1.1.0.Final-v20160613-2000-B8 | > Operating Systems: > | Linux | 3.0.101 | 4.6.3.fc24 | > | MacOSX | 10.11.4 | 10.11.4 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5718e82fe4b0cd449c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Daniel Atallah (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Daniel Atallah commented on JBIDE-22578: ---------------------------------------- Sorry for the delayed response, I was out of the office for a few weeks. [~mmalina], your steps for the dynamic web project seem reasonable to me, and looks very similar to what we have. One difference (which probably isn't important) is that for the "Temporary deploy folder", we have the default {{"standalone\tmp"}} value instead of a full path. Another difference is that there are 20 or so java sub-module projects. As I mentioned earlier, this behavior doesn't happen with every publish - we can recreate it reliably by making a number of changes that cause incremental publications over a few minutes, but we haven't been able to identify a specific activity that causes the behavior. I don't think we're going to be able to come up with a simplified sample project that works differently than what you've already created. Would it be reasonable to add even more debugging (perhaps even to a unreleased test build) that we can use to provide a log with the right details to track this down? > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22965: -------------------------------------- Summary: CDK tools should work behind proxy Key: JBIDE-22965 URL: https://issues.jboss.org/browse/JBIDE-22965 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk Reporter: Alexey Kazakov Assignee: Rob Stryker Priority: Critical Fix For: 4.4.1.Final Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. We should make sure our CDK tooling supports it too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22781) Create integration tests PR check job for cdk

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22781?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22781: ---------------------------------- Fix Version/s: 4.4.1.Final > Create integration tests PR check job for cdk > --------------------------------------------- > > Key: JBIDE-22781 > URL: https://issues.jboss.org/browse/JBIDE-22781 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.4.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22886) Unknown component error when using http://xmlns.jcp.org/jsf/composite instead of http://java.sun.com/jsf/composite

by Karl Nicholas (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22886?page=com.atlassian.jira.plugi... ] Karl Nicholas commented on JBIDE-22886: --------------------------------------- I can confirm [~scabanovich] is saying. If everything is set to "java.sun.com" then it's Okay. If I change everything to "xmlns.jcp.org" then there will be a problem until I do Eclipse->Project->Clean. Then after the rebuild and revalidation there is no problems again. > Unknown component error when using http://xmlns.jcp.org/jsf/composite instead of http://java.sun.com/jsf/composite > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22886 > URL: https://issues.jboss.org/browse/JBIDE-22886 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Final > Environment: JBoss Developer Studio 9.0.1.GA. Windows 10. Java 8. > Reporter: Karl Nicholas > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: screenshot-1.png, screenshot-2.png > > > 1. Create a JSF 2.2 KickStart project with WildFly target server. > 2. Create a composite component "mycomp.xhtml" > 4. Import composite component with http://xmlns.jcp.org/jsf/composite/mycomp"> > 5. FAILURE: Unknown composite component "mycomp" in validation. > 6. change to Import composite component with http://java.sun.com/jsf/composite/mycomp"> > 7. No validation, unknown composite component warning. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016