September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-11766) Work with "Annotation Properties" view breaks JAX-RS explorer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11766?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11766: --------------------------------------------- bumping up in priority since probably more than annotation properties can cause this. > Work with "Annotation Properties" view breaks JAX-RS explorer > ------------------------------------------------------------- > > Key: JBIDE-11766 > URL: https://issues.jboss.org/browse/JBIDE-11766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.Beta3 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: report-2.ogv > > > After some random clicking on JAX-RS annotation in Annotation Properties view, JAX-RS breaks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11766) Work with "Annotation Properties" view breaks JAX-RS explorer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11766?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11766: ---------------------------------------- Priority: Critical (was: Major) > Work with "Annotation Properties" view breaks JAX-RS explorer > ------------------------------------------------------------- > > Key: JBIDE-11766 > URL: https://issues.jboss.org/browse/JBIDE-11766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.Beta3 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: report-2.ogv > > > After some random clicking on JAX-RS annotation in Annotation Properties view, JAX-RS breaks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-3141 at 9/4/14 11:06 AM: ------------------------------------------------------------ I checked importing https://github.com/victims/victims-enforcer/tree/master/sample doesn't crash. The enforcer plugin is ignored by m2e by default so the victi.ms plugin is never called during eclipse builds. Do you expect another behavior? was (Author: fbricon): I checked importing https://github.com/victims/victims-enforcer/tree/master/sample doesn't crash. The enforcer plugin is is ignored by m2e by default so the victi.ms plugin is never called during eclipse builds. Do you expect another behavior? > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3141: ----------------------------------- I checked importing https://github.com/victims/victims-enforcer/tree/master/sample doesn't crash. The enforcer plugin is is ignored by m2e by default so the victi.ms plugin is never called during eclipse builds. Do you expect another behavior? > Test victi.ms maven plugin works within jbds (or at least does not fail) > ------------------------------------------------------------------------ > > Key: JBDS-3141 > URL: https://issues.jboss.org/browse/JBDS-3141 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: maven > Reporter: Burr Sutter > > http://victi.ms has a maven plugin to check/assert maven dependencies have issues. > should check how it works and if it works within eclipse -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15482: --------------------------------------------- no progress and not seeing this happening before GA and we will have to survive until then. thus punting. > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: f2f2014 > Fix For: 4.2.x, 4.3.0.Alpha1 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15482: ---------------------------------------- Fix Version/s: 4.2.x 4.3.0.Alpha1 (was: 4.2.0.CR1) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: f2f2014 > Fix For: 4.2.x, 4.3.0.Alpha1 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15482: ---------------------------------------- Labels: f2f2014 (was: ) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: f2f2014 > Fix For: 4.2.x, 4.3.0.Alpha1 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17110) Correct failing Mylyn tests - Update to Red Deer causing test failures

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17110?page=com.atlassian.jira.plugi... ] Len DiMaggio resolved JBIDE-17110. ---------------------------------- Resolution: Done Sorry - this was solved months ago - should have been closed. > Correct failing Mylyn tests - Update to Red Deer causing test failures > ---------------------------------------------------------------------- > > Key: JBIDE-17110 > URL: https://issues.jboss.org/browse/JBIDE-17110 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR1 > > > Correct failing Mylyn tests - Update to Red Deer causing test failures > http://machydra.brq.redhat.com:8080/job/jbt-integration-tests-verificatio... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17110) Correct failing Mylyn tests - Update to Red Deer causing test failures

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17110?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-17110. -------------------------------- > Correct failing Mylyn tests - Update to Red Deer causing test failures > ---------------------------------------------------------------------- > > Key: JBIDE-17110 > URL: https://issues.jboss.org/browse/JBIDE-17110 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR1 > > > Correct failing Mylyn tests - Update to Red Deer causing test failures > http://machydra.brq.redhat.com:8080/job/jbt-integration-tests-verificatio... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-18265: ------------------------------------- Assignee: Snjezana Peco > NullPointerException in ArquillianBuilder when creating test class with the name Test > ------------------------------------------------------------------------------------- > > Key: JBIDE-18265 > URL: https://issues.jboss.org/browse/JBIDE-18265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.0.CR1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.0.CR2 > > > When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP. > {code} > java.lang.NullPointerException > at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205) > at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104) > at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862) > at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849) > at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > This is because the test method is generated with the @Test annotation without fully qualified name. > {code} > @Test > public void test() { > fail("Not yet implemented"); > } > {code} > In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name > {code} > @Test > @org.junit.Test > public void test() { > fail("Not yet implemented"); > } > {code} > However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014