Tools and projects overview
There are several tools that are provided for Maven development that you can use to define Java™ EE module dependencies. You can also use POM entries to define project structure.
Important: Applicable to Liberty, WebSphere® Application Server traditional
POM editor overview
To open
the POM editor, double-click a pom.xml file in
a Maven enabled project. This multi-tabbed, form-based editor simplifies
editing of the Maven object model.
- Overview page
- Quickly view the project archive type and related properties.
- Dependencies page
- Add project and archive dependencies, and define how they are
managed.
- Dependency Hierarchy
- View deeper dependencies.
- Effective POM
- See a read-only full-model view that includes all of the default
values merged with the source pom.xml.
- pom.xml (source view)
- Edit the POM XML source with help from content assist.
Maven Repositories view
In the Maven Repository viewer, you can drill down and search local and remote repositories that are used for building your applications. You can define more repositories in the local ${user.home}/.m2/settings.xml file or in the pom.xml file of a project.
POM entries that affect the development workbench project structure
The following table shows several scenarios and attributes that are described in the Maven pom.xml and their affect on development workbench project settings.Scenario | POM attribute | Project structure change |
---|---|---|
Set the source folder location. |
|
Java build path settings are changed to this source folder. |
Set the output folder location. |
|
Java build path settings are changed to this output folder. |
Define the archive name for EAR or WAR files. |
|
Changes the deploy name for the project and creates the archive name upon export and deployment. |
Add dependencies using the MANIFEST file in an EJB project. |
|
Generated MANIFEST.MF file includes dependencies. |
Use the MANIFEST file in the src folder. |
|
Use the existing MANIFEST.MF file in the deployed JAR file. |
Create a WAR module. |
|
The dynamic web facet is specified and WAR plug-in settings are read for detailed changes. |
Do not generate an EAR deployment descriptor XML. |
|
The Application.xml file is not generated in the output location. |