Opened 14 years ago

Closed 13 years ago

#69 closed task (fixed)

Create independent build for org.opensha.commons

Reported by: Peter Powers Owned by: Kevin Milner
Priority: minor Milestone: OpenSHA 1.1
Component: build-process Version:
Keywords: Cc:

Description

Create a build step that compiles just org.opensha.commons and publish to

/var/www/html/apps/opensha/commons/

Change History (5)

comment:1 Changed 13 years ago by Peter Powers

Kevin, I created a ...html/dev/ directory for opensha jar products, e.g. 'opensha-commons.jar'. Can you add the packaging of just the commons directory for nightly and release ditribution, using the current repository as a 1.0.2 release. Shouldn't need any symlinks. I think we should shorten the dist build filenames to just e.g. opensha-commons-1.0.2.jar, keeping the releases of commons and any other future products in sync with the applications. Let's not worry about dependencies for now.

I'm working to add pages to the site that will allow access to builds.

comment:2 Changed 13 years ago by Kevin Milner

Peter, sounds good, I'll get on that. Want to aim for a 1.1 release on Friday?

comment:3 in reply to:  2 Changed 13 years ago by Peter Powers

Replying to kmilner:

Peter, sounds good, I'll get on that. Want to aim for a 1.1 release on Friday?

Yeah, that sounds good. I will be out of town.

WIll you have time to do a Masha-style release notes associated with the 1.1 milestone page?
The only other thing I want to do is remove the password protection which I'll do Monday when I'm back in the office. We're all set to go on that front, right? I'll finish up any drupal changes at that time as well.

comment:4 Changed 13 years ago by Kevin Milner

Peter, just to confirm, normal naming for nightly releases, shorter naming (version only) for dist?

Yeah I'll do a release notes page. And I'm cool with the password removal.

comment:5 Changed 13 years ago by Kevin Milner

Component: commonsbuild-process
Milestone: OpenSHA 1.1
Resolution: fixed
Status: newclosed

OK done, builds are now being done nightly to /var/www/html/dev/opensha-commons/nightly

Note that it's called "opensha-commons" and not just "commons". The directory must match the jar name in order to reuse the ant tasks for app jar building. I also did a release build (with the shorter file name).

I also created builds for opensha-complete (classes, dependencies, and data), and opensha-lite (currently it's simply classes only).

Note: See TracTickets for help on using tickets.