[JBoss JIRA] (JBIDE-21016) compile failed in openshift
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-21016.
---------------------------------
Resolution: Done
fixed in 4.3.x
> compile failed in openshift
> ---------------------------
>
> Key: JBIDE-21016
> URL: https://issues.jboss.org/browse/JBIDE-21016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
>
> Compilation failure in 4.3.x:
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615]
> [ERROR] private IObservableList mutableTargets = new WritableList<>();
> [ERROR] ^^^^^^^^^^^^
> [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <>
> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21016) compile failed in openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21016:
----------------------------------------
Assignee: Fred Bricon (was: Andre Dietisheim)
> compile failed in openshift
> ---------------------------
>
> Key: JBIDE-21016
> URL: https://issues.jboss.org/browse/JBIDE-21016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
>
> Compilation failure in 4.3.x:
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615]
> [ERROR] private IObservableList mutableTargets = new WritableList<>();
> [ERROR] ^^^^^^^^^^^^
> [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <>
> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21016) compile failed in openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21016:
-------------------------------------
Affects Version/s: (was: 4.4.0.Alpha1)
> compile failed in openshift
> ---------------------------
>
> Key: JBIDE-21016
> URL: https://issues.jboss.org/browse/JBIDE-21016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
>
> Compilation failure in 4.3.x:
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615]
> [ERROR] private IObservableList mutableTargets = new WritableList<>();
> [ERROR] ^^^^^^^^^^^^
> [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <>
> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-21012 at 10/23/15 5:01 PM:
-----------------------------------------------------------------------
deploy to nexus is interesting because it should be much simpler to use rather than manually copying around sites on jboss.org.
was (Author: maxandersen):
deploy to nexus is interesting because it would be much simpler to use rather than manually copying around sites on jboss.org.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20845:
----------------------------------------
[~snjeza] could you please take a look?
> Unable to install breakpoint even if line number set to be generated
> --------------------------------------------------------------------
>
> Key: JBIDE-20845
> URL: https://issues.jboss.org/browse/JBIDE-20845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.CR2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.x, 4.4.0.Alpha1
>
> Attachments: breakpoint-error.png, compiler-settings.png
>
>
> I am unable to get breakpoints to work for a html5 project running on WildFly.
> I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error:
> Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes.
> Reason: Absent Line Number Information
> !breakpoint-error.png!
> I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has:
> org.eclipse.jdt.core.compiler.debug.lineNumber=generate
> This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same.
> I'm not really sure which component this should belong to, it looks like an upstream issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20845) Unable to install breakpoint even if line number set to be generated
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20845?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20845:
-----------------------------------
Fix Version/s: 4.3.x
(was: 4.3.1.Beta1)
> Unable to install breakpoint even if line number set to be generated
> --------------------------------------------------------------------
>
> Key: JBIDE-20845
> URL: https://issues.jboss.org/browse/JBIDE-20845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.CR2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.x, 4.4.0.Alpha1
>
> Attachments: breakpoint-error.png, compiler-settings.png
>
>
> I am unable to get breakpoints to work for a html5 project running on WildFly.
> I tried to verify JBIDE-20804 so I created the html5 project from central, set a breakpoint in MemberService.listAllMembers() (line 72) and then selected Debug on server -> WildFly. The server was started in debugging mode and the project started deploying, but then I got an error:
> Unable to install breakpoint in org.jboss.tools.example.html5.rest.MemberService$$$view3 due to missing line number attributes. Modify compiler options to generate line number attributes.
> Reason: Absent Line Number Information
> !breakpoint-error.png!
> I checked and this option was checked in Preferences -> Java -> Compiler. Also, I even checked the project settings (.settings/org.eclipse.jdt.core.prefs) and it has:
> org.eclipse.jdt.core.compiler.debug.lineNumber=generate
> This happened to me on Mac with WildFly 8, 9 and 10. And psrna checked this for me on Linux and the result was the same.
> I'm not really sure which component this should belong to, it looks like an upstream issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21012:
---------------------------------------------
deploy to nexus is interesting because it would be much simpler to use rather than manually copying around sites on jboss.org.
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21016) compile failed in openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21016?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21016:
-------------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> compile failed in openshift
> ---------------------------
>
> Key: JBIDE-21016
> URL: https://issues.jboss.org/browse/JBIDE-21016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
>
> Denis says Openshift is failing to compile in master:
> {code}
> [INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on project org.jboss.tools.openshift.egit.ui: Compilation failure: Compilation failure:
> [INFO] [ERROR] <http://0.0.0.0:8088/job/jbosstools-releng/ws/jbosstools-openshift/plugins...>:[41]
> [INFO] [ERROR] return Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR);
> [INFO] [ERROR] ^^^^^^^^^^^^^^^^
> [INFO] [ERROR] DEFAULT_REPO_DIR cannot be resolved or is not a field
> [INFO] [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Different compilation failure in 4.3.x:
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.23.1:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_4.3.mars/sources/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/TemplateListPage.java:[615]
> [ERROR] private IObservableList mutableTargets = new WritableList<>();
> [ERROR] ^^^^^^^^^^^^
> [ERROR] The type WritableList is not generic; it cannot be parameterized with arguments <>
> [ERROR] 1 problem (1 error){code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months