July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3264) Remove welcome/intro page

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-3264?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-3264: --------------------------------------- Thanks [~mickael_istria] but I'm not working on JBDS any more so I'll leave the decision to you guys. > Remove welcome/intro page > ------------------------- > > Key: JBDS-3264 > URL: https://issues.jboss.org/browse/JBDS-3264 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: ui/branding > Affects Versions: 8.0.0.GA > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 9.0.0.Beta2 > > > The welcome page for JBDS is really useless. It doesn't provide any value to the user. Moreover, it looks quite old-fashioned. > In such case, it would be better to remove it and prevent users from seeing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20183) jbosstools-server bundles have compilation problems after importing into workspace

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20183?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20183: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-server/pull/355 (was: https://github.com/jbosstools/jbosstools-server/pull/354) > jbosstools-server bundles have compilation problems after importing into workspace > ---------------------------------------------------------------------------------- > > Key: JBIDE-20183 > URL: https://issues.jboss.org/browse/JBIDE-20183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > org.jboss.ide.eclipse.as.management.wildfly8 should have m2e feature enabled to download required libraries after importing into workspace. > there are also errors about missing indirectly referenced classes in: > * org.jboss.ide.eclipse.archives.ui > * org.jboss.ide.eclipse.as.core > which I solved by re-exporting dependencies. > See linked PR for details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20181) Add m2e nature to o.j.openshift.client and o.j.openshift.client projects

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20181?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20181: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/688 (was: https://github.com/jbosstools/jbosstools-openshift/pull/687) > Add m2e nature to o.j.openshift.client and o.j.openshift.client projects > ------------------------------------------------------------------------ > > Key: JBIDE-20181 > URL: https://issues.jboss.org/browse/JBIDE-20181 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > This is required in relation to JBIDE-19590 to avoid additional steps after importing project from freshly cloned git repository. There is no lib repository until project built at least once, hence after import I have to manually convert it to maven project and update maven project model to download required libraries and update project classpath. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20183) jbosstools-server bundles have compilation problems after importing into workspace

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20183?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20183: ---------------------------------- Fix Version/s: 4.3.0.Beta2 > jbosstools-server bundles have compilation problems after importing into workspace > ---------------------------------------------------------------------------------- > > Key: JBIDE-20183 > URL: https://issues.jboss.org/browse/JBIDE-20183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > org.jboss.ide.eclipse.as.management.wildfly8 should have m2e feature enabled to download required libraries after importing into workspace. > there are also errors about missing indirectly referenced classes in: > * org.jboss.ide.eclipse.archives.ui > * org.jboss.ide.eclipse.as.core > which I solved by re-exporting dependencies. > See linked PR for details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20183) jbosstools-server bundles have compilation problems after importing into workspace

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20183: ------------------------------------- Summary: jbosstools-server bundles have compilation problems after importing into workspace Key: JBIDE-20183 URL: https://issues.jboss.org/browse/JBIDE-20183 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build, server Affects Versions: 4.3.0.Beta2 Reporter: Denis Golovin Assignee: Rob Stryker org.jboss.ide.eclipse.as.management.wildfly8 should have m2e feature enabled to download required libraries after importing into workspace. there are also errors about missing indirectly referenced classes in: * org.jboss.ide.eclipse.archives.ui * org.jboss.ide.eclipse.as.core which I solved by re-exporting dependencies. See linked PR for details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19590: --------------------------------------- I pushed all my changes ti templatized-setup branch, it seems to work, but still requires some manual steps to resolve compilation problems (this is work in progress to fix see related issues). > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20182) Oomph project import task doesn't import livereload feature

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20182: ------------------------------------- Summary: Oomph project import task doesn't import livereload feature Key: JBIDE-20182 URL: https://issues.jboss.org/browse/JBIDE-20182 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, livereload Affects Versions: 4.3.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Feature is not imported into workspace for livereload setup project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20136) Batch diagram generates references in <next> element

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20136?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20136 at 7/2/15 8:33 PM: ----------------------------------------------------------------------- For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. Of course, it makes no sense. I still cannot find if we can prevent it. was (Author: scabanovich): For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. I still cannot find if we can prevent it. > Batch diagram generates references in <next> element > ---------------------------------------------------- > > Key: JBIDE-20136 > URL: https://issues.jboss.org/browse/JBIDE-20136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > Attachments: diagram.png, editor.png > > > I created two steps in batch diagram editor without the ID specified and connected them with "Next on" element. In source view, the "to" values contained some unusual values like "StepNode#0" (see attachmets). > For "Next" element is the behaviour different - editor would not allow me to create connection at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20136) Batch diagram generates references in <next> element

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20136?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20136: ----------------------------------------------- For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. I still cannot find if we can prevent it. > Batch diagram generates references in <next> element > ---------------------------------------------------- > > Key: JBIDE-20136 > URL: https://issues.jboss.org/browse/JBIDE-20136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > Attachments: diagram.png, editor.png > > > I created two steps in batch diagram editor without the ID specified and connected them with "Next on" element. In source view, the "to" values contained some unusual values like "StepNode#0" (see attachmets). > For "Next" element is the behaviour different - editor would not allow me to create connection at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20181) Add m2e nature to o.j.openshift.client and o.j.openshift.client projects

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20181?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20181: ---------------------------------- Fix Version/s: 4.3.0.Beta2 > Add m2e nature to o.j.openshift.client and o.j.openshift.client projects > ------------------------------------------------------------------------ > > Key: JBIDE-20181 > URL: https://issues.jboss.org/browse/JBIDE-20181 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Fix For: 4.3.0.Beta2 > > > This is required in relation to JBIDE-19590 to avoid additional steps after importing project from freshly cloned git repository. There is no lib repository until project built at least once, hence after import I have to manually convert it to maven project and update maven project model to download required libraries and update project classpath. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015