[JBoss JIRA] (JBIDE-22633) jbosstools-multiple.target has multiple incompatible IUs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22633?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22633:
------------------------------------
Output looks like this:
{code}
[WARNING] Found 10 duplicate jbdevstudio plugins:
[WARNING] [1] jbdevstudio-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar
[WARNING] [1] jbdevstudio-multiple.target.repo/plugins/com.google.guava_13.0.0.jar
[WARNING] [2] jbdevstudio-multiple.target.repo/plugins/javax.wsdl_1.5.1.v201012040544.jar
[WARNING] [2] jbdevstudio-multiple.target.repo/plugins/javax.wsdl_1.6.2.v201012040545.jar
[WARNING] [3] jbdevstudio-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201005080400.jar
[WARNING] [3] jbdevstudio-multiple.target.repo/plugins/javax.xml.rpc_1.1.0.v201209140446.jar
[WARNING] [4] jbdevstudio-multiple.target.repo/plugins/javax.xml.soap_1.3.0.v201105210645.jar
[WARNING] [4] jbdevstudio-multiple.target.repo/plugins/javax.xml.soap_1.2.0.v201005080501.jar
[WARNING] [5] jbdevstudio-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201411182030.jar
[WARNING] [5] jbdevstudio-multiple.target.repo/plugins/org.apache.axis_1.4.0.v201005080400.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar
[WARNING] [6] jbdevstudio-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201005080502.jar
[WARNING] [7] jbdevstudio-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.1.0.v20160418-1457.jar
[WARNING] [7] jbdevstudio-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.100.v20160418-1457.jar
[WARNING] [8] jbdevstudio-multiple.target.repo/plugins/org.eclipse.mylyn.wikitext.asciidoc.core_2.9.0.v20160524-1633.jar
[WARNING] [8] jbdevstudio-multiple.target.repo/plugins/org.eclipse.mylyn.wikitext.asciidoc.core_2.8.0.N20160111-1930.jar
[WARNING] [9] jbdevstudio-multiple.target.repo/plugins/org.eclipse.mylyn.wikitext.asciidoc.ui_2.9.0.v20160516-1451.jar
[WARNING] [9] jbdevstudio-multiple.target.repo/plugins/org.eclipse.mylyn.wikitext.asciidoc.ui_2.8.0.N20160111-1930.jar
[WARNING] [10] jbdevstudio-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar
[WARNING] [10] jbdevstudio-multiple.target.repo/plugins/org.objectweb.asm_4.0.0.v201302062210.jar
{code}
Problem is there's no way to identify easily which are OK dupes and which are not. I suppose I could crack open all the jars and see which are singletons...?
> jbosstools-multiple.target has multiple incompatible IUs
> --------------------------------------------------------
>
> Key: JBIDE-22633
> URL: https://issues.jboss.org/browse/JBIDE-22633
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: target-platform
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.1.AM1
>
>
> Please correct the jbosstools-multiple.target to avoid the duplication of the IU as this is causing build failures in both SwitchYard and Fuse Tooling (development).
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> org.eclipse.egit.ui.smartimport is defined twice with two different versions:
> {code}
> [ERROR] Resolution failed:
> [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2
> [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r
> [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3957) No URL set for discovery catalog in central software/update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3957?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3957:
----------------------------------
Verifying I've fixed this from build B5621...
> No URL set for discovery catalog in central software/update
> -----------------------------------------------------------
>
> Key: JBDS-3957
> URL: https://issues.jboss.org/browse/JBDS-3957
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 10.0.1.AM1
> Environment: devstudio-10.0.1.GA-v20160627-0436-B5620-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.1.AM1
>
>
> When opening the central software/update page in nightly devstudio I'm getting the following errors:
> {noformat}
> No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {noformat}
> and
> {noformat}
> Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> After that the page is basically empty (no connectors, surprisingly). Only happens in devstudio, JBT nightly works fine for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21745:
-------------------------------------
[~mmalina] Hey martin:
I just created a few email and rh-developer accounts to test this:
1) oliver+beef1(a)mail.com
2) rob+test(a)oxbeef.net
When I use the download runtime wizard, and use the redhat developer accounts, I get an error: An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 500
I've passed this on to [~dhladky] but I'd like to know if you can replicate this or if it seems to be something particular to my environment.
Thanks.
> Unable to download EAP 7 Beta runtime using username without "@redhat.com"
> --------------------------------------------------------------------------
>
> Key: JBIDE-21745
> URL: https://issues.jboss.org/browse/JBIDE-21745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Final, 4.3.1.CR1
> Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.x
>
>
> Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page.
> Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown:
> {noformat}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {noformat}
> But even after that I'm unable to download that runtime with the same credentials.
> Using login with "@redhat.com" I'm able to download the runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22578:
-------------------------------------
Sadly I'm not able to replicate this at all, even with this information!
Perhaps this is because I'm using neon and not mars. Once I set the module to have a path of "../" in the xml file, the eclipse webtools framework stops recognizing it as a child module and I never get asked to publish it.
[~mmalina] can you verify this isn't replicatable on neon?
> 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
> Priority: Blocker
> Fix For: 4.4.1.AM1
>
> Attachments: jboss_deployment.jpg, 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, 9 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3282.
----------------------------------
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: screencast
> Fix For: 10.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3282:
---------------------------------
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: screencast
> Fix For: 10.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3282:
--------------------------------
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: screencast
> Fix For: 10.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3282:
---------------------------------
Target Release: 10.0.0.GA (was: 9.1.0.GA)
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: screencast
> Fix For: 10.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months