[jira] [Updated] (OFBIZ-7956) Updating various Dutch labels in WorkEffortUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7956: Attachment: OFBIZ-7956-WorkEffortUiLabels.xml.patch This patch addresses the issue. > Updating various Dutch labels in WorkEffortUiLabels.xml > --- > > Key: OFBIZ-7956 > URL: https://issues.apache.org/jira/browse/OFBIZ-7956 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7956-WorkEffortUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7956) Updating various Dutch labels in WorkEffortUiLabels.xml
Pierre Smits created OFBIZ-7956: --- Summary: Updating various Dutch labels in WorkEffortUiLabels.xml Key: OFBIZ-7956 URL: https://issues.apache.org/jira/browse/OFBIZ-7956 Project: OFBiz Issue Type: Improvement Components: workeffort Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421581#comment-15421581 ] Pierre Smits commented on OFBIZ-6184: - It was important enough for me to create the issue. It is nothing more than a moot point in your point of view. > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421404#comment-15421404 ] Pierre Smits commented on OFBIZ-6184: - Splitting them up into separate components is also an option, as it offers choice. Faciltymgr is not something that is used very often in a Professional Services Organisation. > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421227#comment-15421227 ] Pierre Smits commented on OFBIZ-7796: - I surmise that Taher is projecting how he would like things to be in production environments of adopters. In a production environment one doesn't use repositories (of any kind), just executable ready solutions to minimise risks. > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Minor > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, > OFBIZ-7796-rc.ofbiz.for.debian-v2.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
[ https://issues.apache.org/jira/browse/OFBIZ-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421222#comment-15421222 ] Pierre Smits commented on OFBIZ-7921: - Did I do that? My apologies. I will provide a new patch file. > Incorporate the readme for the bizznesstime theme > - > > Key: OFBIZ-7921 > URL: https://issues.apache.org/jira/browse/OFBIZ-7921 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Upcoming Branch > > Attachments: OFBIZ-7921-bizznesstime.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421220#comment-15421220 ] Pierre Smits commented on OFBIZ-6184: - To keep consistency with all other applications? Feel free to execute a search/find action regarding ' Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421217#comment-15421217 ] Pierre Smits commented on OFBIZ-6303: - I don't know what your reasoning regarding that would be, but the entire file is superfluous. ;) > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7953: Attachment: OFBIZ-7953-CommonUiLabels.xml.patch This patch addresses the issues mentioned in the comment by Jacques. > Updating various labels in CommonUiLabels.xml > - > > Key: OFBIZ-7953 > URL: https://issues.apache.org/jira/browse/OFBIZ-7953 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7953-CommonUiLabels.xml.patch, > OFBIZ-7953-CommonUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-7782) Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
[
https://issues.apache.org/jira/browse/OFBIZ-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits reopened OFBIZ-7782:
-
Reopening as applying a trick in a development environment to hide some files
doesn't remove useless bloatware from a .jar file intended to be used in a
production environment.
> Duplicates of .properties and Label files appear in ${ofbizRootName}.jar
>
>
> Key: OFBIZ-7782
> URL: https://issues.apache.org/jira/browse/OFBIZ-7782
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
> Attachments: Screen Shot 2016-07-13 at 10.05.43.png
>
>
> With the switch to gradle/gradlew .properties and the label definition files
> get duplicated into the build folder. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6184) Add setting of activeApp in CommonScreens.xml of AR and AP
[ https://issues.apache.org/jira/browse/OFBIZ-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420517#comment-15420517 ] Pierre Smits commented on OFBIZ-6184: - Ping? > Add setting of activeApp in CommonScreens.xml of AR and AP > --- > > Key: OFBIZ-6184 > URL: https://issues.apache.org/jira/browse/OFBIZ-6184 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk, 14.12.01, 12.04.06, 13.07.02 >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: AP, AR, Accounts > Attachments: OFBIZ-6184-ARAPCommon.patch > > > Currently the CommonScreen of both the AP and the AR applications don't have > the setting of the activeApp field. As these apps are closely related to the > accounting app, the definition can be the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5994) Have view-entity AgreementAndRole removed
[ https://issues.apache.org/jira/browse/OFBIZ-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420516#comment-15420516 ] Pierre Smits commented on OFBIZ-5994: - Ping? > Have view-entity AgreementAndRole removed > - > > Key: OFBIZ-5994 > URL: https://issues.apache.org/jira/browse/OFBIZ-5994 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk, Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Labels: agreement(s), role, roles > Attachments: OFBIZ-5994-AgreementAndRole.patch > > > The view-entity is not referenced in any Screen, Form and Service definition. > Having this in the entity-model is superfluous. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
[ https://issues.apache.org/jira/browse/OFBIZ-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7953: Attachment: OFBIZ-7953-CommonUiLabels.xml.patch This patch addresses the issue. > Updating various labels in CommonUiLabels.xml > - > > Key: OFBIZ-7953 > URL: https://issues.apache.org/jira/browse/OFBIZ-7953 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7953-CommonUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7953) Updating various labels in CommonUiLabels.xml
Pierre Smits created OFBIZ-7953: --- Summary: Updating various labels in CommonUiLabels.xml Key: OFBIZ-7953 URL: https://issues.apache.org/jira/browse/OFBIZ-7953 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6556) Have the means to create a cmssite component in the hot-deploy folder
[ https://issues.apache.org/jira/browse/OFBIZ-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420508#comment-15420508 ] Pierre Smits commented on OFBIZ-6556: - Ping? > Have the means to create a cmssite component in the hot-deploy folder > - > > Key: OFBIZ-6556 > URL: https://issues.apache.org/jira/browse/OFBIZ-6556 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6556-CmsSiteCreator.patch > > > The create-component functionality enables a quick start to create hot-deploy > components for developers. > We should have the same kind of functionality to create cmssite components in > the hot-deploy folder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-5959: Attachment: OFBIZ-5959-party-entitymodel.xml.patch This is a revised patch file addressing the relocation of entity-model files from individual components to the datamodel component. > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits > Labels: role, roles > Attachments: OFBIZ-5959-party-entitymodel.xml.patch > > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-5959: --- Assignee: Pierre Smits > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: role, roles > Attachments: OFBIZ-5959-party-entitymodel.xml.patch > > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6303) Remove EventReminders.properties as it has been declared deprecated
[ https://issues.apache.org/jira/browse/OFBIZ-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420497#comment-15420497 ] Pierre Smits commented on OFBIZ-6303: - Ping? > Remove EventReminders.properties as it has been declared deprecated > --- > > Key: OFBIZ-6303 > URL: https://issues.apache.org/jira/browse/OFBIZ-6303 > Project: OFBiz > Issue Type: Improvement > Components: workeffort >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-6303-WorkEffortReminder.patch > > > The last change came with r1040914. In the comments of the file it is stated > that an example is incorporated in WorkEffortTypeData.xml. The example exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7918) Improve Dutch labels regarding accounting reports
[ https://issues.apache.org/jira/browse/OFBIZ-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420496#comment-15420496 ] Pierre Smits commented on OFBIZ-7918: - Ping? > Improve Dutch labels regarding accounting reports > - > > Key: OFBIZ-7918 > URL: https://issues.apache.org/jira/browse/OFBIZ-7918 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7918-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
[ https://issues.apache.org/jira/browse/OFBIZ-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420495#comment-15420495 ] Pierre Smits commented on OFBIZ-7921: - Ping? > Incorporate the readme for the bizznesstime theme > - > > Key: OFBIZ-7921 > URL: https://issues.apache.org/jira/browse/OFBIZ-7921 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Upcoming Branch > > Attachments: OFBIZ-7921-bizznesstime.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419307#comment-15419307 ] Pierre Smits commented on OFBIZ-7948: - Thanks, Wai. > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[
https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415759#comment-15415759
]
Pierre Smits edited comment on OFBIZ-7948 at 8/10/16 6:48 PM:
--
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
{code}
apply plugin:'java'
{code}
before the dependencies definition.
was (Author: pfm.smits):
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
{code]
apply plugin:'java'
{code}
before the dependencies definition.
> gradle does not recognize paths to 3rd party jars in hot-deploy components
> --
>
> Key: OFBIZ-7948
> URL: https://issues.apache.org/jira/browse/OFBIZ-7948
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Wai
>
> I have a hot-deploy component. This component relies on 3rd party jars. I
> have added the paths to the 3rd party jars in the component's
> ofbiz-component.xml but the gradle build process complains about not being
> able to find symbols in those jars.
> This component used to build successfully with ant but now that ofbiz has
> switched to gradle, the build process fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[
https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415759#comment-15415759
]
Pierre Smits edited comment on OFBIZ-7948 at 8/10/16 6:48 PM:
--
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
{code]
apply plugin:'java'
{code}
before the dependencies definition.
was (Author: pfm.smits):
In order to have your component's build.gradle file compile the local external
libraries in the build process, please include
[code]
apply plugin:'java'
[code]
before the dependencies definition.
> gradle does not recognize paths to 3rd party jars in hot-deploy components
> --
>
> Key: OFBIZ-7948
> URL: https://issues.apache.org/jira/browse/OFBIZ-7948
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Wai
>
> I have a hot-deploy component. This component relies on 3rd party jars. I
> have added the paths to the 3rd party jars in the component's
> ofbiz-component.xml but the gradle build process complains about not being
> able to find symbols in those jars.
> This component used to build successfully with ant but now that ofbiz has
> switched to gradle, the build process fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[ https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415759#comment-15415759 ] Pierre Smits commented on OFBIZ-7948: - In order to have your component's build.gradle file compile the local external libraries in the build process, please include [code] apply plugin:'java' [code] before the dependencies definition. > gradle does not recognize paths to 3rd party jars in hot-deploy components > -- > > Key: OFBIZ-7948 > URL: https://issues.apache.org/jira/browse/OFBIZ-7948 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Wai > > I have a hot-deploy component. This component relies on 3rd party jars. I > have added the paths to the 3rd party jars in the component's > ofbiz-component.xml but the gradle build process complains about not being > able to find symbols in those jars. > This component used to build successfully with ant but now that ofbiz has > switched to gradle, the build process fails -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7948) gradle does not recognize paths to 3rd party jars in hot-deploy components
[
https://issues.apache.org/jira/browse/OFBIZ-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414991#comment-15414991
]
Pierre Smits commented on OFBIZ-7948:
-
If your hot-deploy component uses specific external libraries (e.g. when built
in house), you can include them in the build process. The way to do this is to
create a specific build.gradle file in your hot-deploy component with following
content:
{code}
dependencies {
//local file
compile files(/.jar)
}
{code},
where is the name of the folder within your hot-deploy component
where the external library resided (e.g. lib), and where
is the file name of the external library.
> gradle does not recognize paths to 3rd party jars in hot-deploy components
> --
>
> Key: OFBIZ-7948
> URL: https://issues.apache.org/jira/browse/OFBIZ-7948
> Project: OFBiz
> Issue Type: Bug
> Components: Gradle
>Affects Versions: Trunk
>Reporter: Wai
>
> I have a hot-deploy component. This component relies on 3rd party jars. I
> have added the paths to the 3rd party jars in the component's
> ofbiz-component.xml but the gradle build process complains about not being
> able to find symbols in those jars.
> This component used to build successfully with ant but now that ofbiz has
> switched to gradle, the build process fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-5959) Add lifespan fields to PartyRole and dependency refactoring
[ https://issues.apache.org/jira/browse/OFBIZ-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15413013#comment-15413013 ] Pierre Smits commented on OFBIZ-5959: - new link: https://ofbiz-vm.apache.org:8443/partymgr/control/viewroles?partyId=admin > Add lifespan fields to PartyRole and dependency refactoring > --- > > Key: OFBIZ-5959 > URL: https://issues.apache.org/jira/browse/OFBIZ-5959 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Trunk >Reporter: Pierre Smits > Labels: role, roles > > Currently the assignments of roles to parties are boolean (there or not > there). > However, these role assignments also have a lifespan. This can be achieved by > adding fromDate and thruDate fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407892#comment-15407892 ] Pierre Smits commented on OFBIZ-7796: - adding commented out code is like not having the code in... I am confused here. Why do you insist on having this 'gradlew ofbiz' in the codebase for a rc script that is intended for production servers? Rc scripts are intended to be used for services (e.g. to be triggered by cron script or when a server). As I have shown in https://issues.apache.org/jira/browse/OFBIZ-7796?focusedCommentId=15402191=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15402191 starting through java -jar build/libs/ofbiz.jar is seconds faster than 'gradlew ofbiz'. These are precious seconds, when an IT department (or even an external hosting provider) must meet the requirements of an uptime SLA. With a 5 nines SLA that leaves only 26.3 seconds per month. And each custom component added to the OFBiz default increases to the startup time. And for what? ./gradlew ofbiz basically does nothing more than checking what should already be there (and it gets worse when - due to some unexplicable mishap - gradlew needs to download external libraries). To get an indication what it does before the OFBiz service actually starts, I suggest you run './gradlew ofbiz -- debut > gradlew-ofbiz-start-debugge.txt' and have a look at the generated text file. > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, > OFBIZ-7796-rc.ofbiz.for.debian-v2.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7783) External library files are not in the OFBiz folder structure.
[ https://issues.apache.org/jira/browse/OFBIZ-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407567#comment-15407567 ] Pierre Smits commented on OFBIZ-7783: - >From an adopter's viewpoint, I don't care what the other adopters require for >their environments. Some could feel ok to build anew the OFBiz implementation >in SIT/QA/UAT/PROD, some could feel not ok to do so. That all depends on >whatever GRC policies and procedures the adopter has. But as a contributor to this project I am looking at what the project can and should deliver to existing adopters (visavis their process regarding upgrading in light of OFBiz conventions applied everywhere with respect to previous releases - which includes more than just code) and to new adopters (OFBiz conventions are also found in books/wiki pages/code examples, etc). Thus, getting the best of both words (control over code by the project vs flexibility for adopters) is important to me as a contributor. That includes not having to replace e.g. build.gradle with a version that the adopter requires, but offer options (in the code) to extend it. > External library files are not in the OFBiz folder structure. > - > > Key: OFBIZ-7783 > URL: https://issues.apache.org/jira/browse/OFBIZ-7783 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Blocker > > With the implementation of the external library download feature of > gradle/gradlew, the external libraries (jar files) are not in the folder > structure any more. > They should reside there, like before. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7941) Have more flexibility regarding setting SeoConfig parameters
Pierre Smits created OFBIZ-7941:
---
Summary: Have more flexibility regarding setting SeoConfig
parameters
Key: OFBIZ-7941
URL: https://issues.apache.org/jira/browse/OFBIZ-7941
Project: OFBiz
Issue Type: Improvement
Components: specialpurpose/cmssite, specialpurpose/ecommerce
Affects Versions: Trunk
Reporter: Pierre Smits
Currently when deploying mutilple cmssite and ecommerce based sites and the
adopter wants to have some kind of url shortening, the adopter must adjust the
SeoConfig.xml file manually.
The following needs to be adjusted in the file to include other componentIds:
{code}
/:/ecomseo
{code}
Also, differentiation regarding multiple site components is not obvious (can't
be achieved?) in:
{code}
disable
{code}
Furthermore, for each new addition (to allowed-contex-paths) requires the
addition of:
{code}
sample: remove /ecomseo/main
^/ecomseo/main$
/ecomseo/
/ecomseo/
301
{code}
At the moment I haven't found a work-around to have it configurable through
data (visavis multi-tenancy).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7783) External library files are not in the OFBiz folder structure.
[ https://issues.apache.org/jira/browse/OFBIZ-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407452#comment-15407452 ] Pierre Smits commented on OFBIZ-7783: - Hi [~jacques.le.roux] So basically you're trying to solve a different problem? See my comment earlier -> https://issues.apache.org/jira/browse/OFBIZ-7783?focusedCommentId=15380729=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15380729 See also the solution -> https://issues.apache.org/jira/browse/OFBIZ-7783?focusedCommentId=15384413=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15384413 > External library files are not in the OFBiz folder structure. > - > > Key: OFBIZ-7783 > URL: https://issues.apache.org/jira/browse/OFBIZ-7783 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Blocker > > With the implementation of the external library download feature of > gradle/gradlew, the external libraries (jar files) are not in the folder > structure any more. > They should reside there, like before. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7796: Attachment: OFBIZ-7796-rc.ofbiz.for.debian-v2.patch This patch addresses the issue. It also removes: * the 'kill' reference as there is no function to trigger it * the 'JAVA_BINARY' variable, as the 'start' and 'stop' functions call java directly Also, the '# gradlew terminateOfbiz' function is commented out. > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch, > OFBIZ-7796-rc.ofbiz.for.debian-v2.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[ https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407249#comment-15407249 ] Pierre Smits commented on OFBIZ-7796: - I will proivide a correct patch for the debian rc script shortly. > Running OFBiz as a service fails > > > Key: OFBIZ-7796 > URL: https://issues.apache.org/jira/browse/OFBIZ-7796 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Trunk > Environment: Ubuntu 16.04, openjdk-8-jdk >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch > > > In a new ubuntu environment I performed a checkout from trunk and ran the > loadDefault build script. > After this had completed, I moved the ofbiz directory from my user folder to > the /opt folder, and configured the Ubuntu environment to be able to run > OFBiz as a service. > This entails: > * deploy a script in /etc/init.d > * set the correct permissions of the service script > * create the service user > * changed the owner and ownergroup of the files and folders in /opt/ofbiz > and then fire the service: > sudo /etc/init.d/ofbiz start > This normally starts the proces java -jar ofbiz.jar > But now nothing happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7940) TestSuite 'partystatuschangetests' in party component fails on r15.12 branch
Pierre Smits created OFBIZ-7940:
---
Summary: TestSuite 'partystatuschangetests' in party component
fails on r15.12 branch
Key: OFBIZ-7940
URL: https://issues.apache.org/jira/browse/OFBIZ-7940
Project: OFBiz
Issue Type: Bug
Components: party
Affects Versions: Release Branch 15.12
Reporter: Pierre Smits
When executing
{code}
./ant run-test-suite -Dtest.component=party
-Dtest.suiteName=partystatuschangetests
{code}
the test stops with status unsuccessful
{code}
[java] org.ofbiz.base.start.StartupException: Cannot start()
org.ofbiz.testtools.TestRunContainer (No tests found (party /
partystatuschangetests / null))
[java] at
org.ofbiz.base.container.ContainerLoader.start(ContainerLoader.java:239)
[java] at org.ofbiz.base.start.Start.startStartLoaders(Start.java:408)
[java] at org.ofbiz.base.start.Start.start(Start.java:434)
[java] at org.ofbiz.base.start.Start.main(Start.java:135)
[java] Caused by: org.ofbiz.base.container.ContainerException: No tests
found (party / partystatuschangetests / null)
[java] at
org.ofbiz.testtools.TestRunContainer.start(TestRunContainer.java:120)
[java] at
org.ofbiz.base.container.ContainerLoader.start(ContainerLoader.java:237)
[java] ... 3 more
[java] java.lang.Exception: Error during start.
[java] at org.ofbiz.base.start.Start.start(Start.java:438)
[java] at org.ofbiz.base.start.Start.main(Start.java:135)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7939) Webtools throws an error
[
https://issues.apache.org/jira/browse/OFBIZ-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405548#comment-15405548
]
Pierre Smits commented on OFBIZ-7939:
-
I will create a new JIRA.
> Webtools throws an error
>
>
> Key: OFBIZ-7939
> URL: https://issues.apache.org/jira/browse/OFBIZ-7939
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Critical
> Fix For: Upcoming Branch
>
>
> While working on OFBIZ-7016, I excluded the ecommerce component from the
> component-load.xml file in the special purpose folder.
> In a clean, up-to-date setup I executed ./gradlew cleanAll loadDefault ofbiz
> to start up the new setup. And the following error got thrown:
> {code}
> 2016-08-02 11:46:53,805 |0.0.0.0-startStop-1 |[/webtools]
> |E| StandardWrapper.Throwable
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.loadTransforms(FreeMarkerWorker.java:151)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.makeConfiguration(FreeMarkerWorker.java:133)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.(FreeMarkerWorker.java:85)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.ftl.FreeMarkerViewHandler.(FreeMarkerViewHandler.java:48)
> ~[ofbiz.jar:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.ObjectType.getInstance(ObjectType.java:159)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.webapp.view.ViewFactory.(ViewFactory.java:49)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.(RequestHandler.java:99)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.getRequestHandler(RequestHandler.java:84)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.getRequestHandler(ControlServlet.java:329)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.init(ControlServlet.java:80)
> ~[ofbiz.jar:?]
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
> Caused by: java.lang.NullPointerException
> at
> org.apache.ofbiz.product.category.SeoConfigUtil.init(SeoConfigUtil.java:119)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.product.category.ftl.CatalogUrlSeoTransform.(CatalogUrlSeoTransform.java:76)
> ~[ofbiz.jar:?]
>
[jira] [Comment Edited] (OFBIZ-7939) Webtools throws an error
[
https://issues.apache.org/jira/browse/OFBIZ-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405507#comment-15405507
]
Pierre Smits edited comment on OFBIZ-7939 at 8/3/16 7:36 AM:
-
Should we not create a new JIRA issue to tackle the SeoConfig configuration?
With any addition of a new and deletion of a existing website (cmssite and
ecommerce store) this needs to be adjusted, and current way (modifying
SeoConfig.xml) isn't particularly flexible.
was (Author: pfm.smits):
Should we not create a new JIRA issue to tackle the SeoConfig configuration?
With any addition and deletion of a new website (cmssite and ecommerce store)
this needs to be adjusted, and current way (modifying SeoConfig.xml) isn't
particularly flexible.
> Webtools throws an error
>
>
> Key: OFBIZ-7939
> URL: https://issues.apache.org/jira/browse/OFBIZ-7939
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Critical
>
> While working on OFBIZ-7016, I excluded the ecommerce component from the
> component-load.xml file in the special purpose folder.
> In a clean, up-to-date setup I executed ./gradlew cleanAll loadDefault ofbiz
> to start up the new setup. And the following error got thrown:
> {code}
> 2016-08-02 11:46:53,805 |0.0.0.0-startStop-1 |[/webtools]
> |E| StandardWrapper.Throwable
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.loadTransforms(FreeMarkerWorker.java:151)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.makeConfiguration(FreeMarkerWorker.java:133)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.(FreeMarkerWorker.java:85)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.ftl.FreeMarkerViewHandler.(FreeMarkerViewHandler.java:48)
> ~[ofbiz.jar:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.ObjectType.getInstance(ObjectType.java:159)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.webapp.view.ViewFactory.(ViewFactory.java:49)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.(RequestHandler.java:99)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.getRequestHandler(RequestHandler.java:84)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.getRequestHandler(ControlServlet.java:329)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.init(ControlServlet.java:80)
> ~[ofbiz.jar:?]
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
> at
>
[jira] [Comment Edited] (OFBIZ-7939) Webtools throws an error
[
https://issues.apache.org/jira/browse/OFBIZ-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405507#comment-15405507
]
Pierre Smits edited comment on OFBIZ-7939 at 8/3/16 7:36 AM:
-
Should we not create a new JIRA issue to tackle the SeoConfig configuration?
With any addition and deletion of a new website (cmssite and ecommerce store)
this needs to be adjusted, and current way (modifying SeoConfig.xml) isn't
particularly flexible.
was (Author: pfm.smits):
Should we not create a new JIRA issue to tackle the SeoConfig configuration?
With any addition of a new website (cmssite and ecommerce store) this needs to
be adjusted, and current way (modifying SeoConfig.xml) isn't particularly
flexible.
> Webtools throws an error
>
>
> Key: OFBIZ-7939
> URL: https://issues.apache.org/jira/browse/OFBIZ-7939
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Critical
>
> While working on OFBIZ-7016, I excluded the ecommerce component from the
> component-load.xml file in the special purpose folder.
> In a clean, up-to-date setup I executed ./gradlew cleanAll loadDefault ofbiz
> to start up the new setup. And the following error got thrown:
> {code}
> 2016-08-02 11:46:53,805 |0.0.0.0-startStop-1 |[/webtools]
> |E| StandardWrapper.Throwable
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.loadTransforms(FreeMarkerWorker.java:151)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.makeConfiguration(FreeMarkerWorker.java:133)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.(FreeMarkerWorker.java:85)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.ftl.FreeMarkerViewHandler.(FreeMarkerViewHandler.java:48)
> ~[ofbiz.jar:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.ObjectType.getInstance(ObjectType.java:159)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.webapp.view.ViewFactory.(ViewFactory.java:49)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.(RequestHandler.java:99)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.getRequestHandler(RequestHandler.java:84)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.getRequestHandler(ControlServlet.java:329)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.init(ControlServlet.java:80)
> ~[ofbiz.jar:?]
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
[jira] [Commented] (OFBIZ-7939) Webtools throws an error
[
https://issues.apache.org/jira/browse/OFBIZ-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405507#comment-15405507
]
Pierre Smits commented on OFBIZ-7939:
-
Should we not create a new JIRA issue to tackle the SeoConfig configuration?
With any addition of a new website (cmssite and ecommerce store) this needs to
be adjusted, and current way (modifying SeoConfig.xml) isn't particularly
flexible.
> Webtools throws an error
>
>
> Key: OFBIZ-7939
> URL: https://issues.apache.org/jira/browse/OFBIZ-7939
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Critical
>
> While working on OFBIZ-7016, I excluded the ecommerce component from the
> component-load.xml file in the special purpose folder.
> In a clean, up-to-date setup I executed ./gradlew cleanAll loadDefault ofbiz
> to start up the new setup. And the following error got thrown:
> {code}
> 2016-08-02 11:46:53,805 |0.0.0.0-startStop-1 |[/webtools]
> |E| StandardWrapper.Throwable
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.loadTransforms(FreeMarkerWorker.java:151)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.makeConfiguration(FreeMarkerWorker.java:133)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.(FreeMarkerWorker.java:85)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.ftl.FreeMarkerViewHandler.(FreeMarkerViewHandler.java:48)
> ~[ofbiz.jar:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.ObjectType.getInstance(ObjectType.java:159)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.webapp.view.ViewFactory.(ViewFactory.java:49)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.(RequestHandler.java:99)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.getRequestHandler(RequestHandler.java:84)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.getRequestHandler(ControlServlet.java:329)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.init(ControlServlet.java:80)
> ~[ofbiz.jar:?]
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
> Caused by: java.lang.NullPointerException
> at
> org.apache.ofbiz.product.category.SeoConfigUtil.init(SeoConfigUtil.java:119)
>
[jira] [Commented] (OFBIZ-7016) move base component demo data from specialpurpose/ecommerce to base components
[ https://issues.apache.org/jira/browse/OFBIZ-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404311#comment-15404311 ] Pierre Smits commented on OFBIZ-7016: - It is demo data, for demo and testing purposes.. And I have seen a lot of redundancies. But I rather see redundancy in demo data than dependencies on datasets in other components.. > move base component demo data from specialpurpose/ecommerce to base components > -- > > Key: OFBIZ-7016 > URL: https://issues.apache.org/jira/browse/OFBIZ-7016 > Project: OFBiz > Issue Type: Sub-task > Components: specialpurpose/ecommerce >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Critical > Attachments: demo_marketing_moved.patch > > > Currently a lot of demo data exists in the ecommerce component that should go > into the appropriate base components (e.g. party, product, etc)... > If a adopting organisation wants to assess OFBiz without the components in > special purpose (which should be possible), loading of the demo data of sec > the base components fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7939) Webtools throws an error
[
https://issues.apache.org/jira/browse/OFBIZ-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404298#comment-15404298
]
Pierre Smits commented on OFBIZ-7939:
-
Another workaround is to copy SeoConfig.xml to the config folder of a component
in the application stack, e.g. commonext
> Webtools throws an error
>
>
> Key: OFBIZ-7939
> URL: https://issues.apache.org/jira/browse/OFBIZ-7939
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Priority: Critical
>
> While working on OFBIZ-7016, I excluded the ecommerce component from the
> component-load.xml file in the special purpose folder.
> In a clean, up-to-date setup I executed ./gradlew cleanAll loadDefault ofbiz
> to start up the new setup. And the following error got thrown:
> {code}
> 2016-08-02 11:46:53,805 |0.0.0.0-startStop-1 |[/webtools]
> |E| StandardWrapper.Throwable
> java.lang.ExceptionInInitializerError
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.loadTransforms(FreeMarkerWorker.java:151)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.makeConfiguration(FreeMarkerWorker.java:133)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.base.util.template.FreeMarkerWorker.(FreeMarkerWorker.java:85)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.ftl.FreeMarkerViewHandler.(FreeMarkerViewHandler.java:48)
> ~[ofbiz.jar:?]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[?:1.8.0_45]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[?:1.8.0_45]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[?:1.8.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> ~[?:1.8.0_45]
> at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
> at
> org.apache.ofbiz.base.util.ObjectType.getInstance(ObjectType.java:159)
> ~[ofbiz.jar:?]
> at org.apache.ofbiz.webapp.view.ViewFactory.(ViewFactory.java:49)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.(RequestHandler.java:99)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.getRequestHandler(RequestHandler.java:84)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.getRequestHandler(ControlServlet.java:329)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.init(ControlServlet.java:80)
> ~[ofbiz.jar:?]
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
> [tomcat-catalina-8.0.33.jar:8.0.33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_45]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_45]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
> Caused by: java.lang.NullPointerException
> at
> org.apache.ofbiz.product.category.SeoConfigUtil.init(SeoConfigUtil.java:119)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.product.category.ftl.CatalogUrlSeoTransform.(CatalogUrlSeoTransform.java:76)
>
[jira] [Created] (OFBIZ-7939) Webtools throws an error
Pierre Smits created OFBIZ-7939:
---
Summary: Webtools throws an error
Key: OFBIZ-7939
URL: https://issues.apache.org/jira/browse/OFBIZ-7939
Project: OFBiz
Issue Type: Bug
Components: framework/webtools
Affects Versions: Trunk
Reporter: Pierre Smits
Priority: Critical
While working on OFBIZ-7016, I excluded the ecommerce component from the
component-load.xml file in the special purpose folder.
In a clean, up-to-date setup I executed ./gradlew cleanAll loadDefault ofbiz to
start up the new setup. And the following error got thrown:
{code}
2016-08-02 11:46:53,805 |0.0.0.0-startStop-1 |[/webtools]
|E| StandardWrapper.Throwable
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method) ~[?:1.8.0_45]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
~[?:1.8.0_45]
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
~[?:1.8.0_45]
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
~[?:1.8.0_45]
at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
at
org.apache.ofbiz.base.util.template.FreeMarkerWorker.loadTransforms(FreeMarkerWorker.java:151)
~[ofbiz.jar:?]
at
org.apache.ofbiz.base.util.template.FreeMarkerWorker.makeConfiguration(FreeMarkerWorker.java:133)
~[ofbiz.jar:?]
at
org.apache.ofbiz.base.util.template.FreeMarkerWorker.(FreeMarkerWorker.java:85)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.ftl.FreeMarkerViewHandler.(FreeMarkerViewHandler.java:48)
~[ofbiz.jar:?]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method) ~[?:1.8.0_45]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
~[?:1.8.0_45]
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
~[?:1.8.0_45]
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
~[?:1.8.0_45]
at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_45]
at
org.apache.ofbiz.base.util.ObjectType.getInstance(ObjectType.java:159)
~[ofbiz.jar:?]
at org.apache.ofbiz.webapp.view.ViewFactory.(ViewFactory.java:49)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.RequestHandler.(RequestHandler.java:99)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.RequestHandler.getRequestHandler(RequestHandler.java:84)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.getRequestHandler(ControlServlet.java:329)
~[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.init(ControlServlet.java:80)
~[ofbiz.jar:?]
at
org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1238)
[tomcat-catalina-8.0.33.jar:8.0.33]
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1151)
[tomcat-catalina-8.0.33.jar:8.0.33]
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1038)
[tomcat-catalina-8.0.33.jar:8.0.33]
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4996)
[tomcat-catalina-8.0.33.jar:8.0.33]
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
[tomcat-catalina-8.0.33.jar:8.0.33]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
[tomcat-catalina-8.0.33.jar:8.0.33]
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
[tomcat-catalina-8.0.33.jar:8.0.33]
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
[tomcat-catalina-8.0.33.jar:8.0.33]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[?:1.8.0_45]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[?:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
Caused by: java.lang.NullPointerException
at
org.apache.ofbiz.product.category.SeoConfigUtil.init(SeoConfigUtil.java:119)
~[ofbiz.jar:?]
at
org.apache.ofbiz.product.category.ftl.CatalogUrlSeoTransform.(CatalogUrlSeoTransform.java:76)
~[ofbiz.jar:?]
... 32 more
2016-08-02 11:46:53,811 |0.0.0.0-startStop-1 |[/webtools]
|E| Servlet [ControlServlet] in web application [/webtools] threw load()
exception
java.lang.NullPointerException
at
org.apache.ofbiz.product.category.SeoConfigUtil.init(SeoConfigUtil.java:119)
~[ofbiz.jar:?]
at
[jira] [Updated] (OFBIZ-7754) The big problem when load seed.
[ https://issues.apache.org/jira/browse/OFBIZ-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7754: Attachment: OFBIZ-7754-SystemProperties.patch This patch addresses the issue and moves *SystemPropertyData.xml from the seed loading moment to seed-initial. > The big problem when load seed. > --- > > Key: OFBIZ-7754 > URL: https://issues.apache.org/jira/browse/OFBIZ-7754 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Kongrath Suankaewmanee >Assignee: Pierre Smits > Attachments: OFBIZ-7754-SystemProperties.patch, OFBIZ-7754.patch > > > Hi All, > Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112] > That's good for who start on use the ofbiz with initial setup, but not for > the site that already online and has to update the OFBiz core. Because when > has update OFBiz core they will use command load-seed for update. > The problem is if we use load-seed mean the configuration data that's already > exists will be replaced by the data from this file, > *CommonSystemPropertyData.xml* > So, for my suggestion should change the reader from *seed* to *seed-initial* > or remove systemPropertyValue from the data file. > Thank you, > Kongrath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5473) Expense Declaration application
[ https://issues.apache.org/jira/browse/OFBIZ-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402517#comment-15402517 ] Pierre Smits commented on OFBIZ-5473: - Hi [~Florian M], As far as I can tell (and this issue is already 2 years old), Anil used some parts of an early discussion at the ApacheCon US 2014 in Denver, Co. Unfortunately, no one felt the urge to collaborate on this any further. I completed development on a first iteration. And am using it in production. I have taken the demo site online. So there is no way to test it. > Expense Declaration application > --- > > Key: OFBIZ-5473 > URL: https://issues.apache.org/jira/browse/OFBIZ-5473 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Reporter: Pierre Smits > Labels: Expense > Attachments: ExpenseReport-10020.pdf, Screen Shot 2014-02-26 at > 16.33.11.png, Screen Shot 2014-02-26 at 16.33.43.png, Screen Shot 2014-02-26 > at 16.35.47.png, Screen Shot 2014-02-26 at 16.51.38.png > > > Have a new application to register expenses incurred by employees (and > others) and have these reviewed for approval. > This is the place holder issue for all sub issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7796) Running OFBiz as a service fails
[
https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402191#comment-15402191
]
Pierre Smits edited comment on OFBIZ-7796 at 8/1/16 3:04 PM:
-
Hi [~jacques.le.roux],
I can confirm that I now can start OFBiz with the following command:
{code}
java -jar build/libs/ofbiz.jar --start
{code}
This yielded a gain of approx *8* seconds on my dev machine, compared to:
{code}
./gradlew ofbiz
{code}
and that I can stop OFBiz with following command:
{code}
java -jar build/libs/ofbiz.jar --shutdown
{code}
was (Author: pfm.smits):
Hi [~jacques.le.roux],
I can confirm that I now can start OFBiz with the following command:
{code}
java -jar build/libs/ofbiz.jar --start
{code}
This yielded a gain of approx *8* seconds on my dev machine.
and that I can stop OFBiz with following command:
{code}
java -jar build/libs/ofbiz.jar --shutdown
{code}
> Running OFBiz as a service fails
>
>
> Key: OFBIZ-7796
> URL: https://issues.apache.org/jira/browse/OFBIZ-7796
> Project: OFBiz
> Issue Type: Sub-task
>Affects Versions: Trunk
> Environment: Ubuntu 16.04, openjdk-8-jdk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch
>
>
> In a new ubuntu environment I performed a checkout from trunk and ran the
> loadDefault build script.
> After this had completed, I moved the ofbiz directory from my user folder to
> the /opt folder, and configured the Ubuntu environment to be able to run
> OFBiz as a service.
> This entails:
> * deploy a script in /etc/init.d
> * set the correct permissions of the service script
> * create the service user
> * changed the owner and ownergroup of the files and folders in /opt/ofbiz
> and then fire the service:
> sudo /etc/init.d/ofbiz start
> This normally starts the proces java -jar ofbiz.jar
> But now nothing happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7796) Running OFBiz as a service fails
[
https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402191#comment-15402191
]
Pierre Smits edited comment on OFBIZ-7796 at 8/1/16 2:59 PM:
-
Hi [~jacques.le.roux],
I can confirm that I now can start OFBiz with the following command:
{code}
java -jar build/libs/ofbiz.jar --start
{code}
This yielded a gain of approx *8* seconds on my dev machine.
and that I can stop OFBiz with following command:
{code}
java -jar build/libs/ofbiz.jar --shutdown
{code}
was (Author: pfm.smits):
Hi [~jacques.le.roux],
I can confirm that I now can start OFBiz with the following command:
{code}
java -jar build/libs/ofbiz.jar --start
{start}
This yielded a gain of approx *8* seconds on my dev machine.
and that I can stop OFBiz with following command:
{code}
java -jar build/libs/ofbiz.jar --shutdown
{code}
> Running OFBiz as a service fails
>
>
> Key: OFBIZ-7796
> URL: https://issues.apache.org/jira/browse/OFBIZ-7796
> Project: OFBiz
> Issue Type: Sub-task
>Affects Versions: Trunk
> Environment: Ubuntu 16.04, openjdk-8-jdk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch
>
>
> In a new ubuntu environment I performed a checkout from trunk and ran the
> loadDefault build script.
> After this had completed, I moved the ofbiz directory from my user folder to
> the /opt folder, and configured the Ubuntu environment to be able to run
> OFBiz as a service.
> This entails:
> * deploy a script in /etc/init.d
> * set the correct permissions of the service script
> * create the service user
> * changed the owner and ownergroup of the files and folders in /opt/ofbiz
> and then fire the service:
> sudo /etc/init.d/ofbiz start
> This normally starts the proces java -jar ofbiz.jar
> But now nothing happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7796) Running OFBiz as a service fails
[
https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402191#comment-15402191
]
Pierre Smits commented on OFBIZ-7796:
-
Hi [~jacques.le.roux],
I can confirm that I now can start OFBiz with the following command:
{code}
java -jar build/libs/ofbiz.jar --start
{start}
This yielded a gain of approx *8* seconds on my dev machine.
and that I can stop OFBiz with following command:
{code}
java -jar build/libs/ofbiz.jar --shutdown
{code}
> Running OFBiz as a service fails
>
>
> Key: OFBIZ-7796
> URL: https://issues.apache.org/jira/browse/OFBIZ-7796
> Project: OFBiz
> Issue Type: Sub-task
>Affects Versions: Trunk
> Environment: Ubuntu 16.04, openjdk-8-jdk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
> Attachments: OFBIZ-77796-rc.ofbiz.for.debian.patch
>
>
> In a new ubuntu environment I performed a checkout from trunk and ran the
> loadDefault build script.
> After this had completed, I moved the ofbiz directory from my user folder to
> the /opt folder, and configured the Ubuntu environment to be able to run
> OFBiz as a service.
> This entails:
> * deploy a script in /etc/init.d
> * set the correct permissions of the service script
> * create the service user
> * changed the owner and ownergroup of the files and folders in /opt/ofbiz
> and then fire the service:
> sudo /etc/init.d/ofbiz start
> This normally starts the proces java -jar ofbiz.jar
> But now nothing happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7923) Improve the Marketing Demo data
[ https://issues.apache.org/jira/browse/OFBIZ-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402073#comment-15402073 ] Pierre Smits commented on OFBIZ-7923: - Thanks! > Improve the Marketing Demo data > --- > > Key: OFBIZ-7923 > URL: https://issues.apache.org/jira/browse/OFBIZ-7923 > Project: OFBiz > Issue Type: Improvement > Components: marketing >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Jacques Le Roux >Priority: Minor > Labels: campaign, data, demo, marketing > Fix For: Upcoming Branch > > Attachments: OFBIZ-7923.patch, OFBIZ-7923.patch > > > In the following issue : OFBIZ-7922, there was a problem with the pagination > of the Marketing Campaing list. Because there is not enough data in the demo, > it was more difficult to find this bug. > To help the testing of this component, we can add some Marketing Campaign in > the demo data (at least enough to unlock a second page of search). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7923) Improve the Marketing Demo data
[ https://issues.apache.org/jira/browse/OFBIZ-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401723#comment-15401723 ] Pierre Smits commented on OFBIZ-7923: - In light of removing the dependencies on the ecommerce commerce (OFBIZ-7016) , this patch should not have gone into the datasets of the ecommerce component. Instead, it should have gone into the demo data set of the marketing component. Will you correct this situation, [~jacques.le.roux]? > Improve the Marketing Demo data > --- > > Key: OFBIZ-7923 > URL: https://issues.apache.org/jira/browse/OFBIZ-7923 > Project: OFBiz > Issue Type: Improvement > Components: marketing >Affects Versions: Trunk >Reporter: Montalbano Florian >Assignee: Jacques Le Roux >Priority: Minor > Labels: campaign, data, demo, marketing > Fix For: Upcoming Branch > > Attachments: OFBIZ-7923.patch, OFBIZ-7923.patch > > > In the following issue : OFBIZ-7922, there was a problem with the pagination > of the Marketing Campaing list. Because there is not enough data in the demo, > it was more difficult to find this bug. > To help the testing of this component, we can add some Marketing Campaign in > the demo data (at least enough to unlock a second page of search). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7442) Error in adding Party tax authority
[ https://issues.apache.org/jira/browse/OFBIZ-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400576#comment-15400576 ] Pierre Smits commented on OFBIZ-7442: - You're welcome! :) > Error in adding Party tax authority > --- > > Key: OFBIZ-7442 > URL: https://issues.apache.org/jira/browse/OFBIZ-7442 > Project: OFBiz > Issue Type: Bug > Components: party >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Padmavati Rawat >Assignee: Mridul Pathak > Fix For: Release Branch 13.07, Release Branch 14.12, Release > Branch 15.12 > > Attachments: OFBIZ-7442_trunk.patch, Tax_Authority_Party.png > > > Steps: > 1) Navigate to Party page. > 2) Search for parties, select Company Party ID. > 3) Navigate on Tax Infos tab to, Add Party Tax Authority Info. > 4) Add detail of "Tax Authority Party" and click on Create button. > Expected : > Tax Authority Party should add successfully. > Actual: > Showing error while adding Tax Authority Party. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7767) Have gradle produce logs
[ https://issues.apache.org/jira/browse/OFBIZ-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398992#comment-15398992 ] Pierre Smits edited comment on OFBIZ-7767 at 7/29/16 9:01 AM: -- That makes it easy then, it seems. As none of the other contributors experience the harm, or care, this can then be closed? was (Author: pfm.smits): That makes it easy then, it seems. As none of the others experience the harm, or care, this can then be closed? > Have gradle produce logs > > > Key: OFBIZ-7767 > URL: https://issues.apache.org/jira/browse/OFBIZ-7767 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Minor > > Currently executing gradle tasks doesn't generate logs. > This is related to traceability of where 3rd party libraries (jar files) are > downloaded from and where they are placed in folder structures and which are > used in the various deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7767) Have gradle produce logs
[ https://issues.apache.org/jira/browse/OFBIZ-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398992#comment-15398992 ] Pierre Smits commented on OFBIZ-7767: - That makes it easy then, it seems. As none of the others experience the harm, or care, this can then be closed? > Have gradle produce logs > > > Key: OFBIZ-7767 > URL: https://issues.apache.org/jira/browse/OFBIZ-7767 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Minor > > Currently executing gradle tasks doesn't generate logs. > This is related to traceability of where 3rd party libraries (jar files) are > downloaded from and where they are placed in folder structures and which are > used in the various deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398986#comment-15398986 ] Pierre Smits commented on OFBIZ-7910: - That is an idea potentially to follow. But to date there is no accepted new feature (regarding the plugin proposal). Having the patch in doesn't bite that process. If and when an acceptable proposal has been implemented anything superseded can be put to the attic, right? > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7767) Have gradle produce logs
[ https://issues.apache.org/jira/browse/OFBIZ-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398978#comment-15398978 ] Pierre Smits commented on OFBIZ-7767: - Hi [~jacopoc], May I suggest the project discusses on the dev ML first the importance of logging for various parties involved in using OFBiz, before changing its impact/priority? > Have gradle produce logs > > > Key: OFBIZ-7767 > URL: https://issues.apache.org/jira/browse/OFBIZ-7767 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Priority: Minor > > Currently executing gradle tasks doesn't generate logs. > This is related to traceability of where 3rd party libraries (jar files) are > downloaded from and where they are placed in folder structures and which are > used in the various deployments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395735#comment-15395735 ] Pierre Smits commented on OFBIZ-7808: - Decisions are taken by adopters. And when existing adopters have extended their current implementations with additional Ant tasks (like I have) I can imagine they would appreciate it when the project would provide a solution that wouldn't lead to: * conflicts each time the project updates one of its core elements (the build methodology) * extensive cost regarding repair or circumvention of the solution provided by the project * cost regarding migration from Ant to Gradle. The removal of Ant scripts from the code base, and the changes over the past few weeks in the build.gradle file by the project. has led to me having to go through hoops to get what I have working against trunk - as a pre-emptive to upcoming release. A little more flexibility towards adopters and a less dogma (by 1 privileged contributor; with - what appears - only 'developers' on his mind) could/would make a lot of people happy. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395682#comment-15395682 ] Pierre Smits commented on OFBIZ-7808: - Actually it is both appropriate and good. Both elements define how adopters can extend the existing build.gradle without having the risk of conflicts (through svn up) when build.gradle gets upgraded by the project. And the two skeletons could be treated by the project the same way as it does with respect to the hot-deploy folder. It offers control for the project and flexibility (and risk mitigation) for the adopter. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7930) Copy external jars in OFBiz $buildDir/externalJars for (at least) dependency check
[ https://issues.apache.org/jira/browse/OFBIZ-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15395494#comment-15395494 ] Pierre Smits commented on OFBIZ-7930: - Hi [~jacques.le.roux], What is the difference of this issue when compared to OFBIZ-7783? > Copy external jars in OFBiz $buildDir/externalJars for (at least) dependency > check > -- > > Key: OFBIZ-7930 > URL: https://issues.apache.org/jira/browse/OFBIZ-7930 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As I warned at > https://cwiki.apache.org/confluence/display/OFBIZ/About+OWASP+Dependency+Check > it's currently difficult to separate the OFBiz jars from other jars in the > .gradle\caches contains which may contain jars unrelated to OFBiz. Notably > Eclipse jars if you use the Gradle Eclipse task and more if you use Gradle > for other reasons than OFBiz. > I did not find yet a way to avoid to have all external jars in .gradle\caches > and I wonder if it's even possible. What I would like to have is the external > jars mandatory for OFBiz to work in an isolated place. For instance a sub > folder of the main Gradle build folder. I picked $buildDir/externalJars. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393613#comment-15393613 ] Pierre Smits edited comment on OFBIZ-7808 at 7/26/16 10:45 AM: --- As a solution to this discussion we could consider adding the following two elements to the build.gradle: # apply from: 'implementationSpecificBuild.gradle' # ant.importBuild 'build.xml' And provide skeletons for both (and not being under the control of the project through e.g. .ignore) The first will enable adopters to develop their deployment specific Gradle tasks, and the second will enable the existing adopters to re-use their existing custom Ant tasks without having to spend effort regarding migration. The added value is also that the contributors of project can focus on OOTB solutions and functions. was (Author: pfm.smits): As a solution to this discussion we could consider adding the following two elements to the build.gradle: # apply from: 'implementationSpecificBuild.gradle' # ant.importBuild 'build.xml' And provide skeletons for both (and not being under the control of the project through e.g. .ignore) The first will enable adopters to develop their deployment specific Gradle tasks, and the second will enable the existing adopters to re-use their existing custom Ant tasks with out having to spend effort regarding migration. The added value is also that the contributors of project can focus on OOTB solutions and functions. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393613#comment-15393613 ] Pierre Smits commented on OFBIZ-7808: - As a solution to this discussion we could consider adding the following two elements to the build.gradle: # apply from: 'implementationSpecificBuild.gradle' # ant.importBuild 'build.xml' And provide skeletons for both (and not being under the control of the project through e.g. .ignore) The first will enable adopters to develop their deployment specific Gradle tasks, and the second will enable the existing adopters to re-use their existing custom Ant tasks with out having to spend effort regarding migration. The added value is also that the contributors of project can focus on OOTB solutions and functions. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6087) Extend ./ant create-tenant to be able to differentiate between OLTP and OLAP rdbms
[ https://issues.apache.org/jira/browse/OFBIZ-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393558#comment-15393558 ] Pierre Smits commented on OFBIZ-6087: - Good question, [~jacques le roux]! But aren't requirements depended on the business processes of adopters/users? So far, we have established the following kinds of adopters/users of OFBiz: * various company types in different sectors (Retail and Trade - ecommerce, Manufacturing, Professional services, etc.) in various sizes (SMALL - e.g. mom-and-pop setups, MEDIUM and LARGE), each having their specifics regarding local legislation (or even having a cross border impact legislation wise) * users in various business domains, like accounting, sales, manufacturing, projects, marketing, user mgt, etc. * OFBiz developers working on proprietary solutions and not contributing to the project * OFBiz developers contributing to the project * System admins responsible for adopter specific OFBiz setup ups. All these drive the requirements. And catering (more or less) to that drives the appeal of the product. So, if there is ambiguity/confusion regarding what OFBiz delivers visavis requirements maybe we should make that clear first. That way we create a unified and clear message to any (potential) adopter, and have less confusing questions in the user ml. Food for thought: Is OFBiz a hammer, or something like a Leatherman multi-tool? > Extend ./ant create-tenant to be able to differentiate between OLTP and OLAP > rdbms > -- > > Key: OFBIZ-6087 > URL: https://issues.apache.org/jira/browse/OFBIZ-6087 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Labels: persistence > > Currently the ./ant create-tenant only allows to set a single type and > access/location details (host, port, userid and password) for the OLTP and > OLAP rdbms. > It should be possible to set different types and access/location details for > the rdbms variants. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393330#comment-15393330 ] Pierre Smits edited comment on OFBIZ-7808 at 7/26/16 8:53 AM: -- For the createComponent task we already had a JIRA issue: OFBIZ-7773, which could be reworded and reopened. For the createTenant equivalent in Ant we had: * tenantId * tenantName * domainName * data-readers * db-IP * db-User * db-Password The 'tenantName' could be regarded as optional, but it set in the Tenant entity in the master database The 'domainName' is optional, also set in a entity in the master database The data-readers is not optional, without the proper datasets one would not be able to access the tenant instantiation. And loading all should not be regarded as an option in a production environment. The db-IP, db-User and db-Password are not optional In our environment we have extended the list with a few more parameters, one of which being related to OFBIZ-6087, to feed into a few more Ant tasks. was (Author: pfm.smits): For the createComponent task we already had a JIRA issue: OFBIZ-7773, which could be reworded and reopenend. For the createTenant equivalent in Ant we had: * tenantId * tenantName * domainName * data-readers * db-IP * db-User * db-Password The 'tenantName' could be regarded as optional, but it set in the Tenant entity in the master database The 'domainName' is optional, also set in a entity in the master database The data-readers is not optional, without the proper datasets one would not be able to access the tenant instantiation. And loading all should not be regarded as an option in a production environment. The db-IP, db-User and db-Password are not optional In our environment we have extended the list with a few more parameters, one of which being related to OFBIZ-6087, to feed into a few more Ant tasks. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379608#comment-15379608 ] Pierre Smits edited comment on OFBIZ-7808 at 7/26/16 8:50 AM: -- It seems, you are going for the 'multiple birds with one stone' approach. Though that easily could result in into a disentanglement down the line, as createComponent task to the dev side of the devops spectrum, and the createTenant (and dependents) and createAdminUserlogin task hinges more to the ops side. But I have no problems with you tackling this. ;) was (Author: pfm.smits): It seems, you are going for the 'multiple birds with one stone' approach. Though that easily could result in into a disentanglement down the line, as createCreate task to the dev side of the devops spectrum, and the createTenant (and dependents) and createAdminUserlogin task hinges more to the ops side. But I have no problems with you tackling this. ;) > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393385#comment-15393385 ] Pierre Smits commented on OFBIZ-7808: - re *the dpIp, dpUser and dbPassword are only mandatory if you are switching to a non-embedded database (derby default) which means MySQL, Postgres, Oracle* Derby is *not* advised as a solution for production environments. Furthermore, the settings in entity-engine are more 'master' db specific, than tenant specific. An adopter can deviate form those settings (in entityengine.xml) for each tenant. And in a large enough multi-tenant setup will. Differentiate between RDBMSes (e.g. different cluster) for master and tenant, to ensure maximisation of disentanglement (GRC related risk mitigation), but also regarding differentiation between groups of tenants (different RDBMS clusters) to maximise performance. re *I don't see why the data readers should be considered mandatory. They are optional in "ofbiz --load-data", they are ommitted in loadDefault, they are optional on loadTenant and they are optional in many such contexts* When the data-readers parameters is not mandatory in the createTenant *convenience* task, it might be so that no parameter is provided. Leading to the gradlew 'ofbiz --load-data' task invoking the loading of all datasets (as per definition in entityengine.xml) for all components. Including those that are specific to other tenants (see OFBIZ-6065 and OFBIZ-6066). For you, [~taher], this might be a an academic question, but trust me on this. As I am a *real* user of the OFBiz solution in a multi-tenant setup. And I know a bit about risk mitigation and performance maximisation in relation to multi-clustered OFBIZ, multi-tenant OFBiz and multi-cluster/multi-node RDBMS setups. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7808) Add Gradle Interactive tasks
[ https://issues.apache.org/jira/browse/OFBIZ-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393330#comment-15393330 ] Pierre Smits commented on OFBIZ-7808: - For the createComponent task we already had a JIRA issue: OFBIZ-7773, which could be reworded and reopenend. For the createTenant equivalent in Ant we had: * tenantId * tenantName * domainName * data-readers * db-IP * db-User * db-Password The 'tenantName' could be regarded as optional, but it set in the Tenant entity in the master database The 'domainName' is optional, also set in a entity in the master database The data-readers is not optional, without the proper datasets one would not be able to access the tenant instantiation. And loading all should not be regarded as an option in a production environment. The db-IP, db-User and db-Password are not optional In our environment we have extended the list with a few more parameters, one of which being related to OFBIZ-6087, to feed into a few more Ant tasks. > Add Gradle Interactive tasks > > > Key: OFBIZ-7808 > URL: https://issues.apache.org/jira/browse/OFBIZ-7808 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: Upcoming Branch > > > As explained in OFBIZ-7772 and OFBIZ-7773 we want to test the possiblity to > add Gradle Interactive tasks using > https://github.com/tkruse/gradle-groovysh-plugin > The idea is to have a good general solution to allow users to not feel a > funtional regression with the 3 interactive tasks we had before, namely > create-component > create-admin-user-login > create-tenant and all tasks it depends on -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7754) The big problem when load seed.
[ 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 see whether [~h.bak...@antwebsystems.com] can find himself in this compromise. I have seen some other SystemPropertyData.xml files that are also loaded at load-seed moment. These should move too. > The big problem when load seed. > --- > > Key: OFBIZ-7754 > URL: https://issues.apache.org/jira/browse/OFBIZ-7754 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Kongrath Suankaewmanee >Assignee: Pierre Smits > Attachments: OFBIZ-7754.patch > > > Hi All, > Regarding, [OFBIZ-7112|https://issues.apache.org/jira/browse/OFBIZ-7112] > That's good for who start on use the ofbiz with initial setup, but not for > the site that already online and has to update the OFBiz core. Because when > has update OFBiz core they will use command load-seed for update. > The problem is if we use load-seed mean the configuration data that's already > exists will be replaced by the data from this file, > *CommonSystemPropertyData.xml* > So, for my suggestion should change the reader from *seed* to *seed-initial* > or remove systemPropertyValue from the data file. > Thank you, > Kongrath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7925) Have ListGlAccountsReport open in a new window
[ https://issues.apache.org/jira/browse/OFBIZ-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7925: Attachment: OFBIZ-7925-GlobalGlAccountsScreens.xml.patch This patch addresses the issue. > Have ListGlAccountsReport open in a new window > -- > > Key: OFBIZ-7925 > URL: https://issues.apache.org/jira/browse/OFBIZ-7925 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7925-GlobalGlAccountsScreens.xml.patch > > > The ListGlAccountsReport is used to: > * generate a PDF file > * generate an xml export page > of the Gl Accounts in globalGLSettings. Both screens don't open in a new > window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7925) Have ListGlAccountsReport open in a new window
Pierre Smits created OFBIZ-7925: --- Summary: Have ListGlAccountsReport open in a new window Key: OFBIZ-7925 URL: https://issues.apache.org/jira/browse/OFBIZ-7925 Project: OFBiz Issue Type: Improvement Reporter: Pierre Smits Assignee: Pierre Smits The ListGlAccountsReport is used to: * generate a PDF file * generate an xml export page of the Gl Accounts in globalGLSettings. Both screens don't open in a new window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7920) Have TransactionTotalsPdf.pdf show the internal company show it has been generated for.
[ https://issues.apache.org/jira/browse/OFBIZ-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389469#comment-15389469 ] Pierre Smits commented on OFBIZ-7920: - Hi [~jacques.le.roux], I will go through all the other widgets etc. where the SimpleDecorator is applied and see what the impact of the patch is. > Have TransactionTotalsPdf.pdf show the internal company show it has been > generated for. > --- > > Key: OFBIZ-7920 > URL: https://issues.apache.org/jira/browse/OFBIZ-7920 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-7920-common.patch > > > The TransactionTotalsPdf.pdf currently doesn't show the name of the company > it has been generated for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7893) Rename generated *ofbiz-gradle.jar* to *ofbiz.jar*
[ https://issues.apache.org/jira/browse/OFBIZ-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389407#comment-15389407 ] Pierre Smits commented on OFBIZ-7893: - Hi [~taher], That is unfortunate to read. Could you provide a log excerpt so that I can assess the situation? > Rename generated *ofbiz-gradle.jar* to *ofbiz.jar* > -- > > Key: OFBIZ-7893 > URL: https://issues.apache.org/jira/browse/OFBIZ-7893 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7893-build.gradle-v2.patch, > OFBIZ-7893-build.gradle.patch > > > With the implementation of the Gradle build methodology the name of the OFBiz > executable changed from *ofbiz.jar* to *ofbiz-gradle.jar*. > In order to keep consistency with older releases this should be changed so > that the old name is back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7893) Rename generated *ofbiz-gradle.jar* to *ofbiz.jar*
[ https://issues.apache.org/jira/browse/OFBIZ-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389150#comment-15389150 ] Pierre Smits commented on OFBIZ-7893: - Hi [~taher], No, it is not just applicable for my hosting enviroments. I is intended to keep future releases in line with what our current adopters already have and know. And that not only relates to deployment, but it also applies to development. When a developer has multiple checkouts, he should - under the standard convention (of Gradle, as implemented by you) switch for each checkout to a different executor. This patch alleviates that. It creates consistency in multiple ways, that eases work down the line. > Rename generated *ofbiz-gradle.jar* to *ofbiz.jar* > -- > > Key: OFBIZ-7893 > URL: https://issues.apache.org/jira/browse/OFBIZ-7893 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7893-build.gradle-v2.patch, > OFBIZ-7893-build.gradle.patch > > > With the implementation of the Gradle build methodology the name of the OFBiz > executable changed from *ofbiz.jar* to *ofbiz-gradle.jar*. > In order to keep consistency with older releases this should be changed so > that the old name is back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7893) Rename generated *ofbiz-gradle.jar* to *ofbiz.jar*
[ https://issues.apache.org/jira/browse/OFBIZ-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389150#comment-15389150 ] Pierre Smits edited comment on OFBIZ-7893 at 7/22/16 8:21 AM: -- Hi [~taher], No, it is not just applicable for my hosting environments. I is intended to keep future releases in line with what our current adopters already have and know. And that not only relates to deployment, but it also applies to development. When a developer has multiple checkouts, he should - under the standard convention (of Gradle, as implemented by you) switch for each checkout to a different executor. This patch alleviates that. It creates consistency in multiple ways, that eases work down the line. was (Author: pfm.smits): Hi [~taher], No, it is not just applicable for my hosting enviroments. I is intended to keep future releases in line with what our current adopters already have and know. And that not only relates to deployment, but it also applies to development. When a developer has multiple checkouts, he should - under the standard convention (of Gradle, as implemented by you) switch for each checkout to a different executor. This patch alleviates that. It creates consistency in multiple ways, that eases work down the line. > Rename generated *ofbiz-gradle.jar* to *ofbiz.jar* > -- > > Key: OFBIZ-7893 > URL: https://issues.apache.org/jira/browse/OFBIZ-7893 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7893-build.gradle-v2.patch, > OFBIZ-7893-build.gradle.patch > > > With the implementation of the Gradle build methodology the name of the OFBiz > executable changed from *ofbiz.jar* to *ofbiz-gradle.jar*. > In order to keep consistency with older releases this should be changed so > that the old name is back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7893) Rename generated *ofbiz-gradle.jar* to *ofbiz.jar*
[ https://issues.apache.org/jira/browse/OFBIZ-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7893: Attachment: OFBIZ-7893-build.gradle-v2.patch This new patch addresses the issue. It keeps in line with conventions used in older releases. It also addresses OFBIZ-7783, with respect of not getting external libs in the project folder It also addresses OFBIZ-7796, with respect of not being able to run OFBiz as a service when using Debian/Ubuntu Within this, it also addresses * the JAVA_BINARY setting as that was still reflecting Java version 1.4.2 * the OFBIZ_HOME setting as it is customary to not have this set to the home directory of a user > Rename generated *ofbiz-gradle.jar* to *ofbiz.jar* > -- > > Key: OFBIZ-7893 > URL: https://issues.apache.org/jira/browse/OFBIZ-7893 > Project: OFBiz > Issue Type: Sub-task >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7893-build.gradle-v2.patch, > OFBIZ-7893-build.gradle.patch > > > With the implementation of the Gradle build methodology the name of the OFBiz > executable changed from *ofbiz.jar* to *ofbiz-gradle.jar*. > In order to keep consistency with older releases this should be changed so > that the old name is back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7922) Pagination through marketing campains is broken
[ https://issues.apache.org/jira/browse/OFBIZ-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389098#comment-15389098 ] Pierre Smits commented on OFBIZ-7922: - Well spotted, [~mbrohl]! > Pagination through marketing campains is broken > --- > > Key: OFBIZ-7922 > URL: https://issues.apache.org/jira/browse/OFBIZ-7922 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Michael Brohl > Attachments: MarketingCampaign.xml, OFBIZ-7922.patch > > > Go to /marketing/control/FindMarketingCampaign and select another view size > or paginate - an error occurs because the forms target is > listMarketingCampain which does not exist in the controller. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7922) Pagination through marketing campains is broken
[ https://issues.apache.org/jira/browse/OFBIZ-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389095#comment-15389095 ] Pierre Smits commented on OFBIZ-7922: - I tested the patch as well, and it works for me too. Hi [~Florian M], What about putting the data (with a slight modification) into MarketingDemoData.xml? That way it can be used also for testing purposes. > Pagination through marketing campains is broken > --- > > Key: OFBIZ-7922 > URL: https://issues.apache.org/jira/browse/OFBIZ-7922 > Project: OFBiz > Issue Type: Bug > Components: marketing >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Michael Brohl > Attachments: MarketingCampaign.xml, OFBIZ-7922.patch > > > Go to /marketing/control/FindMarketingCampaign and select another view size > or paginate - an error occurs because the forms target is > listMarketingCampain which does not exist in the controller. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
[ https://issues.apache.org/jira/browse/OFBIZ-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7921: Attachment: OFBIZ-7921-bizznesstime.patch This patch addresses the issue. > Incorporate the readme for the bizznesstime theme > - > > Key: OFBIZ-7921 > URL: https://issues.apache.org/jira/browse/OFBIZ-7921 > Project: OFBiz > Issue Type: Sub-task > Components: themes >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Fix For: Upcoming Branch > > Attachments: OFBIZ-7921-bizznesstime.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7921) Incorporate the readme for the bizznesstime theme
Pierre Smits created OFBIZ-7921: --- Summary: Incorporate the readme for the bizznesstime theme Key: OFBIZ-7921 URL: https://issues.apache.org/jira/browse/OFBIZ-7921 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-7906) Have a gradle build file for the cmssite component
[ https://issues.apache.org/jira/browse/OFBIZ-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-7906. --- Resolution: Not A Problem Closing this issue as the set of specific 3rd party libraries appear not to be used by the current functionality for cmssite as they were intended for a potential docbook based solution for web help. If need be, this issue can be reopened at a later moment in time. > Have a gradle build file for the cmssite component > -- > > Key: OFBIZ-7906 > URL: https://issues.apache.org/jira/browse/OFBIZ-7906 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/cmssite >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-7906-cmssite.patch > > > The cmssite component uses a specific set of external libraries. These were > removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387487#comment-15387487 ] Pierre Smits commented on OFBIZ-7910: - I wonder what it is that you consider to be missing in the patch. It is based on the build.gradle file in the lucene component. That contains nothing else than just the construct for downloading the required external libraries. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387472#comment-15387472 ] Pierre Smits commented on OFBIZ-7910: - Hi [~taher], It seems you are jumping the gun.. The discusion whether the project will have a plugin management solutions is still ongoing in the dev ml. Before there is an acceptable proof of concept, there will be a lot of water under the bridge. Furthermore, as already explained before and elsewhere, the createComponent generates a skeleton of a standard component, that enables a jumpstart for developers. If that new component needs specific external libraries, it will need a build.gradle file in the component. Similar as we have in current specialpurpose component lucene. And that is what the patch provides as part of that skeleton, as a convenience to the developer. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387456#comment-15387456 ] Pierre Smits commented on OFBIZ-7910: - I suggest you discuss this in the existing thread in the dev ml. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387269#comment-15387269 ] Pierre Smits edited comment on OFBIZ-4274 at 7/21/16 6:57 AM: -- Hi [~vijayparamakusum] and [~e...@brainfood.com], [~jacques.le.roux] and I discussed the other day how a REST over HTTP solution would bring the OFBiz services forward into current day conventions. I believe a solutions similar like how we do SOAP services would be the most generic one. And if that could be combined with the OpenAPI standards (e.g. through swagger.io libraries) that would be even more in line with what is believed the goal these days. was (Author: pfm.smits): Hi [~vijayparamakusum] and [~e...@brainfood.com], [~jacques.le.roux] and I discussed the other day how a REST over HTTP solution would bring the OFBiz services forward into current day conventions. I believe a solutions similar like how we do SOAP servers would be the most generic one. And if that could be combined with the OpenAPI standards (e.g. through swagger.io libraries) that would be even more in line with what is believed the goal these days. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387269#comment-15387269 ] Pierre Smits commented on OFBIZ-4274: - Hi [~vijayparamakusum] and [~e...@brainfood.com], [~jacques.le.roux] and I discussed the other day how a REST over HTTP solution would bring the OFBiz services forward into current day conventions. I believe a solutions similar like how we do SOAP servers would be the most generic one. And if that could be combined with the OpenAPI standards (e.g. through swagger.io libraries) that would be even more in line with what is believed the goal these days. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386488#comment-15386488 ] Pierre Smits commented on OFBIZ-4274: - Hi [~vijayparamakusum], Adrian regretfully passed away January 1st of this year. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7920) Have TransactionTotalsPdf.pdf show the internal company show it has been generated for.
[ https://issues.apache.org/jira/browse/OFBIZ-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-7920: --- Assignee: Pierre Smits > Have TransactionTotalsPdf.pdf show the internal company show it has been > generated for. > --- > > Key: OFBIZ-7920 > URL: https://issues.apache.org/jira/browse/OFBIZ-7920 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7920-common.patch > > > The TransactionTotalsPdf.pdf currently doesn't show the name of the company > it has been generated for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7920) Have TransactionTotalsPdf.pdf show the internal company show it has been generated for.
[ https://issues.apache.org/jira/browse/OFBIZ-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7920: Attachment: OFBIZ-7920-common.patch This patch addresses the issue. > Have TransactionTotalsPdf.pdf show the internal company show it has been > generated for. > --- > > Key: OFBIZ-7920 > URL: https://issues.apache.org/jira/browse/OFBIZ-7920 > Project: OFBiz > Issue Type: Improvement >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7920-common.patch > > > The TransactionTotalsPdf.pdf currently doesn't show the name of the company > it has been generated for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7920) Have TransactionTotalsPdf.pdf show the internal company show it has been generated for.
Pierre Smits created OFBIZ-7920: --- Summary: Have TransactionTotalsPdf.pdf show the internal company show it has been generated for. Key: OFBIZ-7920 URL: https://issues.apache.org/jira/browse/OFBIZ-7920 Project: OFBiz Issue Type: Improvement Reporter: Pierre Smits The TransactionTotalsPdf.pdf currently doesn't show the name of the company it has been generated for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7919) Removal of old OFBiz images from images folder
[ https://issues.apache.org/jira/browse/OFBIZ-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386120#comment-15386120 ] Pierre Smits commented on OFBIZ-7919: - The images are: * ofbiz_powered.gif * ofbizOld.ico > Removal of old OFBiz images from images folder > -- > > Key: OFBIZ-7919 > URL: https://issues.apache.org/jira/browse/OFBIZ-7919 > Project: OFBiz > Issue Type: Improvement > Components: framework >Reporter: Pierre Smits >Assignee: Pierre Smits > > There are a few OFBiz images left behind in the image folder in the image > component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7919) Removal of old OFBiz images from images folder
Pierre Smits created OFBIZ-7919: --- Summary: Removal of old OFBiz images from images folder Key: OFBIZ-7919 URL: https://issues.apache.org/jira/browse/OFBIZ-7919 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Pierre Smits Assignee: Pierre Smits There are a few OFBiz images left behind in the image folder in the image component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7918) Improve Dutch labels regarding accounting reports
[ https://issues.apache.org/jira/browse/OFBIZ-7918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7918: Attachment: OFBIZ-7918-AccountingUiLabels.xml.patch This patch addresses the issue. > Improve Dutch labels regarding accounting reports > - > > Key: OFBIZ-7918 > URL: https://issues.apache.org/jira/browse/OFBIZ-7918 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7918-AccountingUiLabels.xml.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7907) Move jsgantt files from images to projectmgr component
[ https://issues.apache.org/jira/browse/OFBIZ-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385919#comment-15385919 ] Pierre Smits commented on OFBIZ-7907: - Hi [~jacques.le.roux], I suggest to start the discussion in the dev ml, and not dilute the issue. > Move jsgantt files from images to projectmgr component > -- > > Key: OFBIZ-7907 > URL: https://issues.apache.org/jira/browse/OFBIZ-7907 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/projectmgr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Jacques Le Roux > Attachments: OFBIZ-7907-jsgantt.patch > > > Currently the jsgantt files (css and js) are only used by the projectmgr > component, but the files are included in the image component in the framework > stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7918) Improve Dutch labels regarding accounting reports
Pierre Smits created OFBIZ-7918: --- Summary: Improve Dutch labels regarding accounting reports Key: OFBIZ-7918 URL: https://issues.apache.org/jira/browse/OFBIZ-7918 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7906) Have a gradle build file for the cmssite component
[ https://issues.apache.org/jira/browse/OFBIZ-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385524#comment-15385524 ] Pierre Smits commented on OFBIZ-7906: - I suggest you follow up in a separate thread/issue. But it shouldn't block implementation of the patch associated attached to this issue. > Have a gradle build file for the cmssite component > -- > > Key: OFBIZ-7906 > URL: https://issues.apache.org/jira/browse/OFBIZ-7906 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/cmssite >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-7906-cmssite.patch > > > The cmssite component uses a specific set of external libraries. These were > removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7906) Have a gradle build file for the cmssite component
[ https://issues.apache.org/jira/browse/OFBIZ-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385476#comment-15385476 ] Pierre Smits commented on OFBIZ-7906: - As for the OFBIZ-6644 issue: I can think of a (few) reason why OFBIZ-6644 hasn't taken of: * the assigned contributor with privileges has new pet projects * PMC didn't enable the contributor involved to do more, because they didn't/don't *like* him (enough). Leading to him losing interest. > Have a gradle build file for the cmssite component > -- > > Key: OFBIZ-7906 > URL: https://issues.apache.org/jira/browse/OFBIZ-7906 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/cmssite >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-7906-cmssite.patch > > > The cmssite component uses a specific set of external libraries. These were > removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7906) Have a gradle build file for the cmssite component
[ https://issues.apache.org/jira/browse/OFBIZ-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385472#comment-15385472 ] Pierre Smits commented on OFBIZ-7906: - Hi [~jacques.le.roux], This issue is about keeping the cmssite in releases as some feel it shouldn't be, because others couldn't find appropriate 3rd party libraries to be referenced in the component specific download definitions. > Have a gradle build file for the cmssite component > -- > > Key: OFBIZ-7906 > URL: https://issues.apache.org/jira/browse/OFBIZ-7906 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/cmssite >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-7906-cmssite.patch > > > The cmssite component uses a specific set of external libraries. These were > removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7906) Have a gradle build file for the cmssite component
[ https://issues.apache.org/jira/browse/OFBIZ-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7906: Priority: Blocker (was: Major) > Have a gradle build file for the cmssite component > -- > > Key: OFBIZ-7906 > URL: https://issues.apache.org/jira/browse/OFBIZ-7906 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/cmssite >Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Blocker > Attachments: OFBIZ-7906-cmssite.patch > > > The cmssite component uses a specific set of external libraries. These were > removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
[ https://issues.apache.org/jira/browse/OFBIZ-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7910: Attachment: OFBIZ-7910-Resources-build.gradle.patch This patch addresses the issue. > Improve component template(s) to work with the Gradle solution > -- > > Key: OFBIZ-7910 > URL: https://issues.apache.org/jira/browse/OFBIZ-7910 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7910-Resources-build.gradle.patch > > > Currently the component generated with the createComponent task doesn't have > the means to work with the Gradle build solution visavis dependency > management. > The reason for this is that no build.gradle template exists that need to be > copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7910) Improve component template(s) to work with the Gradle solution
Pierre Smits created OFBIZ-7910: --- Summary: Improve component template(s) to work with the Gradle solution Key: OFBIZ-7910 URL: https://issues.apache.org/jira/browse/OFBIZ-7910 Project: OFBiz Issue Type: Sub-task Components: framework Reporter: Pierre Smits Assignee: Pierre Smits Currently the component generated with the createComponent task doesn't have the means to work with the Gradle build solution visavis dependency management. The reason for this is that no build.gradle template exists that need to be copied into the new component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7783) External library files are not in the OFBiz folder structure.
[
https://issues.apache.org/jira/browse/OFBIZ-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384413#comment-15384413
]
Pierre Smits commented on OFBIZ-7783:
-
The following piece of code added to the build.gradle file will add the 3rd
party libraries to the lib folder in the project.
{code}
task copyToLib(type: Copy) {
into "$rootDir/lib"
from configurations.runtime
}
{code}
> External library files are not in the OFBiz folder structure.
> -
>
> Key: OFBIZ-7783
> URL: https://issues.apache.org/jira/browse/OFBIZ-7783
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Blocker
>
> With the implementation of the external library download feature of
> gradle/gradlew, the external libraries (jar files) are not in the folder
> structure any more.
> They should reside there, like before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7907) Move jsgantt files from images to projectmgr component
[ https://issues.apache.org/jira/browse/OFBIZ-7907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7907: Attachment: OFBIZ-7907-jsgantt.patch This patch addresses the issue. This patch also moves the projectmgr.css file from the static subfolder to the - generally accepted - image subfolder and deletes the - now empty - static subfolder. > Move jsgantt files from images to projectmgr component > -- > > Key: OFBIZ-7907 > URL: https://issues.apache.org/jira/browse/OFBIZ-7907 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/projectmgr >Affects Versions: Trunk >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7907-jsgantt.patch > > > Currently the jsgantt files (css and js) are only used by the projectmgr > component, but the files are included in the image component in the framework > stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7907) Move jsgantt files from images to projectmgr component
Pierre Smits created OFBIZ-7907: --- Summary: Move jsgantt files from images to projectmgr component Key: OFBIZ-7907 URL: https://issues.apache.org/jira/browse/OFBIZ-7907 Project: OFBiz Issue Type: Improvement Components: framework, specialpurpose/projectmgr Affects Versions: Trunk Reporter: Pierre Smits Assignee: Pierre Smits Currently the jsgantt files (css and js) are only used by the projectmgr component, but the files are included in the image component in the framework stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7906) Have a gradle build file for the cmssite component
[ https://issues.apache.org/jira/browse/OFBIZ-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-7906: Attachment: OFBIZ-7906-cmssite.patch This patch addresses the issue. > Have a gradle build file for the cmssite component > -- > > Key: OFBIZ-7906 > URL: https://issues.apache.org/jira/browse/OFBIZ-7906 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/cmssite >Reporter: Pierre Smits >Assignee: Pierre Smits > Attachments: OFBIZ-7906-cmssite.patch > > > The cmssite component uses a specific set of external libraries. These were > removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7906) Have a gradle build file for the cmssite component
Pierre Smits created OFBIZ-7906: --- Summary: Have a gradle build file for the cmssite component Key: OFBIZ-7906 URL: https://issues.apache.org/jira/browse/OFBIZ-7906 Project: OFBiz Issue Type: Bug Components: specialpurpose/cmssite Reporter: Pierre Smits Assignee: Pierre Smits The cmssite component uses a specific set of external libraries. These were removed as a result of the migration from Ant to Gradle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
