Closed (won't fix)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 Apr 2013 at 19:32 UTC
Updated:
13 Sep 2013 at 22:25 UTC
Jump to comment: Most recent file
Comments
Comment #1
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://ventral.org/pareview/httpgitdrupalorgsandboxccamporeale1979952git
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #2
ccamporeale commentedCode cleanup and documentation fixes have been applied.
Comment #3
dclavain commentedYou need to add a README.txt with the description of the module file.
Every contributed module should provide a README.txt in the package. This file should contain a basic overview of what the module does and how someone may use it. The contents of the file may be a repeat of the synopsis on the project page.
Comment #4
ccamporeale commentedREADME.txt has been added.
Comment #5
ccamporeale commentedComment #6
dclavain commentedhi @ccamporeale
Your branch by default should be the 7.x-1.0-beta1 and you should delete the master branch.
Also you must correct the following notices found in the README.txt file
FILE: /var/www/drupal-7-pareview/pareview_temp/README.txt
--------------------------------------------------------------------------------
FOUND 0 ERROR(S) AND 3 WARNING(S) AFFECTING 3 LINE(S)
--------------------------------------------------------------------------------
1 | WARNING | Line exceeds 80 characters; contains 96 characters
3 | WARNING | Line exceeds 80 characters; contains 217 characters
5 | WARNING | Line exceeds 80 characters; contains 115 characters
--------------------------------------------------------------------------------
It uses http://ventral.org to solve these small bugs
Comment #7
ccamporeale commentedHi @dclavain,
Thanks for taking the time to review this project. I've cleaned up the last of the code formatting issues, and fixed the namespaces, branch names, and tags accordingly.
Comment #8
samvel commentedHi, please change link to git repo:
git clone http://git.drupal.org/sandbox/ccamporeale/1979952.git jasperreports_server_ssomy manual review:
_SESSIONand now it causes noticesMay be you move these functions into a separate file?
It's only .module file. Please check for such errors in other files yourself.
Good luck.
Comment #9
samvel commentedComment #10
ccamporeale commented@asik, thanks for reviewing this project - the changes have been made.
Comment #11
webevt commentedHi
Please take a look at the tips for a great project page.
Project automated reviews tools did not find any issues.
Concerning manual review:
Regards
Comment #12
webevt commentedComment #13
MarianoL commented@WebEvt:
Good call on the $jrs_rest_url, I'll add a function for that.
The idea of using $base_root in this case instead of url() is that I only need the host name where drupal and Jasper are running. This function is to craft the proper URI for doing the REST calls to the Jasper API.
Comment #14
MarianoL commentedChris,
Attached is a patch that refactors the $jrs_rest_url and uses a function to generate that. If you want to give me access to you repo I can just push it there. I'm keeping this as "needs work" since we need to address the permission hook
- MarianoL
Comment #15
ccamporeale commentedHi Mariano,
Thanks for the patch. I've granted VCS access to your account so you can push at will.
I'm not sure if I'll have the bandwidth to look at this in the near future, but let me know if there's anything specific I can help with.
Thanks!
Chris
Comment #16
PA robot commentedClosing due to lack of activity. Feel free to reopen if you are still working on this application.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #16.0
PA robot commentedUpdate git url