2012/7/10 Jacopo Cappellato
>
> The idea is to not include the specialpurpose folder from future releases:
> 13.04, 14.04 etc...
>
>
> -1
It is difficult to groups components in this way because it is based on your
personal experience (mine would be completely different, for example).
The fact that they are not part of the future "OFBiz releases" doesn't mean
that they will not be used, in fact they can be downloaded separately.
J
On Jul 9, 2012, at 10:28 PM, Jacques Le Roux wrote:
> Ha, I forgot about the release aspect of the discussion. I agree, to have
> less burden on committers shoulders when releasing, we could put the
> specialpurpose folder out of releases branches. But then I wonder how they
> will be maintain
[
https://issues.apache.org/jira/browse/OFBIZ-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410046#comment-13410046
]
Ankit Jain commented on OFBIZ-4957:
---
Jacques,
In the groovy EditShoppingList.groovy th
since I have not seen this email yet I thought I would put in my two cents.
I see a couple of ways new committers could earn their wings(avaitors),
so to speak.
1) by showing they understand ofbiz in their patches
2) by given limited rights to say specialpurpose to bring up to day one
of the fo
[
https://issues.apache.org/jira/browse/OFBIZ-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-4955:
---
Attachment: OFBIZ-4955_Add_rtl_layouts_to_pos_application.patch
Ha sorry, I spotted it but di
Ha, I forgot about the release aspect of the discussion. I agree, to have less burden on committers shoulders when releasing, we
could put the specialpurpose folder out of releases branches. But then I wonder how they will be maintained in future. This is what
is worrying me a bit: releases will
I have nothing against these ideas. It seems to me though that some applications currently in specialpurpose are more used and/or
have a larger scope than some others.
Roughly said I see 2 kinds of components there:
"1st class citizens" would be
assetmaint
ecommerce
example*
pos
maybe myportal?
[
https://issues.apache.org/jira/browse/OFBIZ-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409789#comment-13409789
]
Jacques Le Roux commented on OFBIZ-4957:
Hi Ankit, this remembers me
http://svn.a
[
https://issues.apache.org/jira/browse/OFBIZ-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Jain updated OFBIZ-4957:
--
Attachment: OFBIZ-4957.patch
Minor fix. Attached patch fix the problem.
> Error on Sho
Ankit Jain created OFBIZ-4957:
-
Summary: Error on Shopping List Page
Key: OFBIZ-4957
URL: https://issues.apache.org/jira/browse/OFBIZ-4957
Project: OFBiz
Issue Type: Bug
Components: par
From: "Jacopo Cappellato"
On Jul 7, 2012, at 1:55 PM, Jacques Le Roux wrote:
You are certainly right and I agree with your point. But this should not be a
way for committers to escape their
responsabilities.
I think the truth is in the middle. I think that that some committers are not
doing
Yes, this could be the easiest way to implement it.
And if and when we will release the "specialpurpose" applications we could
simply create a tag (if we do not plan to backport fixes for "specialpurpose"
releases) or we could create a release branch specific for "specialpurpose" (if
we do not w
So, we would remove the specialpurpose folder from the release branch?
That sounds fine to me.
-Adrian
On 7/9/2012 1:55 PM, Jacopo Cappellato wrote:
Adrian,
all you proposed sounds good to me, I like it.
What about the idea of not including specialpurpose in the releases? I think it
is impor
Adrian,
all you proposed sounds good to me, I like it.
What about the idea of not including specialpurpose in the releases? I think it
is important because it simplifies the task of reviewing the code that we
officially publish when we do a release; releasing separately will help to
focus on a
I like the general direction, but I think the steps are overly
complicated. I would prefer to keep the specialpurpose folder name, and
keep its components in the build scripts and test runs. This is
important because higher level component tests can reveal problems in
the core logic (those test
A few months ago we discussed about moving out of OFBiz some components from
framework and specialpurpose and introduce the concept of "OFBiz Extras"
projects, managed out of the ASF infrastructure.
I still think it is a good way to go, especially because it will help to grow
an ecosystem of pro
The Buildbot has detected a restored build on builder ofbiz-trunk while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/ofbiz-trunk/builds/3278
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: portunus_ubuntu
Build Reason: scheduler
Build Sourc
[
https://issues.apache.org/jira/browse/OFBIZ-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409287#comment-13409287
]
Jacques Le Roux commented on OFBIZ-3948:
Yes well summarized Jacopo, thanks
[
https://issues.apache.org/jira/browse/OFBIZ-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sascha Rodekamp closed OFBIZ-4281.
--
Resolution: Fixed
Thanks Leon fixed in Trunk @Rev1358988
> parse javascript li
[
https://issues.apache.org/jira/browse/OFBIZ-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409272#comment-13409272
]
Adrian Crum commented on OFBIZ-3948:
Thanks Jacopo - that summarizes what I was trying
[
https://issues.apache.org/jira/browse/OFBIZ-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409270#comment-13409270
]
Jacopo Cappellato commented on OFBIZ-3948:
--
Jacques, Adrian, I think I understand
[
https://issues.apache.org/jira/browse/OFBIZ-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409268#comment-13409268
]
Adrian Crum commented on OFBIZ-3948:
Jacques,
The title of this issue is "Replace all
On Jul 7, 2012, at 1:55 PM, Jacques Le Roux wrote:
> You are certainly right and I agree with your point. But this should not be a
> way for committers to escape their responsabilities.
>
> I think the truth is in the middle. I think that that some committers are not
> doing their (volunteers)
[
https://issues.apache.org/jira/browse/OFBIZ-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohamed Amine AZZI updated OFBIZ-4955:
--
Attachment: OFBIZ-4955_Add_rtl_layouts_to_pos_application.patch
PosTransation class rev
[
https://issues.apache.org/jira/browse/OFBIZ-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409064#comment-13409064
]
Mohamed Amine AZZI edited comment on OFBIZ-4955 at 7/9/12 8:13 AM:
-
[
https://issues.apache.org/jira/browse/OFBIZ-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohamed Amine AZZI updated OFBIZ-4955:
--
Attachment: (was: OFBIZ-4955_Add_rtl_layouts_to_pos_application.patch)
> Add rt
27 matches
Mail list logo
