April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ] Debbie Steigner commented on JBIDE-12161: ----------------------------------------- Ok thank you , I've entered the JBDS RFE - https://issues.jboss.org/browse/PRODMGT-1200 > Deploy application to JBoss AS 7 in domain mode > ----------------------------------------------- > > Key: JBIDE-12161 > URL: https://issues.jboss.org/browse/JBIDE-12161 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.CR1 > Environment: Any. > Reporter: Humberto Ferreira da Luz Jr. > Assignee: Rob Stryker > Labels: f2f2012 > Fix For: 4.2.x > > > I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode. > We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19568) central check for updates fails silently when provisioning errors

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19568: ------------------------------------- This looks like an Ooomph issue to me. Nothing in the stacktrace indicates we have anything to catch in our code. > central check for updates fails silently when provisioning errors > ----------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Reporter: Max Rydahl Andersen > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19568) central check for updates fails silently when provisioning errors

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19568: -------------------------------- Component/s: upstream > central check for updates fails silently when provisioning errors > ----------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Reporter: Max Rydahl Andersen > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3392) Arquillian icon is missing in JBDS 8.1.0 Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3392?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3392: ----------------------------------- No plans for a new release. Fixing the catalog is cheap and doesn't require one. Since it looks bad we might as well fix it quick > Arquillian icon is missing in JBDS 8.1.0 Central > ------------------------------------------------ > > Key: JBDS-3392 > URL: https://issues.jboss.org/browse/JBDS-3392 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.GA > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: JBDS_810_GA.png > > > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5

by Martin Malina (JIRA)

Martin Malina created JBIDE-19569: ------------------------------------- Summary: Unable to switch pages shown in visual preview when editing mobile html5 Key: JBIDE-19569 URL: https://issues.jboss.org/browse/JBIDE-19569 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.3.Final Reporter: Martin Malina I'm not sure if my use case is valid or not. But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one. So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview. Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button? But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :) [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18542: ---------------------------------------- I have hope that fix for JBIDE-19410 improves status here, but since it's not determistic, one cannot know... > NPE during "Check installation for Early Access" > ------------------------------------------------ > > Key: JBIDE-18542 > URL: https://issues.jboss.org/browse/JBIDE-18542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Rob Cernich > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.x, 4.3.0.Alpha2 > > > I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/ > {noformat} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19543) org.sonatype.m2e.egit is not compatible with EGit 4.0

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19543?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19543: -------------------------------- Component/s: upstream > org.sonatype.m2e.egit is not compatible with EGit 4.0 > ----------------------------------------------------- > > Key: JBIDE-19543 > URL: https://issues.jboss.org/browse/JBIDE-19543 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > While trying to move the Mars M6, I noticed that org.sonatype.m2e.egit feature/bundle is not compatible with the upcoming EGit 4.0 version (might be just a matter of version range). > We need to have a compatible version soon to be able to build next JBT/JBDS against Mars M6. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19419) NPE in InstallationChecker

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19419?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19419: ---------------------------------------- Hey [~ilx], thanks for reporting. Can you please comment (in JBIDE-18542) whether you know deterministic steps to reproduce? > NPE in InstallationChecker > -------------------------- > > Key: JBIDE-19419 > URL: https://issues.jboss.org/browse/JBIDE-19419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.Beta1 > Reporter: Ivica Loncar > > {code} > java.lang.NullPointerException > at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99) > at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79) > at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72) > at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:571) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} > {code} > eclipse.buildId=4.4.2.M20150204-1700 > java.version=1.8.0 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19543) org.sonatype.m2e.egit is not compatible with EGit 4.0

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19543?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19543: -------------------------------- Fix Version/s: 4.3.0.Alpha2 > org.sonatype.m2e.egit is not compatible with EGit 4.0 > ----------------------------------------------------- > > Key: JBIDE-19543 > URL: https://issues.jboss.org/browse/JBIDE-19543 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > While trying to move the Mars M6, I noticed that org.sonatype.m2e.egit feature/bundle is not compatible with the upcoming EGit 4.0 version (might be just a matter of version range). > We need to have a compatible version soon to be able to build next JBT/JBDS against Mars M6. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18558) Improve usability of up-to-date Central items

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18558?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18558: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.2.x) (was: 4.3.x) > Improve usability of up-to-date Central items > --------------------------------------------- > > Key: JBIDE-18558 > URL: https://issues.jboss.org/browse/JBIDE-18558 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Install hybrid tools. > restart eclipse. > enable show installed, click hybrid tools. > Install/update is greyed out. > why can I not run update ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 April 2015