October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15198) Move away from sonatype aether to eclipse aether

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15198?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15198: --------------------------------------------- p.s. is arquillian the *only* place aether is used ? > Move away from sonatype aether to eclipse aether > ------------------------------------------------ > > Key: JBIDE-15198 > URL: https://issues.jboss.org/browse/JBIDE-15198 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, project-examples, testing-tools > Affects Versions: 4.1.0.CR1 > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > With Maven 3.1.0, Sonatype Aether has been replaced with Eclipse Aether. m2e 1.5.0 will soon do the same. Currently, I've found that at least the following plugins have a dependency to the Sonatype version : > - org.jboss.tools.arquillian.core > - org.jboss.tools.maven.project.examples > - org.jboss.tools.maven.ui > Ideally the next m2e version won't embed the jars directly (but this is not guaranteed). Aether is available from this p2 repo : http://download.eclipse.org/aether/aether-core/milestones -- 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-15198) Move away from sonatype aether to eclipse aether

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15198?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15198: ---------------------------------------- Fix Version/s: 4.1.1.Beta1 4.2.0.Alpha1 (was: 4.2.x) > Move away from sonatype aether to eclipse aether > ------------------------------------------------ > > Key: JBIDE-15198 > URL: https://issues.jboss.org/browse/JBIDE-15198 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, project-examples, testing-tools > Affects Versions: 4.1.0.CR1 > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > > With Maven 3.1.0, Sonatype Aether has been replaced with Eclipse Aether. m2e 1.5.0 will soon do the same. Currently, I've found that at least the following plugins have a dependency to the Sonatype version : > - org.jboss.tools.arquillian.core > - org.jboss.tools.maven.project.examples > - org.jboss.tools.maven.ui > Ideally the next m2e version won't embed the jars directly (but this is not guaranteed). Aether is available from this p2 repo : http://download.eclipse.org/aether/aether-core/milestones -- 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] (JBDS-2783) Increase default EGit/OpenShift timeout

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2783?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2783: ------------------------------------------- note - this wouldn't work for JBDS Bring-your-own-eclipse. I would prefer we fix this in our interaction with git api instead so it works everywhere. [~adietish] is that possible ? (and wasn't there a jbide on this that should be linked ?) > Increase default EGit/OpenShift timeout > --------------------------------------- > > Key: JBDS-2783 > URL: https://issues.jboss.org/browse/JBDS-2783 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift, p2-product > Affects Versions: 7.0.0.GA, 7.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > > Default value for EGit and OpenShift is 30 seconds. In most cases, this value is too short and isn't enoguh for a successful deploy of a dummy JEE app inside JBDS, which leads to a poor first impression. > As we can control the preferences in JBDS (with installer), I suggest we should make default to 60 which seems to behave better. -- 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-15374) Create target platform from Luna M1 or M2 dependencies

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15374?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15374: ---------------------------------------- More about org.eclipse.osgi.compatibility.state at https://bugs.eclipse.org/bugs/show_bug.cgi?id=407097 > Create target platform from Luna M1 or M2 dependencies > ------------------------------------------------------ > > Key: JBIDE-15374 > URL: https://issues.jboss.org/browse/JBIDE-15374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Create a new target platform for use with JBoss Tools 4.2 (Luna). Should be versioned 4.40.x. > Luna schedule: > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule -- 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-15614) Add support for EAP 6.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15614: ------------------------------------- Max's suggestion here is 6.1+ which makes perfect sense. AS 6.x encompasses all of 6 stream (6.0, 6.1, etc) whereas EAP 6.1+ would exclude 6.0. Simple and elegant solution. Committed. > Add support for EAP 6.2 > ----------------------- > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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-15614) Add support for EAP 6.2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-15614: ------------------------------------------- Assignee: Max Rydahl Andersen (was: Rob Stryker) > Add support for EAP 6.2 > ----------------------- > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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-15614) Add support for EAP 6.2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15614: ------------------------------------- I've merged in the current patches with only a slight change. It is not appropriate to add an eap6.2 server type until we discover incompatibilities that require it. So if we see anything that breaks, management, xpaths, server startup, publish, anything. Until we see anything like that, we won't add a 6.2 server type. Though we may wish to consider renaming the eap6.1 server and runtime types to 6.x (?) If we feel confident there won't be any breakages, then we may consider doing that. [~maxandersen] - is renaming eap6.1 server nad runtime types to 6.x appropriate? We have an existing 6.0. > Add support for EAP 6.2 > ----------------------- > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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-15374) Create target platform from Luna M1 or M2 dependencies

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15374?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15374: --------------------------------------------- Looks cool - any idea what those three new plugins does ? I can guess that jgit.archive and commons.compress is for the somewhat new feature of jgit handling archived git repositories. But what is compatibility.state for ? something we need, should be observant about ? i.e. is there some behavior that changes in Luna that could affect us ? > Create target platform from Luna M1 or M2 dependencies > ------------------------------------------------------ > > Key: JBIDE-15374 > URL: https://issues.jboss.org/browse/JBIDE-15374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Create a new target platform for use with JBoss Tools 4.2 (Luna). Should be versioned 4.40.x. > Luna schedule: > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule -- 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-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13869 at 10/7/13 8:35 AM: ----------------------------------------------------------------- When https://bugs.eclipse.org/bugs/show_bug.cgi?id=386988 gets fixed, it will be necessary to apply https://github.com/jbosstools/jbosstools-build/pull/111 if we want to be able to run surefire plugin on existing application. By the way, I'm not sure forcing the testApplication/testProduct to their default values adds anything useful to the configuration. I guess it could be removed now. was (Author: mickael_istria): When https://bugs.eclipse.org/bugs/show_bug.cgi?id=386988 gets fixed, it will be necessary to apply https://github.com/jbosstools/jbosstools-build/pull/108 if we want to be able to run surefire plugin on existing application. By the way, I'm not sure forcing the testApplication/testProduct to their default values adds anything useful to the configuration. I guess it could be removed now. > Find a way to run testsuite against existing builds but with different TP without requiring publishing > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13869 > URL: https://issues.jboss.org/browse/JBIDE-13869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again. > Possible options: > 1) Create new testsuite that depends on all other testsuites and run them in surefire test. > 2) use something else than surefire to run the already built testsuites. -- 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-15618) Add server mode for management; all tasks performed over management api

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15618?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15618: -------------------------------- Fix Version/s: 4.2.0.Alpha1 > Add server mode for management; all tasks performed over management api > ----------------------------------------------------------------------- > > Key: JBIDE-15618 > URL: https://issues.jboss.org/browse/JBIDE-15618 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > A mode for management-specific behavior. This mode would be a third mode, similar to 'local' or 'rse'. -- 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