[JBoss JIRA] (ERT-755) Device#getDPI method can return incorrect values [EBZ#545953]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-755?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-755:
---------------------------------
Sprint: devex #172 Sep 2019
Assignee: Eric Williams
> Device#getDPI method can return incorrect values [EBZ#545953]
> -------------------------------------------------------------
>
> Key: ERT-755
> URL: https://issues.jboss.org/browse/ERT-755
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.14_M1, SWT, bzira
>
> Since the fix for Bug 535064 there is an issue with Device#getDPI method that can under some unclear conditions return an incorrect DPI. Since my comment in the original bug went unnoticed I'm creating a new bug to raise this issue.
> Here's my comment in the original bug:
> I'm noticing a strange behavior of Device#getScreenDPI on my system (Ubuntu 18.04 with latest updates, and GTK version 3.22.30). The returned DPI value is {102, 102} instead of {96,96} as it should be. I've tried to debug the issue and here are the values used for DPI calculation:
> widthMM=480,scaleFactor=1,monitorGeometry={0, 0, 1920, 1080}
> This gives 254*1920/(480*10.0) = 101.6, value then rounded to 102.
> I've tried to reproduce this issue with VirtualBox with a clean 18.04 install but couldn't. Although it's the same system, returned widthMM is different:
> widthMM=503,scaleFactor=1,monitorGeometry={0, 0, 1920, 988}
> Which gives 254*1920/(503*10.0) = 96.0, which is correct.
> Is this a bug? Running $ xrandr --query gives
> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
> So the 480mm value is there, but I am not sure what this means. The result is that Eclipse 4.9 and onward return and incorrect DPI value on my system.
> "xrdb -query | grep dpi" gives the correct DPI as follows:
> Xft.dpi: 96
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
4 years, 9 months
[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26817 at 9/11/19 11:34 AM:
--------------------------------------------------------------------
removed the 3rd link:
!image-2019-09-11-17-34-37-623.png!
was (Author: adietish):
removed the 3rd link:
!screenshot-1.png|thumbnail!
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.AM1
>
> Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
4 years, 9 months
[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26817 at 9/11/19 11:33 AM:
--------------------------------------------------------------------
removed the 3rd link:
!screenshot-1.png|thumbnail!
was (Author: adietish):
removed the 3rd link:
!screenshot-1.png!
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.13.0.AM1
>
> Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, screenshot-1.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
4 years, 9 months
[JBoss JIRA] (ERT-755) Device#getDPI method can return incorrect values [EBZ#545953]
by Friendly Jira Robot (Jira)
Friendly Jira Robot created ERT-755:
---------------------------------------
Summary: Device#getDPI method can return incorrect values [EBZ#545953]
Key: ERT-755
URL: https://issues.jboss.org/browse/ERT-755
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
Since the fix for Bug 535064 there is an issue with Device#getDPI method that can under some unclear conditions return an incorrect DPI. Since my comment in the original bug went unnoticed I'm creating a new bug to raise this issue.
Here's my comment in the original bug:
I'm noticing a strange behavior of Device#getScreenDPI on my system (Ubuntu 18.04 with latest updates, and GTK version 3.22.30). The returned DPI value is {102, 102} instead of {96,96} as it should be. I've tried to debug the issue and here are the values used for DPI calculation:
widthMM=480,scaleFactor=1,monitorGeometry={0, 0, 1920, 1080}
This gives 254*1920/(480*10.0) = 101.6, value then rounded to 102.
I've tried to reproduce this issue with VirtualBox with a clean 18.04 install but couldn't. Although it's the same system, returned widthMM is different:
widthMM=503,scaleFactor=1,monitorGeometry={0, 0, 1920, 988}
Which gives 254*1920/(503*10.0) = 96.0, which is correct.
Is this a bug? Running $ xrandr --query gives
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
So the 480mm value is there, but I am not sure what this means. The result is that Eclipse 4.9 and onward return and incorrect DPI value on my system.
"xrdb -query | grep dpi" gives the correct DPI as follows:
Xft.dpi: 96
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
4 years, 9 months
[JBoss JIRA] (ERT-755) Device#getDPI method can return incorrect values [EBZ#545953]
by Friendly Jira Robot (Jira)
[ https://issues.jboss.org/browse/ERT-755?page=com.atlassian.jira.plugin.sy... ]
Friendly Jira Robot resolved ERT-755.
-------------------------------------
Resolution: Done
> Device#getDPI method can return incorrect values [EBZ#545953]
> -------------------------------------------------------------
>
> Key: ERT-755
> URL: https://issues.jboss.org/browse/ERT-755
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Priority: Major
> Labels: 4.14_M1, SWT, bzira
>
> Since the fix for Bug 535064 there is an issue with Device#getDPI method that can under some unclear conditions return an incorrect DPI. Since my comment in the original bug went unnoticed I'm creating a new bug to raise this issue.
> Here's my comment in the original bug:
> I'm noticing a strange behavior of Device#getScreenDPI on my system (Ubuntu 18.04 with latest updates, and GTK version 3.22.30). The returned DPI value is {102, 102} instead of {96,96} as it should be. I've tried to debug the issue and here are the values used for DPI calculation:
> widthMM=480,scaleFactor=1,monitorGeometry={0, 0, 1920, 1080}
> This gives 254*1920/(480*10.0) = 101.6, value then rounded to 102.
> I've tried to reproduce this issue with VirtualBox with a clean 18.04 install but couldn't. Although it's the same system, returned widthMM is different:
> widthMM=503,scaleFactor=1,monitorGeometry={0, 0, 1920, 988}
> Which gives 254*1920/(503*10.0) = 96.0, which is correct.
> Is this a bug? Running $ xrandr --query gives
> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
> So the 480mm value is there, but I am not sure what this means. The result is that Eclipse 4.9 and onward return and incorrect DPI value on my system.
> "xrdb -query | grep dpi" gives the correct DPI as follows:
> Xft.dpi: 96
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
4 years, 9 months
[JBoss JIRA] (JBIDE-26825) Hibernate job is red
by stephane bouchet (Jira)
[ https://issues.jboss.org/browse/JBIDE-26825?page=com.atlassian.jira.plugi... ]
stephane bouchet updated JBIDE-26825:
-------------------------------------
Sprint: devex #172 Sep 2019
> Hibernate job is red
> --------------------
>
> Key: JBIDE-26825
> URL: https://issues.jboss.org/browse/JBIDE-26825
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.13.0.AM1
> Environment: Central CI
> Reporter: Josef Kopriva
> Assignee: stephane bouchet
> Priority: Blocker
>
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Compilation errors:
> {code:java}
> 13:02:06 [INFO] Reactor Summary:
> 13:02:06 [INFO]
> 13:02:06 [INFO] jbosstools-hibernate ............................... SUCCESS [ 31.291 s]
> 13:02:06 [INFO] Hibernate Tooling Common Stuff ..................... SUCCESS [ 0.016 s]
> 13:02:06 [INFO] Hibernate Tooling Common Plugins ................... SUCCESS [ 0.017 s]
> 13:02:06 [INFO] Hibernate Common Library Plugins ................... SUCCESS [ 0.017 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.activation.v_1_2_0 .. SUCCESS [ 41.034 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.antlr.v_2_7_7 ....... SUCCESS [ 1.030 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.bsh.v_2_0_b4 ........ SUCCESS [ 2.596 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.dom4j.v_1_6_1 ....... SUCCESS [ 0.911 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.freemarker.v_2_3_23 . SUCCESS [ 3.051 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.jaxb-api.v_2_3_0 .... SUCCESS [ 4.549 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.jaxb-core.v_2_3_0 ... SUCCESS [ 7.358 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.libs.jtidy.v_r8-20060801 . SUCCESS [ 2.721 s]
> 13:02:06 [INFO] Hibernate ORM Tooling .............................. SUCCESS [ 0.011 s]
> 13:02:06 [INFO] Hibernate ORM Tooling Plugins ...................... SUCCESS [ 0.009 s]
> 13:02:06 [INFO] Hibernate ORM Core Plugins ......................... SUCCESS [ 0.010 s]
> 13:02:06 [INFO] Hibernate ORM Runtime Plugins ...................... SUCCESS [ 0.013 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.spi .............. SUCCESS [ 1.794 s]
> 13:02:06 [INFO] org.hibernate.eclipse .............................. SUCCESS [ 3.337 s]
> 13:02:06 [INFO] org.hibernate.eclipse.console ...................... SUCCESS [ 6.056 s]
> 13:02:06 [INFO] org.hibernate.eclipse.help ......................... SUCCESS [ 1.063 s]
> 13:02:06 [INFO] org.hibernate.eclipse.jdt.ui ....................... FAILURE [ 0.768 s]
> 13:02:06 [INFO] org.hibernate.eclipse.mapper ....................... SUCCESS [ 2.051 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.jpt.core ................. SUCCESS [ 2.899 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.jpt.ui ................... SUCCESS [ 2.625 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.ui ....................... SUCCESS [ 2.151 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.xml ...................... SUCCESS [ 2.515 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.xml.ui ................... SUCCESS [ 2.178 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.common ........... SUCCESS [ 1.893 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_3_5 ............ SUCCESS [ 31.901 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_3_6 ............ SUCCESS [ 16.387 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_4_0 ............ SUCCESS [ 15.885 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_4_3 ............ SUCCESS [ 20.628 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_0 ............ SUCCESS [ 23.192 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_1 ............ SUCCESS [ 17.284 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_2 ............ SUCCESS [ 9.974 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_3 ............ SUCCESS [ 20.573 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_4 ............ SUCCESS [ 40.847 s]
> 13:02:06 [INFO] Hibernate ORM Tooling Test Plugins ................. SUCCESS [ 0.010 s]
> 13:02:06 [INFO] Hibernate ORM Tooling Core Test Plugins ............ SUCCESS [ 0.008 s]
> 13:02:06 [INFO] org.hibernate.eclipse.jdt.ui.test .................. SKIPPED
> 13:02:06 [INFO] org.jboss.tools.hibernate.jpt.core.test ............ SUCCESS [ 0.593 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.orm.test ................. SUCCESS [ 3.576 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.ui.test .................. SKIPPED
> 13:02:06 [INFO] Hibernate ORM Tooling Runtime Test Plugins ......... SUCCESS [ 0.009 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.spi.test ......... SUCCESS [ 0.190 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_3_5.test ....... SUCCESS [ 3.444 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_3_6.test ....... SUCCESS [ 0.934 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_4_0.test ....... SUCCESS [ 0.978 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_4_3.test ....... SUCCESS [ 0.862 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_0.test ....... SUCCESS [ 3.456 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_1.test ....... SUCCESS [ 0.911 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_2.test ....... SUCCESS [ 0.920 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_3.test ....... SUCCESS [ 0.878 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.runtime.v_5_4.test ....... SUCCESS [ 0.894 s]
> 13:02:06 [INFO] Hibernate Utilities for ORM Testing Plugins ........ SUCCESS [ 0.020 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.reddeer .................. SUCCESS [ 0.945 s]
> 13:02:06 [INFO] Hibernate Search Tooling ........................... SUCCESS [ 0.008 s]
> 13:02:06 [INFO] Hibernate Search Tooling Plugins ................... SUCCESS [ 0.008 s]
> 13:02:06 [INFO] Hibernate Search Core Plugins ...................... SUCCESS [ 0.007 s]
> 13:02:06 [INFO] Hibernate Search Runtime Plugins ................... SUCCESS [ 0.008 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.spi ....... SUCCESS [ 0.168 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search ................... SUCCESS [ 0.646 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.common .... SUCCESS [ 1.043 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.v_4_0 ..... SUCCESS [ 22.353 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.v_5_3 ..... SUCCESS [ 21.148 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.v_5_5 ..... SUCCESS [ 21.252 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.v_5_5.1 ... SUCCESS [ 5.948 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.runtime.v_5_7 ..... SUCCESS [ 18.812 s]
> 13:02:06 [INFO] Hibernate Search Tooling Test Plugins .............. SUCCESS [ 0.009 s]
> 13:02:06 [INFO] Hibernate Search Core Test Plugins ................. SUCCESS [ 0.007 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.test .............. SUCCESS [ 13.179 s]
> 13:02:06 [INFO] hibernatetools.tests ............................... SUCCESS [ 0.008 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.dummy.test ............... SUCCESS [ 0.161 s]
> 13:02:06 [INFO] hibernatetools.test-framework ...................... SUCCESS [ 0.008 s]
> 13:02:06 [INFO] hibernatetools.itests .............................. SUCCESS [ 0.007 s]
> 13:02:06 [INFO] org.jboss.tools.hibernate.ui.bot.test .............. SKIPPED
> 13:02:06 [INFO] hibernatetools.features ............................ SUCCESS [ 0.010 s]
> 13:02:06 [INFO] org.hibernate.eclipse.feature ...................... SKIPPED
> 13:02:06 [INFO] org.hibernate.search.eclipse.feature ............... SKIPPED
> 13:02:06 [INFO] org.hibernate.eclipse.test.feature ................. SKIPPED
> 13:02:06 [INFO] org.jboss.tools.hibernate.search.test.feature ...... SUCCESS [ 0.260 s]
> 13:02:06 [INFO] hibernatetools.site ................................ SKIPPED
> 13:02:06 [INFO] hibernatetools.docs ................................ SUCCESS [ 0.008 s]
> 13:02:06 [INFO] ------------------------------------------------------------------------
> 13:02:06 [INFO] BUILD FAILURE
> 13:02:06 [INFO] ------------------------------------------------------------------------
> 13:02:06 [INFO] Total time: 17:20 min
> 13:02:06 [INFO] Finished at: 2019-09-11T07:02:06-04:00
> 13:02:07 [INFO] Final Memory: 181M/567M
> 13:02:07 [INFO] ------------------------------------------------------------------------
> 13:02:07 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.4.0:compile (default-compile) on project org.hibernate.eclipse.jdt.ui: Compilation failure: Compilation failure:
> 13:02:07 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-hibernate_master/sources/orm/plugin/core/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/NewHibernateMappingPreviewPage.java:[35]
> 13:02:07 [ERROR] import org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateTextFileChange;
> 13:02:07 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 13:02:07 [ERROR] Access restriction: The type 'CreateTextFileChange' is not API (restriction on classpath entry '/mnt/hudson_workspace/workspace/jbosstools-hibernate_master/.repository/p2/osgi/bundle/org.eclipse.jdt.core.manipulation/1.12.100.v20190816-1501/org.eclipse.jdt.core.manipulation-1.12.100.v20190816-1501.jar')
> 13:02:07 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-hibernate_master/sources/orm/plugin/core/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/NewHibernateMappingPreviewPage.java:[246]
> 13:02:07 [ERROR] CreateTextFileChange change = new CreateTextFileChange(filePathTo_Show, str.toString(), null, "hbm.xml"); //$NON-NLS-1$
> 13:02:07 [ERROR] ^^^^^^^^^^^^^^^^^^^^
> 13:02:07 [ERROR] Access restriction: The type 'CreateTextFileChange' is not API (restriction on classpath entry '/mnt/hudson_workspace/workspace/jbosstools-hibernate_master/.repository/p2/osgi/bundle/org.eclipse.jdt.core.manipulation/1.12.100.v20190816-1501/org.eclipse.jdt.core.manipulation-1.12.100.v20190816-1501.jar')
> 13:02:07 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-hibernate_master/sources/orm/plugin/core/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/NewHibernateMappingPreviewPage.java:[246]
> 13:02:07 [ERROR] CreateTextFileChange change = new CreateTextFileChange(filePathTo_Show, str.toString(), null, "hbm.xml"); //$NON-NLS-1$
> 13:02:07 [ERROR] ^^^^^^^^^^^^^^^^^^^^
> 13:02:07 [ERROR] Access restriction: The type 'CreateTextFileChange' is not API (restriction on classpath entry '/mnt/hudson_workspace/workspace/jbosstools-hibernate_master/.repository/p2/osgi/bundle/org.eclipse.jdt.core.manipulation/1.12.100.v20190816-1501/org.eclipse.jdt.core.manipulation-1.12.100.v20190816-1501.jar')
> 13:02:07 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-hibernate_master/sources/orm/plugin/core/org.hibernate.eclipse.jdt.ui/src/org/hibernate/eclipse/jdt/ui/wizards/NewHibernateMappingPreviewPage.java:[246]
> 13:02:07 [ERROR] CreateTextFileChange change = new CreateTextFileChange(filePathTo_Show, str.toString(), null, "hbm.xml"); //$NON-NLS-1$
> 13:02:07 [ERROR] ^^^^^^^^^^^^^^^^^^^^
> 13:02:07 [ERROR] Access restriction: The constructor 'CreateTextFileChange(IPath, String, String, String)' is not API (restriction on classpath entry '/mnt/hudson_workspace/workspace/jbosstools-hibernate_master/.repository/p2/osgi/bundle/org.eclipse.jdt.core.manipulation/1.12.100.v20190816-1501/org.eclipse.jdt.core.manipulation-1.12.100.v20190816-1501.jar')
> 13:02:07 [ERROR] 4 problems (4 errors)
> 13:02:07 [ERROR] -> [Help 1]
> 13:02:07 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.4.0:compile (default-compile) on project org.hibernate.eclipse.jdt.ui: Compilation failure
> 13:02:07 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
> 13:02:07 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
> 13:02:07 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
> 13:02:07 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> 13:02:07 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> 13:02:07 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
> 13:02:07 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> 13:02:07 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> 13:02:07 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 13:02:07 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 13:02:07 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 13:02:07 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 13:02:07 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 13:02:07 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 13:02:07 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 13:02:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 13:02:07 at java.lang.reflect.Method.invoke (Method.java:498)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 13:02:07 Caused by: copied.org.apache.maven.plugin.CompilationFailureException: Compilation failure
> 13:02:07 at copied.org.apache.maven.plugin.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:420)
> 13:02:07 at org.eclipse.tycho.compiler.AbstractOsgiCompilerMojo.execute (AbstractOsgiCompilerMojo.java:293)
> 13:02:07 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134)
> 13:02:07 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
> 13:02:07 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
> 13:02:07 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
> 13:02:07 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> 13:02:07 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> 13:02:07 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51)
> 13:02:07 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> 13:02:07 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> 13:02:07 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 13:02:07 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 13:02:07 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 13:02:07 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 13:02:07 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 13:02:07 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 13:02:07 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 13:02:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 13:02:07 at java.lang.reflect.Method.invoke (Method.java:498)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 13:02:07 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 13:02:07 [ERROR]
> 13:02:07 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 13:02:07 [ERROR]
> 13:02:07 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 13:02:07 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> 13:02:07 [ERROR]
> 13:02:07 [ERROR] After correcting the problems, you can resume the build with the command
> 13:02:07 [ERROR] mvn <goals> -rf :org.hibernate.eclipse.jdt.ui
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
4 years, 9 months