[JBoss JIRA] (JBIDE-22964) Fuse examples are found even though Fuse is not installed (and is not available in Central)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22964?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-22964:
-------------------------------
Description:
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.
was:
After turning Early Access on, camel, fuse, brms examples can be looked up 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.
> 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
[JBoss JIRA] (JBIDE-22964) Fuse examples are found even though Fuse is not installed (and is not available in Central)
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-22964:
----------------------------------
Summary: 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 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
[JBoss JIRA] (JBIDE-22651) No favicons for credentials domains on Mac or Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22651?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22651.
---------------------------------
Verified in devstudio-10.1.0.AM3-v20160808-1833-B5724-installer-standalone.jar on both mac and windows.
> No favicons for credentials domains on Mac or Windows
> -----------------------------------------------------
>
> Key: JBIDE-22651
> URL: https://issues.jboss.org/browse/JBIDE-22651
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM3
>
>
> Supposedly there should be favicons displayed for our jboss.org and redhat.com domains in the credentials preferences:
> Preferences -> JBoss Tools -> Credentials
> I only noticed this problem after reviewing JBIDE-22468 . And [~jkopriva] just showed me on his Linux box that he has the icons there. I don't have any icons on Mac or Windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3983:
-------------------------------------
In Windows I found two ways to configure proxy settings:
1. In Network Settings
2. In Internet settings
The differences between those two proxy settings:
* (2) supports PAC (Proxy Automatic Configuration) script to configure proxy and applies to requests inside browsers;
* Network level settings for all network traffic (?)
DevSuite currently use two different frameworks to send HTTP requests:
1. Angular $http service to check for T&C's status for user with provided credentials;
2. node-request module to download binaries and report progress during install;
$http service (1) uses windows Internet Settings and probably Network Settings as well.
node-request uses only Network settings.
Would be good to make installer using only angular $http service, but this approach has problems with download progress reporting.
> Development Suite Installer should work behind proxy
> ----------------------------------------------------
>
> Key: JBDS-3983
> URL: https://issues.jboss.org/browse/JBDS-3983
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings.
> CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-827) Update site for JBDS-IS 9.0.1.GA-EA still refers to JBDS-IS 9.0.1.CR2-EA
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-827?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-827.
-----------------------------------
Verified
> Update site for JBDS-IS 9.0.1.GA-EA still refers to JBDS-IS 9.0.1.CR2-EA
> ------------------------------------------------------------------------
>
> Key: JBTIS-827
> URL: https://issues.jboss.org/browse/JBTIS-827
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 9.0.1.GA
>
>
> The composite files are not consistent
> {code:title=compositeArtifacts.xml}
> <children size='2'>
> <!-- IS ONLY -->
> <child location='../9.0.1.GA/earlyaccess/'/>
> <child location='../9.0.1.GA/earlyaccess/targetplatform/'/>
> </children>
> {code}
> {code:title=compositeContent.xml}
> <children size='2'>
> <!-- IS ONLY -->
> <child location='../9.0.1.CR3/earlyaccess/'/>
> <child location='../9.0.1.CR3/earlyaccess/targetplatform/'/>
> </children>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22578:
-----------------------------------
Priority: Major (was: Blocker)
> 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
[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3983:
-------------------------------------
FYI: [~lalatendum], [~akazakov]
> Development Suite Installer should work behind proxy
> ----------------------------------------------------
>
> Key: JBDS-3983
> URL: https://issues.jboss.org/browse/JBDS-3983
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings.
> CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3983:
--------------------------------
Description:
DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings.
CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
was:
DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings.
CDK also requires proxy to be configured to have vagrant up working after installation.
> Development Suite Installer should work behind proxy
> ----------------------------------------------------
>
> Key: JBDS-3983
> URL: https://issues.jboss.org/browse/JBDS-3983
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings.
> CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months