[JBoss JIRA] (JBIDE-21166) AJDT can't install against 4.4/Neon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21166?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21166 at 6/22/16 10:22 AM:
--------------------------------------------------------------
I removed the org.springframework.ide.eclipse.ajdt.feature from our Central connectors in order to make the rest of org.springframework.ide.eclipse.*.feature installable from Central.
So yes, this is expected - for jbosstools 4.4.0 / devstudio 10.0.0, we don't support org.springframework.ide.eclipse.ajdt.feature installation from Central.
If you feel we should add the feature back, eg., from http://download.jboss.org/jbosstools/updates/requirements/springide/3.7.3... please open a new JIRA linked to this one and set its fixversion for 4.4.1.*
was (Author: nickboldt):
I removed the org.springframework.ide.eclipse.ajdt.feature from our Central connectors in order to make the rest of org.springframework.ide.eclipse.*.feature installable from Central.
So yes, this is expected - for jbosstools 4.4.0 / devstudio 10.0.0, we don't support org.springframework.ide.eclipse.ajdt.feature installation from Central.
> AJDT can't install against 4.4/Neon
> -----------------------------------
>
> Key: JBIDE-21166
> URL: https://issues.jboss.org/browse/JBIDE-21166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.4.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: p2diff-summary.txt, p2diff.txt, spring-ide373-all-features-except-ajdt-and-roo.png
>
>
> AJDT fails to install on JBoss Tools 4.4/Eclipse Neon
> Various contraint show that AJDT is not compatible with newer JDT.
> {code}
> !ENTRY org.eclipse.equinox.p2.operations 4 0 2015-11-27 20:08:18.692
> !MESSAGE Operation details
> !SUBENTRY 1 org.eclipse.equinox.p2.operations 2 10001 2015-11-27 20:08:18.692
> !MESSAGE Your original request has been modified.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Commons" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Eclipse Git Team Provider" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Task-Focused Interface" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.692
> !MESSAGE "Eclipse Git Team Provider - Task focused interface" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Atlassian JIRA Connector (Recommended)" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Java implementation of Git" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Task List" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Tasks Connector: Bugzilla" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Eclipse IDE" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Java Development" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Team Support" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.693
> !MESSAGE "Atlassian Connector for Eclipse Usage Monitoring" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10005 2015-11-27 20:08:18.693
> !MESSAGE "JBoss Tools Common - Mylyn" will be ignored because it is already installed.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 10054 2015-11-27 20:08:18.693
> !MESSAGE Cannot complete the install because of a conflicting dependency.
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Software being installed: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Only one of the following can be installed at once:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Java Code Manipulation Functionality 1.5.0.v20120523-1543 (org.eclipse.jdt.core.manipulation 1.5.0.v20120523-1543)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Java Code Manipulation Functionality 1.7.0.v20150713-1605 (org.eclipse.jdt.core.manipulation 1.7.0.v20150713-1605)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE From: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE To: org.eclipse.epp.package.jee.feature.feature.group [4.6.0.20151001-0600]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE From: AspectJ Development Tools Core 2.2.4.e44x-20140516-1000 (org.eclipse.ajdt.core 2.2.4.e44x-20140516-1000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE To: bundle org.eclipse.jdt.core.manipulation [1.3.0,1.7.0)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: EPP Java EE IDE Feature 4.6.0.20151001-0600 (org.eclipse.epp.package.jee.feature.feature.group 4.6.0.20151001-0600)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.feature.group 0.0.0
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.11.0.v20150805-2000 (org.eclipse.jdt.feature.group 3.11.0.v20150805-2000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.12.0.v20150916-2000 (org.eclipse.jdt.feature.group 3.12.0.v20150916-2000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.12.0.v20151029-1349 (org.eclipse.jdt.feature.group 3.12.0.v20151029-1349)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.springframework.ide.eclipse.ajdt.ui.xref [3.7.0.201506251244-RELEASE]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Spring IDE AOP Xref UI 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.ui.xref 3.7.0.201506251244-RELEASE)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: package org.eclipse.ajdt.core 0.0.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21166) AJDT can't install against 4.4/Neon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21166?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21166:
------------------------------------
I removed the org.springframework.ide.eclipse.ajdt.feature from our Central connectors in order to make the rest of org.springframework.ide.eclipse.*.feature installable from Central.
So yes, this is expected - for jbosstools 4.4.0 / devstudio 10.0.0, we don't support org.springframework.ide.eclipse.ajdt.feature installation from Central.
> AJDT can't install against 4.4/Neon
> -----------------------------------
>
> Key: JBIDE-21166
> URL: https://issues.jboss.org/browse/JBIDE-21166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.4.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: p2diff-summary.txt, p2diff.txt, spring-ide373-all-features-except-ajdt-and-roo.png
>
>
> AJDT fails to install on JBoss Tools 4.4/Eclipse Neon
> Various contraint show that AJDT is not compatible with newer JDT.
> {code}
> !ENTRY org.eclipse.equinox.p2.operations 4 0 2015-11-27 20:08:18.692
> !MESSAGE Operation details
> !SUBENTRY 1 org.eclipse.equinox.p2.operations 2 10001 2015-11-27 20:08:18.692
> !MESSAGE Your original request has been modified.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Commons" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Eclipse Git Team Provider" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Task-Focused Interface" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.692
> !MESSAGE "Eclipse Git Team Provider - Task focused interface" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Atlassian JIRA Connector (Recommended)" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Java implementation of Git" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Task List" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
> !MESSAGE "Mylyn Tasks Connector: Bugzilla" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Eclipse IDE" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Java Development" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
> !MESSAGE "Mylyn Context Connector: Team Support" will be ignored because a newer version is already installed.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.693
> !MESSAGE "Atlassian Connector for Eclipse Usage Monitoring" is already present because other installed software requires it. It will be added to the installed software list.
> !SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10005 2015-11-27 20:08:18.693
> !MESSAGE "JBoss Tools Common - Mylyn" will be ignored because it is already installed.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 10054 2015-11-27 20:08:18.693
> !MESSAGE Cannot complete the install because of a conflicting dependency.
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Software being installed: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Only one of the following can be installed at once:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Java Code Manipulation Functionality 1.5.0.v20120523-1543 (org.eclipse.jdt.core.manipulation 1.5.0.v20120523-1543)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE Java Code Manipulation Functionality 1.7.0.v20150713-1605 (org.eclipse.jdt.core.manipulation 1.7.0.v20150713-1605)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE From: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE To: org.eclipse.epp.package.jee.feature.feature.group [4.6.0.20151001-0600]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE From: AspectJ Development Tools Core 2.2.4.e44x-20140516-1000 (org.eclipse.ajdt.core 2.2.4.e44x-20140516-1000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
> !MESSAGE To: bundle org.eclipse.jdt.core.manipulation [1.3.0,1.7.0)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: EPP Java EE IDE Feature 4.6.0.20151001-0600 (org.eclipse.epp.package.jee.feature.feature.group 4.6.0.20151001-0600)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.feature.group 0.0.0
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.11.0.v20150805-2000 (org.eclipse.jdt.feature.group 3.11.0.v20150805-2000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.12.0.v20150916-2000 (org.eclipse.jdt.feature.group 3.12.0.v20150916-2000)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Eclipse Java Development Tools 3.12.0.v20151029-1349 (org.eclipse.jdt.feature.group 3.12.0.v20151029-1349)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: org.springframework.ide.eclipse.ajdt.ui.xref [3.7.0.201506251244-RELEASE]
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE From: Spring IDE AOP Xref UI 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.ui.xref 3.7.0.201506251244-RELEASE)
> !SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
> !MESSAGE To: package org.eclipse.ajdt.core 0.0.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3884) Define the version of EAP that we embed with next major version of devstudio
by Todd Mancini (JIRA)
[ https://issues.jboss.org/browse/JBDS-3884?page=com.atlassian.jira.plugin.... ]
Todd Mancini commented on JBDS-3884:
------------------------------------
Or DevSuite could dynamically determine the latest version of EAP and offer that as one of the optional installation components (downloaded on demand a la Vagrant). This will be an interesting area of discussion post-Summit
> Define the version of EAP that we embed with next major version of devstudio
> ----------------------------------------------------------------------------
>
> Key: JBDS-3884
> URL: https://issues.jboss.org/browse/JBDS-3884
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: runtime
> Affects Versions: 10.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Todd Mancini
> Fix For: 10.x
>
>
> EAP 7.0 will be in devstudio 10.0.0.GA, but future releases may change the way packaging occurs. See linked Trello cards for Big Questions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3884) Define the version of EAP that we embed with next major version of devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3884?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3884:
-----------------------------
Description: EAP 7.0 will be in devstudio 10.0.0.GA, but future releases may change the way packaging occurs. See linked Trello cards for Big Questions. (was: EAP 7.0 will be in devstudio 10.0.0.Alpha3, but future releases may change the way packaging occurs. See linked Trello cards for Big Questions.)
> Define the version of EAP that we embed with next major version of devstudio
> ----------------------------------------------------------------------------
>
> Key: JBDS-3884
> URL: https://issues.jboss.org/browse/JBDS-3884
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: runtime
> Affects Versions: 10.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Todd Mancini
> Fix For: 10.x
>
>
> EAP 7.0 will be in devstudio 10.0.0.GA, but future releases may change the way packaging occurs. See linked Trello cards for Big Questions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21059:
-------------------------------------
I spoke with Fred yesterday discussing some of these issues. I think it might fit better there, but it should also be possible for a user to handle it with a wildfly adapter.
The issues with handling a 'docker' adapter is that the docker must be absolutely generic and extensible. The problem is deploying to a tomcat may just need a .war file deployed, while deploying to wf / eap requires a blah.war AND a blah.war.dodeploy.
Basically, there's custom behavior all over the place that needs to be changeable... so it will require a lot of planning to make something generic enough that can still work for a wide array of usecases. Trying to get some minimal functionality that makes a simple wf docker container work with the existing wildfly server adapter is definitely useful.
Either way, I'd say that this basically works as expected, as a debugger can connect to a simple wf inside a docker container after recent enhancements. The workflow may not be that convenient, but that can be improved through a generic docker container.
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.1.S116
>
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-22619.
--------------------------------
Resolution: Done
> Decide strategy for fixversion targets in JIRA
> ----------------------------------------------
>
> Key: JBIDE-22619
> URL: https://issues.jboss.org/browse/JBIDE-22619
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.4.1.S116
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.S116
>
>
> We need to decide the strategy for milestones / fixversions in JIRA.
> One suggestion has been to align fixversions w/ sprint numbers, thus:
> * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...?
> instead of
> * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ?
> Questions/concerns:
> * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies?
> * whatever schema we adopt has to work with bzira and jiralint
> * any other systems that parse JIRA for integration purposes?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22619:
------------------------------------
In build.next call yesterday Alexey decided we should move ahead with using Sprint numbers in JIRA as fixversions.
As to how this is related to jgit timestamps, we need SOME suffix in foundation.core and devstudio.central to define the vanity version of JBT and devstudio, so that we can differentiate milestones / sprint releases in ide-config.properties. Thus we either use Alpha1, Alpha2, Beta1, etc. or we use Sprint numbers.
Since we're no longer doing quality stages (eg., waterfall is dead, long live agile) sprint numbers are more useful/representative of what we're actually doing.
> Decide strategy for fixversion targets in JIRA
> ----------------------------------------------
>
> Key: JBIDE-22619
> URL: https://issues.jboss.org/browse/JBIDE-22619
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.4.1.S116
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.S116
>
>
> We need to decide the strategy for milestones / fixversions in JIRA.
> One suggestion has been to align fixversions w/ sprint numbers, thus:
> * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...?
> instead of
> * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ?
> Questions/concerns:
> * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies?
> * whatever schema we adopt has to work with bzira and jiralint
> * any other systems that parse JIRA for integration purposes?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22632) Spurious message due to incorrect I18N
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22632?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22632:
-----------------------------------------------
ProjectDeletionDialogTitle constant was removed from OpenShiftUIMessages.properties (replaced by ProjectDeletionConfirmationN) but it remains in NLS class OpenShiftUIMessages. In DeleteResourceHandler, dialog title now is always OpenShiftUIMessages.ResourceDeletionDialogTitle.
Can we for the case when user selected just one project, restore in title ProjectDeletionDialogTitle?
> Spurious message due to incorrect I18N
> --------------------------------------
>
> Key: JBIDE-22632
> URL: https://issues.jboss.org/browse/JBIDE-22632
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.1.S117
>
>
> When JBossTools Openshift is starting, a spurious message is written in the Eclipse log:{{
> Warning: NLS missing message: ProjectDeletionDialogTitle in: org.jboss.tools.openshift.internal.ui.OpenShiftUIMessages}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months