Build failed in Hudson: Jackrabbit-trunk-tests-java14 #339
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk-tests-java14/339/changes Changes: [jukka] Upgrade trunk version to 2.1-SNAPSHOT. -- Started by upstream project Jackrabbit-trunk build number 970 Building remotely on minerva.apache.org (Ubuntu) Updating http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-jcr-tests U pom.xml At revision 891596 [locks-and-latches] Checking to see if we really have the locks [locks-and-latches] Have all the locks, build can start + cd jackrabbit-jcr-tests + MAVEN_OPTS=-Xmx128m + /home/hudson/tools/maven/apache-maven-2.0.9/bin/mvn clean install [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.jackrabbit ArtifactId: jackrabbit-parent Version: 2.1-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.jackrabbit:jackrabbit-parent:pom:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.jackrabbit:jackrabbit-parent for project: null:jackrabbit-jcr-tests:jar:null for project null:jackrabbit-jcr-tests:jar:null at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.jackrabbit:jackrabbit-parent for project: null:jackrabbit-jcr-tests:jar:null for project null:jackrabbit-jcr-tests:jar:null at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.jackrabbit:jackrabbit-parent' not found in repository: Unable to download the artifact from any repository org.apache.jackrabbit:jackrabbit-parent:pom:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.apache.jackrabbit:jackrabbit-parent at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366) ... 17 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.jackrabbit:jackrabbit-parent:pom:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:556) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:331) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200) ... 20 more [INFO]
Hudson build became unstable: Jack rabbit-trunk » Jackrabbit Core #971
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/971/changes
Hudson build became unstable: Jackrabbit-trunk #971
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/971/changes
Hudson build is back to stable: Jac krabbit-trunk » Jackrabbit Core #972
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/972/
Hudson build is back to stable: Jackrabbit-trunk #972
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/972/changes
Hudson build is back to normal: Jackrabbit-trunk-tests-java14 #340
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk-tests-java14/340/changes
[VOTE] Release Apache Jackrabbit 2.0-beta5
Hi, A new Jackrabbit 2.0 beta release candidate is available at: http://people.apache.org/~jukka/jackrabbit/2.0-beta5/ See the RELEASE-NOTES.txt file (also included at the end of this message) for details about this release. The release candidate is a zip archive of the sources in: http://svn.apache.org/repos/asf/jackrabbit/tags/2.0-beta5/ The SHA1 checksum of the release package is 6ecc5d8b56bcee90420d71680289bed3cd253066. In addition to the source archive and the main binaries included in the directory linked above, there is also a staged Maven repository containing all the other binary release artifacts: https://repository.apache.org/content/repositories/orgapachejackrabbit-055/ Please vote on releasing this package as Apache Jackrabbit 2.0-beta5. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. [ ] +1 Release this package as Apache Jackrabbit 2.0-beta5 [ ] -1 Do not release this package because... Here's my +1. BR, Jukka Zitting Release Notes -- Apache Jackrabbit -- Version 2.0-beta5 Introduction This is a beta release of Apache Jackrabbit 2.0. This release is a fully compliant implementation of the JCR 2.0 API that was specified by the Java Specification Request 283 (JSR 283, http://jcp.org/en/jsr/detail?id=283). However, the beta status of this release means that some parts of the implementation are not yet ready for normal production use. Changes in this release --- Jackrabbit 2.0 is a major upgrade from the earlier 1.x releases. The most notable changes in this release are: * Upgrade to JCR 2.0. This Jackrabbit release implements and is based on the official JCR 2.0 API. All of the features required by the JSR 283 specification have been implemented. * Upgrade to Java 5. All of Jackrabbit (except the jcr-tests component) now requires Java 5 as the base platform. Java 1.4 environments are no longer supported. * Removal of deprecated classes and features. Jackrabbit 2.0 is not backwards compatible with client code that used any classes or features that had been deprecated during the 1.x release cycle. * Separate JCR Commons components. Many of the general-purpose JCR components like JCR-RMI and OCM are now developed and released separately from the Jackrabbit content repository. See the individual components for their most recent releases. * Database connection pooling is now available for all database backends. * Data store feature enabled in the default repository configuration. * Full text indexing with Apache Tika. Jackrabbit can now extract and index the full text content of many new types of documents, including the Office Open XML files produced by Microsoft Office 2007 and higher. * Apache Commons Collections, Apache Derby, Jetty, SLF4J and Apache Xerces have been upgraded to a more recent version. * OracleFileSystem class does not use special blob handling anymore and is required for 10R1 and earlier anymore. If you need that use the new Oracle9FileSystem. For more detailed information about all the changes in this and other Jackrabbit releases, please see the Jackrabbit issue tracker at https://issues.apache.org/jira/browse/JCR Release Contents This release consists of a single source archive packaged as a zip file. The archive can be unpacked with the jar tool from your JDK installation. See the README.txt file for instructions on how to build this release. The source archive is accompanied by SHA1 and MD5 checksums and a PGP signature that you can use to verify the authenticity of your download. The public key used for the PGP signature can be found at https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS. About Apache Jackrabbit --- Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR). A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more. For more information, visit http://jackrabbit.apache.org/ About The Apache Software Foundation Established in 1999, The Apache Software Foundation provides organizational, legal, and financial support for more than 100 freely-available, collaboratively-developed Open Source projects. The pragmatic Apache License enables individual and commercial users to easily deploy Apache software; the Foundation's intellectual property framework limits the legal exposure of its 2,500+ contributors. For more information, visit http://www.apache.org/
Re: Jackrabbit 2.0 release plan
Hi, On Wed, Dec 16, 2009 at 2:14 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: I think we're ready to create the 2.0 branch and only apply bug fixes and other finishing touches there before the final release. More extensive changes should go into the branch only with a good enough reason why they should be included in 2.0 instead of 2.1. I have now created the 2.0 release branch and updated Jackrabbit trunk version to 2.1-SNAPSHOT. I also added a 2.1.0 version to Jira. I will be tracking Jira and making sure that any commits on issues resolved for the 2.0 release are merged to the release branch. Please only use the 2.0 version in Jira for bug fixes or other changes that for some reason can't wait for 2.1. BR, Jukka Zitting
[jira] Commented: (JCR-642) Support flat content hierarchies
[ https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792009#action_12792009 ] Jeff Yemin commented on JCR-642: Is this issue still under consideration? It's a big issue for our organization, and we are considering whether we need to build a workaround for it or wait for resolution in Jackrabbit itself. Support flat content hierarchies Key: JCR-642 URL: https://issues.apache.org/jira/browse/JCR-642 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-core Reporter: Jukka Zitting The current best practice with Jackrabbit is to avoid flat content structures due to performance concerns. These concerns are caused by the fact that the NodeState implementation requires the list of child node names and identifiers to be available at all times. In fact many (all?) current persistence managers implement this requirement by storing and loading this list as a part of the serialized node state. When this list grows, the performance and memory overhead of managing the list grows as well. As a side note, this also creates potential consistency issues since the parent/child links are stored both within the child list of the parent node and as the parent link of the child node. To solve this issue, I believe we need to break the tight bonding between the node state and the list of child nodes. This will likely require major refactoring of the Jackrabbit core, including breaking the NodeState and PersistenceManager interfaces, so I don't expect a solution in near future. However, we should start thinking about how to best do this, and at least be concerned about building in any more assumptions about the list of child nodes always being readily available. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Jackrabbit 2.0-beta5
Hi, [X] +1 Release this package as Apache Jackrabbit 2.0-beta5 - checksums [OK] - signature [OK] - license, notice, header and readme files [OK] - maven build [OK] with Ubuntu Jaunty / Sun Java 1.6.0_14-b08 I do not test the maven artifacts just the source package and the war. -- Sébastien Launay
[jira] Reopened: (JCR-2439) More utility methods in JcrUtils
[ https://issues.apache.org/jira/browse/JCR-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra reopened JCR-2439: --- sorry, but i saw this issue too late, i would not mix the sequence of arguments in the signatures like in: Node putFile(Node parent, String name, String mime, InputStream data) Node putFile(Node parent, String name, String mime, Calendar date, InputStream data) but rather have: Node putFile(Node parent, String name, String mime, InputStream data) Node putFile(Node parent, String name, String mime, InputStream data, Calendar date) so that optional arguments always come at the end. More utility methods in JcrUtils Key: JCR-2439 URL: https://issues.apache.org/jira/browse/JCR-2439 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-jcr-commons Reporter: Jukka Zitting Assignee: Jukka Zitting Priority: Minor Fix For: 2.0-beta5 I'd like to add at least the following utility methods to JcrUtils: For logging: // Utility method to simplify log messages and debug prints: // Node - name [type] // Property - @name = value(s) String toString(Item item) For making sure that a node exists: // Returns the identified child node. If the child does not already exist, // it is added using the default node type from the parent. Node setNode(Node parent, String name) // Same as above, but ensures that isNodeType(type) is true for the // returned node, using addNode(name, type) or setPrimaryType(type) // if needed. Node setNode(Node parent, String name, String type) For adding (or setting, see above) nt:folder nodes: // Adds a new nt:folder node with the given name Node addFolder(Node parent, String name) // Ensures that an nt:folder node with the given name exists Node setFolder(Node parent, String name) For adding (or setting) nt:file nodes: // Adds a new nt:file/nt:resource structure // If the mime type contains a charset parameter, then the jcr:encoding property is also set Node addFile(Node parent, String name, String mime, InputStream data) Node addFile(Node parent, String name, String mime, Calendar date, InputStream data) // Ensures that an nt:file/nt:resource structure exists with the given data. // Note that the type of a potential existing jcr:content node is not modified Node setFile(Node parent, String name, String mime, InputStream data) Node setFile(Node parent, String name, String mime, Calendar date, InputStream data) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Jackrabbit 2.0-beta5
[X] +1 Release this package as Apache Jackrabbit 2.0-beta5 - checksums [OK] - maven build [OK] with Maven version: 2.0.10 Java version: 1.5.0_20 OS name: mac os x version: 10.6.2 arch: i386 Family: unix regards, toby On Thu, Dec 17, 2009 at 3:07 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, A new Jackrabbit 2.0 beta release candidate is available at: http://people.apache.org/~jukka/jackrabbit/2.0-beta5/ See the RELEASE-NOTES.txt file (also included at the end of this message) for details about this release. The release candidate is a zip archive of the sources in: http://svn.apache.org/repos/asf/jackrabbit/tags/2.0-beta5/ The SHA1 checksum of the release package is 6ecc5d8b56bcee90420d71680289bed3cd253066. In addition to the source archive and the main binaries included in the directory linked above, there is also a staged Maven repository containing all the other binary release artifacts: https://repository.apache.org/content/repositories/orgapachejackrabbit-055/ Please vote on releasing this package as Apache Jackrabbit 2.0-beta5. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. [ ] +1 Release this package as Apache Jackrabbit 2.0-beta5 [ ] -1 Do not release this package because... Here's my +1. BR, Jukka Zitting Release Notes -- Apache Jackrabbit -- Version 2.0-beta5 Introduction This is a beta release of Apache Jackrabbit 2.0. This release is a fully compliant implementation of the JCR 2.0 API that was specified by the Java Specification Request 283 (JSR 283, http://jcp.org/en/jsr/detail?id=283). However, the beta status of this release means that some parts of the implementation are not yet ready for normal production use. Changes in this release --- Jackrabbit 2.0 is a major upgrade from the earlier 1.x releases. The most notable changes in this release are: * Upgrade to JCR 2.0. This Jackrabbit release implements and is based on the official JCR 2.0 API. All of the features required by the JSR 283 specification have been implemented. * Upgrade to Java 5. All of Jackrabbit (except the jcr-tests component) now requires Java 5 as the base platform. Java 1.4 environments are no longer supported. * Removal of deprecated classes and features. Jackrabbit 2.0 is not backwards compatible with client code that used any classes or features that had been deprecated during the 1.x release cycle. * Separate JCR Commons components. Many of the general-purpose JCR components like JCR-RMI and OCM are now developed and released separately from the Jackrabbit content repository. See the individual components for their most recent releases. * Database connection pooling is now available for all database backends. * Data store feature enabled in the default repository configuration. * Full text indexing with Apache Tika. Jackrabbit can now extract and index the full text content of many new types of documents, including the Office Open XML files produced by Microsoft Office 2007 and higher. * Apache Commons Collections, Apache Derby, Jetty, SLF4J and Apache Xerces have been upgraded to a more recent version. * OracleFileSystem class does not use special blob handling anymore and is required for 10R1 and earlier anymore. If you need that use the new Oracle9FileSystem. For more detailed information about all the changes in this and other Jackrabbit releases, please see the Jackrabbit issue tracker at https://issues.apache.org/jira/browse/JCR Release Contents This release consists of a single source archive packaged as a zip file. The archive can be unpacked with the jar tool from your JDK installation. See the README.txt file for instructions on how to build this release. The source archive is accompanied by SHA1 and MD5 checksums and a PGP signature that you can use to verify the authenticity of your download. The public key used for the PGP signature can be found at https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS. About Apache Jackrabbit --- Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR). A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more. For more information, visit http://jackrabbit.apache.org/ About The Apache Software Foundation Established in 1999, The Apache Software Foundation provides organizational, legal, and financial support for more than 100 freely-available, collaboratively-developed Open Source projects. The pragmatic Apache License enables individual and commercial users to easily deploy Apache software; the Foundation's intellectual property
Re: [VOTE] Release Apache Jackrabbit 2.0-beta5
2009/12/18 Tobias Bocanegra tri...@day.com: [X] +1 Release this package as Apache Jackrabbit 2.0-beta5 The javadoc link in the left column menu when you browse the webpage for the web application still points to JCR 1.0. -- -Tor
