December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18959) New Datalist wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18959?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18959: ----------------------------------- Description: !datalist.png! > New Datalist wizard for HTML5 palette > ------------------------------------- > > Key: JBIDE-18959 > URL: https://issues.jboss.org/browse/JBIDE-18959 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: datalist.png, Datalist.png, DatalistWizBan.png > > > !datalist.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18959) New Datalist wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18959?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18959: ----------------------------------- Attachment: datalist.png > New Datalist wizard for HTML5 palette > ------------------------------------- > > Key: JBIDE-18959 > URL: https://issues.jboss.org/browse/JBIDE-18959 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: datalist.png, Datalist.png, DatalistWizBan.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18862: ---------------------------------------- [~mmalina], no, I don't think it's necessary. For some big changes close to release then yes. But not for every PR. In this case we have plenty of time for testing and if something is wrong we will have time to fix it or revert. But let's not postpone it now. Let's do it in the beginning of 4.2.2 development cycle since the change is critical and relatively big. > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18862: ----------------------------------- Priority: Major (was: Minor) > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18862: ----------------------------------- Issue Type: Bug (was: Feature Request) > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18862: --------------------------------------- [~akazakov], is it really necessary to test every PR before it is pushed? I understand that it can make sense during test cycle when we want to reduce the risk of the next respin being broken, but in development cycle it is usually not necessary. WDYT? > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18967) Inconsistent search results in Central - JBDS returns more results than Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18967?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18967: ---------------------------------- Assignee: Len DiMaggio (was: Nick Boldt) > Inconsistent search results in Central - JBDS returns more results than Tools > ----------------------------------------------------------------------------- > > Key: JBIDE-18967 > URL: https://issues.jboss.org/browse/JBIDE-18967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.1.Final > Environment: eclipse-standard-luna-SR1-RC1-linux-gtk-x86_64 > RHEL 6.5 > Java 1.7 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.1.Final > > Attachments: JBDS801.png, JBT421_1.png, JBT421_2.png, mylyn-stuff-in-central.png > > > To recreate: > * Install Eclipse > * Install JBDS 8.0.1 through Eclipse Marketplace > * In Central, select software/update > * In the filter, enter "mylyn" > * Observe the results in the attached screenshots - JBDS returns all (4) packages, Tools returns (2) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3296: ----------------------------- Target Release: 8.0.1.GA (was: 8.0.3.GA) > P2 reports several locations without repositories in case product installed on different device from user home directory > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3296 > URL: https://issues.jboss.org/browse/JBDS-3296 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Affects Versions: 8.0.0.GA, 8.0.1.GA > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 8.0.1.GA > > Attachments: fixed.png > > > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > 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:54) > {code} > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > 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:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3296. ---------------------------- Resolution: Done > P2 reports several locations without repositories in case product installed on different device from user home directory > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3296 > URL: https://issues.jboss.org/browse/JBDS-3296 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Affects Versions: 8.0.0.GA, 8.0.1.GA > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 8.0.1.GA > > Attachments: fixed.png > > > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > 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:54) > {code} > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > 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:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3296) P2 reports several locations without repositories in case product installed on different device from user home directory

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3296?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3296: ----------------------------- Attachment: fixed.png p2 browser now shows both sites exist and work: !fixed.png! > P2 reports several locations without repositories in case product installed on different device from user home directory > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3296 > URL: https://issues.jboss.org/browse/JBDS-3296 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Affects Versions: 8.0.0.GA, 8.0.1.GA > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 8.0.1.GA > > Attachments: fixed.png > > > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0-development/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > 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:54) > {code} > {code}org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.redhat.com/updates/8.0/central/core/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692) > 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:54){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 December 2014