January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- {quote} what does "knownReferences" refer to exactly ? are the unknown referenes too and why is both HEAD and master listed ? will there ever be multiple different ones ? is it a name used by jenkins ? I do see it lists multiple of my branches when building locally..which one is relevant ?{quote} knownReferences allow to know from which tag or branch the build was triggered. I feel this might be useful one day, but I didn't figure out any real use-case yet. We can get rid of it if you want. {quote} Also I saw today this error: [ERROR] Could not read build info at http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas... when running a single openshift build but the resulting buildInfo.json did not have any trace of that error. In case it fails to get those upstream references I think that should be visible somehow in the file and we should even for a CR/GA build fail the build. {quote} Yes, that makes sense. The "upstream" should be there with a field such as "error": "No upstream build description file found". I'll change that. {quote} Last point: I know you guys hate (or forgot about) it but could we please continue to use lowercase filenames, not mixed case names for artifacts so that would be buildinfo.json, not buildInfo.json {quote} ok... > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15135: --------------------------------------------- I like the format/idea of using json and embedding the upstream info for verifcation purposes. what does "knownReferences" refer to exactly ? are the unknown referenes too and why is both HEAD and master listed ? will there ever be multiple different ones ? is it a name used by jenkins ? I do see it lists multiple of my branches when building locally..which one is relevant ? Also I saw today this error: [ERROR] Could not read build info at http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_mas... when running a single openshift build but the resulting buildInfo.json did not have any trace of that error. In case it fails to get those upstream references I think that should be visible somehow in the file and we should even for a CR/GA build fail the build. Last point: I know you guys hate (or forgot about) it but could we please continue to use lowercase filenames, not mixed case names for artifacts ;) so that would be buildinfo.json, not buildInfo.json > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19116) itests not being linked from build page

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19116?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19116: --------------------------------------------- i've manually set the include filter to "sources/*/tests/*/target/surefire-reports/TEST-*.xml,sources/*/itests/*/target/surefire-reports/TEST-*.xml" which should make it pick up the itests. Trial run for that is running a https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... If that works we should add the above to all our jobs config. I hope [~mickael_istria] can help with that. > itests not being linked from build page > --------------------------------------- > > Key: JBIDE-19116 > URL: https://issues.jboss.org/browse/JBIDE-19116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Rob Stryker > Assignee: Mickael Istria > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > There is no link to the itests, and yet the build has failed. This makes it troublesome to browse the failing tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19083) Rename org.jboss.tools.hibenate.spi.test into org.jboss.tools.hibernate.runtime.spi.test

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19083?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-19083. ------------------------------- Resolution: Done > Rename org.jboss.tools.hibenate.spi.test into org.jboss.tools.hibernate.runtime.spi.test > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19083 > URL: https://issues.jboss.org/browse/JBIDE-19083 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19117) Rename org.jboss.tools.hibernate3_5 into org.jboss.tools.hibernate.runtime.v_3_5

by Koen Aers (JIRA)

Koen Aers created JBIDE-19117: --------------------------------- Summary: Rename org.jboss.tools.hibernate3_5 into org.jboss.tools.hibernate.runtime.v_3_5 Key: JBIDE-19117 URL: https://issues.jboss.org/browse/JBIDE-19117 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.3.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19100) On RHEL7 (JBT and JBDS) tooltips appear as dark text on a dark background

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19100?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19100: --------------------------------------- Does the same issue happen in the Javadoc view? > On RHEL7 (JBT and JBDS) tooltips appear as dark text on a dark background > ------------------------------------------------------------------------- > > Key: JBIDE-19100 > URL: https://issues.jboss.org/browse/JBIDE-19100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cleanup > Affects Versions: 4.2.2.Final > Environment: RHEL7 > Reporter: Len DiMaggio > Assignee: Snjezana Peco > Attachments: JBDS8_RHEL7_vnc.png, RHEL7_devtoolset3_JBT422_QS_Tooltip.png > > > On RHEL7, some tooltips - for example - the notice displayed when updates to Tools/JBDS are available and the information relating to quickstarts as displayed in Central are shown as dark text on a dark background. See attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12282?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12282: ------------------------------------- Linking new jar requirement for wf8 > Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really > ---------------------------------------------------------------------------------------- > > Key: JBIDE-12282 > URL: https://issues.jboss.org/browse/JBIDE-12282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.Final > Environment: JBDS 5.0.0.GA > Fedora 17 / OS X 10.7 Lion > JBoss EAP 6.0.0.GA > Reporter: Martin Malina > Labels: help_wanted > Fix For: LATER > > > When you set up your server to be bound to IPv6 (but you don't bind the management port to anything), the server fails to stop. Second attempt will force the server to stop. > This is the error in the log: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2012-07-02 16:49:05.284 > !MESSAGE Server jboss-eap-6.0.0.GA failed to stop. > {code} > This happens most probably because in such scenario, the management port is bound to IPv4 localhost (127.0.0.1). > Indeed I just verified that this is not related to IPv6 specifically but any host name other than localhost - if you don't check "Expose your management port" (and don't set -Dmanagement manually) and the hostname is something else than localhost, then this issue will arise. Note that with remote servers you don't need to bind the management port to anything for server stop to work. So we either need to set -Dmanagement always or make sure it is not needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19115: ----------------------------------- Component/s: updatesite (was: build) > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19115) Include FeedHenry feature in Mobile Category

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19115?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19115. ------------------------------------ Resolution: Done Fixed with https://github.com/jbosstools/jbosstools-build-sites/commit/201456caa098c... > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19115 > URL: https://issues.jboss.org/browse/JBIDE-19115 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Pavol Srna > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- See how this looks like for aggregate: http://download.jboss.org/jbosstools/updates/nightly/core/master/buildInf... I believe we can slowly move away from GIT_REVISION and build.properties file, as this file provides the same result, and is generated at build-time and it automatically included in the repository. [~nickboldt] Do you think there anything still to do as part of this Jira, or can we mark it as resolved? > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015