August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22439: ------------------------------------------ I mailed sonarqube.com to get an account. Awaiting reply. > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22593. -------------------------------------- Resolution: Cannot Reproduce Bug cant replicate, resolving > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23056) Change the name of the TestService contribution to 0.0.0.Test

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23056?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23056: ------------------------------ Fix Version/s: 4.4.1.Final > Change the name of the TestService contribution to 0.0.0.Test > ------------------------------------------------------------- > > Key: JBIDE-23056 > URL: https://issues.jboss.org/browse/JBIDE-23056 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM3 > Reporter: Koen Aers > Fix For: 4.4.1.Final > > > This is important because with the current name this test service comes up as the default when running an Eclipse runtime environment while the default is expected to be the highest Hibernate version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23056) Change the name of the TestService contribution to 0.0.0.Test

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23056?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-23056: --------------------------------- Story Points: 1 Sprint: devex #119 August 2016 Assignee: Koen Aers > Change the name of the TestService contribution to 0.0.0.Test > ------------------------------------------------------------- > > Key: JBIDE-23056 > URL: https://issues.jboss.org/browse/JBIDE-23056 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.1.AM3 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.1.Final > > > This is important because with the current name this test service comes up as the default when running an Eclipse runtime environment while the default is expected to be the highest Hibernate version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23056) Change the name of the TestService contribution to 0.0.0.Test

by Koen Aers (JIRA)

Koen Aers created JBIDE-23056: --------------------------------- Summary: Change the name of the TestService contribution to 0.0.0.Test Key: JBIDE-23056 URL: https://issues.jboss.org/browse/JBIDE-23056 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.1.AM3 Reporter: Koen Aers This is important because with the current name this test service comes up as the default when running an Eclipse runtime environment while the default is expected to be the highest Hibernate version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Jan Richter (JIRA)

Jan Richter created JBIDE-23055: ----------------------------------- Summary: Repeated toggling of JAX-RS support on project does not cause it to rebuild Key: JBIDE-23055 URL: https://issues.jboss.org/browse/JBIDE-23055 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.4.1.AM3 Reporter: Jan Richter When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22880) List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab

by Mikhail Kalkov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22880?page=com.atlassian.jira.plugi... ] Mikhail Kalkov commented on JBIDE-22880: ---------------------------------------- There seems to be no nightly build for DevStudio 10.0: http://tools.jboss.org/downloads/devstudio/neon/ However, if you can give me a direct link, I'll be able to verify this solution... or record a screencast. ^^ > List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22880 > URL: https://issues.jboss.org/browse/JBIDE-22880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > Attachments: test-projects.zip > > > It is impossible to select "filter by" dropdown or press "Refresh Table" on the deployment tab of ServerEditor in JBoss Developer Studio when anything is deployed. I think it should be possible to change filter configuration but do not edit the table itself. Otherwise, both "Refresh" button and some of filter options becomes useless. See Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

by Mikhail Kalkov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ] Mikhail Kalkov edited comment on JBIDE-22878 at 8/30/16 6:06 AM: ----------------------------------------------------------------- I mean that since I get JBIDE-18697 in DevStudio 8.1.0.GA (includes 4.2.3.Final) with this test-ear project it could not have been completely fixed in 4.2.1. However, I don't get that bug i 10.0.0.GA (includes 4.4.0.Final) with the same test project so it must have been fixed by now anyway. I'm testing with a stock version of DevStudio 10.0.0.GA, which has m2e-wtp installed. See a screenshot with deployment assembly properties for test-ear attached. See my copy of test-ear attached. I get this problem 100% of attempts. I actually don't mind if GUI shows wrong name as long as the end result in test-ear is correct. was (Author: mkalkov): I mean that since I get JBIDE-18697 in DevStudio 8.1.0.GA (includes 4.2.3.Final) it could not have been completely fixed in 4.2.1. However, I don't get that bug i 10.0.0.GA (includes 4.4.0.Final) so it must have been fixed by now anyway. I'm testing with a stock version of DevStudio 10.0.0.GA, which has m2e-wtp installed. See a screenshot with deployment assembly properties for test-ear attached. See my copy of test-ear attached. I get this problem 100% of attempts. I actually don't mind if GUI shows wrong name as long as the end result in test-ear is correct. > EAR deployed from DevStudio to EAP contains errorneously named ejbs > ------------------------------------------------------------------- > > Key: JBIDE-22878 > URL: https://issues.jboss.org/browse/JBIDE-22878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip > > > I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar. > When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot. > This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs

by Mikhail Kalkov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ] Mikhail Kalkov edited comment on JBIDE-22878 at 8/30/16 6:06 AM: ----------------------------------------------------------------- I mean that since I get JBIDE-18697 in DevStudio 8.1.0.GA (includes 4.2.3.Final) with this test-ear project it could not have been completely fixed in 4.2.1. However, I don't get that bug in 10.0.0.GA (includes 4.4.0.Final) with the same test project so it must have been fixed by now anyway. I'm testing with a stock version of DevStudio 10.0.0.GA, which has m2e-wtp installed. See a screenshot with deployment assembly properties for test-ear attached. See my copy of test-ear attached. I get this problem 100% of attempts. I actually don't mind if GUI shows wrong name as long as the end result in test-ear is correct. was (Author: mkalkov): I mean that since I get JBIDE-18697 in DevStudio 8.1.0.GA (includes 4.2.3.Final) with this test-ear project it could not have been completely fixed in 4.2.1. However, I don't get that bug i 10.0.0.GA (includes 4.4.0.Final) with the same test project so it must have been fixed by now anyway. I'm testing with a stock version of DevStudio 10.0.0.GA, which has m2e-wtp installed. See a screenshot with deployment assembly properties for test-ear attached. See my copy of test-ear attached. I get this problem 100% of attempts. I actually don't mind if GUI shows wrong name as long as the end result in test-ear is correct. > EAR deployed from DevStudio to EAP contains errorneously named ejbs > ------------------------------------------------------------------- > > Key: JBIDE-22878 > URL: https://issues.jboss.org/browse/JBIDE-22878 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip > > > I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar. > When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot. > This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016