October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20845: --------------------------------------- [~snjeza], I tried again now. And you are right, when I uncheck "Warn when unable to install breakpoint...", it will no longer complain and when I click "List Members" in the web app, it will hit the breakpoint. But there are still a few questions: 1. Why does it display the warning in the first place? It seems that the breakpoint works fine, so why is Eclipse complaining (unless you make turn off the warning)? 2. Why do I need to click the "List Members" button in the web app to trigger this when [~vpakan] allegedly didn't have to do that. Now I actually tend to think that Vlado must have had the breakpoint somewhere else, because it seems to make sense to me that the listAllMembers method is only called when you want to list the members. > Unable to install breakpoint even if line number set to be generated > -------------------------------------------------------------------- > > Key: JBIDE-20845 > URL: https://issues.jboss.org/browse/JBIDE-20845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: breakpoint-error.png, compiler-settings.png, lineNumber.png > > > I am unable to get breakpoints to work for a html5 project running on WildFly. > I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error: > Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes. > Reason: Absent Line Number Information > !breakpoint-error.png! > I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has: > org.eclipse.jdt.core.compiler.debug.lineNumber=generate > This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same. > I'm not really sure which component this should belong to, it looks like an upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-20442: ------------------------------------- Nothing from test scenarios above is implemented. I have test checking code assist for AngularJS attributes 'ng-*' but I don't know if that is coming from Tern > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21034: ----------------------------------- Summary: new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list Key: JBIDE-21034 URL: https://issues.jboss.org/browse/JBIDE-21034 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.3.0.Final Reporter: Rob Stryker Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- [~burrsutter] btw. if we could avoid having different names for this thing in community vs product that would be great - i.e. its ADB in community and CDK in product. Would be good if we could have a common name to refer to it. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-21033: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/1221 > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-21033: ------------------------------------ Summary: Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test Key: JBIDE-21033 URL: https://issues.jboss.org/browse/JBIDE-21033 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.3.0.Final Reporter: Len DiMaggio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-21033: ------------------------------------ Assignee: Len DiMaggio > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20990: ------------------------------------- Everything here is PoC for now. None of these strings are permanent until they're in a GA release... and even then I'd imagine they can be changed with some annoyance to docs team. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3551: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > User Story: > As a JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3552: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 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 October 2015