August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-149) update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-149?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-149: ------------------------------------------ Yes yes, this is the right build number. The previous one was for helios and earlier but somehow got copied to the juno update site. I built the juno artifacts before heilos, that's why the earlier timestamp. Besides that, the helios artifacts did not include the fix because, as I said earlier, I forgot there are two code branches: one for helios and one for juno. Long story short, http://download.eclipse.org/bpel/site/1.0.3 is for juno and beyond; http://download.eclipse.org/bpel/site-helios/1.0.3 is for helios and prior; both update sites have the fix for this JIRA. <whew!> > update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3 > --------------------------------------------------------------- > > Key: JBTIS-149 > URL: https://issues.jboss.org/browse/JBTIS-149 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > Fix For: 4.1.2 > > > New content: http://download.eclipse.org/bpel/site/1.0.3 - version 1.0.3.v20130816-0911-H221-CI > Reason: https://bugzilla.redhat.com/show_bug.cgi?id=996874 -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-149) update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-149?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-149: ---------------------------------- [~bbrodt] Are you sure you want an older version? Previously tested 1.0.3.v20130816-0911-H221-CI. Also, why does this respin lack a build number (B221), yet override the previous site with an older timestamped version? [~jsedlacek] Can you install BPEL 1.0.3.v20130816-0854-CI from http://download.eclipse.org/bpel/site/1.0.3/ on top of your existing install, and see if the problem is fixed? That way we can verify this is the correct solution before we respin the JBTIS TP, respin JBoss BPEL, publish it, then respin JBTIS. > update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3 > --------------------------------------------------------------- > > Key: JBTIS-149 > URL: https://issues.jboss.org/browse/JBTIS-149 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > Fix For: 4.1.2 > > > New content: http://download.eclipse.org/bpel/site/1.0.3 - version 1.0.3.v20130816-0911-H221-CI > Reason: https://bugzilla.redhat.com/show_bug.cgi?id=996874 -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15358) No code completion when navigating in jsp files of Spring examples

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15358?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-15358. ------------------------------------ Resolution: Rejected Resolving the issue. Max, please reopen it if you still have any questions ;) > No code completion when navigating in jsp files of Spring examples > ------------------------------------------------------------------ > > Key: JBIDE-15358 > URL: https://issues.jboss.org/browse/JBIDE-15358 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Final > Reporter: Jiri Peterka > Assignee: Alexey Kazakov > Fix For: 4.1.1.Final > > Attachments: jboss-wfk-2.3.0-spring-demo.zip > > > There is no code completion when editing standard.jsp spring example -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15377) A duplicate method JBossServerType.getUnderlyingTypeId(File) in the org.jboss.ide.eclipse.as.wtp.core plugin

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15377?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-15377: ---------------------------------- Component/s: server (was: Seam 2) > A duplicate method JBossServerType.getUnderlyingTypeId(File) in the org.jboss.ide.eclipse.as.wtp.core plugin > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15377 > URL: https://issues.jboss.org/browse/JBIDE-15377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > > See https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or... > The issue doesn't exist in the jboostools-4.1.x branch. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15377) A duplicate method JBossServerType.getUnderlyingTypeId(File) in the org.jboss.ide.eclipse.as.wtp.core plugin

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-15377: ------------------------------------- Summary: A duplicate method JBossServerType.getUnderlyingTypeId(File) in the org.jboss.ide.eclipse.as.wtp.core plugin Key: JBIDE-15377 URL: https://issues.jboss.org/browse/JBIDE-15377 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 4.2.0.Alpha1 Reporter: Snjezana Peco See https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or... The issue doesn't exist in the jboostools-4.1.x branch. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13851) Add source lookup classes to Java Search

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13851?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13851: --------------------------------------- I have replaced the exception log with an information log and rebased the PR. > Add source lookup classes to Java Search > ---------------------------------------- > > Key: JBIDE-13851 > URL: https://issues.jboss.org/browse/JBIDE-13851 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.2.x > > > This feature would be implemented in a similar way to adding PDE plugins to the Java Search. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14597) ng-app AngularJS

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14597?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-14597 at 8/27/13 12:30 PM: ------------------------------------------------------------------- The issue is created in BugZilla: [Bug 415980|https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980] - HTML5 attribute validator marks ng-app AngularJS attributes as undefined, as well as the [patch|https://bugs.eclipse.org/bugs/attachment.cgi?id=234815] is provided for the issue. was (Author: vrubezhny): The issue is created in BugZilla: [Bug 415980|https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980] - HTML5 attribute validator marks ng-app AngularJS attributes as undefined, as well as the [patch|https://bugs.eclipse.org/bugs/attachment.cgi?id=189943] is provided for the issue. > ng-app AngularJS > ---------------- > > Key: JBIDE-14597 > URL: https://issues.jboss.org/browse/JBIDE-14597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.2.x > > Attachments: 2013-05-23_0752.png, 2013-05-23_1548.png, html5_demo.fsh, Screen Shot 2013-05-23 at 3.51.53 PM.png > > > Warning: > Undefined attribute name (ng-app). > Undefined attribute name (ng-controller). > AngularJS is part of the new HTML5 Scaffolding feature in Forge 1.3 > forge install-plugin angularjs -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14597) ng-app AngularJS

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14597?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-14597: ----------------------------------------- The issue is created in BugZilla: [Bug 415980|https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980] - HTML5 attribute validator marks ng-app AngularJS attributes as undefined, as well as the [patch|https://bugs.eclipse.org/bugs/attachment.cgi?id=189943] is provided for the issue. > ng-app AngularJS > ---------------- > > Key: JBIDE-14597 > URL: https://issues.jboss.org/browse/JBIDE-14597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Burr Sutter > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.2.x > > Attachments: 2013-05-23_0752.png, 2013-05-23_1548.png, html5_demo.fsh, Screen Shot 2013-05-23 at 3.51.53 PM.png > > > Warning: > Undefined attribute name (ng-app). > Undefined attribute name (ng-controller). > AngularJS is part of the new HTML5 Scaffolding feature in Forge 1.3 > forge install-plugin angularjs -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15375) File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo

by Andy Goldstein (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15375?page=com.atlassian.jira.plugi... ] Andy Goldstein commented on JBIDE-15375: ---------------------------------------- I tested in the target environment using Kepler and JBoss Tools 4.1 and was able to create a vanilla jbossas-7 application and the hooks are executable for me. Once Eric gets his JIRA account issue resolved, hopefully he can provide exact steps to reproduce the error. > File permissions for OpenShift actions hooks are sometimes incorrect when cloning repo > -------------------------------------------------------------------------------------- > > Key: JBIDE-15375 > URL: https://issues.jboss.org/browse/JBIDE-15375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final > Environment: Windows, cygwin > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Attachments: resource-properties.png, set-x-permissions.png > > > (filing on behalf of another user who is having login issues) > When I clone a git repo (git@...:user/myapp.git) using the Eclipse plugins, the file permissions for my action_hooks are set as: > {code} > /cygdrive/c/Users/user/git/myapp/.openshift/action_hooks > $ ls -l > total 45 > -rwx------+ 1 Administrators Domain Users 265 Aug 22 14:38 build > -rwx------+ 1 Administrators Domain Users 264 Aug 22 14:38 deploy > -rwx------+ 1 Administrators Domain Users 186 Aug 22 14:38 post_deploy > -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_start_jbossas-7 > -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 post_stop_jbossas-7 > -rwx------+ 1 Administrators Domain Users 640 Aug 22 14:38 pre_build > -rwx------+ 1 Administrators Domain Users 272 Aug 22 14:38 pre_build_jbossas-7 > -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_start_jbossas-7 > -rwx------+ 1 Administrators Domain Users 645 Aug 22 14:38 pre_stop_jbossas-7 > {code} > When they are pushed to OpenShift, they can't be executed. > {code} > /var/lib/openshift/5216951d76c3b22b77000362/app-root/runtime/repo/.openshift/action_hooks/post_stop_jbossjsw-1.0: Permission denied > remote: Failed to stop jbossjsw-1.0 > To > ssh://5216951d76c3b22b77000362@ppon-tsujarit.qa02.shift.paypal.com/~/git/pp > on.git/ > ! [remote rejected] master -> master (pre-receive hook declined) > error: failed to push some refs to > {code} > On a different machine, when I clone using Eclipse, the file permission are set as expected: > {code} > -rwxr-xr-x 1 Administrators Domain Users 270 Aug 22 11:25 build > -rwxr-xr-x 1 Administrators Domain Users 271 Aug 22 11:25 deploy > -rwxr-xr-x 1 Administrators Domain Users 189 Aug 22 11:25 post_deploy > -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_start_jbossas-7 > -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 post_stop_jbossas-7 > -rwxr-xr-x 1 Administrators Domain Users 650 Aug 22 11:25 pre_build > -rwxr-xr-x 1 Administrators Domain Users 277 Aug 22 11:25 pre_build_jbossas-7 > -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_start_jbossas-7 > -rwxr-xr-x 1 Administrators Domain Users 659 Aug 22 11:25 pre_stop_jbossas-7 > {code} > Is it possible to set the file perms to +x on the action_hooks? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Rob Cernich commented on JBTIS-158: ----------------------------------- Yep. That is exactly what I was thinking: have a simple little project that zips up the two sites (jbds-is and jbds-is-tp), along with some composite*.xml files to facilitate using it as a p2 site. That zip can be used for pretty much everything and, if the paths are named correctly, portions can be expanded into their target folders on the server (e.g. unzip site.zip integration-stack/aggregate/<version>/*). As for the directory layout, I don't really have an opinion, other than the zip should mirror the hierarchies under "integration-stack" whatever those might be. > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013