[Neo tickets] #128: configure components as modules

neo4j.org noreply at neo4j.org
Mon Nov 10 23:43:47 CET 2008


#128: configure components as modules
---------------------------------+------------------------------------------
 Reporter:  andersn              |        Owner:  johans
     Type:  enhancement request  |       Status:  new   
 Priority:  major                |    Milestone:        
Component:  other                |   Resolution:        
 Keywords:                       |  
---------------------------------+------------------------------------------

Old description:

> Change the configuration of the parent POM of components, so that all
> components can be easily checked out at once using Maven. In Eclipse they
> will be imported as separate projects, it's really handy. See example
> (from Sonatype) importing the Jetty project into Eclipse:
>
> http://vimeo.com/2057706

New description:

 Change the configuration of the parent POM of components, to use the
 modular structure provided by Maven. This has different benefits when
 deploying, building sites and for nesting of modules/components.

 In the Eclipse IDE submodules can be imported as separate projects, it's
 really handy. See example (from Sonatype) importing the Jetty project into
 Eclipse:

 http://vimeo.com/2057706

--

Comment(by andersn):

 AFAIK adding/removing modules in the parent POM will not require any
 version updates of the POM, as module definitions are not inherited anyhow
 (wouldn't make any sense). The version number only needs to be bumped up
 when things that get inherited are changed.

-- 
Ticket URL: <https://trac.neo4j.org/ticket/128#comment:3>
neo4j.org <http://trac.neo4j.org/>
The Neo4J.org Issue Tracker


More information about the Tickets mailing list