You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Dave Brondsema (JIRA)" <ji...@codehaus.org> on 2005/10/27 14:33:12 UTC

[jira] Commented: (MNG-1340) antlib doesn't check SNAPSHOTs

    [ http://jira.codehaus.org/browse/MNG-1340?page=comments#action_49372 ] 

Dave Brondsema commented on MNG-1340:
-------------------------------------

I deploy with:

<artifact:deploy file="${dist.home}/${app.name}.${jar.dist.suffix}">
	<remoteSnapshotRepository refid="jar.repo.cu" />
	<pom refid="jar.pom" />
</artifact:deploy>

The repository's maven-metadata.xml has:
<metadata>
  <groupId>edu.cornerstone.portal.eforms</groupId>
  <artifactId>eforms</artifactId>
  <version>1.0-SNAPSHOT</version>
  <versioning>
    <snapshot>
      <buildNumber>89</buildNumber>
    </snapshot>
    <lastUpdated>20051025124212</lastUpdated>
  </versioning>
</metadata>

The local repository of the box that deployed the artifact has the same
contents in maven-metadata-remote.xml

However, when other users download the artifact from the repository
their maven-metadata-remote.xml does not have any <versioning> tags.

Thanks,
Dave

Brett Porter wrote:

>> How were the snapshots deployed? The mechanism now relies on the
>> correct management of maven-metadata.xml.
>> 
>> - Brett
>> 
>> On 10/24/05, Dave Brondsema <da...@brondsema.net> wrote:
>> 
>
>>>>I have an ant task to download all the jar artifacts but it won't
>>>>download new SNAPSHOTs if there is already a snapshot in the local user
>>>>repository.
>>>>
>>>>The relavant parts of my ant build file:
>>>>
>>>><artifact:remoteRepository id="jar.repo.cu" url="${jar.repo.cu.url}"
>>>>layout="default">
>>>>        <snapshots updatePolicy="always" />
>>>></artifact:remoteRepository>
>>>>
>>>><artifact:dependencies verbose="true" useScope="compile"
>>>>filesetId="jar.libs.fileset">
>>>>        <pom refid="jar.pom" />
>>>>        <remoteRepository refid="jar.repo.suppl" />
>>>>        <remoteRepository refid="jar.repo.cu" />
>>>>        <remoteRepository refid="jar.repo.m2" />
>>>></artifact:dependencies>
>>>>
>>>>
>>>>
>>>>And the dependencies that are declared like this:
>>>><dependency>
>>>>  <groupId>edu.cornerstone.portal.jsf-utilities</groupId>
>>>>  <artifactId>jsf-utilities</artifactId>
>>>>  <version>1.0-SNAPSHOT</version>
>>>></dependency>
>>>>
>>>>
>>>>According to my apache logs (which serves the repository at
>>>>${jar.repo.cu.url}) maven never accesses the repository.

> antlib doesn't check SNAPSHOTs
> ------------------------------
>
>          Key: MNG-1340
>          URL: http://jira.codehaus.org/browse/MNG-1340
>      Project: Maven 2
>         Type: Bug
>   Components: maven-artifact-ant
>     Versions: 2.0
>     Reporter: Dave Brondsema

>
>
> The antlib tasks do not check all specified repositories for newer versions of SNAPSHOT dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org