March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21725: ---------------------------------------- {quote}We can do that, but that would only be an improvement if we know some other repo wants to use it, no?{quote} On the mid-term, we can hope some component-specific tests will move to the same repository as the component they test, so that Red Deer would be used across multiple modules. > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Martin said: > {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. > I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. > After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. > What do you think? Makes sense? > So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} > Nick said: > {quote}Makes sense. When stable, add to TP; until stable, just use nightly. > Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21791: --------------------------------------------- ps. Forge would be a really really bad citizen if it had to force-save users files. > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21791 > URL: https://issues.jboss.org/browse/JBIDE-21791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: Claus Ibsen > Fix For: 4.3.1.CR1 > > Attachments: eclipse-add.png > > > Similar problem as FORGE-2605 but this time its in Eclipse. > See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog. > I wonder if the fix should be like in IDEA to save the file before the command is run. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21791: --------------------------------------------- can you check if this happen with any editor not just camel if you edit the file ? I would expect the editor to not complain before you use the editor again. So for now I would call this a fuse tools bug [~lhein] thoughts ? > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21791 > URL: https://issues.jboss.org/browse/JBIDE-21791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: Claus Ibsen > Fix For: 4.3.1.CR1 > > Attachments: eclipse-add.png > > > Similar problem as FORGE-2605 but this time its in Eclipse. > See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog. > I wonder if the fix should be like in IDEA to save the file before the command is run. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21725: --------------------------------------- [~mickael_istria], so you suggest instead of having this in [integration tests parent pom|https://github.com/jbosstools/jbosstools-integration-tests/blob/maste...]: {code} <reddeer-master-site>http://download.jboss.org/jbosstools/mars/snapshots/builds/reddeer_master/</reddeer-master-site> <reddeer-site>${reddeer-master-site}</reddeer-site> {code} To have this in [jbosstools parent pom|https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom...]: {code} <reddeer-site>http://download.jboss.org/jbosstools/mars/snapshots/builds/reddeer_master/</reddeer-site> {code} We can do that, but that would only be an improvement if we know some other repo wants to use it, no? Or you think it's beneficial even if it's just us who uses it? I'm fine with that. > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Martin said: > {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. > I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. > After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. > What do you think? Makes sense? > So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} > Nick said: > {quote}Makes sense. When stable, add to TP; until stable, just use nightly. > Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21725: ---------------------------------------- I believe if you want reddeer to evolve together with JBT and have JBT using nightly builds of Red Deer, the best is to define the site in JBT parent pom, like most jbosstools-whatever component. Then the module that need it can define the dependency to the repository. > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Martin said: > {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. > I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. > After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. > What do you think? Makes sense? > So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} > Nick said: > {quote}Makes sense. When stable, add to TP; until stable, just use nightly. > Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-565) Provide a hash file which contains only the hash sum

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-565?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-565: -------------------------------- Assignee: Paul Leacu > Provide a hash file which contains only the hash sum > ---------------------------------------------------- > > Key: JBTIS-565 > URL: https://issues.jboss.org/browse/JBTIS-565 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 9.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > > The following file > https://devstudio.redhat.com/9.0/staging/updates/integration-stack/devstu... > contains > {code} > dee28ecd1a6a8ca471a870f9daeb4ca5 /mnt/hudson_workspace/workspace/JBDSIS-aggregate-discovery/sources/devstudio/site-ea/target/site-ea-9.0.0-SNAPSHOT.zip > {code} > The hash sum is correct but the file name is incorrect and I suggest to remove it from that file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21386: ------------------------------------ Still to do: * mirror WTP, BIRT, other projects we use which are not already in Neon M5 mirror * update JBT/JBDS/Central TPs using Neon M5, WTP M5, m2e-apt 1.2, latest AERI 1.100, easymport, etc. * send emails to jbosstools-dev@ asking for feedback * merge changes to TPs; build * send emails to jbosstools-dev@ confirming changes applied& TPs updated * notify on JBDS-3600 that AERI 1.100.latest is updated in 4.60.x TP > Create and use Neon M5 target platform > -------------------------------------- > > Key: JBIDE-21386 > URL: https://issues.jboss.org/browse/JBIDE-21386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt > > > Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3649) is cygwin *really* required could we just use mingw

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3649?page=com.atlassian.jira.plugin.... ] Alexey Kazakov closed JBDS-3649. -------------------------------- Fix Version/s: 9.1.0.CR1 Resolution: Duplicate Issue Duplicates JBDS-3647 > is cygwin *really* required could we just use mingw > ---------------------------------------------------- > > Key: JBDS-3649 > URL: https://issues.jboss.org/browse/JBDS-3649 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Fix For: 9.1.0.CR1 > > > current installer installs cygwin - can we not just use mingw and make sure its available in path for users after the install is done ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3650) username used for cdk could not be used with vagrant up on cdk

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3650?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3650: -------------------------------------- [~maxandersen] I mentioned this issue before. Denis's user name doesn't have RHEL subscription needed for registration during vargrant up. We need to solve this problem so, users registered on the site will have all needed subscriptions or instructions what they need to do to use the product. > username used for cdk could not be used with vagrant up on cdk > -------------------------------------------------------------- > > Key: JBDS-3650 > URL: https://issues.jboss.org/browse/JBDS-3650 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Reporter: Max Rydahl Andersen > Priority: Blocker > > in demo by [~dgolovin] he mentions the username used for running the installer could not be used with vagrant registration. > Why is that ? just unique for denis usernames or general problem ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3649) is cygwin *really* required could we just use mingw

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3649?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3649: -------------------------------------- Priority: Major (was: Critical) > is cygwin *really* required could we just use mingw > ---------------------------------------------------- > > Key: JBDS-3649 > URL: https://issues.jboss.org/browse/JBDS-3649 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > > current installer installs cygwin - can we not just use mingw and make sure its available in path for users after the install is done ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016