[JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20066?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20066:
------------------------------------------
I dont remember having reviewed this PR but I could be wrong. Nevertheless this should show us that we should use extra care when committing to branches - especially if in a hurry - and review each others changes, 4 eyes better spot problems.
ps. Not the first time, this happened to me quite a few times
> openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
> ---------------------------------------------------------
>
> Key: JBIDE-20066
> URL: https://issues.jboss.org/browse/JBIDE-20066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta1
>
>
> Current Beta1a update site includes openshift plugins in version Beta2:
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/
> {code}
> org.jboss.tools.openshift.egit.integration.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.egit.integration.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.express.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.express.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.feature.source 3.0.0.Beta2-v20150613-0235-B25
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20067) Unable to add second server of the same type via runtime detection.
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20067?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-20067:
-------------------------------
Description:
When adding second server of the same type via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
I saw no error, when I tried to add them at once. It must be done one after another to see the error.
was:
When adding second Wildfly 9 (servlet only distribution) via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
I saw no error, when I tried to add them at once. It must be done one after another to see the error.
> Unable to add second server of the same type via runtime detection.
> -------------------------------------------------------------------
>
> Key: JBIDE-20067
> URL: https://issues.jboss.org/browse/JBIDE-20067
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
>
> When adding second server of the same type via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
> I saw no error, when I tried to add them at once. It must be done one after another to see the error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20067) Unable to add second server of the same type via runtime detection.
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20067?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-20067:
-------------------------------
Description:
When adding second server of the same type via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
I saw no error, when I tried to add them at once. It must be done one after another to see the error.
I have tried this scenario with wildfly 8.2, wildfly 9, wildfly-web 9.
was:
When adding second server of the same type via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
I saw no error, when I tried to add them at once. It must be done one after another to see the error.
> Unable to add second server of the same type via runtime detection.
> -------------------------------------------------------------------
>
> Key: JBIDE-20067
> URL: https://issues.jboss.org/browse/JBIDE-20067
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
>
> When adding second server of the same type via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
> I saw no error, when I tried to add them at once. It must be done one after another to see the error.
> I have tried this scenario with wildfly 8.2, wildfly 9, wildfly-web 9.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20067) Unable to add second server of the same type via runtime detection.
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20067?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-20067:
-------------------------------
Steps to Reproduce:
1) Have two instances of Wildfly 9 distribution
2) Add one of them via runtime detection - success
3) Add second one of them via runtime detection - error
was:
1) Have two instances of Wildfly 9 Servlet only distribution
2) Add one of them via runtime detection - success
3) Add second one of them via runtime detection - error
> Unable to add second server of the same type via runtime detection.
> -------------------------------------------------------------------
>
> Key: JBIDE-20067
> URL: https://issues.jboss.org/browse/JBIDE-20067
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
>
> When adding second Wildfly 9 (servlet only distribution) via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
> I saw no error, when I tried to add them at once. It must be done one after another to see the error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20066?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20066 at 6/15/15 5:00 AM:
-------------------------------------------------------------------
The list of issues included in the PR were the following:
* JBIDE-19920 -> removed in PR by mistria
* JBIDE-19886 -> inteded for Beta1, OK
* JBIDE-19955 -> intended for Beta2, suggesting that we keep this since minor, not harmful
* JBIDE-20015 -> indented for Beta1, OK
So the only faulty one is:
* JBIDE-19955 -> Beta2
Removing it would force a history change (unless we change the 2 files back to their state before the fix), so I suggest that we keep it since it's a minor change which isnt harmful.
ps. commit for JBIDE-19866 is a typo, it was done for JBIDE-19886 which was targeted for Beta1.
was (Author: adietish):
Another commit included in the PR seems to have be included where it shouldnt:
* https://issues.jboss.org/browse/JBIDE-19955 -> Beta2
ps. commit for JBIDE-19866 is a typo, it was done for JBIDE-19886 which was targeted for Beta1.
But removing it would force a history change (unless we change the 2 files back to their state before the fix), so I suggest that we keep it since it's a minor change which isnt harmful.
> openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
> ---------------------------------------------------------
>
> Key: JBIDE-20066
> URL: https://issues.jboss.org/browse/JBIDE-20066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta1
>
>
> Current Beta1a update site includes openshift plugins in version Beta2:
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/
> {code}
> org.jboss.tools.openshift.egit.integration.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.egit.integration.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.express.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.express.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.feature.source 3.0.0.Beta2-v20150613-0235-B25
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20067) Unable to add second server of the same type via runtime detection.
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20067?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-20067:
-------------------------------
Summary: Unable to add second server of the same type via runtime detection. (was: Unable to add second servlet only distribution of Wildfly 9 via runtime detection.)
> Unable to add second server of the same type via runtime detection.
> -------------------------------------------------------------------
>
> Key: JBIDE-20067
> URL: https://issues.jboss.org/browse/JBIDE-20067
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
>
> When adding second Wildfly 9 (servlet only distribution) via runtime detection, error pops up: "Unable to initialize some runtime paths.", "All runtime detectors failed to initialize Wildfly-Web 9.0". The runtime gets added, but the server doesn't.
> I saw no error, when I tried to add them at once. It must be done one after another to see the error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-19984) Wrong version of playground components
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19984?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19984.
-----------------------------------
Easymport components are in version beta1 in JBDS 9.0.0.beta1a
> Wrong version of playground components
> --------------------------------------
>
> Key: JBIDE-19984
> URL: https://issues.jboss.org/browse/JBIDE-19984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, easymport, updatesite
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
>
> JBDS 9.0.0.beta1 build contains alpha2 easymport plugins
> org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar
> Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar
> looks quite old but maybe nothing changed there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20066?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-20066:
----------------------------------------
Assignee: Max Rydahl Andersen (was: Andre Dietisheim)
> openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
> ---------------------------------------------------------
>
> Key: JBIDE-20066
> URL: https://issues.jboss.org/browse/JBIDE-20066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta1
>
>
> Current Beta1a update site includes openshift plugins in version Beta2:
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/
> {code}
> org.jboss.tools.openshift.egit.integration.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.egit.integration.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.express.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.express.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.feature.source 3.0.0.Beta2-v20150613-0235-B25
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20066?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20066:
----------------------------------------
Ok to keep minor changes in branch to make respin easier. However, if you want to keep them, don't forget to change the related bug fixVersions to 4.3.0.Beta1 with a "respin-b" label.
> openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
> ---------------------------------------------------------
>
> Key: JBIDE-20066
> URL: https://issues.jboss.org/browse/JBIDE-20066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta1
>
>
> Current Beta1a update site includes openshift plugins in version Beta2:
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/
> {code}
> org.jboss.tools.openshift.egit.integration.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.egit.integration.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.express.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.express.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.feature.source 3.0.0.Beta2-v20150613-0235-B25
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years
[JBoss JIRA] (JBIDE-20066) openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20066?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20066 at 6/15/15 4:52 AM:
-------------------------------------------------------------------
Another commit included in the PR seems to have be included where it shouldnt:
* https://issues.jboss.org/browse/JBIDE-19955 -> Beta2
ps. commit for JBIDE-19866 is a typo, it was done for JBIDE-19886 which was targeted for Beta1.
But removing it would force a history change (unless we change the 2 files back to their state before the fix), so I suggest that we keep it since it's a minor change which isnt harmful.
was (Author: adietish):
Another commit included in the PR seems to have be included where it shouldnt:
* https://issues.jboss.org/browse/JBIDE-19955 -> Beta2
ps. commit for JBIDE-19866 is a typo, it was done for JBIDE-19886 which was targeted for Beta1.
But removing it would be a forcing change, so I suggest that we keep it since it's a minor change which isnt harmful.
> openshift in 4.3.0.Beta1x branch is versioned 4.3.0.Beta2
> ---------------------------------------------------------
>
> Key: JBIDE-20066
> URL: https://issues.jboss.org/browse/JBIDE-20066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta1
>
>
> Current Beta1a update site includes openshift plugins in version Beta2:
> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.0.Beta1a/
> {code}
> org.jboss.tools.openshift.egit.integration.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.egit.integration.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.express.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.express.feature.source 3.0.0.Beta2-v20150613-0235-B25
> org.jboss.tools.openshift.feature 3.0.0.Beta2-v20150613-0235-B25 | CoreTools | CloudTools
> org.jboss.tools.openshift.feature.source 3.0.0.Beta2-v20150613-0235-B25
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years