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

Move the Add-In menu #17

Open
arejay73 opened this issue Jul 19, 2018 · 8 comments
Open

Move the Add-In menu #17

arejay73 opened this issue Jul 19, 2018 · 8 comments

Comments

@arejay73
Copy link

Is it possible to move the Add-In menu to the end after reports. When user go to RTC it load the Bulk Mover UI instead of defaulting to the Project Area Dashboard.

@innerjoin
Copy link
Contributor

@arejay73 Sorry, I was on vacation when this issue arrived and have not seen it until now.

I've experienced similar behavior on my side, but only when using a Jetty based server, which we only have for development.

On which kind of server did you try it?

@daytalker
Copy link

@innerjoin
We're facing this issue, too when using the extension on WebSphere Application Server.
In our dev environment we're running a WebSphere Liberty Server and there we do not see this issue. The Add-Ons menu entry on this server is been put at the end.

@innerjoin
Copy link
Contributor

This is weird. I always thought that this is a Jetty only issue because there are other spots where Jetty behaves differently as well... So I guess it all comes down at which time the Add-ons plugin is activated.

If we can find out the identifier of the plugin which provides the standard RTC menu, we could at this identifier to the Add-on manifest to ensure the plugins are activated in the right order.

@MartinBenninger You have already looked at how the work item menu is built. Can you find out what it'a identifier is?

@innerjoin
Copy link
Contributor

This issue was linked by RTC Work Item 684932 on behalf of [email protected]

@innerjoin
Copy link
Contributor

@arejay73 @daytalker
Please have a look at the Menu Provider in WIBM 1.4.4. It contains a new dependency entry in the MANIFEST.MF file that should fix this issue.

Thank you @MartinBenninger for searching the respective plugin for me 🥇

@innerjoin innerjoin reopened this Nov 17, 2018
@innerjoin
Copy link
Contributor

It seems not to be working, so I'm opening this issue again...

@arejay73 @daytalker I think I can't do anything here, so you should open a Case (former PMR) at IBM.

@innerjoin
Copy link
Contributor

@arejay73 @daytalker
Have you guys opened a Case (PMR) for this? If not, shall I?

@daytalker
Copy link

daytalker commented Dec 3, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants