January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19018) JBT Central Discovery staging site contains early access child site in its composite*.xml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19018?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19018: --------------------------------------------- yes, but it points to the same url. it should be something like: {{{ jboss.discovery.earlyaccess.site.url|jbosstools|4.2.2.CR1=http://download... }}} and remove the EA child entry from http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/compos... and http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/compos... > JBT Central Discovery staging site contains early access child site in its composite*.xml > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19018 > URL: https://issues.jboss.org/browse/JBIDE-19018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.2.Final, 4.2.3.Final > > > http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/ composites early access site into the main update site, so anyone using that site as an update site (rather than simply as the back end to Central) will see EA content as if it's from Central. > If we stop publishing this staging discovery site that includes EA content, the release process will need to be updated to pull the EA plugin from another place. > Related to JBIDE-18984 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19017: ------------------------------------ Jobs enabled: *Projects* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *Composites/Aggregates* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... *Verification Tests* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... I have NOT enabled webtools and hibernatetools aggregate builds because there's nothing new. This means when it's time to release, we have to remember to OMIT those steps. > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by James Cobb (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] James Cobb commented on JBDS-3275: ---------------------------------- Commented in: https://issues.jboss.org/browse/DESIGN-659 > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-378) Update bpmn2 for IS beta2 TP and aggregate - bpmn2 feature source bundle

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-378?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-378: ----------------------------- Description: *Reason:* Create .Final - pick up a bpmn2 feature source bundle. *Project page/sources:* *Version:* 4.2.0.Final *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected projects:* JBDSIS 8.0.0.GA *Include in JBDS:* No *Type of dependency:* distribution *List of bundles added/removed:* < org.eclipse.bpmn2.editor [0.7.0.201308220617] < org.eclipse.bpmn2.edit [0.7.0.201308220617] < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201412181844] < org.eclipse.bpmn2.feature.feature.jar [0.7.0.201308220617] < org.eclipse.bpmn2 [0.7.0.201308220617] < org.eclipse.bpmn2.modeler.help [1.1.1.201412181844] < org.eclipse.bpmn2.feature.feature.group [0.7.0.201308220617] < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201412181844] < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201412181844] < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201412181844] < org.eclipse.bpmn2.modeler.core [1.1.1.201412181844] < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201412181844] < org.eclipse.bpmn2.modeler.ui [1.1.1.201412181844] > org.eclipse.bpmn2.modeler.help [1.1.1.201501081320] > org.eclipse.bpmn2 [1.0.0.201412192138] > org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201501081320] > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201501081320] > org.eclipse.bpmn2.editor [1.0.0.201412192138] > org.eclipse.bpmn2.modeler.feature.group [1.1.1.201501081320] > org.eclipse.bpmn2.modeler.ui [1.1.1.201501081320] > org.eclipse.bpmn2.modeler.core [1.1.1.201501081320] > org.eclipse.bpmn2.edit [1.0.0.201412192138] > org.eclipse.bpmn2.feature.jar [1.0.0.201412192138] > org.eclipse.bpmn2.feature.group [1.0.0.201412192138] > org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201501081320] > org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201501081320] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 13 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 13 unique IUs was: *Reason:* Create .Final - pick up a bpmn2 feature source bundle. *Project page/sources:* *Version:* 4.2.0.Final *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected projects:* JBDSIS 8.0.0.GA *Include in JBDS:* No *Type of dependency:* distribution *List of bundles added/removed:* > Update bpmn2 for IS beta2 TP and aggregate - bpmn2 feature source bundle > ------------------------------------------------------------------------ > > Key: JBTIS-378 > URL: https://issues.jboss.org/browse/JBTIS-378 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: BPMN2, distribution > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.0.Final-TP > > > *Reason:* Create .Final - pick up a bpmn2 feature source bundle. > *Project page/sources:* > *Version:* 4.2.0.Final > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected projects:* JBDSIS 8.0.0.GA > *Include in JBDS:* No > *Type of dependency:* distribution > *List of bundles added/removed:* > < org.eclipse.bpmn2.editor [0.7.0.201308220617] > < org.eclipse.bpmn2.edit [0.7.0.201308220617] > < org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201412181844] > < org.eclipse.bpmn2.feature.feature.jar [0.7.0.201308220617] > < org.eclipse.bpmn2 [0.7.0.201308220617] > < org.eclipse.bpmn2.modeler.help [1.1.1.201412181844] > < org.eclipse.bpmn2.feature.feature.group [0.7.0.201308220617] > < org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201412181844] > < org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201412181844] > < org.eclipse.bpmn2.modeler.feature.group [1.1.1.201412181844] > < org.eclipse.bpmn2.modeler.core [1.1.1.201412181844] > < org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201412181844] > < org.eclipse.bpmn2.modeler.ui [1.1.1.201412181844] > > org.eclipse.bpmn2.modeler.help [1.1.1.201501081320] > > org.eclipse.bpmn2 [1.0.0.201412192138] > > org.eclipse.bpmn2.modeler.runtime.jboss.feature.jar [1.1.1.201501081320] > > org.eclipse.bpmn2.modeler.runtime.jboss.jbpm5 [1.1.1.201501081320] > > org.eclipse.bpmn2.editor [1.0.0.201412192138] > > org.eclipse.bpmn2.modeler.feature.group [1.1.1.201501081320] > > org.eclipse.bpmn2.modeler.ui [1.1.1.201501081320] > > org.eclipse.bpmn2.modeler.core [1.1.1.201501081320] > > org.eclipse.bpmn2.edit [1.0.0.201412192138] > > org.eclipse.bpmn2.feature.jar [1.0.0.201412192138] > > org.eclipse.bpmn2.feature.group [1.0.0.201412192138] > > org.eclipse.bpmn2.modeler.runtime.jboss.feature.group [1.1.1.201501081320] > > org.eclipse.bpmn2.modeler.feature.jar [1.1.1.201501081320] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 13 unique IUs > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 13 unique IUs -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19016) UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19016?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-19016: ----------------------------------------- Eclipse does not provide a dialog to select a file or a directory natively. Thoughts? > UI Wizards should default Resource<?> UIInput types to support selecting a File OR Directory > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19016 > URL: https://issues.jboss.org/browse/JBIDE-19016 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Lincoln Baxter III > > There is currently no way to hint to the IDE to allow an input to select a file OR directory in Eclipse. I assume this will also be problematic in other IDEs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18678: ---------------------------------------- It worked fine because you had usage impl plugin installed. But suppose you have a plain Eclipse and want to install browsersim. But because the current browsersim depends on usage api only, you will get the browsersim and usage api plugin and you will miss usage imp. > Make dependencies to org.jboss.tools.usage optional > --------------------------------------------------- > > Key: JBIDE-18678 > URL: https://issues.jboss.org/browse/JBIDE-18678 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim, usage > Affects Versions: 4.2.0.CR1 > Reporter: Kaloyan Raev > Assignee: Alexey Kazakov > Fix For: 4.3.x > > > I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build. > Is it possible to make the dependencies to org.jboss.tools.usage optional? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19017: ------------------------------- Priority: Blocker (was: Major) > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19017: ------------------------------------ According to Github, all three projects (Central, WS, Forge) have committed changes to 4.2.x branch without upverisioning the project's features'/plugins' versions. Please ensure that your plugins/features are a larger version than what you released in 4.2.1. Thanks! cc: [~maxandersen] [~mickael_istria] [~koen.aers] [~xcoulon] [~fbricon] > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19017: ------------------------------- Description: TODOs for preparing for the 4.2.2 release. For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. was: TODOs for preparing for the 4.2.2 release. For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: a) ensure we're all using the right TP & parent pom b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19018) staging site contains earlyaccess

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19018?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19018: ------------------------------------ ide-config.properties already does that for staging sites. eg., https://github.com/jbosstools/jbosstools-download.jboss.org/commit/dc2d80... > staging site contains earlyaccess > ---------------------------------- > > Key: JBIDE-19018 > URL: https://issues.jboss.org/browse/JBIDE-19018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.2.Final, 4.2.3.Final > > > http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/ composites early access site into the main update site, so anyone using that site as an update site (rather than simply as the back end to Central) will see EA content as if it's from Central. > If we stop publishing this staging discovery site that includes EA content, the release process will need to be updated to pull the EA plugin from another place. > Related to JBIDE-18984 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 January 2015