帮助管理许多大型项目的工具
The Maven's swiss knife
When a team writes a lot of maven projects, it is painful to manage versionning and connections between them. This tool helps you to update you pom graph easily.
It has several objectives:
Main functions :
${foobar.version}, pom-explorer will go to update the foobar.version property...This project is in active development and serves also as a platform to work on useful use cases that can manifest. It is used to manage the versions, connections and dependencies of 43 projects. If you have ideas or anything like that, don't hesitate to write a pull request.
This project is certainly not production ready nor really user-friendly. That's because the functionality set is not well defined yet. So any feature you need related to your pom dependency graph could be added in the feature list and will maybe impact the final architecture. So that is certainly the moment for you to say what you need in this project !
To build :
mvn clean installTo run :
java -jar pom-explorer/target/pom-explorer.jarThen go with your browser on this address
http://localhost:8090If you want the application to bind on a different port, you can specify the listening port like this :
java -jar pom-explorer/target/pom-explorer.jar PORT_NUMBERThis is the console to the application. You can type commands in the prompt, they will be sent to the server and it will answer.
Let's start by typing ? to get the available commands :
If you use a specific maven configuration file, you can specify it prior to the next commands with the session mavenSettingsFilePath String command.
First, you will want to analyze some projects. Depending on where they are on your computer, you can type something like this in the application console/web page :
analyze directory c:\documents\reposThe program will analyze the directory recursively to find all the pom.xml files. They are then processed with the traditionnal MavenXpp3Reader and also resolved through the internal resolver, handing back to ShrinkWrap component if there is a problem. A graph is then constructed in memory representing the dependencies between projects.
If you need, you can add more analyzes by repeating the analyze directory command again on another directory.
Let's have a look at the GAVs (groupId/artifactId/version) that are registered in the graph :
gav listHere's an example of a result :
It is possible to visualize dynamically the graph dependency. The graph is using WebGL and allows to walk in the 3D space with the W, S, A, D, Q and E keys. It is using the VivaGraph and NGraph libraries.
You can enter the graph command :
> graph
To display the graph, go to : graph.html?session=1441798206Then click on the given link to see the graph for your current session.
In the main part, you can navigate with W,A,S,D,E,A and the arrow keys. On the right side, you can edit javascript filters and customizers for node and links.
You can filter edges and vertices, and even change their color and size with the right panel of the window. The graph is given unfiltered by the server to the client, and you can then customize what to render and how to render it.
The panel on the right side of the graph page allows to stop the animation (the checkbox at the bottom) and also to customize
the rendering. This is done by customizing javascript callback functions that are called by the rendering engine. Click the Refresh button
to make your changes live.
For instance in the confirmNode function, you can add the following code to only accept gavs containing the string "my.groupIds' :
if( gav.indexOf( "my.groupIds" ) uses `pom-explorer-core` to perform a maven project analysis gradle and npm projects暂无开放 Issues,或尚未同步最近议题。