January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16407) Decouple openshift from legacy astools code

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16407?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-16407: ---------------------------------------- Assignee: Rob Stryker (was: Andre Dietisheim) @Rob Stryker: dare to comment? > Decouple openshift from legacy astools code > ------------------------------------------- > > Key: JBIDE-16407 > URL: https://issues.jboss.org/browse/JBIDE-16407 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > > With coming changes to astools, openshift depends on classes that will most likely be deprecated and removed. > Even if its not, openshift is currently using an astools framework that is really geared for servers that can change behavior heavily based on various settings. It's not quite appropriate for openshift which has only one core behavior in terms of publishing 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16411: ------------------------------------- Yes, see fixVersions > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1, 4.2.0.CR1 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16411: ---------------------------------------- Is this version OK to be shipped as part of next JBT and JBDS maintenance release? > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1, 4.2.0.CR1 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15888: ------------------------------------- Radim, can you please test the archetype as per the instructions 2 comments ago? Please ignore the deployment structure issue as JBIDE-15311.has been fixed. You can reassign it to me when you're done, so I can proceed with the update. > Update the Spring Archetype reference > ------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Radim Hopp > Labels: spring > Fix For: 4.1.2.CR1 > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16285) Support for Selenium Server adapter

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16285?page=com.atlassian.jira.plugi... ] Lukáš Fryč commented on JBIDE-16285: ------------------------------------ The use case is support of reusable sessions that: * speeds up test development (the difference is similar to difference between managed and remote Arquillian container modes) * allows in-browser debugging of Selenium tests (again, similar to remote container in debugging mode) ---- We could either: * let an user point to {{selenium-server-standalone.jar}} binary and phantomjs[.exe] binary manually * detect the artifacts on classpath in one of opened projects - here we could depend on presence of Arquillian Drone - so the only dependency between JBoss Tools and Selenium would be Drone API A right solution highly depends on requirements (e.g. minimize maintanance efforts on JBoss Tools side, leveraging classpath resolution, hooking up Drone API), so I would prefer to discuss possibilities once we know whether we want something like this in JBDS or not.. ;-) > Support for Selenium Server adapter > ----------------------------------- > > Key: JBIDE-16285 > URL: https://issues.jboss.org/browse/JBIDE-16285 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Lukáš Fryč > Fix For: LATER > > > Running Selenium Server remotely is integral part of Arquillian Drone workflow for authoring [Selenium/WebDriver/Graphene|https://docs.jboss.org/author/display/ARQGRA2...] based tests (both are part of WFK), leveraging [Drone Reusable Browser Session|https://docs.jboss.org/author/display/ARQGRA2/Using+Drone?_sscc=t...] feature. > The idea is having a Selenium Server as a server adapter in Servers view (similarly to Livereload server adapter). > ---- > Available actions: > * start/stop/restart > * kill all running browsers > ** there is [well-defined (RESTful) API|https://code.google.com/p/selenium/wiki/JsonWireProtocol#/sessions called JsonWireProtocol] for controlling the Selenium Server > * eventually selecting a browser to run tests against (e.g. PhantomJS in (now it is leveraged via arquillian.xml configuration) > Configuration options: > * select [{{selenium-server-standalone.jar}}|http://docs.seleniumhq.org/download/] to run > ** upgrades of Selenium are necessary because of browser-compatibility reasons > ** there could be even an option for downloading newer versions automatically > Advanced features: > * debugging support for PhantomJS browser driver (need to pass [remote debugging arguments|https://github.com/ariya/phantomjs/wiki/Troubleshooting#remote-...]) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15888) Update the Spring Archetype reference

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15888?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15888: -------------------------------- Assignee: Radim Hopp (was: Fred Bricon) > Update the Spring Archetype reference > ------------------------------------- > > Key: JBIDE-15888 > URL: https://issues.jboss.org/browse/JBIDE-15888 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Joshua Wilson > Assignee: Radim Hopp > Labels: spring > Fix For: 4.1.2.CR1 > > Attachments: springmvc-test.xml > > > I updated the Spring Archetype. The one in JBDS/JBIDE needs to point to the new version. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15662) Warning Multiple JAX-RS Activators doesn't disappear

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15662?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-15662. ----------------------------------- Verified in JBDS 8.0.0 Alpha1-v20131212-0740-B25 > Warning Multiple JAX-RS Activators doesn't disappear > ---------------------------------------------------- > > Key: JBIDE-15662 > URL: https://issues.jboss.org/browse/JBIDE-15662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, upstream, webservices > Affects Versions: 4.1.1.Alpha2 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Fix For: 4.2.0.Alpha1 > > > Warning Multiple JAX-RS Activators doesn't disappear after only one activator is present. This bug is probably related to JBIDE-15402 and JBIDE-12860. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16411: ----------------------------------- Priority: Blocker (was: Major) > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.2.CR1, 4.2.0.CR1 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-16411: -------------------------------------- Assignee: Mickael Istria > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 4.1.2.CR1, 4.2.0.CR1 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16411: -------------------------------- Fix Version/s: 4.2.0.CR1 > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Fix For: 4.1.1.CR1, 4.2.0.CR1 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 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 January 2014