[JBoss JIRA] (JBDS-3497) Installer randomly failing to report download statistics
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3497?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3497:
-----------------------------
Priority: Optional (was: Minor)
> Installer randomly failing to report download statistics
> --------------------------------------------------------
>
> Key: JBDS-3497
> URL: https://issues.jboss.org/browse/JBDS-3497
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: usage
> Affects Versions: 9.0.0.Beta2
> Environment: jboss-devstudio-9.0.0.Beta2-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 10.x
>
>
> In about every third attempt to install JBDS (or maybe more frequently) a p2 error log appears saying this:
> {noformat}!ENTRY org.eclipse.equinox.p2.artifact.repository 2 0 2015-08-04 08:14:33.521
> !MESSAGE Failure reporting download statistics to URL: https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9....
> !STACK 1
> org.eclipse.core.runtime.CoreException: HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:235)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.collectStats(MirrorRequest.java:268)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:235)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1
> at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> ... 1 more
> !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2015-08-04 08:14:33.522
> !MESSAGE HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt
> !STACK 1
> org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1
> at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !SUBENTRY 2 org.eclipse.ecf.identity 4 0 2015-08-04 08:14:33.522
> !MESSAGE General connection error with response code=-1 {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-3497) Installer randomly failing to report download statistics
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3497?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3497:
----------------------------------
Does this still happen with 10.x builds? You should be getting a 404 code back from the server, not a -1.
> Installer randomly failing to report download statistics
> --------------------------------------------------------
>
> Key: JBDS-3497
> URL: https://issues.jboss.org/browse/JBDS-3497
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: usage
> Affects Versions: 9.0.0.Beta2
> Environment: jboss-devstudio-9.0.0.Beta2-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 10.x
>
>
> In about every third attempt to install JBDS (or maybe more frequently) a p2 error log appears saying this:
> {noformat}!ENTRY org.eclipse.equinox.p2.artifact.repository 2 0 2015-08-04 08:14:33.521
> !MESSAGE Failure reporting download statistics to URL: https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9....
> !STACK 1
> org.eclipse.core.runtime.CoreException: HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:235)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.collectStats(MirrorRequest.java:268)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:235)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1
> at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> ... 1 more
> !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2015-08-04 08:14:33.522
> !MESSAGE HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt
> !STACK 1
> org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1
> at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !SUBENTRY 2 org.eclipse.ecf.identity 4 0 2015-08-04 08:14:33.522
> !MESSAGE General connection error with response code=-1 {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-21312) Duplicate quickstarts found in Central?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21312?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21312.
------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.5.0.AM1)
Assignee: Nick Boldt (was: Fred Bricon)
Resolution: Cannot Reproduce Bug
Cannot reproduce in Devstudio 10.2.0.GA, so closing.
> Duplicate quickstarts found in Central?
> ---------------------------------------
>
> Key: JBIDE-21312
> URL: https://issues.jboss.org/browse/JBIDE-21312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.Final
>
>
> After installing all of JBT 4.3.1.Beta1 from http://download.jboss.org/jbosstools/mars/staging/updates/ into eclipse-jee-mars-1-RC3-linux-gtk-x86_64.tar.gz, then installing all the stuff in Central (including EA content) EXCEPT JRebel and Android connectors, I see this in my console:
> {code}
> !MESSAGE Found duplicate quickstart helloworld
> !MESSAGE Found duplicate quickstart helloworld_action
> !MESSAGE Found duplicate quickstart helloworld_file_action
> !MESSAGE Found duplicate quickstart webservice_consumer1
> !MESSAGE Found duplicate quickstart webservice_producer
> !MESSAGE Found duplicate quickstart transform_CSV2XML
> !MESSAGE Found duplicate quickstart transform_XML2POJO
> !MESSAGE Found duplicate quickstart transform_XML2XML_date_manipulation
> !MESSAGE Found duplicate quickstart transform_XML2XML_simple
> {code}
> Same list appears if I install everything from https://devstudio.redhat.com/9.0/staging/updates/ into another clean Eclipse install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-3595) dark theme not nice
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3595?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3595:
-----------------------------
Component/s: (was: upstream)
> dark theme not nice
> -------------------
>
> Key: JBDS-3595
> URL: https://issues.jboss.org/browse/JBDS-3595
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.1.0.Beta2
> Reporter: Aleksandar Kostadinov
> Priority: Minor
> Fix For: 10.x
>
> Attachments: jbds_dark.png
>
>
> Selecting "Dark" them in appearance yields somehow ugly result. Would be nice to be fixed.
> !jbds_dark.png|thumbnail!
> btw have installed GoClipse, not sure if that matters. Have not checked dark theme before install.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-23647:
------------------------------------
Affects Version/s: 4.4.1.Final
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-23647:
---------------------------------------
Summary: UI freeze while trying to starting the forge runtime
Key: JBIDE-23647
URL: https://issues.jboss.org/browse/JBIDE-23647
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: Aurélien Pupier
Attachments: image-2016-12-14-18-17-34-950.png
maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
I hit Ctrl+4 and then the UI is blocked:
!image-2016-12-14-18-17-34-950.png|thumbnail!
I have this stack in logs
{noformat}
Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
SEVERE: Error occurred.
java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18983:
------------------------------------
[~clerum] Is this still a problem with JBoss Tools 4.4.1 and Eclipse 4.6.x ?
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, maven
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Fix For: 4.4.3.AM1
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-18983:
----------------------------------
Assignee: Jeff MAURY
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, maven
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Fix For: 4.4.3.AM1
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-4223) Promisify installer's detection methods
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4223:
-----------------------------------
Summary: Promisify installer's detection methods
Key: JBDS-4223
URL: https://issues.jboss.org/browse/JBDS-4223
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: platform-installer
Affects Versions: 10.3.0.AM1
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.3.0.AM1
Current implementation gets callbak to notify about detection results, method should return promise instance instead to simplify chaining and testing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4191:
----------------------------------
PR: https://github.com/jbosstools/jbosstools-discovery/pull/339
> problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM1
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months