February 2014 - jbosstools-issues

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBTIS-253?page=com.atlassian.jira.plugin.... ] Barry LaFond commented on JBTIS-253: ------------------------------------ Teiid Designer 8.4 Final should be released early next week, hopefully 3/3. We'll upgrade our TP right after that but we won't have a milestone to tag as our IS contribution for awhile. Not sure how to transition smoothly yet and keep on project schedule. > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-253 > URL: https://issues.jboss.org/browse/JBTIS-253 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Barry LaFond > > 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-16292) Need to restore ability to select specific archetype version per runtime in Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16292?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-16292 at 2/27/14 4:39 AM: -------------------------------------------------------------- PR https://github.com/jbosstools/jbosstools-central/pull/218 When selecting an enterprise runtime, we try to look for the matching product version of an archetype type. If the runtime doesn't define an enterprise archetype, the closest archetype version (community) defined on this runtime will take precedence. Until now, it would take the next available product archetype from another enterprise runtime : eg. if EAP 6.0 only had mobile-html5 community, it would pick the mobile-html5 product version from EAP 6.2. Now it will return mobile-html5 community. In practice, the current stacks.yaml file doesn't currently provide ways to test the fix (unit tests do), We'll have to wait for WFK 2.5 archetypes to be added to EAP 6.2 to see it work was (Author: fbricon): PR https://github.com/jbosstools/jbosstools-central/pull/218 When selecting an enterprise runtime, we try to look for the matching product version of an archetype type. If the runtime doesn't define an enterprise archetype, the closest archetype version (community) defined on this runtime will take precedence. Until now, it would take the next available product archetype from another enterprise runtime : eg. if EAP 6.0 only had mobile-html5 community, it would pick the mobile-html5 product version from EAP 6.2. Now it will return mobile-html5 community. In practice, the current stacks.yaml file doesn't currently provide ways to test the fix (unit tests do), We'll have to wwait for WFK 2.5 archetypes to be added to EAP 6.2 to see it work > Need to restore ability to select specific archetype version per runtime in Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-16292 > URL: https://issues.jboss.org/browse/JBIDE-16292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.2.CR1 > > > The changes done in JBIDE-15645 introduced a regression in the way archetypes are selected. > Basically, we can get different archetype versions depending on the EE version of the runtime (web/full-ee6 vs web/full-ee7) but we lost the ability to pick a different archetype version between 2 different runtimes of the same product and same EE level (eg. EAP 6.1 vs EAP 6.2) > As a consequence, archetype versions designed to run on EAP 6.2 will be selected when EAP 6.1 is selected in the project wizard. > Hopefully EAP 6.2 archetypes will still be able to run on EAP 6.1 so that shouldn't be a problem, but we should fix that for the next minor release. -- 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-2946) The installer should be fast, simple and work on all platforms.

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2946: ----------------------------------------- Summary: The installer should be fast, simple and work on all platforms. Key: JBDS-2946 URL: https://issues.jboss.org/browse/JBDS-2946 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen -- 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-16525) API for retrieving the Cordova.js for a platform

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16525?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-16525. ---------------------------------- Resolution: Done > API for retrieving the Cordova.js for a platform > ------------------------------------------------ > > Key: JBIDE-16525 > URL: https://issues.jboss.org/browse/JBIDE-16525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Cordova.js file is special interest for several reasont and the Engines should have a way of retrieving them directly. HybridMobileLibraryResolver is probably a good candidate for this API. -- 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-16525) API for retrieving the Cordova.js for a platform

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16525?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16525: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes > API for retrieving the Cordova.js for a platform > ------------------------------------------------ > > Key: JBIDE-16525 > URL: https://issues.jboss.org/browse/JBIDE-16525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Cordova.js file is special interest for several reasont and the Engines should have a way of retrieving them directly. HybridMobileLibraryResolver is probably a good candidate for this API. -- 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-16525) API for retrieving the Cordova.js for a platform

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16525?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16525: -------------------------------------- There is now a path constant that is honored by all the platforms. It is possible to retrieve the cordova js with a call like below. HybridMobileLibraryResolver.getTemplateFile(HybridMobileLibraryResolver.PATH_CORDOVA_JS); > API for retrieving the Cordova.js for a platform > ------------------------------------------------ > > Key: JBIDE-16525 > URL: https://issues.jboss.org/browse/JBIDE-16525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Cordova.js file is special interest for several reasont and the Engines should have a way of retrieving them directly. HybridMobileLibraryResolver is probably a good candidate for this API. -- 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-16525) API for retrieving the Cordova.js for a platform

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16525?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16525: --------------------------------- Component/s: aerogear-hybrid > API for retrieving the Cordova.js for a platform > ------------------------------------------------ > > Key: JBIDE-16525 > URL: https://issues.jboss.org/browse/JBIDE-16525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > > Cordova.js file is special interest for several reasont and the Engines should have a way of retrieving them directly. HybridMobileLibraryResolver is probably a good candidate for this API. -- 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-16525) API for retrieving the Cordova.js for a platform

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16525?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-16525: ------------------------------------ Assignee: Gorkem Ercan > API for retrieving the Cordova.js for a platform > ------------------------------------------------ > > Key: JBIDE-16525 > URL: https://issues.jboss.org/browse/JBIDE-16525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Cordova.js file is special interest for several reasont and the Engines should have a way of retrieving them directly. HybridMobileLibraryResolver is probably a good candidate for this API. -- 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-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16651?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-16651: ----------------------------------- Assignee: Denis Golovin (was: Fred Bricon) Hey Denis, could you please review the PR for central? > Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16651 > URL: https://issues.jboss.org/browse/JBIDE-16651 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, project-examples > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Denis Golovin > Fix For: 4.1.2.CR1 > > > In JBoss Central, when an Enterprise runtime is selected for any given Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml > Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype. > Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes that do not add the RH repo to the gen'd pom.xml -- 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-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16651?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16651: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/217, https://github.com/jboss-jdf/jdf-stack/pull/36 (was: https://github.com/jbosstools/jbosstools-central/pull/217) > Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16651 > URL: https://issues.jboss.org/browse/JBIDE-16651 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, project-examples > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.2.CR1 > > > In JBoss Central, when an Enterprise runtime is selected for any given Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml > Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype. > Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes that do not add the RH repo to the gen'd pom.xml -- 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