March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16946) JBoss buzz: File not found: http://planet.jboss.org/feeds/buzz

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16946?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16946: ------------------------------- Attachment: jboss-buzz.png > JBoss buzz: File not found: http://planet.jboss.org/feeds/buzz > -------------------------------------------------------------- > > Key: JBIDE-16946 > URL: https://issues.jboss.org/browse/JBIDE-16946 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Fix For: 4.2.0.Beta1 > > Attachments: jboss-buzz.png > > -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14765) Support <weld:exclude>

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14765?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-14765. ------------------------------------ verified in JBDS 8.0.0 Beta1-v20140330-1929-B79 > Support <weld:exclude> > ---------------------- > > Key: JBIDE-14765 > URL: https://issues.jboss.org/browse/JBIDE-14765 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi-extensions > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > See http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html > 1. Import test project jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1 > 2. Open Java source file src/test/TestExcluded.java and src/META-INF/beans.xml > Check satisfied and unsatisfied dependencies: > - @Inject Bean1 bean1 - is unsatisfied (has marker 'No bean is eligible for injection') > because beans.xml contains <weld:exclude name="exclude.p1.Bean1"/> > - @Inject Bean2 bean2 - is satisfied (there is open-on for injected bean Bean2) > - @Inject Bean3 bean3 - is unsatisfied > because of <weld:exclude name="exclude.p2.*"/> > - @Inject Bean4 bean4 - is satisfied > because package "exclude.p2.p3" is not excluded by <weld:exclude name="exclude.p2.*"/> > - @Inject Bean5 bean5 and @Inject Bean6 bean6 are both unsatisfied > because of <weld:exclude name="exclude.p4.**"> which is active as all restrictions weld:if-class-available are fulfilled > - @Inject Bean7 bean7 - is satisfied > because <weld:exclude name="exclude.p6.**"> is inactive. > Supported use-cases for <weld:exclude> are limited to use-cases for <exclude> in CDI, which does not support pattern, symbol ?, use of symbol * other than in suffixes .* and .**, 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16866) Publishing on AS7/wf servers too slow, does not need to mess with deployment scanners

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16866?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-16866: --------------------------------------- @fbricon, I opened JBIDE-16945 to see if/how the LiveReload part of the workflow can be improved. > Publishing on AS7/wf servers too slow, does not need to mess with deployment scanners > ------------------------------------------------------------------------------------- > > Key: JBIDE-16866 > URL: https://issues.jboss.org/browse/JBIDE-16866 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.Beta1 > > > Publishing a single file on WF8 takes at least 2 to 3 seconds before LiveReload refreshes the browser (I experienced worse turnarounds during EclipseCon demos): > http://screencast.com/t/kQj2kXev3Gyf > If you manually modify the file in the deployment directory on the server, changes are picked much faster (< 1sec), so it means the whole publishing part within eclipse takes a tremendous amount of time. > Every time a file is saved in the workspace, the following line shows up in the server log : > {quote} > INFO [org.jboss.as.server.deployment.scanner] (management-handler-thread - 12) JBAS015012: Started FileSystemDeploymentService for directory D:\Dev\servers\wildfly-8.0.0.Final\standalone\deployments > {quote} > This service invocation (which takes at least 1 sec to show up in the log) should be invoked only once, during server startup, instead of every time a file is published -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16945) See if/how refresh delay can be reduced

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-16945: ------------------------------------- Summary: See if/how refresh delay can be reduced Key: JBIDE-16945 URL: https://issues.jboss.org/browse/JBIDE-16945 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: livereload Affects Versions: 4.2.0.Beta1 Reporter: Xavier Coulon Fix For: 4.2.0.Beta2 In relation with JBIDE-16866, see if the ~500ms reported by [~fbricon] can be reduced. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16939) OpenShift application creation should not lock the UI while waiting for DNS to propagate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16939?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16939: ------------------------------------------ [~lincolnthree] Still puzzled where you experience this and what tells you that it is DNS related. All tasks are afaik done in background jobs. Any chance you screencast what you exactly mean? > OpenShift application creation should not lock the UI while waiting for DNS to propagate > ---------------------------------------------------------------------------------------- > > Key: JBIDE-16939 > URL: https://issues.jboss.org/browse/JBIDE-16939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Lincoln Baxter III > > After completing the OpenShift -> New Application wizard, the UI locks while Eclipse waits for the OpenShift operation to complete. Many OpenShift operations (including application creation) can take quite a while, and it should be able to be moved to the background, allowing the user to continue working while waiting. -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2838) OpenShift Usability

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2838: ----------------------------------- Fix Version/s: 8.0.0.GA > OpenShift Usability > ------------------- > > Key: JBDS-2838 > URL: https://issues.jboss.org/browse/JBDS-2838 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Priority: Blocker > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.GA > > > This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069) -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2868: ----------------------------------- Fix Version/s: 8.0.x > Support multiple protocols when talking to OpenShift servers > ------------------------------------------------------------ > > Key: JBDS-2868 > URL: https://issues.jboss.org/browse/JBDS-2868 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Andre Dietisheim > Fix For: 8.0.x > > > The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions. -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2864: ----------------------------------- Fix Version/s: 8.0.0.Beta2 > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.Beta2 > > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2851) Team Usability

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2851: ----------------------------------- Fix Version/s: 8.0.x > Team Usability > -------------- > > Key: JBDS-2851 > URL: https://issues.jboss.org/browse/JBDS-2851 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Priority: Critical > Labels: QE_JBDS80_needinfo > Fix For: 8.0.x > > > It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as > - how to integrate with CVS, SVN, Git > - how to "import" a Maven-based project from SCM > "Check out Maven Projects from SCM" has misfired for some users > - how to "checkin" changes back to the SCM > To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things. > For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14818: ------------------------------------- Fix Version/s: 4.2.x > Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Priority: Critical > Labels: server_adapter_editor > Fix For: 4.2.x > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- 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

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