March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-13703: -------------------------------- Description: The average end-user would like to: check out (clone) a project from CVS, SVN or Git -- 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 favorite app server? -- how do I step if there are no break points? 6) Make a change to a file 7) Run tests 8) Check the change back in with comments was: The average end-user would like to: check out (clone) a project from CVS, SVN or Git -- 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 favorite app server? - how do I step if there are no break points? 6) Make a change to a file 7) Run tests 8) Check the change back in with comments > Team - Verify the workflow > -------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > > The average end-user would like to: > check out (clone) a project from CVS, SVN or Git > -- 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 favorite app server? > -- how do I step if there are no break points? > 6) Make a change to a file > 7) Run tests > 8) Check the change back in 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13684) BrowserSim: create iPad skin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13684?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13684: ---------------------------------- Labels: new_and_noteworthy (was: ) > BrowserSim: create iPad skin > ---------------------------- > > Key: JBIDE-13684 > URL: https://issues.jboss.org/browse/JBIDE-13684 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.0.x > > > Need to create iPad skin for BrowserSim -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13685) Create new navigation bar for iPad /iPad mini skins

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13685?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13685: ---------------------------------- Labels: new_and_noteworthy (was: ) > Create new navigation bar for iPad /iPad mini skins > --------------------------------------------------- > > Key: JBIDE-13685 > URL: https://issues.jboss.org/browse/JBIDE-13685 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.0.x > > > Need to create new navigation bar for iPad /iPad mini skins -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13671: --------------------------------------- [~nickboldt] but isn't this dangerous exactly because of what [~mickael_istria] said? You will skip the publish because there are no changes in the git repo. But the newly built plugins might differ because of a change in the parent pom. (At least until we stop using SNAPSHOT.) > parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13666) Error when renaming a domain with 1+ applications

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13666?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13666: ------------------------------------------------- Abhishek Gupta <abhgupta(a)redhat.com> made a comment on [bug 916330|https://bugzilla.redhat.com/show_bug.cgi?id=916330] I believe this was an issue with trying to read the parent domain pending_op from secondary within 500ms of the domain pending op being created. Perhaps not enough time for things to have been synced to secondary on a loaded mongo. This has now been fixed to read from the primary. > Error when renaming a domain with 1+ applications > ------------------------------------------------- > > Key: JBIDE-13666 > URL: https://issues.jboss.org/browse/JBIDE-13666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: rename-domain-error.png > > > This is a TRACKER/WATCHER issue that helps us tracking the fixing-progress on OpenShift (https://bugzilla.redhat.com/show_bug.cgi?id=916330). There's nothing we can do about this. > When trying to rename an existing domain to a domain name which already exists (within different openshift account): > {code} > Could not rename domain "sbunciak": [Operation failed with exit code "1".Reason given: " > Problem: > Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa. > Summary: > When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa. > Resolution: > Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."] > Could not request https://openshift.redhat.com/broker/rest/domains/pipistik: Operation failed with exit code "1".Reason given: " > Problem: > Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa. > Summary: > When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa. > Resolution: > Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples." > {code} > This message really doesn't describe the real problem - that I'm trying to use a domain name which is already used. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13666) Error when renaming a domain with 1+ applications

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13666?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13666: ------------------------------------------------- Abhishek Gupta <abhgupta(a)redhat.com> changed the Status of [bug 916330|https://bugzilla.redhat.com/show_bug.cgi?id=916330] from ASSIGNED to ON_QA > Error when renaming a domain with 1+ applications > ------------------------------------------------- > > Key: JBIDE-13666 > URL: https://issues.jboss.org/browse/JBIDE-13666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: rename-domain-error.png > > > This is a TRACKER/WATCHER issue that helps us tracking the fixing-progress on OpenShift (https://bugzilla.redhat.com/show_bug.cgi?id=916330). There's nothing we can do about this. > When trying to rename an existing domain to a domain name which already exists (within different openshift account): > {code} > Could not rename domain "sbunciak": [Operation failed with exit code "1".Reason given: " > Problem: > Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa. > Summary: > When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa. > Resolution: > Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."] > Could not request https://openshift.redhat.com/broker/rest/domains/pipistik: Operation failed with exit code "1".Reason given: " > Problem: > Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa. > Summary: > When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa. > Resolution: > Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples." > {code} > This message really doesn't describe the real problem - that I'm trying to use a domain name which is already used. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13699) Confusing web.xml declaration in generated CDI Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13699?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13699: ---------------------------------------- And we have it in our JIRA too. See JBIDE-7455 > Confusing web.xml declaration in generated CDI Web Project > ---------------------------------------------------------- > > Key: JBIDE-13699 > URL: https://issues.jboss.org/browse/JBIDE-13699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Priority: Minor > Fix For: LATER > > > Newly generated CDI Web project contains following web.xml declaration: > {noformat} > <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" > version="3.0"> > {noformat} > I think we would like to use 3.0 declaration and not any mixture. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13699) Confusing web.xml declaration in generated CDI Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13699?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-13699. ------------------------------------ Fix Version/s: 4.1.0.Alpha2 (was: LATER) Resolution: Duplicate Issue > Confusing web.xml declaration in generated CDI Web Project > ---------------------------------------------------------- > > Key: JBIDE-13699 > URL: https://issues.jboss.org/browse/JBIDE-13699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Newly generated CDI Web project contains following web.xml declaration: > {noformat} > <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" > version="3.0"> > {noformat} > I think we would like to use 3.0 declaration and not any mixture. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13699) Confusing web.xml declaration in generated CDI Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13699: ----------------------------------- Fix Version/s: LATER > Confusing web.xml declaration in generated CDI Web Project > ---------------------------------------------------------- > > Key: JBIDE-13699 > URL: https://issues.jboss.org/browse/JBIDE-13699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Priority: Minor > Fix For: LATER > > > Newly generated CDI Web project contains following web.xml declaration: > {noformat} > <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" > version="3.0"> > {noformat} > I think we would like to use 3.0 declaration and not any mixture. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13201) BYOE - Marketplace Installation on Mac - fails to start JBoss EAP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13201?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13201: ---------------------------------- Release Notes Docs Status: Not Required > BYOE - Marketplace Installation on Mac - fails to start JBoss EAP > ----------------------------------------------------------------- > > Key: JBIDE-13201 > URL: https://issues.jboss.org/browse/JBIDE-13201 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Environment: Mac OSX Lion (10.7) > Eclipse Java EE IDE for Web Developers for Mac OS X 64bit > * Version: Juno Service Release 1 > * Build id: 20121004-1855 > * Oracle Java 1.7.0_04 > EAP 6.0.0 > * Oracle Java 1.7.0_04 > Reporter: Burr Sutter > Assignee: Denis Golovin > Labels: respin-a > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: Configuration.txt, EAP6_FirstPage.png, EAP_Stack.txt, JBDS_Stack.txt, jbosstools-diagnostics-20121129152254.zip, Server_Starting.png > > > The IDE does not recognize that JBoss EAP 6.0.0 is started - it eventually times 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

13 years, 1 month

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 March 2013