Re: [NOTICE] Release TLP POM 32
I have released the project. Now to release Mavibot, Shared and Apacheds :-) Le 29/06/2014 07:33, Emmanuel Lécharny a écrit : Hi devs, I'd like to release a new project pom (version 32). Changes [1]: Bumped up plugin revisions for : maven-deploy-plugin 2.7 - 2.8.1 maven-enforcer-plugin 1.0.1 - 1.3.1 maven-gpg-plugin 1.4 - 1.5 maven-install-plugin 2.4 - 2.5.1 maven-jar-plugin 2.4 - 2.5 maven-javadoc-plugin 2.8 - 2.9.1 maven-jxr-plugin 2.3 - 2.4 maven-release-plugin 2.4.1 - 2.5 maven-shade-plugin 2.1 - 2.3 maven-surefire-report-plugin 2.15 - 2.17 maven-surefire-plugin 2.15 - 2.17 maven-bundle-plugin 2.3.7 - 2.5.0 apache-rat-plugin 0.9 - 0.10 findbugs-maven-plugin 2.3.2 - 2.5.4 The tagged pom can be found at [2], the staging repository can be found at [3]. I'll continue to release the staging repository after the grace period of 4 hours. Regards, Emmanuel [1] - http://svn.apache.org/viewvc/directory/project/trunk/pom.xml?rev=1606388r1=1606387r2=1606388view=diff [2] - http://svn.apache.org/epos/asf/directory/project/tags/32 [3] - https://repository.apache.org/content/repositories/orgapachedirectory-1005/
Re: Release issues...
What a pain in the ass this release plugin can be !!!
I still have the exact same error I had yesterday, even if I was able to
release project.
I have attached the error I get when I run mvn release:prepare.
I have also set my /etc/hosts to point to the US mirror, to no avail.
If anyone has an idea on what's going on and how to fix it, it would be
very appreciated !
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Maven home: /opt/maven/apache-maven-3.2.1
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: mac os x, version: 10.9.3, arch: x86_64, family: mac
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
/opt/maven/apache-maven-3.2.1/conf/settings.xml
[DEBUG] Reading user settings from /Users/elecharny/.m2/settings.xml
[DEBUG] Using local repository at /Users/elecharny/.m2/repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
/Users/elecharny/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=2,
ConflictMarker.markTime=1, ConflictMarker.nodeCount=197,
ConflictIdSorter.graphTime=1, ConflictIdSorter.topsortTime=0,
ConflictIdSorter.conflictIdCount=51, ConflictIdSorter.conflictIdCycleCount=0,
ConflictResolver.totalTime=15, ConflictResolver.conflictItemCount=114,
DefaultDependencyCollector.collectTime=342,
DefaultDependencyCollector.transformTime=20}
[DEBUG] org.apache.felix:maven-bundle-plugin:jar:2.5.0:
[DEBUG]biz.aQute.bnd:bndlib:jar:2.3.0:compile
[DEBUG] org.osgi:org.osgi.core:jar:4.3.1:compile
[DEBUG]org.apache.felix:org.apache.felix.bundlerepository:jar:1.6.6:compile
[DEBUG] org.easymock:easymock:jar:2.4:compile
[DEBUG]org.apache.felix:org.apache.felix.utils:jar:1.6.0:compile
[DEBUG] org.osgi:org.osgi.compendium:jar:4.2.0:compile
[DEBUG]org.apache.maven:maven-core:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-settings:jar:2.0.7:compile
[DEBUG]
org.apache.maven:maven-plugin-parameter-documenter:jar:2.0.7:compile
[DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-profile:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-model:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.7:compile
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG] junit:junit:jar:3.8.1:compile
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-project:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0.7:compile
[DEBUG] commons-cli:commons-cli:jar:1.0:compile
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-plugin-descriptor:jar:2.0.7:compile
[DEBUG]
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:compile
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.7:compile
[DEBUG] org.apache.maven:maven-monitor:jar:2.0.7:compile
[DEBUG] classworlds:classworlds:jar:1.1:compile
[DEBUG]org.apache.maven:maven-archiver:jar:2.5:compile
[DEBUG] org.codehaus.plexus:plexus-archiver:jar:2.1:compile
[DEBUG] org.codehaus.plexus:plexus-io:jar:2.0.2:compile
[DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.15:compile
[DEBUG]org.apache.maven.shared:maven-dependency-tree:jar:2.1:compile
[DEBUG] org.codehaus.plexus:plexus-component-annotations:jar:1.5.5:compile
[DEBUG] org.eclipse.aether:aether-util:jar:0.9.0.M2:compile
[DEBUG]org.codehaus.plexus:plexus-utils:jar:3.0.10:compile
[DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.0:compile
[DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.0:compile
[DEBUG] org.apache.maven.doxia:doxia-core:jar:1.0:compile
[DEBUG] org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:compile
[DEBUG] org.codehaus.plexus:plexus-velocity:jar:1.1.7:compile
[DEBUG] org.apache.velocity:velocity:jar:1.5:compile
[DEBUG] commons-lang:commons-lang:jar:2.1:compile
[DEBUG] oro:oro:jar:2.0.8:compile
[DEBUG] org.apache.maven.doxia:doxia-decoration-model:jar:1.0:compile
[DEBUG] commons-collections:commons-collections:jar:3.2:compile
[DEBUG] org.apache.maven.doxia:doxia-module-apt:jar:1.0:compile
[DEBUG] org.apache.maven.doxia:doxia-module-fml:jar:1.0:compile
[DEBUG] org.apache.maven.doxia:doxia-module-xdoc:jar:1.0:compile
[DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.0:compile
[DEBUG] Created new class realm maven.api
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: org.apache.maven.wagon.events
Re: Release issues...
On 06/29/2014 02:13 PM, Emmanuel Lécharny wrote: What a pain in the ass this release plugin can be !!! I still have the exact same error I had yesterday, even if I was able to release project. I have attached the error I get when I run mvn release:prepare. I have also set my /etc/hosts to point to the US mirror, to no avail. If anyone has an idea on what's going on and how to fix it, it would be very appreciated ! You are on OSX? I remember that there were/are issues that /etc/hosts has lower priority than DNS resulution. What do $ host svn.apache.org $ host svn.us.apache.org $ host svn.eu.apache.org return? Maybe try to change the scm URLs in pom.xml, explicitely use svn.us.apache.org for developerConnection. Kind Regards, Stefan
Re: Git ?
On 06/27/2014 01:02 PM, Kiran Ayyagari wrote: On Fri, Jun 27, 2014 at 2:31 PM, Emmanuel Lécharny elecha...@gmail.com I have a small concern regarding the studio repo, as it includes binaries from various Eclipse versions, the .git directory of the current git-mirror is 700 MB. That means when cloning the studio git repo on has to download the full 700 MB. That’s indeed a big concern. I’d be tempted to have that in another repository, that we can even use online as a real maven repository. Without requiring us to have it checked out on our computers. Would Tycho solve this issue ? Yes, with Tycho we'd download the artifacts directly from the P2 repository. Otherwise, we can probably avoid migrating all the history, in order to avoid loading hundreds of megabytes. I'd be ok to drop history of the repository folder which contains all the binaries. But I really like to keep the full history of the source, this is essential when looking why things were implemented in a certain way, e.g. when fixing bugs. In any case, at some point, we should find a way to access to those bins by other means than having them in SVN. This is just overkilling. +1 setting up Studio workspace is already complicated(I have recently tried but it is taking more time to setup than the time it took to implement a fix, so my fix is still lying there waiting to be tested) If your patch is applied you can also run mvn install from command line, the Studio binary for you platform should then be present in application/application-your platform/target/ApacheDirectoryStudio-your platform/ so -1 to move Studio to git until we find a solution to keep the binary jars out of the repo. So we have to ask if it is possible to migrate subproject by subproject. Or we have to wait till Studio is cleaned up. Kind Regards, Stefan
Re: Release issues...
Le 29/06/2014 14:37, Stefan Seelmann a écrit : On 06/29/2014 02:13 PM, Emmanuel Lécharny wrote: What a pain in the ass this release plugin can be !!! I still have the exact same error I had yesterday, even if I was able to release project. I have attached the error I get when I run mvn release:prepare. I have also set my /etc/hosts to point to the US mirror, to no avail. If anyone has an idea on what's going on and how to fix it, it would be very appreciated ! You are on OSX? I remember that there were/are issues that /etc/hosts has lower priority than DNS resulution. What do $ host svn.apache.org $ host svn.us.apache.org $ host svn.eu.apache.org return? Maybe try to change the scm URLs in pom.xml, explicitely use svn.us.apache.org for developerConnection. I realized, checking the pom.xml, that it was containing references to /tags/1.0.0-M5 instead of /trunk. That explains the failures... Having changed it, it now works !
Re: Git ?
Le 29/06/2014 14:49, Stefan Seelmann a écrit : On 06/27/2014 01:02 PM, Kiran Ayyagari wrote: On Fri, Jun 27, 2014 at 2:31 PM, Emmanuel Lécharny elecha...@gmail.com I have a small concern regarding the studio repo, as it includes binaries from various Eclipse versions, the .git directory of the current git-mirror is 700 MB. That means when cloning the studio git repo on has to download the full 700 MB. That’s indeed a big concern. I’d be tempted to have that in another repository, that we can even use online as a real maven repository. Without requiring us to have it checked out on our computers. Would Tycho solve this issue ? Yes, with Tycho we'd download the artifacts directly from the P2 repository. So we defitively have to switch to Tycho... Otherwise, we can probably avoid migrating all the history, in order to avoid loading hundreds of megabytes. I'd be ok to drop history of the repository folder which contains all the binaries. But I really like to keep the full history of the source, this is essential when looking why things were implemented in a certain way, e.g. when fixing bugs. Sure. The key is that anyone should be able to build from the sources. However, I don't think we will face a pb here. We just have to migrate all the sources from SVN to GIT, except the binaries, and we keep the existing SVN content for those wanting to build the previous releases. That should fly. The question is : should we release Studio *before* going to Git ? so -1 to move Studio to git until we find a solution to keep the binary jars out of the repo. So we have to ask if it is possible to migrate subproject by subproject. Or we have to wait till Studio is cleaned up. I don't think it's a problem to migrate only some subprojects. I'll double check.
[VOTE] Release Apache Mavibot 1.0.0-M5
Hi ! This is the first release of Apache Mavibot, the MVCC BTree in Java ! This milestone is the fifth step toward a complete MVCC implementation. The main added features are : - bulk load implementation - subtrees handling Some other fixes have been applied, and some preliminary work toward transaction support and free pages management. The tests done on bulk load shows good performances so far : we can load 30 000 entries in around 20 seconds (1500/s). So let's vote now ! The revision : http://svn.apache.org/r1606519 The SVN tag: https://svn.apache.org/repos/asf/directory/mavibot/tags/1.0.0-M5/ The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1006/ Please cast your votes: [ ] +1 Release Mavibot 1.0.0-M5 [ ] 0 abstain [ ] -1 Do not release Mavibot 1.0.0-M5 Emmanuel
[VOTE] Release of LDAP API 1.0.0-M23
Hi, This is a vote for the 23th milestone of the 1.0.0 LDAP API/Shared, 1.0.0-M23. It's a bug fix release. It contains a few bug fixes and improvements, and some feature added by Lucas (Templating for LdapConnection) : Bugs * [DIRAPI-190 https://issues.apache.org/jira/browse/DIRAPI-190] - Search request time limit should override connection timeout * [DIRAPI-192 https://issues.apache.org/jira/browse/DIRAPI-192] - Rdn.escapeValue() should not escape unicode characters Improvement --- * [DIRAPI-168 https://issues.apache.org/jira/browse/DIRAPI-168] - Create an LdapConnectionFactory that is not pooled to create LdapConnection objects for an LdapConnectionConfig The revision : http://svn.apache.org/r1606612 The SVN tag: http://svn.apache.org/repos/asf/directory/shared/tags/1.0.0-M23 The source and binary distribution packages: http://people.apache.org/~elecharny/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1007 Please cast your votes: [ ] +1 Release Shared/LDAP API 1.0.0-M23 [ ] 0 abstain [ ] -1 Do not release Shared/LDAP API 1.0.0-M23 Emmanuel -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
