Re: Maven release conventions?
Nope, using the maven-release-plugin [1] would be enough as it takes care of checking/changing versions both in the dependencies (if there is any -SNAPSHOT dependency) and in the modules' versions. A very quickly look at the process goes like running mvn release:prepare which signs artifact, creating a svn tag with the release version and preparing the poms for the next development version, then if the RC is ok run mvn release:perform otherwise if there is any problem run mvn release:rollback to bring back the trunk to the -SNAPSHOT version. One more nice thing would be to add the apache-pom as parent pom of our manifoldcf-parent: parent groupIdorg.apache/groupId artifactIdapache/artifactId version9/version relativePath / /parent this will allow using the -Papache-release option (enabling the apache-release profile) to create reports and sign artifacts. Hope this helps. Tommaso 2011/9/8 Karl Wright daddy...@gmail.com Hi folks, I'm handling the 0.3-incubating release of MCF, and I'm trying to figure out what the version tags in the maven pom files should say. They currently say 0.3-SNAPSHOT. Should I edit them in the release branch to be just 0.3? Karl
Re: Maven release conventions?
Thanks for the answers. This would all be fine if maven were the primary build mechanism for ManifoldCF, but it is not at this time, for many reasons. From your description the pom's should remain -SNAPSHOT in the release if this is the case, no? Also, is there any way to have it not change anything other than the pom's themselves? I don't want maven to create svn tags etc. Karl On Thu, Sep 8, 2011 at 2:58 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: Nope, using the maven-release-plugin [1] would be enough as it takes care of checking/changing versions both in the dependencies (if there is any -SNAPSHOT dependency) and in the modules' versions. A very quickly look at the process goes like running mvn release:prepare which signs artifact, creating a svn tag with the release version and preparing the poms for the next development version, then if the RC is ok run mvn release:perform otherwise if there is any problem run mvn release:rollback to bring back the trunk to the -SNAPSHOT version. One more nice thing would be to add the apache-pom as parent pom of our manifoldcf-parent: parent groupIdorg.apache/groupId artifactIdapache/artifactId version9/version relativePath / /parent this will allow using the -Papache-release option (enabling the apache-release profile) to create reports and sign artifacts. Hope this helps. Tommaso 2011/9/8 Karl Wright daddy...@gmail.com Hi folks, I'm handling the 0.3-incubating release of MCF, and I'm trying to figure out what the version tags in the maven pom files should say. They currently say 0.3-SNAPSHOT. Should I edit them in the release branch to be just 0.3? Karl
[jira] [Commented] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100504#comment-13100504 ] Emmanuel Keller commented on CONNECTORS-240: Sorry, I am a little bit late. I hope you can wait one more day. I will be able to provide the documentation tomorrow morning. Thanks for your patience! OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-240) OpenSearchServer connector needs end-user documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100509#comment-13100509 ] Karl Wright commented on CONNECTORS-240: I put together an RC0, but have not yet called a vote. If you can contribute the documentation by tomorrow, I'll spin an RC1 after it's merged. OpenSearchServer connector needs end-user documentation --- Key: CONNECTORS-240 URL: https://issues.apache.org/jira/browse/CONNECTORS-240 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.3 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.3 Attachments: oss-mfc-site.patch We need end-user documentation for the OpenSearchServer connector -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: 0.3-incubating RC0 available for inspection
Hello. I tested sharedrive connector/ authority connector on 0.3RC0 and confirmed changes. It worked well. BTW, ant run-script-engine-tests said build failed. The same error is in trunk . Is it okay? Regards, Shinichiron Abe On 2011/09/08, at 8:17, Karl Wright wrote: You can find it here: http://people.apache.org/~kwright/apache-manifoldcf-0.3-incubating/ There have been a number of significant changes this release, so I think it's a good idea if at least one other person has a thorough look at it. Karl
[jira] [Created] (CONNECTORS-251) jcifs.jar download
jcifs.jar download -- Key: CONNECTORS-251 URL: https://issues.apache.org/jira/browse/CONNECTORS-251 Project: ManifoldCF Issue Type: Improvement Components: JCIFS connector Affects Versions: ManifoldCF next Reporter: Shinichiro Abe Priority: Minor Fix For: ManifoldCF next Attachments: CONNECTORS-251.patch jcifs.jar should be downloaded automatically at jcifs/build.xml as a approach similar to pom.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
