geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1672) Migrate security module to M2
Date Tue, 07 Mar 2006 17:57:41 GMT
    [ ] 

Henri Yandell commented on GERONIMO-1672:

Security was building fine for me yesterday :)

M2 Build:

Top level pom has a dependenciesManagement section. This sets up a pool of dependencies for
the multiproject, but does not make them actual dependencies - it allows for the version handling
to be in one place.

Sublevel poms then have dependencies in which they refer to elements in the top level pom
- and don't need the version specified.

A common problem (for me anyway) is to run mvn package in the module, having changed the top
level pom, and not have it see the new dependenciesManagement dependency. Then I remember
I have to go back up to the top, run mvn -N install to put the pom in my local repository
and then go back to the sub module.

Things got a lot easier once that clicked

> Migrate security module to M2
> -----------------------------
>          Key: GERONIMO-1672
>          URL:
>      Project: Geronimo
>         Type: Task
>   Components: security
>     Versions: 1.x
>  Environment: All
>     Reporter: Anita Kulshreshtha
>     Assignee: Anita Kulshreshtha
>      Fix For: 1.x
>  Attachments: pom.patch

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message