[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
2. Should be able to find references in job.xml files for Batch Artifact Property
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> 2. Should be able to find references in job.xml files for Batch Artifact Property
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19568:
--------------------------------
Summary: Disable the "Check for update" button while a check for update is in progress (was: Disable the "Check for update" button while an check for update is in progress)
> Disable the "Check for update" button while a check for update is in progress
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> 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
[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while an check for update is in progress
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19568:
-----------------------------------
Assignee: Mickael Istria
> Disable the "Check for update" button while an check for update is in progress
> ------------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> 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
[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while an check for update is in progress
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19568:
--------------------------------
Summary: Disable the "Check for update" button while an check for update is in progress (was: central check for updates fails silently when provisioning errors)
> Disable the "Check for update" button while an check for update is in progress
> ------------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> 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
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
{quote}I hope you are just kidding.
Currently Im forced to disable central manually or live with slow startup and a modal dialog every time I start eclipse in Dev mode.
This did not happen in previous versions of central,
Thus this is a regression.
Please fix that or explain why we cannot just fix it with a simple if statement to check if p2 is actually available in this install. Thank you.{quote}
In previous central it was failing with NPE w/o any message or explanation see https://github.com/mickaelistria/jbosstools-central/commit/d9e82bb6ef425e....
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19190:
---------------------------------------------
not sure why this is assigned to me since nothing except #0 is related to me.
lets move it as its own repo. it does not seem to fit anywhere else and its supposed to be completely independent anyway.
Can you fix the rest ?
> migrate VersionWatch to jbosstools-* repo
> -----------------------------------------
>
> Key: JBIDE-19190
> URL: https://issues.jboss.org/browse/JBIDE-19190
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly.
> 1. remove all refs to QA Jenkins file paths to make this more generic
> 2. migrate those internal file paths into jenkins config.xml files
> 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19568) central check for updates fails silently when provisioning errors
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19568:
---------------------------------------------
so I did not notice the oomph part here - that is interesting and worrying if oomph is hooking into things.
But back to the original issue - after about 5 minutes a dialog showed up showing what was being suggested for update.
Is there a way the button could be disabled until the first check has finsihed or tell the user an update is already running ?
> 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
> 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
[JBoss JIRA] (JBIDE-19568) central check for updates fails silently when provisioning errors
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19568:
----------------------------------------
Component/s: (was: 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
> 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