March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16719) Maven.resolver().loadPomFromFile(<relative_path>) doesn't work in Arquillian Eclipse

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16719?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16719: --------------------------------------- {quote} Well, I want to make sure that it works from both CI and IDE. If introducing a new property can fix that, I'll do that. However, it would be better if that works without any property. {quote} You should use a property only if it exists and a file can't be found in the current directory. That won't affect CLI tests because they won't set that property. {quote} Why is Arquillan Eclipse actually having problem with currentDirectory != projectDirectory? For test execution it works fine from Eclipse (e.g. in test execution, currentDirectory==projectDirectory). {quote} When you start a test in the project's home directory, it will work. When you launch a new configuration in Eclipse (or run a test via CLI), you can set the current directory. If it is set in the project's home directory, the test will work. See my screencast - http://screencast.com/t/jQka9WXD5. However, when running a deployment method within IDE, the current directory is set when IDE is started. Mostly, it isn't the home directory of a project so that a file can't be found. We can't change the current directory within JVM because it can cause different issues in other threads and starting a new JVM session would significantly decrease performance. {quote} Right, that's something which is set by plugin, so user does not have to fiddle with how it it actually set. If IDE (m2e) has support for the plugin, it would just work. {quote} We can do it, but it is another issue. If a user doesn't use the Maven.configureResolverViaPlugin method, but uses the loadPomFromFile method, a relative path won't be found. > Maven.resolver().loadPomFromFile(<relative_path>) doesn't work in Arquillian Eclipse > ------------------------------------------------------------------------------------ > > Key: JBIDE-16719 > URL: https://issues.jboss.org/browse/JBIDE-16719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > Shrinkwrap resolver solves relative paths using the current working directory. > I don't know a reliable way to change the current working directory so that the deployment method mentioned in JBIDE-16696 can't be analyzed properly. > Since I don't know how to solve the issue, I will add the following problem marker: > "Cannot solve relative paths in the Maven.resolver().loadPomFromFile() method" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16720) Allow easier access to openshift operations from jboss servers

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ] Mark Drilling commented on JBIDE-16720: --------------------------------------- The OpenShift Explorer does improve the connection scenario. I updated the 'how to connect' article https://community.jboss.org/wiki/ProvisionDataVirtualizationOnOpenShiftAn... . Let me know if there is a better way to do this currently. > Allow easier access to openshift operations from jboss servers > -------------------------------------------------------------- > > Key: JBIDE-16720 > URL: https://issues.jboss.org/browse/JBIDE-16720 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.1.Final > Reporter: Mark Drilling > > We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case. > Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push. > Currently, we connect to an OpenShift DV instance like this: > 1) Deploy DV cartridge via OpenShift web console. > 2) Port forward from command line using rhc port-forward > 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective > The issues we observed: > 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo. > 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list. > Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-16440. ------------------------------- Verified with JBDS 7.1.1.GA-v20140303-1841-B672 > Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors > --------------------------------------------------------------------- > > Key: JBIDE-16440 > URL: https://issues.jboss.org/browse/JBIDE-16440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Victor Rubezhny > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.1.2.CR1 > > Attachments: 1640_1.png, 1640_2.png, 1640_3.png, JBossToolsHTMLEditor.png, WTPHTMLEditor.png > > > It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-16440: ----------------------------------------- Yes, Vlado. It works as expected. > Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors > --------------------------------------------------------------------- > > Key: JBIDE-16440 > URL: https://issues.jboss.org/browse/JBIDE-16440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Victor Rubezhny > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.1.2.CR1 > > Attachments: 1640_1.png, 1640_2.png, 1640_3.png, JBossToolsHTMLEditor.png, WTPHTMLEditor.png > > > It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16440) Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16440?page=com.atlassian.jira.plugi... ] Victor Rubezhny resolved JBIDE-16440. ------------------------------------- Resolution: Done > Standard HTML quickfixes aren't shown in JBoss Tools HTML/JSP editors > --------------------------------------------------------------------- > > Key: JBIDE-16440 > URL: https://issues.jboss.org/browse/JBIDE-16440 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Victor Rubezhny > Assignee: Daniel Azarov > Priority: Blocker > Fix For: 4.1.2.CR1 > > Attachments: 1640_1.png, 1640_2.png, 1640_3.png, JBossToolsHTMLEditor.png, WTPHTMLEditor.png > > > It looks like we have overrode quick assist functionality in source viewer configuration that don't includes standard HTML quick fixes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16717) CLONE - Seam 2.3 Portlet deployment error on JPP 6

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16717?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16717: ------------------------------------- [~snjeza] : can you please give us an update on that one? > CLONE - Seam 2.3 Portlet deployment error on JPP 6 > -------------------------------------------------- > > Key: JBIDE-16717 > URL: https://issues.jboss.org/browse/JBIDE-16717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.2.CR1 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.2.Final > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16249) Offline groovy script not working - FileNotFoundException

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16249?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16249: ------------------------------------- I'm pretty sure these are not errors but logs with a wrong qualifier. You can ignore those > Offline groovy script not working - FileNotFoundException > ---------------------------------------------------------- > > Key: JBIDE-16249 > URL: https://issues.jboss.org/browse/JBIDE-16249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0.CR1a B560 > OS X > Groovy Version: 2.1.8 JVM: 1.7.0_45 Vendor: Oracle Corporation OS: Mac OS X (installed via mac ports) > Reporter: Martin Malina > Assignee: Fred Bricon > Fix For: 4.1.2.CR1 > > Attachments: groovy.log > > > I tried to run the offline examples groovy script today (Preferences -> JBoss Tools -> Project Examples -> Offline Support). > When I ran the script I saw a couple of errors along the way, see at the end of email. I was told that it could have to do with WFK 2.4 not being available in the online repo yet. > But ultimately the script failed this exception: > java.io.FileNotFoundException: /Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype > I had jboss nexus and http://maven.repository.redhat.com/techpreview/all/ in my settings.xml. After the script finished, the offline dir was 536M big. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16249) Offline groovy script not working - FileNotFoundException

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16249?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16249: --------------------------------------- I see the same as Radim - with the JBoss Public repo I no longer have missing archetypes, but still a lot of errors in errai archetype build. > Offline groovy script not working - FileNotFoundException > ---------------------------------------------------------- > > Key: JBIDE-16249 > URL: https://issues.jboss.org/browse/JBIDE-16249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0.CR1a B560 > OS X > Groovy Version: 2.1.8 JVM: 1.7.0_45 Vendor: Oracle Corporation OS: Mac OS X (installed via mac ports) > Reporter: Martin Malina > Assignee: Fred Bricon > Fix For: 4.1.2.CR1 > > Attachments: groovy.log > > > I tried to run the offline examples groovy script today (Preferences -> JBoss Tools -> Project Examples -> Offline Support). > When I ran the script I saw a couple of errors along the way, see at the end of email. I was told that it could have to do with WFK 2.4 not being available in the online repo yet. > But ultimately the script failed this exception: > java.io.FileNotFoundException: /Users/rasp/jbossqa/runtimes/zip/offline/workDir/jboss-javaee6-webapp-blank-archetype/my-jboss-javaee6-webapp-blank-archetype > I had jboss nexus and http://maven.repository.redhat.com/techpreview/all/ in my settings.xml. After the script finished, the offline dir was 536M big. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2866) CordovaSim Debugger

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-2866: ----------------------------------- [~maxandersen], sounds great. I will create a separate jira for it > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Priority: Blocker > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.Alpha2 > > Attachments: DevToolsMenu.png > > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16720) Allow easier access to openshift operations from jboss servers

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ] Mark Drilling commented on JBIDE-16720: --------------------------------------- A) Currently the cartridge is here - https://github.com/mdrillin/openshift-cartridge-datavirtualization . The readme has the manifest link you need to deploy as a downloadable cartridge. When the alpha is released there will be a quickstart on the openShift web console. I published a 'how to connect' article - https://community.jboss.org/wiki/ProvisionDataVirtualizationOnOpenShiftAn... Also short modeling use case - https://community.jboss.org/wiki/SalesforceAsARESTServiceUsingDataVirtual... I'll update the first one if we can use OpenShift explorer instead. B) The clone of the project is not large, so that's not the problem. The process of cloning in the wizard is a little cumbersome, requires explaining, and we don't really need it. Also in the Designer perspective we normally work in a ModelExplorer view which only shows the model projects. The git clone creates a separate project in a different view which requires more explaining - not good for demos. C) I wasn't aware of OpenShift explorer, so that is probably the answer. I'll try it. Yes, being able to mark the existing server instance as an openShift application may be an option - like the externally managed option. That may even help to minimize the work that we'd need to do in Teiid Designer to use the OpenShift adapters. Right about the "Cant deploy our downloadable cartridge from the wizard" - cant currently specify the url. I saw the jira, so I knew that was in the works. Also, OpenShift will soon allow users to register their downloadable cartridge. In that case, it should show up in the wizard cartridge list also. > Allow easier access to openshift operations from jboss servers > -------------------------------------------------------------- > > Key: JBIDE-16720 > URL: https://issues.jboss.org/browse/JBIDE-16720 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.1.Final > Reporter: Mark Drilling > > We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case. > Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push. > Currently, we connect to an OpenShift DV instance like this: > 1) Deploy DV cartridge via OpenShift web console. > 2) Port forward from command line using rhc port-forward > 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective > The issues we observed: > 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo. > 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list. > Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 March 2014