September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18153) For JBIDE 4.2.0.CR1: Code Freeze + Branch [JBT Update Sites]

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18153?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18153. ------------------------------ I suppose this was done. Closing. > For JBIDE 4.2.0.CR1: Code Freeze + Branch [JBT Update Sites] > ------------------------------------------------------------ > > Key: JBIDE-18153 > URL: https://issues.jboss.org/browse/JBIDE-18153 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [JBT Update Sites]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JBT Update Sites task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18154) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18154?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18154. ------------------------------ I suppose this was done. Closing. > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery] > ------------------------------------------------------------- > > Key: JBIDE-18154 > URL: https://issues.jboss.org/browse/JBIDE-18154 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: discovery > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Central Discovery]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18195) Arquillian New and Noteworthy for 4.2.0.CR1

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18195?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-18195. ----------------------------------- Closing the issue. > Arquillian New and Noteworthy for 4.2.0.CR1 > ------------------------------------------- > > Key: JBIDE-18195 > URL: https://issues.jboss.org/browse/JBIDE-18195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.0.CR1 > > > 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 Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18224) Table Selection has poor performance if "Verify Database Connection" is checked in previous step

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18224?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18224: ---------------------------------------- Fix Version/s: 4.2.0.CR2 4.3.0.Alpha1 (was: 4.2.0.CR1) > Table Selection has poor performance if "Verify Database Connection" is checked in previous step > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18224 > URL: https://issues.jboss.org/browse/JBIDE-18224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR2, 4.3.0.Alpha1 > > > If the "Verify Database Connection" *is checked* then there is very *poor performance* in the next step during tables selection on JPA: Generate Entities From Tables wizard. > I don't understand what is going on behind the scenes - but there is for sure some communication with DB happening. Not sure if this is necessary as the list of tables is read correctly and imho the list should be just checked if there is at least one table selected. > It works *without performance problems* if "Verify Database Connection" was *not checked* in previous step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18254) Change in remote server's config dir is not reflected in the launch command

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18254?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18254: ---------------------------------- Steps to Reproduce: 1. Create a remote EAP 6 / AS 7 / WildFly 8 server 2. Open server editor, change Remote Server Base Directory to something other than the default "standalone" 3. Start the server / check the launch command used in launch config - you will see that the new dir is used to set up logging, but not for the standalone.xml config - that still only has --server-config=standalone.xml was: 1. Create a remote EAP 6 / AS 7 / WildFly 8 server 2. Open server editor, change Remote Server Base Directory to something other than the default "standalone" 3. Start the server / check the launch command used in launch config - you will see that the new dir is used to set up logging, but not for the standalone.xml config - that still only has --config=standalone.xml > Change in remote server's config dir is not reflected in the launch command > --------------------------------------------------------------------------- > > Key: JBIDE-18254 > URL: https://issues.jboss.org/browse/JBIDE-18254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > When you create a remote server and then change the Remote Server Base Directory from standalone to something else, this change is not reflected in the config= setting in the launch command. > This may apply to local servers as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16898) no error handling for nonexisting remote home

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16898?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16898: --------------------------------------- [~maxandersen] I changed "Remote Server Base Directory" in server config to something other than "standalone". OK, you're right it's a separate issue. Here: JBIDE-18254 But this jira still deserves to be reopened because it does not work the way Rob said it would (remote dir validation). > no error handling for nonexisting remote home > --------------------------------------------- > > Key: JBIDE-16898 > URL: https://issues.jboss.org/browse/JBIDE-16898 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Downloaded EAP 6.2 via downlod runtimes. > configured it to use remote, entered in bogus name for home folder. > This is in the console log: > "/> > /> > Error: Unable to access jarfile urft/jboss-modules.jar > JBTOOLS_SERVER_START_CMD:JBoss Enterprise Application Platform 6.1+1395830330282:11785 > />" > I would have expected some validation or better info in the console on what users should do now. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18254) Change in remote server's config dir is not reflected in the launch command

by Martin Malina (JIRA)

Martin Malina created JBIDE-18254: ------------------------------------- Summary: Change in remote server's config dir is not reflected in the launch command Key: JBIDE-18254 URL: https://issues.jboss.org/browse/JBIDE-18254 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.CR2 When you create a remote server and then change the Remote Server Base Directory from standalone to something else, this change is not reflected in the config= setting in the launch command. This may apply to local servers as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18225) Jenkins build unstable, failing unit tests

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18225?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18225: ---------------------------------------- Assignee: Rob Stryker > Jenkins build unstable, failing unit tests > ------------------------------------------ > > Key: JBIDE-18225 > URL: https://issues.jboss.org/browse/JBIDE-18225 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR1 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.2... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18240) Show in Forge Console should ask to start forge if forge is not started

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18240?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18240: --------------------------------------------- not a blocker/priority for CR1 IMO. moving off. > Show in Forge Console should ask to start forge if forge is not started > ----------------------------------------------------------------------- > > Key: JBIDE-18240 > URL: https://issues.jboss.org/browse/JBIDE-18240 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18240) Show in Forge Console should ask to start forge if forge is not started

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18240?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18240: ---------------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 (was: 4.2.0.CR1) > Show in Forge Console should ask to start forge if forge is not started > ----------------------------------------------------------------------- > > Key: JBIDE-18240 > URL: https://issues.jboss.org/browse/JBIDE-18240 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > -- 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