October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2729) Add mobile web quickstarts for JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2729?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2729: ---------------------------------- [~pmuir] Which quickstarts are actually done, and where are they? Looking at https://github.com/pmuir?tab=activity doesn't really clarify things. :) > Add mobile web quickstarts for JBoss Central > -------------------------------------------- > > Key: JBDS-2729 > URL: https://issues.jboss.org/browse/JBDS-2729 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 7.1.0.GA > > > The mobile web quickstarts being proced on WFK2 side should be included in JBoss Central -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15783) CordovaSim: CordovaSim doesn't support android projects

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15783?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15783: ------------------------------------- Fix Version/s: 4.1.1.CR1 > CordovaSim: CordovaSim doesn't support android projects > ------------------------------------------------------- > > Key: JBIDE-15783 > URL: https://issues.jboss.org/browse/JBIDE-15783 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > > CordovaSim should support hybrid and android (hybrid project that was built for the android platform) projects. After cordova 3.1 migration CordovaSim fails to emulate android projects -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15783) CordovaSim: CordovaSim doesn't support android projects

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15783?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15783: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > CordovaSim: CordovaSim doesn't support android projects > ------------------------------------------------------- > > Key: JBIDE-15783 > URL: https://issues.jboss.org/browse/JBIDE-15783 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha1 > > > CordovaSim should support hybrid and android (hybrid project that was built for the android platform) projects. After cordova 3.1 migration CordovaSim fails to emulate android projects -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Len DiMaggio resolved JBDS-2767. -------------------------------- Resolution: Done > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Beta1 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2767: ----------------------------- Fix Version/s: 7.1.0.Alpha2 (was: 7.1.0.Beta1) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2767: ---------------------------------- Pushed + for QE_ACK, and [~ldimaggio] resolved it for verification. Pushed back to Alpha2. > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Alpha2 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2767: ----------------------------- CDW release: + (was: ?) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Beta1 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2767: ------------------------------- CDW qa_ack: + (was: ?) Status: New (was: New) > Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection > --------------------------------------------------------------------- > > Key: JBDS-2767 > URL: https://issues.jboss.org/browse/JBDS-2767 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: servers, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 7.1.0.Beta1 > > Attachments: 15498.png > > > Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0. > Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances. > Original from Nick: > Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7. > Comparing the update sites for JBT 4.1.x and JBDS 7.1.x: > !15498.png! > Was it intentionally excluded from the update site, or forgotten? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15685) For JBIDE 4.1.1.Beta1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15685?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15685. ------------------------------ Assignee: Nick Boldt Resolution: Done > For JBIDE 4.1.1.Beta1: Code Freeze + Branch > ------------------------------------------- > > Key: JBIDE-15685 > URL: https://issues.jboss.org/browse/JBIDE-15685 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Beta1 > > > For JBIDE 4.1.1.Beta1: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Beta1 > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.1.1.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Beta1; > {code} > mvn clean verify -Dtpc.version=4.31.0.Final # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.31.1.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Beta1x branch; > {code} > git checkout jbosstools-4.1.x > git pull origin jbosstools-4.1.x > git checkout -b jbosstools-4.1.1.Beta1x > git push origin jbosstools-4.1.1.Beta1x > {code} > 5. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-2804 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15827) Failed to remove JAX-RS Metamodel when closing a project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15827: ------------------------------------- Summary: Failed to remove JAX-RS Metamodel when closing a project Key: JBIDE-15827 URL: https://issues.jboss.org/browse/JBIDE-15827 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.1.1.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.Alpha1 When closing a JAX-RS project, the following error is reported in the log: {code} org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications. at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116) at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2283) at org.eclipse.core.internal.resources.Resource.deleteMarkers(Resource.java:844) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.remove(JaxrsMetamodel.java:332) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedListener.resourceChanged(ResourceChangedListener.java:62) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:249) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:391) at org.eclipse.core.internal.resources.Project.close(Project.java:199) at org.eclipse.ui.actions.CloseResourceAction.invokeOperation(CloseResourceAction.java:129) at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:164) at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:485) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) 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, 5 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 October 2013