[jira] [Commented] (OFBIZ-12938) BlueLight theme error when launching OFBiz
[
https://issues.apache.org/jira/browse/OFBIZ-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825841#comment-17825841
]
Pierre Smits commented on OFBIZ-12938:
--
Hi Jacques,
Analysis of the error log shows a detail you neglected to show in your error
statement in order to get to the root-cause of this issue:
{code:java}
FTL stack trace ("~" means nesting-related):
- Failed at: ${screens.render(thisAppShortcutScree... [in template
"component://bluelight/template/AppBarOpen.ftl" at line 61, column 31] {code}
> BlueLight theme error when launching OFBiz
> --
>
> Key: OFBIZ-12938
> URL: https://issues.apache.org/jira/browse/OFBIZ-12938
> Project: OFBiz
> Issue Type: Bug
> Components: theme/bluelight
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
>
> We have this error for BlueLight theme. HumanResShortcutAppBar and
> AccountingShortcutAppBar are concerned. Tomahawk (derived from BlueLight)
> seems OK.
>
> {noformat}
> 2024-03-12 14:39:40,921 |jsse-nio-8443-exec-7 |UtilXml
> |W| [UtilXml.readXmlDocument] URL was null, doing nothing
> 2024-03-12 14:39:40,922 |jsse-nio-8443-exec-7 |ModelScreenWidget
> |E| Error rendering included menu named [HumanResShortcutAppBar] at location
> []:
> java.lang.IllegalArgumentException: Could not find menu file in location []
> at
> org.apache.ofbiz.widget.model.MenuFactory.getMenuFromLocation(MenuFactory.java:117)
> ~[main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Menu.getModelMenu(ModelScreenWidget.java:1644)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Menu.renderWidgetString(ModelScreenWidget.java:1635)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$DecoratorSection.renderWidgetString(ModelScreenWidget.java:947)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$SectionsRenderer.render(ModelScreenWidget.java:142)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$DecoratorSectionInclude.renderWidgetString(ModelScreenWidget.java:986)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:481)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:297)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:481)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:481)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:297)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:158)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ScreenFactory.renderReferencedScreen(ScreenFactory.java:214)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$IncludeScreen.renderWidgetString(ModelScreenWidget.java:819)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:109)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:297)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:158)
> [main/:?]
> at
> org.apache.ofbiz.widget.model.ScreenFactory.renderReferenced
[jira] [Commented] (OFBIZ-12937) Prevent possible file race conditions with SecuredUpload class
[ https://issues.apache.org/jira/browse/OFBIZ-12937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825546#comment-17825546 ] Pierre Smits commented on OFBIZ-12937: -- Hi [~jleroux] IMO, these same issues in ImageManagementServices and ProductServices should not exist, but the functions/servics there should call the functions in DataServices in the framework stack. > Prevent possible file race conditions with SecuredUpload class > -- > > Key: OFBIZ-12937 > URL: https://issues.apache.org/jira/browse/OFBIZ-12937 > Project: OFBiz > Issue Type: Bug > Components: framework/security >Affects Versions: 18.12.13 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > While trying to upload PDF files I found a possible file race conditions in > DataServices::createFileMethod and DataServices::updateFileMethod > The same could exist in several places in ImageManagementServices and > ProductServices classes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12929) OFBiz doesn't allow upload.
[
https://issues.apache.org/jira/browse/OFBIZ-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825106#comment-17825106
]
Pierre Smits commented on OFBIZ-12929:
--
Hi [~jleroux],
Like I stated in an earlier posting:
{code:java}
git -c color.branch=false -c color.diff=false -c color.status=false -c
diff.mnemonicprefix=false -c core.quotepath=false -c
credential.helper=sourcetree apply -v --reject -p 1
/Users/mine/Downloads/OFBIZ-12926.patch
error: corrupt patch at line 77
Completed with errors, see above {code}
git apply gives an error.
> OFBiz doesn't allow upload.
> ---
>
> Key: OFBIZ-12929
> URL: https://issues.apache.org/jira/browse/OFBIZ-12929
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
>Affects Versions: Upcoming Branch
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: Screenshot 2024-03-05 at 09.18.27.png
>
>
> In demo trunk and local with demo data in an existing agreement, no files of
> following type can be uploaded:
> * pdf
> * xlsx
> * pptx
> * docx
> in screen a message as per attached image is shown, in the console following
> is shown:
> {code:java}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |SecuredUpload
> |E| For security reason lines over 1 are not allowed
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceUtil
> |E| {errorMessage=For security reason only valid files of supported image
> formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text files with safe
> names (only Alpha-Numeric characters, hyphen, underscore and spaces, only 1
> dot, name and extension not empty) and contents are accepted.,
> responseMessage=error}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceDispatcher
> |E| Error in Service [createAnonFile]: For security reason only valid files
> of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text
> files with safe names (only Alpha-Numeric characters, hyphen, underscore and
> spaces, only 1 dot, name and extension not empty) and contents are accepted.
> 2024-03-05 09:22:57,839 |jsse-nio-8443-exec-4 |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Error in Service [createAnonFile]: For security reason
> only valid files of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF,
> and ZIP or text files with safe names (only Alpha-Numeric characters, hyphen,
> underscore and spaces, only 1 dot, name and extension not empty) and contents
> are accepted.
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:372)
> [main/:?]
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:306)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:577)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244)
> [main/:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93)
> [main/:?]
> at org.apache.ofbiz.service.LocalDispatcher$runSync$0.call(Unknown
> Source) [main/:?]
> at
> org.apache.ofbiz.service.engine.GroovyBaseScript.runService(GroovyBaseScript.groovy:74)
> [main/:?]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:?]
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> ~[?:?]
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?]
> at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
> at
> org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:48)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:57)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:62)
> [gro
[jira] [Commented] (OFBIZ-12929) OFBiz doesn't allow upload.
[
https://issues.apache.org/jira/browse/OFBIZ-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825065#comment-17825065
]
Pierre Smits commented on OFBIZ-12929:
--
Hey [~jleroux]
{noformat}
Also I guess you don't cross any issue uploadging with stable demo?{noformat}
Maybe I have overlooked something, but was there an issue reporting regarding
this and any of the released versions?
> OFBiz doesn't allow upload.
> ---
>
> Key: OFBIZ-12929
> URL: https://issues.apache.org/jira/browse/OFBIZ-12929
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
>Affects Versions: Upcoming Branch
>Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: Screenshot 2024-03-05 at 09.18.27.png
>
>
> In demo trunk and local with demo data in an existing agreement, no files of
> following type can be uploaded:
> * pdf
> * xlsx
> * pptx
> * docx
> in screen a message as per attached image is shown, in the console following
> is shown:
> {code:java}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |SecuredUpload
> |E| For security reason lines over 1 are not allowed
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceUtil
> |E| {errorMessage=For security reason only valid files of supported image
> formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text files with safe
> names (only Alpha-Numeric characters, hyphen, underscore and spaces, only 1
> dot, name and extension not empty) and contents are accepted.,
> responseMessage=error}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceDispatcher
> |E| Error in Service [createAnonFile]: For security reason only valid files
> of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text
> files with safe names (only Alpha-Numeric characters, hyphen, underscore and
> spaces, only 1 dot, name and extension not empty) and contents are accepted.
> 2024-03-05 09:22:57,839 |jsse-nio-8443-exec-4 |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Error in Service [createAnonFile]: For security reason
> only valid files of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF,
> and ZIP or text files with safe names (only Alpha-Numeric characters, hyphen,
> underscore and spaces, only 1 dot, name and extension not empty) and contents
> are accepted.
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:372)
> [main/:?]
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:306)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:577)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244)
> [main/:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93)
> [main/:?]
> at org.apache.ofbiz.service.LocalDispatcher$runSync$0.call(Unknown
> Source) [main/:?]
> at
> org.apache.ofbiz.service.engine.GroovyBaseScript.runService(GroovyBaseScript.groovy:74)
> [main/:?]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:?]
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> ~[?:?]
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?]
> at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
> at
> org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:48)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:57)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:62)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(A
[jira] [Commented] (OFBIZ-12929) OFBiz doesn't allow upload.
[
https://issues.apache.org/jira/browse/OFBIZ-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825032#comment-17825032
]
Pierre Smits commented on OFBIZ-12929:
--
Hi [~jleroux] ,
I downloaded the patch file and tried to incorporate it in latest from trunk.
However, I got following error:
{code:java}
git -c color.branch=false -c color.diff=false -c color.status=false -c
diff.mnemonicprefix=false -c core.quotepath=false -c
credential.helper=sourcetree apply -v --reject -p 1
/Users/mine/Downloads/OFBIZ-12926.patch
error: corrupt patch at line 77
Completed with errors, see above {code}
so I could not progress any further.
> OFBiz doesn't allow upload.
> ---
>
> Key: OFBIZ-12929
> URL: https://issues.apache.org/jira/browse/OFBIZ-12929
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
> Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: Screenshot 2024-03-05 at 09.18.27.png
>
>
> In demo trunk and local with demo data in an existing agreement, no files of
> following type can be uploaded:
> * pdf
> * xlsx
> * pptx
> * docx
> in screen a message as per attached image is shown, in the console following
> is shown:
> {code:java}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |SecuredUpload
> |E| For security reason lines over 1 are not allowed
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceUtil
> |E| {errorMessage=For security reason only valid files of supported image
> formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text files with safe
> names (only Alpha-Numeric characters, hyphen, underscore and spaces, only 1
> dot, name and extension not empty) and contents are accepted.,
> responseMessage=error}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceDispatcher
> |E| Error in Service [createAnonFile]: For security reason only valid files
> of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text
> files with safe names (only Alpha-Numeric characters, hyphen, underscore and
> spaces, only 1 dot, name and extension not empty) and contents are accepted.
> 2024-03-05 09:22:57,839 |jsse-nio-8443-exec-4 |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Error in Service [createAnonFile]: For security reason
> only valid files of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF,
> and ZIP or text files with safe names (only Alpha-Numeric characters, hyphen,
> underscore and spaces, only 1 dot, name and extension not empty) and contents
> are accepted.
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:372)
> [main/:?]
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:306)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:577)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244)
> [main/:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93)
> [main/:?]
> at org.apache.ofbiz.service.LocalDispatcher$runSync$0.call(Unknown
> Source) [main/:?]
> at
> org.apache.ofbiz.service.engine.GroovyBaseScript.runService(GroovyBaseScript.groovy:74)
> [main/:?]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:?]
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> ~[?:?]
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?]
> at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
> at
> org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:48)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:57)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(Pogo
[jira] [Commented] (OFBIZ-12930) Expose demo-site logs through Apache HTTP Server
[ https://issues.apache.org/jira/browse/OFBIZ-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823773#comment-17823773 ] Pierre Smits commented on OFBIZ-12930: -- Is it worth the effort? We provide this feature to address issues we experience while performing activities via the browser in the OFBiz applications. Same as users would do with their implementations. But These log files are available locally too. Developers (and even members of the devops teams of those who have implemented OFBiz So there should be ample means available to report on issues. > Expose demo-site logs through Apache HTTP Server > > > Key: OFBIZ-12930 > URL: https://issues.apache.org/jira/browse/OFBIZ-12930 > Project: OFBiz > Issue Type: Task > Components: Demo >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > Logs from the project's demo sites are not understood to contain any > sensitive information. If this. If this understanding if found to be > incorrect then this ticket will need to be reconsidered. > Exposing demo-site logs through Apache HTTP Server will make it easier for > users to investigate any issues that might arise during testing with the demo > sites. Users may be able to raise tickets with snippets of relevant log > messages that could help developers identify issues faster. > Configuration changes should be made to the demo-sites' Apache HTTP Server > configurations to add an Alias directive, "/logs", which references each demo > site's log directory. > The Apache HTTP Server configuration is managed by Puppet, so any changes > will need to be created using Puppet configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12930) Expose demo-site logs through Apache HTTP Server
[ https://issues.apache.org/jira/browse/OFBIZ-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823710#comment-17823710 ] Pierre Smits commented on OFBIZ-12930: -- HI [~danwatford], Could you make the puppet file available via this ticket so that I could have a look too? > Expose demo-site logs through Apache HTTP Server > > > Key: OFBIZ-12930 > URL: https://issues.apache.org/jira/browse/OFBIZ-12930 > Project: OFBiz > Issue Type: Task > Components: Demo >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > Logs from the project's demo sites are not understood to contain any > sensitive information. If this. If this understanding if found to be > incorrect then this ticket will need to be reconsidered. > Exposing demo-site logs through Apache HTTP Server will make it easier for > users to investigate any issues that might arise during testing with the demo > sites. Users may be able to raise tickets with snippets of relevant log > messages that could help developers identify issues faster. > Configuration changes should be made to the demo-sites' Apache HTTP Server > configurations to add an Alias directive, "/logs", which references each demo > site's log directory. > The Apache HTTP Server configuration is managed by Puppet, so any changes > will need to be created using Puppet configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12931) Add mainMenuLocation to web.xml
[ https://issues.apache.org/jira/browse/OFBIZ-12931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12931: - Summary: Add mainMenuLocation to web.xml (was: Manufacturing - Add mainMenuLocation to web.xml) > Add mainMenuLocation to web.xml > --- > > Key: OFBIZ-12931 > URL: https://issues.apache.org/jira/browse/OFBIZ-12931 > Project: OFBiz > Issue Type: Sub-task > Components: manufacturing > Reporter: Pierre Smits >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12931) Manufacturing - Add mainMenuLocation to web.xml
Pierre Smits created OFBIZ-12931: Summary: Manufacturing - Add mainMenuLocation to web.xml Key: OFBIZ-12931 URL: https://issues.apache.org/jira/browse/OFBIZ-12931 Project: OFBiz Issue Type: Sub-task Components: manufacturing Reporter: Pierre Smits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12922) HumanRes - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12922: - Parent: OFBIZ-12928 Issue Type: Sub-task (was: Improvement) > HumanRes - Move from hard-code menu location to parameterized > - > > Key: OFBIZ-12922 > URL: https://issues.apache.org/jira/browse/OFBIZ-12922 > Project: OFBiz > Issue Type: Sub-task > Components: humanres > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12918) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12918: - Parent: OFBIZ-12928 Issue Type: Sub-task (was: Improvement) > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12918 > URL: https://issues.apache.org/jira/browse/OFBIZ-12918 > Project: OFBiz > Issue Type: Sub-task > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12928) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12928: - Description: Customization is a key aspect of the OFBiz (Open For Business) platform, providing businesses with a robust and adaptable base to customize their enterprise software solutions according to their unique operational requirements. The *Menus.xml file of a component, essential for designing user interfaces that are both intuitive and tailored to the specific roles and tasks of its users, plays a significant role in this context, as referenced within screen widgets and Freemarker templates. However, as customizations and the project's source code evolve over time, the likelihood of encountering merge conflicts increases significantly, especially when attempting to incorporate customizations alongside ongoing bug fixes and enhancements from the project. To improve the appeal of OFbiz and the developer experience, it is recommended to shift from fixed menu locations to a parameterized approach in our components and plugins. This change would enable developers to more seamlessly incorporate a 'custom' menu, facilitating the integration of project updates. This is a parent ticket, intended to capture and catalog bite-size code changes over all components and plugins. was: Customization is a key aspect of the OFBiz (Open For Business) platform, providing businesses with a robust and adaptable base to customize their enterprise software solutions according to their unique operational requirements. The *Menus.xml file of a component, essential for designing user interfaces that are both intuitive and tailored to the specific roles and tasks of its users, plays a significant role in this context, as referenced within screen widgets and Freemarker templates. However, as customizations and the project's source code evolve over time, the likelihood of encountering merge conflicts increases significantly, especially when attempting to incorporate customizations alongside ongoing bug fixes and enhancements from the project. To improve the appeal of OFbiz and the developer experience, it is recommended to shift from fixed menu locations to a parameterized approach in our components and plugins. This change would enable developers to more seamlessly incorporate a 'custom' menu, facilitating the integration of project updates. > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12928 > URL: https://issues.apache.org/jira/browse/OFBIZ-12928 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. > This is a parent ticket, intended to capture and catalog bite-size code > changes over all components and plugins. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12928) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12928: - Summary: Move from hard-code menu location to parameterized (was: MFG - Move from hard-code menu location to parameterized) > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12928 > URL: https://issues.apache.org/jira/browse/OFBIZ-12928 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12930) Expose demo-site logs through Apache HTTP Server
[ https://issues.apache.org/jira/browse/OFBIZ-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823648#comment-17823648 ] Pierre Smits commented on OFBIZ-12930: -- Instead of exposing individual log files to a user via the http server used by the demo site, it is much easier to link to the log directory. With exposing that folder via an improvement in WEBTools, the route via INFRA can be circumvented. > Expose demo-site logs through Apache HTTP Server > > > Key: OFBIZ-12930 > URL: https://issues.apache.org/jira/browse/OFBIZ-12930 > Project: OFBiz > Issue Type: Task > Components: Demo >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > Logs from the project's demo sites are not understood to contain any > sensitive information. If this. If this understanding if found to be > incorrect then this ticket will need to be reconsidered. > Exposing demo-site logs through Apache HTTP Server will make it easier for > users to investigate any issues that might arise during testing with the demo > sites. Users may be able to raise tickets with snippets of relevant log > messages that could help developers identify issues faster. > Configuration changes should be made to the demo-sites' Apache HTTP Server > configurations to add an Alias directive, "/logs", which references each demo > site's log directory. > The Apache HTTP Server configuration is managed by Puppet, so any changes > will need to be created using Puppet configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12929) OFBiz doesn't allow upload.
[
https://issues.apache.org/jira/browse/OFBIZ-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823538#comment-17823538
]
Pierre Smits commented on OFBIZ-12929:
--
Is this, per chance, a result of recent changes related to OFBIZ-12920?
> OFBiz doesn't allow upload.
> ---
>
> Key: OFBIZ-12929
> URL: https://issues.apache.org/jira/browse/OFBIZ-12929
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
> Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Major
> Attachments: Screenshot 2024-03-05 at 09.18.27.png
>
>
> In demo trunk and local with demo data in an existing agreement, no files of
> following type can be uploaded:
> * pdf
> * xlsx
> * pptx
> * docx
> in screen a message as per attached image is shown, in the console following
> is shown:
> {code:java}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |SecuredUpload
> |E| For security reason lines over 1 are not allowed
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceUtil
> |E| {errorMessage=For security reason only valid files of supported image
> formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text files with safe
> names (only Alpha-Numeric characters, hyphen, underscore and spaces, only 1
> dot, name and extension not empty) and contents are accepted.,
> responseMessage=error}
> 2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceDispatcher
> |E| Error in Service [createAnonFile]: For security reason only valid files
> of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text
> files with safe names (only Alpha-Numeric characters, hyphen, underscore and
> spaces, only 1 dot, name and extension not empty) and contents are accepted.
> 2024-03-05 09:22:57,839 |jsse-nio-8443-exec-4 |TransactionUtil
> |W| Calling transaction setRollbackOnly; this stack trace shows where this is
> happening:
> java.lang.Exception: Error in Service [createAnonFile]: For security reason
> only valid files of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF,
> and ZIP or text files with safe names (only Alpha-Numeric characters, hyphen,
> underscore and spaces, only 1 dot, name and extension not empty) and contents
> are accepted.
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:372)
> [main/:?]
> at
> org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:306)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:577)
> [main/:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244)
> [main/:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93)
> [main/:?]
> at org.apache.ofbiz.service.LocalDispatcher$runSync$0.call(Unknown
> Source) [main/:?]
> at
> org.apache.ofbiz.service.engine.GroovyBaseScript.runService(GroovyBaseScript.groovy:74)
> [main/:?]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:?]
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> ~[?:?]
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?]
> at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
> at
> org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:48)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:57)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:62)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:194)
> [groovy-3.0.21.jar:3.0.21]
> at
> org.apache.ofbiz.service.engine.GroovyBaseScript.run(GroovyBaseScript.groovy:82)
> [main/:?]
> at
> org.apache.ofbiz.service.engine.GroovyBaseScript$r
[jira] [Created] (OFBIZ-12929) OFBiz doesn't allow upload.
Pierre Smits created OFBIZ-12929:
Summary: OFBiz doesn't allow upload.
Key: OFBIZ-12929
URL: https://issues.apache.org/jira/browse/OFBIZ-12929
Project: OFBiz
Issue Type: Bug
Components: accounting
Reporter: Pierre Smits
Attachments: Screenshot 2024-03-05 at 09.18.27.png
In demo trunk and local with demo data in an existing agreement, no files of
following type can be uploaded:
* pdf
* xlsx
* pptx
* docx
in screen a message as per attached image is shown, in the console following is
shown:
{code:java}
2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |SecuredUpload
|E| For security reason lines over 1 are not allowed
2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceUtil
|E| {errorMessage=For security reason only valid files of supported image
formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text files with safe names
(only Alpha-Numeric characters, hyphen, underscore and spaces, only 1 dot, name
and extension not empty) and contents are accepted., responseMessage=error}
2024-03-05 09:22:57,838 |jsse-nio-8443-exec-4 |ServiceDispatcher
|E| Error in Service [createAnonFile]: For security reason only valid files of
supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF, and ZIP or text files
with safe names (only Alpha-Numeric characters, hyphen, underscore and spaces,
only 1 dot, name and extension not empty) and contents are accepted.
2024-03-05 09:22:57,839 |jsse-nio-8443-exec-4 |TransactionUtil
|W| Calling transaction setRollbackOnly; this stack trace shows where this is
happening:
java.lang.Exception: Error in Service [createAnonFile]: For security reason
only valid files of supported image formats (GIF, JPEG, PNG, TIFF), SVG, PDF,
and ZIP or text files with safe names (only Alpha-Numeric characters, hyphen,
underscore and spaces, only 1 dot, name and extension not empty) and contents
are accepted.
at
org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:372)
[main/:?]
at
org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:306)
[main/:?]
at
org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:577)
[main/:?]
at
org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244)
[main/:?]
at
org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93)
[main/:?]
at org.apache.ofbiz.service.LocalDispatcher$runSync$0.call(Unknown
Source) [main/:?]
at
org.apache.ofbiz.service.engine.GroovyBaseScript.runService(GroovyBaseScript.groovy:74)
[main/:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:?]
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
~[?:?]
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:?]
at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
at
org.codehaus.groovy.runtime.callsite.PlainObjectMetaMethodSite.doInvoke(PlainObjectMetaMethodSite.java:48)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:166)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:57)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:62)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:194)
[groovy-3.0.21.jar:3.0.21]
at
org.apache.ofbiz.service.engine.GroovyBaseScript.run(GroovyBaseScript.groovy:82)
[main/:?]
at
org.apache.ofbiz.service.engine.GroovyBaseScript$run$3.callCurrent(Unknown
Source) [main/:?]
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:171)
[groovy-3.0.21.jar:3.0.21]
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
[groovy-3.0.21.jar:3.0.21]
at
org.apache.ofbiz.content.data.DataServicesScript.saveLocalFileDataResource(DataServicesScript.groovy:274)
[script:?]
at
org.apache.ofbiz.content.data.DataServicesScript$saveLocalFileDataResource.callCurrent(Unknown
Source) [script:?]
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent
[jira] [Created] (OFBIZ-12928) MFG - Move from hard-code menu location to parameterized
Pierre Smits created OFBIZ-12928: Summary: MFG - Move from hard-code menu location to parameterized Key: OFBIZ-12928 URL: https://issues.apache.org/jira/browse/OFBIZ-12928 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits Assignee: Jacques Le Roux Fix For: Upcoming Branch Customization is a key aspect of the OFBiz (Open For Business) platform, providing businesses with a robust and adaptable base to customize their enterprise software solutions according to their unique operational requirements. The *Menus.xml file of a component, essential for designing user interfaces that are both intuitive and tailored to the specific roles and tasks of its users, plays a significant role in this context, as referenced within screen widgets and Freemarker templates. However, as customizations and the project's source code evolve over time, the likelihood of encountering merge conflicts increases significantly, especially when attempting to incorporate customizations alongside ongoing bug fixes and enhancements from the project. To improve the appeal of OFbiz and the developer experience, it is recommended to shift from fixed menu locations to a parameterized approach in our components and plugins. This change would enable developers to more seamlessly incorporate a 'custom' menu, facilitating the integration of project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12922) HumanRes - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823090#comment-17823090 ] Pierre Smits commented on OFBIZ-12922: -- Thanks Jacques > HumanRes - Move from hard-code menu location to parameterized > - > > Key: OFBIZ-12922 > URL: https://issues.apache.org/jira/browse/OFBIZ-12922 > Project: OFBiz > Issue Type: Improvement > Components: humanres > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12920) Allow uploading ZUGFeRD compliant pdf files
[ https://issues.apache.org/jira/browse/OFBIZ-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822516#comment-17822516 ] Pierre Smits commented on OFBIZ-12920: -- Hi Johannes, [~jschreiber] As the original intent of this ticket has been implemented and thus the ticket has been closed (see also resolution), you should preferably do new improvement via a new ticket. Apart from the above, Is this a specific use-case scenario? While not being familiar with the intricacies of ZUGFeRD,/Factur-X, I can imagine that in other situations the pdf to be uploaded as content (Invoice, or otherwise related) may have valid multiple files attached? And thus may be rejected, due to the catch-all solution for ZUGFeRD? On a related subject: should OFBiz not be able to generate ZUGFeRD/Factur-X PDF files for sales invoices and credit-notes? Is that something you could work on? Best regards, Pierre > Allow uploading ZUGFeRD compliant pdf files > --- > > Key: OFBIZ-12920 > URL: https://issues.apache.org/jira/browse/OFBIZ-12920 > Project: OFBiz > Issue Type: Improvement > Components: framework/security >Affects Versions: Upcoming Branch >Reporter: originalnichtskoenner >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: invalid_sample_invoice.pdf, sample_invoice.pdf > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12922) HumanRes - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12922: - Component/s: humanres (was: accounting) > HumanRes - Move from hard-code menu location to parameterized > - > > Key: OFBIZ-12922 > URL: https://issues.apache.org/jira/browse/OFBIZ-12922 > Project: OFBiz > Issue Type: Improvement > Components: humanres > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (OFBIZ-12922) HumanRes - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12922 ] Pierre Smits deleted comment on OFBIZ-12922: -- was (Author: pfm.smits): This is regarding the AP web app in the accounting component. > HumanRes - Move from hard-code menu location to parameterized > - > > Key: OFBIZ-12922 > URL: https://issues.apache.org/jira/browse/OFBIZ-12922 > Project: OFBiz > Issue Type: Improvement > Components: humanres > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-12922) HumanRes - Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-12922: - Summary: HumanRes - Move from hard-code menu location to parameterized (was: ACC-AP - Move from hard-code menu location to parameterized) > HumanRes - Move from hard-code menu location to parameterized > - > > Key: OFBIZ-12922 > URL: https://issues.apache.org/jira/browse/OFBIZ-12922 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[
https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822092#comment-17822092
]
Pierre Smits commented on OFBIZ-10924:
--
{quote}Another option would be for me to finish and push the changes I was
(slowly) working on. Then you would pull and automatically incorporate them,
OFBIZ-12920 included, in the current trunk HEAD and recreate your PR from that.
What do you think about that?
{quote}
That works for me :D
> Have library dependencies moved to a dependencies.gradle file
> -
>
> Key: OFBIZ-10924
> URL: https://issues.apache.org/jira/browse/OFBIZ-10924
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk, Upcoming Branch
> Reporter: Pierre Smits
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: Image1.png, OFBIZ-10924-started.patch
>
>
> Currently the libraries needed by ofbiz are defined in the build.gradle file.
> These should reside in a separate dependencies.gradle file that is referenced
> in the build.gradle file, like the common.gradle. As is common practice in
> other projects/solutions that work with dependencies on external libraries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[ https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822072#comment-17822072 ] Pierre Smits commented on OFBIZ-10924: -- Btb, are you ok with the location of the dependencies.gradle file in the gradle folder? > Have library dependencies moved to a dependencies.gradle file > - > > Key: OFBIZ-10924 > URL: https://issues.apache.org/jira/browse/OFBIZ-10924 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk, Upcoming Branch > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Attachments: Image1.png, OFBIZ-10924-started.patch > > > Currently the libraries needed by ofbiz are defined in the build.gradle file. > These should reside in a separate dependencies.gradle file that is referenced > in the build.gradle file, like the common.gradle. As is common practice in > other projects/solutions that work with dependencies on external libraries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[ https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822071#comment-17822071 ] Pierre Smits commented on OFBIZ-10924: -- Hi Jacques, When looking at the PR, I now see a merge conflict (as a result of your latest commit related to OFBIZ-12920... When looking at the checkers of the PR, I see that the original commit ([5eb1b52|https://github.com/apache/ofbiz-framework/pull/714/commits/5eb1b5263938cd7e44348e02bfd834903b5ec237]) passed successfully, but subsequent library upgrades led to a failure to pass. It seems there must be something wrong there. What I will do is submitting a new PR based on the original intent, for you to review/test. And after that has been incorporated successfully, we can look at the upgrades. What are your thoughts? > Have library dependencies moved to a dependencies.gradle file > - > > Key: OFBIZ-10924 > URL: https://issues.apache.org/jira/browse/OFBIZ-10924 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk, Upcoming Branch > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Attachments: Image1.png, OFBIZ-10924-started.patch > > > Currently the libraries needed by ofbiz are defined in the build.gradle file. > These should reside in a separate dependencies.gradle file that is referenced > in the build.gradle file, like the common.gradle. As is common practice in > other projects/solutions that work with dependencies on external libraries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12918) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822014#comment-17822014 ] Pierre Smits commented on OFBIZ-12918: -- Besides, there is still some outstanding discussion on how to move forward with Accounts Payable and Accounts Receivable. > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12918 > URL: https://issues.apache.org/jira/browse/OFBIZ-12918 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12922) ACC-AP - Move from hard-code menu location to parameterized
Pierre Smits created OFBIZ-12922: Summary: ACC-AP - Move from hard-code menu location to parameterized Key: OFBIZ-12922 URL: https://issues.apache.org/jira/browse/OFBIZ-12922 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits Assignee: Jacques Le Roux Customization is a key aspect of the OFBiz (Open For Business) platform, providing businesses with a robust and adaptable base to customize their enterprise software solutions according to their unique operational requirements. The *Menus.xml file of a component, essential for designing user interfaces that are both intuitive and tailored to the specific roles and tasks of its users, plays a significant role in this context, as referenced within screen widgets and Freemarker templates. However, as customizations and the project's source code evolve over time, the likelihood of encountering merge conflicts increases significantly, especially when attempting to incorporate customizations alongside ongoing bug fixes and enhancements from the project. To improve the appeal of OFbiz and the developer experience, it is recommended to shift from fixed menu locations to a parameterized approach in our components and plugins. This change would enable developers to more seamlessly incorporate a 'custom' menu, facilitating the integration of project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-12918) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821822#comment-17821822 ] Pierre Smits edited comment on OFBIZ-12918 at 2/28/24 6:54 PM: --- Thanks Jacques, I prefer to do one web-app/ticket at a time, given the number of changes in web.xml and the various screens that will be affected in the component. So you can set the resolution as implemented, set the fix version and close this one. was (Author: pfm.smits): Thanks Jacques, I prefer to do one web-app/ticket at a time, given the number of changes in web.xml and the various screens in the component. So you can set the resolution as implemented, set the fix version and close this one. > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12918 > URL: https://issues.apache.org/jira/browse/OFBIZ-12918 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12918) Move from hard-code menu location to parameterized
[ https://issues.apache.org/jira/browse/OFBIZ-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821822#comment-17821822 ] Pierre Smits commented on OFBIZ-12918: -- Thanks Jacques, I prefer to do one web-app/ticket at a time, given the number of changes in web.xml and the various screens in the component. So you can set the resolution as implemented, set the fix version and close this one. > Move from hard-code menu location to parameterized > -- > > Key: OFBIZ-12918 > URL: https://issues.apache.org/jira/browse/OFBIZ-12918 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > > Customization is a key aspect of the OFBiz (Open For Business) platform, > providing businesses with a robust and adaptable base to customize their > enterprise software solutions according to their unique operational > requirements. > The *Menus.xml file of a component, essential for designing user interfaces > that are both intuitive and tailored to the specific roles and tasks of its > users, plays a significant role in this context, as referenced within screen > widgets and Freemarker templates. > However, as customizations and the project's source code evolve over time, > the likelihood of encountering merge conflicts increases significantly, > especially when attempting to incorporate customizations alongside ongoing > bug fixes and enhancements from the project. > To improve the appeal of OFbiz and the developer experience, it is > recommended to shift from fixed menu locations to a parameterized approach in > our components and plugins. This change would enable developers to more > seamlessly incorporate a 'custom' menu, facilitating the integration of > project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[ https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821688#comment-17821688 ] Pierre Smits commented on OFBIZ-10924: -- No worries, I noticed it too late (after I had pushed your requested changes to the PR) also. It's a good thing to have these PR checkers. > Have library dependencies moved to a dependencies.gradle file > - > > Key: OFBIZ-10924 > URL: https://issues.apache.org/jira/browse/OFBIZ-10924 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk, Upcoming Branch > Reporter: Pierre Smits >Priority: Minor > Attachments: OFBIZ-10924-started.patch > > > Currently the libraries needed by ofbiz are defined in the build.gradle file. > These should reside in a separate dependencies.gradle file that is referenced > in the build.gradle file, like the common.gradle. As is common practice in > other projects/solutions that work with dependencies on external libraries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[
https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821670#comment-17821670
]
Pierre Smits commented on OFBIZ-10924:
--
HI Jacques,
when changing
* implementation 'com.googlecode.ez-vcard:ez-vcard:0.11.3'
* + implementation 'com.googlecode.ez-vcard:ez-vcard:0.12.1'
I get following build error:
{code:java}
/Users/nl04748/dev/asf/ofbiz-framework/applications/marketing/src/main/java/org/apache/ofbiz/sfa/vcard/VCard.java:298:
error: no suitable method found for go(File)
Ezvcard.write(vcard).go(file);
^
method ChainingTextWriter.go(OutputStream) is not applicable
(argument mismatch; File cannot be converted to OutputStream)
method ChainingTextWriter.go(Path) is not applicable
(argument mismatch; File cannot be converted to Path)
method ChainingTextWriter.go(Writer) is not applicable
(argument mismatch; File cannot be converted to Writer)
method ChainingTextWriter.go(VCardWriter) is not applicable
(argument mismatch; File cannot be converted to VCardWriter)
{code}
Did you experience that too?
I reverted that one back to 0.11.3
> Have library dependencies moved to a dependencies.gradle file
> -
>
> Key: OFBIZ-10924
> URL: https://issues.apache.org/jira/browse/OFBIZ-10924
> Project: OFBiz
> Issue Type: Improvement
>Affects Versions: Trunk, Upcoming Branch
> Reporter: Pierre Smits
>Priority: Minor
> Attachments: OFBIZ-10924-started.patch
>
>
> Currently the libraries needed by ofbiz are defined in the build.gradle file.
> These should reside in a separate dependencies.gradle file that is referenced
> in the build.gradle file, like the common.gradle. As is common practice in
> other projects/solutions that work with dependencies on external libraries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[ https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821665#comment-17821665 ] Pierre Smits commented on OFBIZ-10924: -- Hi Jacques, Of course I will incorporate the changes in the [^OFBIZ-10924-started.patch]. And I will have at OFBiz-12920. > Have library dependencies moved to a dependencies.gradle file > - > > Key: OFBIZ-10924 > URL: https://issues.apache.org/jira/browse/OFBIZ-10924 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk, Upcoming Branch > Reporter: Pierre Smits >Priority: Minor > Attachments: OFBIZ-10924-started.patch > > > Currently the libraries needed by ofbiz are defined in the build.gradle file. > These should reside in a separate dependencies.gradle file that is referenced > in the build.gradle file, like the common.gradle. As is common practice in > other projects/solutions that work with dependencies on external libraries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-10213) Update build.gradle to the latest dependencies
[
https://issues.apache.org/jira/browse/OFBIZ-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821629#comment-17821629
]
Pierre Smits commented on OFBIZ-10213:
--
Hi Jacques,
A pull request has been submitted under OFBIZ-10924
> Update build.gradle to the latest dependencies
> --
>
> Key: OFBIZ-10213
> URL: https://issues.apache.org/jira/browse/OFBIZ-10213
> Project: OFBiz
> Issue Type: Task
> Components: Gradle
>Affects Versions: Trunk, Upcoming Branch
>Reporter: Jacques Le Roux
>Priority: Trivial
> Attachments: OFBIZ-10213.patch, OFBIZ-10213.patch, OFBIZ-10213.patch
>
>
> h2. This is an umbrella task for its action subtasks, please do not close,
> thanks.
> We want to check from time to time if we need to update the dependencies.
> It's easily done with the [gradle-versions-plugin
> |https://github.com/ben-manes/gradle-versions-plugin] which analyzes the
> dependencies and checks if there are newer versions available.
> Running the check with
> {code:java}
> gradlew -PenableDependencyUpdates dependencyUpdates -Drevision=release
> {code}
> We get a list of dependencies to update.
> We have problems with a number of libs. We keep comments in the main
> build.gradle for special updating issues. Be sure to check the main
> build.gradle. Some Java classes need internal versions update too:
> Also Solr et Lucene should use the same version, luceneMatchVersion should be
> updated in solrconfig.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-10924) Have library dependencies moved to a dependencies.gradle file
[ https://issues.apache.org/jira/browse/OFBIZ-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821621#comment-17821621 ] Pierre Smits commented on OFBIZ-10924: -- Hi Daniel, It is indeed about decluttering and reorganizing. Moving the listed implentation, testImplementation and runtimeOnly from the 'build.gradle' file into a separate 'dependencies.gradle' file should not affect similar dependencies in the other build.gradle file. I have not seen any negative effects building OFBiz with the definitions in the 'build.gradle' file in the solr plugin. > Have library dependencies moved to a dependencies.gradle file > - > > Key: OFBIZ-10924 > URL: https://issues.apache.org/jira/browse/OFBIZ-10924 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Trunk, Upcoming Branch > Reporter: Pierre Smits >Priority: Minor > > Currently the libraries needed by ofbiz are defined in the build.gradle file. > These should reside in a separate dependencies.gradle file that is referenced > in the build.gradle file, like the common.gradle. As is common practice in > other projects/solutions that work with dependencies on external libraries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DIRSTUDIO-1336) split GitHub workflow builds of pull requests
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1336. - Fix Version/s: 2.0.0-M18 Resolution: Implemented > split GitHub workflow builds of pull requests > - > > Key: DIRSTUDIO-1336 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1336 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > Splitting GitHub workflows for building Directory Studio. > Having build workflows for: > * openjdk 11 > * openjdk 17 > * openjdk 21 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1336) split GitHub workflow builds of pull requests
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1336. --- > split GitHub workflow builds of pull requests > - > > Key: DIRSTUDIO-1336 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1336 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > Splitting GitHub workflows for building Directory Studio. > Having build workflows for: > * openjdk 11 > * openjdk 17 > * openjdk 21 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1336) split GitHub workflow builds of pull requests
Pierre Smits created DIRSTUDIO-1336: --- Summary: split GitHub workflow builds of pull requests Key: DIRSTUDIO-1336 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1336 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits Splitting GitHub workflows for building Directory Studio. Having build workflows for: * openjdk 11 * openjdk 17 * openjdk 21 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1335) Bump tycho.version from 2.3.0 to 4.0.0
Pierre Smits created DIRSTUDIO-1335: --- Summary: Bump tycho.version from 2.3.0 to 4.0.0 Key: DIRSTUDIO-1335 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1335 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits Fix For: 2.0.0-M18 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1334) Bump org.codehaus.mojo:exec-maven-plugin from 3.1.1 to 3.2.0
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1334. --- > Bump org.codehaus.mojo:exec-maven-plugin from 3.1.1 to 3.2.0 > > > Key: DIRSTUDIO-1334 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1334 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1304) vulnerability for poi-3.9.jar
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1304. --- > vulnerability for poi-3.9.jar > - > > Key: DIRSTUDIO-1304 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1304 > Project: Directory Studio > Issue Type: Task >Affects Versions: 2.0.0-M17 >Reporter: Krystian Tokarz >Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > Our vulnerability system (Nessus) discovers that poi-3.9.jar file is > vulnerable (medium risk). This file is created when Apache Directory Studio > is started on our Windows 2016 Server OS. > Folders: > C:\Documents and > Settings\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar > and > C:\Users\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar > > Plugin ID: 106717 > Plugin description: The version of Apache POI installed on the remote host is > a version prior to 3.17. It is, therefore, affected by multiple DoS > vulnerabilities. Note that Nessus has not tested for these issues but has > instead relied only on the application's self-reported version number. > Apache POI < 3.17 Multiple DoS Vulnerabilities > > Could you provide any information about this issue? Can we patch this somehow? > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1304) vulnerability for poi-3.9.jar
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1304. - Resolution: Done > vulnerability for poi-3.9.jar > - > > Key: DIRSTUDIO-1304 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1304 > Project: Directory Studio > Issue Type: Task >Affects Versions: 2.0.0-M17 >Reporter: Krystian Tokarz >Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > Our vulnerability system (Nessus) discovers that poi-3.9.jar file is > vulnerable (medium risk). This file is created when Apache Directory Studio > is started on our Windows 2016 Server OS. > Folders: > C:\Documents and > Settings\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar > and > C:\Users\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar > > Plugin ID: 106717 > Plugin description: The version of Apache POI installed on the remote host is > a version prior to 3.17. It is, therefore, affected by multiple DoS > vulnerabilities. Note that Nessus has not tested for these issues but has > instead relied only on the application's self-reported version number. > Apache POI < 3.17 Multiple DoS Vulnerabilities > > Could you provide any information about this issue? Can we patch this somehow? > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (OFBIZ-12918) Move from hard-code menu location to parameterized
Pierre Smits created OFBIZ-12918: Summary: Move from hard-code menu location to parameterized Key: OFBIZ-12918 URL: https://issues.apache.org/jira/browse/OFBIZ-12918 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits Customization is a key aspect of the OFBiz (Open For Business) platform, providing businesses with a robust and adaptable base to customize their enterprise software solutions according to their unique operational requirements. The *Menus.xml file of a component, essential for designing user interfaces that are both intuitive and tailored to the specific roles and tasks of its users, plays a significant role in this context, as referenced within screen widgets and Freemarker templates. However, as customizations and the project's source code evolve over time, the likelihood of encountering merge conflicts increases significantly, especially when attempting to incorporate customizations alongside ongoing bug fixes and enhancements from the project. To improve the appeal of OFbiz and the developer experience, it is recommended to shift from fixed menu locations to a parameterized approach in our components and plugins. This change would enable developers to more seamlessly incorporate a 'custom' menu, facilitating the integration of project updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12812) [SECURITY] Remove deprecated Apache XML-RPC related code (CVE-2023-49070)
[ https://issues.apache.org/jira/browse/OFBIZ-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821204#comment-17821204 ] Pierre Smits commented on OFBIZ-12812: -- Hi [~deepak] This has been implemented and this ticket has been closed, but in the repository on GitHub the branch ([https://github.com/apache/ofbiz-framework/compare/trunk...remove-xml-rpc]) still exists. Should that not be removed from there too? > [SECURITY] Remove deprecated Apache XML-RPC related code (CVE-2023-49070) > - > > Key: OFBIZ-12812 > URL: https://issues.apache.org/jira/browse/OFBIZ-12812 > Project: OFBiz > Issue Type: Sub-task > Components: framework/service >Affects Versions: Upcoming Branch >Reporter: Deepak Dixit >Assignee: Deepak Dixit >Priority: Major > Fix For: Upcoming Branch > > > Apache XML-RPC is no longer maintained[1], we should remove the xml rpc > related code from trunk. > > [1] https://github.com/advisories/GHSA-6vwp-35w3-xph8 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12567) FinAccount Screen shows create trigger to user with VIEW permission
[ https://issues.apache.org/jira/browse/OFBIZ-12567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821119#comment-17821119 ] Pierre Smits commented on OFBIZ-12567: -- Thanks Jacques > FinAccount Screen shows create trigger to user with VIEW permission > --- > > Key: OFBIZ-12567 > URL: https://issues.apache.org/jira/browse/OFBIZ-12567 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Labels: finAccount, permissions, trust, user-experience > Fix For: Upcoming Branch > > > When accessing > [https://localhost:8443/accounting/control/EditFinAccount?finAccountId=ABN_CHECKING] > as a user with only VIEW permissions (e.g. userid=auditor) the screen shows > a action trigger to create something. > This should not be visible to such a user as it leads to a undesired effect > and diminished user experience. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12723) Remove fields oldQuantityOnHand and oldAvailableToPromise from InventoryItem entity
[ https://issues.apache.org/jira/browse/OFBIZ-12723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821069#comment-17821069 ] Pierre Smits commented on OFBIZ-12723: -- HI [~danwatford], This has been implemented,, but in the repository on GitHub the branch ([https://github.com/apache/ofbiz-framework/tree/ofbiz-12723]) still exists. Should that not be removed from there? Best regards, Pierre > Remove fields oldQuantityOnHand and oldAvailableToPromise from InventoryItem > entity > --- > > Key: OFBIZ-12723 > URL: https://issues.apache.org/jira/browse/OFBIZ-12723 > Project: OFBiz > Issue Type: Improvement > Components: datamodel, product >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > Fix For: Upcoming Branch > > > Remove fields oldQuantityOnHand and oldAvailableToPromise from the > InventoryItem entity, associated view-entities, forms and services. > OFBiz currently has a maintenance service, updateOldInventoryToDetailAll, > which finds any InventoryItems where oldQuantityOnHand or > oldAvailableToPromise are populated and creates corresponding > InventoryItemDetail entities. The oldQuantityOnHand and oldAvailableToPromise > fields are then cleared. > Based on source code repository logs, were already in the data model when > OFBiz was imported into subversion 1st July 2006. > Given the column names for the fields are hard-coded in the data model as > QUANTITY_ON_HAND and AVAILABLE_TO_PROMISE, I assume these entity fields, > along with the updateOldInventoryToDetailAll service, were implemented as a > method of upgrading the data model and are no longer used. > Since these fields are no longer used, lets remove them and their related > code, (slightly) reducing the size of ofbiz' sources that need to be > maintained. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12917) Move Create Agreement action trigger to MainActionsMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821043#comment-17821043 ] Pierre Smits commented on OFBIZ-12917: -- Thanks Jacques > Move Create Agreement action trigger to MainActionsMenu > --- > > Key: OFBIZ-12917 > URL: https://issues.apache.org/jira/browse/OFBIZ-12917 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > On the agreements search/find page and the agreement pages a create trigger > exists. This should move too the MainActionMenu for a unified User Experience. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12917) Move Create Agreement action trigger to MainActionsMenu
Pierre Smits created OFBIZ-12917: Summary: Move Create Agreement action trigger to MainActionsMenu Key: OFBIZ-12917 URL: https://issues.apache.org/jira/browse/OFBIZ-12917 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits On the agreements search/find page and the agreement pages a create trigger exists. This should move too the MainActionMenu for a unified User Experience. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DIRSTUDIO-1304) vulnerability for poi-3.9.jar
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820865#comment-17820865 ] Pierre Smits commented on DIRSTUDIO-1304: - [~elecharny] I will address this soon. > vulnerability for poi-3.9.jar > - > > Key: DIRSTUDIO-1304 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1304 > Project: Directory Studio > Issue Type: Task >Affects Versions: 2.0.0-M17 >Reporter: Krystian Tokarz >Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > Our vulnerability system (Nessus) discovers that poi-3.9.jar file is > vulnerable (medium risk). This file is created when Apache Directory Studio > is started on our Windows 2016 Server OS. > Folders: > C:\Documents and > Settings\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar > and > C:\Users\%username%\.eclipse\1407070357_win32_win32_x86_64\configuration\org.eclipse.osgi\65\0\.cp\lib\poi-3.9.jar > > Plugin ID: 106717 > Plugin description: The version of Apache POI installed on the remote host is > a version prior to 3.17. It is, therefore, affected by multiple DoS > vulnerabilities. Note that Nessus has not tested for these issues but has > instead relied only on the application's self-reported version number. > Apache POI < 3.17 Multiple DoS Vulnerabilities > > Could you provide any information about this issue? Can we patch this somehow? > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSTUDIO-1317) Improve CI processes
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820863#comment-17820863 ] Pierre Smits commented on DIRSTUDIO-1317: - Hi [~elecharny] OFBIZ-1331 is a sub-task of this ticket, should therefore stay open till done. IMO, sub-task 1 is about the GitHub actions, which should be light-weight and catered primarily to vetting Pull Requests. Sub-task 2m on the other hand, is about the more heavy-weight CI processes on CI-builds.a.o, running on the Jenkins variants. These should be about vetting the code base against various JDKs, packaging for the various platforms, etc. And it looks like that our CI process(es) on CI-builds.a.o. haven't run successfully for about 10 months now. So there is something definitely wrong in the params and/or code. > Improve CI processes > > > Key: DIRSTUDIO-1317 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1317 > Project: Directory Studio > Issue Type: Improvement > Components: studio-build > Reporter: Pierre Smits >Assignee: Pierre Smits >Priority: Major > > While working DIRSTUDIO-1316 I noticed that > * tools/run-ui-tests.sh > could do with some improvements, like > * the use of the referenced container > * running an individual test > We should also look at aligning the Studio CI processes with other Directory > sub-projects: > * > h4. [directory-server|https://github.com/apache/directory-server] > * > h4. [directory-ldap-api|https://github.com/apache/directory-ldap-api] > * and potentially others -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (OFBIZ-12916) Menu-items of EditGlAcctgTransSubTabBar are visible to user with only VIIEW PERMISSIONS
[ https://issues.apache.org/jira/browse/OFBIZ-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820811#comment-17820811 ] Pierre Smits commented on OFBIZ-12916: -- Hi Jacques, Thanks for your assistance and feedback. As a viewer, you can get to accounting transactions via various ways, including via processed invoices and payments (of which we have demo data). That is how I got there.. Having in such menu-item changes is a courtesy to our many adopters who customise the product to suit their requirements. Should I forego on that one, next time? > Menu-items of EditGlAcctgTransSubTabBar are visible to user with only VIIEW > PERMISSIONS > --- > > Key: OFBIZ-12916 > URL: https://issues.apache.org/jira/browse/OFBIZ-12916 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Reporter: Pierre Smits >Priority: Major > > The menu-items of the EditGlAcctgTransSubTabBar with en-US translated labels > * Duplicate Accounting Transaction > * Revert Accounting Transaction > are visible to a user with only VIEW permissions, like 'auditor' > This should not be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12916) Menu-items of EditGlAcctgTransSubTabBar are visible to user with only VIIEW PERMISSIONS
Pierre Smits created OFBIZ-12916: Summary: Menu-items of EditGlAcctgTransSubTabBar are visible to user with only VIIEW PERMISSIONS Key: OFBIZ-12916 URL: https://issues.apache.org/jira/browse/OFBIZ-12916 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits The menu-items of the EditGlAcctgTransSubTabBar with en-US translated labels * Duplicate Accounting Transaction * Revert Accounting Transaction are visible to a user with only VIEW permissions, like 'auditor' This should not be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12913) entity references wrong package
[ https://issues.apache.org/jira/browse/OFBIZ-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820458#comment-17820458 ] Pierre Smits commented on OFBIZ-12913: -- Thanks Jacques > entity references wrong package > --- > > Key: OFBIZ-12913 > URL: https://issues.apache.org/jira/browse/OFBIZ-12913 > Project: OFBiz > Issue Type: Improvement > Components: datamodel > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > The ShoppingLiistItemAttribute references the wrong package -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12913) entity references wrong package
Pierre Smits created OFBIZ-12913: Summary: entity references wrong package Key: OFBIZ-12913 URL: https://issues.apache.org/jira/browse/OFBIZ-12913 Project: OFBiz Issue Type: Improvement Components: datamodel Reporter: Pierre Smits The ShoppingLiistItemAttribute references the wrong package -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DIRSTUDIO-1333) Typo correction oorg.apache
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits closed DIRSTUDIO-1333.
---
> Typo correction oorg.apache
> ---
>
> Key: DIRSTUDIO-1333
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1333
> Project: Directory Studio
> Issue Type: Improvement
> Components: studio-ldapbrowser
> Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Fix For: 2.0.0-M18
>
>
> The valueEditor reference in valueEditors.exsd contains a typo in the class
> name:
> {code:java}
> oorg.apache.directory.studio.valueeditors.TextValueEditor {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1333) Typo correction oorg.apache
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits resolved DIRSTUDIO-1333.
-
Fix Version/s: 2.0.0-M18
Resolution: Implemented
> Typo correction oorg.apache
> ---
>
> Key: DIRSTUDIO-1333
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1333
> Project: Directory Studio
> Issue Type: Improvement
> Components: studio-ldapbrowser
> Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
> Fix For: 2.0.0-M18
>
>
> The valueEditor reference in valueEditors.exsd contains a typo in the class
> name:
> {code:java}
> oorg.apache.directory.studio.valueeditors.TextValueEditor {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSTUDIO-1333) Typo correction oorg.apache
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits reassigned DIRSTUDIO-1333:
---
Assignee: Pierre Smits
> Typo correction oorg.apache
> ---
>
> Key: DIRSTUDIO-1333
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1333
> Project: Directory Studio
> Issue Type: Improvement
> Components: studio-ldapbrowser
> Reporter: Pierre Smits
>Assignee: Pierre Smits
>Priority: Major
>
> The valueEditor reference in valueEditors.exsd contains a typo in the class
> name:
> {code:java}
> oorg.apache.directory.studio.valueeditors.TextValueEditor {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1333) Typo correction oorg.apache
Pierre Smits created DIRSTUDIO-1333:
---
Summary: Typo correction oorg.apache
Key: DIRSTUDIO-1333
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1333
Project: Directory Studio
Issue Type: Improvement
Components: studio-ldapbrowser
Reporter: Pierre Smits
The valueEditor reference in valueEditors.exsd contains a typo in the class
name:
{code:java}
oorg.apache.directory.studio.valueeditors.TextValueEditor {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (OFBIZ-12907) Move create new BillingAccount trigger to MainActionMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818548#comment-17818548 ] Pierre Smits commented on OFBIZ-12907: -- Thanks Jacques, for your assistance to get this into the codebase > Move create new BillingAccount trigger to MainActionMenu > > > Key: OFBIZ-12907 > URL: https://issues.apache.org/jira/browse/OFBIZ-12907 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > On CommonBillingAccountDecorator there is a action trigger to create a new > Billing Account that is visible to users with only VIEW permissions. > Moving the action trigger to the MainActionMenu with a permission condition > ensures that is only visible to the appropriate users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12907) Move create new BillingAccount trigger to MainActionMenu
Pierre Smits created OFBIZ-12907: Summary: Move create new BillingAccount trigger to MainActionMenu Key: OFBIZ-12907 URL: https://issues.apache.org/jira/browse/OFBIZ-12907 Project: OFBiz Issue Type: Improvement Components: accounting Reporter: Pierre Smits On CommonBillingAccountDecorator there is a action trigger to create a new Billing Account that is visible to users with only VIEW permissions. Moving the action trigger to the MainActionMenu with a permission condition ensures that is only visible to the appropriate users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12904) Duplicate create trigger for PaymentGroup
[ https://issues.apache.org/jira/browse/OFBIZ-12904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818218#comment-17818218 ] Pierre Smits commented on OFBIZ-12904: -- Thanks Jacques, for your assistance to get this into the codebase > Duplicate create trigger for PaymentGroup > - > > Key: OFBIZ-12904 > URL: https://issues.apache.org/jira/browse/OFBIZ-12904 > Project: OFBiz > Issue Type: Improvement > Components: accounting > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > The action trigger for creating a new PaymentGroup record is included in the > MainActionMenu of the component and in the action menu related to Payment > group. > The second one is superfluous. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12904) Duplicate create trigger for PaymentGroup
Pierre Smits created OFBIZ-12904: Summary: Duplicate create trigger for PaymentGroup Key: OFBIZ-12904 URL: https://issues.apache.org/jira/browse/OFBIZ-12904 Project: OFBiz Issue Type: Bug Components: accounting Reporter: Pierre Smits The action trigger for creating a new PaymentGroup record is included in the MainActionMenu of the component and in the action menu related to Payment group. The second one is superfluous. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12820) PaymentGroup Cancel button is shown to viewer
[ https://issues.apache.org/jira/browse/OFBIZ-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818132#comment-17818132 ] Pierre Smits commented on OFBIZ-12820: -- The 'Cancel' functionality is also included in the action menu for PaymentGroup, and it has conditions for permissions defined. So can be safely removed from the form. > PaymentGroup Cancel button is shown to viewer > - > > Key: OFBIZ-12820 > URL: https://issues.apache.org/jira/browse/OFBIZ-12820 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Priority: Major > Attachments: Screenshot from 2023-05-12 11-53-42.png > > > Currently when a user with only view permissions accesses the PaymentGroup > overview, as demonstrated in demo-trunk with userid=auditor, the action > trigger to cancel a PaymentGroup is shown. See attached image. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12903) Have screen ImportExport show Party MainActionMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818034#comment-17818034 ] Pierre Smits commented on OFBIZ-12903: -- Thanks Jacques for your assistance to get this into the codebase. > Have screen ImportExport show Party MainActionMenu > -- > > Key: OFBIZ-12903 > URL: https://issues.apache.org/jira/browse/OFBIZ-12903 > Project: OFBiz > Issue Type: Improvement > Components: party > Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Currently the ImportExport screen in PartyScreens.xml does not show the > MainActionMenu of the party component. > For a consistent user experience this should be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-12903) Have screen ImportExport show Party MainActionMenu
Pierre Smits created OFBIZ-12903: Summary: Have screen ImportExport show Party MainActionMenu Key: OFBIZ-12903 URL: https://issues.apache.org/jira/browse/OFBIZ-12903 Project: OFBiz Issue Type: Improvement Components: party Reporter: Pierre Smits Currently the ImportExport screen in PartyScreens.xml does not show the MainActionMenu of the party component. For a consistent user experience this should be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-12900) Have screen FindPartyClassificationGroups show Party MainActionMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-12900. Fix Version/s: Upcoming Branch Resolution: Implemented > Have screen FindPartyClassificationGroups show Party MainActionMenu > --- > > Key: OFBIZ-12900 > URL: https://issues.apache.org/jira/browse/OFBIZ-12900 > Project: OFBiz > Issue Type: Improvement > Components: party > Reporter: Pierre Smits >Priority: Major > Fix For: Upcoming Branch > > > Currently the FindPartyClassificationGroups screen in > PartyClassificationScreens.xml does not show the MainActionMenu of the party > component. > For a consistent user experience this should be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DIRSTUDIO-1323) Dependabot: Bump tycho.version from 2.3.0 to 4.0.5
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated DIRSTUDIO-1323: Summary: Dependabot: Bump tycho.version from 2.3.0 to 4.0.5 (was: Dependably: Bump tycho.version from 2.3.0 to 4.0.5) > Dependabot: Bump tycho.version from 2.3.0 to 4.0.5 > -- > > Key: DIRSTUDIO-1323 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1323 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > > see: [https://github.com/apache/directory-studio/pull/58] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSTUDIO-1323) Dependably: Bump tycho.version from 2.3.0 to 4.0.5
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned DIRSTUDIO-1323: --- Assignee: Pierre Smits > Dependably: Bump tycho.version from 2.3.0 to 4.0.5 > -- > > Key: DIRSTUDIO-1323 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1323 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > > see: [https://github.com/apache/directory-studio/pull/58] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1329) Bump org.apache.xmlgraphics:xmlgraphics-commons from 2.6 to 2.9
Pierre Smits created DIRSTUDIO-1329: --- Summary: Bump org.apache.xmlgraphics:xmlgraphics-commons from 2.6 to 2.9 Key: DIRSTUDIO-1329 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1329 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (OFBIZ-12900) Have screen FindPartyClassificationGroups show Party MainActionMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817753#comment-17817753 ] Pierre Smits commented on OFBIZ-12900: -- Thanks Jacques for your assistance to get this into the codebase > Have screen FindPartyClassificationGroups show Party MainActionMenu > --- > > Key: OFBIZ-12900 > URL: https://issues.apache.org/jira/browse/OFBIZ-12900 > Project: OFBiz > Issue Type: Improvement > Components: party > Reporter: Pierre Smits >Priority: Major > > Currently the FindPartyClassificationGroups screen in > PartyClassificationScreens.xml does not show the MainActionMenu of the party > component. > For a consistent user experience this should be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (DIRSTUDIO-1326) Dependabot: Bump org.apache.directory.project:project from 45 to 48
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1326. --- > Dependabot: Bump org.apache.directory.project:project from 45 to 48 > --- > > Key: DIRSTUDIO-1326 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1326 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > [https://github.com/apache/directory-studio/pull/59] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1326) Dependabot: Bump org.apache.directory.project:project from 45 to 48
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1326. - Fix Version/s: 2.0.0-M18 Assignee: Pierre Smits Resolution: Implemented > Dependabot: Bump org.apache.directory.project:project from 45 to 48 > --- > > Key: DIRSTUDIO-1326 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1326 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > [https://github.com/apache/directory-studio/pull/59] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1326) Dependabot: Bump org.apache.directory.project:project from 45 to 48
Pierre Smits created DIRSTUDIO-1326: --- Summary: Dependabot: Bump org.apache.directory.project:project from 45 to 48 Key: DIRSTUDIO-1326 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1326 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits [https://github.com/apache/directory-studio/pull/59] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSTUDIO-1325) Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned DIRSTUDIO-1325: --- Assignee: Pierre Smits > Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2 > --- > > Key: DIRSTUDIO-1325 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1325 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > > see [https://github.com/apache/directory-studio/pull/57] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1325) Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1325. --- > Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2 > --- > > Key: DIRSTUDIO-1325 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1325 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > see [https://github.com/apache/directory-studio/pull/57] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1325) Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1325. - Fix Version/s: 2.0.0-M18 Resolution: Implemented > Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2 > --- > > Key: DIRSTUDIO-1325 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1325 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > see [https://github.com/apache/directory-studio/pull/57] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1325) Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2
Pierre Smits created DIRSTUDIO-1325: --- Summary: Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2 Key: DIRSTUDIO-1325 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1325 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1325) Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated DIRSTUDIO-1325: Description: see [https://github.com/apache/directory-studio/pull/57] > Dependably: Bump junit.jupiter.version from 5.7.1 to 5.10.2 > --- > > Key: DIRSTUDIO-1325 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1325 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits >Priority: Major > > see [https://github.com/apache/directory-studio/pull/57] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1324) Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1324. --- > Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14 > --- > > Key: DIRSTUDIO-1324 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1324 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > See: [https://github.com/apache/directory-studio/pull/56] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSTUDIO-1324) Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned DIRSTUDIO-1324: --- Assignee: Pierre Smits > Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14 > --- > > Key: DIRSTUDIO-1324 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1324 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > > See: [https://github.com/apache/directory-studio/pull/56] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1324) Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1324. - Fix Version/s: 2.0.0-M18 Resolution: Implemented > Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14 > --- > > Key: DIRSTUDIO-1324 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1324 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > See: [https://github.com/apache/directory-studio/pull/56] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1324) Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14
Pierre Smits created DIRSTUDIO-1324: --- Summary: Dependabot: Bump org.apache.ant:ant-apache-regexp from 1.7.1 to 1.10.14 Key: DIRSTUDIO-1324 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1324 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits See: [https://github.com/apache/directory-studio/pull/56] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1323) Dependably: Bump tycho.version from 2.3.0 to 4.0.5
Pierre Smits created DIRSTUDIO-1323: --- Summary: Dependably: Bump tycho.version from 2.3.0 to 4.0.5 Key: DIRSTUDIO-1323 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1323 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits see: [https://github.com/apache/directory-studio/pull/58] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1322) Dependabot: Bump org.codehaus.mojo:exec-maven-plugin from 1.5.0 to 3.1.1
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1322. --- > Dependabot: Bump org.codehaus.mojo:exec-maven-plugin from 1.5.0 to 3.1.1 > > > Key: DIRSTUDIO-1322 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1322 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > see [https://github.com/apache/directory-studio/pull/55] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1322) Dependabot: Bump org.codehaus.mojo:exec-maven-plugin from 1.5.0 to 3.1.1
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1322. - Fix Version/s: 2.0.0-M18 Resolution: Implemented > Dependabot: Bump org.codehaus.mojo:exec-maven-plugin from 1.5.0 to 3.1.1 > > > Key: DIRSTUDIO-1322 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1322 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > see [https://github.com/apache/directory-studio/pull/55] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1322) Dependabot: Bump org.codehaus.mojo:exec-maven-plugin from 1.5.0 to 3.1.1
Pierre Smits created DIRSTUDIO-1322: --- Summary: Dependabot: Bump org.codehaus.mojo:exec-maven-plugin from 1.5.0 to 3.1.1 Key: DIRSTUDIO-1322 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1322 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits Assignee: Pierre Smits see [https://github.com/apache/directory-studio/pull/55] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1321) Dependably: Bump github/codeql-action from 2 to 3
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated DIRSTUDIO-1321: Description: see [https://github.com/apache/directory-studio/pull/54] > Dependably: Bump github/codeql-action from 2 to 3 > - > > Key: DIRSTUDIO-1321 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1321 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits >Priority: Major > > see [https://github.com/apache/directory-studio/pull/54] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1320) Dependabot issue: Bump actions/checkout from 2 to 4
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed DIRSTUDIO-1320. --- > Dependabot issue: Bump actions/checkout from 2 to 4 > --- > > Key: DIRSTUDIO-1320 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1320 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > See [https://github.com/apache/directory-studio/pull/53] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1320) Dependabot issue: Bump actions/checkout from 2 to 4
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1320. - Resolution: Implemented > Dependabot issue: Bump actions/checkout from 2 to 4 > --- > > Key: DIRSTUDIO-1320 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1320 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > See [https://github.com/apache/directory-studio/pull/53] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Reopened] (DIRSTUDIO-1320) Dependabot issue: Bump actions/checkout from 2 to 4
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reopened DIRSTUDIO-1320: - set correct resolution > Dependabot issue: Bump actions/checkout from 2 to 4 > --- > > Key: DIRSTUDIO-1320 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1320 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > See [https://github.com/apache/directory-studio/pull/53] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1320) Dependabot issue: Bump actions/checkout from 2 to 4
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved DIRSTUDIO-1320. - Fix Version/s: 2.0.0-M18 Resolution: Fixed > Dependabot issue: Bump actions/checkout from 2 to 4 > --- > > Key: DIRSTUDIO-1320 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1320 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > Fix For: 2.0.0-M18 > > > See [https://github.com/apache/directory-studio/pull/53] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1320) Dependabot issue: Bump actions/checkout from 2 to 4
Pierre Smits created DIRSTUDIO-1320: --- Summary: Dependabot issue: Bump actions/checkout from 2 to 4 Key: DIRSTUDIO-1320 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1320 Project: Directory Studio Issue Type: Improvement Reporter: Pierre Smits See [https://github.com/apache/directory-studio/pull/53] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Assigned] (DIRSTUDIO-1320) Dependabot issue: Bump actions/checkout from 2 to 4
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned DIRSTUDIO-1320: --- Assignee: Pierre Smits > Dependabot issue: Bump actions/checkout from 2 to 4 > --- > > Key: DIRSTUDIO-1320 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1320 > Project: Directory Studio > Issue Type: Improvement > Reporter: Pierre Smits > Assignee: Pierre Smits >Priority: Major > > See [https://github.com/apache/directory-studio/pull/53] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (OFBIZ-12900) Have screen FindPartyClassificationGroups show Party MainActionMenu
Pierre Smits created OFBIZ-12900: Summary: Have screen FindPartyClassificationGroups show Party MainActionMenu Key: OFBIZ-12900 URL: https://issues.apache.org/jira/browse/OFBIZ-12900 Project: OFBiz Issue Type: Improvement Components: party Reporter: Pierre Smits Currently the FindPartyClassificationGroups screen in PartyClassificationScreens.xml does not show the MainActionMenu of the party component. For a consistent user experience this should be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DIRSTUDIO-1319) Have an installer for Apple Mac on Apple Silicon
Pierre Smits created DIRSTUDIO-1319: --- Summary: Have an installer for Apple Mac on Apple Silicon Key: DIRSTUDIO-1319 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1319 Project: Directory Studio Issue Type: Improvement Components: studio-installer Reporter: Pierre Smits Have an installer for running Directory Studio on Apple Mac machines having Apple Silicon -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSTUDIO-1293) Fails to start on MacOS Monterey
[
https://issues.apache.org/jira/browse/DIRSTUDIO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817605#comment-17817605
]
Pierre Smits commented on DIRSTUDIO-1293:
-
Is this still an issue?
I took latest download
(ApacheDirectoryStudio-2.0.0.v20210717-M17-macosx.cocoa.x86_64) from
[https://directory.apache.org/studio/download/download-macosx.html] and
installed it on my MacBook with Sonoma 14.2.1 and OpenJDK Runtime Environment
Temurin-17.0.6+10 (build 17.0.6+10)
> Fails to start on MacOS Monterey
>
>
> Key: DIRSTUDIO-1293
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1293
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
>Affects Versions: 2.0.0-M17
> Environment: Model Name:MacBook Pro
> Model Identifier: MacBookPro18,2
> Chip: Apple M1 Max
> Total Number of Cores: 10 (8 performance and 2 efficiency)
> Memory: 32 GB
> System Firmware Version:7429.41.5
> OS Loader Version: 7429.41.5
>Reporter: Philip Peake
>Priority: Major
> Fix For: 2.0.0-M18
>
> Attachments: alert.png
>
>
> Launching Directory Studio fails with an error (see attached image),
> basically saying that the JNI_CreateJavaVM symbol is not found in
> libjvm.dylib.
> The symbol is actually there:
>
> {code:java}
> bin philip$ nm ../lib/server/libjvm.dylib | grep -i jni_create
> 004e3190 T _JNI_CreateJavaVM
> {code}
>
> Tried two different java versions:
> * zulu-11.jdk
> * zulu-17.jdk
> Tried adding the path to the java version explicitly in the Info.plist file:
>
> {code:java}
>
>
>
>
> -vm/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home/bin/java
> -keyring
> ~/.eclipse_keyring
>
>
> {code}
>
> This appears to be a problem in Eclipse/Directory Studio.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Comment Edited] (DIRSTUDIO-1316) Fix CI dir-studio-pipeline
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817248#comment-17817248 ] Pierre Smits edited comment on DIRSTUDIO-1316 at 2/14/24 11:29 AM: --- Analysis shows that failures are in [org.apache.directory.studio.test.integration.core|https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/lastBuild/testReport/junit/org.apache.directory.studio.test.integration.core/] for both linux 11 and linux 17 around h3. Error Message expected: but was: This is regarding DirectoryApiConnectionWrapperTest and h3. Error Message Prepare failed for LDAP server type Fedora389ds was (Author: pfm.smits): Analysis shows that failures are in [org.apache.directory.studio.test.integration.core|https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/lastBuild/testReport/junit/org.apache.directory.studio.test.integration.core/] for both linux 11 and linux 17 around h3. Error Message expected: but was: and h3. Error Message Prepare failed for LDAP server type Fedora389ds > Fix CI dir-studio-pipeline > -- > > Key: DIRSTUDIO-1316 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1316 > Project: Directory Studio > Issue Type: Bug > Components: studio-build > Reporter: Pierre Smits >Priority: Major > > The build and test pipeline for Studio has been failing for quit some time. > See [https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/] . > Last successful run was 10 months ago. > > How it works is defined in: > [https://github.com/apache/directory-studio/blob/master/Jenkinsfile] > See also: [https://www.jenkins.io/doc/book/pipeline/getting-started/] and > following pages. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1316) Fix CI dir-studio-pipeline
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated DIRSTUDIO-1316: Component/s: studio-build > Fix CI dir-studio-pipeline > -- > > Key: DIRSTUDIO-1316 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1316 > Project: Directory Studio > Issue Type: Bug > Components: studio-build > Reporter: Pierre Smits >Priority: Major > > The build and test pipeline for Studio has been failing for quit some time. > See [https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/] . > Last successful run was 10 months ago. > > How it works is defined in: > [https://github.com/apache/directory-studio/blob/master/Jenkinsfile] > See also: [https://www.jenkins.io/doc/book/pipeline/getting-started/] and > following pages. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (OFBIZ-12895) Have screen ListLoggedInUsers show Party MainActionMenu
[ https://issues.apache.org/jira/browse/OFBIZ-12895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817297#comment-17817297 ] Pierre Smits commented on OFBIZ-12895: -- Thanks Jacques, for your assistance > Have screen ListLoggedInUsers show Party MainActionMenu > --- > > Key: OFBIZ-12895 > URL: https://issues.apache.org/jira/browse/OFBIZ-12895 > Project: OFBiz > Issue Type: Improvement > Components: party >Affects Versions: Upcoming Branch >Reporter: Pierre Smits >Assignee: Jacques Le Roux >Priority: Major > Labels: user-experience > Fix For: Upcoming Branch > > > Currently the ListLoggedInUsers screen in VisitScreens.xml does not show the > MainActionMenu of the party component. > For a consistent user experience this should be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DIRSERVER-2393) Incorrect version naming inside the archive
[ https://issues.apache.org/jira/browse/DIRSERVER-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817260#comment-17817260 ] Pierre Smits commented on DIRSERVER-2393: - A similar question was posted on user@, and addressed by [~elecharny] . See https://lists.apache.org/thread/q2x6lwz1gtzlclkhpx5r9nqrmmm2x722 > Incorrect version naming inside the archive > > > Key: DIRSERVER-2393 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2393 > Project: Directory ApacheDS > Issue Type: Bug > Components: build >Affects Versions: 2.0.0.AM27 >Reporter: Oleksandr Andreiev >Priority: Major > Attachments: Screenshot from 2024-02-14 10-15-00.png > > > Hello, > When you download the archive for version *2.0.0.AM27 *from the official > resource and un-archive it you will notice that the unpacked folder name is > *2.0.0.AM28* > So, what is the version inside? > https://downloads.apache.org/directory/apacheds/dist/2.0.0.AM27/apacheds-2.0.0.AM27.tar.gz > The same for the .zip. > Regards, > Oleksandr -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1316) Fix CI dir-studio-pipeline
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated DIRSTUDIO-1316: Description: The build and test pipeline for Studio has been failing for quit some time. See [https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/] . Last successful run was 10 months ago. How it works is defined in: [https://github.com/apache/directory-studio/blob/master/Jenkinsfile] See also: [https://www.jenkins.io/doc/book/pipeline/getting-started/] and following pages. was:The build and test pipeline for Studio has been failing for quit some time. See [https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/] . Last successful run was 10 months ago. > Fix CI dir-studio-pipeline > -- > > Key: DIRSTUDIO-1316 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1316 > Project: Directory Studio > Issue Type: Bug > Reporter: Pierre Smits >Priority: Major > > The build and test pipeline for Studio has been failing for quit some time. > See [https://ci-builds.apache.org/job/Directory/job/dir-studio-pipeline/] . > Last successful run was 10 months ago. > > How it works is defined in: > [https://github.com/apache/directory-studio/blob/master/Jenkinsfile] > See also: [https://www.jenkins.io/doc/book/pipeline/getting-started/] and > following pages. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
