You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openjpa.apache.org by mi...@apache.org on 2012/11/14 02:50:14 UTC
svn commit: r1409057 [1/25] - in /openjpa/site: branches/ trunk/
trunk/cgi-bin/ trunk/content/ trunk/content/images/ trunk/lib/
trunk/resources/ trunk/templates/
Author: mikedd
Date: Wed Nov 14 01:49:37 2012
New Revision: 1409057
URL: http://svn.apache.org/viewvc?rev=1409057&view=rev
Log:
Exporting site from confluence.
Added initial path structure, templates and build files.
Cwiki and mdtext files are exported after spidering the site.
Added:
openjpa/site/branches/
openjpa/site/trunk/
openjpa/site/trunk/build.sh (with props)
openjpa/site/trunk/cgi-bin/
openjpa/site/trunk/content/
openjpa/site/trunk/content/2.1-roadmap
openjpa/site/trunk/content/2.1-roadmap.cwiki (with props)
openjpa/site/trunk/content/2.1-roadmap.mdtext
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x)
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).cwiki (with props)
openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
openjpa/site/trunk/content/apidiscussionfollowup
openjpa/site/trunk/content/apidiscussionfollowup.cwiki (with props)
openjpa/site/trunk/content/apidiscussionfollowup.mdtext
openjpa/site/trunk/content/apply-an-eclipse-patch
openjpa/site/trunk/content/apply-an-eclipse-patch.cwiki (with props)
openjpa/site/trunk/content/apply-an-eclipse-patch.mdtext
openjpa/site/trunk/content/architecture-notes
openjpa/site/trunk/content/architecture-notes.cwiki (with props)
openjpa/site/trunk/content/architecture-notes.mdtext
openjpa/site/trunk/content/automated-builds
openjpa/site/trunk/content/automated-builds.cwiki (with props)
openjpa/site/trunk/content/automated-builds.mdtext
openjpa/site/trunk/content/banner
openjpa/site/trunk/content/banner.cwiki (with props)
openjpa/site/trunk/content/banner.mdtext
openjpa/site/trunk/content/bean-validation-primer
openjpa/site/trunk/content/bean-validation-primer.cwiki (with props)
openjpa/site/trunk/content/bean-validation-primer.mdtext
openjpa/site/trunk/content/begin-using-openjpa---the-basics
openjpa/site/trunk/content/begin-using-openjpa---the-basics.cwiki (with props)
openjpa/site/trunk/content/begin-using-openjpa---the-basics.mdtext
openjpa/site/trunk/content/beginners-performance-guide
openjpa/site/trunk/content/beginners-performance-guide.cwiki (with props)
openjpa/site/trunk/content/beginners-performance-guide.mdtext
openjpa/site/trunk/content/build-and-runtime-dependencies
openjpa/site/trunk/content/build-and-runtime-dependencies.cwiki (with props)
openjpa/site/trunk/content/build-and-runtime-dependencies.mdtext
openjpa/site/trunk/content/building
openjpa/site/trunk/content/building-and-running-openbooks
openjpa/site/trunk/content/building-and-running-openbooks.cwiki (with props)
openjpa/site/trunk/content/building-and-running-openbooks.mdtext
openjpa/site/trunk/content/building.cwiki (with props)
openjpa/site/trunk/content/building.mdtext
openjpa/site/trunk/content/coding-standards
openjpa/site/trunk/content/coding-standards.cwiki (with props)
openjpa/site/trunk/content/coding-standards.mdtext
openjpa/site/trunk/content/committers
openjpa/site/trunk/content/committers.cwiki (with props)
openjpa/site/trunk/content/committers.mdtext
openjpa/site/trunk/content/community
openjpa/site/trunk/content/community-top-link
openjpa/site/trunk/content/community-top-link.cwiki (with props)
openjpa/site/trunk/content/community-top-link.mdtext
openjpa/site/trunk/content/community.cwiki (with props)
openjpa/site/trunk/content/community.mdtext
openjpa/site/trunk/content/development
openjpa/site/trunk/content/development-process
openjpa/site/trunk/content/development-process.cwiki (with props)
openjpa/site/trunk/content/development-process.mdtext
openjpa/site/trunk/content/development-top-link
openjpa/site/trunk/content/development-top-link.cwiki (with props)
openjpa/site/trunk/content/development-top-link.mdtext
openjpa/site/trunk/content/development.cwiki (with props)
openjpa/site/trunk/content/development.mdtext
openjpa/site/trunk/content/documentation
openjpa/site/trunk/content/documentation-top-link
openjpa/site/trunk/content/documentation-top-link.cwiki (with props)
openjpa/site/trunk/content/documentation-top-link.mdtext
openjpa/site/trunk/content/documentation.cwiki (with props)
openjpa/site/trunk/content/documentation.mdtext
openjpa/site/trunk/content/domain-model-browser
openjpa/site/trunk/content/domain-model-browser.cwiki (with props)
openjpa/site/trunk/content/domain-model-browser.mdtext
openjpa/site/trunk/content/downloads
openjpa/site/trunk/content/downloads-top-link
openjpa/site/trunk/content/downloads-top-link.cwiki (with props)
openjpa/site/trunk/content/downloads-top-link.mdtext
openjpa/site/trunk/content/downloads.cwiki (with props)
openjpa/site/trunk/content/downloads.mdtext
openjpa/site/trunk/content/embeddable-samples
openjpa/site/trunk/content/embeddable-samples.cwiki (with props)
openjpa/site/trunk/content/embeddable-samples.mdtext
openjpa/site/trunk/content/enhancement-with-ant
openjpa/site/trunk/content/enhancement-with-ant.cwiki (with props)
openjpa/site/trunk/content/enhancement-with-ant.mdtext
openjpa/site/trunk/content/enhancement-with-eclipse
openjpa/site/trunk/content/enhancement-with-eclipse.cwiki (with props)
openjpa/site/trunk/content/enhancement-with-eclipse.mdtext
openjpa/site/trunk/content/enhancement-with-maven
openjpa/site/trunk/content/enhancement-with-maven.cwiki (with props)
openjpa/site/trunk/content/enhancement-with-maven.mdtext
openjpa/site/trunk/content/entity-enhancement
openjpa/site/trunk/content/entity-enhancement.cwiki (with props)
openjpa/site/trunk/content/entity-enhancement.mdtext
openjpa/site/trunk/content/events-and-news
openjpa/site/trunk/content/events-and-news.cwiki (with props)
openjpa/site/trunk/content/events-and-news.mdtext
openjpa/site/trunk/content/faq
openjpa/site/trunk/content/faq.cwiki (with props)
openjpa/site/trunk/content/faq.mdtext
openjpa/site/trunk/content/fetch-statistics
openjpa/site/trunk/content/fetch-statistics.cwiki (with props)
openjpa/site/trunk/content/fetch-statistics.mdtext
openjpa/site/trunk/content/findbugs-presentation-notes
openjpa/site/trunk/content/findbugs-presentation-notes.cwiki (with props)
openjpa/site/trunk/content/findbugs-presentation-notes.mdtext
openjpa/site/trunk/content/found-a-bug
openjpa/site/trunk/content/found-a-bug.cwiki (with props)
openjpa/site/trunk/content/found-a-bug.mdtext
openjpa/site/trunk/content/get-involved
openjpa/site/trunk/content/get-involved.cwiki (with props)
openjpa/site/trunk/content/get-involved.mdtext
openjpa/site/trunk/content/getting-started
openjpa/site/trunk/content/getting-started.cwiki (with props)
openjpa/site/trunk/content/getting-started.mdtext
openjpa/site/trunk/content/images/
openjpa/site/trunk/content/images/asf_logo_wide2.png (with props)
openjpa/site/trunk/content/images/check.gif (with props)
openjpa/site/trunk/content/images/header-bg3.png (with props)
openjpa/site/trunk/content/images/openjpa-logo.png (with props)
openjpa/site/trunk/content/index
openjpa/site/trunk/content/index-top-link
openjpa/site/trunk/content/index-top-link.cwiki (with props)
openjpa/site/trunk/content/index-top-link.mdtext
openjpa/site/trunk/content/index.cwiki (with props)
openjpa/site/trunk/content/index.mdtext
openjpa/site/trunk/content/integration
openjpa/site/trunk/content/integration.cwiki (with props)
openjpa/site/trunk/content/integration.mdtext
openjpa/site/trunk/content/intro
openjpa/site/trunk/content/intro.cwiki (with props)
openjpa/site/trunk/content/intro.mdtext
openjpa/site/trunk/content/jconsole-datacache-plugin
openjpa/site/trunk/content/jconsole-datacache-plugin.cwiki (with props)
openjpa/site/trunk/content/jconsole-datacache-plugin.mdtext
openjpa/site/trunk/content/jest
openjpa/site/trunk/content/jest-examples
openjpa/site/trunk/content/jest-examples.cwiki (with props)
openjpa/site/trunk/content/jest-examples.mdtext
openjpa/site/trunk/content/jest-representation
openjpa/site/trunk/content/jest-representation.cwiki (with props)
openjpa/site/trunk/content/jest-representation.mdtext
openjpa/site/trunk/content/jest-syntax
openjpa/site/trunk/content/jest-syntax.cwiki (with props)
openjpa/site/trunk/content/jest-syntax.mdtext
openjpa/site/trunk/content/jest-transaction
openjpa/site/trunk/content/jest-transaction.cwiki (with props)
openjpa/site/trunk/content/jest-transaction.mdtext
openjpa/site/trunk/content/jest-usage
openjpa/site/trunk/content/jest-usage.cwiki (with props)
openjpa/site/trunk/content/jest-usage.mdtext
openjpa/site/trunk/content/jest.cwiki (with props)
openjpa/site/trunk/content/jest.mdtext
openjpa/site/trunk/content/jpa-2.0-development-process
openjpa/site/trunk/content/jpa-2.0-development-process.cwiki (with props)
openjpa/site/trunk/content/jpa-2.0-development-process.mdtext
openjpa/site/trunk/content/jpa-2.0-iterations
openjpa/site/trunk/content/jpa-2.0-iterations.cwiki (with props)
openjpa/site/trunk/content/jpa-2.0-iterations.mdtext
openjpa/site/trunk/content/jpa-2.0-presentations
openjpa/site/trunk/content/jpa-2.0-presentations.cwiki (with props)
openjpa/site/trunk/content/jpa-2.0-presentations.mdtext
openjpa/site/trunk/content/jpa-2.0-roadmap
openjpa/site/trunk/content/jpa-2.0-roadmap.cwiki (with props)
openjpa/site/trunk/content/jpa-2.0-roadmap.mdtext
openjpa/site/trunk/content/jpa-2.0-tasks
openjpa/site/trunk/content/jpa-2.0-tasks.cwiki (with props)
openjpa/site/trunk/content/jpa-2.0-tasks.mdtext
openjpa/site/trunk/content/jpa-2.0-test-coverage
openjpa/site/trunk/content/jpa-2.0-test-coverage.cwiki (with props)
openjpa/site/trunk/content/jpa-2.0-test-coverage.mdtext
openjpa/site/trunk/content/jpa-m2-demo
openjpa/site/trunk/content/jpa-m2-demo.cwiki (with props)
openjpa/site/trunk/content/jpa-m2-demo.mdtext
openjpa/site/trunk/content/jsr-317-20081031-public-draft-tasks
openjpa/site/trunk/content/jsr-317-20081031-public-draft-tasks.cwiki (with props)
openjpa/site/trunk/content/jsr-317-20081031-public-draft-tasks.mdtext
openjpa/site/trunk/content/license
openjpa/site/trunk/content/license.cwiki (with props)
openjpa/site/trunk/content/license.mdtext
openjpa/site/trunk/content/logo-contest
openjpa/site/trunk/content/logo-contest.cwiki (with props)
openjpa/site/trunk/content/logo-contest.mdtext
openjpa/site/trunk/content/mailing-lists
openjpa/site/trunk/content/mailing-lists.cwiki (with props)
openjpa/site/trunk/content/mailing-lists.mdtext
openjpa/site/trunk/content/mdd.mdtext
openjpa/site/trunk/content/migration-tool
openjpa/site/trunk/content/migration-tool.cwiki (with props)
openjpa/site/trunk/content/migration-tool.mdtext
openjpa/site/trunk/content/obtaining
openjpa/site/trunk/content/obtaining.cwiki (with props)
openjpa/site/trunk/content/obtaining.mdtext
openjpa/site/trunk/content/openbooks---featuring-jpa-2.0
openjpa/site/trunk/content/openbooks---featuring-jpa-2.0.cwiki (with props)
openjpa/site/trunk/content/openbooks---featuring-jpa-2.0.mdtext
openjpa/site/trunk/content/openjpa+email
openjpa/site/trunk/content/openjpa+email.cwiki (with props)
openjpa/site/trunk/content/openjpa+email.mdtext
openjpa/site/trunk/content/openjpa-2.0.0
openjpa/site/trunk/content/openjpa-2.0.0-beta
openjpa/site/trunk/content/openjpa-2.0.0-beta-2
openjpa/site/trunk/content/openjpa-2.0.0-beta-2.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.0-beta-2.mdtext
openjpa/site/trunk/content/openjpa-2.0.0-beta-3
openjpa/site/trunk/content/openjpa-2.0.0-beta-3.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.0-beta-3.mdtext
openjpa/site/trunk/content/openjpa-2.0.0-beta.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.0-beta.mdtext
openjpa/site/trunk/content/openjpa-2.0.0-early-access-2
openjpa/site/trunk/content/openjpa-2.0.0-early-access-2.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.0-early-access-2.mdtext
openjpa/site/trunk/content/openjpa-2.0.0-milestone-3
openjpa/site/trunk/content/openjpa-2.0.0-milestone-3.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.0-milestone-3.mdtext
openjpa/site/trunk/content/openjpa-2.0.0.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.0.mdtext
openjpa/site/trunk/content/openjpa-2.0.1
openjpa/site/trunk/content/openjpa-2.0.1.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.0.1.mdtext
openjpa/site/trunk/content/openjpa-2.1.0
openjpa/site/trunk/content/openjpa-2.1.0.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.1.0.mdtext
openjpa/site/trunk/content/openjpa-2.2.0
openjpa/site/trunk/content/openjpa-2.2.0.cwiki (with props)
openjpa/site/trunk/content/openjpa-2.2.0.mdtext
openjpa/site/trunk/content/openjpa-confluence-user-groups
openjpa/site/trunk/content/openjpa-confluence-user-groups.cwiki (with props)
openjpa/site/trunk/content/openjpa-confluence-user-groups.mdtext
openjpa/site/trunk/content/openjpa-development-resources
openjpa/site/trunk/content/openjpa-development-resources.cwiki (with props)
openjpa/site/trunk/content/openjpa-development-resources.mdtext
openjpa/site/trunk/content/openjpa-logo-contest---round-1
openjpa/site/trunk/content/openjpa-logo-contest---round-1.cwiki (with props)
openjpa/site/trunk/content/openjpa-logo-contest---round-1.mdtext
openjpa/site/trunk/content/openjpa-logo-contest---round-2
openjpa/site/trunk/content/openjpa-logo-contest---round-2.cwiki (with props)
openjpa/site/trunk/content/openjpa-logo-contest---round-2.mdtext
openjpa/site/trunk/content/openjpa-logo-contest---run-off
openjpa/site/trunk/content/openjpa-logo-contest---run-off.cwiki (with props)
openjpa/site/trunk/content/openjpa-logo-contest---run-off.mdtext
openjpa/site/trunk/content/openjpa-release-policy
openjpa/site/trunk/content/openjpa-release-policy.cwiki (with props)
openjpa/site/trunk/content/openjpa-release-policy.mdtext
openjpa/site/trunk/content/openjpa-up-close-and-personal
openjpa/site/trunk/content/openjpa-up-close-and-personal.cwiki (with props)
openjpa/site/trunk/content/openjpa-up-close-and-personal.mdtext
openjpa/site/trunk/content/openjpaeclipseenhancementbuilder
openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.cwiki (with props)
openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.mdtext
openjpa/site/trunk/content/openjpaeclipseinstallation
openjpa/site/trunk/content/openjpaeclipseinstallation.cwiki (with props)
openjpa/site/trunk/content/openjpaeclipseinstallation.mdtext
openjpa/site/trunk/content/openjpaeclipsetoolingdevandbuild
openjpa/site/trunk/content/openjpaeclipsetoolingdevandbuild.cwiki (with props)
openjpa/site/trunk/content/openjpaeclipsetoolingdevandbuild.mdtext
openjpa/site/trunk/content/opentrader
openjpa/site/trunk/content/opentrader.cwiki (with props)
openjpa/site/trunk/content/opentrader.mdtext
openjpa/site/trunk/content/opentraderarchitecture
openjpa/site/trunk/content/opentraderarchitecture.cwiki (with props)
openjpa/site/trunk/content/opentraderarchitecture.mdtext
openjpa/site/trunk/content/opentraderbuild
openjpa/site/trunk/content/opentraderbuild.cwiki (with props)
openjpa/site/trunk/content/opentraderbuild.mdtext
openjpa/site/trunk/content/opentraderclient
openjpa/site/trunk/content/opentraderclient.cwiki (with props)
openjpa/site/trunk/content/opentraderclient.mdtext
openjpa/site/trunk/content/opentradercommunication
openjpa/site/trunk/content/opentradercommunication.cwiki (with props)
openjpa/site/trunk/content/opentradercommunication.mdtext
openjpa/site/trunk/content/opentraderdeploy
openjpa/site/trunk/content/opentraderdeploy.cwiki (with props)
openjpa/site/trunk/content/opentraderdeploy.mdtext
openjpa/site/trunk/content/opentraderenvironment
openjpa/site/trunk/content/opentraderenvironment.cwiki (with props)
openjpa/site/trunk/content/opentraderenvironment.mdtext
openjpa/site/trunk/content/opentraderserver
openjpa/site/trunk/content/opentraderserver.cwiki (with props)
openjpa/site/trunk/content/opentraderserver.mdtext
openjpa/site/trunk/content/overview
openjpa/site/trunk/content/overview.cwiki (with props)
openjpa/site/trunk/content/overview.mdtext
openjpa/site/trunk/content/performance-guide
openjpa/site/trunk/content/performance-guide.cwiki (with props)
openjpa/site/trunk/content/performance-guide.mdtext
openjpa/site/trunk/content/powered-by
openjpa/site/trunk/content/powered-by.cwiki (with props)
openjpa/site/trunk/content/powered-by.mdtext
openjpa/site/trunk/content/privacy-policy
openjpa/site/trunk/content/privacy-policy.cwiki (with props)
openjpa/site/trunk/content/privacy-policy.mdtext
openjpa/site/trunk/content/publishing-serp-to-maven-central-repository
openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.cwiki (with props)
openjpa/site/trunk/content/publishing-serp-to-maven-central-repository.mdtext
openjpa/site/trunk/content/query-notes
openjpa/site/trunk/content/query-notes.cwiki (with props)
openjpa/site/trunk/content/query-notes.mdtext
openjpa/site/trunk/content/quick-start
openjpa/site/trunk/content/quick-start.cwiki (with props)
openjpa/site/trunk/content/quick-start.mdtext
openjpa/site/trunk/content/recovering-from-a-vetoed-release
openjpa/site/trunk/content/recovering-from-a-vetoed-release.cwiki (with props)
openjpa/site/trunk/content/recovering-from-a-vetoed-release.mdtext
openjpa/site/trunk/content/related-projects
openjpa/site/trunk/content/related-projects.cwiki (with props)
openjpa/site/trunk/content/related-projects.mdtext
openjpa/site/trunk/content/release-management
openjpa/site/trunk/content/release-management.cwiki (with props)
openjpa/site/trunk/content/release-management.mdtext
openjpa/site/trunk/content/release-setup
openjpa/site/trunk/content/release-setup.cwiki (with props)
openjpa/site/trunk/content/release-setup.mdtext
openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps)
openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).cwiki (with props)
openjpa/site/trunk/content/releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).mdtext
openjpa/site/trunk/content/releasing-openjpa-1.2.x-(old-scp-steps)
openjpa/site/trunk/content/releasing-openjpa-1.2.x-(old-scp-steps).cwiki (with props)
openjpa/site/trunk/content/releasing-openjpa-1.2.x-(old-scp-steps).mdtext
openjpa/site/trunk/content/running-openjpa-examples
openjpa/site/trunk/content/running-openjpa-examples.cwiki (with props)
openjpa/site/trunk/content/running-openjpa-examples.mdtext
openjpa/site/trunk/content/running-the-sun-tck-for-jpa
openjpa/site/trunk/content/running-the-sun-tck-for-jpa.cwiki (with props)
openjpa/site/trunk/content/running-the-sun-tck-for-jpa.mdtext
openjpa/site/trunk/content/runtime-enhancement
openjpa/site/trunk/content/runtime-enhancement.cwiki (with props)
openjpa/site/trunk/content/runtime-enhancement.mdtext
openjpa/site/trunk/content/samples
openjpa/site/trunk/content/samples.cwiki (with props)
openjpa/site/trunk/content/samples.mdtext
openjpa/site/trunk/content/sampletemplate
openjpa/site/trunk/content/sampletemplate.cwiki (with props)
openjpa/site/trunk/content/sampletemplate.mdtext
openjpa/site/trunk/content/sidenav
openjpa/site/trunk/content/sidenav-community
openjpa/site/trunk/content/sidenav-community.cwiki (with props)
openjpa/site/trunk/content/sidenav-community.mdtext
openjpa/site/trunk/content/sidenav-development
openjpa/site/trunk/content/sidenav-development.cwiki (with props)
openjpa/site/trunk/content/sidenav-development.mdtext
openjpa/site/trunk/content/sidenav-overview
openjpa/site/trunk/content/sidenav-overview.cwiki (with props)
openjpa/site/trunk/content/sidenav-overview.mdtext
openjpa/site/trunk/content/sidenav-quick-links
openjpa/site/trunk/content/sidenav-quick-links.cwiki (with props)
openjpa/site/trunk/content/sidenav-quick-links.mdtext
openjpa/site/trunk/content/sidenav.cwiki (with props)
openjpa/site/trunk/content/sidenav.mdtext
openjpa/site/trunk/content/site-index
openjpa/site/trunk/content/site-index.cwiki (with props)
openjpa/site/trunk/content/site-index.mdtext
openjpa/site/trunk/content/site-map
openjpa/site/trunk/content/site-map.cwiki (with props)
openjpa/site/trunk/content/site-map.mdtext
openjpa/site/trunk/content/source-code
openjpa/site/trunk/content/source-code.cwiki (with props)
openjpa/site/trunk/content/source-code.mdtext
openjpa/site/trunk/content/testing
openjpa/site/trunk/content/testing.cwiki (with props)
openjpa/site/trunk/content/testing.mdtext
openjpa/site/trunk/content/thanks
openjpa/site/trunk/content/thanks.cwiki (with props)
openjpa/site/trunk/content/thanks.mdtext
openjpa/site/trunk/content/tools
openjpa/site/trunk/content/tools.cwiki (with props)
openjpa/site/trunk/content/tools.mdtext
openjpa/site/trunk/content/top-navigation-bar
openjpa/site/trunk/content/top-navigation-bar.cwiki (with props)
openjpa/site/trunk/content/top-navigation-bar.mdtext
openjpa/site/trunk/content/update-release-text-files
openjpa/site/trunk/content/update-release-text-files.cwiki (with props)
openjpa/site/trunk/content/update-release-text-files.mdtext
openjpa/site/trunk/content/using-criteria-api-in-daytrader
openjpa/site/trunk/content/using-criteria-api-in-daytrader.cwiki (with props)
openjpa/site/trunk/content/using-criteria-api-in-daytrader.mdtext
openjpa/site/trunk/content/verifying-release-signatures
openjpa/site/trunk/content/verifying-release-signatures.cwiki (with props)
openjpa/site/trunk/content/verifying-release-signatures.mdtext
openjpa/site/trunk/content/websphere-application-server
openjpa/site/trunk/content/websphere-application-server.cwiki (with props)
openjpa/site/trunk/content/websphere-application-server.mdtext
openjpa/site/trunk/content/whither-openjpa
openjpa/site/trunk/content/whither-openjpa.cwiki (with props)
openjpa/site/trunk/content/whither-openjpa.mdtext
openjpa/site/trunk/content/wiki
openjpa/site/trunk/content/wiki.cwiki (with props)
openjpa/site/trunk/content/wiki.mdtext
openjpa/site/trunk/content/writing-test-cases-for-openjpa
openjpa/site/trunk/content/writing-test-cases-for-openjpa.cwik
openjpa/site/trunk/content/writing-test-cases-for-openjpa.cwiki (with props)
openjpa/site/trunk/content/writing-test-cases-for-openjpa.mdtext
openjpa/site/trunk/export.xml (with props)
openjpa/site/trunk/lib/
openjpa/site/trunk/lib/path.pm (with props)
openjpa/site/trunk/lib/view.pm (with props)
openjpa/site/trunk/resources/
openjpa/site/trunk/start_markdown.sh (with props)
openjpa/site/trunk/templates/
openjpa/site/trunk/templates/standard.html (with props)
openjpa/site/trunk/templates/standard_markdown.html (with props)
Added: openjpa/site/trunk/build.sh
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/build.sh?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/build.sh (added)
+++ openjpa/site/trunk/build.sh Wed Nov 14 01:49:37 2012
@@ -0,0 +1,17 @@
+#!/bin/bash
+
+# path where you checked out https://svn.apache.org/repos/infra/websites/cms/build
+# change this to match your environment
+CMS_BUILD_PATH=~/cms/cms/build
+
+# path to where you checked out https://svn.apache.org/repos/asf/openjpa/site/trunk
+SOURCE=~/work/openjpa/site/trunk
+
+# target dir for website files
+TARGET=${SOURCE}/target
+
+# markdown socket file - this should match the one in setup_env.sh
+MARKDOWN_SOCKET=${CMS_BUILD_PATH}/markdown.socket
+
+MARKDOWN_SOCKET=${MARKDOWN_SOCKET} perl ${CMS_BUILD_PATH}/build_site.pl --source-base ${SOURCE} --target-base ${TARGET}
+
Propchange: openjpa/site/trunk/build.sh
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: openjpa/site/trunk/build.sh
------------------------------------------------------------------------------
svn:executable = *
Added: openjpa/site/trunk/content/2.1-roadmap
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/2.1-roadmap?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/2.1-roadmap (added)
+++ openjpa/site/trunk/content/2.1-roadmap Wed Nov 14 01:49:37 2012
@@ -0,0 +1,35 @@
+h1. OpenJPA 2.1 Roadmap
+
+We'll try to maintain this page with delivered and planned features for the OpenJPA 2.1.0 release, so check back often.
+
+h3. Planned Features
+
+* Built-in connection pooling for Java SE applications
+** Inclusion of commons-dbcp in openjpa-all.jar and the binary distribution
+** Ability to configure or disable commons-dbcp
+* Built-in Bean Validation Provider
+** Inclusion of Apache Bean Validation Provider in openjpa-all.jar and the binary distribution
+* Additional Database Support
+** Microsoft SQL Server 2008 R2
+** Microsoft SQL JDBC driver v3.0
+** IBM solidDB
+* Additional Samples
+** OpenBook
+** Image Gallery
+** OpenTrader
+* Instrumentation and Platform MBean support
+** Pluggable instrumentation support
+** Remote monitoring of OpenJPA's caches using JMX
+* New Tools
+** [JConsole plugin for monitoring OpenJPA's datacache|https://issues.apache.org/jira/browse/OPENJPA-1844]
+
+
+h3. Migration Issues
+
+* This release will officially *drop support for Java SE 5*. Anyone requiring Java SE 5 support will have to continue using OpenJPA 2.0.x, which is fully JPA 2.0 compliant.
+
+h3. Release Plan
+
+A [2.1.x branch|https://svn.apache.org/repos/asf/openjpa/branches/2.1.x/] is available in SVN and 2.1.0 release preparations are underway. The OpenJPA team is planning to deliver a 2.1.0 release in late January, 2011.
+
+\\
Added: openjpa/site/trunk/content/2.1-roadmap.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/2.1-roadmap.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/2.1-roadmap.cwiki (added)
+++ openjpa/site/trunk/content/2.1-roadmap.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,35 @@
+h1. OpenJPA 2.1 Roadmap
+
+We'll try to maintain this page with delivered and planned features for the OpenJPA 2.1.0 release, so check back often.
+
+h3. Planned Features
+
+* Built-in connection pooling for Java SE applications
+** Inclusion of commons-dbcp in openjpa-all.jar and the binary distribution
+** Ability to configure or disable commons-dbcp
+* Built-in Bean Validation Provider
+** Inclusion of Apache Bean Validation Provider in openjpa-all.jar and the binary distribution
+* Additional Database Support
+** Microsoft SQL Server 2008 R2
+** Microsoft SQL JDBC driver v3.0
+** IBM solidDB
+* Additional Samples
+** OpenBook
+** Image Gallery
+** OpenTrader
+* Instrumentation and Platform MBean support
+** Pluggable instrumentation support
+** Remote monitoring of OpenJPA's caches using JMX
+* New Tools
+** [JConsole plugin for monitoring OpenJPA's datacache|https://issues.apache.org/jira/browse/OPENJPA-1844]
+
+
+h3. Migration Issues
+
+* This release will officially *drop support for Java SE 5*. Anyone requiring Java SE 5 support will have to continue using OpenJPA 2.0.x, which is fully JPA 2.0 compliant.
+
+h3. Release Plan
+
+A [2.1.x branch|https://svn.apache.org/repos/asf/openjpa/branches/2.1.x/] is available in SVN and 2.1.0 release preparations are underway. The OpenJPA team is planning to deliver a 2.1.0 release in late January, 2011.
+
+\\
Propchange: openjpa/site/trunk/content/2.1-roadmap.cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: openjpa/site/trunk/content/2.1-roadmap.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/2.1-roadmap.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/2.1-roadmap.mdtext (added)
+++ openjpa/site/trunk/content/2.1-roadmap.mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,47 @@
+Title: 2.1 Roadmap
+<a name="2.1Roadmap-OpenJPA2.1Roadmap"></a>
+# OpenJPA 2.1 Roadmap
+
+We'll try to maintain this page with delivered and planned features for the
+OpenJPA 2.1.0 release, so check back often.
+
+<a name="2.1Roadmap-PlannedFeatures"></a>
+## Planned Features
+
+* Built-in connection pooling for Java SE applications
+ * Inclusion of commons-dbcp in openjpa-all.jar and the binary distribution
+ * Ability to configure or disable commons-dbcp
+* Built-in Bean Validation Provider
+ * Inclusion of Apache Bean Validation Provider in openjpa-all.jar and the
+binary distribution
+* Additional Database Support
+ * Microsoft SQL Server 2008 R2
+ * Microsoft SQL JDBC driver v3.0
+ * IBM solidDB
+* Additional Samples
+ * OpenBook
+ * Image Gallery
+ * OpenTrader
+* Instrumentation and Platform MBean support
+ * Pluggable instrumentation support
+ * Remote monitoring of OpenJPA's caches using JMX
+* New Tools
+ * [JConsole plugin for monitoring OpenJPA's datacache](https://issues.apache.org/jira/browse/OPENJPA-1844)
+
+
+<a name="2.1Roadmap-MigrationIssues"></a>
+# Migration Issues
+
+* This release will officially *drop support for Java SE 5*. Anyone
+requiring Java SE 5 support will have to continue using OpenJPA 2.0.x,
+which is fully JPA 2.0 compliant.
+
+<a name="2.1Roadmap-ReleasePlan"></a>
+# Release Plan
+
+A [2.1.x branch](https://svn.apache.org/repos/asf/openjpa/branches/2.1.x/)
+ is available in SVN and 2.1.0 release preparations are underway. The
+OpenJPA team is planning to deliver a 2.1.0 release in late January, 2011.
+
+
+
Added: openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x)
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x) (added)
+++ openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x) Wed Nov 14 01:49:37 2012
@@ -0,0 +1,281 @@
+We're starting to move our builds over to using the Apache Nexus repository (repository.apache.org) for releasing SNAPSHOT and release artifacts. More details on releasing artifacts and using Nexus can be found on the Maven website at - [http://maven.apache.org/developers/release/apache-release.html]
+
+h3. Release Steps for OpenJPA 1.2.x - 2.1.x
+
+# Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
+## Increase the default Java heap available to Maven (required for Java SE 6)
+{code:none}
+export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
+{code}
+## Use the latest Sun 1.6.0 JDK (1.5.0 for 1.2.x and 1.3.x)
+## Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
+## Make sure the [Release Setup] steps have been performed.
+# Prepare the source for release:
+## Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
+## Update the text files in a working copy of the openjpa-project subdir -
+### Update the CHANGES.txt based on the Text release reports from JIRA.
+#### Choose the release from the "Versions" tab in the [releases page|https://issues.apache.org/jira/browse/OPENJPA/fixforversion/].
+#### Click "Release Notes" link in upper right.
+### Update the RELEASE-NOTES.html based on the HTML release reports from JIRA.
+### Review and update README.txt and BUILDING.txt if needed.
+### Commit any changes back to svn -
+{code:none}
+$ svn commit -m "updating files for release"
+{code}
+## Stage any Roadmap or Release landing pages on the wiki.
+## Verify the source has the required headers before trying to release.
+{code:none}
+$ mvn apache-rat:check
+{code}
+## Perform a full build with tests
+{code:none}
+$ mvn clean install -Papache-release,docbook-profile,test-derby,bval
+{code}
+## Run the JPA 1.0 TCK (for 1.x) and JPA 2.0 TCK (for 2.x) to verify the latest code passes.
+## Perform a full build and deploy the SNAPSHOT artifacts
+{code:none}
+$ mvn clean deploy site site-deploy -Papache-release,docbook-profile,test-derby,bval -DskipTests
+{code}
+## Inspect the files in your local target directories to ensure:
+### All jars and zips include: LICENSE and NOTICE files
+### The NOTICE files cover all third-party included files (like XSD schemas)
+### The LICENSE files include any third-party licenses (like XSD schemas)
+### The openjpa and openjpa-all jars include the right packages.
+### The openjpa source and release distribution files have the right content.
+### All jars/zips/poms have .asc (PGP signature) and md5 files
+# For new major releases (like 2.0.0 to 2.1.0)
+## Create a sub-branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. It also provides a future maintenance branch (like 2.0.x.) A branch can be made by running: \\
+{code:none}
+$ mvn release:branch -DbranchName=2.0.x [-Dusername=svn.user -Dpassword=svn.password]
+{code}
+# Checkout a clean copy of the trunk/branch to release using command line svn.
+## Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing and will get included in the source distribution. \\
+{code:none}
+$ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/ 2.0.1-rc1/
+{code}
+# (Optional) Do a dry run of the release:prepare step.
+## The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
+### Release version - take the default - (default 2.0.1)
+### SCM release tag - *DO NOT TAKE THE DEFAULT - (default openjpa-parent-2.0.1): : 2.0.1
+### New development version - take the default - (default 2.0.2-SNAPSHOT)
+### _optional_ if you have not specified a GPG passphrase in settings.xml you will be prompted for it.
+{code:none}
+$ mvn -Papache-release release:prepare -DdryRun=true
+{code}
+{note}
+If you cancel a release:prepare before it updates the pom.xml versions, then use the *release:clean* goal to just remove the extra files that were created. If that doesn't help, try running *mvn clean*.
+{note}
+## Verify that the release process completed as expected
+### The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.
+### If other formatting changes have been made you should review the changes and then commit them -
+{code:none}
+$ svn commit -m "fixing formatting for release"
+{code}
+### Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful
+#### Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
+#### verify signatures [Verifying release signatures|#verifySig]
+## Once any failures or required updates have been committed to svn, rollback the release prepare files -
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+# Prepare the release
+## Run the "release:prepare" step for real this time. You'll be prompted for the same version information and optionally your GPG passphrase again.
+{code:none}
+$ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests [-Dusername=svn.user -Dpassword=svn.password] -DpreparationGoals="clean install"
+{code}
+{note}Different arguments and steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See [http://jira.codehaus.org/browse/MJAR-68] and [http://jira.codehaus.org/browse/MRELEASE-285].
+{code:none}
+$ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -DpreparationGoals="clean install"
+... Build failed....
+$ mvn install -DskipTests
+$ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -DpreparationGoals="clean install"
+{code}
+{note}
+# Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
+{code:none}
+$ cd ..
+$ tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
+$ cd 2.0.1-rc1
+{code}
+# Perform the release
+## This step will create a maven staging repository and site for use in testing and voting. You will be prompted for your repository.apache.org and people.apache.org password several times if you have not added server profiles to your settings.xml. See [Release Setup] for more information.
+{code:none}
+$ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
+{code}
+## The maven-release-plugin is configured with goals "deploy site site-deploy" and will deploy the site files to a staging-site directory on people.apache.org.
+# Verify the release artifacts
+## Verify the HTML links in staging-site/index.html are correct
+### Login to people.apache.org
+### Edit public_html/openjpa/\[release\]/staging-site/index.html and updates the followings:
+#### {code:none}
+ <a href="downloads/">Downloads</a>
+ to
+ <a href="apache-openjpa/downloads/">Downloads</a>
+{code}
+#### {code:none}
+ <a href="docs/index.html">docs/index.html</a></td>
+ to
+ <a href="apache-openjpa/docs/index.html">docs/index.html</a></td>
+{code}
+## Login to [Nexus - https://repository.apache.org/index.html|https://repository.apache.org/index.html]
+## Verify the staged artifacts in the nexus repo
+### Build Promotion --> Staging Repositories
+### Select/check org.apache.openjpa-xxx
+### In Browser tab, navigate through the artifact tree and make sure that all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. See [http://people.apache.org/~henkp/repo/faq.html] and [http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig]
+## Close the nexus staging repo
+### Select/check org.apache.openjpa-xxx and select Close.
+# Put the release candidate up for a vote
+## Create a VOTE email thread on dev@openjpa to record votes as replies, like -
+{code:none}
+To: dev@
+Subject: [VOTE] Apache OpenJPA 2.0.1 Release Candidate
+
+I've created a 2.0.1 release candidate, with the following artifacts up for a vote:
+
+SVN source tag (rXXXXXX):
+https://svn.apache.org/repos/asf/openjpa/tags/2.0.1/
+
+Maven staging repo:
+https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/
+
+Source release:
+https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/org/apache/openjpa/openjpa-parent/2.0.1/openjpa-parent-2.0.1-source-release.zip
+
+Javadoc staging site:
+http://people.apache.org/~dwoods/openjpa/2.0.1/staging-site/apidocs/
+
+PGP release keys (signed using D018E6B1):
+https://svn.apache.org/repos/asf/openjpa/KEYS
+
+
+Vote will be open for 72 hours.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
+
+{code}
+## Create a DISCUSS email thread on dev@ for any vote questions, like -
+{code:none}
+To: dev@
+Subject: [DISCUSS] Apache OpenJPA 2.0.1 Release Candidate
+
+Discussion thread for vote on 2.0.1 release candidate, with SVN source tag (rXXXXXX).
+
+For more information on the release process, checkout -
+http://www.apache.org/dev/release.html
+http://incubator.apache.org/guides/releasemanagement.html
+
+Some of the things to check before voting are:
+- does "mvn apache-rat:check" pass on the source
+- can you build the contents of source-release.zip and svn tag
+- do all of the staged jars/zips contain the required LICENSE and NOTICE files
+- are all of the staged jars signed and the signature verifiable
+- is the signing key in the project's KEYS file and on a public server
+- does the release pass the TCK
+
+{code}
+## Perform a review of the release and cast your vote. See the following for more details on Apache releases -
+### [http://www.apache.org/dev/release.html]
+### [http://incubator.apache.org/guides/releasemanagement.html]
+## A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - [#Recovering from a vetoed release]
+## After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -
+### reply to the initial email and prepend to the original subject -
+{code:none}[RESULTS]{code}
+### Include a list of everyone who voted +1, 0 or -1.
+# Finalizing a release
+## Release the staged nexus artifacts -
+### https://repository.apache.org/index.html
+### Build Promotion --> Staging Repositories
+### Select/check org.apache.openjpa-xxx and select Release.
+## Copy the staged site over to the openjpa/builds location on people.apache.org.
+### ssh to people.apache.org
+{code:none}
+$ mkdir /www/openjpa.apache.org/builds/2.0.1
+$ cp -r ~/public_html/openjpa/2.0.1/staging-site/* /www/openjpa.apache.org/builds/2.0.1/
+$ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
+{code}
+### Update the assemblies in the Downloads directory.
+For this, we'll just wget copies of the released assemblies with their signatures and hashes from the Apache repo:
+{code:none}
+$ cd /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
+wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
+wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
+{code}
+Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP files above.
+### verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is populated correctly by comparing it to a previous release.
+{code:none}
+$ rm /www/openjpa.apache.org/docs/latest
+$ ln -fvs ../builds/2.0.1/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest
+{code}
+## Copy the distribution artifacts over to the distribution area.
+{code:none}
+mkdir /www/www.apache.org/dist/openjpa/2.0.1
+cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/2.0.1/
+chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
+chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
+{code}
+### Optional: Remove the previous version from /dist. Ie if you're publishing 2.0.1 you would remove 2.0.0. Verify that the release being removed is in the distribution archives before removing.
+{code:none}
+$ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
+$ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.0
+{code}
+## Update the [JIRA Releases | https://issues.apache.org/jira/browse/OPENJPA] page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.
+# Update wiki pages
+## After the distribution and build files have been mirrored out to the external sites (takes about an hour), update the [Downloads] and [Documentation] pages with the new release.
+## Make a blog announcement on the OpenJPA wiki.
+*** Go to [Confluence|https://cwiki.apache.org/confluence/display/openjpa/Index], "+Add" -> "Blog Post".
+# Announcing the release
+## After the Maven mirrors have had time to update (24 hours to be on the safe side) and the wiki updates have been exported and mirrored to the external website, then it's time to announce the release. Make an announcement about the release on the dev@, user@ and [mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html#foundation-announce])
+{note}
+Make sure you send the announcement to announce@apache.org from your user@apache.org. This can be achieved using gmail by setting the "From" field to user@apche.org instead of user@gmail.com when sending the announcement.
+{note}
+
+\\
+
+h3. Recovering from a vetoed release
+# Reply to the initial vote email and prepend to the original subject -
+{code:none}[CANCELED]{code}
+# Rollback the version upgrades in trunk by either -
+## Restore the 2.0.1-rc1.tar.gz and run
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+## Manually revert the versions in trunk to the prior version and commit
+# Delete the svn tag created by the release:perform step -
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/openjpa/tags/2.0.1 -m "rollback release attempt"
+{code}
+# Drop the nexus staging repo
+## https://repository.apache.org/index.html
+## Enterprise --> Staging
+## Staging tab --> Name column --> org.apache.openjpa
+## Right click on the closed staging repo (org.apache.openjpa-XXX) and select Drop.
+# Remove the staged site
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ cd ~/public_html/openjpa
+$ rm -fr ${project.version}
+{code}
+# Make the required updates that caused the vote to be canceled
+# Spin another release candidate!
+
+\\
+
+h3. {anchor:verifySig}Verifying release signatures
+
+On unix platforms the following command can be executed -
+{code:none}
+for file in `find . -type f -iname '*.asc'`
+do
+ gpg --verify ${file}
+done
+{code}
+
+You'll need to look at the output to ensure it contains only good signatures -
+{code:none}
+gpg: Good signature from ...
+gpg: Signature made ...
+{code}
+
+\\
Added: openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).cwiki (added)
+++ openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,289 @@
+We're starting to move our builds over to using the Apache Nexus repository (repository.apache.org) for releasing SNAPSHOT and release artifacts. More details on releasing artifacts and using Nexus can be found on the Maven website at - [http://maven.apache.org/developers/release/apache-release.html]
+
+h3. Release Steps for OpenJPA 1.2.x - 2.1.x
+
+# Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
+## Increase the default Java heap available to Maven (required for Java SE 6)
+{code:none}
+export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
+{code}
+## Use the latest Sun 1.6.0 JDK (1.5.0 for 1.2.x and 1.3.x)
+## Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
+## Make sure the [Release Setup] steps have been performed.
+# Prepare the source for release:
+## Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
+## Update the text files in a working copy of the openjpa-project subdir -
+### Update the CHANGES.txt based on the Text release reports from JIRA.
+#### Choose the release from the "Versions" tab in the [releases page|https://issues.apache.org/jira/browse/OPENJPA/fixforversion/].
+#### Click "Release Notes" link in upper right.
+### Update the RELEASE-NOTES.html based on the HTML release reports from JIRA.
+### Review and update README.txt and BUILDING.txt if needed.
+### Commit any changes back to svn -
+{code:none}
+$ svn commit -m "updating files for release"
+{code}
+## Stage any Roadmap or Release landing pages on the wiki.
+## Verify the source has the required headers before trying to release.
+{code:none}
+$ mvn apache-rat:check
+{code}
+## Perform a full build with tests
+{code:none}
+$ mvn clean install -Papache-release,docbook-profile,test-derby,bval
+{code}
+## Run the JPA 1.0 TCK (for 1.x) and JPA 2.0 TCK (for 2.x) to verify the latest code passes.
+## Perform a full build and deploy the SNAPSHOT artifacts
+{code:none}
+$ mvn clean deploy site site-deploy -Papache-release,docbook-profile,test-derby,bval -DskipTests
+{code}
+## Inspect the files in your local target directories to ensure:
+### All jars and zips include: LICENSE and NOTICE files
+### The NOTICE files cover all third-party included files (like XSD schemas)
+### The LICENSE files include any third-party licenses (like XSD schemas)
+### The openjpa and openjpa-all jars include the right packages.
+### The openjpa source and release distribution files have the right content.
+### All jars/zips/poms have .asc (PGP signature) and md5 files
+# For new major releases (like 2.0.0 to 2.1.0)
+## Create a sub-branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. It also provides a future maintenance branch (like 2.0.x.) A branch can be made by running: \\
+{code:none}
+$ mvn release:branch -DbranchName=2.0.x [-Dusername=svn.user -Dpassword=svn.password]
+{code}
+# Checkout a clean copy of the trunk/branch to release using command line svn.
+## Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing and will get included in the source distribution. \\
+{code:none}
+$ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/ 2.0.1-rc1/
+{code}
+{note}
+Make sure you use https:// protocol because the following release:prepare step requires update to the svn repository.
+{note}
+# (Optional) Do a dry run of the release:prepare step.
+## The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
+### Release version - take the default - (default 2.0.1)
+### SCM release tag - *DO NOT TAKE THE DEFAULT - (default openjpa-parent-2.0.1): : 2.0.1
+### New development version - take the default - (default 2.0.2-SNAPSHOT)
+### _optional_ if you have not specified a GPG passphrase in settings.xml you will be prompted for it.
+{code:none}
+$ mvn -Papache-release release:prepare -DdryRun=true
+{code}
+{note}
+If you cancel a release:prepare before it updates the pom.xml versions, then use the *release:clean* goal to just remove the extra files that were created. If that doesn't help, try running *mvn clean*.
+{note}
+## Verify that the release process completed as expected
+### The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.
+### If other formatting changes have been made you should review the changes and then commit them -
+{code:none}
+$ svn commit -m "fixing formatting for release"
+{code}
+### Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful
+#### Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
+#### verify signatures [Verifying release signatures|#verifySig]
+## Once any failures or required updates have been committed to svn, rollback the release prepare files -
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+# Prepare the release
+## Run the "release:prepare" step for real this time. You'll be prompted for the same version information and optionally your GPG passphrase again.
+{code:none}
+$ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -Dusername=svn.user -Dpassword=svn.password -DpreparationGoals="clean install"
+{code}
+{note}Different arguments and steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See [http://jira.codehaus.org/browse/MJAR-68] and [http://jira.codehaus.org/browse/MRELEASE-285].
+{code:none}
+$ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -Dusername=svn.user -Dpassword=svn.password -DpreparationGoals="clean install"
+... Build failed....
+$ mvn install -DskipTests
+$ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -Dusername=svn.user -Dpassword=svn.password -DpreparationGoals="clean install"
+{code}
+{note}
+# Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
+{code:none}
+$ cd ..
+$ tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
+$ cd 2.0.1-rc1
+{code}
+# Perform the release
+## This step will create a maven staging repository and site for use in testing and voting. You will be prompted for your repository.apache.org and people.apache.org password several times if you have not added server profiles to your settings.xml. See [Release Setup] for more information.
+{code:none}
+$ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
+{code}
+## The maven-release-plugin is configured with goals "deploy site site-deploy" and will deploy the site files to a staging-site directory on people.apache.org.
+# Verify the release artifacts
+## Verify the HTML links in staging-site/index.html are correct
+### Login to people.apache.org
+### Edit public_html/openjpa/\[release\]/staging-site/index.html and updates the followings:
+#### {code:none}
+ <a href="downloads/">Downloads</a>
+ to
+ <a href="apache-openjpa/downloads/">Downloads</a>
+{code}
+#### {code:none}
+ <a href="docs/index.html">docs/index.html</a></td>
+ to
+ <a href="apache-openjpa/docs/index.html">docs/index.html</a></td>
+{code}
+## Login to [Nexus - https://repository.apache.org/index.html|https://repository.apache.org/index.html]
+## Verify the staged artifacts in the nexus repo
+### Build Promotion --> Staging Repositories
+### Select/check org.apache.openjpa-xxx
+### In Browser tab, navigate through the artifact tree and make sure that all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. See [http://people.apache.org/~henkp/repo/faq.html] and [http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig]
+## Close the nexus staging repo
+### Select/check org.apache.openjpa-xxx and select Close.
+# Put the release candidate up for a vote
+## Create a VOTE email thread on dev@openjpa to record votes as replies, like -
+{code:none}
+To: dev@
+Subject: [VOTE] Apache OpenJPA 2.0.1 Release Candidate
+
+I've created a 2.0.1 release candidate, with the following artifacts up for a vote:
+
+SVN source tag (rXXXXXX):
+https://svn.apache.org/repos/asf/openjpa/tags/2.0.1/
+
+Maven staging repo:
+https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/
+
+Source release:
+https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/org/apache/openjpa/openjpa-parent/2.0.1/openjpa-parent-2.0.1-source-release.zip
+
+Javadoc staging site:
+http://people.apache.org/~dwoods/openjpa/2.0.1/staging-site/apidocs/
+
+PGP release keys (signed using D018E6B1):
+https://svn.apache.org/repos/asf/openjpa/KEYS
+
+
+Vote will be open for 72 hours.
+
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove (and reason why)
+
+{code}
+## Create a DISCUSS email thread on dev@ for any vote questions, like -
+{code:none}
+To: dev@
+Subject: [DISCUSS] Apache OpenJPA 2.0.1 Release Candidate
+
+Discussion thread for vote on 2.0.1 release candidate, with SVN source tag (rXXXXXX).
+
+For more information on the release process, checkout -
+http://www.apache.org/dev/release.html
+http://incubator.apache.org/guides/releasemanagement.html
+
+Some of the things to check before voting are:
+- does "mvn apache-rat:check" pass on the source
+- can you build the contents of source-release.zip and svn tag
+- do all of the staged jars/zips contain the required LICENSE and NOTICE files
+- are all of the staged jars signed and the signature verifiable
+- is the signing key in the project's KEYS file and on a public server
+- does the release pass the TCK
+
+{code}
+## Perform a review of the release and cast your vote. See the following for more details on Apache releases -
+### [http://www.apache.org/dev/release.html]
+### [http://incubator.apache.org/guides/releasemanagement.html]
+## A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - [#Recovering from a vetoed release]
+## After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -
+### reply to the initial email and prepend to the original subject -
+{code:none}[RESULTS]{code}
+### Include a list of everyone who voted +1, 0 or -1.
+# Finalizing a release
+## Release the staged nexus artifacts -
+### https://repository.apache.org/index.html
+### Build Promotion --> Staging Repositories
+### Select/check org.apache.openjpa-xxx and select Release.
+## Copy the staged site over to the openjpa/builds location on people.apache.org.
+### ssh to people.apache.org
+{code:none}
+$ mkdir /www/openjpa.apache.org/builds/2.0.1
+$ cp -r ~/public_html/openjpa/2.0.1/staging-site/* /www/openjpa.apache.org/builds/2.0.1/
+$ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
+{code}
+### Update the assemblies in the Downloads directory.
+For this, we'll just wget copies of the released assemblies with their signatures and hashes from the Apache repo:
+{code:none}
+$ cd /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
+wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
+wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
+{code}
+Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP files above.
+### copy the RELEASE-NOTES.html to the proper location
+{code:none}
+$ cd ...../2.0.1-rc1/
+$ scp openjpa-project/RELEASE-NOTES.html allee8285@people.apache.org:/www/openjpa.apache.org/builds/2.0.1/apache-openjpa
+{code}
+### verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is populated correctly by comparing it to a previous release.
+{code:none}
+$ rm /www/openjpa.apache.org/docs/latest
+$ ln -fvs ../builds/2.0.1/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest
+{code}
+## Copy the distribution artifacts over to the distribution area.
+{code:none}
+mkdir /www/www.apache.org/dist/openjpa/2.0.1
+cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/2.0.1/
+chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
+chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
+{code}
+### Optional: Remove the previous version from /dist. Ie if you're publishing 2.0.1 you would remove 2.0.0. Verify that the release being removed is in the distribution archives before removing.
+{code:none}
+$ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
+$ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.0
+{code}
+## Update the [JIRA Releases | https://issues.apache.org/jira/browse/OPENJPA] page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.
+# Update wiki pages
+## After the distribution and build files have been mirrored out to the external sites (takes about an hour), update the [Downloads] and [Documentation] pages with the new release.
+## Make a blog announcement on the OpenJPA wiki.
+*** Go to [Confluence|https://cwiki.apache.org/confluence/display/openjpa/Index], "+Add" -> "Blog Post".
+# Announcing the release
+## After the Maven mirrors have had time to update (24 hours to be on the safe side) and the wiki updates have been exported and mirrored to the external website, then it's time to announce the release. Make an announcement about the release on the dev@, user@ and [mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html#foundation-announce])
+{note}
+Make sure you send the announcement to announce@apache.org from your user@apache.org. This can be achieved using gmail by setting the "From" field to user@apche.org instead of user@gmail.com when sending the announcement.
+{note}
+
+\\
+
+h3. Recovering from a vetoed release
+# Reply to the initial vote email and prepend to the original subject -
+{code:none}[CANCELED]{code}
+# Rollback the version upgrades in trunk by either -
+## Restore the 2.0.1-rc1.tar.gz and run
+{code:none}
+$ mvn -Papache-release release:rollback
+{code}
+## Manually revert the versions in trunk to the prior version and commit
+# Delete the svn tag created by the release:perform step -
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/openjpa/tags/2.0.1 -m "rollback release attempt"
+{code}
+# Drop the nexus staging repo
+## https://repository.apache.org/index.html
+## Enterprise --> Staging
+## Staging tab --> Name column --> org.apache.openjpa
+## Right click on the closed staging repo (org.apache.openjpa-XXX) and select Drop.
+# Remove the staged site
+{code:none}
+$ ssh ${user.name}@people.apache.org
+$ cd ~/public_html/openjpa
+$ rm -fr ${project.version}
+{code}
+# Make the required updates that caused the vote to be canceled
+# Spin another release candidate!
+
+\\
+
+h3. {anchor:verifySig}Verifying release signatures
+
+On unix platforms the following command can be executed -
+{code:none}
+for file in `find . -type f -iname '*.asc'`
+do
+ gpg --verify ${file}
+done
+{code}
+
+You'll need to look at the output to ensure it contains only good signatures -
+{code:none}
+gpg: Good signature from ...
+gpg: Signature made ...
+{code}
+
+\\
Propchange: openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).cwiki
------------------------------------------------------------------------------
svn:eol-style = native
Added: openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29.mdtext?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext (added)
+++ openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext Wed Nov 14 01:49:37 2012
@@ -0,0 +1,282 @@
+Title: Apache Nexus Release Process (1.2.x-2.1.x)
+
+We're starting to move our builds over to using the Apache Nexus repository (repository.apache.org) for releasing SNAPSHOT and release artifacts. More details on releasing artifacts and using Nexus can be found on the Maven website at - [http://maven.apache.org/developers/release/apache-release.html](http://maven.apache.org/developers/release/apache-release.html)
+
+<!--<a name="ApacheNexusReleaseProcess(1.2.x-2.1.x)-ReleaseStepsforOpenJPA1.2.x-2.1.x"></a>-->
+
+Release Steps for OpenJPA 1.2.x - 2.1.x
+======
+
+Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
+- - - - - -
+
+2. Increase the default Java heap available to Maven (required for Java SE 6)
+ export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
+
+2. Use the latest Sun 1.6.0 JDK (1.5.0 for 1.2.x and 1.3.x)
+3. Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
+
+Instructions
+- - - - -
+4. Make sure the [Release Setup] steps have been performed.
+5. Prepare the source for release:
+ * Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
+ * Update the text files in a working copy of the openjpa-project subdir -
+ * Update the CHANGES.txt based on the Text release reports from JIRA.
+ * Choose the release from the "Versions" tab in the [releases page|https://issues.apache.org/jira/browse/OPENJPA/fixforversion/]
+ * Click "Release Notes" link in upper right.
+ * Update the RELEASE-NOTES.html based on the HTML release reports from JIRA.
+ * Review and update README.txt and BUILDING.txt if needed.
+ * Commit any changes back to svn -
+ $ svn commit -m "updating files for release"
+
+1. Stage any Roadmap or Release landing pages on the wiki.
+1. Verify the source has the required headers before trying to release.
+ $ mvn apache-rat:check
+
+1. Perform a full build with tests
+ $ mvn clean install -Papache-release,docbook-profile,test-derby,bval
+
+1. * Run the JPA 1.0 TCK (for 1.x) and JPA 2.0 TCK (for 2.x) to verify the latest code passes.
+1. * Perform a full build and deploy the SNAPSHOT artifacts
+ $ mvn clean deploy site site-deploy -Papache-release,docbook-profile,test-derby,bval -DskipTests
+
+1. Inspect the files in your local target directories to ensure:
+ * All jars and zips include: LICENSE and NOTICE files
+ * The NOTICE files cover all third-party included files (like XSD schemas)
+ * The LICENSE files include any third-party licenses (like XSD schemas)
+ * The openjpa and openjpa-all jars include the right packages.
+ * The openjpa source and release distribution files have the right content.
+ * All jars/zips/poms have .asc (PGP signature) and md5 files
+
+1. For new major releases (like 2.0.0 to 2.1.0)
+ * Create a sub-branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. It also provides a future maintenance branch (like 2.0.x.) A branch can be made by running: \\ $ mvn release:branch -DbranchName=2.0.x [-Dusername=svn.user -Dpassword=svn.password]
+
+1. Checkout a clean copy of the trunk/branch to release using command line svn.
+
+ $ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/ 2.0.1-rc1/
+
+1. (Optional) Do a dry run of the release:prepare step.
+ * The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
+ * Release version - take the default - (default 2.0.1)
+ * SCM release tag - *DO NOT TAKE THE DEFAULT* - (default openjpa-parent-2.0.1): : 2.0.1
+ * New development version - take the default - (default 2.0.2-SNAPSHOT)
+ * _optional_ if you have not specified a GPG passphrase in settings.xml you will be prompted for it.
+ $ mvn -Papache-release release:prepare -DdryRun=true
+
+<!--{note}-->
+If you cancel a release:prepare before it updates the pom.xml versions,
+then use the *release:clean* goal to just remove the extra files that were
+created. If that doesn't help, try running *mvn clean*.
+{note}
+1. Verify that the release process completed as expected
+ * The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.
+ * If other formatting changes have been made you should review the changes and then commit them -
+ $ svn commit -m "fixing formatting for release"
+
+ * Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful
+ * Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version. *
+ * verify signatures [Verifying release signatures|*verifySig]
+ * Once any failures or required updates have been committed to svn, rollback the release prepare files -
+ $ mvn -Papache-release release:rollback
+
+1. Prepare the release
+ * Run the "release:prepare" step for real this time. You'll be prompted for the same version information and optionally your GPG passphrase again.
+ $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests [-Dusername=svn.user -Dpassword=svn.password](-dusername=svn.user--dpassword=svn.password.html) -DpreparationGoals="clean install"
+
+<!--{note} -->
+Different arguments and steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See [http://jira.codehaus.org/browse/MJAR-68] and [http://jira.codehaus.org/browse/MRELEASE-285].
+ $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -DpreparationGoals="clean install"
+ ... Build failed....
+ $ mvn install -DskipTests
+ $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests -DpreparationGoals="clean install"
+
+<!--{note}-->
+1. Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
+ cd ..
+ tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
+ cd 2.0.1-rc1
+
+1. Perform the release
+ * This step will create a maven staging repository and site for use in testing and voting. You will be prompted for your repository.apache.org and people.apache.org password several times if you have not added server profiles to your settings.xml. See [Release Setup] for more information.
+ $ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
+
+1. The maven-release-plugin is configured with goals "deploy site site-deploy" and will deploy the site files to a staging-site directory on people.apache.org.
+1. Verify the release artifacts
+1. Verify the HTML links in staging-site/index.html are correct
+ * Login to people.apache.org
+ * Edit public_html/openjpa/\[release\](release\.html) /staging-site/index.html and updates the followings:
+ * <a href="downloads/">Downloads</a>
+ to
+ <a href="apache-openjpa/downloads/">Downloads</a>
+
+ * <a href="docs/index.html">docs/index.html</a></td>
+ to
+ <a href="apache-openjpa/docs/index.html">docs/index.html</a></td>
+
+1. * Login to [Nexus - https://repository.apache.org/index.html](https://repository.apache.org/index.html)
+1. * Verify the staged artifacts in the nexus repo
+1. ** Build Promotion --> Staging Repositories
+1. ** Select/check org.apache.openjpa-xxx
+1. ** In Browser tab, navigate through the artifact tree and make sure that
+all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5
+files. See [http://people.apache.org/~henkp/repo/faq.html](http://people.apache.org/~henkp/repo/faq.html)
+ and [http://www.apache.org/dev/release-signing.html*openpgp-ascii-detach-sig]
+1. * Close the nexus staging repo
+1. ** Select/check org.apache.openjpa-xxx and select Close.
+1. Put the release candidate up for a vote
+1. * Create a VOTE email thread on dev@openjpa to record votes as replies, like -
+ To: dev@
+ Subject: [VOTE](vote.html)
+ Apache OpenJPA 2.0.1 Release Candidate
+
+ I've created a 2.0.1 release candidate, with the following artifacts up for
+ a vote:
+
+ SVN source tag (rXXXXXX):
+ https://svn.apache.org/repos/asf/openjpa/tags/2.0.1/
+
+ Maven staging repo:
+ https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/
+
+ Source release:
+ https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/org/apache/openjpa/openjpa-parent/2.0.1/openjpa-parent-2.0.1-source-release.zip
+
+ Javadoc staging site:
+ http://people.apache.org/~dwoods/openjpa/2.0.1/staging-site/apidocs/
+
+ PGP release keys (signed using D018E6B1):
+ https://svn.apache.org/repos/asf/openjpa/KEYS
+
+
+ Vote will be open for 72 hours.
+
+ [ ](-.html)
+ +1 approve
+ [ ](-.html)
+ +0 no opinion
+ [ ](-.html)
+ -1 disapprove (and reason why)
+
+
+ * Create a DISCUSS email thread on dev@ for any vote questions, like -
+ To: dev@
+ Subject: [DISCUSS]
+ Apache OpenJPA 2.0.1 Release Candidate
+
+ Discussion thread for vote on 2.0.1 release candidate, with SVN source tag
+(rXXXXXX).
+
+ For more information on the release process, checkout -
+ http://www.apache.org/dev/release.html
+ http://incubator.apache.org/guides/releasemanagement.html
+
+ Some of the things to check before voting are:
+ - does "mvn apache-rat:check" pass on the source
+ - can you build the contents of source-release.zip and svn tag
+ - do all of the staged jars/zips contain the required LICENSE and NOTICE
+files
+ - are all of the staged jars signed and the signature verifiable
+ - is the signing key in the project's KEYS file and on a public server
+ - does the release pass the TCK
+
+
+1. * Perform a review of the release and cast your vote. See the following
+for more details on Apache releases -
+ * [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
+ * [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
+ * A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - [*Recovering from a vetoed release](*recovering-from-a-vetoed-release.html)
+1. * After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -
+ * reply to the initial email and prepend to the original subject -
+ [RESULTS](results.html)
+ * Include a list of everyone who voted +1, 0 or -1.
+1. Finalizing a release
+ * Release the staged nexus artifacts -
+ * https://repository.apache.org/index.html
+ * Build Promotion --> Staging Repositories
+ * Select/check org.apache.openjpa-xxx and select Release.
+ * Copy the staged site over to the openjpa/builds location on people.apache.org.
+ * ssh to people.apache.org
+ $ mkdir /www/openjpa.apache.org/builds/2.0.1
+ $ cp -r ~/public_html/openjpa/2.0.1/staging-site/*
+ /www/openjpa.apache.org/builds/2.0.1/
+ $ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
+
+ * Update the assemblies in the Downloads directory. For this, we'll just wget copies of the released assemblies with their signatures and hashes from the Apache repo:
+ $ cd /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
+ wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
+ wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
+
+Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP files
+above.
+1. ** verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is populated correctly by comparing it to a previous release.
+ $ rm /www/openjpa.apache.org/docs/latest
+ $ ln -fvs ../builds/2.0.1/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest
+
+ * Copy the distribution artifacts over to the distribution area.
+ mkdir /www/www.apache.org/dist/openjpa/2.0.1
+ cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/2.0.1/
+ chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
+ chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
+
+1. ** Optional: Remove the previous version from /dist. Ie if you're publishing 2.0.1 you would remove 2.0.0. Verify that the release being removed is in the distribution archives before removing.
+ $ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
+ $ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.0
+
+ * Update the [JIRA Releases | https://issues.apache.org/jira/browse/OPENJPA] page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.
+* Update wiki pages
+ * After the distribution and build files have been mirrored out to the external sites (takes about an hour), update the [Downloads] and [Documentation] pages with the new release.
+ * Make a blog announcement on the OpenJPA wiki.
+ * Go to [Confluence|https://cwiki.apache.org/confluence/display/openjpa/Index]
+**** "+Add" -> "Blog Post".
+* Announcing the release
+ * After the Maven mirrors have had time to update (24 hours to be on the safe side) and the wiki updates have been exported and mirrored to the external website, then it's time to announce the release. Make an announcement about the release on the dev@, user@ and [mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html*foundation-announce]
+)
+ <!--{note}-->
+Make sure you send the announcement to announce@apache.org from your
+user@apache.org. This can be achieved using gmail by setting the "From"
+field to user@apche.org instead of user@gmail.com when sending the
+announcement.
+ <!--{note}-->
+
+- - - - - - -
+Recovering from a vetoed release
+* Reply to the initial vote email and prepend to the original subject - [CANCELED]
+* Rollback the version upgrades in trunk by either -
+ * Restore the 2.0.1-rc1.tar.gz and run
+ $ mvn -Papache-release release:rollback
+
+1. * Manually revert the versions in trunk to the prior version and commit
+1. Delete the svn tag created by the release:perform step -
+ $ svn del https://svn.apache.org/repos/asf/openjpa/tags/2.0.1 -m "rollback release attempt"
+
+* Drop the nexus staging repo
+ * https://repository.apache.org/index.html
+ * Enterprise --> Staging
+ * Staging tab --> Name column --> org.apache.openjpa
+ * Right click on the closed staging repo (org.apache.openjpa-XXX) and select Drop.
+* Remove the staged site
+ $ ssh ${user.name}@people.apache.org
+ $ cd ~/public_html/openjpa
+ $ rm -fr ${project.version}
+
+1. Make the required updates that caused the vote to be canceled
+1. Spin another release candidate!
+
+
+<a name="ApacheNexusReleaseProcess(1.2.x-2.1.x)-{anchor:verifySig}Verifyingreleasesignatures"></a>
+ * {anchor:verifySig}Verifying release signatures
+
+On unix platforms the following command can be executed -
+ for file in `find . -type f -iname '*.asc'`
+ do
+ gpg --verify ${file}
+ done
+
+
+You'll need to look at the output to ensure it contains only good
+signatures -
+ gpg: Good signature from ...
+ gpg: Signature made ...
+
+
Added: openjpa/site/trunk/content/apidiscussionfollowup
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apidiscussionfollowup?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/apidiscussionfollowup (added)
+++ openjpa/site/trunk/content/apidiscussionfollowup Wed Nov 14 01:49:37 2012
@@ -0,0 +1,57 @@
+After our meeting, Patrick did some analysis of our current API and where we might want to take it. Here are some initial observations. Please comment as appropriate.
+- OpenJPAEntityManager extends EntityTransaction; should it?
+clr no, I like your idea below to add an OpenJPAEntityTransaction interface, so users could do OpenJPAEntityTransaction tx = (OpenJPAEntityTransaction)em.getTransaction();
+
+- StoreCache, QueryResultCache, Extent, FetchPlan, Generator, OpenJPAQuery all have getDelegate() calls that return an underlying kernel implementation detail. Maybe these should be pushed down to theh impl classes only?
+clr I agree these don't belong in OpenJPAEntityManager
+
+- OpenJPAEntityManager and OpenJPAEntityManagerFactory both have a getConfiguration() method. Maybe this should be pushed down to the impl classes only?
+clr I don't know when I would use the Configuration, so no opinion on this one.
+
+- OpenJPAEntityManager.getManagedRuntime() should be pushed down to impl only
+clr I agree
+
+- The following methods in OpenJPAPersistence return things that are not currently part of what I consider a user-focused API:
+ toBrokerFactory()
+ toBroker()
+ toEntityManagerFactory()
+ toEntityManager()
+ getMetaData()
+ toOpenJPAObjectId() / toOpenJPAObjectIds()\\
+ \\
+ I think that we should move these methods to o.a.o.persistence.impl.ImplHelper or some other impl-specific class.\\
+\\
+clr I agree.
+
+- We have a bunch of methods in OpenJPAEntityManager that seem like they should belong on a new OpenJPAEntityTransaction interface:
+ public void commitAndResume();
+ public void rollbackAndResume();
+ public void setRollbackOnly(); (already part of EntityTransaction)
+ public void setRollbackOnly(Throwable cause);
+ public Throwable getRollbackCause();
+ public boolean getRollbackOnly(); (also already part of EntityTransaction)\\
+\\
+ public boolean isStoreActive();
+ public void beginStore();\\
+\\
+ I'm not quite as sure where these belong:\\
+\\
+ public void setSavepoint(String name);
+ public void rollbackToSavepoint();
+ public void rollbackToSavepoint(String name);
+ public void releaseSavepoint();
+ public void releaseSavepoint(String name);\\
+\\
+ public void preFlush();
+ public void validateChanges();\\
+\\
+clr All of these seem like transaction-focused methods that belong in OpenJPAEntityTransaction...
+pcl: I moved the commit / rollback / rollbackOnly stuff into OpenJPAEntityTransaction, but things are trickier for the rest of the methods: you can only call EM.getTransaction() when not in a JTA context, and these other methods are valuable in a JTA env as well as a non-JTA env. So, we can either leave them on OpenJPAEM or create some other interface for them.
+
+
+- I don't like the OpenJPAEntityManager.setLargeTransaction() method name - I'd like to rename it to setTrackChangesByType() instead, since it better reflects what the method does. (We can easily deprecate the old method if desired.)
+clr I kinda like setLargeTransaction. It's more "task-oriented".
+pcl: The thing is that if you are using large transactions, you might want to call either (or both) setLargeTx() and setPopulateDataCache(), depending on the nature of the tx workload.
+
+- I think that it might make sense to move OpenJPAEntityManager.setPopulateDataCache() to FetchPlan, and rename FetchPlan.setQueryResultCache() to setPopulateQueryResultCache(). (We can easily deprecate the old methods if desired.)
+clr No opinion here.
\ No newline at end of file
Added: openjpa/site/trunk/content/apidiscussionfollowup.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apidiscussionfollowup.cwiki?rev=1409057&view=auto
==============================================================================
--- openjpa/site/trunk/content/apidiscussionfollowup.cwiki (added)
+++ openjpa/site/trunk/content/apidiscussionfollowup.cwiki Wed Nov 14 01:49:37 2012
@@ -0,0 +1,57 @@
+After our meeting, Patrick did some analysis of our current API and where we might want to take it. Here are some initial observations. Please comment as appropriate.
+- OpenJPAEntityManager extends EntityTransaction; should it?
+clr no, I like your idea below to add an OpenJPAEntityTransaction interface, so users could do OpenJPAEntityTransaction tx = (OpenJPAEntityTransaction)em.getTransaction();
+
+- StoreCache, QueryResultCache, Extent, FetchPlan, Generator, OpenJPAQuery all have getDelegate() calls that return an underlying kernel implementation detail. Maybe these should be pushed down to theh impl classes only?
+clr I agree these don't belong in OpenJPAEntityManager
+
+- OpenJPAEntityManager and OpenJPAEntityManagerFactory both have a getConfiguration() method. Maybe this should be pushed down to the impl classes only?
+clr I don't know when I would use the Configuration, so no opinion on this one.
+
+- OpenJPAEntityManager.getManagedRuntime() should be pushed down to impl only
+clr I agree
+
+- The following methods in OpenJPAPersistence return things that are not currently part of what I consider a user-focused API:
+ toBrokerFactory()
+ toBroker()
+ toEntityManagerFactory()
+ toEntityManager()
+ getMetaData()
+ toOpenJPAObjectId() / toOpenJPAObjectIds()\\
+ \\
+ I think that we should move these methods to o.a.o.persistence.impl.ImplHelper or some other impl-specific class.\\
+\\
+clr I agree.
+
+- We have a bunch of methods in OpenJPAEntityManager that seem like they should belong on a new OpenJPAEntityTransaction interface:
+ public void commitAndResume();
+ public void rollbackAndResume();
+ public void setRollbackOnly(); (already part of EntityTransaction)
+ public void setRollbackOnly(Throwable cause);
+ public Throwable getRollbackCause();
+ public boolean getRollbackOnly(); (also already part of EntityTransaction)\\
+\\
+ public boolean isStoreActive();
+ public void beginStore();\\
+\\
+ I'm not quite as sure where these belong:\\
+\\
+ public void setSavepoint(String name);
+ public void rollbackToSavepoint();
+ public void rollbackToSavepoint(String name);
+ public void releaseSavepoint();
+ public void releaseSavepoint(String name);\\
+\\
+ public void preFlush();
+ public void validateChanges();\\
+\\
+clr All of these seem like transaction-focused methods that belong in OpenJPAEntityTransaction...
+pcl: I moved the commit / rollback / rollbackOnly stuff into OpenJPAEntityTransaction, but things are trickier for the rest of the methods: you can only call EM.getTransaction() when not in a JTA context, and these other methods are valuable in a JTA env as well as a non-JTA env. So, we can either leave them on OpenJPAEM or create some other interface for them.
+
+
+- I don't like the OpenJPAEntityManager.setLargeTransaction() method name - I'd like to rename it to setTrackChangesByType() instead, since it better reflects what the method does. (We can easily deprecate the old method if desired.)
+clr I kinda like setLargeTransaction. It's more "task-oriented".
+pcl: The thing is that if you are using large transactions, you might want to call either (or both) setLargeTx() and setPopulateDataCache(), depending on the nature of the tx workload.
+
+- I think that it might make sense to move OpenJPAEntityManager.setPopulateDataCache() to FetchPlan, and rename FetchPlan.setQueryResultCache() to setPopulateQueryResultCache(). (We can easily deprecate the old methods if desired.)
+clr No opinion here.
\ No newline at end of file
Propchange: openjpa/site/trunk/content/apidiscussionfollowup.cwiki
------------------------------------------------------------------------------
svn:eol-style = native