May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3859: ----------------------------- > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3849. --------------------------------- Resolution: Done > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22270) [jiralint] Error in JQL Query: Expecting either a value, list or function but got ')'

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22270?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22270: --------------------------------------------- inflight wifi is too slow for me to run this locally nor access jenkins to see the actual failing query. Go look at the query that cause the failure and look for empty "()" like version in (), most likely version metadata in jira is missing expected versions. Like a next version for maintanence. > [jiralint] Error in JQL Query: Expecting either a value, list or function but got ')' > ------------------------------------------------------------------------------------- > > Key: JBIDE-22270 > URL: https://issues.jboss.org/browse/JBIDE-22270 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.4.0.Alpha2 > > > Somewhere in the last 8 days, a commit [1] broke jiralint: > [1] https://github.com/maxandersen/jiralint/commits/master > {code}HTTPError = 400 {"errorMessages":["Error in JQL Query: Expecting either a value, list or function but got ')'. You must surround ')' in quotation marks to use it as a value. (line 1, character 41)"],"errors":{}} > Build step 'Jenkins Text Finder' changed build result to FAILURE > {code} - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... ... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > The last good build was #2066: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... (Apr 19, 2016 2:58:01 AM EST) > Since then all builds have been red. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18697: --------------------------------------------- [~Bardioc] sorry to hear you still have problems. Any chance you can provide project/steps to reproduce ? Also, any chance you can see if you are hitting the JDK bug we recently found causing problem like this in *any* Java app trying to monitor directores using Java FileWatcher api ? See http://tools.jboss.org/blog/2016-04-18-debug-down-the-turtle-stack.html > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22253) Update to SWTBot 2.4.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22253?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22253: --------------------------------------------- [~psrna] doesn't reddeer *use* SWTBot ? > Update to SWTBot 2.4.0 > ---------------------- > > Key: JBIDE-22253 > URL: https://issues.jboss.org/browse/JBIDE-22253 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa, target-platform > Affects Versions: 4.3.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > *Reason:* SWTBot 2.4.0 comes with several fixes (about menus) and other that JBT/JBDS can probably take advantage of > *Project page/sources:* http://eclipse.org/swtbot > *Version:* 2.4.0 > *License and owner:* EPL, Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/swtbot/releases/2.4.0 > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.4.0/ > *Include Sources:* No > *Affected JBoss Tools components:* tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22279) Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22279?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22279: --------------------------------------------- seems more an issue of our or some 3rd party we depend on having too inflexibe version constraints ? > Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22279 > URL: https://issues.jboss.org/browse/JBIDE-22279 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update, target-platform, upstream > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > Attachments: jbide22279.png > > > Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed: > {code} Software being installed: Mylyn Context Connector: Plug-in Development 3.18.0.v20151013-1847 (org.eclipse.mylyn.pde_feature.feature.group 3.18.0.v20151013-1847) > Software currently installed: Mylyn Context Connector: Java Development 3.19.0.v20160111-2059 (org.eclipse.mylyn.java_feature.feature.group 3.19.0.v20160111-2059) > {code} > Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-674: ------------------------------------------- my point being runtime detection is not part of soa 5.x compatibility afaik. > Deprecate 'SOA 5.x Compatibility' tooling > ----------------------------------------- > > Key: JBTIS-674 > URL: https://issues.jboss.org/browse/JBTIS-674 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > Attachments: dep1.png, dep2.png, dep3.png, dep4.png, dep5.png > > > The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of: > org.guvnor.tools.feature > org.jboss.tools.esb.feature > org.jboss.tools.jbpm3.feature > org.jboss.tools.jbpm.common.feature > org.jboss.tools.jbpm.convert.feature > The runtime detector features will not be deprecated: > org.jboss.tools.runtime.drools.detector.feature > org.jboss.tools.runtime.esb.detector.feature > org.jboss.tools.runtime.jbpm.detector.feature > FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-674: ------------------------------------------- reopen for clarification sorry, i'm not following - are you saying runtime detection will be deprecated now even for jbpm/drools ? are you planning on removing jbpm/drools ? > Deprecate 'SOA 5.x Compatibility' tooling > ----------------------------------------- > > Key: JBTIS-674 > URL: https://issues.jboss.org/browse/JBTIS-674 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > Attachments: dep1.png, dep2.png, dep3.png, dep4.png, dep5.png > > > The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of: > org.guvnor.tools.feature > org.jboss.tools.esb.feature > org.jboss.tools.jbpm3.feature > org.jboss.tools.jbpm.common.feature > org.jboss.tools.jbpm.convert.feature > The runtime detector features will not be deprecated: > org.jboss.tools.runtime.drools.detector.feature > org.jboss.tools.runtime.esb.detector.feature > org.jboss.tools.runtime.jbpm.detector.feature > FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13671: --------------------------------------------- so i'm all for having reliable and reproducible build qualifiers but got some questions to these claims: {quote} we can trust that the timestamp shows when the plugin was ACTUALLY last changed in Github.{quote} yes, but we will also now be generating identical filenames for *different* content, especially since we still have the parent pom pointing to snapshot's and uses overrides in mvn commands from jenkins. We'll now no longer be able to trust which binary contains what. i.e. what happens when we've rebuilt hibernate tools multiple times using the same SHA1 but against changing parent pom/TP's making different binaries under same name be available in a cmompsite on the updatesite. How do we know which binary users *actually* have when their name is the same ? {quote} So yes, it's worth it. We've been trying to make this change for 3 years. We tested it for Locus and it works great there. No reason not to roll it out to the rest of the team.{quote} No, in Locus we don't have an ever cahnging parent pom thus this is not comparable IMO. Also Locus does not have branches - it is just one stream so you don't get builds that mixes up branches as part of the daily work. Thus i'm struggling to see what has changed since we tried last time to apply this ? What makes it better to use this if we still generate different content ? > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ] Darryl Miles updated JBIDE-22283: --------------------------------- Summary: reveng *.java emitter does not escape java keyword 'return' as variable name (was: revgen *.java emitter does not escape java keyword 'return' as variable name) > reveng *.java emitter does not escape java keyword 'return' as variable name > ---------------------------------------------------------------------------- > > Key: JBIDE-22283 > URL: https://issues.jboss.org/browse/JBIDE-22283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.x > Environment: Eclipse Mars > Reporter: Darryl Miles > > revgen *.java emitter does not escape java keyword 'return' as variable name > <table name="oc_return_history"> > <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return"> > <column-ref local-column="return_id" foreign-column="return_id"/> >  > <many-to-one property="return"/> > </foreign-key> > </table> > The expected output would be: > private Return _return; > but actual output is: > private Return return; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 May 2016