June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-14544: -------------------------------- Attachment: runasandroidemulatorwin7_32.png > Cannot run Cordova project on Android Emulator/Device > ----------------------------------------------------- > > Key: JBIDE-14544 > URL: https://issues.jboss.org/browse/JBIDE-14544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Fedora 17 32bit > Android 4.1.2 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Priority: Blocker > Labels: respin-a > Fix For: 4.1.0.Beta2 > > Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > {code} > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:883) > at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99) > at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14544: ------------------------------------- On MS Widnows 7 32 bit this error dialog is displayed. !runasandroidemulatorwin7_32.png! Tested with latest Aerogear plugin version installed from staging site mentioned in Gorkem comment. No error messages in error log. > Cannot run Cordova project on Android Emulator/Device > ----------------------------------------------------- > > Key: JBIDE-14544 > URL: https://issues.jboss.org/browse/JBIDE-14544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.0.Beta1 > Environment: Fedora 17 32bit > Android 4.1.2 > Reporter: Stefan Bunciak > Assignee: Gorkem Ercan > Priority: Blocker > Labels: respin-a > Fix For: 4.1.0.Beta2 > > Attachments: Screen Shot 2013-06-03 at 10.50.52 AM.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > {code} > java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.createNewFile(File.java:883) > at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99) > at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68) > at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12121) The openshift profile is added to newly created maven projects, regardless of their packaging type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12121: ------------------------------------- Fix Version/s: 4.1.0.Beta2 (was: 4.1.x) > The openshift profile is added to newly created maven projects, regardless of their packaging type > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-12121 > URL: https://issues.jboss.org/browse/JBIDE-12121 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > Attachments: new-openarchetype-project-2.png, new-openarchetype-project.png > > > I created a project using the org.openarchetypes:multi-javaee6-archetype:0.0.1-SNAPSHOT from http://open-archetypes.github.com/maven-repo/snapshots/archetype-catalog.xml (Maven > Archetypes > Add Remote Catalog) > This creates a multi module project, containing a parent pom, an ear, war, ejb and utility projects. This openshift profile was added to the pom project : > {code:xml} > <profiles> > <profile> >  >  >  >  > <id>openshift</id> > <build> > <finalName>hello</finalName> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.1.1</version> > <configuration> > <outputDirectory>deployments</outputDirectory> > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </build> > </profile> > {code} > Actually, it should : > - check the packaging type of *all* the generated projects > - if some EARs are found, then add the following to the parent pom (pay attention to the <pluginManagement> section) : > {code:xml} > <profile> > <id>openshift</id> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-ear-plugin</artifactId> > <version>2.7</version> > <configuration> > <outputDirectory>deployments</outputDirectory> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > </profile> > {code} > - if there are no EARs but some WARs are found (count them), then add the following to the parent pom (pay attention to the <pluginManagement> section) : > {code:xml} > <profiles> > <profile> > <id>openshift</id> > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.2</version> > <configuration> > <outputDirectory>deployments</outputDirectory> >  > <warName>ROOT</warName> > </configuration> > </plugin> > </plugins> > </pluginManagement> > </build> > </profile> > {code} > The finalName is irrelevant to openshift, only the warName counts. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14514) openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14514?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14514: ------------------------------------------ postponed to 4.1.x since this is manitenance of the openshift-java-client codebase and no urgent change. Freezing 4.1.0.Beta2 gets closer and we need to sort out the most urgent tasks. > openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046 > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-14514 > URL: https://issues.jboss.org/browse/JBIDE-14514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > In the latest implementations the OpenShift broker returns the embedded cartridges within the application as follows: > {code} > "embedded":{ > "mongodb-2.2":{ > "connection_url":"mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/", > "username":"admin", > "password":"NNxXMT1z8dVj", > "database_name":"springeap6", > "info":"Connection URL: mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/" > } > }, > {code} > Prior code was only returning the *info* property where we had to exctract the url via regex. The new broker is returning the *connection_url* which does not require any regex-treatment any more > The code in openshift-java-client marks this workaround with a TODO: > {code} > protected EmbeddedCartridgeResource(final String name, final String displayName, final String description, final CartridgeType type, String info, final Map<String, Link> links, > final Map<String, Message> messages, final ApplicationResource application) { > super(application.getService(), links, messages); > this.name = name; > this.displayName = displayName; > this.description = description; > this.type = type; > // TODO: fix this workaround once > // https://bugzilla.redhat.com/show_bug.cgi?id=812046 is fixed > this.url = extractUrl(info, messages); > this.application = application; > } > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14514) openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14514?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14514: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Beta2) > openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046 > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-14514 > URL: https://issues.jboss.org/browse/JBIDE-14514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > > In the latest implementations the OpenShift broker returns the embedded cartridges within the application as follows: > {code} > "embedded":{ > "mongodb-2.2":{ > "connection_url":"mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/", > "username":"admin", > "password":"NNxXMT1z8dVj", > "database_name":"springeap6", > "info":"Connection URL: mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/" > } > }, > {code} > Prior code was only returning the *info* property where we had to exctract the url via regex. The new broker is returning the *connection_url* which does not require any regex-treatment any more > The code in openshift-java-client marks this workaround with a TODO: > {code} > protected EmbeddedCartridgeResource(final String name, final String displayName, final String description, final CartridgeType type, String info, final Map<String, Link> links, > final Map<String, Message> messages, final ApplicationResource application) { > super(application.getService(), links, messages); > this.name = name; > this.displayName = displayName; > this.description = description; > this.type = type; > // TODO: fix this workaround once > // https://bugzilla.redhat.com/show_bug.cgi?id=812046 is fixed > this.url = extractUrl(info, messages); > this.application = application; > } > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14737) Change link label on N&N page from BrowserSim to BrowserSim/CordovaSim

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14737?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-14737: -------------------------------- Priority: Minor (was: Major) > Change link label on N&N page from BrowserSim to BrowserSim/CordovaSim > ---------------------------------------------------------------------- > > Key: JBIDE-14737 > URL: https://issues.jboss.org/browse/JBIDE-14737 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Vlado Pakan > Priority: Minor > > From JBT 4.1.0 on label for link to BrowserSim/CordovaSim N&N should be changed from "BrowserSim" to "BrowserSim/CordovaSim" on N&N main page http://docs.jboss.org/tools/whatsnew/ to correspond to title of linked page http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.Bet... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14737) Change link label on N&N page from BrowserSim to BrowserSim/CordovaSim

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-14737: ----------------------------------- Summary: Change link label on N&N page from BrowserSim to BrowserSim/CordovaSim Key: JBIDE-14737 URL: https://issues.jboss.org/browse/JBIDE-14737 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Affects Versions: 4.1.0.Beta1 Reporter: Vlado Pakan >From JBT 4.1.0 on label for link to BrowserSim/CordovaSim N&N should be changed from "BrowserSim" to "BrowserSim/CordovaSim" on N&N main page http://docs.jboss.org/tools/whatsnew/ to correspond to title of linked page http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.Bet... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14737) Change link label on N&N page from BrowserSim to BrowserSim/CordovaSim

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14737?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-14737: -------------------------------- Issue Type: Task (was: Bug) > Change link label on N&N page from BrowserSim to BrowserSim/CordovaSim > ---------------------------------------------------------------------- > > Key: JBIDE-14737 > URL: https://issues.jboss.org/browse/JBIDE-14737 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Vlado Pakan > > From JBT 4.1.0 on label for link to BrowserSim/CordovaSim N&N should be changed from "BrowserSim" to "BrowserSim/CordovaSim" on N&N main page http://docs.jboss.org/tools/whatsnew/ to correspond to title of linked page http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.Bet... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14720) No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14720?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14720: --------------------------------------------- This looks like a compatibility issue somewhere in m2e. Caused by: java.lang.RuntimeException: Property not located:JpaFacetInstallDataModelProperties.CREATE_ORM_XML at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.checkValidPropertyName(DataModelImpl.java:100) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.getOwningDataModel(DataModelImpl.java:105) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:171) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.getDataModel(JpaProjectConfigurator.java:176) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:131) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:98) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:472) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:465) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:245) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:102) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProjects0(ProjectConfigurationManager.java:780) > No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1 > ------------------------------------------------------------------------------- > > Key: JBIDE-14720 > URL: https://issues.jboss.org/browse/JBIDE-14720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha2, 4.1.0.Beta1 > Reporter: Juergen Zimmermann > Assignee: Nick Boldt > Attachments: jbosstools-diagnostics-20130601182344.zip, screenshot-after-wizard-has-completed.jpg > > > 1) I'm using JBoss Tools version 2013-05-29_02-05-21-B272 which I got from http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core... and also the Java EE package for Kepler RC2. > 2) I created a server config for JBossAS 7.1.0 (btw, same happens for EAP 6.1). > 3) I created a new "Java EE Web Project". > I'll attach a screenshot after the project wizard has completed, and also a "Help > Report Problem". -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14720) No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14720?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14720: ---------------------------------------- Fix Version/s: 4.1.0.Beta2 > No Project Facets are set when creating a "Java EE Web Project" for JBossAS 7.1 > ------------------------------------------------------------------------------- > > Key: JBIDE-14720 > URL: https://issues.jboss.org/browse/JBIDE-14720 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha2, 4.1.0.Beta1 > Reporter: Juergen Zimmermann > Assignee: Fred Bricon > Fix For: 4.1.0.Beta2 > > Attachments: jbosstools-diagnostics-20130601182344.zip, screenshot-after-wizard-has-completed.jpg > > > 1) I'm using JBoss Tools version 2013-05-29_02-05-21-B272 which I got from http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core... and also the Java EE package for Kepler RC2. > 2) I created a server config for JBossAS 7.1.0 (btw, same happens for EAP 6.1). > 3) I created a new "Java EE Web Project". > I'll attach a screenshot after the project wizard has completed, and also a "Help > Report Problem". -- 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, 10 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 June 2013