[
https://issues.apache.org/jira/browse/DIRSHARED-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056578#comment-13056578
]
Pierre-Arnaud Marcelot commented on DIRSHARED-129:
--------------------------------------------------
Hi Aleksander,
Indeed, I had you in mind. It was a hint to help you resolve the issue. ;)
We have a ML hooked up to our SVN repository where each new commit triggers a
mail to be sent.
The ML is [email protected], and you can subscribe to it by sending
a mail to: [email protected] .
Following our Dev list is probably also a good idea.
For more information about our MLs, have a look here:
http://directory.apache.org/community%26resources/mailing-lists-and-irc.html
We are aware and sorry about the fact that we sometimes "force" our users to
rely on a SNAPSHOT branch.
Moving forward to 2.0 is not an easy path and it requires a lot of time and
effort given the relative small size of the Apache Directory team (we greatly
appreciate any help by the way).
That's why we decided to go for milestone releases. Version 2.0.0-M1 being the
first one.
That should give our users a clearer vision of the development of ApacheDS 2.0
and will probably help them avoid depending on a moving target.
However, it is important to keep in mind that these milestone releases are not
official and certainly not final releases (nor betas).
They are just important incremental steps towards the release of 2.0 and should
not been considered bug-free.
If your application is working fine using version 2.0.0-M1, then I think you
should probably depend on this version, to avoid breaking your build later when
we change something.
> 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
