January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-471) Unify component versions

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-471: ------------------------------------------ Nick: why can't I call my next 1.0.5 something like 1.0.501 (since you're suggestion a triple digit service release number anyway)? Besides, I'm not planing on making any more changes to BPEL editor - it's basically at EOL anyway (except it still needs to be in Neon) Paul: yes, I haven't changed anything in jbosstools-bpel either. > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21363: ------------------------------------ PR updated again today. Max says: {quote} for me the thing we need before going live is: 1) actually implement the version mapping lambdas for the products we know 2) figure out what to do with bz's we don't have mapped - i.e. have the build fail with a report with enough info so someone can go and add the mapping - but without stopping doing imports of those that does work 3) at least know we can within decent time implement a way to update fields if version mappings changes 4) check that we can avoid having to query all bugzillas and jiras at every run (i.e. have the script only query things that changed since last run) {quote} > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3557) JBDS Installer should be EPL licensed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3557: ---------------------------------- +1 to adding EPL-based LICENCE file (or LICENSE, your version of English may vary) to the root of the installer. Not a blocker for Beta2, though. > JBDS Installer should be EPL licensed > ------------------------------------- > > Key: JBDS-3557 > URL: https://issues.jboss.org/browse/JBDS-3557 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer, legal > Reporter: Ken Finnigan > Assignee: Nick Boldt > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL > Sources code in repository ether has Apache Licence or no license. > IzPack distribution jar's and licenses: > 1. kunstoff Look and Feel is under LGPL http://kunstoff.incors.com/archive/licence.php3 > 2. Birosoft Liquid Look and Feel > The source code (except the files or methods mentioned below) of the look and feel is released under the LGPL (GNU Lesser General Public License), > which you can view on http://www.gnu.org/copyleft/lesser.html. > Some methods are marked as SUN proprietary, the LGPL does not apply for those methods. > 3. JGoodies Karsten Lentzsch - BSD open source license http://www.jgoodies.com/downloads/libraries/ > 4. Metouia Look And Feel: a free pluggable look and feel for java - LGPLv2.1 http://grepcode.com/file/repo1.maven.org/maven2/net.sf.squirrel-sql.third... > 5. Nimbus Look And Feel > This library is free software; you can redistribute it and/or > * modify it under the terms of the GNU Lesser General Public > * License as published by the Free Software Foundation; either > * version 2.1 of the License, or (at your option) any later version. > 6. Substance Java Look and Feel (bundles several components with licenses listed below) > 6.1 Copyright (c) 2005-2007, Kirill Grouchnikov and contributors > All rights reserved. > Redistribution and use in source and binary forms, with or without > modification, are permitted provided that the following conditions are met: > * Redistributions of source code must retain the above copyright > notice, this list of conditions and the following disclaimer. > * Redistributions in binary form must reproduce the above copyright > notice, this list of conditions and the following disclaimer in the > documentation and/or other materials provided with the distribution. > * Neither the name of the Kirill Grouchnikov and contributors nor > the names of its contributors may be used to endorse or promote products > derived from this software without specific prior written permission. > 6.2 Source code, documentation and binaries of the Quaqua Look and > Feel (also called "this software") are subject to the GNU Lesser > General Public License (LGPL). > 6.3. MOZILLA PUBLIC LICENSE Version 1.1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on LOCUS-50: --------------------------------- Hey [~lhein] [~nickboldt] - So - there's an issue with the required bundles for jsonschema2pojo. Locus' target platform is pulling an older orbit - https://github.com/jbosstools/jbosstools-locus/blob/master/target-platfor... There is no org.apache.commons.lang3 in there. There is an org.apache.commons.lang. Do we advance the locus TP orbit? Do we use org.apache.commons.lang ? wdyt? > Locus bundle for jsonschema2pojo has corrupted Export-Package statement > ----------------------------------------------------------------------- > > Key: LOCUS-50 > URL: https://issues.jboss.org/browse/LOCUS-50 > Project: JBoss Tools Locus > Issue Type: Bug > Affects Versions: 1.5.0 > Reporter: Lars Heinemann > Assignee: Nick Boldt > Priority: Blocker > Fix For: 1.6.0 > > > see https://gist.github.com/lhein/47405c1fcb9dc2a7138e > Bundle: > org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710 > When trying to resolve classes from this bundle it fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21490) Enforce non empty git source parameter in templates

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21490?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21490: -------------------------------- Fix Version/s: 4.3.1.CR1 > Enforce non empty git source parameter in templates > --------------------------------------------------- > > Key: JBIDE-21490 > URL: https://issues.jboss.org/browse/JBIDE-21490 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.3.1.CR1 > > > Following JBIDE-21340, we need to add validation of required git source parameter property in ParameterListPage. > To find out what parameter is the git repository url you'd do: > {code} > public String getGitRepoParameterKey() { > ITemplate template = model.getSelectedTemplate(); > if (template != null) { > for(String key : new String[]{"SOURCE_REPOSITORY_URL", "GIT_URI"}) { > if (template.getParameters().containsKey(key)) { > return key; > } > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21475) Use vagrant.bat to start vagrant

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21475?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-21475. --------------------------------- Resolution: Rejected > Use vagrant.bat to start vagrant > -------------------------------- > > Key: JBIDE-21475 > URL: https://issues.jboss.org/browse/JBIDE-21475 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Environment: Windows > Reporter: Denis Golovin > Priority: Blocker > > CDK adapter uses %VRGANT_PATH%\bin\vagrant to start vagrant on windows, but vargant file is a shell script. vagrant.bat should be used instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21475) Use vagrant.bat to start vagrant

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21475?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-21475: --------------------------------------- Original problem is in vagrant distributed through installer (see https://github.com/redhat-developer-tooling/vagrant-distribution) which has no vagrant.exe in it. Going to close it as 'Rejected'. I've opened issue for installer (see DEVEX-98). > Use vagrant.bat to start vagrant > -------------------------------- > > Key: JBIDE-21475 > URL: https://issues.jboss.org/browse/JBIDE-21475 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Environment: Windows > Reporter: Denis Golovin > Priority: Blocker > > CDK adapter uses %VRGANT_PATH%\bin\vagrant to start vagrant on windows, but vargant file is a shell script. vagrant.bat should be used instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21490) Enforce non empty git source parameter in templates

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21490: ----------------------------------- Summary: Enforce non empty git source parameter in templates Key: JBIDE-21490 URL: https://issues.jboss.org/browse/JBIDE-21490 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Fred Bricon Following JBIDE-21340, we need to add validation of required git source parameter property in ParameterListPage. To find out what parameter is the git repository url you'd do: {code} public String getGitRepoParameterKey() { ITemplate template = model.getSelectedTemplate(); if (template != null) { for(String key : new String[]{"SOURCE_REPOSITORY_URL", "GIT_URI"}) { if (template.getParameters().containsKey(key)) { return key; } } } return null; } {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21343) Kitchensink-cordova* quickstart example is not available from JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21343?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21343: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Kitchensink-cordova* quickstart example is not available from JBoss Central > --------------------------------------------------------------------------- > > Key: JBIDE-21343 > URL: https://issues.jboss.org/browse/JBIDE-21343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.1.Beta1 > Reporter: Pavol Srna > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21119: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21119 > URL: https://issues.jboss.org/browse/JBIDE-21119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > 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.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016