July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17800) Compile errors in birt

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17800?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17800. --------------------------------- Birt is now building fine: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... Closing. > Compile errors in birt > ---------------------- > > Key: JBIDE-17800 > URL: https://issues.jboss.org/browse/JBIDE-17800 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt > Affects Versions: 4.2.0.Beta3 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > The errors are caused by the changes in the hibernate component. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13283: --------------------------------------- [~nickboldt] can you check all is done here and close the JIRA? Thanks! > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Beta2 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3014) On Mac Maverick JVM shared library points to wrong directory

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3014?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3014. ------------------------------- I checked the scenario when the installer is launched by double-clicking in Finder. The default java in that case is the JRE as stated in this JIRA. So the installer now says this java is not supported and you need to select a different java installation. BTW, [~maxandersen], a few days ago you complained about this exact error - you didn't understand why it was rejecting that java. Well, it was exactly a result of this JIRA :) It's true that it doesn't say why that java cannot be used, but I'm not sure what better wording to have there. Verified in JBDS 8.0.0.Beta3c B194 > On Mac Maverick JVM shared library points to wrong directory > ------------------------------------------------------------ > > Key: JBDS-3014 > URL: https://issues.jboss.org/browse/JBDS-3014 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Environment: Mac on Maverick > Reporter: Robb Greathouse > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Beta3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The JVM shared library "/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/../lib/server/libjvm.dylib" > does not contain the JNI_CreateJavaVM symbol. > This prevents it from starting. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3025) Installer duplicates last folder in path causing errors (Mac OS X)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3025?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3025. ------------------------------- There is no folder duplication now, but sometimes you can end up with the parent folder. I'm closing this JIRA and created a new one JBDS-3109 Verified in JBDS 8.0.0.Beta3c B194 > Installer duplicates last folder in path causing errors (Mac OS X) > ------------------------------------------------------------------ > > Key: JBDS-3025 > URL: https://issues.jboss.org/browse/JBDS-3025 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta1 > Reporter: Michelle Murray > Assignee: Denis Golovin > Fix For: 8.0.0.Beta3 > > Attachments: Installer_jrelocationerror.png > > > Mac OS X Mavericks > Universal installer, step 4 - choose JVM: > * Click 'Specific Java JVM' > * Click Browse to locate JDK or JRE > * Navigate to find folder and click ok in file browser > the last folder is added twice to the displayed path > In most cases this path now doesn't exist and causes error messages to this extent. > !Installer_jrelocationerror.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3109) OS X: Browse for Java VM returns parent folder from the selected one

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3109?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3109: -------------------------------- Fix Version/s: 8.0.0.CR1 > OS X: Browse for Java VM returns parent folder from the selected one > -------------------------------------------------------------------- > > Key: JBDS-3109 > URL: https://issues.jboss.org/browse/JBDS-3109 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta3 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > > This is a follow up of JBDS-3025 > When you browse for Java VM during installation on mac, there are two use cases: > a) Either you get to the parent folder and click the Home directory and and the push the Select button. In this case the parent will show up in the field, e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents (note the Home missing at the end). > b) Or you browse all the way to the final directory, i.e. you double click Home when you're in the parent folder. Then, without selecting anything, you can click the Select button. This way, you will end up with e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home in the field. This is expected. > So scenario a) doesn't work as it should. > I would like to add, that there is a similar thing in Step 5 - Select Platforms and Servers. Here you can add paths with runtimes. In this case, both a) and b) scenarios work correctly. So perhaps you can check the code used there and use that? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3109) OS X: Browse for Java VM returns parent folder from the selected one

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3109?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3109: -------------------------------- CDW qa_ack: + (was: ?) > OS X: Browse for Java VM returns parent folder from the selected one > -------------------------------------------------------------------- > > Key: JBDS-3109 > URL: https://issues.jboss.org/browse/JBDS-3109 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta3 > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > > This is a follow up of JBDS-3025 > When you browse for Java VM during installation on mac, there are two use cases: > a) Either you get to the parent folder and click the Home directory and and the push the Select button. In this case the parent will show up in the field, e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents (note the Home missing at the end). > b) Or you browse all the way to the final directory, i.e. you double click Home when you're in the parent folder. Then, without selecting anything, you can click the Select button. This way, you will end up with e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home in the field. This is expected. > So scenario a) doesn't work as it should. > I would like to add, that there is a similar thing in Step 5 - Select Platforms and Servers. Here you can add paths with runtimes. In this case, both a) and b) scenarios work correctly. So perhaps you can check the code used there and use that? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3109) OS X: Browse for Java VM returns parent folder from the selected one

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3109?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3109: -------------------------------- Environment: JBDS 8.0.0.Beta3c B194 OS X 10.9 Mavericks > OS X: Browse for Java VM returns parent folder from the selected one > -------------------------------------------------------------------- > > Key: JBDS-3109 > URL: https://issues.jboss.org/browse/JBDS-3109 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta3 > Environment: JBDS 8.0.0.Beta3c B194 > OS X 10.9 Mavericks > Reporter: Martin Malina > Assignee: Denis Golovin > Fix For: 8.0.0.CR1 > > > This is a follow up of JBDS-3025 > When you browse for Java VM during installation on mac, there are two use cases: > a) Either you get to the parent folder and click the Home directory and and the push the Select button. In this case the parent will show up in the field, e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents (note the Home missing at the end). > b) Or you browse all the way to the final directory, i.e. you double click Home when you're in the parent folder. Then, without selecting anything, you can click the Select button. This way, you will end up with e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home in the field. This is expected. > So scenario a) doesn't work as it should. > I would like to add, that there is a similar thing in Step 5 - Select Platforms and Servers. Here you can add paths with runtimes. In this case, both a) and b) scenarios work correctly. So perhaps you can check the code used there and use that? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3109) OS X: Browse for Java VM returns parent folder from the selected one

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3109?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3109: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > OS X: Browse for Java VM returns parent folder from the selected one > -------------------------------------------------------------------- > > Key: JBDS-3109 > URL: https://issues.jboss.org/browse/JBDS-3109 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta3 > Reporter: Martin Malina > Assignee: Denis Golovin > > This is a follow up of JBDS-3025 > When you browse for Java VM during installation on mac, there are two use cases: > a) Either you get to the parent folder and click the Home directory and and the push the Select button. In this case the parent will show up in the field, e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents (note the Home missing at the end). > b) Or you browse all the way to the final directory, i.e. you double click Home when you're in the parent folder. Then, without selecting anything, you can click the Select button. This way, you will end up with e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home in the field. This is expected. > So scenario a) doesn't work as it should. > I would like to add, that there is a similar thing in Step 5 - Select Platforms and Servers. Here you can add paths with runtimes. In this case, both a) and b) scenarios work correctly. So perhaps you can check the code used there and use that? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3109) OS X: Browse for Java VM returns parent folder from the selected one

by Martin Malina (JIRA)

Martin Malina created JBDS-3109: ----------------------------------- Summary: OS X: Browse for Java VM returns parent folder from the selected one Key: JBDS-3109 URL: https://issues.jboss.org/browse/JBDS-3109 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 8.0.0.Beta3 Reporter: Martin Malina Assignee: Denis Golovin This is a follow up of JBDS-3025 When you browse for Java VM during installation on mac, there are two use cases: a) Either you get to the parent folder and click the Home directory and and the push the Select button. In this case the parent will show up in the field, e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents (note the Home missing at the end). b) Or you browse all the way to the final directory, i.e. you double click Home when you're in the parent folder. Then, without selecting anything, you can click the Select button. This way, you will end up with e.g. /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home in the field. This is expected. So scenario a) doesn't work as it should. I would like to add, that there is a similar thing in Step 5 - Select Platforms and Servers. Here you can add paths with runtimes. In this case, both a) and b) scenarios work correctly. So perhaps you can check the code used there and use that? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17536: --------------------------------------- [~nickboldt] said: {quote} Since I don't want to move staging folders while QE is using them, I won't be moving the contents in /updates/staging/ until we start on CR1. {quote} Once we're done with Beta3 (i.e. it's released), you're free to do this. > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014