December 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3279) Screencasts: Maven

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-3279: -------------------------------- Assignee: Fred Bricon > Screencasts: Maven > ------------------ > > Key: JBDS-3279 > URL: https://issues.jboss.org/browse/JBDS-3279 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, maven > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.x > > > As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow. > Use cases include: > - creation of a new project and its pom.xml, with the pom.xml editor > - dependencies adds/removes > - Import maven projects - from a SVN or Git repo > - multi-module maven projects > - run on server > - package vs install > - update - the magic "update project" that helps get Eclipse and Maven back into agreement > - adjust profiles - address the Arquillian profile -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3292) https://devstudio.jboss.com/updates/8.0/ needs 8.0.1 release notes link

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3292?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3292. ---------------------------- Fix Version/s: 8.0.1.GA Resolution: Done PR merged. Also updated links to the blog announcement so they ref the 8.0.1 blog instead of the 8.0.0 one. > https://devstudio.jboss.com/updates/8.0/ needs 8.0.1 release notes link > ----------------------------------------------------------------------- > > Key: JBDS-3292 > URL: https://issues.jboss.org/browse/JBDS-3292 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: website > Affects Versions: 8.0.1.GA > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 8.0.1.GA > > > Now that 8.0.1.GA is released, https://devstudio.jboss.com/updates/8.0/ is mostly updated for that. But one thing was omitted - the release notes link on the right points to 8.0.0 release notes. > It needs this link: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18964) Changing bean discovery mode doesn't run validation for existing beans

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-18964 at 12/16/14 1:26 PM: ------------------------------------------------------------------------- CDI Core builder checks discovery mode change: {code} //5.2.a Update bean discovery mode. if(updateBeanDiscoveryMode()) { kind = FULL_BUILD; } {code} and does full build when it happens. Validator, however, starts with incremental build and has to detect that bean mode changed since previous validation. Current mode can be obtained as {code} CDICoreNature.getBeanDiscoveryMode() {code} Can validator be stateful, to keep last value of mode and compare it to the current one? Alternatively, we can add to CDI model methods {code} boolean isFullValidationRequired(); void setFullValidationRequired(boolean b); {code} This will be of use when CDI builder for any reason decides that validation should be full. CDI validator, when doing by this hint full validation, will return that property to false. was (Author: scabanovich): CDI Core builder checks discovery mode change: {code} //5.2.a Update bean discovery mode. if(updateBeanDiscoveryMode()) { kind = FULL_BUILD; } {code} and does full build when it happens. Validator, however, starts with incremental build and has to detect that bean mode changed since previous validation. Current mode can be obtained as {code} CDICoreNature.getBeanDiscoveryMode() {code} Can validator be stateful, to keep last value of mode and compare it to the current one? > Changing bean discovery mode doesn't run validation for existing beans > ---------------------------------------------------------------------- > > Key: JBIDE-18964 > URL: https://issues.jboss.org/browse/JBIDE-18964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final, 4.2.1.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18964) Changing bean discovery mode doesn't run validation for existing beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18964: ---------------------------------------- We could keep the last used mode in the validation context (which is persistent) but we should be very careful if we run full validation instead of incremental to avoid performance problems. We mast to make sure the full validation is invoked only once. > Changing bean discovery mode doesn't run validation for existing beans > ---------------------------------------------------------------------- > > Key: JBIDE-18964 > URL: https://issues.jboss.org/browse/JBIDE-18964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final, 4.2.1.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18964) Changing bean discovery mode doesn't run validation for existing beans

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-18964: ----------------------------------------------- CDI Core builder checks discovery mode change: {code} //5.2.a Update bean discovery mode. if(updateBeanDiscoveryMode()) { kind = FULL_BUILD; } {code} and does full build when it happens. Validator, however, starts with incremental build and has to detect that bean mode changed since previous validation. Current mode can be obtained as {code} CDICoreNature.getBeanDiscoveryMode() {code} Can validator be stateful, to keep last value of mode and compare it to the current one? > Changing bean discovery mode doesn't run validation for existing beans > ---------------------------------------------------------------------- > > Key: JBIDE-18964 > URL: https://issues.jboss.org/browse/JBIDE-18964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.2.0.Final, 4.2.1.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18650: ----------------------------------- Fix Version/s: (was: 4.2.2.Final) There is a separate issue for 4.2.2 - JBIDE-18905 > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: jbds 8.0.0.CR1 > [selrahal@fedora20 jbdevstudio]$ uname -a > Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > [selrahal@fedora20 jbdevstudio]$ java -version > java version "1.7.0_65" > OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Reporter: Salem Elrahal > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > > I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18905) Forge wizard window isn't focused after command selection (CTRL-4)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18905?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18905: ----------------------------------- Affects Version/s: 4.2.0.CR1 > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18905 > URL: https://issues.jboss.org/browse/JBIDE-18905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3289: ------------------------------ Fix Version/s: 8.0.2.GA > JBoss Central proxy wizards need to recognize early access. > ----------------------------------------------------------- > > Key: JBDS-3289 > URL: https://issues.jboss.org/browse/JBDS-3289 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Fred Bricon > Priority: Blocker > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18650) Forge wizard window isn't focused after command selection (CTRL-4)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18650?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-18650: ------------------------------------ Fix Version/s: 4.2.2.Final > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18650 > URL: https://issues.jboss.org/browse/JBIDE-18650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Environment: jbds 8.0.0.CR1 > [selrahal@fedora20 jbdevstudio]$ uname -a > Linux fedora20 3.15.10-201.fc20.x86_64 #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > [selrahal@fedora20 jbdevstudio]$ java -version > java version "1.7.0_65" > OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17) > OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) > Reporter: Salem Elrahal > Assignee: Koen Aers > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > I have created a new project and used forge to add a JPA entity. I select the class, use ctrl+4 to bring up the forge 2 UI, and select 'JPA: New Field'. The new window pops up but is not in focus. I have to then click on the window to enter the field name etc... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18905) Forge wizard window isn't focused after command selection (CTRL-4)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18905?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18905: ---------------------------------------- [~koen.aers] +1 to merge. > Forge wizard window isn't focused after command selection (CTRL-4) > ------------------------------------------------------------------ > > Key: JBIDE-18905 > URL: https://issues.jboss.org/browse/JBIDE-18905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 December 2014