October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Description: In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 2 or more URLs. So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: {code} target/composite/compositeContent.xml target/composite/compositeArtifacts.xml target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) {code} was: In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 2 or more URLs. So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce: target/composite/ target/composite/compositeContent.xml target/composite/compositeArtifacts.xml target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 2 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21065: ------------------------------------- I've made two commits for this issue. The first fixes a few similar issues, of properties being changed when you change the host. The second fixes the specific issue here of setDefaults being called too often. Upstream has made a commit on the issue. Unfortunately it's not yet in neon.2. I will request for it to be so. You may notice fixes via the first commit, but still some things not working, until we get the patch into neon.2 and also consume it in our TP. Things you will notice as fixed now: In new server wizard, go to 2nd page, change a setting (such as runtime or externally-launched flag), go back to first page, change host, go forward again to 2nd page, and note that all attributes now seem to match the current status of the new server wizard model. But the specific issue of the host itself being incorrect will not be fixed until we get the neon.2 patch. > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Project: Tools (JBoss Tools) (was: WindUp) Key: JBIDE-23322 (was: WINDUP-1192) Workflow: GIT Pull Request workflow (was: GIT Pull Request workflow with automatic PR triggers) Component/s: build (was: Eclipse Plugin) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Nick Boldt > > It would be great if local build of windup eclipse plugins could create a composite update site. > Details: > 1) windup eclipse plugin source: https://github.com/windup/windup-eclipse-plugin > 2) windup eclipse code nightly update site: http://download.jboss.org/jbosstools/neon/snapshots/builds/windup-eclipse... > 3) jbt dependency update site: http://download.jboss.org/jbosstools/neon/snapshots/updates/ > 4) Jenkins job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Windup/job/windup-e... > Making these maven flags would allow for easier over-riding so that when windup tools branch for alpha1 they can change the deps to our am2 release for stability. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Reporter: Nick Boldt (was: Rob Stryker) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > It would be great if local build of windup eclipse plugins could create a composite update site. > Details: > 1) windup eclipse plugin source: https://github.com/windup/windup-eclipse-plugin > 2) windup eclipse code nightly update site: http://download.jboss.org/jbosstools/neon/snapshots/builds/windup-eclipse... > 3) jbt dependency update site: http://download.jboss.org/jbosstools/neon/snapshots/updates/ > 4) Jenkins job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Windup/job/windup-e... > Making these maven flags would allow for easier over-riding so that when windup tools branch for alpha1 they can change the deps to our am2 release for stability. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Fix Version/s: 4.4.2.AM3 > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > It would be great if local build of windup eclipse plugins could create a composite update site. > Details: > 1) windup eclipse plugin source: https://github.com/windup/windup-eclipse-plugin > 2) windup eclipse code nightly update site: http://download.jboss.org/jbosstools/neon/snapshots/builds/windup-eclipse... > 3) jbt dependency update site: http://download.jboss.org/jbosstools/neon/snapshots/updates/ > 4) Jenkins job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Windup/job/windup-e... > Making these maven flags would allow for easier over-riding so that when windup tools branch for alpha1 they can change the deps to our am2 release for stability. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22225: ------------------------------------ update jobs to use new 4.60.2.AM1-SNAPSHOT TP > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23309: ------------------------------------ update jobs to use new 4.60.2.AM1-SNAPSHOT TP > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven, target-platform > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22225: ------------------------------------ update jobs to use new 4.60.2.AM1-SNAPSHOT TP > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23309) Update to latest m2e-mavenarchiver

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23309: ------------------------------------ update jobs to use new 4.60.2.AM1-SNAPSHOT TP > Update to latest m2e-mavenarchiver > ---------------------------------- > > Key: JBIDE-23309 > URL: https://issues.jboss.org/browse/JBIDE-23309 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven, target-platform > Affects Versions: 4.4.1.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Please update m2e-mavenarchiver to the latest version. > The issue https://issues.jboss.org/browse/JBIDE-23207 could be solved by update. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22581: ------------------------------------ update Central to include neon.1 201609281000 > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM2 > > Attachments: jbosstools.p2diff.summary.txt, jbosstools.p2diff.txt, jbtcentral.p2diff.txt > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016