Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Rob Stryker
    @robstryker
    but i dont think they use the newest rsp-server
    i'd need to check
    but thats where nightlies would go
    also that page has way too many builds ;) we might need to figure out how to trimp it
    version to be released is 0.21.0 but i dont see it there
    Rafael Henrique
    @rafadev7
    Hello there, I'm getting an error when trying to create a server downloading through the Internet, I'm getting timeout and this message:
    Unable to create the server: Extension backend error - failed to list downloadable runtimes in time
    Andre Dietisheim
    @adietish
    @rafadev7 hi Rafael
    is the error persistent?
    lampsbr
    @lampsbr

    Hi, how can I manually remove a deployment from the list in vscode extension? I mean, I have some deployments listed in my wildfly9 installation that are no longer there. They're not in deployments directory for a long time (several reboots). But they are still listed in vscode extension. I tried right-click in the server > edit server and removing the deployables, but turns out it's a tmp file and what I change in there isn't reflected anywhere. Of course I tried right clicking the deployment > remove deployment, but nothing happens after this. The server is always annotated with "full publish required", but I get an extension backend error when I try to full publish, and I don't know how to do it manually in wildfly.

    Sorry for the long message, I'm not sure if it's clear

    Rob Stryker
    @robstryker
    @rafadev7 That's a UI error that the backend (rsp-server) took too long to download the list of runtimes to download. Typically, if you just re-execute the action, it should work unless you have an issue with your internet connection
    Rob Stryker
    @robstryker
    @lampsbr depending on which version you have, you would want to look in ~/.rsp/redhat-server-connector/servers/yourServerNameHere or ~/.org.jboss.tools.rsp.data/servers/yourServerNameHere
    if you edit that file when your rsp is stopped, you can remove the deployments there
    then next time you start your rsp it should work
    but also, can you make a github issue for the workflow you have that's failing now? So i can look into it?
    lampsbr
    @lampsbr
    Hi @robstryker ! Yes, I'll create the github issue and try this solution tomorrow morning. Thank you!
    lampsbr
    @lampsbr
    I just created the issue. Thanks for helping and please let me know if you need more info. I'll keep my "ghost deploy" in here for another day. =]
    Gabriel Gaudina
    @gabrielg-dev
    hi all ... I can't deploy a java app using the extension, neither java13 + wildfly17 nor java8 + wildfly15 (ubuntu), the extension does nothing after "add deployment -> exploded" or "deploy incremental/full" ... I'm doing something wrong?
    Luca Stocchi
    @lstocchi
    Hi @gabrielg-dev, do you have any error displayed? In the bottom-right is there any box with a message? Are you able to start your server properly?
    Gabriel Gaudina
    @gabrielg-dev
    Hi @lstocchi, I see no error, no vscode message, just usual wildfly starting log output in "output" console after start server but nothing more after right clic -> deploy server, if it helps, "red hat RSP console" shows a message: SLF4J: Defaulting to no-operation (NOP) logger implementation
    ... I see "building ..." messages in vscode toolbar after change something in any source, but nothing changes in server
    Rob Stryker
    @robstryker
    @gabrielg-dev do you mean publish server?
    @gabrielg-dev can you tell me what version of vscode-server-connector you are using?
    Gabriel Gaudina
    @gabrielg-dev
    yes, "publish server" ... and version 0.21.1, reinstalled today after manually deleting config folder
    vscode 1.40.1
    Rob Stryker
    @robstryker
    so you use vscode-server-connector to start your wildfly? and then try to publish to it? and nothing happens? or are you publishing / deploying to a stopped server?
    Rob Stryker
    @robstryker
    @gabrielg-dev
    Gabriel Gaudina
    @gabrielg-dev
    I use connector to start server, then I try to publish
    @robstryker
    Luca Stocchi
    @lstocchi
    @gabrielg-dev you said that you're looking at "red hat RSP" console, don't you have another output channel like "Server: wildfly-17.0"?
    Rob Stryker
    @robstryker
    @gabrielg-dev can you verify that the files are at least copied to wildfly/standalone/deployments?
    Gabriel Gaudina
    @gabrielg-dev
    @lstocchi I have 3 output channels, I see a warn/error only in that channel
    @robstryker yes I can, give me few minutes ....
    Gabriel Gaudina
    @gabrielg-dev
    @robstryker @lstocchi there is a change .... after clean wildfly deployment folder, started server with extension, and trying to add deployment get next message (popup below right):
    Unable to add deployment to the server: Extension backend error - server wildfly17 does not support deployment of resources without an approved suffix. use the deployment.output.name deployment option to override the output name.
    Rob Stryker
    @robstryker
    @gabrielg-dev ok so how are you trying to add this deployment?
    what exactly are you trying to add as a deployment?
    Gabriel Gaudina
    @gabrielg-dev
    @robstryker add deployment -> exploded -> project folder inside "target"
    Rob Stryker
    @robstryker
    @gabrielg-dev can you give me an example of your target folder on pastebin?
    @gabrielg-dev so when we developed this, we made it so you either deploy a built / packaged file (something.war, something.jar, something.ear, something.rar) or a folder (like target/something) which looks exactly like an exploded version of your desired output
    if you choose the second option, you still have to tell it what you want your output name to be
    so you need to go to optional deployment attributes and set it to be "something.war"
    Luca Stocchi
    @lstocchi
    These are the steps as Rob described ... add deployment -> exploded -> proj folder -> "Do you want to edit optional deployment params?" -> Yes -> type something like "something.war" -> done
    Gabriel Gaudina
    @gabrielg-dev
    @robstryker "if you choose the second option, you still have to tell it what you want your output name to be" ... that worked, I was confused by "leave it blank for default"
    @lstocchi @robstryker thank you a lot
    Rob Stryker
    @robstryker
    @gabrielg-dev Thanks. I wish we could find a way to improve this workflow, but for now this is what we have. It's very difficult to tell what a maven project is by default.
    Stéphane Bouchet
    @sbouchet
    @robstryker : my 2cs -> can you access to the pom and get the project name as default ? or just set a "real" default value like project.war ? for now i understand that is leaving the default value and use exploded it simply does not work..
    Rob Stryker
    @robstryker
    @sbouchet problem is if someone tries to deploy a jar, or a rar, or an ear. We can't just magically tell its a war file
    also we currently dont even know that the folder they're selecting is even a maven project
    they just point to a folder or a file
    Thiago Henrique Hüpner
    @Thihup
    Can I deploy a global jar in Wildfly like in old versions of JBoss?
    Stéphane Bouchet
    @sbouchet
    @robstryker : ok get it. so the only thing is when user select exploded deplyment, the name MUST be changed .