That's other story and we can solve it if you provide the right
metadata in http://jira.codehaus.org/browse/MEV
On 10/7/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
Even though I was able to update and correct the artifact's
maven-metadata.xml (plus correct checksums)[1]? It would be nice to at
least have this correct, so that the release version points to the
latest version, rather than the oldest.
-Nathan
[1] http://repo1.maven.org/maven2/xerces/xercesImpl/maven-metadata.xml
On 10/6/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> Remove the one in the m2-ibiblio-sync directory
>
> On 10/7/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
> > I deployed Xerces to m2 and then did a legacy deploy to m1. Should I
> > clear out the legacy deploy?
> >
> > Thanks,
> > -Nathan
> >
> > On 10/6/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > > sorry, I forgot, if you build with ant you deploy to the m1 repo. The
> > > m2 is only for m2 builds because it's more accurate and has some
> > > metadata.
> > >
> > > Files deployed to any of the repos will be available to both m1 and m2
> > > users, so just deploy to one of them.
> > >
> > > On 10/6/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> > > > Nathan Beyer wrote:
> > > >
> > > > > Xerces doesn't build with either Maven 1 or Maven 2; everything is
> > > > > built with a custom Ant script. I created a custom POM and deployed
> > > > > using deploy:deploy-file for the binary and source JAR to m2 and then
> > > > > to m1 by setting the repo type to legacy.
> > > > >
> > > > > I essentially duplicated what exists for Xerces 2.8.0 (it's in both
> > > > > repos). I just updated the POM to reference the latest parent and
> > > > > added some more reference information. Consumers requested these
> > > > > deployments for m2 and I assume some people would want the m1 repo as
> > > > > well.
> > > > >
> > > > > What's the prescribed thing to do? The documentation isn't great and
> > > > > what exists seems to conflict and when I posted a question on this
> > > > > list earlier responses weren't necessarily conflicting, but they
> > > > > differed.
> > > >
> > > > I've meanwhile learned from Brett , that if you deploy to the M2 repo,
this
> > > > is automatically also available for M1.
> > > >
> > > > But I have also the problem, if you have stuffed the same artifact into
the
> > > > M1 & M2 repo and they were synched ... what should I do to resolve this?
> > > > Remove the artifact from the M1 repo and request again for a sync?
> > > >
> > > > - Jörg
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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]
> > >
> > >
> >
>
>
> --
> 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]
>
>
--
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]
