[JBoss JIRA] (JBIDE-20248) compile failed in openshift
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20248?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20248:
------------------------------------
Here ya go: JBIDE-20252
> compile failed in openshift
> ---------------------------
>
> Key: JBIDE-20248
> URL: https://issues.jboss.org/browse/JBIDE-20248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> This happened:
> https://github.com/jbosstools/jbosstools-openshift/commit/08206fefb9beb06...
> Then this happened:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-openshift_master/869/console}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/project/NewProjectWizardModel.java:[52]
> [ERROR] IProject project = connection.getResourceFactory().stub(ResourceKind.PROJECT, getProjectName());
> [ERROR] ^^^^
> [ERROR] The method stub(String, String) is undefined for the type IResourceFactory
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/project/NewProjectWizardModel.java:[53]
> [ERROR] project.setDescription(getDescription());
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method setDescription(String) is undefined for the type IProject
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/project/NewProjectWizardModel.java:[54]
> [ERROR] project.setDisplayName(getDisplayName());
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method setDisplayName(String) is undefined for the type IProject
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/project/ManageProjectsWizardPage.java:[223]
> [ERROR] return object.getDescription();
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getDescription() is undefined for the type IProject
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/application/TemplateListPage.java:[472]
> [ERROR] public void setAnnoation(String key, String value) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method setAnnoation(String, String) of type TemplateListPage.TemplateNode must override or implement a supertype method
> [ERROR] 5 problems (5 errors)
> {code}
> Related: http://memegenerator.net/instance2/662763
> Please fix this and kick a new build to get the job back to blue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBTIS-460) When editing blueprint.xml, xml snippets disappearing and changing for no apparent reason.
by Roger Hui (JIRA)
[ https://issues.jboss.org/browse/JBTIS-460?page=com.atlassian.jira.plugin.... ]
Roger Hui updated JBTIS-460:
----------------------------
Affects Version/s: 8.0.2.GA
> When editing blueprint.xml, xml snippets disappearing and changing for no apparent reason.
> ------------------------------------------------------------------------------------------
>
> Key: JBTIS-460
> URL: https://issues.jboss.org/browse/JBTIS-460
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 8.0.2.GA
> Environment: JBoss Fuse Tooling Apache Camel Editor 7.3.0.v20150622-1435-H1-Final org.fusesource.ide.camel.editor.feature.feature.group JBoss by Red Hat
> Reporter: Roger Hui
>
> 1. create new Fuse Project, select camel-archetype-cxf-contract-first
> 2. select blueprint.xml from src/main/resources/OSGI-INF/blueprint
> 3. 'Design' view is shown
> 4. select 'Source' tab
> 5. select 'Design' tab
> 6. select 'Source' tab
> 7. At this point blueprint.xml is showing that a change has been made. Further inspection shows that some of the xml has been removed. Selecting 'Design' tab again shows that some components have been deleted.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20251) m2e exception occurs after importing freemarker editor plugin into eclipse workspace
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20251?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-20251.
---------------------------------
> m2e exception occurs after importing freemarker editor plugin into eclipse workspace
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-20251
> URL: https://issues.jboss.org/browse/JBIDE-20251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Denis Golovin
> Fix For: 4.3.0.Beta2
>
>
> Right after freemarker imported into workspace, m2e builder throws exception:
> {code}!ENTRY org.eclipse.core.resources 4 75 2015-07-09 17:41:50.488
> !MESSAGE Errors occurred during the build.
> !SUBENTRY 1 org.eclipse.m2e.core 4 75 2015-07-09 17:41:50.488
> !MESSAGE Errors running builder 'Maven Project Builder' on project 'org.jboss.ide.eclipse.freemarker'.
> !STACK 0
> java.lang.IllegalArgumentException: Path must include project and resource name: /org.jboss.ide.eclipse.freemarker
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2069)
> at org.eclipse.core.internal.resources.Container.getFolder(Container.java:201)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.refreshResources(MavenBuilderImpl.java:246)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:175)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> 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.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> which happens because freemarker dependency jar is placet in project root. Moving to sub-folder lib solves the issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20251) m2e exception occurs after importing freemarker editor plugin into eclipse workspace
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20251?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-20251:
----------------------------------
Summary: m2e exception occurs after importing freemarker editor plugin into eclipse workspace (was: m2e exception after importing freemarker editor plugin into eclipse workspace)
> m2e exception occurs after importing freemarker editor plugin into eclipse workspace
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-20251
> URL: https://issues.jboss.org/browse/JBIDE-20251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Denis Golovin
>
> Right after freemarker imported into workspace, m2e builder throws exception:
> {code}!ENTRY org.eclipse.core.resources 4 75 2015-07-09 17:41:50.488
> !MESSAGE Errors occurred during the build.
> !SUBENTRY 1 org.eclipse.m2e.core 4 75 2015-07-09 17:41:50.488
> !MESSAGE Errors running builder 'Maven Project Builder' on project 'org.jboss.ide.eclipse.freemarker'.
> !STACK 0
> java.lang.IllegalArgumentException: Path must include project and resource name: /org.jboss.ide.eclipse.freemarker
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2069)
> at org.eclipse.core.internal.resources.Container.getFolder(Container.java:201)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.refreshResources(MavenBuilderImpl.java:246)
> at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:175)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> 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.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> which happens because freemarker dependency jar is placet in project root. Moving to sub-folder lib solves the issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20251) m2e exception after importing freemarker editor plugin into eclipse workspace
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-20251:
-------------------------------------
Summary: m2e exception after importing freemarker editor plugin into eclipse workspace
Key: JBIDE-20251
URL: https://issues.jboss.org/browse/JBIDE-20251
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, freemarker
Affects Versions: 4.3.0.Beta2
Reporter: Denis Golovin
Right after freemarker imported into workspace, m2e builder throws exception:
{code}!ENTRY org.eclipse.core.resources 4 75 2015-07-09 17:41:50.488
!MESSAGE Errors occurred during the build.
!SUBENTRY 1 org.eclipse.m2e.core 4 75 2015-07-09 17:41:50.488
!MESSAGE Errors running builder 'Maven Project Builder' on project 'org.jboss.ide.eclipse.freemarker'.
!STACK 0
java.lang.IllegalArgumentException: Path must include project and resource name: /org.jboss.ide.eclipse.freemarker
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:2069)
at org.eclipse.core.internal.resources.Container.getFolder(Container.java:201)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.refreshResources(MavenBuilderImpl.java:246)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:175)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
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.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
which happens because freemarker dependency jar is placet in project root. Moving to sub-folder lib solves the issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months