You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2011/06/24 08:40:51 UTC

[jira] [Issue Comment Edited] (DIRSHARED-129) Push shared-i18n-1.0.0-M5 artifact to Apache releases repository

    [ https://issues.apache.org/jira/browse/DIRSHARED-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054261#comment-13054261 ] 

Pierre-Arnaud Marcelot edited comment on DIRSHARED-129 at 6/24/11 6:39 AM:
---------------------------------------------------------------------------

There's no mistake anywhere.

The move to version 1.0.0-M5 was mandatory to cut the release, have a tagged version of the code in SVN and the installers ready for the release vote

Our Jenkins/Continuum tasks were probably run between the short period of time the build stayed with version 1.0.0-M5 (less than a day from the commit logs).

That said, how about depending on 2.0.0-M2-SNAPSHOT for ApacheDS since you were depending on 1.5.8-SNAPSHOT ?

1.5.8-SNAPSHOT won't evolve anymore now...

      was (Author: pamarcelot):
    There's no mistake anywhere.

The move to version 1.0.0-M5 was mandatory to cut the release, have a tagged version of the code in SVN and the installers ready for the release vote

Our Jenkins/Continuum tasks were probably run between the short period of time the build stayed with version 1.0.0-M5 (less than a day from the commit logs).

That said, how about depending on 1.0.0-M6-SNAPSHOT since you were depending on 1.5.8-SNAPSHOT ?

1.5.8-SNAPSHOT won't evolve anymore now...
  
> Push shared-i18n-1.0.0-M5 artifact to Apache releases repository
> ----------------------------------------------------------------
>
>                 Key: DIRSHARED-129
>                 URL: https://issues.apache.org/jira/browse/DIRSHARED-129
>             Project: Directory Shared
>          Issue Type: Task
>            Reporter: Aleksander Adamowski
>
> ApacheDS server snapshots have started using shared-* artifacts version 1.0.0-M5 through the new parent POM from 22 June:
> https://repository.apache.org/content/repositories/snapshots/org/apache/directory/server/apacheds-parent/1.5.8-SNAPSHOT/apacheds-parent-1.5.8-20110622.155135-270.pom
> The POM specifies:
> <!-- Set versions for depending projects -->
> <org.apache.directory.shared.version>1.0.0-M5</org.apache.directory.shared.version>
> However, the 1.0.0-M5 version has not been released to the Apache releases Maven repository: 
> https://repository.apache.org/content/repositories/releases/org/apache/directory/shared/shared-i18n/
> despite the fact that shared snapshots have moved on to 1.0.0-M6-SNAPSHOT version:
> https://repository.apache.org/content/repositories/snapshots/org/apache/directory/shared/shared-i18n/1.0.0-M6-SNAPSHOT/
> This broke the build for anything dependent on apacheds server snapshots:
> The following artifacts could not be resolved: org.apache.directory.shared:shared-i18n:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-extras-aci:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-extras-trigger:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-extras-util:jar:1.0.0-M5, org.apache.directory.shared:shared-asn1-ber:jar:1.0.0-M5, org.apache.directory.shared:shared-asn1-api:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-extras-sp:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-codec-core:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-extras-codec:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-model:jar:1.0.0-M5, org.apache.directory.shared:shared-util:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-client-api:jar:1.0.0-M5, org.apache.directory.shared:shared-dsml-engine:jar:1.0.0-M5, org.apache.directory.shared:shared-ldap-schema-data:jar:1.0.0-M5: Could not find artifact org.apache.directory.shared:shared-i18n:jar:1
 .0.0-M5
> Please, release shared 1.0.0-M5 artifacts to the official Apache releases repo ASAP.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira