History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEABKL-5151
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Vladislav Kaznacheev
Reporter: Bryan Dollery
Votes: 0
Watchers: 0
Available Workflow Actions

Mark as Stalled
Operations

If you were logged in you would be able to see more operations.
IDEA: Backlog

Generate POM

Created: 06 Jun 07 21:06   Updated: 13 Jun 07 17:29
Component/s: Maven Integration
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Build: 6,981
Severity: Low


 Description  « Hide
I work in an environment where everyone else has the misfotune to use Eclipse. It would be really useful if I could generate a detailed POM based on my Idea project files. Then we can use that to share project files using project generation.

 All   Comments   Work Log   Change History      Sort Order:
Vladislav Kaznacheev - 07 Jun 07 21:13
There are many features of IDEA projects that cannot be correctly mapped to Maven pom.xml:
  • multiple content roots
  • cyclical dependencies
  • project and global libraries

For an environment like yours I would suggest using Maven as a primary source of project configuration information. Maven Integration plugin is supposed to make your life in IDEA easy.


Bryan Dollery - 13 Jun 07 14:04
Thansk for your answer Vlad, but I'm not convinced. I understand that Idea must support all developers, even those who don't follow the optimal Maven2 patterns, but isn't there a danger here of not providing useful tools for the masses because of a few strange edge cases.

Most developers have no cyclical dependencies. They're evil anyway, and are a profound smell. I wouldn't like to think that I'm being denied a useful tool because of some bizarre edge case that is only truly necessary to only a handful of users.

Most developers follow the default Maven2 model (even though nameing and directory-location often vary), and have only two source roots – src, and test. Those that don't have this structure, are moving towards it, as it is becoming the industry standard. Maven2 directly and simply supports multiple content roots anyway, so this isn't a reason not to generate a POM.

Project and Global libraries. Maven supports this concept through POM inheritance. In this model, the master POM is seen as the project POM, and it contains the project libraries. The module level POMs add in module specific settings, and provide for the concept of module libraries. The Maven2 dependency management facilities remove the need for global libraries. If these exist in a project, they can be generated in a POM as a simple project or module level library.

Maven is rapidly becoming the industry's defacto project modelling tool. I know that we have a few plug-ins that offer some basic support, but I believe that Idea needs to adopt Maven directly ASAP in order to remain competative.


Vladislav Kaznacheev - 13 Jun 07 17:29
Well, this is all theoretically doable, but I am afraid that the POM generated this way would look ugly and "inhuman" (similar to Microsoft Word document saved in HTML format It is so easy to create and reference a global library in IDEA, and think how it is going to look in auto-generated POM.

I agree that the feature looks useful, but given the current state of Maven integration it is unlikely to be addressed in the current release cycle.