Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved: have profileMenuLocation (OFBIZ-12981) #106

Closed
wants to merge 2 commits into from

Conversation

PierreSmits
Copy link
Member

Profile screens are used in various components as portalpageportlets, and have references to various party menus. As menus in the various profile screens are parameterized to use ${parameters.mainMenuLocation} this generates errors in the components/applications where these screens are used as portal page elements. Having a context-param profileMenuLocation resolves this issue.

modified:
myportal-web.xml: have contex-param profileMenuLocation

Profile screens are used in various components as portalpageportlets, and have references to various party menus. As menus in the various profile screens are parameterized to use ${parameters.mainMenuLocation} this generates errors in the components/applications where these screens are used as portal page elements.
Having a context-param profileMenuLocation resolves this issue.

modified:
myportal-web.xml: have contex-param profileMenuLocation
Copy link

sonarcloud bot commented Apr 11, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@JacquesLeRoux
Copy link
Contributor

Thanks Pierre, the AssetMaint integration tests pass?

@PierreSmits
Copy link
Member Author

HI @JacquesLeRoux,

the AssetMaint integration aspect got accidentally in this, but is something you committed to the main branch 4 days ago via 21aff95

I apologize if some things got crossed.

@JacquesLeRoux
Copy link
Contributor

I meant: did you run gradlew "ofbiz --test component=assetmain" ?

@PierreSmits
Copy link
Member Author

Hi @JacquesLeRoux

I did not. As the changes in this are in the web.xml file, which only affect the UI side and not any tests.

However, I just ran the test against the main branch (trunk, up tp date per 07:00 this morning) and it failed. So something before that moment must have gone wrong in FixedAssetMaintTests.groovy

@PierreSmits
Copy link
Member Author

Did you run the test(s)?

@JacquesLeRoux
Copy link
Contributor

Hi Pierre,

the changes in this are in the web.xml file, which only affect the UI side and not any tests.

Wrong you also modified FixedAssetMaintTests and it's different than locally.
To run the tests I'd need to patch locally. I have enough on my plate. So my question remains:

did you run gradlew "ofbiz --test component=assetmain" ? (in your branch)

@JacquesLeRoux
Copy link
Contributor

With https://issues.apache.org/jira/browse/OFBIZ-12985
we have completly fixed all the integration tests. Why would you want to change
assetmaint/src/main/groovy/org/apache/ofbiz/assetmaint/assetmaint/test/FixedAssetMaintTests.groovy?

@PierreSmits
Copy link
Member Author

Closing this. Time for a do-over as it is giving to much headache.

@PierreSmits PierreSmits deleted the OFBIZ-12981 branch April 12, 2024 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants