May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19791) Switch OpenShift plugins to require JDK7

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19791?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19791: ------------------------------------- Sprint: Sprint #3 May 2015 > Switch OpenShift plugins to require JDK7 > ---------------------------------------- > > Key: JBIDE-19791 > URL: https://issues.jboss.org/browse/JBIDE-19791 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compilein Eclipse. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19791) Switch OpenShift plugins to require JDK7

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19791?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19791: ------------------------------------- Description: With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compilein Eclipse. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7. (was: With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compile. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7.) > Switch OpenShift plugins to require JDK7 > ---------------------------------------- > > Key: JBIDE-19791 > URL: https://issues.jboss.org/browse/JBIDE-19791 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compilein Eclipse. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19791) Switch OpenShift plugins to require JDK7

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19791: ---------------------------------------- Summary: Switch OpenShift plugins to require JDK7 Key: JBIDE-19791 URL: https://issues.jboss.org/browse/JBIDE-19791 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.0.Beta1 With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compile. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19790) Limit the possible Hibernate runtime choices to only the supported ones in the JPA generation dialogs

by Koen Aers (JIRA)

Koen Aers created JBIDE-19790: --------------------------------- Summary: Limit the possible Hibernate runtime choices to only the supported ones in the JPA generation dialogs Key: JBIDE-19790 URL: https://issues.jboss.org/browse/JBIDE-19790 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Affects Versions: 4.3.0.Alpha2 Reporter: Koen Aers - Create a maven project - Add hibernate-entitymanager dependencies (I used version 4.3.9.Final) - Convert into JPA project: choose JPA 2.1 with the Hibernate platform -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19757: --------------------------------------------- A) yes so we still need the separate url B) Not following you. You want us to put alpha, beta, etc. on the url we used for stable releases ? How do you then do milestones of the updates after the first GA/Final ? Note, even if we did do it for jbosstools main site we would still need the url used for webtools to *stay* on the stable content so its a chicken and egg problem and we just accept that pre-first-Final WTP points to an ever moving updatesite, after GA it is locked down together with jbosstools stable. > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19789) User Defined Modules are not loading in Eclipse

by Raj Kumar (JIRA)

Raj Kumar created JBIDE-19789: --------------------------------- Summary: User Defined Modules are not loading in Eclipse Key: JBIDE-19789 URL: https://issues.jboss.org/browse/JBIDE-19789 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: java 1.8, wildfly 8.1 , Mysql Reporter: Raj Kumar Hi , i want to load the Application server Libraries in Java Build Path in eclipse, i have 5 applications in eclipse which shares common libraries, i can't put all the libraries in each project lib folder, so i want to add the libraries in Wildfly Application server using modules. This is my module.xml file add added the lib at WILDFLY_HOME/modules/system/layers/base/com/mysql/main/mysql-connector-java-5.1.23-bin.jar <?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.1" name="com.mysql"> <resources> <resource-root path="mysql-connector-java-5.1.23-bin.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="javax.transaction.api"/> </dependencies> </module> After Restarting the server,this module is not loading in Eclipse Build path. Can any one knows what wrong with this modules ? In Wildfly i have some predefined modules, those are loading in build path successfully, but user-defined modules are not loading ? why ? - See more at: https://developer.jboss.org/thread/257825?sr=inbox#sthash.MWLbzbco.dpuf -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19776: --------------------------------------------- Please see https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11808.html Notice this line: "Remaining ACTION is for the EPP packages to please replace any “org.eclipse.tcf.te” feature references with “org.eclipse.tm.terminal.feature”" So seems like we either do the same or at least go into this this new feature and see which of the plugins in those we need. > Create and use Mars M7 target-platform > -------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19757: ---------------------------------------- I wrote in a previous comment that this couldn't be completed before Mars release anyway so that we'll have to stick to webtools-site for a few months at least. A) that's something we'll only be able to really check after the Beta1 milestone release B) For webtools, we currently have a static URL that doesn't change from first milestone to last service release ( http://download.jboss.org/jbosstools/updates/webtools/mars/ ). We could imagine a similar one for JBoss Tools, so we wouldn't need to change our URLs. C) That's a good point. I don't have any good alternative to suggest. > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19757: --------------------------------------------- For the following reasons: A) we don't know yet if the performance is acceptable. By having the composite site we can decide later which it is. B) we need to give a url to them *Before* we actually release something to Mars, thus for a bit it will composite to /development, later on to /stable. If we give them the direct site that will always have to be /stable. By having the composite site we can control where it points over time. C) we can track via access logs how the server adapter gets installed. By having the composite site we can see how often the site at least is checked from server wizards. I think all of the above combined, but A and B especially means it makes sense to keep the indirection. > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18672: ------------------------------------- Seems that the issue was fixed with a brand-new web kit - can reproduce neiter against jdk 8u60 nor jdk9. Waiting for official 8u60 release and then resolving > cannot run ionic tabs (the default) app with cordovasim > ------------------------------------------------------- > > Key: JBIDE-18672 > URL: https://issues.jboss.org/browse/JBIDE-18672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.Final > Environment: Mac OS X, JavaFX > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.3.0.Beta1 > > > run: > ionic start ionic-demo > import ionic-demo > run as > cordova sim > try use the app, click back. > Two issues: > 1) cordova sim complains about app.appexit not being supported > 2) when trying to click do not show again I get the following in the cordovasim error log: > Outstanding resource locks detected: > ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total > 84 total resources being managed > average resource age is 15.1 frames > 0 resources at maximum supported age (0.0%) > 16 resources marked permanent (19.0%) > 17 resources have had mismatched locks (20.2%) > 17 resources locked (20.2%) > 30 resources contain interesting data (35.7%) > 0 resources disappeared (0.0%) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015