geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2430) Correct M2 POMs for Geronimo 1.1.1
Date Thu, 28 Sep 2006 08:57:52 GMT
    [ ] 
Jason Dillon commented on GERONIMO-2430:

Why were m2 poms published for G builds that are not using m2?  That is really confusing to
me.  Who is maintaining those poms?

I would suggest that if you need to depend on G 1.1.x then you should setup a legacy repository
and depend on the m1 generated artifacts.

And... well, isn't 1.1.1 out the door?  Its artifacts are part of the release and we should
not just go and change them... ya even if they are broken.  Changing released artifacts in
this manner will only confuse the problem even more.  If the artifacts need to be fixed, then
we should make a new release.

> Correct M2 POMs for Geronimo 1.1.1
> ----------------------------------
>                 Key: GERONIMO-2430
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.1.1
>            Reporter: Aaron Mulder
>         Assigned To: Jason Dillon
>            Priority: Critical
>             Fix For: 1.1.1
>         Attachments: geronimo-kernel-1.1.1.pom, geronimo-schema-1.0.pom, specs-1.1.1.pom
> The geronimo-kernel-1.1.1 POM has a typo (<type>test</type>) that causes
M2 builds including it to fail.
> There are two POMs that are referenced by other POMs but not actually present in the
M2 repo, which also causes M2 builds including common parts of Geronimo to fail (specs-1.1.1.pom,
> Bottom line, nearly any M2 build using Geronimo 1.1.1 will fail without manually applying
these POMs to the local M2 repo.
> The corrected kernel POM and missing other POMs are attached -- hopefully we can get
them distributed somehow.

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