January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13297) Prevent from associating xml files to Android xml editor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13297?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13297: --------------------------------------- Why not to just hack it somewhere in IStartup implementation. Good candidate is ModelPluginStartup. Lets check if Webtools Structured XML editor is not default and set it default at first startup. > Prevent from associating xml files to Android xml editor > -------------------------------------------------------- > > Key: JBIDE-13297 > URL: https://issues.jboss.org/browse/JBIDE-13297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.0.0.Final > Reporter: Stefan Bunciak > Assignee: Viacheslav Kabanovich > Fix For: 4.1.2.CR1, 4.2.0.Alpha1 > > > After installing the Android Development Tools into JBDS/JBT all xml files gets associated to Android Common Xml Editor, even pom.xml files which we used to open with the Maven POM Editor. This issue was discussed with Burr Sutter on Face2Face that it should be fixed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16287) Missing dependencies warning doesn't disappear once settings.xml is fixed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16287?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16287: --------------------------------------- (+) for PR > Missing dependencies warning doesn't disappear once settings.xml is fixed > ------------------------------------------------------------------------- > > Key: JBIDE-16287 > URL: https://issues.jboss.org/browse/JBIDE-16287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Final > Environment: JBDS 7.1.0.GA B592 > Reporter: Martin Malina > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > Prerequisite : > * don't reference redhat repositories in your settings.xml > * have an EAP runtime handy > When creating the Java EE Web Project from Central, a warning show up about missing dependencies and a link to add the required repository > Once the repository is added to your settings.xml, the warning should disappear from the wizard. It doesn't. If you close the wizard and reopen it, the warning won't be displayed. > The problem is caused by the warning composite not being refreshed in the UI thread : https://github.com/jbosstools/jbosstools-central/blob/284a6e5762fd1b3d800... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16376) Disabled "fetch-zips" on aggregate

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16376?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16376: ---------------------------------------- Suggested PR: https://github.com/jbosstools/jbosstools-build-sites/pull/130 > Disabled "fetch-zips" on aggregate > ---------------------------------- > > Key: JBIDE-16376 > URL: https://issues.jboss.org/browse/JBIDE-16376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > As a consequence of changes for JBIDE-16309, the Maven mojo which fetches zip from aggregate files doesn't work any more. > So I disabled it (added fetch-zips-for-aggregate.skip=true ). We should decide whether to keep this or not. It seems to me that so far, the individual zips have not been used often, so we may be able to get rid of it. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16413) [iOS] Incorrect value for XCode Bundle ID

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16413?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16413: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Gorkem Ercan > [iOS] Incorrect value for XCode Bundle ID > ----------------------------------------- > > Key: JBIDE-16413 > URL: https://issues.jboss.org/browse/JBIDE-16413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Currently, project name is used for bundle ID however, the ID from the config.xml become Xcode's bundle ID? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16413) [iOS] Incorrect value for XCode Bundle ID

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16413?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16413: -------------------------------------- fix dropped to master > [iOS] Incorrect value for XCode Bundle ID > ----------------------------------------- > > Key: JBIDE-16413 > URL: https://issues.jboss.org/browse/JBIDE-16413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Currently, project name is used for bundle ID however, the ID from the config.xml become Xcode's bundle ID? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16413) [iOS] Incorrect value for XCode Bundle ID

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-16413: ------------------------------------ Summary: [iOS] Incorrect value for XCode Bundle ID Key: JBIDE-16413 URL: https://issues.jboss.org/browse/JBIDE-16413 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.1.1.Final Reporter: Gorkem Ercan Currently, project name is used for bundle ID however, the ID from the config.xml become Xcode's bundle ID? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2857) Add OS X 10.9 Mavericks to the support matrix

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2857: ---------------------------------- Updated: https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... > Add OS X 10.9 Mavericks to the support matrix > --------------------------------------------- > > Key: JBDS-2857 > URL: https://issues.jboss.org/browse/JBDS-2857 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.1.0.CR1 > Reporter: Martin Malina > Assignee: Len DiMaggio > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > I know this comes very late, so you may want to just push this to 8.0.0 immediately. > However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it. > I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13297) Prevent from associating xml files to Android xml editor

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13297?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-13297: ----------------------------------------------- In discussion, (comment #14) they say that editor will not reformat files outside of Android projects. However, the editor itself is declared as default for all xml files: {code} <editor class="com.android.ide.eclipse.adt.internal.editors.common.CommonXmlEditor" contributorClass="com.android.ide.eclipse.adt.internal.editors.common.CommonActionContributor" default="true" extensions="xml" icon="icons/android_file.png" id="com.android.ide.eclipse.editors.CommonXmlEditor" matchingStrategy="com.android.ide.eclipse.adt.internal.editors.common.CommonMatchingStrategy" name="Android Common XML Editor"> </editor> {code} Proposing possible solutions, I meant them to be suggested to ADT, but I stated that both proposals have drawbacks that may prevent ADT team from accepting them. The first suggestion is most consistent, but it would require from ADT a framework change to bind a namespace to each ADT relevant xml. As for a patch, we would be quite satisfied with just removing default="true". In this case, user would have once change in File Associations the default xml editor from WTP's to ADT's one. > Prevent from associating xml files to Android xml editor > -------------------------------------------------------- > > Key: JBIDE-13297 > URL: https://issues.jboss.org/browse/JBIDE-13297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.0.0.Final > Reporter: Stefan Bunciak > Assignee: Viacheslav Kabanovich > Fix For: 4.1.2.CR1, 4.2.0.Alpha1 > > > After installing the Android Development Tools into JBDS/JBT all xml files gets associated to Android Common Xml Editor, even pom.xml files which we used to open with the Maven POM Editor. This issue was discussed with Burr Sutter on Face2Face that it should be fixed. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2885) Add m2eclipse-mavenarchiver 0.16.0 to the JBDS 7.1.1/8 installers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2885?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2885: ---------------------------------- This feature is contained in ./features/com.jboss.devstudio.core.feature/feature.xml and the update site ./site/category.xml for both 4.1.x and master branches, so upon updating the JBDS target platform used for those builds, the included feature should simply move up from 0.15 to 0.16. Therefore there's nothing to do here except verify that once the TP is updated (JBIDE-16411), the JBDS 7.1.1 and 8.0.0 builds contains the updated version at the URLs below. http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71... http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_80... > Add m2eclipse-mavenarchiver 0.16.0 to the JBDS 7.1.1/8 installers > ----------------------------------------------------------------- > > Key: JBDS-2885 > URL: https://issues.jboss.org/browse/JBDS-2885 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to the JBDS 7.1.1 and JBDS 8 installers > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2885) Add m2eclipse-mavenarchiver 0.16.0 to the JBDS 7.1.1/8 installers

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2885?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2885: ----------------------------- Labels: jbds711 (was: ) > Add m2eclipse-mavenarchiver 0.16.0 to the JBDS 7.1.1/8 installers > ----------------------------------------------------------------- > > Key: JBDS-2885 > URL: https://issues.jboss.org/browse/JBDS-2885 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Labels: jbds711 > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to the JBDS 7.1.1 and JBDS 8 installers > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 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 January 2014