Jacques Le Roux created OFBIZ-5889:
--
Summary: The online help is broken
Key: OFBIZ-5889
URL: https://issues.apache.org/jira/browse/OFBIZ-5889
Project: OFBiz
Issue Type: Bug
[
https://issues.apache.org/jira/browse/OFBIZ-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh Vijaywargiya updated OFBIZ-5546:
--
Attachment: OFBIZ-5546.patch
RAW_MATERIAL return/RMA functionality not supported OOTB
[
https://issues.apache.org/jira/browse/OFBIZ-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228199#comment-14228199
]
Harsh Vijaywargiya commented on OFBIZ-5546:
---
Created required data and attaching
Finally another question: I wanted to ask if you have made a benchmark with load tests? I guess this new layer should have a minimal impact on
performance, but better to be safe than sorry.
Jacques
Le 28/11/2014 10:09, Jacques Le Roux a écrit :
Hi Scott,
I have just a question.
The private
Hi,
OFBiz use HtmlEncoder:
public static class HtmlEncoder implements SimpleEncoder {
public String encode(String original) {
return
StringUtil.defaultWebEncoder.encodeForHTMLAttribute(original);
}
}
and before return to client side, every String is processed by
[
https://issues.apache.org/jira/browse/OFBIZ-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228203#comment-14228203
]
Swapnil Shah commented on OFBIZ-5364:
-
[~ofbizzer] The issue seems to me in step#9. If
[
https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228207#comment-14228207
]
Jacques Le Roux commented on OFBIZ-5464:
It's a pity only Jacopo and I expressed
[
https://issues.apache.org/jira/browse/OFBIZ-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228215#comment-14228215
]
Rishi Solanki commented on OFBIZ-4494:
--
As per my understanding the purchase orders
Afterthought: we agreed about having the same setting in both the releases branches and the trunk. So if we disable a component in the releases
branches it will be also in the trunk.
Then, even we enable tests, we will not be aware of UI related issues and globally all those which are no covered
[
https://issues.apache.org/jira/browse/OFBIZ-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228203#comment-14228203
]
Swapnil Shah edited comment on OFBIZ-5364 at 11/28/14 10:26 AM:
Hi Jacques,
Regarding question #1, pretty much every method in the API has been
added because I found a use case for it in the existing code. In this
case, it's not at all uncommon for useCache parameter to be passed
into a method that performs the query. If you look at the conversions
done so
Hi Scott,
I agree it's a quite an improvement once you get used to it. Thanks for your
idea and work on it!
Jacques
Le 28/11/2014 11:36, Scott Gray a écrit :
Hi Jacques,
Regarding question #1, pretty much every method in the API has been
added because I found a use case for it in the
On Nov 28, 2014, at 11:24 AM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
Also if you remember this thread started with my idea of creating a wiki page
to explain to our users the alternative strategy of using release branches
rather than released packages.
I'd like to have a
Hello all !
I followed the discussion, a bit late :
Le 28/11/2014 11:24, Jacques Le Roux a écrit :
Afterthought: we agreed about having the same setting in both the
releases branches and the trunk. So if we disable a component in the
releases branches it will be also in the trunk.
Then, even
[
https://issues.apache.org/jira/browse/OFBIZ-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Shah updated OFBIZ-1094:
Attachment: PO.png
problem in purchase order processing related to returns
[
https://issues.apache.org/jira/browse/OFBIZ-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Shah updated OFBIZ-1094:
Attachment: Return Item.png
problem in purchase order processing related to returns
[
https://issues.apache.org/jira/browse/OFBIZ-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Shah updated OFBIZ-1094:
Attachment: Return Header.png
problem in purchase order processing related to returns
[
https://issues.apache.org/jira/browse/OFBIZ-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228259#comment-14228259
]
Swapnil Shah commented on OFBIZ-1094:
-
[~vikrant] [~adri...@hlmksw.com] I think this
What is the downside if the non-core components are released on their
own with a clear set of documentation that describes the state of the
component?
My feeling is that it is better to release a clean core and framework
where ALL component are warranteed by the team to be tested and
What is the effect of this strategy on the implied warranty?
What is guaranteed to be tested?
Where will the test results for the release be available?
What is the responsibility of someone who changes the release branch
after it is released in terms of testing, support and documentation?
Is
First I might be a bit confuse in this email, sorry for that, quite
ideas came up while writing it, some organization missing.
Le 28/11/2014 14:31, Ron Wheeler a écrit :
What is the downside if the non-core components are released on their
own with a clear set of documentation that describes
If we do decide to use DITA, you may find that that posts on my web site
might give some ideas about editing and SCM for DITA using Eclipse.
http://blog.artifact-software.com/tech/?tag=dita
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype:
[
https://issues.apache.org/jira/browse/OFBIZ-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228345#comment-14228345
]
Adrian Crum commented on OFBIZ-5840:
I noticed that the icons (and screenlet behavior)
The components not supported as part of the core and framework would not
leave Apache.
They become separate sub-projects under OFBiz so that they stay in the
community but are released and supported separately so that there is
more transparency about their state.
The release of new core and
Oh, sorry i did miss a big point :)
I miss-interpreted Adrian proposal on seperate project, not enough
self-explanatory for me I guess :).
Gil
Le 28/11/2014 17:01, Ron Wheeler a écrit :
The components not supported as part of the core and framework would
not leave Apache.
They become
Can someone on the PMC or a current committer find out what has to be
done to set up an Apacahe sub-project in terms of administration (might
be nothing) and fixing the SCM access so that committers to the
sub-project are not required to be committers to the core and framework.
This may not be
As has been discussed in this thread, we can spin off special purpose
components to their own projects - where they can form their own
communities and support structure.
I am willing to use the Asset Maintenance component as a trial run. Here
are some of my initial thoughts, comments are
NP.
This is a new idea for OfBiz.
Some Apache examples
http://db.apache.org/ where Derby is a sub-project with some others.
http://xmlgraphics.apache.org/ is an example where the skill sets and
interests of the sub-projects are very different from the core
http://portals.apache.org/ is more of
I agree with Jacopo that OFBiz sub-projects will be nearly impossible to
maintain. That is why I suggested moving special purpose components to
separate projects.
I am willing to move one component to a separate project as a trial run.
I have no interest in being a chair of a sub-PMC.
[
https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228386#comment-14228386
]
Gil Portenseigne commented on OFBIZ-5464:
-
To open a branch it needs to have
[
https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228401#comment-14228401
]
Pierre Smits commented on OFBIZ-5464:
-
Gil,
Please read all the comments in this
[
https://issues.apache.org/jira/browse/OFBIZ-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228414#comment-14228414
]
Gil Portenseigne commented on OFBIZ-5464:
-
Oh, you mean you've already done the
No need to fork the project. Let's keep it within Apache.
On 28/11/2014 11:20 AM, Adrian Crum wrote:
As has been discussed in this thread, we can spin off special purpose
components to their own projects - where they can form their own
communities and support structure.
I am willing to use
On 28/11/2014 11:23 AM, Adrian Crum wrote:
I agree with Jacopo that OFBiz sub-projects will be nearly impossible
to maintain. That is why I suggested moving special purpose components
to separate projects.
Apache sub-projects seem to be very easy to maintain for other projects.
Perhaps we
On 28/11/2014 11:23 AM, Adrian Crum wrote:
I agree with Jacopo that OFBiz sub-projects will be nearly impossible
to maintain. That is why I suggested moving special purpose components
to separate projects.
I am willing to move one component to a separate project as a trial
run. I have no
This conversation has stopped making any sense.
The special purpose components are removed from releases because we
don't have enough resources to maintain them. Now there is interest in
putting them back, but we STILL don't have the resources to maintain
them. A suggestion was made to make
Hi Adrian and everyone,
I think this issue was discussed in multiple threads before. There seems to
be a general agreement that resources are low. The question is then why
sub-projects or forks or spinoffs? Why not just keep specialpurpose in the
project? It's live functioning code even if not
!) Sub-projects allow worthwhile projects to find new supporters through
better transparency, focused mission and clearer borders around the
knowledge needed to contribute.
2) I thought that Adrian was suggesting that Asset Management was an
effort that he would support
3) Just when people
Ron, we get that you really like the idea of sub-projects. The only
positive I can see about a sub-project is that the component gets to
stick with the Apache brand/trademark, I'm pretty sure that's the only
positive I've seen you mention that doesn't also apply to an external
project. With the
On 28/11/2014 5:49 PM, Scott Gray wrote:
Ron, we get that you really like the idea of sub-projects. The only
positive I can see about a sub-project is that the component gets to
stick with the Apache brand/trademark, I'm pretty sure that's the only
positive I've seen you mention that doesn't
A few responses below but all I really have left to say is that if Adrian
or anyone else wants to take a fork of any special purpose component and
maintain it outside of the OFBiz project then I'm all for it. Assuming
those forks made good progress on improving the component then I'd also be
in
On 28/11/2014 7:06 PM, Scott Gray wrote:
A few responses below but all I really have left to say is that if Adrian
or anyone else wants to take a fork of any special purpose component and
maintain it outside of the OFBiz project then I'm all for it. Assuming
those forks made good progress on
Hi Adrian,
Sounds like a good plan to me. I think there should probably be some sort
of a delay in step #5 and it should ultimately be decided by a PMC vote at
that point in time as well. I totally support the concept though.
Regards
Scott
On Sat, Nov 29, 2014 at 5:20 AM, Adrian Crum
Don't forget to get ICLAs and Corporate CLAs for the new site for each
contributor otherwise you will have trouble if you want to submit it to
Apache OFBiz in the future.
I guess that if you offer it under an Apache license without having an
ICLA /CCLA in place, you would be personally liable
OFBiz itself went through that on a much larger scale when joining the ASF.
It took some time but it wasn't a big deal.
No users are forced to do anything other than make a choice: stick with
what you have or change to what is now available. Open source users make
these types of decisions on a
On 28/11/2014 9:38 PM, Scott Gray wrote:
OFBiz itself went through that on a much larger scale when joining the ASF.
It took some time but it wasn't a big deal.
No users are forced to do anything other than make a choice: stick with
what you have or change to what is now available. Open source
Yeah I understood that. Deleting simply means it won't be available in
future releases. It wouldn't suddenly disappear out of pre-existing
releases.
Regards
Scott
On Sat, Nov 29, 2014 at 3:49 PM, Ron Wheeler rwhee...@artifact-software.com
wrote:
On 28/11/2014 9:38 PM, Scott Gray wrote:
On 28/11/2014 10:14 PM, Scott Gray wrote:
Yeah I understood that. Deleting simply means it won't be available
in future releases. It wouldn't suddenly disappear out of
pre-existing releases.
Got it.
Regards
Scott
On Sat, Nov 29, 2014 at 3:49 PM, Ron Wheeler
[
https://issues.apache.org/jira/browse/OFBIZ-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228624#comment-14228624
]
Swapnil Shah commented on OFBIZ-965:
[~jacopoc] I have tried to replicate this issue
[
https://issues.apache.org/jira/browse/OFBIZ-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Shah updated OFBIZ-965:
---
Attachment: SO_with_Shipment.png
PO_with_Receipt.png
[
https://issues.apache.org/jira/browse/OFBIZ-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228630#comment-14228630
]
Jacopo Cappellato commented on OFBIZ-965:
-
Thank you for the tests [~swash78]. The
On Nov 29, 2014, at 12:09 AM, Ron Wheeler rwhee...@artifact-software.com
wrote:
Can the Apache project abandon a component if someone says that they will
make a private fork?
Everyone can start a new open (or closed) source project forking a component
from OFBiz: it doesn't require any
On Nov 28, 2014, at 5:20 PM, Adrian Crum adrian.c...@sandglass-software.com
wrote:
1. Check with the ASF legal department before doing anything.
You can do step #1 without any approval from the ASF or the OFBiz project.
2. Create a project on a popular hosting site (like SourceForge, but it
[
https://issues.apache.org/jira/browse/OFBIZ-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228643#comment-14228643
]
Arun Patidar commented on OFBIZ-4482:
-
Hello Wai,
This behaviour looks correct to me.
54 matches
Mail list logo
