October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15596) Report JVM name in Usage

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15596?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15596: --------------------------------------------- if vm.name reports Oracle for OpenJDK then that won't help. But yes, having jvm name reported somewhere would be interesting. Adding it into Flash Version would make that field even harder to use though. What does java.vm.name actually report for the various VM's is what need to find out and then where in GA request we could put it. > Report JVM name in Usage > ------------------------ > > Key: JBIDE-15596 > URL: https://issues.jboss.org/browse/JBIDE-15596 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > Priority: Optional > > It appears that having statistics about the used JVM (Oracle HotSpot, OpenJDK...) would be useful for JBoss Tools, but also for other runtime projects. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14018) Default OpenShift commit message should be possible to override

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14018?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14018: ---------------------------------------- Summary: Default OpenShift commit message should be possible to override (was: OpenShift commit message references JBoss Tools) > Default OpenShift commit message should be possible to override > --------------------------------------------------------------- > > Key: JBIDE-14018 > URL: https://issues.jboss.org/browse/JBIDE-14018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: commit_from_JBT.png, Customized Git Commit on Publish.png > > > In Servers tab, when you right-click on an OpenShift server adapter and click Publish, an automatic commit message is generated: "Commit from JBoss Tools". > This message references JBoss Tools - for JBDS it should mention JBDS. I realise it is difficult to have a different message for JBT and JBDS so I guess the message needs to be changed to not reference either. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14018) OpenShift commit message references JBoss Tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14018?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14018: --------------------------------------------- [~erbarber] I think you are seeing this a bit too black and white :) The only time JBoss Tools adds this commit message is if you say Yes to having the server adapter commit the uncommitted code it finds before it is doing a Push. This is a *completely* optional feature. You can simply say No and instead use normal egit commit features where you specify all the details you want, including even doing the push directly if you wish too. Doing this doesn't even require more clicks - its simply just using "Team > Commit" on the project. Using this also allows you to add *new* files - something that the "commit before push" we currently provide does not. Thus I find it very harsh and unfounded to state "unacceptable by the development teams and many developers are refusing to use the Eclipse plugins that you've provided". You can simply use *all* the features of git available in eclipse to do this fine grained commit and cleanup of history you would like - the tools were built to allow for this flexibility. That said, I agree we should allow for custom message to be set when doing commits BUT just be aware this does not cover the case where there are actually *new* files to add - in this case you still have to go use "Team > Commit" or "Team > Add" I'm going to change this jira description to be about making this message configurable - but please do realize you have already eclipse UI for doing this. > OpenShift commit message references JBoss Tools > ----------------------------------------------- > > Key: JBIDE-14018 > URL: https://issues.jboss.org/browse/JBIDE-14018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: commit_from_JBT.png, Customized Git Commit on Publish.png > > > In Servers tab, when you right-click on an OpenShift server adapter and click Publish, an automatic commit message is generated: "Commit from JBoss Tools". > This message references JBoss Tools - for JBDS it should mention JBDS. I realise it is difficult to have a different message for JBT and JBDS so I guess the message needs to be changed to not reference either. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15607) openshift-java-client: no ssh session available to get environment properties

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15607?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15607: ----------------------------------- Component/s: openshift > openshift-java-client: no ssh session available to get environment properties > ----------------------------------------------------------------------------- > > Key: JBIDE-15607 > URL: https://issues.jboss.org/browse/JBIDE-15607 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Syed Iqbal > Priority: Optional > > The ssh session is null when trying to retrieve the environment properties. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15607) openshift-java-client: no ssh session available to get environment properties

by Syed Iqbal (JIRA)

Syed Iqbal created JBIDE-15607: ---------------------------------- Summary: openshift-java-client: no ssh session available to get environment properties Key: JBIDE-15607 URL: https://issues.jboss.org/browse/JBIDE-15607 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.2.0.Alpha1 Reporter: Syed Iqbal Priority: Optional The ssh session is null when trying to retrieve the environment properties. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15606: ---------------------------------- Summary: build tool to regenerate component update sites from published JBT aggregate Key: JBIDE-15606 URL: https://issues.jboss.org/browse/JBIDE-15606 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.1.1.Alpha2 Reporter: Nick Boldt Fix For: 4.1.1.Beta1 When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-15606: ---------------------------------- Assignee: Nick Boldt > build tool to regenerate component update sites from published JBT aggregate > ---------------------------------------------------------------------------- > > Key: JBIDE-15606 > URL: https://issues.jboss.org/browse/JBIDE-15606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. > We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. > This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15605) Validation problem in faces-config.xml for JSF 2.2 projects

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15605?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15605: ----------------------------------------------- I failed to add javaee_7.xsd to catalog. But since WTP adds web-facesconfig_2_2.xsd, let's just remove our file from the catalog. > Validation problem in faces-config.xml for JSF 2.2 projects > ----------------------------------------------------------- > > Key: JBIDE-15605 > URL: https://issues.jboss.org/browse/JBIDE-15605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > > 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet). > 2. There is an error in problems view: > Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation? > BTW, http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd is already registered in XML Catalog by WTP. There is no need to keep our own version in XML Catalog: > {code} > Entry element: URI > Location: dtdsAndSchemas/web-facesconfig_2_2.xsd in jar file home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar > URI: jar:file:/home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar!/dtdsAndSchemas/web-facesconfig_2_2.xsd > Key type: Namespace name > Key: http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15605) Validation problem in faces-config.xml for JSF 2.2 projects

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15605?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15605: ----------------------------------- Description: 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet). 2. There is an error in problems view: Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..." Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation? BTW, http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd is already registered in XML Catalog by WTP. There is no need to keep our own version in XML Catalog: {code} Entry element: URI Location: dtdsAndSchemas/web-facesconfig_2_2.xsd in jar file home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar URI: jar:file:/home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar!/dtdsAndSchemas/web-facesconfig_2_2.xsd Key type: Namespace name Key: http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd {code} was: 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet). 2. There is an error in problems view: Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..." Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation? > Validation problem in faces-config.xml for JSF 2.2 projects > ----------------------------------------------------------- > > Key: JBIDE-15605 > URL: https://issues.jboss.org/browse/JBIDE-15605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > > 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet). > 2. There is an error in problems view: > Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..." > Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation? > BTW, http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd is already registered in XML Catalog by WTP. There is no need to keep our own version in XML Catalog: > {code} > Entry element: URI > Location: dtdsAndSchemas/web-facesconfig_2_2.xsd in jar file home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar > URI: jar:file:/home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar!/dtdsAndSchemas/web-facesconfig_2_2.xsd > Key type: Namespace name > Key: http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15605) Validation problem in faces-config.xml for JSF 2.2 projects

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-15605: -------------------------------------- Summary: Validation problem in faces-config.xml for JSF 2.2 projects Key: JBIDE-15605 URL: https://issues.jboss.org/browse/JBIDE-15605 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.2.0.Alpha1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet). 2. There is an error in problems view: Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..." Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation? -- 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, 6 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 October 2013