you just add the relocation info to the old poms pointing to the new ones
On 6/27/06, Stefan Hübner <[EMAIL PROTECTED]> wrote:
Hi there,
in our company we successfully introduced Maven2 for a fair lot of
modules. We didn't define conventions on group- and artifact-Ids in
the early days of adoption. Thus, those artifacts are somewhat spread
over our internal repository and I would like to reorganize them by
giving them nice hierarchical groupIds.
Studying the POM-structure there's a relocation-Element inside
distributionManagemet, which can be used to expose the new location of
an artifact.
But how do I populate that information the right way?
I came up with this steps:
1) get the artifact's regarding version from SCM
2) add the relocation-info to its POM
3) deploy the artifact
4) change the groupId of the POM to meet our new conventions
5) remove the relocation-element
6) deploy the artifact again (now to its new location)
This looks a bit odd to me, though. Is there any other (smarter) way
of relocating artifacts in a repository?
Cheers,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
