May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (LOCUS-13) Build number in qualifier are against reproducible version qualifier

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/LOCUS-13?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on LOCUS-13: --------------------------------- My issue was this: {code} [ERROR] Resolution failed: [ERROR] Software being installed: org.jboss.tools.locus.mockito 1.9.5.Final_patched_TEIIDDES-1681-v20131024-0922-B58 [ERROR] Software being installed: org.jboss.tools.locus.mockito 1.9.5.Final_patched_TEIIDDES-1681-v20131024-0922-B77 [ERROR] Only one of the following can be installed at once: [org.jboss.tools.locus.mockito 1.9.5.Final_patched_TEIIDDES-1681-v20131024-0922-B77, org.jboss.tools.locus.mockito 1.9.5.Final_patched_TEIIDDES-1681-v20131024-0922-B58] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE {code} The JBTIS TP was including mockito from locus as was the JBT core TP. I simply removed the JBTIS TP mockito reference. > Build number in qualifier are against reproducible version qualifier > -------------------------------------------------------------------- > > Key: LOCUS-13 > URL: https://issues.jboss.org/browse/LOCUS-13 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 1.2.0 > > > We did set up git-based reproducible qualifiers but in the other end, we have the qualifier always changing because it contains the BUILD_NUMBER. > Those metadata should not be part of the qualifier, but should instead be in a future index.html, or attached to the Maven artifact. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Martin Schröder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Martin Schröder updated JBIDE-19772: ------------------------------------ Attachment: jbosstools-diagnostics-20150506142332.zip > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Martin Schröder > Attachments: jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Martin Schröder (JIRA)

Martin Schröder created JBIDE-19772: --------------------------------------- Summary: Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 Key: JBIDE-19772 URL: https://issues.jboss.org/browse/JBIDE-19772 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Martin Schröder I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-13) Build number in qualifier are against reproducible version qualifier

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/LOCUS-13?page=com.atlassian.jira.plugin.s... ] Mickael Istria commented on LOCUS-13: ------------------------------------- {quote}when I used other builds using reproducible version qualifiers it was not possible to build without committing all code first. Very tedious to work with.{quote} This is not really an issue with reproducible version qualifier, but with Git-based timestamps, that we've already been using for a year and half in Locus, so this is a separate thing. {quote}For me SNAPSHOT makes perfect sense for a build for testing, but when doing the release we shouldn't ever have SNAPSHOT in this so not sure I follow the problem.{quote} The principle of reproducible version qualifier is that they also reuse artifacts from baseline when available. https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers If we put SNAPSHOT in testing, then testing won't consume artifacts from baseline (that wouldn't be SNASPHOTs), and the output would be too far from the output of a release. > Build number in qualifier are against reproducible version qualifier > -------------------------------------------------------------------- > > Key: LOCUS-13 > URL: https://issues.jboss.org/browse/LOCUS-13 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 1.2.0 > > > We did set up git-based reproducible qualifiers but in the other end, we have the qualifier always changing because it contains the BUILD_NUMBER. > Those metadata should not be part of the qualifier, but should instead be in a future index.html, or attached to the Maven artifact. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-13) Build number in qualifier are against reproducible version qualifier

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/LOCUS-13?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on LOCUS-13: ------------------------------------------ when I used other builds using reproducible version qualifiers it was not possible to build without committing all code first. Very tedious to work with. For me SNAPSHOT makes perfect sense for a build for testing, but when doing the release we shouldn't ever have SNAPSHOT in this so not sure I follow the problem. > Build number in qualifier are against reproducible version qualifier > -------------------------------------------------------------------- > > Key: LOCUS-13 > URL: https://issues.jboss.org/browse/LOCUS-13 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 1.2.0 > > > We did set up git-based reproducible qualifiers but in the other end, we have the qualifier always changing because it contains the BUILD_NUMBER. > Those metadata should not be part of the qualifier, but should instead be in a future index.html, or attached to the Maven artifact. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-19007. --------------------------------- Verified in JBDS 9.0.0.Alpha2 build ID B25. > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19768: ---------------------------------------- That's indeed one of the hot topics. The import mechanism currently doesn't integrate a concept of "project candidate". The difficulty comes from the fact that choosing of importing or not a project can affect how it would import its parent. > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Priority: Critical > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19765) Add description to easy import wizard

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19765?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19765: -------------------------------------- Assignee: Mickael Istria > Add description to easy import wizard > ------------------------------------- > > Key: JBIDE-19765 > URL: https://issues.jboss.org/browse/JBIDE-19765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Attachments: wizard.png > > > There is no descrption of the wizard (see picture attached). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19765) Add description to easy import wizard

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19765?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19765: ---------------------------------------- Suggested Gerrit patch: https://git.eclipse.org/r/47287 [~ljelinko] Can you please check the suggested text, and suggest improvements on the Gerrit review? > Add description to easy import wizard > ------------------------------------- > > Key: JBIDE-19765 > URL: https://issues.jboss.org/browse/JBIDE-19765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Attachments: wizard.png > > > There is no descrption of the wizard (see picture attached). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-13) Build number in qualifier are against reproducible version qualifier

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/LOCUS-13?page=com.atlassian.jira.plugin.s... ] Mickael Istria commented on LOCUS-13: ------------------------------------- I'm not sure how to interpret your answer. Is it ok to remove the SNAPSHOT/Final distinction in build? > Build number in qualifier are against reproducible version qualifier > -------------------------------------------------------------------- > > Key: LOCUS-13 > URL: https://issues.jboss.org/browse/LOCUS-13 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 1.2.0 > > > We did set up git-based reproducible qualifiers but in the other end, we have the qualifier always changing because it contains the BUILD_NUMBER. > Those metadata should not be part of the qualifier, but should instead be in a future index.html, or attached to the Maven artifact. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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