[
https://issues.apache.org/jira/browse/JAMES-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Knecht resolved JAMES-1335.
---------------------------------
Resolution: Fixed
> Merge project/pom.xml and project/project/pom.xml
> -------------------------------------------------
>
> Key: JAMES-1335
> URL: https://issues.apache.org/jira/browse/JAMES-1335
> Project: JAMES Server
> Issue Type: Task
> Affects Versions: Trunk
> Reporter: Felix Knecht
> Assignee: Felix Knecht
> Priority: Minor
>
> ATM all modules are referencing james-project as parent pom whereas
> james-project references james-parent as parent pom.
> Merging current james-project.pom into current james-parent.pom, renaming
> current james-parent.pom to james-project.pom, moving the project site
> documentation from project/project to project is probably the easiest way and
> will (AFAICS) not need any changes in all the other James modules.
> We can still after this refactoring decide
> a) What shall happen with the legacy code of server 2.x
> (project/project/server) which is still in the tree but not anymore
> referenced as module by any pom.xml
> b) If dependencyManagement / pluginManagement shall become part of the TLP
> pom or not
> See also discussion on
> http://www.mail-archive.com/[email protected]/msg36344.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
