You can test a build generated by our CI :
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/

Arnaud

On 9/9/06, Todd Nine <[EMAIL PROTECTED]> wrote:

Sure did, here's the settings.xml I'm using

Also, this seems to be a bug, I've found this issue in Jira

http://jira.codehaus.org/browse/MNG-1928

It says its been fixed for Maven 2.0.5, is it stable enough for me to
build
with if I compile it from CVS?

Todd


    <profile>
            <id>default</id>
            <properties>
                 <jboss_home_dir>C:\development\server\jboss-3.2.6
</jboss_home_dir>

<installDir>C:\development\server\integrationserver</installDir>
                 <winntcvs>true</winntcvs>
            </properties>
            <repositories>
                <repository>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <id>ata-release</id>
                    <name>ATA Internal Project Repository</name>
                    <!--
<url>scpexe://sun10.ata.com:/a01/proj/Maven2/repository</url>-->
                    <url>
                        http://sun10.ata.com:9200/Maven2/repository
                    </url>
                    <layout>default</layout>

                </repository>
                <repository>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>

                    <id>ata-snapshot</id>
                    <name>
                        ATA Internal Project Repository Snapshots
                    </name>

<!--<url>scpexe://sun10.ata.com:/a01/proj/Maven2/repository</url>-->
                    <url>http://sun10.ata.com:9200/Maven2/snapshot</url>
                    <layout>default</layout>

                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <id>ata-plugin-repository</id>
                    <name>ATA Plugin snapshot</name>
                    <url>

http://sun10.ata.com:9200/Maven2/plugins/repository
                    </url>
                    <layout>default</layout>
                </pluginRepository>

                <pluginRepository>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                    <id>ata-plugin-snapshot</id>
                    <name>ATA Plugin snapshot</name>
                    <url>
                        http://sun10.ata.com:9200/Maven2/plugins/snapshot
                    </url>
                    <layout>default</layout>
                </pluginRepository>
            </pluginRepositories>
        </profile>




On 9/8/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> Did they define a pluginRepository to download it where you deployed it
?
>
http://maven.apache.org/maven-settings/settings.html#class_pluginRepository
>
>
> Arnaud
>
> On 9/9/06, Todd Nine <[EMAIL PROTECTED]> wrote:
> >
> > Hi all,
> >   I've submitted a patch for the release plugin for maven.  I've built
> the
> > plugin and installed it to my local repository, however everyone else
> > receives the following error when they try to download it.
> >
> > Downloading:
> > http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl
> > ugins/maven-release-plugin/2.0-beta-5-20060908/maven-
> > release-plugin-2.0-beta-5-2
> > 0060908.pom
> > Downloading:
> > http://sun10.ata.com:9200/Maven2/plugins/repository/org/apache/mave
> > n/plugins/maven-release-plugin/2.0-beta-5-20060908/maven-
> > release-plugin-2.0-beta
> > -5-20060908.jar
> > 78K downloaded
> >
> > As you can see, it tries to download the pom from ibiblio, where it
> > definately won't be, then pulls the jar from our local plugin
> repository.
> > Why doesn't it download the pom from our local repository?  Is this a
> bug,
> > or did I miss a step in building the plugins?  I used the default
> > release:prepare, release:perform to perform the release.
> >
> > Thanks,
> > Todd
> >
> >
>
>


Reply via email to