June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19598: ------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19986) Updatesite contains Beta2 version plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19986?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19986. ------------------------------ Verified, closing. > Updatesite contains Beta2 version plugins > ----------------------------------------- > > Key: JBIDE-19986 > URL: https://issues.jboss.org/browse/JBIDE-19986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Beta1 > > > Namely: > o.j.t.common.* > o.j.t.foundation.* > o.j.t.runtime > o.j.t.stacks > o.j.t.usage -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18985) provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18985?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18985: ------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated > ----------------------------------------------------------------------- > > Key: JBIDE-18985 > URL: https://issues.jboss.org/browse/JBIDE-18985 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Based on discussion {quote}Do you have a test for "expected BUILD_ALIAS value in feature qualifiers" ?{quote} > Some tests we can run (forgive this pseudocode): > {code} > // for builds up to a x.y.0 release > if ((BUILD_ALIAS in (Alpha*, Beta*, CR*) and jbosstools.version endsWith(".0")) { > // make sure all features end in the same BUILD_ALIAS, or Final > // if anything doesn't match WARN (want a build to be yellow, not red) > } > {code} > {code} > // for GA builds and followup maintenance > if ((BUILD_ALIAS in (Final, GA)) { > // make sure all com.* features end in GA, and all others end in Final > // if anything doesn't match FAIL (want a build to be red) > } > {code} > Once we have that coded, perhaps into a maven enforcer plugin?, we can fine tune it for cases like where Freemarker does an update in Alpha and then does nothing for 4 months, waiting for CR/GA. > Should they have to keep updating their root pom just so the BUILD_ALIAS matches and they're building against the correct target platform? > Or, should their code remain dormant, but their job's config.xml be updated to override the BUILD_ALIAS & TARGET_PLATFORM values to the correct versions? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19986) Updatesite contains Beta2 version plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19986?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19986: ------------------------------------ To avoid this sort of problem in the future, see JBIDE-18985 > Updatesite contains Beta2 version plugins > ----------------------------------------- > > Key: JBIDE-19986 > URL: https://issues.jboss.org/browse/JBIDE-19986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Critical > Labels: respin-a > Fix For: 4.3.0.Beta1 > > > Namely: > o.j.t.common.* > o.j.t.foundation.* > o.j.t.runtime > o.j.t.stacks > o.j.t.usage -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3408. ------------------------------ Resolution: Done PR merged in Beta1x and master. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3408: ----------------------------- Labels: respin-a (was: ) > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Labels: respin-a > Fix For: 9.0.0.Beta1 > > Attachments: JBDS3408.install.jboss-devstudio-9.0.0.Beta1-v20150430-1113-B3095-installer-standalone.jar.log.txt > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3432) create verification test - JBDS update site(s) and installer should not contain <references> to external URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3432?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3432: ----------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > create verification test - JBDS update site(s) and installer should not contain <references> to external URLs > ------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3432 > URL: https://issues.jboss.org/browse/JBDS-3432 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: build, installer, updatesite > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > We ought to have some sort of maven-based verification test that can unpack the update site zip and installer, and verify that the p2 metadata doesn't reference any unexpected 3rd party URLs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20005) Navigation to Batch artifacts from properties editor

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-20005: -------------------------------------- Summary: Navigation to Batch artifacts from properties editor Key: JBIDE-20005 URL: https://issues.jboss.org/browse/JBIDE-20005 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: batch Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta2 It would be useful to be able to navigate from Properties editor and Tree form editor tab (feel free to create a separate issue if needed) to the corresponding artifact. If the reference is empty then the new artifact wizard should be opened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19997) Add possibility to select interface and abstract class in New Batch Artifact wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19997?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-19997 at 6/9/15 1:35 PM: ----------------------------------------------------------------------- There was a doubt about advantages of New Batch Artifact wizard over the common New Class wizard. When I just select kind of Batch artifact and then either accept default 'abstract' choice or have to at maximum click radio for 'interface' choice, I see some advantage. If user has to both select artifact and then browse for superclass/interface, I suspect most users may prefer New Class wizard. I may suggest a solution: Preserve radio buttons and add below dropdown 'Type' that by default displays out-of-box class/interface and lists all available types. was (Author: scabanovich): There was a doubt about advantages of New Batch Artifact wizard over the common New Class wizard. When I just select kind of Batch artifact and then either accept default 'abstract' choice or have to at maximum click radio for 'interface' choice, I see some advantage. If user has to both select artifact and then browse for superclass/interface, I suspect most users may prefer New Class wizard. I may suggest a solution: Preserve radio buttons and add below dropdown 'Type' that by default displays out-of-box class/interface and list all available types. > Add possibility to select interface and abstract class in New Batch Artifact wizard > ----------------------------------------------------------------------------------- > > Key: JBIDE-19997 > URL: https://issues.jboss.org/browse/JBIDE-19997 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > I think that in every bigger enterprise project you would have your own implementation of batch interfaces and abstract classes. So the possibility to select them in the New Batch Artifact wizard would be very useful. > Maybe you could just put there interface and abstract class selection section from New Java Class wizard and pre-define the right batch classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19590: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015