[JBoss JIRA] (JBIDE-22046) add aeri for jboss tools
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22046?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-22046.
------------------------------------
verified on JBT and Devstudio nightly
> add aeri for jboss tools
> ------------------------
>
> Key: JBIDE-22046
> URL: https://issues.jboss.org/browse/JBIDE-22046
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aeri
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha1
>
>
> We have the possibility to get at test environment for error reporting for JBoss Tools.
> For that we need Mars.2 (pre-Mars.2 will not work) and the latest aeri.
> Thus we can't add it by default to i.e. usage (unless we want to force upgrade everyone), but we can at least include it in the default set.
> In Neon we can add to usage.
> jira here is to capture this + implement the extension point.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22501:
---------------------------------------
So after IDE restart, I was able to launch cdk. Now I tried to stop and start again and once again it's stuck on Starting..
> CDK stuck on Starting... after launch
> -------------------------------------
>
> Key: JBIDE-22501
> URL: https://issues.jboss.org/browse/JBIDE-22501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this.
> This is what I did today (verifying JBDS-3739):
> 1. Start my Eclipse Neon RC2
> 2. Updated Eclipse
> 3. Updated Docker Tools to latest nightly
> 4. Installed nightly JBoss Tools Abridged
> 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before)
> 6. Start CDK server
> Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked.
> 7. Stop CDK server
> 8. Start CDK server
> This time it's stuck on Starting... even though I can see from the console that the vagrant box started:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> {code}
> Now it will probably time out and stop the server. And most probably next start will work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22484) For JBIDE 4.4.0.Final: Prepare for Final/GA [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22484?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-22484.
-----------------------------
Resolution: Done
> For JBIDE 4.4.0.Final: Prepare for Final/GA [Hibernate]
> -------------------------------------------------------
>
> Key: JBIDE-22484
> URL: https://issues.jboss.org/browse/JBIDE-22484
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Final
>
>
> For JBIDE 4.4.0.Final [Hibernate]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch
> 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.x
> git push origin jbosstools-4.4.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!)
> * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch
> 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22505) Deploy Docker Image wizard: ImageSearch changed in API, wont compile any more
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22505?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22505:
------------------------------------------
[~xcoulon]tested it, works for me. Thanks!
> Deploy Docker Image wizard: ImageSearch changed in API, wont compile any more
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22505
> URL: https://issues.jboss.org/browse/JBIDE-22505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.0.Final
>
>
> ImageSearch broke API at some point. Current 2.0.0.201606010301 that we use in OpenShift wont allow
> {code}
> new ImageSearch(IDockerConnection conn, String name)
> {code}
> The new API now is:
> {code}
> new ImageSearch(IDockerConnection conn, String name, IRegistry reg)
> {code}
> reg cant be set to *null*, even though it now compiles and you can open up the search dialog. But searches wont find anything, the results stay empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ]
Martin Malina edited comment on JBDS-3739 at 6/2/16 8:54 AM:
-------------------------------------------------------------
I wanted to test this, but right now I'm getting another problem on consequent cdk launches (first start was fine) - it gets stuck on Starting... - reported here: JBIDE-22501
But at least I don't get IDE freeze now.
EDIT: After IDE restart, I was able to start CDK and docker connection worked.
was (Author: mmalina):
I wanted to test this, but right now I'm getting another problem on consequent cdk launches (first start was fine) - it gets stuck on Starting... - reported here: JBIDE-22501
But at least I don't get IDE freeze now.
> Docker connection does not work after cdk restart
> -------------------------------------------------
>
> Key: JBDS-3739
> URL: https://issues.jboss.org/browse/JBDS-3739
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Marián Labuda
> Priority: Blocker
> Labels: havoc
> Fix For: 10.0.0.GA
>
> Attachments: docker-frozen.txt
>
>
> When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work.
> This is caused by a bug in vagrant-service-manager 0.0.4:
> https://github.com/projectatomic/vagrant-service-manager/issues/80
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-22501 at 6/2/16 8:53 AM:
---------------------------------------------------------------
As expected, after launch timeout was reached, I got the "Problem Occurred" window pop up:
Server Container Development Kit Support at localhost was unable to start within 1800 seconds. If the server requires more time, try increasing the timeout in the server editor.
So I wonder what check does the tooling do. I thought it was vagrant status. But that returns "running" in cli.
EDIT: After IDE restart, I was able to start CDK and docker connection worked.
was (Author: mmalina):
As expected, after launch timeout was reached, I got the "Problem Occurred" window pop up:
Server Container Development Kit Support at localhost was unable to start within 1800 seconds. If the server requires more time, try increasing the timeout in the server editor.
So I wonder what check does the tooling do. I thought it was vagrant status. But that returns "running" in cli.
> CDK stuck on Starting... after launch
> -------------------------------------
>
> Key: JBIDE-22501
> URL: https://issues.jboss.org/browse/JBIDE-22501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this.
> This is what I did today (verifying JBDS-3739):
> 1. Start my Eclipse Neon RC2
> 2. Updated Eclipse
> 3. Updated Docker Tools to latest nightly
> 4. Installed nightly JBoss Tools Abridged
> 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before)
> 6. Start CDK server
> Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked.
> 7. Stop CDK server
> 8. Start CDK server
> This time it's stuck on Starting... even though I can see from the console that the vagrant box started:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Configuring and enabling network interfaces...
> ==> default: Registering box with vagrant-registration...
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> {code}
> Now it will probably time out and stop the server. And most probably next start will work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22436:
----------------------------------
Attachment: org.jboss.tools.cheatsheet.test.zip
> Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22436
> URL: https://issues.jboss.org/browse/JBIDE-22436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Michal Jurc
> Assignee: Snjezana Peco
> Fix For: 4.4.x
>
> Attachments: helloworld-cheatsheet.xml, JBIDE-22436-9.1-helloworld.log, kitchensink-cheatsheet.xml, org.jboss.tools.cheatsheet.test.zip
>
>
> After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message:
> {quote}An error has occurred. See error log for more details.
> java.lang.NullPointerException{quote}
> The detailed error log produces the same message.
> The quickstarts and their cheat sheets work even after the prompt with NullPointerException message.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-22436:
---------------------------------------
I have created and attached a plugin that opens and closes cheatsheets 100 times.
I haven't succeeded to reproduce the issue either on Fedora 23 GNOME or on Cinnamon.
Did you reproduce it on a real Fedora 23 Cinnamon or on a virtual machine?
Can you reproduce the issue using some other desktop (GNOME, KDE, Plasma, Mate ...)?
> Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22436
> URL: https://issues.jboss.org/browse/JBIDE-22436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Michal Jurc
> Assignee: Snjezana Peco
> Fix For: 4.4.x
>
> Attachments: helloworld-cheatsheet.xml, JBIDE-22436-9.1-helloworld.log, kitchensink-cheatsheet.xml
>
>
> After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message:
> {quote}An error has occurred. See error log for more details.
> java.lang.NullPointerException{quote}
> The detailed error log produces the same message.
> The quickstarts and their cheat sheets work even after the prompt with NullPointerException message.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months