February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16390) CordovaSim: need to implement multiple version support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16390?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-16390: -------------------------------- Attachment: multiple-version-support.png > CordovaSim: need to implement multiple version support > ------------------------------------------------------ > > Key: JBIDE-16390 > URL: https://issues.jboss.org/browse/JBIDE-16390 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta1 > > Attachments: multiple-version-support.png > > > Cordovasim should get the version info from HMT (hybrid mobile tools) and handle it in an appropriate way > "Cordova Versioning Challenge" meeting minutes: http://rhatlog:festisub2010@people.redhat.com/~manderse/irc.devel.redhat.... -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2913: -------------------------------------- CDW release: ? Status: New (was: New) CDW blocker: + Target Release: 7.1.1.GA I consider this a blocker for release if the issue is still present. JBDS 7.1 should not have broken EAP 6.x nor JBoss 7.x support Was supposed to have been fixed in https://issues.jboss.org/browse/JBIDE-14561 https://issues.jboss.org/browse/JBIDE-14380 > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0) -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2913: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.0) -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16665) Add Sapphire to TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16665: ---------------------------------------- Sapphire is part of the release train, and the luna repository does include the source bundles as well, so there is no need to mirror sapphire repository. > Add Sapphire to TP > ------------------ > > Key: JBIDE-16665 > URL: https://issues.jboss.org/browse/JBIDE-16665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, testing-tools > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > > Reason: Required by new feature described in JBIDE-15394 > License and owner: EPL, Eclipse > Original repository: http://download.eclipse.org/sapphire/0.7/repository > JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire > Source: Yes > Affected projects: arquillian > Required in devstudio: No > Type of dependency: > List of bundles added: > org.eclipse.sapphire.java > org.eclipse.sapphire.java.jdt > org.eclipse.sapphire.java.jdt.ui > org.eclipse.sapphire.modeling > org.eclipse.sapphire.modeling.xml > org.eclipse.sapphire.osgi > org.eclipse.sapphire.osgi.fragment > org.eclipse.sapphire.platform > org.eclipse.sapphire.ui > org.eclipse.sapphire.ui.swt.gef > org.eclipse.sapphire.ui.swt.xml.editor > org.eclipse.sapphire.workspace > org.eclipse.sapphire.workspace.ui > org.objectweb.asm -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16666) Remove org.jboss.tools.maven.profiles.feature from update sites / installer

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16666: ----------------------------------- Summary: Remove org.jboss.tools.maven.profiles.feature from update sites / installer Key: JBIDE-16666 URL: https://issues.jboss.org/browse/JBIDE-16666 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Reporter: Fred Bricon Fix For: 4.2.0.Beta1 org.jboss.tools.maven.profiles.feature should not be made available once m2e 1.5 M6 is out -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16666) Remove org.jboss.tools.maven.profiles.feature from update sites / installer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16666?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16666: ------------------------------------- JBIDE-16666 mwaahhahahah > Remove org.jboss.tools.maven.profiles.feature from update sites / installer > --------------------------------------------------------------------------- > > Key: JBIDE-16666 > URL: https://issues.jboss.org/browse/JBIDE-16666 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Fred Bricon > Fix For: 4.2.0.Beta1 > > > org.jboss.tools.maven.profiles.feature should not be made available once m2e 1.5 M6 is out -- 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

10 years, 9 months

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, https://github.com/jbosstools/jbosstools-central/pull/220 (was: https://github.com/jbosstools/jbosstools-central/pull/217, https://github.com/jboss-jdf/jdf-stack/pull/36) > 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

10 years, 9 months

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 commented on JBIDE-16651: ------------------------------------- PR fixing the issue https://github.com/jbosstools/jbosstools-central/pull/220 > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16661) Eclipse Console Logging for CordovaSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16661: ------------------------------------------------ It looks like getting this console requires LaunchConfiguration extension. Implementing all requires interfaces requires a lot of time. So I guess we should have everything done only for cordovaSim. At least for now. > Eclipse Console Logging for CordovaSim > -------------------------------------- > > Key: JBIDE-16661 > URL: https://issues.jboss.org/browse/JBIDE-16661 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Beta1 > > Attachments: Screenshot 2014-02-27 16.23.47.png > > > If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching. > My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser". -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16664) Mylyn related packages removed from Target Platform - can we get them back?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16664?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16664: ---------------------------------------- Does your test actually depend on a feature? If so, it this really necessary? What's missing with plain MANIFEST.MF dependencies? > Mylyn related packages removed from Target Platform - can we get them back? > --------------------------------------------------------------------------- > > Key: JBIDE-16664 > URL: https://issues.jboss.org/browse/JBIDE-16664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.2.0.Beta1 > > > I noticed that this test starting failing a few days ago: > https://github.com/ldimaggi/jbosstools-integration-tests/tree/master/test... > For exmaple: > http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/38... > With an error of: > [ERROR] Software being installed: org.eclipse.mylyn.context_feature.feature.group 3.11.0.20131105-2146 > [ERROR] Missing requirement: org.eclipse.mylyn.context_feature.feature.group 3.11.0.20131105-2146 requires 'org.eclipse.mylyn_feature.feature.group [3.11.0,3.12.0)' but it could not be found > And I found that here - the mylyn-related packages that the test needs were indeed removed - can we get them back? > https://github.com/jbosstools/jbosstools-target-platforms/pull/36/files > -  > - <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"> > - <repository location="http://download.jboss.org/jbosstools/updates/requirements/mylyn/3.11.0-I2..."/> > - <unit id="org.eclipse.mylyn.bugzilla_feature.feature.group" version="3.11.0.20131218-0113"/> > - <unit id="org.eclipse.mylyn.commons.feature.group" version="3.11.0.20131024-1846"/> > - <unit id="org.eclipse.mylyn.commons.compatibility.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.commons.core" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.commons.identity.feature.group" version="1.3.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.commons.net" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.commons.notifications.feature.group" version="1.3.0.20131105-2126"/> > - <unit id="org.eclipse.mylyn.commons.repositories.feature.group" version="1.3.0.20131127-1955"/> > - <unit id="org.eclipse.mylyn.commons.repositories.http.feature.group" version="1.3.0.20131129-1037"/> > - <unit id="org.eclipse.mylyn.commons.screenshots" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.commons.soap" version="3.11.0.20131219-1119"/> > - <unit id="org.eclipse.mylyn.commons.ui" version="3.11.0.20131024-1846"/> > - <unit id="org.eclipse.mylyn.commons.xmlrpc" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.context_feature.feature.group" version="3.11.0.20131105-2146"/> > - <unit id="org.eclipse.mylyn.cvs.feature.group" version="1.3.0.20131021-1910"/> > - <unit id="org.eclipse.mylyn.discovery.core" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.discovery.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.discovery.ui" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn_feature.feature.group" version="3.11.0.20131218-0113"/> > - <unit id="org.eclipse.mylyn.git.feature.group" version="1.3.0.20131021-1910"/> > - <unit id="org.eclipse.mylyn.ide_feature.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.java_feature.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.monitor.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.pde_feature.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.tasks.bugs" version="3.11.0.20131021-1910"/> > - <unit id="org.eclipse.mylyn.tasks.core" version="3.11.0.20131218-0113"/> > - <unit id="org.eclipse.mylyn.tasks.ide.feature.group" version="3.11.0.20131021-1910"/> > - <unit id="org.eclipse.mylyn.tasks.ui" version="3.11.0.20131218-0113"/> > - <unit id="org.eclipse.mylyn.team_feature.feature.group" version="3.11.0.20131021-1909"/> > - <unit id="org.eclipse.mylyn.versions.feature.group" version="1.3.0.20131021-1910"/> > - <unit id="org.eclipse.mylyn.wikitext_feature.feature.group" version="2.0.0.20131219-0024"/> > - </location> -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2014