February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-16402: ----------------------------------- I haven't been able to reproduce this on OSX, on Windows 7 & 8 nor on Fedora 20. So I'll resolve this as 'Cannot Reproduce Bug'. Feel free to reopen with clear instructions on how to reproduce this if the need would still exist. > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.1.2.CR1, 4.2.0.Beta1 > > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-245?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-245: ------------------------------------------- Last years promises was that we would at least get alpha builds running so we are not yet repeating not having IS tooling at all available for next release of JBDS 8. Could we at least do one that contains the components that will work on Luna out of the box ? We have many things that need IS feedback for the changes we are doing in JBT core/JBDS core like based on bug reports from users and IS QE: * Runtime less server to allow defining a server without having a local runtime * Refactored JBoss server adapter to have better management support (incl. wildfly/eap 6.x new requirements) * Allow installation of earlyaccess components from Central Luna itself is what will provide: * Java 8 support * Support for eclipse on newer Linux versions (GTK3 on fedora 20/Ubuntu) - kepler will and does have issues. * much faster maven import/support ...and of course bugfixes etc. > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-245 > URL: https://issues.jboss.org/browse/JBTIS-245 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Greetings - welcome to Luna! > An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. > I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. > Thanks! > [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... > [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16402) A newly created project is not imported into Eclipse when the project location is non-existent

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16402?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-16402. ------------------------------- Resolution: Cannot Reproduce Bug > A newly created project is not imported into Eclipse when the project location is non-existent > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-16402 > URL: https://issues.jboss.org/browse/JBIDE-16402 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Vineet Reynolds > Assignee: Koen Aers > Fix For: 4.1.2.CR1, 4.2.0.Beta1 > > > When a non-existent location is specified in Eclipse, Forge creates the project, but fails to import the project into the Eclipse workspace. > This also seems to be related to an issue where the Location field is not pre-filled (not sure why; I'm reporting this bug on behalf of a user, so I'm hoping to get more details). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2864: ------------------------------- CDW devel_ack: + (was: ?) > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Jiri Pallich commented on JBDS-2864: ------------------------------------ Setting pm_ack on behalf of Burr and restoring devel_ack. > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2864: ------------------------------- CDW pm_ack: + (was: ?) > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2864: ----------------------------- CDW qa_ack: ? > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2864: -------------------------------------- Component/s: requirements > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2864: ----------------------------- CDW devel_ack: ? (was: +) > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2950) Target Platform Requirements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2950?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2950: -------------------------------------- Description: Work that defines which java, OS, eclipse dependencies we need/use. > Target Platform Requirements > ---------------------------- > > Key: JBDS-2950 > URL: https://issues.jboss.org/browse/JBDS-2950 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > > Work that defines which java, OS, eclipse dependencies we need/use. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 February 2014