April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-175) Add xml validator option to ignore "Referenced file contains errors" error [EBZ#491313]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-175?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny reassigned ERT-175: ----------------------------------- Assignee: Victor Rubezhny > Add xml validator option to ignore "Referenced file contains errors" error [EBZ#491313] > --------------------------------------------------------------------------------------- > > Key: ERT-175 > URL: https://issues.jboss.org/browse/ERT-175 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: 3.8_M7, bzira, wst.xml > Fix For: Neon (4.6) M7 > > > The biggest problems we have for our customers is when the customer's xml file is fine, but validating against an imperfect schema upstream ends up with an error like this: > "Referenced file contains errors (file:/home/rob/apps/eclipse/builds/tp/4.60.x_20160308/../../../../../code/jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/ourBundledSchema.xsd). For > more information, right click on the message in the Problems View and select "Show Details..." > It'd be great if we had an xml validator option to allow this to be an error, a warning, or even ignored. > Since this is our most common error for users, we consider it a pretty high priority request. We'd be willing to do some of the work if you could point us to where such a thing could be implemented easily (or even not easily... at least a starting-off point). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-60) JSON Editor formatter is broken [EBZ#486524]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-60?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny resolved ERT-60. -------------------------------- Fix Version/s: Neon (4.6) M7 Resolution: Done > JSON Editor formatter is broken [EBZ#486524] > -------------------------------------------- > > Key: ERT-60 > URL: https://issues.jboss.org/browse/ERT-60 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Labels: bzira, wst.json > Fix For: Neon (4.6) M7 > > > Open a JSON editor and do a source>format. > In my tests a simple JSON such as > { > "test":123 > > } > has been formatted to > { > "test":123 > > } > } > and a more complex example > { > "test":123, > "field2":"f", > "ignore": [ > "examples", > "test", > "tools" > ] > } > ended up as > { > "test":123 > > }"field2":"f" > > }"ignore":["examples","test","tools"] > > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21118) Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21118?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21118: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Update 4.60.x TP to m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21118 > URL: https://issues.jboss.org/browse/JBIDE-21118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.7 (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.60.x TPs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16158) Investigate tools/processes to templatize CI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16158?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16158: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Investigate tools/processes to templatize CI jobs > ------------------------------------------------- > > Key: JBIDE-16158 > URL: https://issues.jboss.org/browse/JBIDE-16158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > Attachments: devstudio.product_master_diff_generated_vs_server_copy.diff > > > Found something a bit more complete than the maven plugin - haven't tried it yet but its examples looks extremely clean. > python script for creating jobs (linked to puppet but can be used standalone) > http://ci.openstack.org/jenkins-job-builder/installation.html > Example: https://github.com/adaptivelab/jenkins-build/blob/develop/template.yaml > Article: http://techs.enovance.com/6006/manage-jenkins-jobs-with-yaml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21283) Update Central to Spring IDE 3.7.3 release when available (replaces CI build)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21283?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21283: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Update Central to Spring IDE 3.7.3 release when available (replaces CI build) > ----------------------------------------------------------------------------- > > Key: JBIDE-21283 > URL: https://issues.jboss.org/browse/JBIDE-21283 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > [~mlippert] said: {quote} > Sorry for the inconvenience regarding the weaving hook versions, the AJDT build uses a specific self-built version of that instead of the one that is included in the Mars and Neon repos. However, this will change in the near future. We are switching to a new build and had to made a few additional changes (as a heads-up): > org.eclipse.equinox.weaving.aspectj(.source) will be moved to the AJDT project, therefore no longer in Neon (from M5 on, I think) > org.eclipse.equinox.weaving.sdk(.feature.group) will be moved to the AJDT project as well, also no longer in the Neon repo (from M5 on as well) > Both will have higher version numbers and being distributed as part of the AJDT build (instead of Equinox). > I think this will affect the AJDT versions for Eclipse 4.5 + 4.6, so you might come across a similar situation with the Mars repositories (two different versions of the weaving.sdk feature, two different versions of the weaving.hook bundle). > {quote} > Then [~dgolovin] said: {quote}Didn't test it, but it seems good to be applied and get Spring IDE back to Central. But it is a nightly build, isn't it? We should remember to update it to released version at some point. Could you create issue for that?{quote} > So here's that tracker issue, to ensure we get a working SpringIDE 3.7.3 for Neon once it's released, along with a working version of AJDT. May require TWO mirrors instead of one, as we used to have for Mars. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21439: ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Add JSON Editor to JBDS/JBT Target Platform > ------------------------------------------- > > Key: JBIDE-21439 > URL: https://issues.jboss.org/browse/JBIDE-21439 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Missing description. Need update site from which to fetch IUs, and a list of which IUs to add. > Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13671: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/217 (was: https://github.com/jbosstools/jbosstools-build/pull/73) > 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)

8 years, 1 month

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ {quote}How do we map binaries to jenkins build without -BXXX suffix?{quote} The whole point here is that it no longer matters in which build the bits are built because we know they're coming from the same SHA in github. So we could add that suffix back onto the update site version qualifier if we want but I'm not sure we need it. > 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)

8 years, 1 month

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ Found a better implementation: https://github.com/jbosstools/jbosstools-build/pull/217 For a dirty git workspace local build (changing the local arquillian feature.xml & having an extra untracked file in there), I get: {code} org.jboss.tools.arquillian.feature_1.2.100.Alpha1-v20160429-1802-LOCAL.jar (local timestamp, not jgit) org.jboss.tools.arquillian.ui_1.2.100.Alpha1-v20160211-2142-LOCAL.jar (remote jgit timestamp, unchanged except the -LOCAL suffix) $➔ cat site/target/repository/index.html | grep 1.2.100 <title>JBoss Tools - arquillian.site -  Update Site: 1.2.100-SNAPSHOT (Alpha1-v20160429-1802-LOCAL)</title> (local timestamp, not jgit) {code} If I commit the change and remove the untracked files so we're clean locally: {code} org.jboss.tools.arquillian.feature_1.2.100.Alpha1-v20160429-1811-LOCAL.jar (local jgit timestamp) org.jboss.tools.arquillian.ui_1.2.100.Alpha1-v20160211-2142-LOCAL.jar (remote jgit timestamp, unchanged except the -LOCAL suffix) <title>JBoss Tools - arquillian.site -  Update Site: 1.2.100-SNAPSHOT (Alpha1-v20160429-1811-LOCAL)</title> (local jgit timestamp) {code} If I remove the change and all untracked files: {code} org.jboss.tools.arquillian.feature_1.2.100.Alpha1-v20160211-2142-LOCAL.jar (remote jgit timestamp, unchanged except the -LOCAL suffix) org.jboss.tools.arquillian.ui_1.2.100.Alpha1-v20160211-2142-LOCAL.jar (remote jgit timestamp, unchanged except the -LOCAL suffix) <title>JBoss Tools - arquillian.site -  Update Site: 1.2.100-SNAPSHOT (Alpha1-v20160211-2142-LOCAL)</title> (remote jgit timestamp, unchanged except the -LOCAL suffix) {code} If I rebuild the last Jenkins build locally: {code} org.jboss.tools.arquillian.feature_1.2.100.Alpha1-v20160211-2142-ci.jar (remote jgit timestamp, unchanged except the -ci suffix) org.jboss.tools.arquillian.ui_1.2.100.Alpha1-v20160211-2142-ci.jar (remote jgit timestamp, unchanged except the -ci suffix) <title>JBoss Tools - arquillian.site -  Update Site: 1.2.100-SNAPSHOT (Alpha1-v20160211-2142-ci)</title> (remote jgit timestamp, unchanged except the -ci suffix) {code} Why use 'LOCAL' and 'ci'? That way just in case there are two builds done at the exact same time, one in Jenkins and one locally, the Jenkins one will always be considered NEWER (lowercase letters are of higher priority in the ASCII table than uppercase ones, which is how OSGi determines which is newer). > 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)

8 years, 1 month

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13671: --------------------------------------- How do we map binaries to jenkins build without -BXXX suffix? > 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)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016