Difference between revisions of "IDempiere/FullMeeting20150311"

From WikiQSS
(full meeting)
 
(drop JIRA notifications from log)
 
Line 23: Line 23:
 
'''''CarlosRuiz''''': ok, will annotate it in ticket<br>
 
'''''CarlosRuiz''''': ok, will annotate it in ticket<br>
 
'''''nmicoud''''': ok, thanks<br>
 
'''''nmicoud''''': ok, thanks<br>
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2512<br>
 
'''''Not-522e''''': [IDEMPIERE] [~nmicoud], maybe an easier workaround is to try: @SQL=SELECT 'nmicoud'||chr(64)||'tgi.fr' FROM DUAL Can you please check it?<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2512<br>
 
 
'''''ocuriele_''''': The Cash Plan is used on iDempiere ? or come from ADemDead?<br>
 
'''''ocuriele_''''': The Cash Plan is used on iDempiere ? or come from ADemDead?<br>
 
'''''aguerra''''': Buenos días a todos<br>
 
'''''aguerra''''': Buenos días a todos<br>
Line 41: Line 38:
 
'''''ocuriele_''''': mm -  I imported the new account Element and I created the new Accounting Schema but the importer don't put the default account<br>
 
'''''ocuriele_''''': mm -  I imported the new account Element and I created the new Accounting Schema but the importer don't put the default account<br>
 
'''''ocuriele_''''': for this Schema<br>
 
'''''ocuriele_''''': for this Schema<br>
'''''Not-522e''''': [IDEMPIERE] nmicoud updated IDEMPIERE-2512<br>
 
'''''Not-522e''''': [IDEMPIERE] It worked ! ... but this notation cannot be used with a process when using in a scheduler "@SQL=SELECT 'nmicoud'||chr(64)||'tgi.fr' FROM DUAL" => nmicoud@tgi.fr but when using in a process, it is not interpreted and the program tries to send an email to a not valid address<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2512<br>
 
'''''Not-522e''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.1 [+2/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/<br>
 
'''''Not-522e''''': [iDempiere] nmicoud 4bf5b5d - IDEMPIERE-2509 ResetLockedAccount messages are hardcoded<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2509 status set to "Resolved" -assignee set to "Nicolas Micoud" -resolution set to "Fixed"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2509<br>
 
 
'''''tbayen''''': Hi CarlosRuiz I heard about an earthquake in the news. Is everything ok for you?<br>
 
'''''tbayen''''': Hi CarlosRuiz I heard about an earthquake in the news. Is everything ok for you?<br>
 
'''''ocuriele_''''': http://ecodiario.eleconomista.es/telecomunicaciones-tecnologia/noticias/6543474/03/15/Colombia-hit-by-61-magnitude-earthquake-felt-in-several-cities.html<br>
 
'''''ocuriele_''''': http://ecodiario.eleconomista.es/telecomunicaciones-tecnologia/noticias/6543474/03/15/Colombia-hit-by-61-magnitude-earthquake-felt-in-several-cities.html<br>
Line 72: Line 62:
 
'''''tbayen_''''': Do you know about error 137? (http://stackoverflow.com/questions/18524574/java-program-terminate-with-java-result-137) That sounds like you have not enough resources or such<br>
 
'''''tbayen_''''': Do you know about error 137? (http://stackoverflow.com/questions/18524574/java-program-terminate-with-java-result-137) That sounds like you have not enough resources or such<br>
 
'''''JanThielemann''''': i have this wired behaviour. i change the configuration to use buckminster 3.7 ->build fails. I switch back to 4.2 -> build succeeds. A second build with 4.2 will then fail :/<br>
 
'''''JanThielemann''''': i have this wired behaviour. i change the configuration to use buckminster 3.7 ->build fails. I switch back to 4.2 -> build succeeds. A second build with 4.2 will then fail :/<br>
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2510 status set to "In Progress"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2510<br>
 
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2511 status set to "In Progress"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2511<br>
 
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2510 status set to "Peer Review Queue"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2510<br>
 
 
'''''tbayen_''''': A rule that I learned long ago is to delete ~/buckminster.output everytime I change something.<br>
 
'''''tbayen_''''': A rule that I learned long ago is to delete ~/buckminster.output everytime I change something.<br>
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2511 status set to "Peer Review Queue"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2511<br>
 
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2511 labels set to "+Patch"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2511<br>
 
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2510 labels set to "+Patch"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2510<br>
 
 
'''''tbayen_''''': This rule solves every single "error:13" for me. Perhaps it applies also to "error:137". ;)<br>
 
'''''tbayen_''''': This rule solves every single "error:13" for me. Perhaps it applies also to "error:137". ;)<br>
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2510 Attachment set to "IDEMPIERE-2510.patch"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2510<br>
 
'''''Not-522e''''': [IDEMPIERE] tsvikruha updated IDEMPIERE-2511 Attachment set to "IDEMPIERE-2511.patch"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2511<br>
 
 
'''''JanThielemann''''': tbayne: first line of my build: rm -rf ${WORKSPACE}/buckminster.output/ ${WORKSPACE}/buckminster.temp/ ${WORKSPACE}/targetPlatform/<br>
 
'''''JanThielemann''''': tbayne: first line of my build: rm -rf ${WORKSPACE}/buckminster.output/ ${WORKSPACE}/buckminster.temp/ ${WORKSPACE}/targetPlatform/<br>
 
'''''tbayen_''''': hmmm.... sorry. In german I would say "then my latin is at its end" ;)<br>
 
'''''tbayen_''''': hmmm.... sorry. In german I would say "then my latin is at its end" ;)<br>
Line 96: Line 70:
 
'''''tbayen_''''': I gtg. See you later. And CarlosRuiz: say good luck to Diego! :-)<br>
 
'''''tbayen_''''': I gtg. See you later. And CarlosRuiz: say good luck to Diego! :-)<br>
 
'''''CarlosRuiz''''': thanks tbayen_ <br>
 
'''''CarlosRuiz''''': thanks tbayen_ <br>
'''''Not-522e''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.1 [+2/-0/±2] https://bitbucket.org/idempiere/idempiere/commits/<br>
 
'''''Not-522e''''': [iDempiere] globalqss ebebaa3 - IDEMPIERE-2440 lengh of client name in session active is wrong<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2440<br>
 
'''''Not-522e''''': [IDEMPIERE] Same issue found with clientname - solving the issue definitely using substr in the view (in case a specific implementation has one of the columns larger) https://bitbucket.org/idempiere/idempiere/commits/ebebaa3<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2440<br>
 
 
'''''CarlosRuiz''''': nmicoud, what do you mean "in a process" on IDEMPIERE-2512  ?<br>
 
'''''CarlosRuiz''''': nmicoud, what do you mean "in a process" on IDEMPIERE-2512  ?<br>
 
'''''nmicoud''''': when you launch the process from the menu<br>
 
'''''nmicoud''''': when you launch the process from the menu<br>
Line 127: Line 96:
 
'''''mhernandezve''''': Hi CarlosRuiz<br>
 
'''''mhernandezve''''': Hi CarlosRuiz<br>
 
'''''mhernandezve''''': Hi orlandocurieles<br>
 
'''''mhernandezve''''': Hi orlandocurieles<br>
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss created IDEMPIERE-2513 Sequence Check not working for native sequences<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2513<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2513 status set to "Resolved" -assignee set to "Carlos Antonio Ruiz Gomez" -resolution set to "Fixed"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2513<br>
 
'''''Not-522e''''': [iDempiere] CarlosRuiz_globalqss pushed 1 commit to release-2.1 [+0/-0/±2] https://bitbucket.org/idempiere/idempiere/commits/<br>
 
'''''Not-522e''''': [iDempiere] globalqss 4bd5570 - IDEMPIERE-2513 Sequence Check not working for native sequences<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss created IDEMPIERE-2514 Copy Record failing on hidden fields<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2514<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2514 Attachment set to "jira-capture-screenshot-20150311-113810-558.png"<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2514<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2514<br>
 
'''''Not-522e''''': [IDEMPIERE] Found this is caused by CalloutInOut.orderLine {code} mTab.setValue("C_ProjectPhase_ID", new Integer(ol.getC_ProjectPhase_ID())); {code} As the field is not displayed it seems is not validated either, so instead of changing to null (which happens when the lookup is validated) it keeps the zero value set here.<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2514<br>
 
'''''Not-522e''''': [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2514<br>
 
'''''Not-522e''''': [IDEMPIERE] Workaround - set displaylogic to 1=2 on those fields instead of hiding them<br>
 
'''''Not-522e''''': [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-2514<br>
 
 
'''''CarlosRuiz''''': going out - c u then<br>
 
'''''CarlosRuiz''''': going out - c u then<br>

Latest revision as of 19:58, 11 March 2015

Table of Contents | Full Meeting Minutes | Full Meeting 2015-03-11

CarlosRuiz: Good Morning
nmicoud: Bonjour
CarlosRuiz: will be checking the peer review queue :-)
CarlosRuiz: .
ocurieles: Good Morning :D
nmicoud: Could you have a rapid look at https://idempiere.atlassian.net/browse/IDEMPIERE-2512 (there is no patch only a possible solution)
CarlosRuiz: nmicoud, that must be happening in other points where SQL is allowed
carlos__: strange my old connection as CarlosRuiz is zombie
carlos__: nmicoud, that must be happening in other points where SQL is allowed
CarlosRuiz: nmicoud, that must be happening in other points where SQL is allowed
carlos__: easier workaround maybe is to use chr(64)
nmicoud: ah i see
CarlosRuiz: can you test it ? @SQL=SELECT 'nmicoud'||chr(64)||'tgi.fr' FROM DUAL
nmicoud: not ATM, (at a meeting) but ASAP
CarlosRuiz: ok, will annotate it in ticket
nmicoud: ok, thanks
ocuriele_: The Cash Plan is used on iDempiere ? or come from ADemDead?
aguerra: Buenos días a todos
aguerra: Hello everybody
CarlosRuiz: Hi Alejandro
CarlosRuiz: ocuriele_, the cash plan is deprecated in iDempiere
CarlosRuiz: ah sorry
CarlosRuiz: cash journal is deprecated in iDempiere - cash plan is a new feature - I think is not present in adempiere
CarlosRuiz: I mean - cash flow -> http://www.adempiere.com/FS02_Cash_Flow
CarlosRuiz: don't know if you're looking for that one?
ocuriele_: Yes @CarlosRuiz, let's me make a review
ocuriele_: Some guide for use two Chart of Accounts
ocuriele_: ?
CarlosRuiz: I don't remember a guide about that - advanced functionality
ocuriele_: mm - I imported the new account Element and I created the new Accounting Schema but the importer don't put the default account
ocuriele_: for this Schema
tbayen: Hi CarlosRuiz I heard about an earthquake in the news. Is everything ok for you?
ocuriele_: http://ecodiario.eleconomista.es/telecomunicaciones-tecnologia/noticias/6543474/03/15/Colombia-hit-by-61-magnitude-earthquake-felt-in-several-cities.html
ocuriele_: :/
CarlosRuiz: thanks tbayen_ and ocuriele_ - everything fine here - it moved a lot the buildings
tbayen_: I hoped that everything is fine with your family. :)
tbayen_: I heard that some airports closed... I hope that Diego will find his way nevertheless.
CarlosRuiz: Bogota airport is working fine
tbayen_: Is he prepared for the big adventure?
CarlosRuiz: yep - bags ready
tbayen_: Di you give him all instructions which iDempiere projects are most urgent to be done? And that he has to convince his new boss to agree with your plans?
CarlosRuiz: hahaha - I can't do that - don't know your priorities
tbayen_: I am sure there will be time to do some sponorings in the sense of the community needs. ;-)
CarlosRuiz: that sounds great
JanThielemann: hey guys, i'm trying to build idempiere 2.1 via jenkins but i always get this error: ERROR: org.eclipse.core.runtime.CoreException: /var/lib/jenkins/workspace/iDempiere2.1/org.adempiere.server-feature/product.ant:23: Java returned: 137
JanThielemann: do you know why? because on the same server i build my 2.0 and theres no problem at all
JanThielemann: im using java 7 and buckminster 4.2
CarlosRuiz: JanThielemann, you can open a user on ci.idempiere.org and check what is different there
CarlosRuiz: ah - I think I have that option disabled - I can create a user for you
tbayen_: The ant script does not write its error messages. I had a similar issue in IDEMPIERE-1618. There is a patch to see the erroro messages. afair you can also see the error log in the logfile of your eclipse installation.
JanThielemann: carlosruiz i already have a user :)
JanThielemann: jthielemann
JanThielemann: i'll check it out
tbayen_: Do you know about error 137? (http://stackoverflow.com/questions/18524574/java-program-terminate-with-java-result-137) That sounds like you have not enough resources or such
JanThielemann: i have this wired behaviour. i change the configuration to use buckminster 3.7 ->build fails. I switch back to 4.2 -> build succeeds. A second build with 4.2 will then fail :/
tbayen_: A rule that I learned long ago is to delete ~/buckminster.output everytime I change something.
tbayen_: This rule solves every single "error:13" for me. Perhaps it applies also to "error:137". ;)
JanThielemann: tbayne: first line of my build: rm -rf ${WORKSPACE}/buckminster.output/ ${WORKSPACE}/buckminster.temp/ ${WORKSPACE}/targetPlatform/
tbayen_: hmmm.... sorry. In german I would say "then my latin is at its end" ;)
JanThielemann: tbayen_: the translation is "I am at my wits end" :)
tbayen_: But that's not so funny. :-D
tbayen_: I gtg. See you later. And CarlosRuiz: say good luck to Diego! :-)
CarlosRuiz: thanks tbayen_
CarlosRuiz: nmicoud, what do you mean "in a process" on IDEMPIERE-2512 ?
nmicoud: when you launch the process from the menu
CarlosRuiz: the default for a parameter?
nmicoud: yes
CarlosRuiz: must do the same - let me test it ...
CarlosRuiz: testing with Recurring Run > Parameter Comment
CarlosRuiz: it worked here
nmicoud: wow
CarlosRuiz: in default from a prm worked also without the chr
nmicoud: mean you use same param in scheduler and process ?
CarlosRuiz: ah - just tested default prm in process
CarlosRuiz: don't understand the case?
nmicoud: try the request email processor ; email adress param : launch it through in a scheduler ; with chr(64) is ok launch it in a process ; with chr(64) is not ok
CarlosRuiz: yes - the scheduler must be doing Env.parseContext - so it requires the chr
CarlosRuiz: and solving the default doesn't require it - but work both ways
nmicoud: means that @SQL=SELECT 'nmicoud'||(chr64)||'tgi.fr' FROM DUAL works for scheduler and process (from menu) ?
CarlosRuiz: yep - in my test it worked as a default from menu (tested with recurring process
nmicoud: that's weird ; need to retest then
mhernandezve: Hi partners!!
orlandocurieles: HI @mhernandezve
orlandocurieles: @CarlosRuiz in the Tree Maintenance i can't see the search box in demo.idempiere.com
orlandocurieles: i need close the form and open again to see correctly
CarlosRuiz: Hi Miguel
CarlosRuiz: yes orlandocurieles - I've seen that bug since some time - also in 2.1
mhernandezve: Hi CarlosRuiz
mhernandezve: Hi orlandocurieles
CarlosRuiz: going out - c u then