[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21193.
---------------------------------
Assignee: Rob Stryker
Resolution: Done
One line fix was to revalidate later in the workflow, because all runtime detectors are asked to initialize all possible runtime definitions, not just the runtime definitions they created.
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21193:
-------------------------------------
Detection works fine, its only when creating the runtimes that the CDK mutants appear in the servers view :
!http://content.screencast.com/users/fbricon/folders/Jing/media/50060112-bb3a-479f-8760-cd32ebccf259/00000244.png|width=527!
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21193:
-------------------------------------
I cannot get the cdk detector to detect anything other than a proper cdk folder WITH a marker as a cdk runtime. The code seems to very clearly check only for a folder with a vagrantfile and a .cdk marker. Are you sure you're running with the most up-to-date code? Xavier recently mentioned that the upstream update sites seem out of date but I didn't have a chance to verify yet.
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3562:
----------------------------------
Possible PR to update existing JBDS 9.0.0.GA entry on tools.jboss.org:
https://github.com/jbosstools/jbosstools-website/pull/527 -- WDYT [~akazakov] [~ldimaggio] [~mmusaji] ?
> Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
> --------------------------------------------------------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.CVE-2015-7501-GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.CVE-2015-7501-GA
>
> Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3562:
-----------------------------
Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/350, https://github.com/jbosstools/jbosstools-website/pull/527 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/350)
> Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
> --------------------------------------------------------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.CVE-2015-7501-GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.CVE-2015-7501-GA
>
> Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21193:
-------------------------------------
Runtime detection moved away from using the foldername at least for jboss servers ever since
JBDS-3162 - change generated server names to short-form abreviated names
So runtime detection uses generated short-form abreviated names. Not folder names... unless it can't discover a proper short-form name (such as an unknown as7x productized installation) in which case it will use the folder name instead.
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21193:
-------------------------------------
>From what I can see, you have 3 wildfly-8.0's listed in your screenshot. And your folder contents are:
wildfly-8.0.0.Beta1
wildfly-8.0.0.Final
wildfly-core-8.0.0.Final
So that seems to match.
I don't see any other duplicates except from the CDK
> runtime detection detects *any* folder as a CDK and jboss multiple times
> ------------------------------------------------------------------------
>
> Key: JBIDE-21193
> URL: https://issues.jboss.org/browse/JBIDE-21193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.Beta1
>
> Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png
>
>
> with build from last week I now get this list of runtime detected in my folder of servers.
> At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name.
> Here is the content of my folder
> {code}
> apache-karaf-2.3.5
> apache-tomcat-7.0.35
> app.js
> app.js.1
> fsw-6
> jboss as 7
> jboss-5.1.0.GA
> jboss-as-7.0.1.Final
> jboss-as-7.1.0.Final
> jboss-as-7.1.1.Final
> jboss-as-web-7.0.0.Final
> jboss-as-web-7.0.2.Final
> jboss-eap-6.0.1
> jboss-eap-6.1
> weld-1.1.0.Final
> weld-1.1.5.Final
> wildfly-10.0.0.CR4
> wildfly-8.0.0.Beta1
> wildfly-8.0.0.Final
> wildfly-8.1.0.Final
> wildfly-8.2.0
> wildfly-core-8.0.0.Final
> {code}
> and attached is the list I get.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21172) CDK server in Starting state and cannot be stopped with wrong path to vagrant
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21172?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21172.
---------------------------------
Resolution: Done
I've pushed a change to make sure the launch errors properly and cleans itself up. The majority of the work though was done for https://issues.jboss.org/browse/JBIDE-21175
> CDK server in Starting state and cannot be stopped with wrong path to vagrant
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21172
> URL: https://issues.jboss.org/browse/JBIDE-21172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When I first set up a CDK 2 Beta3 server adapter in Eclipse, it had the launch config set up with the wrong path to vagrant - /usr/bin/vagrant instead of /usr/local/bin/vagrant which is the default location on OS X - I didn't notice this and just tried to start the adapter.
> Obviously it failed, but I was left in a state where the server was Starting and I couldn't stop it unless I restarted the IDE.
> I think it should fail more gracefully.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21172) CDK server in Starting state and cannot be stopped with wrong path to vagrant
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21172?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21172:
--------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
> CDK server in Starting state and cannot be stopped with wrong path to vagrant
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21172
> URL: https://issues.jboss.org/browse/JBIDE-21172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When I first set up a CDK 2 Beta3 server adapter in Eclipse, it had the launch config set up with the wrong path to vagrant - /usr/bin/vagrant instead of /usr/local/bin/vagrant which is the default location on OS X - I didn't notice this and just tried to start the adapter.
> Obviously it failed, but I was left in a state where the server was Starting and I couldn't stop it unless I restarted the IDE.
> I think it should fail more gracefully.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3562.
------------------------------
Resolution: Done
> Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
> --------------------------------------------------------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.CVE-2015-7501-GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.CVE-2015-7501-GA
>
> Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months