[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-15304:
-------------------------------------
Summary: NullPointerExceptions in JAX-RS doesn't report what project is affected
Key: JBIDE-15304
URL: https://issues.jboss.org/browse/JBIDE-15304
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 4.1.0.Final
Reporter: Denis Golovin
I've seen this exception happens many times when I have several projects imported out of JBoss Central:
{code}java.lang.NullPointerException
at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105)
at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674)
at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69)
at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672)
at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524)
at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788)
at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247)
at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126)
at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108)
at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87)
at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178)
at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114)
at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136)
at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105)
at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406)
at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173)
{code}
couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ]
Lars Heinemann commented on JBIDE-15301:
----------------------------------------
Fuse Plugins for Eclipse uses those dependencies. I need to find out why we have Red Hat specific build for aries and camel. Those come from Fuse build. Let me check whats up and I will come back with more information tomorrow as Paul is currently not available.
> Locus 1.0.0.Final contains some unwanted jars
> ---------------------------------------------
>
> Key: JBIDE-15301
> URL: https://issues.jboss.org/browse/JBIDE-15301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: locus
> Affects Versions: 1.0.0-LOCUS
> Reporter: Mickael Istria
> Assignee: Paul Leacu
> Priority: Critical
> Fix For: 1.0.1-LOCUS
>
>
> Locus contains some jars that are against Locus rules because:
> * They are SNAPSHOTs
> * They are -redhat- build.
> Instead, it should be public releases only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBTIS-118) Inclusion of Aries plugins in Locus causing console errors
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBTIS-118?page=com.atlassian.jira.plugin.... ]
Paul Richardson commented on JBTIS-118:
---------------------------------------
Messages still appear, when using Locus 1.0.0.Final-B31.
Investigation shows that installing [aries.jmx.core|http://download.jboss.org/jbosstools/updates/integration/l...] and [aries.blueprint|http://download.jboss.org/jbosstools/updates/integration/...] in a new eclipse installation and workspace causes [osgi.enterprise_4.2|http://download.jboss.org/jbosstools/updates/requirem...] to also be installed, presumably because the installer is clever enough to try and satisfy 'Imported Package' requirements of plugins. osgi.enterprise exports the relevant packages hence is installed as an implicit dependency.
However, using JBT-IS as a TP must skip this particular step hence anyone developing with JBT-IS as their TP will see these errors.
To mitigate, it should just require osgi.enterprise to be included in the base target definition. This, I have successfully tested by adding this to teiid designer's target:
{code}
<!-- Implementation of osgi 4.2 specification -->
<location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
<unit id="osgi.enterprise" version="4.2.0.v201108120515"/>
<repository location="http://download.jboss.org/jbosstools/updates/requirements/kepler/20130626..."/>
</location>
{code}
In a similar manner, I note that the felix plugins are also complaining about missing a service:
{code}
!SUBENTRY 2 org.apache.felix.configadmin 2 0 2013-07-29 16:53:08.750
!MESSAGE Missing required capability Require-Capability: service-reference; filter="(objectClass=org.osgi.service.log.LogService)".
{code}
So I would imagine another plugin should be included from the requirements repository to fix this as well.
> Inclusion of Aries plugins in Locus causing console errors
> ----------------------------------------------------------
>
> Key: JBTIS-118
> URL: https://issues.jboss.org/browse/JBTIS-118
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.0.Final
> Reporter: Paul Richardson
> Assignee: Paul Leacu
>
> Errors generated in the console when executing Eclipse IDE based on JBT-IS base.target target platform. This occurred while executing Teiid Designer, which makes no use of the Aries plugins.
> {code}
> !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.174
> !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.175
> !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT.jar was not resolved.
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175
> !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.175
> !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.176
> !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.177
> !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0).
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.177
> !MESSAGE Bundle reference:file:/home/phantomjinx/programming/java/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.apache.felix.configadmin_1.4.0.redhat-610-SNAPSHOT.jar was not resolved.
> !SUBENTRY 2 org.apache.felix.configadmin 2 0 2013-07-25 15:15:59.177
> !MESSAGE Missing required capability Require-Capability: service-reference; filter="(objectClass=org.osgi.service.log.LogService)".
> !ENTRY org.eclipse.osgi 2 0 2013-07-25 15:15:59.280
> !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2013-07-25 15:15:59.281
> !MESSAGE Bundle org.apache.aries.jmx.core_1.0.1.redhat-610-SNAPSHOT [89] was not resolved.
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.281
> !MESSAGE Missing imported package org.osgi.jmx_[1.0.0,2.0.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282
> !MESSAGE Missing imported package org.osgi.jmx.framework_[1.5.0,1.6.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.282
> !MESSAGE Missing imported package org.osgi.jmx.service.cm_[1.3.0,1.4.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283
> !MESSAGE Missing imported package org.osgi.jmx.service.permissionadmin_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.283
> !MESSAGE Missing imported package org.osgi.jmx.service.provisioning_[1.2.0,1.3.0).
> !SUBENTRY 2 org.apache.aries.jmx.core 2 0 2013-07-25 15:15:59.284
> !MESSAGE Missing imported package org.osgi.jmx.service.useradmin_[1.1.0,1.2.0).
> {code}
> Understand that Fuse is the main beneficiary of these plugins. Are the Aries plugins essential to the Fuse project (or any other projects)?
> The missing imports all relate to the osgi jmx specification, which is implemented by the [Eclipse Gemini|http://eclipse.org/gemini] project. Can / should its plugins be included to satisfy the import errors or does Fuse rely on another implementation?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-15301) Locus 1.0.0.Final contains some unwanted jars
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15301?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-15301:
-------------------------------------------
Assignee: Paul Leacu (was: Mickael Istria)
afaics its not [~phantomjinx] asking for these dependencies, but [~pleacu] and [~lhein].
The two issues I got with what is suggested / in locus now is primarily figuring out why we got -snapshot builds (we can't, at least not in a 1.0.0.final) and finally why they are coming from redhat internal/fuse specific builds and why we need custom builds for these ?
> Locus 1.0.0.Final contains some unwanted jars
> ---------------------------------------------
>
> Key: JBIDE-15301
> URL: https://issues.jboss.org/browse/JBIDE-15301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: locus
> Affects Versions: 1.0.0-LOCUS
> Reporter: Mickael Istria
> Assignee: Paul Leacu
> Priority: Critical
> Fix For: 1.0.1-LOCUS
>
>
> Locus contains some jars that are against Locus rules because:
> * They are SNAPSHOTs
> * They are -redhat- build.
> Instead, it should be public releases only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months