October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21012: ---------------------------------------- The reasons why this was experimentally implemented are in JBIDE-16128 . However, it's now pretty clear that we're not able/not willing to bump Maven artifacts versions between milestones, so it makes that we're not able to use Nexus in our build pipeline. I wouldn't mind if we remove the deploy step from CI jobs. > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21012: ------------------------------------ That's true in theory as of this moment, it's currently impossible. We need a way to ensure that there's an unpacked update site in nexus, such as: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... Currently that folder exists but is empty. Once it has content, we can start using it in parent pom [0] and composite*.xml [1] in place of what's currently there. [0] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/_composite_/co... Perhaps we need to add a *build-helper-maven-plugin::package::attach-artifact* build step to each update site pom, as we do for Locus [2]? [2] https://github.com/jbosstools/jbosstools-locus/blob/master/deployment/pom... Or for the sake of reuse, perhaps it's better in the parent pom. We could add it to the existing deploy-to-jboss.org profile, or create a new *deploy-to-nexus-unzip* profile? [~mickael_istria] WDYT? > Why do we deploy JBT components to Nexus snapshots repo? > -------------------------------------------------------- > > Key: JBIDE-21012 > URL: https://issues.jboss.org/browse/JBIDE-21012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo. > But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just: > * eat disk space in Nexus > * consume time/resources in Jenkins > Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3553: ------------------------------------ +1 too! > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3553: ----------------------------------- +1 > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3518) Eclipse-cs update to 6.9.0 on JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3518?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3518: -------------------------------------- Assigning to [~nickboldt] since he was much more active in this discussion so I believe he's the best one to take care of that change, but feel free to reassign to me if you want that I specifically apply the necessary changes. > Eclipse-cs update to 6.9.0 on JBoss Central > ------------------------------------------- > > Key: JBDS-3518 > URL: https://issues.jboss.org/browse/JBDS-3518 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: 3rd-party-certification, build, central > Affects Versions: 9.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 9.0.1.Beta1 > > Attachments: checkstyle.png > > > I've checked Release 6.9.0 with JBDS 9.0.0.CR1 and experienced no issues. > Changes since last version: http://eclipse-cs.sourceforge.net/#!/releasenotes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3518) Eclipse-cs update to 6.9.0 on JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3518?page=com.atlassian.jira.plugin.... ] Mickael Istria reassigned JBDS-3518: ------------------------------------ Assignee: Nick Boldt (was: Mickael Istria) > Eclipse-cs update to 6.9.0 on JBoss Central > ------------------------------------------- > > Key: JBDS-3518 > URL: https://issues.jboss.org/browse/JBDS-3518 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: 3rd-party-certification, build, central > Affects Versions: 9.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 9.0.1.Beta1 > > Attachments: checkstyle.png > > > I've checked Release 6.9.0 with JBDS 9.0.0.CR1 and experienced no issues. > Changes since last version: http://eclipse-cs.sourceforge.net/#!/releasenotes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-527: -------------------------------- Assignee: Paul Leacu > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.A... I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-526) JBDSIS on marketplace contains category for WTP patches

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-526?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-526: -------------------------------- Assignee: Paul Leacu > JBDSIS on marketplace contains category for WTP patches > ------------------------------------------------------- > > Key: JBTIS-526 > URL: https://issues.jboss.org/browse/JBTIS-526 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.3.GA > Environment: Eclipse Luna JEE SR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis803_marketplace_features.png > > > JBDSIS on marketplace contains category for WTP patches. Is this really intended (see the attached screenshot)? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3553: --------------------------------- Fix Version/s: 9.0.1.Beta1 > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3553: ------------------------------------ Assignee: Mickael Istria Agreed. We should enable it in JBDS. [~mickael_istria] could you take care of it? > Integrate/Enable CodeRecommenders substring completion in JBDS > -------------------------------------------------------------- > > Key: JBDS-3553 > URL: https://issues.jboss.org/browse/JBDS-3553 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 9.0.1.Beta1 > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. -- 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 October 2015