[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23093.
------------------------------
Resolution: Done
> use consistent variables across all jenkins jobs for streams, TP versions, etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-23093
> URL: https://issues.jboss.org/browse/JBIDE-23093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> We have a number of inconsistencies between jobs / pom.xml:
> * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX
> * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN
> * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX
> * jbosstools_site_stream -> stream_jbt
> * JBT_buildversion -> version_jbt, versionWithRespin_jbt
> * JBDS_buildversion -> version_ds, versionWithResin_ds
> * JBDSVersion -> devstudioReleaseVersion
> Should standardize these.
> Can also (where applicable) script the relationship between version_* and versionWithRespin_*:
> {code}
> version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23093 at 10/20/16 5:13 PM:
--------------------------------------------------------------
refactor jbosstools_site_stream -> stream_jbt, TARGET_PLATFORM_VERSION_MAXIMUM -> TARGET_PLATFORM_VERSION_MAX, TARGET_PLATFORM_VERSION -> TARGET_PLATFORM_VERSION_MIN, etc. in jbt aggregate site builds; also add tpc.version = TARGET_PLATFORM_VERSION_MAX (for JBIDE-23364)
https://github.com/jbosstools/jbosstools-build-sites/commit/e1d42d7e2ebc4...
was (Author: nickboldt):
refactor jbosstools_site_stream -> stream_jbt, TARGET_PLATFORM_VERSION_MAXIMUM -> TARGET_PLATFORM_VERSION_MAX, TARGET_PLATFORM_VERSION -> TARGET_PLATFORM_VERSION_MIN, etc. in jbt aggregate site builds; also add tpc.version = TARGET_PLATFORM_VERSION_MAX (for
> use consistent variables across all jenkins jobs for streams, TP versions, etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-23093
> URL: https://issues.jboss.org/browse/JBIDE-23093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> We have a number of inconsistencies between jobs / pom.xml:
> * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX
> * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN
> * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX
> * jbosstools_site_stream -> stream_jbt
> * JBT_buildversion -> version_jbt, versionWithRespin_jbt
> * JBDS_buildversion -> version_ds, versionWithResin_ds
> * JBDSVersion -> devstudioReleaseVersion
> Should standardize these.
> Can also (where applicable) script the relationship between version_* and versionWithRespin_*:
> {code}
> version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23093:
------------------------------------
refactor jbosstools_site_stream -> stream_jbt, TARGET_PLATFORM_VERSION_MAXIMUM -> TARGET_PLATFORM_VERSION_MAX, TARGET_PLATFORM_VERSION -> TARGET_PLATFORM_VERSION_MIN, etc. in devstudio build
> use consistent variables across all jenkins jobs for streams, TP versions, etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-23093
> URL: https://issues.jboss.org/browse/JBIDE-23093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> We have a number of inconsistencies between jobs / pom.xml:
> * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX
> * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN
> * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX
> * jbosstools_site_stream -> stream_jbt
> * JBT_buildversion -> version_jbt, versionWithRespin_jbt
> * JBDS_buildversion -> version_ds, versionWithResin_ds
> * JBDSVersion -> devstudioReleaseVersion
> Should standardize these.
> Can also (where applicable) script the relationship between version_* and versionWithRespin_*:
> {code}
> version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23093) use consistent variables across all jenkins jobs for streams, TP versions, etc.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23093?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23093:
------------------------------------
refactor jbosstools_site_stream -> stream_jbt, TARGET_PLATFORM_VERSION_MAXIMUM -> TARGET_PLATFORM_VERSION_MAX, TARGET_PLATFORM_VERSION -> TARGET_PLATFORM_VERSION_MIN, etc. in jbt aggregate site builds; also add tpc.version = TARGET_PLATFORM_VERSION_MAX (for
> use consistent variables across all jenkins jobs for streams, TP versions, etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-23093
> URL: https://issues.jboss.org/browse/JBIDE-23093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> We have a number of inconsistencies between jobs / pom.xml:
> * JBTCENTRALTARGET_VERSION -> TARGET_PLATFORM_CENTRAL_MAX
> * TARGET_PLATFORM_VERSION vs. TARGET_PLATFORM_VERSION_MIN
> * TARGET_PLATFORM_VERSION_MAXIMUM vs. TARGET_PLATFORM_VERSION_MAX
> * jbosstools_site_stream -> stream_jbt
> * JBT_buildversion -> version_jbt, versionWithRespin_jbt
> * JBDS_buildversion -> version_ds, versionWithResin_ds
> * JBDSVersion -> devstudioReleaseVersion
> Should standardize these.
> Can also (where applicable) script the relationship between version_* and versionWithRespin_*:
> {code}
> version_jbt=$(echo ${versionWithRespin_jbt} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> version_ds=$(echo ${versionWithRespin_ds} | sed -e '/[abcdwxyz]$/ s/\(^.*\)\(.$\)/\1/')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23320) New server window server type picker is single line long on Cinnamon
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23320?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23320:
-------------------------------------
As far as I can tell, all the widgets are just a little bit bigger. This leaves less room for the viewer.
> New server window server type picker is single line long on Cinnamon
> --------------------------------------------------------------------
>
> Key: JBIDE-23320
> URL: https://issues.jboss.org/browse/JBIDE-23320
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Fedora 24 x86-64
> Cinnamon 3.0.7
> Linux 4.7.6
> JBDS 10.1.0.GA
> Reporter: Michal Jurc
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
> Attachments: jbds-10.1-new-server.png
>
>
> In JBoss Developer Studio 10.1.0.GA, the New Server window server type choice only displays single server at time without scrolling which is uncomfortable to navigate through.
> Screenshot attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23311) Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23311?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23311.
---------------------------------
Fix Version/s: 4.4.2.AM3
Resolution: Done
I've reviewed it. No changes to be taken.
> Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
> -----------------------------------------------------------------
>
> Key: JBIDE-23311
> URL: https://issues.jboss.org/browse/JBIDE-23311
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> Rather than reopening JBIDE-23161 to ask you about some discrepancies that I found, I am opening this JIRA.
> I compared the contents of org.jboss.tools.as.catalog_3.2.2.v20160923-0424.jar and what's in the wildfly 10.1.0 zip. And there are some diffs. I understand that there will always be more in the plugin - we keep some previous versions. But there are many xsd files missing in the plugin:
> {code}
> $ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> nattura:jar rasp$ find . -name javaee_7.xsd
> nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$
> nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> {code}
> But I randomly checked one and it was visible in Preferences -> XML -> XML Catalog. My guess is that these are not ours so they will be present in some Eclipse plugin and we don't need to add them. Can you confirm this?
> And in that case, what would you recommend as the best option to verify that our catalog is correct and also that the jboss.org.schema git repo is correct?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (ERT-439) Add remote mount support to ContainerLauncher [EBZ#506312]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-439:
---------------------------------------
Summary: Add remote mount support to ContainerLauncher [EBZ#506312]
Key: ERT-439
URL: https://issues.jboss.org/browse/ERT-439
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
The ContainerLauncher class in Docker uses a HostConfig binds setting to mount specified mount points in the Container. This does not work when the daemon is remote. What needs to be done is to determine the daemon is remote and then create a mount point that we copy host files into before starting the container.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4129) Bundled JDK is trying to install from non existing location
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4129?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4129:
--------------------------------
Fix Version/s: 10.2.0.AM3
> Bundled JDK is trying to install from non existing location
> -----------------------------------------------------------
>
> Key: JBDS-4129
> URL: https://issues.jboss.org/browse/JBDS-4129
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Environment: Windows 10
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> OpenJDK fails to install from bundled installer, it is trying to execute the msi from the location it would normally be downloaded into by the online installer. But it is just not there, since it's bundled instead.
> {noformat}
> Thu, 20 Oct 2016 18:53:13 GMT-INFO: jdk - Execute msiexec /i,C:\Users\jbossqa\AppData\Local\Temp\jdk.msi,INSTALLDIR=c:\DevelopmentSuite\jdk8,/qn,/norestart,/Lviwe,c:\DevelopmentSuite\openjdk.log
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk -
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk failed to install: Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4129) Bundled JDK is trying to install from non existing location
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4129?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4129:
--------------------------------
Sprint: devex #122 October 2016
> Bundled JDK is trying to install from non existing location
> -----------------------------------------------------------
>
> Key: JBDS-4129
> URL: https://issues.jboss.org/browse/JBDS-4129
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Environment: Windows 10
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> OpenJDK fails to install from bundled installer, it is trying to execute the msi from the location it would normally be downloaded into by the online installer. But it is just not there, since it's bundled instead.
> {noformat}
> Thu, 20 Oct 2016 18:53:13 GMT-INFO: jdk - Execute msiexec /i,C:\Users\jbossqa\AppData\Local\Temp\jdk.msi,INSTALLDIR=c:\DevelopmentSuite\jdk8,/qn,/norestart,/Lviwe,c:\DevelopmentSuite\openjdk.log
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk -
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk failed to install: Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months