Extension downloaded from ABAP repository Not Valid Extension Project

[adtoth]

Hi Experts,

I have an extended Fiori application uploaded into the ABAP repository. When I try to download it from another WebIDE account and I start to continue the extension the WebIDE says "The selected project is not a valid extension Project".

Any ideas how to tell the webIDE that it's an extension project?

Thanks,

David

[michal_keidar · Accepted solution]

Hi,

I guess this extension project wasn't created in Web IDE?

This is a problem.

One thing that comes to my mind is its project.json file probably missing the "extensibility" block with all the relevant information.

So I would recommend to create the extension project in Web IDE and add your extensions and modifications to it.

If you don't want to do that you can create it and just copy the "extensibility" block from its project.json file to your file. But there might by other issues too.

Regards,
Michal.

[adtoth · Accepted solution]

Hi,

Actually the project was created in WebIDE. And that's what I want to avoid, to create a new extension project and copy the ready extensions, if i want to do some modification or new ones.. 😕

[michal_keidar · Accepted solution]

Can you attach it?

[adtoth · Accepted solution]

what do oyu mean?

[michal_keidar · Accepted solution]

I mean can you attach your project here so that I could take a look at it?

[Former Member · Accepted solution]

Hi,

I was facing the same issue (see screenshot below).

After analysis, I found differences in “.project.json” file.

In the webIDE extension project of the creator, the file ".project.json" contains informations about extensions which are missing during deployment and so missing after importation in my workspace.

So I asked the creator to send me this file content and I pasted it in the “.project.json” of this extension project imported in my workspace.

And now it works well, the error disappeared . So this seems to be a solution.

BRs,

Eric

[michal_keidar · Accepted solution]

Yes it's true. When creating an extension project in Web IDE, there's an "extensibility" block generated in its project.json file, which identifies the project as an extension project.

During deployment either only the content of webapp is deployed or a client build is happening and then only the content of the dist folder is deployed, without the project.json file.

Then when importing an extension project this information is missing and it isn't identified as an extension project.

The thing is, the flow of importing an extension project seems a bit invalid.

Why would you want to import an extension project?

I mean, the flow as I see it is either create an extension project from scratch, or use Git source control if you want to share your extension project with others.

Regards,
Michal.

[adtoth · Accepted solution]

This was the thing I've also found about the project.json.

I just wanted to check if it's possible to do import it, becouse let's say I develop something for a client, and after years another developer want's to modify this extension. In this case it wont be so easy to find the project on git, it would be easier just import it from the system.

But okey, we will keep using git Thanks for helping!

[Former Member · Accepted solution]

OK, in my case, we didn't use git for the moment. But if I understand well, as the "dist" folder doesn't contains the ".project.json", the same problem can happen with git.

Our case was:

We have one application with two extension points in one view.

Someone created the extension project, implemented one extension point and deployed it to our server.

And after some days, I had to implement the other extension point. So I have imported the project from the server, but it was not possible to add new extension in this project..

So, what is the normal flow to achieve this ?

BRs,

Eric

[adtoth · Accepted solution]

I think the only way is to use git. Or Re-create the extension project in your workspace, and copy the extensions from the one you've imported from the repository.

[michal_keidar · Accepted solution]

Hi Eric,

The "dist" folder is only relevant when building the application during deployment.

There is no build when developing the app using Git. Only when you're finished with the development and ready to go to the testing/production phase, then you deploy it (and the build happens in the process).

So in your case I guess the valid flow would be that one developer creates the extension project and implements one extension-point, then he connects it to a Git repository and commits and pushes his code.

The second developer takes the app's Git repository URL and clones the app to his workspace in Web IDE, implements another extension-point and commits and pushes his code to the repository.

And so on.

After you're finished with the development - deploy the app.

What do you think?

Regards,
Michal.

[Former Member · Accepted solution]

OK thanks Michal.

So now we have to see how to use GIT in webIDE of HCP.

When deploying on our server, the versions are already managed in ABAP repository via transport flow, so to keep it simple we decided to not use GIT to begin (but for sure this doesn't give all possibilities of GIT). This was probably a wrong decision, specially for collaborative working.. Now I don't know if we can easily create a new git repository for our existing apps already implemented and deployed.

So if you have any inputs/helpful links about this (how to configure existing app git repository) , I'm open .

One last word about this, miss the project type during deploying and importing from ABAP repository is little bad, but it forces us to use GIT.

BRs,

Eric

[michal_keidar · Accepted solution]

Hi,

I'm still looking into how we can improve and not lose the project type after importing/deploying the app.

Regarding your questions about Git - - can you please assist?

Thanks,
Michal.

[Former Member · Accepted solution]

About my question, we are thinking to recreate all with GIT repository this time, there is already many good inputs on scn forums and blogs (some wrote by you by the way). For a collaborative work and more flexible development, it looks good.

And thanks to abap repository is well separated, we can do many modifications on HCP without break anything (and by webIDE local export/import functionality without loosing code). So we will success.

Sure it could be good to not loose project type after importing/deploying app to server.. because now it is a little confusing.

Many thanks Michal.

BRs,

Eric