Thanks Mallah,
I think in this case you can use Confluence as I suggested because this work
will for now stay there.
Option: in future grab these documents and put them directly in the repo under applications/datamodel with the necessary explanation (Michael already
changed the component to
Yeah .. makes sense. It would be cool to centralize everything related to
documentation to focus efforts and avoid duplications.
On Mar 14, 2018 1:48 PM, "Sharan Foga" wrote:
Hi Taher
Thanks for the feedback, I'll do that. I am also wondering about grouping
all existing Jira
On 2018/03/13 16:37:31, Taher Alkhateeb wrote:
> Hey guys, feature implemented in r1826656. Now both plugins and ofbiz
> manual will delete before re-generating their artifacts. I believe
> this will solve the problem and I think we won't have a big problem
> with
Hi Taher
Thanks for the feedback, I'll do that. I am also wondering about grouping all
existing Jira documentation tickets into the one main umbrella task too. Like
you say it will then be a single point of reference. It could also help us
clean up some old issues that have been hanging around
Hi Jacques ,
The issue was filed.
https://issues.apache.org/jira/browse/OFBIZ-10279
I also observed that there was no way to tag the issue to be related
to docs . Some kind of "component" or "category" was expected.
regds
mallah.
Jacques,
I did not receive any error at my end. I'm retesting the improvement
locally and get back on this.
Thanks!
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co
On Wed, Mar 14, 2018 at 2:46
Thanks Deepak!
I have updated the commit log.
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co
On Wed, Mar 14, 2018 at 11:03 AM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:
> Hi Rishi,