it's just a matter that deploy:deploy-file does not work very well, I
think almost everybody just copies the things by hand when not
building with maven
The problem with metadata is a known problem that we'll try to solve soon
On 10/7/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
Okay, I've clean
Okay, I've cleaned up the m2 sync repo. Please sync the m1 repo.
BTW - Maybe I'm just not getting it, but it seems very odd that I use
Maven 2 with a v4.0.0 POM and perform a deploy:deploy-file using
legacy style to the m1 sync repo, then do a manual upload of source
JARs to the m1 sync repo (leg
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
l
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/xercesImp
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
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 h
why would ever the jars differ?
remove the sutff in m2, it hasn't been synced to ibiblio
On 10/7/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Carlos Sanchez 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 h
Carlos Sanchez 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.
Yes, but
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 PROTECTE
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 dupl
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.
you shouldn't deploy to both places. Deploy to m2 only if you build with m2.
On 10/6/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
I've deployed the latest Xerces release, v2.8.1 to the m1 and m2 sync
folders. Please run the rsync when you can.
Thanks,
-Nathan
--
I could give you my word
I've deployed the latest Xerces release, v2.8.1 to the m1 and m2 sync
folders. Please run the rsync when you can.
Thanks,
-Nathan
13 matches
Mail list logo
