IDempiere/FullMeeting20150114

From WikiQSS
Revision as of 19:53, 14 January 2015 by CarlosRuiz (talk | contribs) (drop JIRA notifications from log)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Table of Contents | Full Meeting Minutes | Full Meeting 2015-01-14

CarlosRuiz: Good Morning
nmicoud_: Bonjour
hieplq: good everning.
hieplq: i has gift for you :D
hieplq: IDEMPIERE-2105:IDEMPIERE-1555:IDEMPIERE-2109:IDEMPIERE-1657 IDEMPIERE-2152:IDEMPIERE-1969:IDEMPIERE-2367:IDEMPIERE-2230
CarlosRuiz: gr8 :-) thanks
CarlosRuiz: hieplq, any suggested order to follow to apply those tickets?
hieplq: order as i sent :D
CarlosRuiz: ok - will start with 2105 :-)
CarlosRuiz: nope - ProcessInfoDialog.showProcessInfo doesn't exist
hieplq: huh. i just test and it still ok
hieplq: you use development branch?
CarlosRuiz: will try IDEMPIERE-2109 first - is created there ...
CarlosRuiz: nope - it requires IDEMPIERE-1657 first
hieplq: in local i start same order i sent. with clean branch development
hieplq: wait me export and commit.
hieplq: ah but. i just download it from web and it stil ok.
hieplq: ah, yes it can import with error.
CarlosRuiz: succeeded with IDEMPIERE-1657 first
hieplq: compiler error
hieplq: ok. with reimport to check with you.
hieplq: confirm this order is ok IDEMPIERE-1657 IDEMPIERE-1555 IDEMPIERE-2109 will continue check
CarlosRuiz: I already applied 4 and testing ...
hieplq: other ok. IDEMPIERE-2105 IDEMPIERE-2152 IDEMPIERE-1969:IDEMPIERE-2367:IDEMPIERE-2230
aguerra: Hello for everybody!!!!
CarlosRuiz: Hi Alejandro
aguerra: Hi Carlos
CarlosRuiz: hieplq, I integrated IDEMPIERE-1969
CarlosRuiz: tested with InfoProduct - set a value preference for warehouse (also tested with SKU)
CarlosRuiz: re-login
CarlosRuiz: opened info window again but the value preference is not shown
hieplq: it only affect with field has defaut value.
hieplq: wait me point it .
CarlosRuiz: ah - but a value preference is to set a default value for user - and if there is a default set by dictionary - the default dict must prevail
hieplq: comment out line it will ok with other !Util.isEmpty(mField.getVO().DefaultValue, true)
CarlosRuiz: which class?
hieplq: it in infowindow
hieplq: this purpose of this line is void default value type set to field. without this line, all number field will load with 0 (want null)
hieplq: for test you can comment out this code. i will make a complete patch for it at tomorro
CarlosRuiz: ok - will comment on ticket
CarlosRuiz: hieplq, will leave IDEMPIERE-2367 and IDEMPIERE-2230 open for the moment - they require deeper tests
hieplq: yes. i apply in my server. will report when has any issue
egil: Hi to every body
CarlosRuiz: hi Eduardo
hieplq: @CarlosRuiz has some mini issue. please also help me review it. IDEMPIERE-2397 IDEMPIERE-1652 IDEMPIERE-1983 IDEMPIERE-2268
aguerra: CarlosRuiz some case
aguerra: After upgrading to version 2.1 reports the bill cxp windows, are generated in the tmp directory, but does not show
aguerra: @egil estas ahi?
aguerra: egil has migrado a 2.1?
CarlosRuiz: aguerra, you must try to reproduce that in demo.idempiere.com
CarlosRuiz: sorry - in demo.globalqss.com for 2.1
aguerra: Yes CarlosRuiz
aguerra: The password for system dosen't work
CarlosRuiz: SuperUser / System
egil: hi aguerra
egil: yes i am here
aguerra: in any of the two
egil: i reproduce this error in a seed
aguerra: sorry CarlosRuiz
aguerra: uhm
egil: jasper do not work fin print format from window
egil: and do not log any error
egil: @CarlosRuiz we are going to create the test case of this in demo.globalqss.com
aguerra: egil all my reports from window doesn't work
alara: hi @CarlosRuiz We Created the test case in the demo. If you open the invoice vendor window you'll see a print format named Error jasper from window, from the window the report is not generated. but if you created the menu directly for the report & process record, the jasper is generated correctly
alara: we created a menu named Error jasper from window where you can see the second case
alara: i tested it with C_invoice_id = 1000001
CarlosRuiz: ok - I'm checking now IDEMPIERE-2397 - will check it after
CarlosRuiz: hieplq, still there?
hieplq: yes. i'm here
CarlosRuiz: attached a patch for IDEMPIERE-2397 to avoid using IDEMPIERE_HOME at all
CarlosRuiz: and safer - it deletes the temporary files
hieplq: yes. it's bester when don't afect IDEMPIERE_HOME
CarlosRuiz: ok, will commit that
hieplq: developement branch is plan become 3.0? i ask to category for new wiki i will create for new commit.
CarlosRuiz: http://wiki.idempiere.org/en/Category:New_Features_v3.0
hieplq: @CarlosRuiz, i think IDEMPIERE-2311 and IDEMPIERE-2136 also should add to release-2.1
CarlosRuiz: yep - sounds correct
hieplq: @CarlosRuiz if you stil has time slot. please also look IDEMPIERE-2217 (change one LOC) hi @nmicoud maybe you confirm it?
CarlosRuiz: egil, alara : for jasper to work with Record_ID must be assigned to the Print button - not the Report button
CarlosRuiz: hieplq, I was able to reproduce 2217 - but the patch doesn't solve it
CarlosRuiz: I see the width in px is not saved in ad_tab_customization
hieplq: ok. i will retest it tomorrow. for now must go to bed. thanks a lot for support my ticket.
CarlosRuiz: thanks to you for contributing
aguerra: CarlosRuiz, but in the version 2.0 all my reports with out problem
aguerra: works with out problems
CarlosRuiz: hieplq, sorry - I was doing wrong test - will test again
alara: @CarlosRuiz but in 2.0 it works that way
CarlosRuiz: is not intended to work like that - probably the test case you set in demo is different
alara: i'll change the name of the parameter and try
alara: i changed the name of the parameter to C_Invoice_ID in idempiere and the jasper file but it still doesn't work
CarlosRuiz: don't understand
CarlosRuiz: you must attach it to Print button - not report button
alara: we were not taking as the default report
aguerra: for ej: to print "Las Retenciones" we put in the print button
alara: the default report is the invoice, and we create an alternative report from the report button
aguerra: alara, mi problema son todos los que están en report button
aguerra: se generan en la carpeta tmp pero no los muestra en pantalla
aguerra: It is the same as you case?
aguerra: CarlosRuiz, sorry - but you understand the case?
alara: hi @CarlosRuiz any suggestion on the case that i told you about?
CarlosRuiz: nope- I don't have a 2.0 to check
alara: idempiere.ghintech.net:10000 admin @ gardenworld.com GardenAdmin I am going to create the case there
alara: thats 2.0
egil: Hi @CarlosRuiz the test case of jasper error on window is already in the site @alara gave to you
egil: I have been testing a lot and is so rare because not show any error but the report does not work. In the site idempiere.ghintech.net:10000 you will se it work perfectly
aguerra: egil i have the same error
CarlosRuiz: ok - now I see what you mean
aguerra: for case of jasper?
CarlosRuiz: yes
aguerra: excelente!!!!!
CarlosRuiz: aguerra, alara, egil : that commit 868bbad must solve the problem
aguerra: thk
aguerra: thk a lot CarlosRuiz
alara: thanks Carlos =)
egil: If i try to update an instace the change are allready there?
egil: or i have to wait for tomorrow?
CarlosRuiz: jenkins is compiling at this moment
CarlosRuiz: http://ci.idempiere.org/
CarlosRuiz: 5 minutes to go
egil: Ok thanks you. Is good to know for future events :)
CarlosRuiz: 2.1 is ready to update - I'll restore demo.globalqss.com now
aguerra: Mil gracias!!!
CarlosRuiz: ah - sorry - compilation broken
aguerra: if I upgrade but it is currently being compiled, what happens?
CarlosRuiz: bad things happen :-)
CarlosRuiz: I always take a backup before running update.sh because of those possible issues
aguerra: I have to restore the IDempiere folder and re-upgrade, no?
CarlosRuiz: better
aguerra: ok
aguerra: I did it like 20 times, because I thought I had done wrong by reports
CarlosRuiz: ready - now it compiled fine
aguerra: ok updating !!!
CarlosRuiz: ok - gtg - c u then