[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
[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
[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
[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
[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