In preparation for the 13.04 branch
Locked
In preparation for the 13.04 branch
 
|
Hi all,
the next month is the month of the creation of our annual branch release: release13.04. In preparation for this, I would like to propose to exclude from the upcoming new branch the specialpurpose folder and some of the themes components: this is inline with what we have discussed recently for the trunk (and there seemed to be a good consensus/interest about this), i.e. separating the specialpurpose folders into an optional module that is not built and deployed by default: for the trunk this requires some work to make the build scripts more flexible, but for the branch it is much simpler (we can simply remove the folders from the branch). This will help a lot to avoid the risk to receive vulnerability reports for the future releases, that require a good amount of work for us; in fact there are a lot of external jars in specialpurpose and if we deliver them in our releases we should also take care of making sure that, if the external projects issue new releases with fixes for vulnerabilities then we should also issue a new release as well: maintaining this is time consuming and also reviewing all the code to make sure it meets good standard of quality and it is clear from license issues when a release is issued is becoming an overwhelming effort. If we deliver in releases a smaller codebase, everything will be easier and more manageable. Of course we can still decide to issue a release of "specialpurpose" components separately. WDYT? Jacopo |
Re: In preparation for the 13.04 branch
|
|
That seems pretty harmless. Anyone wanting to use specialpurpose can
just add it to their local copy. -Adrian On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: > Hi all, > > the next month is the month of the creation of our annual branch release: release13.04. > In preparation for this, I would like to propose to exclude from the upcoming new branch the specialpurpose folder and some of the themes components: this is inline with what we have discussed recently for the trunk (and there seemed to be a good consensus/interest about this), i.e. separating the specialpurpose folders into an optional module that is not built and deployed by default: for the trunk this requires some work to make the build scripts more flexible, but for the branch it is much simpler (we can simply remove the folders from the branch). > This will help a lot to avoid the risk to receive vulnerability reports for the future releases, that require a good amount of work for us; in fact there are a lot of external jars in specialpurpose and if we deliver them in our releases we should also take care of making sure that, if the external projects issue new releases with fixes for vulnerabilities then we should also issue a new release as well: maintaining this is time consuming and also reviewing all the code to make sure it meets good standard of quality and it is clear from license issues when a release is issued is becoming an overwhelming effort. If we deliver in releases a smaller codebase, everything will be easier and more manageable. > Of course we can still decide to issue a release of "specialpurpose" components separately. > > WDYT? > > Jacopo |
Re: In preparation for the 13.04 branch
Administrator
|
Agreed
Jacques From: "Adrian Crum" <[hidden email]> > That seems pretty harmless. Anyone wanting to use specialpurpose can > just add it to their local copy. > > -Adrian > > On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: >> Hi all, >> >> the next month is the month of the creation of our annual branch release: release13.04. >> In preparation for this, I would like to propose to exclude from the upcoming new branch the specialpurpose folder and some of the themes components: this is inline with what we have discussed recently for the trunk (and there seemed to be a good consensus/interest about this), i.e. separating the specialpurpose folders into an optional module that is not built and deployed by default: for the trunk this requires some work to make the build scripts more flexible, but for the branch it is much simpler (we can simply remove the folders from the branch). >> This will help a lot to avoid the risk to receive vulnerability reports for the future releases, that require a good amount of work for us; in fact there are a lot of external jars in specialpurpose and if we deliver them in our releases we should also take care of making sure that, if the external projects issue new releases with fixes for vulnerabilities then we should also issue a new release as well: maintaining this is time consuming and also reviewing all the code to make sure it meets good standard of quality and it is clear from license issues when a release is issued is becoming an overwhelming effort. If we deliver in releases a smaller codebase, everything will be easier and more manageable. >> Of course we can still decide to issue a release of "specialpurpose" components separately. >> >> WDYT? >> >> Jacopo > |
Re: In preparation for the 13.04 branch
|
|
+1
One thing will need to move convertProductPriceCurrency property from ecommerce.properies file, may be place it in catalog.properties or in some other property file. As this is used for automatic product price currency conversion (r1125215). Thanks & Regards -- Deepak Dixit On Mar 23, 2013, at 2:40 AM, Jacques Le Roux wrote: > Agreed > > Jacques > > From: "Adrian Crum" <[hidden email]> >> That seems pretty harmless. Anyone wanting to use specialpurpose can >> just add it to their local copy. >> >> -Adrian >> >> On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: >>> Hi all, >>> >>> the next month is the month of the creation of our annual branch release: release13.04. >>> In preparation for this, I would like to propose to exclude from the upcoming new branch the specialpurpose folder and some of the themes components: this is inline with what we have discussed recently for the trunk (and there seemed to be a good consensus/interest about this), i.e. separating the specialpurpose folders into an optional module that is not built and deployed by default: for the trunk this requires some work to make the build scripts more flexible, but for the branch it is much simpler (we can simply remove the folders from the branch). >>> This will help a lot to avoid the risk to receive vulnerability reports for the future releases, that require a good amount of work for us; in fact there are a lot of external jars in specialpurpose and if we deliver them in our releases we should also take care of making sure that, if the external projects issue new releases with fixes for vulnerabilities then we should also issue a new release as well: maintaining this is time consuming and also reviewing all the code to make sure it meets good standard of quality and it is clear from license issues when a release is issued is becoming an overwhelming effort. If we deliver in releases a smaller codebase, everything will be easier and more manageable. >>> Of course we can still decide to issue a release of "specialpurpose" components separately. >>> >>> WDYT? >>> >>> Jacopo >> |
|
|
It is OK,
But Does this mean ecommerce application will be removed to another directory, or will be entirely suppressed from the new release and released separately? Does this mean we will have main release with core components, and any other components will be treated as plugins or something like that? Regards, Medhat On Sat, Mar 23, 2013 at 6:36 AM, Deepak Dixit <[hidden email]>wrote: > +1 > > One thing will need to move convertProductPriceCurrency property from > ecommerce.properies file, may be place it in catalog.properties or in some > other property file. > As this is used for automatic product price currency conversion (r1125215). > > Thanks & Regards > -- > Deepak Dixit > > On Mar 23, 2013, at 2:40 AM, Jacques Le Roux wrote: > > > Agreed > > > > Jacques > > > > From: "Adrian Crum" <[hidden email]> > >> That seems pretty harmless. Anyone wanting to use specialpurpose can > >> just add it to their local copy. > >> > >> -Adrian > >> > >> On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: > >>> Hi all, > >>> > >>> the next month is the month of the creation of our annual branch > release: release13.04. > >>> In preparation for this, I would like to propose to exclude from the > upcoming new branch the specialpurpose folder and some of the themes > components: this is inline with what we have discussed recently for the > trunk (and there seemed to be a good consensus/interest about this), i.e. > separating the specialpurpose folders into an optional module that is not > built and deployed by default: for the trunk this requires some work to > make the build scripts more flexible, but for the branch it is much simpler > (we can simply remove the folders from the branch). > >>> This will help a lot to avoid the risk to receive vulnerability > reports for the future releases, that require a good amount of work for us; > in fact there are a lot of external jars in specialpurpose and if we > deliver them in our releases we should also take care of making sure that, > if the external projects issue new releases with fixes for vulnerabilities > then we should also issue a new release as well: maintaining this is time > consuming and also reviewing all the code to make sure it meets good > standard of quality and it is clear from license issues when a release is > issued is becoming an overwhelming effort. If we deliver in releases a > smaller codebase, everything will be easier and more manageable. > >>> Of course we can still decide to issue a release of "specialpurpose" > components separately. > >>> > >>> WDYT? > >>> > >>> Jacopo > >> > > |
Re: In preparation for the 13.04 branch
|
|
Based on the feedback from Deepak and Medhat: what if we include ecommerce only?
I mean: we remove from the 13.04 branch all the specialpurpose components except the ecommerce component; we could also include the "example" component, but that is probably less useful in a release. The ecommerce component has been historically always present in all our releases (as it has been implemented in the applications folder). Jacopo On Mar 23, 2013, at 6:59 AM, Medhat AbdelBadie <[hidden email]> wrote: > It is OK, > > But Does this mean ecommerce application will be removed to another > directory, or will be entirely suppressed from the new release and > released separately? > Does this mean we will have main release with core components, and any > other components will be treated as plugins or something like that? > > Regards, > Medhat > > > On Sat, Mar 23, 2013 at 6:36 AM, Deepak Dixit > <[hidden email]>wrote: > >> +1 >> >> One thing will need to move convertProductPriceCurrency property from >> ecommerce.properies file, may be place it in catalog.properties or in some >> other property file. >> As this is used for automatic product price currency conversion (r1125215). >> >> Thanks & Regards >> -- >> Deepak Dixit >> >> On Mar 23, 2013, at 2:40 AM, Jacques Le Roux wrote: >> >>> Agreed >>> >>> Jacques >>> >>> From: "Adrian Crum" <[hidden email]> >>>> That seems pretty harmless. Anyone wanting to use specialpurpose can >>>> just add it to their local copy. >>>> >>>> -Adrian >>>> >>>> On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: >>>>> Hi all, >>>>> >>>>> the next month is the month of the creation of our annual branch >> release: release13.04. >>>>> In preparation for this, I would like to propose to exclude from the >> upcoming new branch the specialpurpose folder and some of the themes >> components: this is inline with what we have discussed recently for the >> trunk (and there seemed to be a good consensus/interest about this), i.e. >> separating the specialpurpose folders into an optional module that is not >> built and deployed by default: for the trunk this requires some work to >> make the build scripts more flexible, but for the branch it is much simpler >> (we can simply remove the folders from the branch). >>>>> This will help a lot to avoid the risk to receive vulnerability >> reports for the future releases, that require a good amount of work for us; >> in fact there are a lot of external jars in specialpurpose and if we >> deliver them in our releases we should also take care of making sure that, >> if the external projects issue new releases with fixes for vulnerabilities >> then we should also issue a new release as well: maintaining this is time >> consuming and also reviewing all the code to make sure it meets good >> standard of quality and it is clear from license issues when a release is >> issued is becoming an overwhelming effort. If we deliver in releases a >> smaller codebase, everything will be easier and more manageable. >>>>> Of course we can still decide to issue a release of "specialpurpose" >> components separately. >>>>> >>>>> WDYT? >>>>> >>>>> Jacopo >>>> >> >> |
Re: In preparation for the 13.04 branch
|
Administrator
|
I'm also for keeping the specialpurpose/ecommerce component in releases, it's an important part of the OFBiz brand.
I'd also like we finalize its UI, tought I have not much time/energy to put in it. At least 3 Jira are waiting for ages, 2 of them are important https://issues.apache.org/jira/browse/OFBIZ-3037 BTW about our slim-down effort, In Jira I see https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20fixVersion%20%3D%20SlimDown that issues are done (I'd not want to change the Examples components more) What else? Jacques From: "Jacopo Cappellato" <[hidden email]> > Based on the feedback from Deepak and Medhat: what if we include ecommerce only? > I mean: we remove from the 13.04 branch all the specialpurpose components except the ecommerce component; we could also include the "example" component, but that is probably less useful in a release. The ecommerce component has been historically always present in all our releases (as it has been implemented in the applications folder). > > Jacopo > > On Mar 23, 2013, at 6:59 AM, Medhat AbdelBadie <[hidden email]> wrote: > >> It is OK, >> >> But Does this mean ecommerce application will be removed to another >> directory, or will be entirely suppressed from the new release and >> released separately? >> Does this mean we will have main release with core components, and any >> other components will be treated as plugins or something like that? >> >> Regards, >> Medhat >> >> >> On Sat, Mar 23, 2013 at 6:36 AM, Deepak Dixit >> <[hidden email]>wrote: >> >>> +1 >>> >>> One thing will need to move convertProductPriceCurrency property from >>> ecommerce.properies file, may be place it in catalog.properties or in some >>> other property file. >>> As this is used for automatic product price currency conversion (r1125215). >>> >>> Thanks & Regards >>> -- >>> Deepak Dixit >>> >>> On Mar 23, 2013, at 2:40 AM, Jacques Le Roux wrote: >>> >>>> Agreed >>>> >>>> Jacques >>>> >>>> From: "Adrian Crum" <[hidden email]> >>>>> That seems pretty harmless. Anyone wanting to use specialpurpose can >>>>> just add it to their local copy. >>>>> >>>>> -Adrian >>>>> >>>>> On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: >>>>>> Hi all, >>>>>> >>>>>> the next month is the month of the creation of our annual branch >>> release: release13.04. >>>>>> In preparation for this, I would like to propose to exclude from the >>> upcoming new branch the specialpurpose folder and some of the themes >>> components: this is inline with what we have discussed recently for the >>> trunk (and there seemed to be a good consensus/interest about this), i.e. >>> separating the specialpurpose folders into an optional module that is not >>> built and deployed by default: for the trunk this requires some work to >>> make the build scripts more flexible, but for the branch it is much simpler >>> (we can simply remove the folders from the branch). >>>>>> This will help a lot to avoid the risk to receive vulnerability >>> reports for the future releases, that require a good amount of work for us; >>> in fact there are a lot of external jars in specialpurpose and if we >>> deliver them in our releases we should also take care of making sure that, >>> if the external projects issue new releases with fixes for vulnerabilities >>> then we should also issue a new release as well: maintaining this is time >>> consuming and also reviewing all the code to make sure it meets good >>> standard of quality and it is clear from license issues when a release is >>> issued is becoming an overwhelming effort. If we deliver in releases a >>> smaller codebase, everything will be easier and more manageable. >>>>>> Of course we can still decide to issue a release of "specialpurpose" >>> components separately. >>>>>> >>>>>> WDYT? >>>>>> >>>>>> Jacopo >>>>> >>> >>> > > |
Re: In preparation for the 13.04 branch
|
|
I think we should not include anything from specialpurpose folder in next release.
Deepak mentioned about an item that we may have to move to application folder, lets do that. In the process we may find few other similar things. Applications in specialpurpose folder can have their own release cycles. At that point ecommerce application will compete with third party applications like BigFish. Sometime in future either ecommerce application will be upgraded and become popular or will loose its fans to better third party application. Our goal should be to enhance the core and let service providers build specialpurpose applications. Regards Anil Patel On Mar 23, 2013, at 6:35 AM, Jacques Le Roux <[hidden email]> wrote: > I'm also for keeping the specialpurpose/ecommerce component in releases, it's an important part of the OFBiz brand. > I'd also like we finalize its UI, tought I have not much time/energy to put in it. At least 3 Jira are waiting for ages, 2 of them are important https://issues.apache.org/jira/browse/OFBIZ-3037 > > BTW about our slim-down effort, > In Jira I see https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20fixVersion%20%3D%20SlimDown that issues are done (I'd not want to change the Examples components more) > What else? > > Jacques > > From: "Jacopo Cappellato" <[hidden email]> >> Based on the feedback from Deepak and Medhat: what if we include ecommerce only? >> I mean: we remove from the 13.04 branch all the specialpurpose components except the ecommerce component; we could also include the "example" component, but that is probably less useful in a release. The ecommerce component has been historically always present in all our releases (as it has been implemented in the applications folder). >> >> Jacopo >> >> On Mar 23, 2013, at 6:59 AM, Medhat AbdelBadie <[hidden email]> wrote: >> >>> It is OK, >>> >>> But Does this mean ecommerce application will be removed to another >>> directory, or will be entirely suppressed from the new release and >>> released separately? >>> Does this mean we will have main release with core components, and any >>> other components will be treated as plugins or something like that? >>> >>> Regards, >>> Medhat >>> >>> >>> On Sat, Mar 23, 2013 at 6:36 AM, Deepak Dixit >>> <[hidden email]>wrote: >>> >>>> +1 >>>> >>>> One thing will need to move convertProductPriceCurrency property from >>>> ecommerce.properies file, may be place it in catalog.properties or in some >>>> other property file. >>>> As this is used for automatic product price currency conversion (r1125215). >>>> >>>> Thanks & Regards >>>> -- >>>> Deepak Dixit >>>> >>>> On Mar 23, 2013, at 2:40 AM, Jacques Le Roux wrote: >>>> >>>>> Agreed >>>>> >>>>> Jacques >>>>> >>>>> From: "Adrian Crum" <[hidden email]> >>>>>> That seems pretty harmless. Anyone wanting to use specialpurpose can >>>>>> just add it to their local copy. >>>>>> >>>>>> -Adrian >>>>>> >>>>>> On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: >>>>>>> Hi all, >>>>>>> >>>>>>> the next month is the month of the creation of our annual branch >>>> release: release13.04. >>>>>>> In preparation for this, I would like to propose to exclude from the >>>> upcoming new branch the specialpurpose folder and some of the themes >>>> components: this is inline with what we have discussed recently for the >>>> trunk (and there seemed to be a good consensus/interest about this), i.e. >>>> separating the specialpurpose folders into an optional module that is not >>>> built and deployed by default: for the trunk this requires some work to >>>> make the build scripts more flexible, but for the branch it is much simpler >>>> (we can simply remove the folders from the branch). >>>>>>> This will help a lot to avoid the risk to receive vulnerability >>>> reports for the future releases, that require a good amount of work for us; >>>> in fact there are a lot of external jars in specialpurpose and if we >>>> deliver them in our releases we should also take care of making sure that, >>>> if the external projects issue new releases with fixes for vulnerabilities >>>> then we should also issue a new release as well: maintaining this is time >>>> consuming and also reviewing all the code to make sure it meets good >>>> standard of quality and it is clear from license issues when a release is >>>> issued is becoming an overwhelming effort. If we deliver in releases a >>>> smaller codebase, everything will be easier and more manageable. >>>>>>> Of course we can still decide to issue a release of "specialpurpose" >>>> components separately. >>>>>>> >>>>>>> WDYT? >>>>>>> >>>>>>> Jacopo >>>>>> >>>> >>>> >> >> |
|
|
Hi,
No matter where you keep ecommerce component in releases, but the point is to exist in the release. From my prospective, it should exist as part of the main product. Functionality like link to the "PRODUCT PAGE" in the Product page in catalog manager, will not exist if ecommerce component does not exist, and if it is added as a separate component, it will need a lot of work to integrate it again, taking into consideration we do not have a vision now regarding how additional component will be added to the main product or core functions. I think we need a thread discusses how additional or separate components will be installed/integrated with the main product. Regards, Medhat On Sat, Mar 23, 2013 at 1:41 PM, Anil Patel <[hidden email]>wrote: > I think we should not include anything from specialpurpose folder in next > release. > > Deepak mentioned about an item that we may have to move to application > folder, lets do that. In the process we may find few other similar things. > > Applications in specialpurpose folder can have their own release cycles. > At that point ecommerce application will compete with third party > applications like BigFish. Sometime in future either ecommerce application > will be upgraded and become popular or will loose its fans to better third > party application. > > Our goal should be to enhance the core and let service providers build > specialpurpose applications. > > Regards > Anil Patel > > > > > > On Mar 23, 2013, at 6:35 AM, Jacques Le Roux <[hidden email]> > wrote: > > > I'm also for keeping the specialpurpose/ecommerce component in releases, > it's an important part of the OFBiz brand. > > I'd also like we finalize its UI, tought I have not much time/energy to > put in it. At least 3 Jira are waiting for ages, 2 of them are important > https://issues.apache.org/jira/browse/OFBIZ-3037 > > > > BTW about our slim-down effort, > > In Jira I see > https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20fixVersion%20%3D%20SlimDownthat issues are done (I'd not want to change the Examples components more) > > What else? > > > > Jacques > > > > From: "Jacopo Cappellato" <[hidden email]> > >> Based on the feedback from Deepak and Medhat: what if we include > ecommerce only? > >> I mean: we remove from the 13.04 branch all the specialpurpose > components except the ecommerce component; we could also include the > "example" component, but that is probably less useful in a release. The > ecommerce component has been historically always present in all our > releases (as it has been implemented in the applications folder). > >> > >> Jacopo > >> > >> On Mar 23, 2013, at 6:59 AM, Medhat AbdelBadie <[hidden email]> > wrote: > >> > >>> It is OK, > >>> > >>> But Does this mean ecommerce application will be removed to another > >>> directory, or will be entirely suppressed from the new release and > >>> released separately? > >>> Does this mean we will have main release with core components, and any > >>> other components will be treated as plugins or something like that? > >>> > >>> Regards, > >>> Medhat > >>> > >>> > >>> On Sat, Mar 23, 2013 at 6:36 AM, Deepak Dixit > >>> <[hidden email]>wrote: > >>> > >>>> +1 > >>>> > >>>> One thing will need to move convertProductPriceCurrency property from > >>>> ecommerce.properies file, may be place it in catalog.properties or in > some > >>>> other property file. > >>>> As this is used for automatic product price currency conversion > (r1125215). > >>>> > >>>> Thanks & Regards > >>>> -- > >>>> Deepak Dixit > >>>> > >>>> On Mar 23, 2013, at 2:40 AM, Jacques Le Roux wrote: > >>>> > >>>>> Agreed > >>>>> > >>>>> Jacques > >>>>> > >>>>> From: "Adrian Crum" <[hidden email]> > >>>>>> That seems pretty harmless. Anyone wanting to use specialpurpose can > >>>>>> just add it to their local copy. > >>>>>> > >>>>>> -Adrian > >>>>>> > >>>>>> On 3/22/2013 4:19 PM, Jacopo Cappellato wrote: > >>>>>>> Hi all, > >>>>>>> > >>>>>>> the next month is the month of the creation of our annual branch > >>>> release: release13.04. > >>>>>>> In preparation for this, I would like to propose to exclude from > the > >>>> upcoming new branch the specialpurpose folder and some of the themes > >>>> components: this is inline with what we have discussed recently for > the > >>>> trunk (and there seemed to be a good consensus/interest about this), > i.e. > >>>> separating the specialpurpose folders into an optional module that is > not > >>>> built and deployed by default: for the trunk this requires some work > to > >>>> make the build scripts more flexible, but for the branch it is much > simpler > >>>> (we can simply remove the folders from the branch). > >>>>>>> This will help a lot to avoid the risk to receive vulnerability > >>>> reports for the future releases, that require a good amount of work > for us; > >>>> in fact there are a lot of external jars in specialpurpose and if we > >>>> deliver them in our releases we should also take care of making sure > that, > >>>> if the external projects issue new releases with fixes for > vulnerabilities > >>>> then we should also issue a new release as well: maintaining this is > time > >>>> consuming and also reviewing all the code to make sure it meets good > >>>> standard of quality and it is clear from license issues when a > release is > >>>> issued is becoming an overwhelming effort. If we deliver in releases a > >>>> smaller codebase, everything will be easier and more manageable. > >>>>>>> Of course we can still decide to issue a release of > "specialpurpose" > >>>> components separately. > >>>>>>> > >>>>>>> WDYT? > >>>>>>> > >>>>>>> Jacopo > >>>>>> > >>>> > >>>> > >> > >> > > |
Re: In preparation for the 13.04 branch
|
|
In reply to this post by Jacques Le Roux
Am 23.03.2013 11:35, schrieb Jacques Le Roux:
> I'm also for keeping the specialpurpose/ecommerce component in releases, it's an important part of the OFBiz brand. > I'd also like we finalize its UI, tought I have not much time/energy to put in it. At least 3 Jira are waiting for ages, 2 of them are important https://issues.apache.org/jira/browse/OFBIZ-3037 I also tend to say that "specialpurpose/ecommerce" should not be removed or moved. Why I think so: ecommerce is one of most important core examples (as some other parts like eg. examples, ofbizwebsite, myportal etc). moving around always confuses users of frameworks. Define it once and keep in the defined place (or remove it) As OFBIz is a free software I would remove from there only google and ebay components. > BTW about our slim-down effort, > In Jira I see https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20fixVersion%20%3D%20SlimDown that issues are done (I'd not want to change the Examples components more) > What else? > > Jacques > > From: "Jacopo Cappellato"<[hidden email]> >> Based on the feedback from Deepak and Medhat: what if we include ecommerce only? >> I mean: we remove from the 13.04 branch all the specialpurpose components except the ecommerce component; we could also include the "example" component, but that is probably less useful in a release. The ecommerce component has been historically always present in all our releases (as it has been implemented in the applications folder). >> >> Jacopo regards, Mark -- [hidden email] http://rsync.it-infrastrukturen.org |
Re: In preparation for the 13.04 branch
|
In reply to this post by Jacopo Cappellato-4
Le 22/03/2013 17:19, Jacopo Cappellato a écrit :
> Of course we can still decide to issue a release of "specialpurpose" components separately. I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. I hope good, Nicolas -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ ------- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/ |
Re: In preparation for the 13.04 branch
|
|
I am going to commit a fix for this soon, I am working on it right now.
Jacopo On Mar 28, 2013, at 6:43 PM, Nicolas Malin <[hidden email]> wrote: > Le 22/03/2013 17:19, Jacopo Cappellato a écrit : >> Of course we can still decide to issue a release of "specialpurpose" components separately. > I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. > > I hope good, > > Nicolas > > -- > Nicolas MALIN > Consultant > Tél : 06.17.66.40.06 > Site projet : http://www.neogia.org/ > ------- > Société LibrenBerry > Tél : 02.48.02.56.12 > Site : http://www.librenberry.net/ > |
Re: In preparation for the 13.04 branch
|
|
this is now fixed (except for the ecommerce component) in rev. 1462421
Jacopo On Mar 28, 2013, at 7:04 PM, Jacopo Cappellato <[hidden email]> wrote: > I am going to commit a fix for this soon, I am working on it right now. > > Jacopo > > On Mar 28, 2013, at 6:43 PM, Nicolas Malin <[hidden email]> wrote: > >> Le 22/03/2013 17:19, Jacopo Cappellato a écrit : >>> Of course we can still decide to issue a release of "specialpurpose" components separately. >> I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. >> >> I hope good, >> >> Nicolas >> >> -- >> Nicolas MALIN >> Consultant >> Tél : 06.17.66.40.06 >> Site projet : http://www.neogia.org/ >> ------- >> Société LibrenBerry >> Tél : 02.48.02.56.12 >> Site : http://www.librenberry.net/ >> > |
Re: In preparation for the 13.04 branch
|
|
Hi jacopo,
Just to understand, what you have been fixed ? I try this process : $ svn up Actualisé à la révision 1464192 $ rm -fr specialpurpose $ ant clean-all load-demo run-tests and I have some errors :) You can see it on : http://lila.librenberry.net/html/ Sure I'm a on the wrong way ! Nicolas Le 29/03/2013 08:35, Jacopo Cappellato a écrit : > this is now fixed (except for the ecommerce component) in rev. 1462421 > > Jacopo > > > On Mar 28, 2013, at 7:04 PM, Jacopo Cappellato <[hidden email]> wrote: > >> I am going to commit a fix for this soon, I am working on it right now. >> >> Jacopo >> >> On Mar 28, 2013, at 6:43 PM, Nicolas Malin <[hidden email]> wrote: >> >>> Le 22/03/2013 17:19, Jacopo Cappellato a écrit : >>>> Of course we can still decide to issue a release of "specialpurpose" components separately. >>> I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. >>> >>> I hope good, >>> >>> Nicolas >>> >>> -- >>> Nicolas MALIN >>> Consultant >>> Tél : 06.17.66.40.06 >>> Site projet : http://www.neogia.org/ >>> ------- >>> Société LibrenBerry >>> Tél : 02.48.02.56.12 >>> Site : http://www.librenberry.net/ >>> -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ ------- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/ |
Re: In preparation for the 13.04 branch
|
|
Hi Nicolas,
the only specialpurpose component that is still required is "ecommerce" (because it contains data that is used by tests): please find below the patch that I am using to skip them. Sooner or later we should also remove the dependency on ecommerce, but for now it is less urgent because we are considering, for the upcoming branch 13.04, to include the ecommerce in the branch and leave the others out. Kind regards, Jacopo Index: specialpurpose/build.xml =================================================================== --- specialpurpose/build.xml (revision 1464006) +++ specialpurpose/build.xml (working copy) @@ -20,6 +20,7 @@ <project name="OFBiz Special Purpose Applications Build" default="build" basedir="."> <import file="../macros.xml"/> + <!-- <filelist id="specialpurpose-builds" dir="." files=" ecommerce/build.xml, @@ -39,6 +40,9 @@ birt/build.xml, example/build.xml "/> +--> + <filelist id="specialpurpose-builds" dir="." + files="ecommerce/build.xml"/> <!-- ================================================================== --> <!-- Removes all created files and directories --> Index: specialpurpose/ebay/ofbiz-component.xml =================================================================== --- specialpurpose/ebay/ofbiz-component.xml (revision 1464006) +++ specialpurpose/ebay/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="ebay" enabled="true" +<ofbiz-component name="ebay" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/ldap/ofbiz-component.xml =================================================================== --- specialpurpose/ldap/ofbiz-component.xml (revision 1464006) +++ specialpurpose/ldap/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="ldap" enabled="true" +<ofbiz-component name="ldap" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <!-- define resource loaders; most common is to use the component resource loader --> Index: specialpurpose/hhfacility/ofbiz-component.xml =================================================================== --- specialpurpose/hhfacility/ofbiz-component.xml (revision 1464006) +++ specialpurpose/hhfacility/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="hhfacility" enabled="true" +<ofbiz-component name="hhfacility" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/scrum/ofbiz-component.xml =================================================================== --- specialpurpose/scrum/ofbiz-component.xml (revision 1464006) +++ specialpurpose/scrum/ofbiz-component.xml (working copy) @@ -17,7 +17,7 @@ specific language governing permissions and limitations under the License. --> -<ofbiz-component name="scrum" enabled="true" +<ofbiz-component name="scrum" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <!-- define resource loaders; most common is to use the component resource loader --> Index: specialpurpose/example/ofbiz-component.xml =================================================================== --- specialpurpose/example/ofbiz-component.xml (revision 1464006) +++ specialpurpose/example/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="example" enabled="true" +<ofbiz-component name="example" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <!-- define resource loaders; most common is to use the component resource loader --> Index: specialpurpose/ofbizwebsite/ofbiz-component.xml =================================================================== --- specialpurpose/ofbizwebsite/ofbiz-component.xml (revision 1464006) +++ specialpurpose/ofbizwebsite/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="ofbiz" enabled="true" +<ofbiz-component name="ofbiz" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/ebaystore/ofbiz-component.xml =================================================================== --- specialpurpose/ebaystore/ofbiz-component.xml (revision 1464006) +++ specialpurpose/ebaystore/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="ebaystore" enabled="true" +<ofbiz-component name="ebaystore" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/webpos/ofbiz-component.xml =================================================================== --- specialpurpose/webpos/ofbiz-component.xml (revision 1464006) +++ specialpurpose/webpos/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="webpos" enabled="true" +<ofbiz-component name="webpos" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/birt/ofbiz-component.xml =================================================================== --- specialpurpose/birt/ofbiz-component.xml (revision 1464006) +++ specialpurpose/birt/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="birt" enabled="true" +<ofbiz-component name="birt" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/pos/ofbiz-component.xml =================================================================== --- specialpurpose/pos/ofbiz-component.xml (revision 1464006) +++ specialpurpose/pos/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="pos" enabled="true" +<ofbiz-component name="pos" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/googlecheckout/ofbiz-component.xml =================================================================== --- specialpurpose/googlecheckout/ofbiz-component.xml (revision 1464006) +++ specialpurpose/googlecheckout/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="googlecheckout" enabled="true" +<ofbiz-component name="googlecheckout" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/oagis/ofbiz-component.xml =================================================================== --- specialpurpose/oagis/ofbiz-component.xml (revision 1464006) +++ specialpurpose/oagis/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="oagis" enabled="true" +<ofbiz-component name="oagis" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/googlebase/ofbiz-component.xml =================================================================== --- specialpurpose/googlebase/ofbiz-component.xml (revision 1464006) +++ specialpurpose/googlebase/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="googlebase" enabled="true" +<ofbiz-component name="googlebase" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/cmssite/ofbiz-component.xml =================================================================== --- specialpurpose/cmssite/ofbiz-component.xml (revision 1464006) +++ specialpurpose/cmssite/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="cmssite" enabled="true" +<ofbiz-component name="cmssite" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/myportal/ofbiz-component.xml =================================================================== --- specialpurpose/myportal/ofbiz-component.xml (revision 1464006) +++ specialpurpose/myportal/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="myportal" enabled="true" +<ofbiz-component name="myportal" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/assetmaint/ofbiz-component.xml =================================================================== --- specialpurpose/assetmaint/ofbiz-component.xml (revision 1464006) +++ specialpurpose/assetmaint/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="assetmaint" enabled="true" +<ofbiz-component name="assetmaint" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <!-- define resource loaders; most common is to use the component resource loader --> Index: specialpurpose/exampleext/ofbiz-component.xml =================================================================== --- specialpurpose/exampleext/ofbiz-component.xml (revision 1464006) +++ specialpurpose/exampleext/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="exampleext" enabled="true" +<ofbiz-component name="exampleext" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/projectmgr/ofbiz-component.xml =================================================================== --- specialpurpose/projectmgr/ofbiz-component.xml (revision 1464006) +++ specialpurpose/projectmgr/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="projectmgr" enabled="true" +<ofbiz-component name="projectmgr" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> Index: specialpurpose/crowd/ofbiz-component.xml =================================================================== --- specialpurpose/crowd/ofbiz-component.xml (revision 1464006) +++ specialpurpose/crowd/ofbiz-component.xml (working copy) @@ -18,7 +18,7 @@ under the License. --> -<ofbiz-component name="crowd" enabled="true" +<ofbiz-component name="crowd" enabled="false" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> <resource-loader name="main" type="component"/> On Apr 3, 2013, at 10:45 PM, Nicolas Malin <[hidden email]> wrote: > Hi jacopo, > > Just to understand, what you have been fixed ? > > I try this process : > $ svn up > Actualisé à la révision 1464192 > $ rm -fr specialpurpose > $ ant clean-all load-demo run-tests > > and I have some errors :) > You can see it on : http://lila.librenberry.net/html/ > > Sure I'm a on the wrong way ! > Nicolas > > Le 29/03/2013 08:35, Jacopo Cappellato a écrit : >> this is now fixed (except for the ecommerce component) in rev. 1462421 >> >> Jacopo >> >> >> On Mar 28, 2013, at 7:04 PM, Jacopo Cappellato <[hidden email]> wrote: >> >>> I am going to commit a fix for this soon, I am working on it right now. >>> >>> Jacopo >>> >>> On Mar 28, 2013, at 6:43 PM, Nicolas Malin <[hidden email]> wrote: >>> >>>> Le 22/03/2013 17:19, Jacopo Cappellato a écrit : >>>>> Of course we can still decide to issue a release of "specialpurpose" components separately. >>>> I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. >>>> >>>> I hope good, >>>> >>>> Nicolas >>>> >>>> -- >>>> Nicolas MALIN >>>> Consultant >>>> Tél : 06.17.66.40.06 >>>> Site projet : http://www.neogia.org/ >>>> ------- >>>> Société LibrenBerry >>>> Tél : 02.48.02.56.12 >>>> Site : http://www.librenberry.net/ >>>> > > > -- > Nicolas MALIN > Consultant > Tél : 06.17.66.40.06 > Site projet : http://www.neogia.org/ > ------- > Société LibrenBerry > Tél : 02.48.02.56.12 > Site : http://www.librenberry.net/ > |
Re: In preparation for the 13.04 branch
|
|
Indeed, I didn't take the easier way. I continue my work to solve tests
for the next step. Thanks Jacopo Nicolas Le 04/04/2013 05:48, Jacopo Cappellato a écrit : > Hi Nicolas, > > the only specialpurpose component that is still required is "ecommerce" (because it contains data that is used by tests): please find below the patch that I am using to skip them. > Sooner or later we should also remove the dependency on ecommerce, but for now it is less urgent because we are considering, for the upcoming branch 13.04, to include the ecommerce in the branch and leave the others out. > > Kind regards, > > Jacopo > > > Index: specialpurpose/build.xml > =================================================================== > --- specialpurpose/build.xml (revision 1464006) > +++ specialpurpose/build.xml (working copy) > @@ -20,6 +20,7 @@ > > <project name="OFBiz Special Purpose Applications Build" default="build" basedir="."> > <import file="../macros.xml"/> > + <!-- > <filelist id="specialpurpose-builds" dir="." > files=" > ecommerce/build.xml, > @@ -39,6 +40,9 @@ > birt/build.xml, > example/build.xml > "/> > +--> > + <filelist id="specialpurpose-builds" dir="." > + files="ecommerce/build.xml"/> > > <!-- ================================================================== --> > <!-- Removes all created files and directories --> > Index: specialpurpose/ebay/ofbiz-component.xml > =================================================================== > --- specialpurpose/ebay/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/ebay/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="ebay" enabled="true" > +<ofbiz-component name="ebay" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/ldap/ofbiz-component.xml > =================================================================== > --- specialpurpose/ldap/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/ldap/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="ldap" enabled="true" > +<ofbiz-component name="ldap" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <!-- define resource loaders; most common is to use the component resource loader --> > Index: specialpurpose/hhfacility/ofbiz-component.xml > =================================================================== > --- specialpurpose/hhfacility/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/hhfacility/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="hhfacility" enabled="true" > +<ofbiz-component name="hhfacility" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/scrum/ofbiz-component.xml > =================================================================== > --- specialpurpose/scrum/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/scrum/ofbiz-component.xml (working copy) > @@ -17,7 +17,7 @@ > specific language governing permissions and limitations > under the License. > --> > -<ofbiz-component name="scrum" enabled="true" > +<ofbiz-component name="scrum" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <!-- define resource loaders; most common is to use the component resource loader --> > Index: specialpurpose/example/ofbiz-component.xml > =================================================================== > --- specialpurpose/example/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/example/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="example" enabled="true" > +<ofbiz-component name="example" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <!-- define resource loaders; most common is to use the component resource loader --> > Index: specialpurpose/ofbizwebsite/ofbiz-component.xml > =================================================================== > --- specialpurpose/ofbizwebsite/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/ofbizwebsite/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="ofbiz" enabled="true" > +<ofbiz-component name="ofbiz" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/ebaystore/ofbiz-component.xml > =================================================================== > --- specialpurpose/ebaystore/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/ebaystore/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="ebaystore" enabled="true" > +<ofbiz-component name="ebaystore" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/webpos/ofbiz-component.xml > =================================================================== > --- specialpurpose/webpos/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/webpos/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="webpos" enabled="true" > +<ofbiz-component name="webpos" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/birt/ofbiz-component.xml > =================================================================== > --- specialpurpose/birt/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/birt/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="birt" enabled="true" > +<ofbiz-component name="birt" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/pos/ofbiz-component.xml > =================================================================== > --- specialpurpose/pos/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/pos/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="pos" enabled="true" > +<ofbiz-component name="pos" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/googlecheckout/ofbiz-component.xml > =================================================================== > --- specialpurpose/googlecheckout/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/googlecheckout/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="googlecheckout" enabled="true" > +<ofbiz-component name="googlecheckout" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/oagis/ofbiz-component.xml > =================================================================== > --- specialpurpose/oagis/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/oagis/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="oagis" enabled="true" > +<ofbiz-component name="oagis" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/googlebase/ofbiz-component.xml > =================================================================== > --- specialpurpose/googlebase/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/googlebase/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="googlebase" enabled="true" > +<ofbiz-component name="googlebase" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/cmssite/ofbiz-component.xml > =================================================================== > --- specialpurpose/cmssite/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/cmssite/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="cmssite" enabled="true" > +<ofbiz-component name="cmssite" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/myportal/ofbiz-component.xml > =================================================================== > --- specialpurpose/myportal/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/myportal/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="myportal" enabled="true" > +<ofbiz-component name="myportal" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/assetmaint/ofbiz-component.xml > =================================================================== > --- specialpurpose/assetmaint/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/assetmaint/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="assetmaint" enabled="true" > +<ofbiz-component name="assetmaint" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <!-- define resource loaders; most common is to use the component resource loader --> > Index: specialpurpose/exampleext/ofbiz-component.xml > =================================================================== > --- specialpurpose/exampleext/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/exampleext/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="exampleext" enabled="true" > +<ofbiz-component name="exampleext" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/projectmgr/ofbiz-component.xml > =================================================================== > --- specialpurpose/projectmgr/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/projectmgr/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="projectmgr" enabled="true" > +<ofbiz-component name="projectmgr" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > Index: specialpurpose/crowd/ofbiz-component.xml > =================================================================== > --- specialpurpose/crowd/ofbiz-component.xml (revision 1464006) > +++ specialpurpose/crowd/ofbiz-component.xml (working copy) > @@ -18,7 +18,7 @@ > under the License. > --> > > -<ofbiz-component name="crowd" enabled="true" > +<ofbiz-component name="crowd" enabled="false" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/ofbiz-component.xsd"> > <resource-loader name="main" type="component"/> > > > On Apr 3, 2013, at 10:45 PM, Nicolas Malin <[hidden email]> wrote: > >> Hi jacopo, >> >> Just to understand, what you have been fixed ? >> >> I try this process : >> $ svn up >> Actualisé à la révision 1464192 >> $ rm -fr specialpurpose >> $ ant clean-all load-demo run-tests >> >> and I have some errors :) >> You can see it on : http://lila.librenberry.net/html/ >> >> Sure I'm a on the wrong way ! >> Nicolas >> >> Le 29/03/2013 08:35, Jacopo Cappellato a écrit : >>> this is now fixed (except for the ecommerce component) in rev. 1462421 >>> >>> Jacopo >>> >>> >>> On Mar 28, 2013, at 7:04 PM, Jacopo Cappellato <[hidden email]> wrote: >>> >>>> I am going to commit a fix for this soon, I am working on it right now. >>>> >>>> Jacopo >>>> >>>> On Mar 28, 2013, at 6:43 PM, Nicolas Malin <[hidden email]> wrote: >>>> >>>>> Le 22/03/2013 17:19, Jacopo Cappellato a écrit : >>>>>> Of course we can still decide to issue a release of "specialpurpose" components separately. >>>>> I worked on it, unit tests failed because specialpurpose components load some data needing. I continued the investigation but by lack of time I didn't solve the problem. >>>>> >>>>> I hope good, >>>>> >>>>> Nicolas >>>>> >>>>> -- >>>>> Nicolas MALIN >>>>> Consultant >>>>> Tél : 06.17.66.40.06 >>>>> Site projet : http://www.neogia.org/ >>>>> ------- >>>>> Société LibrenBerry >>>>> Tél : 02.48.02.56.12 >>>>> Site : http://www.librenberry.net/ >>>>> >> >> -- >> Nicolas MALIN >> Consultant >> Tél : 06.17.66.40.06 >> Site projet : http://www.neogia.org/ >> ------- >> Société LibrenBerry >> Tél : 02.48.02.56.12 >> Site : http://www.librenberry.net/ >> -- Nicolas MALIN Consultant Tél : 06.17.66.40.06 Site projet : http://www.neogia.org/ ------- Société LibrenBerry Tél : 02.48.02.56.12 Site : http://www.librenberry.net/ |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |