[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19338:
-------------------------------------
Unable to replicate on the same environment I used when reporting this Jira. Seems that my PC was in some strange conditions now it works fine. Probably we can mark this one as Unable to replicate.
> Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19338
> URL: https://issues.jboss.org/browse/JBIDE-19338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Check the button "Show only palette groups for which libraries are defined on the page"
> ASSERT: No Palette groups are visible in HTML 5 Palette
> 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 4. Check the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
> 5. Uncheck the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19338) Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19338?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19338:
-------------------------------------
Unable to replicate on Fedora 21 Gnome with JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Ionic palette items disappears when "Show only palette groups for which libraries are defined on the page" filter is applied
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19338
> URL: https://issues.jboss.org/browse/JBIDE-19338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Environment: MS Windows 7 JBDS 9.0.0.Alpha1-v20150216-1042-B11
> Reporter: Vlado Pakan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta1
>
>
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Check the button "Show only palette groups for which libraries are defined on the page"
> ASSERT: No Palette groups are visible in HTML 5 Palette
> 3. Open following html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT: Following palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 4. Check the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
> 5. Uncheck the button "Show only palette groups for which libraries are defined on the page"
> ERROR: Ionic palette is not displayed
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19607) Offline quickstarts not working - Could not calculate build plan
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19607?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-19607.
---------------------------------
Fix Version/s: 4.3.0.Alpha2
Resolution: Done
I could reproduce while running the script with a Maven version different from the Maven embedder version, used by m2e. This version mismatch causes plugins dependencies to be missing when running in Eclipse.
In order to mitigate the problem, I forced the script to use the maven wrapper, which, for now, uses the same Maven version as m2e (3.3.1). I'll try to make it more robust later.
> Offline quickstarts not working - Could not calculate build plan
> ----------------------------------------------------------------
>
> Key: JBIDE-19607
> URL: https://issues.jboss.org/browse/JBIDE-19607
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.3.0.Alpha2
> Environment: JBDS 9.0.0 nightly build Alpha2-v20150414-2227-B2953
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha2
>
>
> After running offline script and configuring JBDS to use that (without internet connectivity) I'm unable to import any of quickstarts. Some (as HTML5 project archetype for example) throw error into error log right after wizard startup:
> {noformat:title=Could not resolve artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final}
> org.eclipse.core.runtime.CoreException: Could not resolve artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:776)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:262)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:252)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:206)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:191)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:140)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.createControl(ArchetypeExamplesWizardPage.java:113)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Contains: Failure to transfer org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: unknown error
> org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.wildfly.archetype:wildfly-html5-mobile-archetype:pom:8.2.0.Final from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: unknown error
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:753)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$5.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:743)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:720)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.downloadArchetype(ArchetypeExamplesWizardPage.java:262)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.access$4(ArchetypeExamplesWizardPage.java:252)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$3.run(ArchetypeExamplesWizardPage.java:206)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.getRequiredProperties(ArchetypeExamplesWizardPage.java:191)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.initializeArchetype(ArchetypeExamplesWizardPage.java:140)
> at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage.createControl(ArchetypeExamplesWizardPage.java:113)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
> After hitting Finish on wizard, the imported project (if it was imported) cannot be build, because it cannot resolve maven-resources-plugin. Error log:
> {noformat:title=Errors occurred during the build.}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred during the build.
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:498)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: Errors running builder 'Maven Project Builder' on project 'jboss-greeter'.
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 30 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 36 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 39 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 42 more
> Contains: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:113)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486)
> at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:398)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator$1.run(ProjectExamplesActivator.java:207)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 36 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 39 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-resources-plugin:pom:2.6 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 42 more
> {noformat}
> Note, that all artifacts that eclipse cannot resolve (maven-resources-plugin, HTML5 archetype, ...) I have in my local repository (were downloaded by offline script correctly). I checked few sha1 checksums and they are correct.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19350.
---------------------------------
Resolution: Done
So long as this bug was mostly about not being able to cancel, and frozen progress monitors, I'd say it's fixed.
If there's a bug regarding the transfer itself freezing, I guess another bug should be opened, but I'm not really sure that's my responsibility, since I just use their API client jars and stuff...
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19350:
-------------------------------------
https://github.com/jbosstools/jbosstools-server/pull/339
I've been seriously completely unable to replicate any actual freezing in terms of the transfer stopping, despite several hours of trying. Obviously the progress monitor froze, but I can't replicate the transfer itself freezing.
Either way, this PR now allows for more cancels and an infinite-progress-bar during the transfer portion.
Pushing to 4.3.0.Alpha2 for further consumption but as far as I can tell it works for me.... and I tested on a deployment that was 1.7 gigabytes, though I did test with a local docker image (so tools thought was remote).
> big war deployment to remote server (management) gets stuck
> -----------------------------------------------------------
>
> Key: JBIDE-19350
> URL: https://issues.jboss.org/browse/JBIDE-19350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-publishing-stuck.png
>
>
> I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %).
> I used the project from JBIDE-19043 - see "Steps to Reproduce".
> !remote-publishing-stuck.png!
> I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months