February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18917) Provide better error message when getJBossDiscoveryDirectory() returns null

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18917?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-18917: -------------------------------------- Assignee: Fred Bricon (was: Mickael Istria) > Provide better error message when getJBossDiscoveryDirectory() returns null > --------------------------------------------------------------------------- > > Key: JBIDE-18917 > URL: https://issues.jboss.org/browse/JBIDE-18917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.1.CR1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Optional > Fix For: 4.3.0.Alpha1 > > > This is followup of JBIDE-18819. > Now, the error message suggests user to check internet connection, but as I understand this, getJBossDiscoveryDirectory() could only return null when jboss.discovery.directory.url property is not set (meaning ide-config.properties was loaded, but does not contain jboss.discovery.directory.url for given version of JBT/JBDS). Thus internet is working but something wrong happened on ide-config.propertis side (our side). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- This is implemented and available. However, we still need to implement the mechanism that consume those data instead of the various files that are generated in publish.sh; and remove creation of useless files from publish.sh. > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15135: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15332: ---------------------------------------- So what's the status/expectation here? Should we close the issue as Out Of Date? Merge the PR I suggested? Postpone ticket resolution?... > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18559) when no updates available the full but empty p2 install UI is still shown

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18559?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18559: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > when no updates available the full but empty p2 install UI is still shown > ------------------------------------------------------------------------- > > Key: JBIDE-18559 > URL: https://issues.jboss.org/browse/JBIDE-18559 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > run check for updates from central with no updates available. > P2 ui with two step wizards is shown with no content. > Would have expected something like a simple "No updates found" instead. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18917) Provide better error message when getJBossDiscoveryDirectory() returns null

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18917?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18917: ---------------------------------------- [~fbricon] Can you please review and merge the suggested PR ASAP? Code-Freeze for Alpha1 is in a few hours, and review has been pending for weeks... Or, if you don't like the request, please close as Won't Fix and assign it to yourself. > Provide better error message when getJBossDiscoveryDirectory() returns null > --------------------------------------------------------------------------- > > Key: JBIDE-18917 > URL: https://issues.jboss.org/browse/JBIDE-18917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.1.CR1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.3.0.Alpha1 > > > This is followup of JBIDE-18819. > Now, the error message suggests user to check internet connection, but as I understand this, getJBossDiscoveryDirectory() could only return null when jboss.discovery.directory.url property is not set (meaning ide-config.properties was loaded, but does not contain jboss.discovery.directory.url for given version of JBT/JBDS). Thus internet is working but something wrong happened on ide-config.propertis side (our side). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19025: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-18535: ------------------------------ Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Opening of wizards from forge cheatsheet does not result in "attached cheatsheet" > --------------------------------------------------------------------------------- > > Key: JBIDE-18535 > URL: https://issues.jboss.org/browse/JBIDE-18535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, project-examples > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.3.0.Alpha2 > > Attachments: screenshot-1.png, screenshot-2.png > > > I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective. > But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-18535: ----------------------------------- No time yet to investigate properly, moving to 4.3.0.Alpha2 > Opening of wizards from forge cheatsheet does not result in "attached cheatsheet" > --------------------------------------------------------------------------------- > > Key: JBIDE-18535 > URL: https://issues.jboss.org/browse/JBIDE-18535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, project-examples > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.3.0.Alpha2 > > Attachments: screenshot-1.png, screenshot-2.png > > > I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective. > But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19164) Upgrade Forge Runtime to 2.14.0.Final

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19164?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19164: ---------------------------------------- eng-ops has added Maven 3.2.5 to Jenkins and builds are now working. So from a buid POV, there is nothing more to do with this issue. Feel free to close it if there is no more things to do. > Upgrade Forge Runtime to 2.14.0.Final > ------------------------------------- > > Key: JBIDE-19164 > URL: https://issues.jboss.org/browse/JBIDE-19164 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.2.3.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015