November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16022) Seam Portlet deployment error on JPP 6

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16022?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-16022: ------------------------------------ Attachment: jpp-seam-server.log > Seam Portlet deployment error on JPP 6 > -------------------------------------- > > Key: JBIDE-16022 > URL: https://issues.jboss.org/browse/JBIDE-16022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1-v20131116-1929-B543, JPP 6.1 (also JPP 6.0) and Seam 2.2.2 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: jpp-seam-server.log > > > Deployment of Seam Portal Project with Seam Portlet ends with error on JPP 6. -- 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-16022) Seam Portlet deployment error on JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16022?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-16022: ------------------------------------- Assignee: Snjezana Peco > Seam Portlet deployment error on JPP 6 > -------------------------------------- > > Key: JBIDE-16022 > URL: https://issues.jboss.org/browse/JBIDE-16022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1-v20131116-1929-B543, JPP 6.1 (also JPP 6.0) and Seam 2.2.2 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.1.1.CR1 > > > Deployment of Seam Portal Project with Seam Portlet ends with error on JPP 6. -- 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-16023) Publishing of exploded projects to remote servers is very slow - Luna

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16023?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-16023. ----------------------------------- Fix Version/s: (was: 4.1.1.CR1) Resolution: Done > Publishing of exploded projects to remote servers is very slow - Luna > --------------------------------------------------------------------- > > Key: JBIDE-16023 > URL: https://issues.jboss.org/browse/JBIDE-16023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > When you try to publish something to a remote server and the deployment is set to exploded archives (i.e. the default), it is very slow. For example the java ee web project from Central takes several minutes. -- 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-12202) Publishing of exploded projects to remote servers is very slow

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12202?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-12202. ----------------------------------- Fix Version/s: (was: 4.2.0.Alpha1) Resolution: Done > Publishing of exploded projects to remote servers is very slow > -------------------------------------------------------------- > > Key: JBIDE-12202 > URL: https://issues.jboss.org/browse/JBIDE-12202 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.CR1 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: jbds.ogg, rse > > > When you try to publish something to a remote server and the deployment is set to exploded archives (i.e. the default), it is very slow. For example the java ee web project from Central takes several minutes. -- 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-12202) Publishing of exploded projects to remote servers is very slow

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12202?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12202. --------------------------------- > Publishing of exploded projects to remote servers is very slow > -------------------------------------------------------------- > > Key: JBIDE-12202 > URL: https://issues.jboss.org/browse/JBIDE-12202 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.CR1 > Reporter: Martin Malina > Assignee: Martin Malina > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: jbds.ogg, rse > > > When you try to publish something to a remote server and the deployment is set to exploded archives (i.e. the default), it is very slow. For example the java ee web project from Central takes several minutes. -- 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-16023) Publishing of exploded projects to remote servers is very slow - Luna

by Martin Malina (JIRA)

Martin Malina created JBIDE-16023: ------------------------------------- Summary: Publishing of exploded projects to remote servers is very slow - Luna Key: JBIDE-16023 URL: https://issues.jboss.org/browse/JBIDE-16023 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Martin Malina Assignee: Martin Malina Priority: Critical Fix For: 4.1.1.CR1, 4.2.0.Alpha1 When you try to publish something to a remote server and the deployment is set to exploded archives (i.e. the default), it is very slow. For example the java ee web project from Central takes several minutes. -- 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-16020) jboss-kitchensink-backbone does not work due to missing deps

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16020?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16020: ------------------------------------- The backbone quickstart requires the WFK 2.4 maven repo, which has not been released yet. It will be available via http://maven.repository.redhat.com/techpreview/all/ by the time JBDS 7.1 is released. Until then you need to manually unzip the 2.4 repo locally and add it to your settings.xml. [~burrsutter] : maybe we should remove the backbone QS from central until WFK is released? Put it back between CR1 and GA? > jboss-kitchensink-backbone does not work due to missing deps > ------------------------------------------------------------ > > Key: JBIDE-16020 > URL: https://issues.jboss.org/browse/JBIDE-16020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Rastislav Wagner > Fix For: 4.1.1.Final > > > backbone example requires org.jboss.bom.wfk.jboss-javaee-6.0-with-tools.2.4.0-redhat-2 but it cannot be found. It is missing in online enterprise repository. -- 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-16020) jboss-kitchensink-backbone does not work due to missing deps

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16020?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-16020: ----------------------------------- Assignee: Fred Bricon > jboss-kitchensink-backbone does not work due to missing deps > ------------------------------------------------------------ > > Key: JBIDE-16020 > URL: https://issues.jboss.org/browse/JBIDE-16020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.1.Final > > > backbone example requires org.jboss.bom.wfk.jboss-javaee-6.0-with-tools.2.4.0-redhat-2 but it cannot be found. It is missing in online enterprise repository. -- 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-16021) Revisit whether file transfer requests can trust rse's isConnected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16021?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16021: ------------------------------------- Linking to previous issue on the topic > Revisit whether file transfer requests can trust rse's isConnected > ------------------------------------------------------------------- > > Key: JBIDE-16021 > URL: https://issues.jboss.org/browse/JBIDE-16021 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server, upstream > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > With the large speed increases in jbt's RSE integration, the new bottleneck is during the beginning of the publish event. > A block of code currently exists as follows: > {code} > boolean isConnected = fileSubSystem != null && fileSubSystem.isConnected(); > String connectionName = RSEUtils.getRSEConnectionName(behaviour.getServer()); > if( isConnected ) { > // The RSE tools might be mistaken here. The user may in fact have lost internet connectivity > NamedRunnableWithProgress run = new NamedRunnableWithProgress("Accessing Remote System Root") { > public Object run(IProgressMonitor monitor) throws CoreException, > SystemMessageException, RuntimeException { > getFileService().getRoots(monitor); > return Status.OK_STATUS; > } > }; > IProgressMonitor childMonitor = AbstractServerToolsPublisher.getSubMon(monitor, 100); > Exception e = RSERemotePublishHandler.wrapRemoteCallStatusTimeLimit(run, "null", "null", null, 15000, childMonitor); > {code} > It would seem strange for the rse's isConnected() method to be incorrect. Investigate whether it is still possible it is incorrect, and file an appropriate upstream bug, or, if no bug, simply remove the lines and improve speed. -- 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-16022) Seam Portlet deployment error on JPP 6

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-16022: --------------------------------------- Summary: Seam Portlet deployment error on JPP 6 Key: JBIDE-16022 URL: https://issues.jboss.org/browse/JBIDE-16022 Project: Tools (JBoss Tools) Issue Type: Bug Components: portal-gatein Affects Versions: 4.1.1.CR1 Environment: JBDS 7.1.0 CR1-v20131116-1929-B543, JPP 6.1 (also JPP 6.0) and Seam 2.2.2 Reporter: Radoslav Rábara Priority: Critical Fix For: 4.1.1.CR1 Deployment of Seam Portal Project with Seam Portlet ends with error on JPP 6. -- 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 November 2013