[JBoss JIRA] (JBIDE-18494) Importing EAP "jboss-logging" quickstart raises errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18494?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18494:
-------------------------------------
So jboss-logging for 6.4.0.GA, which is fixed, shows up in Central now, but also does the one for 6.3.0.GA.
BTW both appear in http://www.jboss.org/developer-materials/#!sys_type=jbossdeveloper_quicks...
I've added product/version tags in Central to distinguish them (cc [~burrsutter]) :
!http://content.screencast.com/users/fbricon/folders/Jing/media/8ec3aaff-bad5-4462-817e-1f3812d27435/00000105.png|width=700px!
> Importing EAP "jboss-logging" quickstart raises errors
> ------------------------------------------------------
>
> Key: JBIDE-18494
> URL: https://issues.jboss.org/browse/JBIDE-18494
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects - select the quickstart
> The error raised is:
> The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path home.jsp /jboss-logging/src/main/webapp line 1 JSP Problem
> (This can be fixed by adding Maven Managed Dependencies to the Java Build path)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17836) Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17836?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17836:
----------------------------------
Attachment: jbide17836.zip
> Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17836
> URL: https://issues.jboss.org/browse/JBIDE-17836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide-17836.patch, jbide17836.zip, screencast.ogv
>
>
> When I have JBOSS_AS_REMOTE_7.X profile selected in the launch configuration and I deselect it and select some other profile, the following error is logged in error log:
> {code}
> /home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist
> Java Model Exception: Java Model Status [/home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getUnderlyingResource(JarPackageFragmentRoot.java:215)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder_(PackageFragmentRootTools.java:82)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder(PackageFragmentRootTools.java:74)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:65)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:80)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.next(FilteringIterator.java:68)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath_(SimpleJavaResourceLocator.java:144)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath(SimpleJavaResourceLocator.java:135)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.MavenResourceLocator.getWorkspacePath(MavenResourceLocator.java:137)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.getPersistenceXml(JpaProjectConfigurator.java:119)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:92)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:304)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:286)
> at org.eclipse.m2e.profiles.core.internal.management.ProfileManager.updateActiveProfiles(ProfileManager.java:87)
> at org.eclipse.m2e.profiles.ui.internal.actions.ProfileSelectionHandler$UpdateProfilesJob.runInWorkspace(ProfileSelectionHandler.java:319)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17836) Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17836?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-17836:
---------------------------------------
It can be reproduced by importing the attached project into JBT and following the steps above in the description.
> Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17836
> URL: https://issues.jboss.org/browse/JBIDE-17836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide-17836.patch, screencast.ogv
>
>
> When I have JBOSS_AS_REMOTE_7.X profile selected in the launch configuration and I deselect it and select some other profile, the following error is logged in error log:
> {code}
> /home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist
> Java Model Exception: Java Model Status [/home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getUnderlyingResource(JarPackageFragmentRoot.java:215)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder_(PackageFragmentRootTools.java:82)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder(PackageFragmentRootTools.java:74)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:65)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:80)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.next(FilteringIterator.java:68)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath_(SimpleJavaResourceLocator.java:144)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath(SimpleJavaResourceLocator.java:135)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.MavenResourceLocator.getWorkspacePath(MavenResourceLocator.java:137)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.getPersistenceXml(JpaProjectConfigurator.java:119)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:92)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:304)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:286)
> at org.eclipse.m2e.profiles.core.internal.management.ProfileManager.updateActiveProfiles(ProfileManager.java:87)
> at org.eclipse.m2e.profiles.ui.internal.actions.ProfileSelectionHandler$UpdateProfilesJob.runInWorkspace(ProfileSelectionHandler.java:319)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19757:
------------------------------------
Versioning the symlink is entirely possible, and we do it today. Here are 3 versions of symlinks for mars and luna:
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/jbosstoo... [tag]
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/jbosstoo... [branch]
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/jbosstoo... [branch]
Hard to maintain? Well, as I said, it's 1 file vs. 2. I've done both approaches and have chosen the one I prefer. You don't have to worry about the maintenance of the link (be it composite or sym). The ONLY reason to use composite (with higher maintenance cost) vs. symlink is, as I said, above:
{quote}
If you can prove there's performance gain by using a composite instead of a symlink, then I will agree with you that your approach is better than mine.
{quote}
Want to convince me? Use science to prove your opinion. :D
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19542?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19542:
-------------------------------------
I'd only make org.jboss.tools.common.mylyn.feature depend on the feature providing JIRA
> Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19542
> URL: https://issues.jboss.org/browse/JBIDE-19542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Minor
>
> Steps to recreate the error:
> * Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz)
> * Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/)
> * Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group)
> * Whenever eclipse is started, this error is written to the .log
> ============================================================================
> cat .log
> !SESSION 2015-03-31 14:33:50.481 -----------------------------------------------
> eclipse.buildId=4.4.2.M20150204-1700
> java.version=1.7.0_55
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> ============================================================================
> Workaround:
> * From JBoss Central, install: "Mylyn Issue Tracker Connectors"
> * This results in the following packages being installed
> * Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group
> * Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group
> * Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group
> * Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group
> * Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group
> * Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group
> * Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group
> * Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group
> * Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group
> After installing this^, the error is not generated
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19756:
------------------------------------
{quote}Why do you want to have jbds use local sources and not same as jbosstools ? {quote}
Because no github auth is therefore required and the JBDS sources are ALREADY on disk (unlike for the JBT build, where they're all upstream in the 17 projects' builds). Why fetch them from github when they're already available locally? #performanceImprovement #simplerApproach
{quote} And why is it a problem to have you as user access jbdevstudio ? you can't run these builds if you dont have the access.{quote}
The big reason we started providing a zip of JBDS sources was so that customers could build it. If we make it buildable only for those with VPN (eg., to pull in EAP or upstream files like devstudio-earlyacccess.properties) or github auth access (to fetch a copy of the sources already on disk from the jbdevstudio-product repo, after authenticating), we break that "API contract" we put in place for JBDS 7. Ref: JBDS-2456
Today you CAN build JBDS without having access to jbdevstudio-product. You just need the installer-src.zip and you can build everything locally. Why would we break change that to make it harder?
> jbosstools-src.zip has incomplete/misleading version info in folder names/structure
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19756
> URL: https://issues.jboss.org/browse/JBIDE-19756
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide19756.png, jbide19756_jbds-sources-zip.png, jbide19756_new_subfolders_and_zipfile_name.png
>
>
> Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named:
> <componentname>_<buildqualifier>_<sha1>
> example:
> jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad
> A few issues with this:
> a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ?
> b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19542?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19542:
-----------------------------------
Assignee: Nick Boldt
> Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19542
> URL: https://issues.jboss.org/browse/JBIDE-19542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Minor
>
> Steps to recreate the error:
> * Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz)
> * Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/)
> * Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group)
> * Whenever eclipse is started, this error is written to the .log
> ============================================================================
> cat .log
> !SESSION 2015-03-31 14:33:50.481 -----------------------------------------------
> eclipse.buildId=4.4.2.M20150204-1700
> java.version=1.7.0_55
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> ============================================================================
> Workaround:
> * From JBoss Central, install: "Mylyn Issue Tracker Connectors"
> * This results in the following packages being installed
> * Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group
> * Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group
> * Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group
> * Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group
> * Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group
> * Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group
> * Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group
> * Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group
> * Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group
> After installing this^, the error is not generated
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months