Great work, Taher,
thank you for the example setup. I'm going to play with it in the next
days and provide my feedback.
Thanks,
Michael
Am 20.02.18 um 17:48 schrieb Taher Alkhateeb:
Hello documentation team and everyone
I have created a slightly modified design of the documentation
Hi Michael
Thanks - with Jira spam we also usually ask the infra team to disable
the Jira user so it can't create any more issues. In this case it seems
OK since they only created one issue, it's just something to note for
next time :-)
Thanks
Sharan
On 21/02/18 14:24, Michael Brohl
Hi Sharan,
thanks you for the hint, I'll try to remember next time!
Regards,
Michael
Am 21.02.18 um 14:44 schrieb Sharan Foga:
Hi Michael
Thanks - with Jira spam we also usually ask the infra team to disable
the Jira user so it can't create any more issues. In this case it
seems OK
Thank you for the work, Taher
I have played with it and merge with my tests.
Currently, I have start from Accounting_Agreement, convert from docbook and
update and
test renderer by both your gradle task and by AsciidocFx html button
With a lot of include, result html file would be very large
I have just deleted this SPAM issue.
Regards,
Michael
Am 21.02.18 um 14:00 schrieb creehackrooting (JIRA):
creehackrooting created OFBIZ-10229:
---
Summary: Creehack APk On Android
Key: OFBIZ-10229
URL:
So here is what happened from my view:
- you committed something which impacts design without taking it to the
community
- we objected to the design and suggested to revert and cooperate on a new
design
- instead you went ahead and immediately committed a new design without
asking anyone for
Hi Taher, all,
we already had several discussions about this pattern and the bad
effects we have to suffer from it. As an example, see [1], [2], there
are others.
Appealing and discussing does not seem to work for a a few people so I
am more and more in favor of a general review-then-commit
Hello Apache Supporters and Enthusiasts
This is your FINAL reminder that the Call for Papers (CFP) for the
Apache EU Roadshow is closing soon. Our Apache EU Roadshow will focus on
Cloud, IoT, Apache Tomcat, Apache Http and will run from 13-14 June 2018
in Berlin.
Note that the CFP deadline
Is converting minilang to groovy the standard now? Any objections to
converting minilang to java.
--
Sent from: http://ofbiz.135035.n4.nabble.com/OFBiz-Dev-f165671.html
Hi Wai,
yes, the community decided to convert mini lang to groovy, see [1] and
the discussion around it.
Regards,
Michael
Am 21.02.18 um 20:55 schrieb Wai:
Is converting minilang to groovy the standard now? Any objections to
converting minilang to java.
--
Sent from:
[1]
https://lists.apache.org/thread.html/fd68dff364fde41dcb0d0d0384ebf169cbaa1e8e6c6ac60701d3d774@%3Cdev.ofbiz.apache.org%3E
Am 21.02.18 um 21:01 schrieb Michael Brohl:
Hi Wai,
yes, the community decided to convert mini lang to groovy, see [1] and
the discussion around it.
Regards,
11 matches
Mail list logo
