January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10061) keys created within the wizard have to be corrected in terms of read-/write-permissions so that they can be used in ssh-add

by Andre Dietisheim (Created) (JIRA)

keys created within the wizard have to be corrected in terms of read-/write-permissions so that they can be used in ssh-add --------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10061 URL: https://issues.jboss.org/browse/JBIDE-10061 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9080) Extend EGit to allow use of git-flow

by George Gastaldi (JIRA)

Extend EGit to allow use of git-flow ------------------------------------- Key: JBIDE-9080 URL: https://issues.jboss.org/browse/JBIDE-9080 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: George Gastaldi It would be nice if JBoss tools added a "Enable Git Flow" extension on GIT Projects so that it would be easier to use git-flow extensions. More info: - http://nvie.com/posts/a-successful-git-branching-model/ - Explanation of the workflow - http://nvie.com/posts/a-git-flow-screencast/ - Screencast showing it in action - http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ - Usage of the workflow in blog post form - https://github.com/nvie/gitflow - Repo of the git flow extension, also contains wiki pages about it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-10112) CLONE - Incremental Publish forcing a push request for openshift when it should not.

by Pavol Srna (Created) (JIRA)

CLONE - Incremental Publish forcing a push request for openshift when it should not. ------------------------------------------------------------------------------------- Key: JBIDE-10112 URL: https://issues.jboss.org/browse/JBIDE-10112 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M4 Reporter: Pavol Srna Assignee: Rob Stryker Fix For: 3.3.0.M4, 3.3.0.Beta1 Every attempt to run as -> run on server creates a publish request, though if no changes have been made it's an incremental request. In the case where there are no changes in the workspace, the request to push is still being initiated even for these incremental publishes. Bad. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10590) maven integration - finalName is ignored

by erik van altena (Created) (JIRA)

maven integration - finalName is ignored ---------------------------------------- Key: JBIDE-10590 URL: https://issues.jboss.org/browse/JBIDE-10590 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Affects Versions: 3.3.0.M5 Reporter: erik van altena Assignee: Fred Bricon I'm not sure if this belongs under the hood of the m2eclipse plugin or JBoss Tools; it seems that m2eclipse could also be to blame if I see what is created in the target directories. Anyway, I'll report the problem just in case it is helpful. I have a simple Mavenized project with a parent pom that manages an ejb, war and ear module that I hot-deploy to a JBoss 7 server (by dragging the ear module to the server runtime). Pretty much the average JEE application structure. When you provide a finalName in for example the maven EAR plugin, that is the name that Maven will give to the produced ear file. JBoss Tools however seems to ignore the finalName and uses the name of the Eclipse project (or the directory name as the module exists on disc) as the deployed name. An example will help to illustrate that: ear module as it exists on disc: myproject-ear finalName mentioned in the ear plugin: myproject Maven will then produce a myproject.ear, JBoss Tools will hot-deploy a myproject-ear.ear This may seem trivial, but this will break code that does manual JDNI lookups as the global jndi name of EJBs changes. Similarly: the bundleFileName property of the Maven ear plugin will alter the resulting filename of packaged child modules and should also be considered by JBoss Tools during publishing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10317) central tells me to check internet conections when the feed is empty

by Max Rydahl Andersen (Created) (JIRA)

central tells me to check internet conections when the feed is empty -------------------------------------------------------------------- Key: JBIDE-10317 URL: https://issues.jboss.org/browse/JBIDE-10317 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.0.Beta1 currently the blogs feed is empty - central says No entries found but then also ask user to check network connections. That makes no difference/sense since it actually did connect - the feed was just empty. Do we not know the difference between there being a network error and empty feed ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-9934) handle the case where a project already exist with the same name

by Max Rydahl Andersen (Created) (JIRA)

handle the case where a project already exist with the same name ---------------------------------------------------------------- Key: JBIDE-9934 URL: https://issues.jboss.org/browse/JBIDE-9934 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 when you import a project via openshift it does not handle the case where a project of the same name already exist. It does warn you but then the wizard "crashes". Two tests: Import the same openshift app twice. or create a project with same name then import openshift app with project with same name. Needs to be tested for both the maven and general import scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

9
13
0 / 0

[JBoss JIRA] (JBIDE-10110) openshift component maven build fails

by Andre Dietisheim (Created) (JIRA)

openshift component maven build fails -------------------------------------- Key: JBIDE-10110 URL: https://issues.jboss.org/browse/JBIDE-10110 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Currently the maven build of the openshift component is failing: {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.jboss.tools.openshift.express.ui 2.3.0.qualifier [ERROR] Missing requirement: org.jboss.tools.openshift.express.ui 2.3.0.qualifier requires 'bundle org.jboss.ide.eclipse.as.egit.core 2.3.0' but it could not be found [ERROR] {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10053) JBoss AS 7 Archetypes misnamed

by Pete Muir (Created) (JIRA)

JBoss AS 7 Archetypes misnamed ------------------------------ Key: JBIDE-10053 URL: https://issues.jboss.org/browse/JBIDE-10053 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Pete Muir Attachments: jboss_central.tiff They are called "JBoss AS 7 Archetypes" Not "Java EE 6 Quickstarts" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

10
30
0 / 0

[JBoss JIRA] (JBIDE-10288) The (freshly created) server adapter wants to publish the freshly imported project to OpenShift - even though there are no changes

by Andre Dietisheim (Created) (JIRA)

The (freshly created) server adapter wants to publish the freshly imported project to OpenShift - even though there are no changes ---------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10288 URL: https://issues.jboss.org/browse/JBIDE-10288 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10173) VPE source navigation: open css file for my custom tag implementation does not work (Ctrl + left mouse button)

by Vitali Yemialyanchyk (Created) (JIRA)

VPE source navigation: open css file for my custom tag implementation does not work (Ctrl + left mouse button) -------------------------------------------------------------------------------------------------------------- Key: JBIDE-10173 URL: https://issues.jboss.org/browse/JBIDE-10173 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Alexey Kazakov Priority: Minor 1) extract 2 demo projects from projects.zip in some folder on you PC intended for such things; a) stopka-ui-base - this project contains implementation of several tags which I use in other project stopka-ui-test. stopka-ui-base contains maven build script so you can easy assemble stopka-ui-base-1.0.1.jar to use it in stopka-ui-test; b) stopka-ui-test - is a jsp demo project, which is use stopka-ui-base as a custom templates library; c) stopka-ui-test\src\main\webapp\WEB-INF\lib\stopka-taglib-0.9.jar - tld description of custom tag for testing; 2) stopka-ui-base - to assemble stopka-ui-base-1.0.1.jar with maven - use: {code} mvn clean install {code} 3) stopka-ui-test\src\main\webapp\WEB-INF\lib contains stopka-taglib-0.9.jar and stopka-ui-base-1.0.1.jar for test purposes you should install these jars into you maven repository - stopka-ui-test\install-ui.sh this script contains necessary instructions: run {code} mvn install:install-file -Dfile=stopka-taglib-0.9.jar -DgroupId=stopka.us -DartifactId=ui-components -Dversion=0.9 -Dpackaging=jar mvn install:install-file -Dfile=stopka-ui-base-1.0.1.jar -DgroupId=stopka.us -DartifactId=stopka-ui-base -Dversion=1.0.1 -Dpackaging=jar {code} from stopka-ui-test\src\main\webapp\WEB-INF\lib as a current directory 4) run Eclipse with JBossTools; 5) import stopka-ui-test\pom.xml as a maven project; 6) open stopka-ui-test\src\main\webapp\test.jspx page with VPE: {code} <stopka:page xmlns="http://www.w3.org/1999/xhtml" xmlns:stopka="http://stopka.us" xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:utils="http://stopka.us/ui/utils"> <jsp:output xmlns:jsp="http://java.sun.com/JSP/Page" omit-xml-declaration="yes"/> <c:set var="bannerType" scope="page" value="simple"/> <html xmlns="http://www.w3.org/1999/xhtml" lang="en-us"> <head> <title>StopKa filemanager</title> <stopka:css file="system/styles/stopka.css" /> <utils:common-head-data/> <stopka:css file="system/styles/filemanager.css" /> </head> <body> <div class="component"> <div class="subitem"> </div> </div> <div class="article"/> <div class="in_stopka"> </div> <div class="in_filemanager"> </div> </body> </html> </stopka:page> {code} 7) try to open css files {code} <stopka:css file="system/styles/stopka.css" /> {code} and {code} <stopka:css file="system/styles/filemanager.css" /> {code} with Ctrl + left mouse button click it does not work; I expect VPE context assist could open css files in any case, i.e. if I make an error: {code} <stopka:dss file="system/styles/filemanager.css" /> {code} VPE context assist should work and should open filemanager.css. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

7
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2012