标签: eclipse-luna

在我的Web应用程序中,servlet甚至在开始编写响应之前需要多秒.我想知道,在servlet执行期间调用哪些方法以及每个方法花费的时间.

是否已在Eclipse IDE for Java EE开发人员的Luna版本中包含了一个分析器？我该如何激活它？

网上有很多信息,但是接缝名称一直在变化,所以我很难过滤相关信息.

使"快速访问"搜索字段可选是Eclipse中期待已久的功能.现在,根据Eclipse Luna项目站点,这是可能的.我的问题是:我们如何删除它？我在设置或透视自定义中找不到它的选项.

我们的产品使用最新的生产就绪型SWT,3.7.2.既然当时没有人知道下一个Java版本会被调用(以及他们怎么会知道8之后是8,这就像高等数学一样),我们被迫将org.eclipse.osgi3.7.2 交换到3.10.0,这样我们现在可以支持Java 8.虽然这可能不是最好的想法,但理论上它应该可行.

当然,作为Eclipse Luna的主要搞砸,当我们启动应用程序时会出现这个"错误"(大约50%的时间,我猜):

org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true" [id=0] STARTED [STARTED] invalid
at org.eclipse.osgi.container.Module.lockStateChange(Module.java:329)
at org.eclipse.osgi.container.SystemModule.init(SystemModule.java:44)
at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:170)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:393)
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:412)
at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:936)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:319)
at org.eclipse.osgi.container.Module.doStart(Module.java:571)
at org.eclipse.osgi.container.Module.start(Module.java:439)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242)
at org.eclipse.osgi.container.Module.doStart(Module.java:571)
at org.eclipse.osgi.container.Module.start(Module.java:439) …

如果我按下Ctrl并且鼠标在方法调用上,则会打开一个菜单:

公开宣言

开放实施

打开返回类型

如果我按下Ctrl+ 单击方法调用,将考虑第一个选项(Open Declaration).

我想将这些选项的顺序更改为:

开放实施

公开宣言

打开返回类型

是否有可能实现二阶秩序？(或者以相同的顺序让它们改变,但是改为"默认"为Ctrl+ 点击是开放实施)

我知道我可以从" 窗口">"首选项">"常规">"编辑器">"文本编辑器">"超链接 "中取消选中"打开声明" ,但我希望在默认情况下将所有选项与Open Implementation一起使用.

细节

• 操作系统:Windows 7
• IDE:Eclipse Luna(4.4)

• 图片(默认):

  

我有Eclipse Luna 4.4.1和JBoss Server 7.1.问题是,当我启动服务器时,它永远不会启动,并且在很长一段时间后它会显示超时错误."JBoss无法在450秒内启动".

如何解决这个问题？

控制台显示以下输出,并在此处挂起很长时间:

12:47:54,100 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
12:47:54,438 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
12:47:54,552 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

服务器永远不会启动.我已经更改了时间设置,但它从来没有帮助.

我为Eclipse Luna安装了Oracle WebLogic Tools,现在我在启动时收到了标题中的错误.我已经在下面附上了Eclipse日志.

java.lang.NullPointerException
    at org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:48)
    at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2902)
    at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1937)
    at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:3247)
    at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2693)
    at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2857)
    at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1962)
    at org.eclipse.jdt.internal.core.JavaProject.buildStructure(JavaProject.java:464)
    at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259)
    at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:557)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
    at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
    at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1642)
    at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2329)
    at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2339)
    at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1357)
    at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1264)
    at oracle.eclipse.tools.webtier.jsf.AbstractJSFTechnologyDiscoverer.isActive(AbstractJSFTechnologyDiscoverer.java:68)
    at oracle.eclipse.tools.common.services.project.technology.DefaultTechnologyDiscoveryProvider.getActiveTechnologyDescriptors(DefaultTechnologyDiscoveryProvider.java:82)
    at oracle.eclipse.tools.common.services.project.technology.DefaultTechnologyDiscoveryProvider.getActiveTechnologies(DefaultTechnologyDiscoveryProvider.java:64)
    at oracle.eclipse.tools.common.services.project.internal.ProjectImpl.getTechnologyExtensions(ProjectImpl.java:75)
    at oracle.eclipse.tools.common.services.project.internal.ProjectImpl.getTechnologyExtensionById(ProjectImpl.java:96)
    at oracle.eclipse.tools.webtier.javawebapp.app.WebAppClassloaderResetCommand.execute(WebAppClassloaderResetCommand.java:45)
    at oracle.eclipse.tools.common.services.resources.internal.CommandSetJob.runPreLockCommands(CommandSetJob.java:211)
    at oracle.eclipse.tools.common.services.resources.internal.CommandSetJob.run(CommandSetJob.java:79)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

我创建了一个函数来过滤多个谓词,我为它们执行逻辑AND:

@SafeVarargs
public static <T> Stream<T> filter(Stream<T> source, Predicate<T>... predicates) {
    return source.filter(Arrays.stream(predicates).reduce(predicates[0], Predicate::and));
}  

致电时:

filter(IntStream.range(0, 10).boxed(), x -> x % 2 != 0, x -> x%3 == 0).forEach(System.out::println);

它工作正常并打印3和9.但是,当我传递一个谓词,如:

filter(IntStream.range(0, 10).boxed(), x -> x % 2 != 0).forEach(System.out::println);

我收到编译错误:

The target type of this expression must be a functional interface

为什么是这样？

对于infos我使用Eclipse Luna版本1.

在Eclipse Luna中更新Spring Tool Suite,因为我关闭了下载Eclipse 3.7更新的选项,因此出现以下错误:

**An error occurred while collecting items to be installed session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.springsource.ide.eclipse.commons.quicksearch,3.6.1.201408250654-RELEASE
No repository found containing: osgi.bundle,org.springsource.sts,3.6.1.201408250824-RELEASE
No repository found containing: org.eclipse.update.feature,org.springsource.ide.eclipse.commons.quicksearch.feature,3.6.1.201408250654-RELEASE
No repository found containing: org.eclipse.update.feature,org.springsource.sts,3.6.1.201408250824-RELEASE
No repository found containing: binary,org.springsource.sts.ide.executable.win32.win32.x86_64,3.6.1.201408250824-RELEASE-e43
No repository found containing: org.eclipse.update.feature,org.springsource.sts.package,3.6.1.201408250824-RELEASE-e43
No repository found containing: binary,org.springsource.sts.package_root,3.6.1.201408250824-RELEASE-e43**

我安装的版本是:

Spring Tool Suite 
Version: 3.6.0.RELEASE
Build Id: 201407101106
Platform: Eclipse Luna (4.4)**

有谁知道如何解决这一问题？

我正在使用Eclipse Luna.更新我的沙箱后,我开始在多个模块中收到以下错误消息.我应该添加API基线还是让Eclipse忽略它？

我试图整合Eclipse Luna与Gradle.

Eclipse Integration Gradle GitHub页面包含有关从更新站点安装Gradle Tooling的说明.

我按照发布(稳定)版本的说明进行操作.

在我选择了所有组件后(如下所示),我继续安装.

它没有按预期进行,并将我带到安装修复页面(下面),该页面显示只能安装Gradle IDE组件.(点击这里查看大图).

在这一点上,我不确定是什么原因导致了这个问题.