[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] New preliminary repo is available...

I neglected to mention that unless new issues are found with this repo, I expect to be going live with it as soon as we are confident that it is a viable repository for all runtime development tasks (one-off-patching included).

So be sure to put it through its paces...

-Eric

On 18/07/2012 11:47 AM, Eric Gwin wrote:
at:
   git.eclipse.org/gitroot/eclipselink/prelim2.eclipselink.runtime.git

I have marked it read-only to all but me. That means pushes will fail for committers, but also that it will be downloadable via http for Edwin to test the QA scripts.

The build and tests should run without need for modification, with exception to the following known caveats:

- Moxy tests will not all download if the root path to the repo is more than about 20 characters long (on Windows).
  The Moxy team is aware of this and, I believe, has plans to shorten their test package naming.

- Git does not store/checkout empty directories, and the build is expecting an empty resource dir in utils/jaxb.
  So ant will fail currently, if the needed dir is not manually created.
  I will be fixing this along with my changes to the nightly build.

- The build still defaults to finding bnd and junit in the "../extension.lib.external" dir, so unless you've defined
  "extensions.depend.dir=<some_dir>" in a ~/build.properties file you will likely need to copy the dir to be a sibling
  of your cloned repo.
  The same is true of "extensions.oracle.depend.dir" with regards to defining it, or needing to copy.

- The plugins, javax.persistence, hermes, and utils/workbench projects are included.
   - I will be pulling out the whole utils tree, and deleting it in the active branches soon.
   - The same is true of javax.persistence - I will be posting the git repo soon.
   - The plugins dir will be removed over time in active branches as the build adapts to git. (though I plan on
     removing the plugins projects much sooner).

Let me know if you run into any issues or have questions.

-Eric
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev