Hi Taher, Gil,
Exactly my thoughts. Nothing (ethically and technically) should force an user to share his/her/its personal plugins. This assumption must be part of
the specifications (assumption as in a theory)
Thanks Taher!
Le 23/07/2016 à 19:44, Taher Alkhateeb a écrit :
Hi Gil,
Thank
Hi Gil,
Thank you for sharing past experiences. It seems we are tackling something
that was attempted multiple times before. I am a bit optimistic though
because having the plugin system integrated into the build system is a
different approach that solves multiple problems I think.
I would like
Hi all,
First, I like the idea of gradle being the plugin solution endebbed
within OFBiz.
This could allow OFBiz integrators to share their specific improvments
with a easy to use, OOTB tool (thinking about OfbizExtra addons or
Pierre's OEM initiatives to name a few).
Then, from what i
Hans,
Thank you for mailing me directly. But I prefer it if you would put your
reaction as a comment to the issue. That way every contributor can learn
from it.
I believe you are referring to the file general.properties, as there is no
file system.properties in any branch.
For what it is worth:
HI Gregory,
If I'm not mistaken (I'll not do it) the idea is indeed to use tokens for one time authentication, but to then use OFBiz current work flow for the
rest (ie handling sessions)
Quoting below: "Behind the scenes, we will be using the current work flow as is"
This is also what we did
[
https://issues.apache.org/jira/browse/OFBIZ-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390655#comment-15390655
]
Jacques Le Roux commented on OFBIZ-7922:
Actually I use tools/mergefromtrunk.bat (same than
Taher, Nicolas,
I like you plan Taher.
I had a small discussion with Nicolas by phone on this subject before he wrote his answer. I told me that he prefers to separate the OOTB things (aka
specialpurpose now) from the outside things (aka hot-deploy now)
I still think that if we have real
Le 22/07/2016 à 15:31, Nicolas Malin a écrit :
Hi,
Taher I like you proposal, and I wish to add some complement :)
hot-deploy is to manage specific customer site component with the business logic specific to each, Apache OFBiz can help to prepare this but do not
more (I will like to have
[
https://issues.apache.org/jira/browse/OFBIZ-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390652#comment-15390652
]
Michael Brohl commented on OFBIZ-7922:
--
Should be, the patch was created on the 13.07 release branch
[
https://issues.apache.org/jira/browse/OFBIZ-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-7922:
---
Fix Version/s: Release Branch 13.07
> Pagination through marketing campains is broken
>
[
https://issues.apache.org/jira/browse/OFBIZ-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390646#comment-15390646
]
Jacques Le Roux commented on OFBIZ-7922:
Was a matter of seconds (not kidding), done at r1753864
My idea was that we had stop and start before. I'd prefer to keep them.
Sincerely I don't see the point to start OFBiz using "gradlew ofbiz" I'd prefer
"gradlew start"
We know it's OFBis, we used start for a "couple" of years (was run before) and
it's clear to everyone I guess.
That's why I
Hi Jacques,
Perhaps we can call it shutdown instead of stop? To maintain the same
naming convention in a way.
And don't worry about the name being longer :) Gradle accepts shortcuts,
you can say ./gradlew shut or even ,/gradlew
Regards
Taher Alkhateeb
On Sat, Jul 23, 2016 at 12:29 AM, Jacques
[
https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390583#comment-15390583
]
Pierre Smits commented on OFBIZ-7754:
-
Thank you for the reminder, [~jacques.le.roux], but I want to
14 matches
Mail list logo
