• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Jeanne Boyarsky
Saloon Keepers:
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Piet Souris
Bartenders:

Wildfly 24 Eclipse javaee add/remove resources

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Whenever I launch a Maven project, several old projects also start up (at least the console reports their errors).
I only have one resource (project) in the configured area of the Wildfly 'Add and Remove' dialog.
Why are old projects being launched, or how can I get rid of them?
Is it possible for Wildfly to ignore old projects without deleting the project code from the hard drive.
The current project still launches but the log is cluttered with old errors and warnings and difficult to read.
Thanks in advance.
 
Ranch Hand
Posts: 31
2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
How about approaching this from another angle.
Move the old Wildfly to a directory you create for archiving stuff. It lives here for posterity.
Then start with a fresh install of Wildfly 24. Bring across configuration and the applications you want to keep from the archive.
Does that work for you ?
 
Saloon Keeper
Posts: 26769
190
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm going to make a wild guess here and assume you're using Maven to launch Wildfly for your project, after having done the same for other projects.

What's probably happening is that Maven is simply launching a master copy of Wildfly and whatever WARs/EARS have been deployed to that Wildfly are launched.

In other words, Wildfly is, like any other JEE webapp server NOT a place you simply dump files, it's a service for running webapps (WARs and EARs). And Maven is simply deploying your latest build and launching Wildfly. Unless Maven also undeploys webapps, they're there until some external force removes them. That includes any situations where Maven intended to undeploy but something terminated the Maven process before it could.

To get rid of the old crud, try launching Wildfly without Maven and see if its "control panel" isn't listing all those apps. If so, undeploy/remove them from Wildfly.

There may also be an undeploy Maven goal, but since I don't launch webapp servers from Maven (I usually launch stand-alone or from an IDE) I don't know for certain.
 
Saloon Keeper
Posts: 14798
333
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I usually just keep the deployments folder of my standalone Wildfly instance open in my file explorer, and manually remove deployments whenever I'm not debugging my applications.
 
The fastest and most reliable components of any system are those that are not there. Tiny ad:
The Low Tech Laboratory Movie Kickstarter is LIVE NOW!
https://www.kickstarter.com/projects/paulwheaton/low-tech
reply
    Bookmark Topic Watch Topic
  • New Topic