不同WildFly运行时环境下通用项目的Eclipse构建路径规划咨询

Hey Marco, let's break down the optimal Eclipse setup for your complex WildFly-based multi-project ecosystem—this is a scenario I’ve helped several teams tackle, so I’ll share practical, maintainable strategies tailored to your needs.

一、工作空间分层：清晰边界，避免混乱 #

First, structure your Eclipse workspace with logical layers to keep projects organized:

• Core Shared Layer: Group all universal jar projects (like your Project Common) into a dedicated Working Set (name it something like Shared-Libraries). Keep these in a top-level folder (e.g., /shared-libs) so you can update them once and have all dependent projects pick up changes.
• Business Application Layers: Create a separate Working Set for each of your 7 EARs (e.g., App-EAR-OrderProcessing, App-EAR-CustomerManagement). Each Working Set should include only the WAR/EJB modules and non-shared projects specific to that EAR. This way, you can focus on one application at a time without clutter from unrelated projects.

二、WildFly Runtime管理：适配多版本，避免兼容性坑 #

With WildFly versions spanning 10 to 12, proper runtime configuration is critical:

• Add all required runtimes to Eclipse: Go to Window > Preferences > Server > Runtime Environments, then add WildFly 10, 11, and 12 (point each to its own installation directory). Pro tip: Rename each runtime to match its target server (e.g., WildFly 10 (Payment Server), WildFly 12 (Analytics Server)) so you never mix them up.
• Link each EAR to its correct runtime: Right-click the EAR project > Properties > Targeted Runtimes, then check the corresponding WildFly version. Eclipse will automatically load the right class libraries and validate deployment descriptors against that version’s specs.

三、共享依赖：高效复用，杜绝重复打包 #

Your shared jars need a reliable management strategy to avoid version conflicts and redundant work:

• Use a build tool (Maven/Gradle) if possible: This is the long-term solution. Publish your shared projects to an internal repo (like Nexus), then have each EAR pull dependencies via coordinates. Eclipse will sync with your build file, so you never have to manually copy jars between projects.
• If stuck without build tools, use Eclipse User Libraries: Create a User Library (go to Window > Preferences > Java > Build Path > User Libraries) named Common-Libs vX.X, add all your shared jars to it, then reference this library in every project that needs the common code. Just make sure everyone on the team uses the same library version to avoid discrepancies.
• Optimize deployment: In each EAR’s application.xml, set a library-directory (e.g., lib/) and place shared jars there. This tells WildFly to share the jars across all modules in the EAR, so you don’t end up with duplicate copies in WARs/EJBs.

四、构建与部署：节省时间，减少错误 #

• Enable automatic incremental builds: Make sure Project > Build Automatically is checked. Eclipse will only recompile modified files instead of rebuilding the entire workspace, which saves tons of time with large projects.
• Map servers to matching EARs: In the Eclipse Servers view, create separate server instances for each WildFly version, then only deploy the EARs that target that version. For example, your WildFly 10 server should only host the 2 EARs designed for it—this prevents deployment failures from incompatible code.
• Leverage WildFly hot deployment: Edit your WildFly standalone.xml to add <deployment-scanner scan-interval="5000" deployment-timeout="600"/> in the deployment scanner section. This lets Eclipse push code changes to the server automatically, no manual restarts needed.

五、日常维护：keep things smooth #

• Filter projects with Working Sets: Switch the Project Explorer to "Working Set" mode and only show the Working Set you’re currently working on. No more scrolling through dozens of unrelated projects!
• Debug dependency conflicts: Use Eclipse’s Dependency Hierarchy view (right-click a project > Show In > Dependency Hierarchy) to spot version conflicts in shared jars. This is a lifesaver when an EAR starts throwing unexpected classpath errors.
• Validate runtime compatibility: Use Eclipse’s Server Tools plugin to check your deployment descriptors (like jboss-web.xml or ejb-jar.xml) against the target WildFly version. It’ll flag any deprecated tags or incompatible configurations before you deploy to production.

内容的提问来源于stack exchange，提问作者Marco Del Percio