You can skin your portal by change skin setting in Portal Setting. You'll see this form if you click Edit Portal's config.
Yeah, I could if the skin would be showing up in there. But I don't see any skin except the default one.
Try to add gatein-sample-skin in the "dependencies" in the file:
And that should work.
Yesterday we actually discussed so that the default will be to add the skin everywhere
Thanks. Could have looked for ages and haven't found that one.
It is working now, thanks.
I'm in the same sittuation: I have created a custom portal container, but it can not see the same skins that the default portal can.
I'm not messing with the code, I have GateIn deployed with JBoss and am only working in the deploy folder.
I can drop new .war skins in the deploy folder and the default portal will detect them, so I'm guessing no config is necessary there.
But my custom portal can not see these skins. Any hints?
Can you try by building trunk or see my previous comment about adding your skin in the dependency list ?
I remember the issue, there is a JIRA somewhere for it IIRC. (been fixed)
Hi Thomas, thank you for your reply
I'll try to get the source and make a build, but I still can't understand. The default portal can detect new skins without being recompiled. Are you saying I have to compile my custom portal every time I deploy a new skin? What is the difference between the default portal and the custom ones? Shouldn't this be a configuration issue?
Thank you again.
No you don't need to recompile every time. There was a bug which IIRC has been fixed in GateIn trunk (it has been fixed for sure in EPP 5.1), it slightly change the behaviour.
I really can't find that issue, if you can find it please post the link.
I'm also having a hard time configuring the develpment environment to build it. Which part would I have to compile and deploy?
I'm sorry to insist, I'm having a hard time checking-out the projects and meanwhile I've tried simething else.
I've added both gatein-sample-skin and my-custom-skin to the dependencies of my custom portal. It works (sort of).
Now, I can see the skins in the custom portal but they are not visible in the default portal. Is this the normal behaviour? Can't a skin be used by two portal containers? Or is this what you were talking about, the corrected issue? Please give me more info on that issue, I ran through all the issues since 3.1 and nothing resembles my problem.