September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15341) use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15341?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15341. ----------------------------------------- Resolution: Done marking as resolved. > use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final > -------------------------------------------------------------------------------------- > > Key: JBIDE-15341 > URL: https://issues.jboss.org/browse/JBIDE-15341 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha1 > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release BPEL tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6010) Tooling Support for Byteman Rule Injection

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6010?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-6010: -------------------------------------------- Masao, As Andrew writes, show the source. Simplest is you create a repository on github and give a link and we can see/try it out. btw. have you compared/tried it with the work done in BYTEMAN-29 which is at https://github.com/adinn/byteman-eclipse-prototype ? > Tooling Support for Byteman Rule Injection > ------------------------------------------ > > Key: JBIDE-6010 > URL: https://issues.jboss.org/browse/JBIDE-6010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: z - Legacy - integration > Reporter: Andrew Dinn > Labels: integration > Fix For: LATER > > > It would be nice to have support for Byteman in these areas: > 1) editor support for creation and modification of Byteman rule files > 2) debugger support for detection of successful or ailed rule injection at runtime > 3) debugger support for stepping through injected rule code > the byteman agent already runs a listener which provides the info required for ii. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2743) Latest target platform for a given eclipse stream should be a composite site under /targetplatforms/<project>/<eclipse-version> not /updates/<eclipse-version>/<project>/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2743?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2743 at 9/6/13 9:18 AM: ---------------------------------------------------------- The following pages have been created: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/juno/ http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/kepler/ The following pages have been updated to point to the new content in /targetplatforms/: http://download.jboss.org/jbosstools/updates/juno/ http://download.jboss.org/jbosstools/updates/kepler/ http://download.jboss.org/jbosstools/updates/kepler/integration-stack/ This doc has been updated: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... was (Author: nickboldt): The following pages have been created: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/juno/ http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/kepler/ The following pages have been updated to point to the new content in /targetplatforms/*/*/: http://download.jboss.org/jbosstools/updates/juno/ http://download.jboss.org/jbosstools/updates/kepler/ http://download.jboss.org/jbosstools/updates/kepler/integration-stack/ This doc has been updated: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... > Latest target platform for a given eclipse stream should be a composite site under /targetplatforms/<project>/<eclipse-version> not /updates/<eclipse-version>/<project>/ > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2743 > URL: https://issues.jboss.org/browse/JBDS-2743 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > > Traditionally, we have hosted the update site w/ the dependencies needed to install JBT here: > http://download.jboss.org/jbosstools/updates/indigo/ (composites) > http://download.jboss.org/jbosstools/updates/indigo/soa-tooling/ (composites) > http://download.jboss.org/jbosstools/updates/juno/ (target platform) > http://download.jboss.org/jbosstools/updates/juno/integration-stack/ (composites) > http://download.jboss.org/jbosstools/updates/kepler/ (target platform) > http://download.jboss.org/jbosstools/updates/kepler/integration-stack (target platform) > Now that we have all the target platforms in one place, under http://download.jboss.org/jbosstools/targetplatforms/ I think it would make sense to change "the latest TP" composite under /updates/<eclipse version>/ to instead exist under > /targetplatforms/<project>/<eclipse-version> > eg., > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/kep... > or > http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/kepler/ > That way all the TPs live under /targetplatforms/ and all the update sites live under /updates/ and never the twain shall meet. > Thoughts? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15455) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Freemarker]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15455?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15455: ------------------------------------ Job disabled w/ comment in header: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Freemarker] > --------------------------------------------------------- > > Key: JBIDE-15455 > URL: https://issues.jboss.org/browse/JBIDE-15455 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Freemarker] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-161: ---------------------------------- I was able to install JBDS 7, then Spring IDE 3.3 from Central, then FUSE 7.2 H61 from http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... I can't speak to whether it was FULLY FUNCTIONAL, co-installation was possible. > Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? > -------------------------------------------------------------------------- > > Key: JBTIS-161 > URL: https://issues.jboss.org/browse/JBTIS-161 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2 > Reporter: Nick Boldt > > The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. > [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... > However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). > Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15420) Project Examples New and Noteworthy for 4.1.1.Alpha1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15420?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-15420. ------------------------------- Resolution: Rejected Nothing new here > Project Examples New and Noteworthy for 4.1.1.Alpha1 > ---------------------------------------------------- > > Key: JBIDE-15420 > URL: https://issues.jboss.org/browse/JBIDE-15420 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Project Examples is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Project Examples by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15417) Maven New and Noteworthy for 4.1.1.Alpha1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15417?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-15417. ------------------------------- Resolution: Rejected Nothing new here > Maven New and Noteworthy for 4.1.1.Alpha1 > ----------------------------------------- > > Key: JBIDE-15417 > URL: https://issues.jboss.org/browse/JBIDE-15417 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Maven is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Maven by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15426) JBoss Central New and Noteworthy for 4.1.1.Alpha1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15426?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-15426. ------------------------------- Resolution: Rejected Nothing new here > JBoss Central New and Noteworthy for 4.1.1.Alpha1 > ------------------------------------------------- > > Key: JBIDE-15426 > URL: https://issues.jboss.org/browse/JBIDE-15426 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-15304: ------------------------------------- Assignee: Xavier Coulon > 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 > Assignee: Xavier Coulon > Fix For: 4.1.1.Alpha2 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15428) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15428?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15428: ---------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: 4.1.1.Alpha1) > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15428 > URL: https://issues.jboss.org/browse/JBIDE-15428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Fix For: 4.1.1.Alpha2 > > Attachments: After import.png, After workaround.png, Before import.png > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013