January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23657) Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23657: ---------------------------------- Assignee: Lukáš Valach (was: Nick Boldt) > Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8 > -------------------------------------------------------------------- > > Key: JBIDE-23657 > URL: https://issues.jboss.org/browse/JBIDE-23657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Marek Novotny > Assignee: Lukáš Valach > Fix For: 4.4.3.AM1 > > > There are _memoryoptions1_ and _memoryoptions2_ properties in https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... which are ignored in Java 8 - instead there are options if you need to set it up like: > * -XX:MetaspaceSize for initial size > * -XX:MaxMetaspaceSize for maximum size (it is not required as the value is by default the max memory on runnning machine. > Otherwise just remove them. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23657) Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23657: ------------------------------------ I'm confused. I applied this change: https://github.com/jbosstools/jbosstools-build/pull/239/files And now the parent pom contains the results of that change in lines 33-34 ( https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... ). But you're saying there's still unnecessary properties there? WHICH ONES? Please provide a PR to explain what you mean and show what should be removed. > Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8 > -------------------------------------------------------------------- > > Key: JBIDE-23657 > URL: https://issues.jboss.org/browse/JBIDE-23657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > There are _memoryoptions1_ and _memoryoptions2_ properties in https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... which are ignored in Java 8 - instead there are options if you need to set it up like: > * -XX:MetaspaceSize for initial size > * -XX:MaxMetaspaceSize for maximum size (it is not required as the value is by default the max memory on runnning machine. > Otherwise just remove them. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23665) Create Windup tooling connector for JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23665?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23665: ------------------------------------ Left comments on John's PR: https://github.com/jbosstools/jbosstools-discovery/pull/340/files ... which will need to be changed once new windup 3.0.0.Alpha2 bits are out next week. > Create Windup tooling connector for JBoss Central > ------------------------------------------------- > > Key: JBIDE-23665 > URL: https://issues.jboss.org/browse/JBIDE-23665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central-update > Affects Versions: 4.4.3.AM1 > Reporter: John Steele > Assignee: John Steele > Fix For: 4.4.3.AM2 > > > For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22774) Create integration tests PR check job for aerogar-hybrid

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22774?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-22774. -------------------------------- Pavol already verified this jira, so closing. > Create integration tests PR check job for aerogar-hybrid > -------------------------------------------------------- > > Key: JBIDE-22774 > URL: https://issues.jboss.org/browse/JBIDE-22774 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, build, qa > Reporter: Rastislav Wagner > Assignee: Pavol Srna > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23657) Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-23657: -------------------------------------- Verified, required changes has been done. But there are still unnecesary properties in https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... Would you like to let it be or remove it? > Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8 > -------------------------------------------------------------------- > > Key: JBIDE-23657 > URL: https://issues.jboss.org/browse/JBIDE-23657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > There are _memoryoptions1_ and _memoryoptions2_ properties in https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... which are ignored in Java 8 - instead there are options if you need to set it up like: > * -XX:MetaspaceSize for initial size > * -XX:MaxMetaspaceSize for maximum size (it is not required as the value is by default the max memory on runnning machine. > Otherwise just remove them. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23510: ------------------------------- Sprint: devex #126 January 2017 (was: devex #125 December 2016) > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Sprint: devex #126 January 2017 (was: devex #125 December 2016) > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23665) Create Windup tooling connector for JBoss Central

by John Steele (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23665?page=com.atlassian.jira.plugi... ] John Steele commented on JBIDE-23665: ------------------------------------- The current Alpha plugins use Forge to run and manage the Windup execution environment. We will roll out another CR build mid next week, which starts Forge in a separate process, and uses RMI as its communication protocal. > Create Windup tooling connector for JBoss Central > ------------------------------------------------- > > Key: JBIDE-23665 > URL: https://issues.jboss.org/browse/JBIDE-23665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central-update > Affects Versions: 4.4.3.AM1 > Reporter: John Steele > Assignee: John Steele > Fix For: 4.4.3.AM2 > > > For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23665) Create Windup tooling connector for JBoss Central

by John Steele (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23665?page=com.atlassian.jira.plugi... ] John Steele edited comment on JBIDE-23665 at 1/5/17 10:09 AM: -------------------------------------------------------------- The current Alpha plugins use Forge to run and manage the Windup execution environment. We will roll out another CR build mid next week, which starts Forge in a separate process, and uses RMI as its communication protocol. was (Author: jsteele): The current Alpha plugins use Forge to run and manage the Windup execution environment. We will roll out another CR build mid next week, which starts Forge in a separate process, and uses RMI as its communication protocal. > Create Windup tooling connector for JBoss Central > ------------------------------------------------- > > Key: JBIDE-23665 > URL: https://issues.jboss.org/browse/JBIDE-23665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central-update > Affects Versions: 4.4.3.AM1 > Reporter: John Steele > Assignee: John Steele > Fix For: 4.4.3.AM2 > > > For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23021. -------------------------------- Verified, SHA check passes. Closing. > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017