December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23595) Integration tests global refactoring: org.jboss.tools.vpe.bot.test

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23595?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-23595: -------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests global refactoring: org.jboss.tools.vpe.bot.test > ------------------------------------------------------------------ > > Key: JBIDE-23595 > URL: https://issues.jboss.org/browse/JBIDE-23595 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests, vpe > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.vpe.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23595) Integration tests global refactoring: org.jboss.tools.vpe.bot.test

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23595?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23595: ------------------------------------- [~jeffmaury] could you please give some info about the issue? what exactly should be done here ? > Integration tests global refactoring: org.jboss.tools.vpe.bot.test > ------------------------------------------------------------------ > > Key: JBIDE-23595 > URL: https://issues.jboss.org/browse/JBIDE-23595 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: integration, integration_tests, vpe > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.vpe.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23536: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, release, release-eng > Fix For: 4.4.3.AM2 > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23322: ------------------------------- Fix Version/s: 4.5.x (was: 4.4.3.AM1) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 2 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23318) fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23318?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23318: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > fork master branch into master and 4.4.x branches, so that master can be for oxygen and 4.4.x can be for Neon.2 and .3 work > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23318 > URL: https://issues.jboss.org/browse/JBIDE-23318 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.x, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2, 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19933: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.2.Final) > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19933: ------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.3.AM1) > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Fix Version/s: 4.4.3.AM3 (was: 4.4.3.AM1) > move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline) > ------------------------------------------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.AM3, 4.5.0.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23653) Add eGit git flow plugin to devstudio and jbosstools?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23653?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23653 at 12/16/16 12:23 PM: --------------------------------------------------------------- [~jeffmaury] do we want to include this in 4.4.3.AM2 and/or 10.3.0.AM2? If so, please see my clarifying questions above. was (Author: nickboldt): [~jeffmaury] do we want to include this in 4.4.3.AM2? > Add eGit git flow plugin to devstudio and jbosstools? > ----------------------------------------------------- > > Key: JBIDE-23653 > URL: https://issues.jboss.org/browse/JBIDE-23653 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Affects Versions: 4.4.2.Final > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23653) Add eGit git flow plugin to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23653?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23653: ------------------------------- Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBIDE-23653 (was: JBDS-4172) Docs QE Status: (was: NEW) Component/s: central-update (was: build) (was: updatesite) Affects Version/s: 4.4.2.Final (was: 10.2.0.AM3) Fix Version/s: 4.4.3.AM2 (was: 10.x) > Add eGit git flow plugin to devstudio > ------------------------------------- > > Key: JBIDE-23653 > URL: https://issues.jboss.org/browse/JBIDE-23653 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Affects Versions: 4.4.2.Final > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016