May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2565) JBDS70_1215: [Commit] (?) (P1) Workflow changes - Auto Push

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2565?page=com.atlassian.jira.plugin.... ] Andre Dietisheim resolved JBDS-2565. ------------------------------------ Resolution: Done This was implemeted in JBIDE-13075 and will get available in JBT 4.1.0.Beta1 aka JBDS 7.0.0.Beta1 > JBDS70_1215: [Commit] (?) (P1) Workflow changes - Auto Push > ----------------------------------------------------------- > > Key: JBDS-2565 > URL: https://issues.jboss.org/browse/JBDS-2565 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 7.0.0.Beta1 > > > Ask for push at wizard ends > "Push" dialog needs to do diff with git remote > Work in background: https://issues.jboss.org/browse/JBIDE-13075 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Explore better ways for team import/sharing of projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-13703 at 5/6/13 2:57 AM: ------------------------------------------------------------- This is a non-trivial subject I don't think we can cover before 4.1.0.GA. In the mean time, in order to get a better workflow, I suggest you install the appropriate m2eclipse-(your scm) connector. Maven connectors for Subclipse, Subversive, EGit can be found in Window > Preferences > Maven > Discovery > Open Catalog The CVS connector's been dropped from the Maven Discovery Catalog for some reason (most likely, Sonatype doesn't maintain it anymore). I haven't tested it, but you can install it from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-cvs/0.13.0/N/0.13... Once the appropriate connector is installed, you can do New > Project > Checkout Maven Projects from SCM. See http://books.sonatype.com/m2eclipse-book/reference/creating.html#creating... for more information. was (Author: fbricon): This is a non-trivial subject I don't think we can cover before 4.1.0.GA. In the mean time, in order to get a better workflow, I suggest you install the appropriate m2eclipse-(your scm) connector. Maven connectors for Subclipse, Subversive, EGit can be found in Window > Preferences > Maven > Discovery > Open Catalog The CVS connector's been dropped from the Maven Discovery Catalog for some reason (most likely, Sonatype doesn't maintain it anymore). I haven't tested the it, but you can install it from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-cvs/0.13.0/N/0.13... Once the appropriate connector is installed, you can do New > Project > Checkout Maven Projects from SCM. See http://books.sonatype.com/m2eclipse-book/reference/creating.html#creating... for more information. > Explore better ways for team import/sharing of projects > ------------------------------------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, common/jst/core > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 4.1.x > > Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Explore better ways for team import/sharing of projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13703: -------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Beta1) This is a non-trivial subject I don't think we can cover before 4.1.0.GA. In the mean time, in order to get a better workflow, I suggest you install the appropriate m2eclipse-(your scm) connector. Maven connectors for Subclipse, Subversive, EGit can be found in Window > Preferences > Maven > Discovery > Open Catalog The CVS connector's been dropped from the Maven Discovery Catalog for some reason (most likely, Sonatype doesn't maintain it anymore). I haven't tested the it, but you can install it from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-cvs/0.13.0/N/0.13... Once the appropriate connector is installed, you can do New > Project > Checkout Maven Projects from SCM. See http://books.sonatype.com/m2eclipse-book/reference/creating.html#creating... for more information. > Explore better ways for team import/sharing of projects > ------------------------------------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, common/jst/core > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 4.1.x > > Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14376) JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing

by Sebastien Blanc (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14376?page=com.atlassian.jira.plugi... ] Sebastien Blanc commented on JBIDE-14376: ----------------------------------------- On the Emulator screen ? Yes I got a class not found message . > JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing > ---------------------------------------------------------------------------------- > > Key: JBIDE-14376 > URL: https://issues.jboss.org/browse/JBIDE-14376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Environment: Fedora 17 > Reporter: Sebastien Blanc > Assignee: Gorkem Ercan > > JBoss Aerogear Tools succeed to start Android Emulator but Cordova app is failing. See logs : > https://gist.github.com/sebastienblanc/5501833 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14351) Make sure ECFTransport is from o.j.tools.common.core, not o.j.t.runtime.core

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14351?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-14351. --------------------------------- Resolution: Done These 2 classes were impacted in central : * central/plugins/org.jboss.tools.central/src/org/jboss/tools/central/jobs/AbstractRefreshJob.java * examples/plugins/org.jboss.tools.project.examples/src/org/jboss/tools/project/examples/model/ProjectExampleUtil.java Fixed in master > Make sure ECFTransport is from o.j.tools.common.core, not o.j.t.runtime.core > ---------------------------------------------------------------------------- > > Key: JBIDE-14351 > URL: https://issues.jboss.org/browse/JBIDE-14351 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > The ECFTransport in o.j.t.runtime.core is deprecated. The new version is in o.j.t.common.core. Convert all your uses to use the new one, not the old one. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14088) Generate TP source feature site + composite site merging matching TP with TP sources

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14088?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14088: ------------------------------- Attachment: JBIDE14088.sources.list.txt After about 10 attempts over various days, this finally completed: {code} mvn install -Dmirror-target-to-repo.includeSources=true {code} Resulting pile of sources found in ~/jbosstools-targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo folder: [^JBIDE14088.sources.list.txt] > Generate TP source feature site + composite site merging matching TP with TP sources > ------------------------------------------------------------------------------------ > > Key: JBIDE-14088 > URL: https://issues.jboss.org/browse/JBIDE-14088 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > Attachments: JBIDE14088.sources.list.txt > > > Every time we produce a target platform update site zip on download.jboss.org we should also produce an update site containing only sources. > Then the composite site http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... could include: > * REPO/ > * SRC-REPO/ *NEW* > * compositeArtifacts.xml, compositeContent.xml --> points to both REPO/ and SRC-REPO/ *NEW* > * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip > * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip.MD5 > * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip *NEW* > * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip.MD5 *NEW* -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14385) Server Adapter ignores deploy-name of EARs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14385?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14385: ------------------------------------- war projects are also affected > Server Adapter ignores deploy-name of EARs > ------------------------------------------ > > Key: JBIDE-14385 > URL: https://issues.jboss.org/browse/JBIDE-14385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Alpha2 > Environment: WTP 3.5.0 > Reporter: Fred Bricon > Assignee: Rob Stryker > Attachments: ear-deploy-name-ignored.png, JBIDE-14385-ear.zip > > > After https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 has been fixed, I expected the deploy-name of EAR projects to be honored during deployment. It's not the case. > !ear-deploy-name-ignored.png! -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14385) Server Adapter ignores deploy-name of component projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14385?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14385: -------------------------------- Summary: Server Adapter ignores deploy-name of component projects (was: Server Adapter ignores deploy-name of EARs) > Server Adapter ignores deploy-name of component projects > -------------------------------------------------------- > > Key: JBIDE-14385 > URL: https://issues.jboss.org/browse/JBIDE-14385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Alpha2 > Environment: WTP 3.5.0 > Reporter: Fred Bricon > Assignee: Rob Stryker > Attachments: ear-deploy-name-ignored.png, JBIDE-14385-ear.zip > > > After https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 has been fixed, I expected the deploy-name of EAR projects to be honored during deployment. It's not the case. > !ear-deploy-name-ignored.png! -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14385) Server Adapter ignores deploy-name of EARs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14385?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14385: -------------------------------- Attachment: JBIDE-14385-ear.zip Attached is an ear project. It can be imported either as a standard eclipse project (maven won't be activated, even if m2e is installed) or a maven project. > Server Adapter ignores deploy-name of EARs > ------------------------------------------ > > Key: JBIDE-14385 > URL: https://issues.jboss.org/browse/JBIDE-14385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Alpha2 > Environment: WTP 3.5.0 > Reporter: Fred Bricon > Attachments: ear-deploy-name-ignored.png, JBIDE-14385-ear.zip > > > After https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 has been fixed, I expected the deploy-name of EAR projects to be honored during deployment. It's not the case. > !ear-deploy-name-ignored.png! -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14385) Server Adapter ignores deploy-name of EARs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14385?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14385: -------------------------------- Assignee: Rob Stryker > Server Adapter ignores deploy-name of EARs > ------------------------------------------ > > Key: JBIDE-14385 > URL: https://issues.jboss.org/browse/JBIDE-14385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Alpha2 > Environment: WTP 3.5.0 > Reporter: Fred Bricon > Assignee: Rob Stryker > Attachments: ear-deploy-name-ignored.png, JBIDE-14385-ear.zip > > > After https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 has been fixed, I expected the deploy-name of EAR projects to be honored during deployment. It's not the case. > !ear-deploy-name-ignored.png! -- 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, 11 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 May 2013