maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MRELEASE-252) Support for multi modules project
Date Fri, 20 Mar 2009 10:27:13 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170396#action_170396
] 

Mark Struberg edited comment on MRELEASE-252 at 3/20/09 5:26 AM:
-----------------------------------------------------------------

please note that not all SCMs support tagging of 'partial' trees of a SCM-module. e.g. for
a Git repo a 'tag' always works on the whole repository and not on single files (in fact there
is no such thing like a 'single file' for Git, but only diffs on the whole repository tree)

So you imho have to separate 4 different 'modularisation points'

1.) maven modules
2.) maven dependency structure (sometimes the maven modules do not represent the dependency
structure, especially if more hierarchies are nested)
3.) file structure (how to handle 'flattened out' projects, or parent poms which reside in
an own subdirectory?)
4.) SCM modules

Sadly, this is a really complex area...

      was (Author: struberg):
    please not that not all SCMs support tagging of 'partial' trees of a SCM-module. e.g.
for a Git repo a 'tag' always works on the whole repository and not on single files (in fact
there is no such thing like a 'single file' for Git, but only diffs on the whole repository
tree)

So you imho have to separate 4 different 'modularisation points'

1.) maven modules
2.) maven dependency structure (sometimes the maven modules do not represent the dependency
structure, especially if more hierarchies are nested)
3.) file structure (how to handle 'flattened out' projects, or parent poms which reside in
an own subdirectory?)
4.) SCM modules

Sadly, this is a really complex area...
  
> Support for multi modules project
> ---------------------------------
>
>                 Key: MRELEASE-252
>                 URL: http://jira.codehaus.org/browse/MRELEASE-252
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: perform, prepare, stage
>    Affects Versions: 2.0-beta-6
>         Environment: Maven 2.0.6
>            Reporter: Franck HUGOT
>
> I would like to prepare a release for multi-modules project.
> I would create tags for all the modules and modify poms.
> Not only the versionId in the pom but also the eventual dependencies between all the
modules.
> Indeed, if a module A has a dependency to module B, the version will be updated.
> The dependency management is a hard task in multi modules project and this feature would
be really appreciated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message