> * mvn install 'freezes' when downloading some dependencies.
I get that too. And yes, interrupting mvn and re-executing it seems to work
around the problem just fine.
Eventually your personal m2 repository will have everything you'll need to
build OODT—or other mvn-based projects.
Good luck,
Wooot! We are on the way!
On 2010.Nov.14, at 12.07p, Mattmann, Chris A (388J) wrote:
> Hi Folks,
>
> This VOTE has passed with the following tallies:
> ...
@apache.org)
> * Chris A. Mattmann (mattm...@apache.org)
> * Dan Crichton (crich...@apache.org)
> * David Kale (davek...@apache.org)
> * David Woollard (wooll...@apache.org)
> * Ian Holsman (i...@apache.org)
> * Joshua Garcia (joshu...@apache.org)
>
(Apologies if this is a duplicate for you.)
Colleagues:
From my workstation I have shown:
Concordance with MD5 hash
Concordance with SHA1 hash
Valid signature from one "David Woollard" that verifies the archive
All Java tests pass
All Python tests pass
I would like to say +1 for release.
Heck,
> Build succeeds, all tests pass!
Don't forget to run: cd agility; python setup.py test
Maybe we could tie it into the mvn build? What do other podlings & projects do?
> [ ] +1 Release the packages as Apache OODT 0.1-incubating
+1, nailed it. Heck, +1.196 even. Good show!
Thanks for your patience and endurance during this process.
> Can you file an issue for this against 0.1-incubating (Fix Version) and (if
> you've got time) go ahead and commit a fix to the 0.1-incubating branch and
> to the trunk?
Issue filed[1], and fix committed to the trunk[2] and 0.1-incubating[3].
Now when I run "python setup.py test" I get: "Ran 34
Hi team:
I'm getting an issue with RC2:
$ curl -L
'http://people.apache.org/~woollard/apache-oodt-0.1-incubating/rc2/apache-oodt-0.1-incubating-src.tar.gz'
| tar xzf -
$ cd apache-oodt-0.1-incubating-src/agility
$ python setup.py test
Traceback (most recent call last):
File "setup.py", line 7
Colleagues:
Thanks for fixing the old jpl.eda references in web-grid. As it was neglected
in the original import of OODT code from JPL into the Apache Incubator, it did
not get the rigorous examination that we afforded the other components.
Warm spal wishes,
Er, I mean warm swimming wishes,
Oop
We could make it "even more optimally" moot by cutting CORBA support altogether.
1999 called: they want their rambling, committee-designed,
documentation-bogged, poorly-implemented, needlessly-acronymed, lumbering,
diseased, behemoth of a remote procedure call system back.
On 2010.Sep.26, at
Woot! Fabulous report, Chris. Thanks for summarizing our accomplishments!
On 2010.Sep.8, at 10.12p, Mattmann, Chris A (388J) wrote:
> Hi Guys,
>
> I've submitted an OODT report to the Incubator wiki here [1], and signed off
> as a mentor. Please review the report and add/update if I've missed a
On the incubator status page for our project,
http://incubator.apache.org/projects/oodt.html
under the heading "OODT Project Incubation Status", there's a link labeled
"project website" which goes to the old OODT page at JPL, aka,
http://oodt.jpl.nasa.gov/. It should probably go to the
As Chris suggested, I posted some brief instructions on how to publish the
Apache OODT web site. Check 'em out at any of these addresses:
https://cwiki.apache.org/confluence/display/OODT/How+to+Publish+the+OODT+Web+Site
https://cwiki.apache.org/confluence/x/LAtkAQ
http:/
Actually, the generated site does indeed go into /site.
OODT team does: .../docs/site + .../oodt/*/target/site → svn ci .../site
Someone on minotaur: svn export .../site → /www/incubator.apache.org/oodt
At least, that's how it seems the other incubator projects do it. I think.
We could also jus
OK if no one else objects I'll go ahead and move forward with this. Thanks!
> P.S. Minor thing, but why Ob and Or instead of O and O on the OO blocks that
> are part of "OODT"?
Chemistry. Heh.
The advertising idea: I want it to look like chemical elements from a periodic
table to emphasize OOD
OODT'ers:
As part of progress on OODT-16, I've got a prototype of the Apache OODT website
up and running at
http://216.146.47.22/oodt/
This site is generated from the Maven site artifacts of the oodt tree as of
r965292 (back when "mvn site" worked for every module except catalog), comb
Good argument, Chris.
Yeah, there are plenty of people out there who don't use Maven and who will
blithely toss any set of files together into a directory in order to avoid
changing java.ext.dirs, classpath, etc.
I'm convinced. +1 to toss in some prefixes on artifact names.
Thanks for setting
n the subject?
>
> -Dave
>
>
> [1] https://issues.apache.org/jira/browse/OODT-5
>
>
> On Jul 22, 2010, at 5:10 PM, Sean Kelly wrote:
>
>> I believe the overall goal is to have two part names for all modules:
>>
>> — cas-* for catalog/archive components
&
I believe the overall goal is to have two part names for all modules:
— cas-* for catalog/archive components
— grid-* for traditional oodt profile & product components
— oodt-* for common components
So the correct dependency is cas-filemgr and the correct version should be
${oodt.version}, aka 0
> Weird! Maybe I forgot to add the classifier to it? The artifact is present on
> Maven central:
>
> http://repo2.maven.org/maven2/org/safehaus/jug/jug/2.0.0/
Turns out the groupId was missing an extra .jug on it. Checked in r966866.
Recent commits to workflow's pom.xml seems to have broken the component:
% cd workflow
% mvn test
1) org.safehaus:jug:jar:asl:2.0.0
Path to dependency:
1) org.apache.oodt:workflow:jar:0.1-incubating
2) org.safehaus:jug:jar:asl:2.0.0
Maybe someone has a ~/.m2/settings.xm
It looks like OSI OSL to me; see http://www.opensource.org/licenses/osl-3.0.php
> Seems GNU GPL:
> * Copyright (C) 2005 Dell Inc.
> * by Michael Brown
> * Licensed under the Open Software License version 2.1
I vote to nuke all Oracle references.
> In the process of wrapping up OODT-3 (Apache license headers), I came across
> the following third-party script that it looks like we swept into the source:
>
> filemgr/src/main/resources/MysqlToOracleFilter.pl
>
> It's a filter to transform mysql ddl int
>> OK, will do.
>>
>> Our incubation sponsors don't read this, right?
>
> Of course not. -- justin
Whew, that was a close one—HEY, wait a minute! ^_^
To get to OODT-15 & OODT-16 up to snuff and publish the OODT website, I've been
preening the Java code and ensuring every component compiles, unit tests pass,
reports generate, and docs are clean.
With Chris's help I've got every component working out of the top-level pom and
things are looking
> Do you have more information on this "svn checksum" issue?
I believe it was caused by local corruption of a `.svn` directory or two after
some clumsy `sed` applications, and was limited to a few subdirectories.
To recover, I:
1. Saved changes to source files elsewhere in the filesystem
2. `rm
2. I need to remember to fix the "From:" header to read from my apache.org
account!
and:
3. No one expects the Spanish Inquisition
On 2010.Jul.17, at 9.52a, Sean Kelly wrote:
>> - OODT-15 WIP: fix problems with extractors in metadata; fix and enable all
>> unit tests that w
> - OODT-15 WIP: fix problems with extractors in metadata; fix and enable all
> unit tests that were disabled per kelly; cleanup license headers on conf
> files; deploy conf files using Maven testResource bootstrap. Clean up deps.
> metadata fully functioning
Those tests are still, sadly, brok
Nothing to see here! Just ...
Just uhm .. good, plain, old-fashioned software development. Yeah, that's it!
On 2010.Jul.16, at 4.17p, Mattmann, Chris A (388J) wrote:
> LOL...to late for that! ^_^
>
>
> On 7/16/10 2:08 PM, "Sean Kelly" wrote:
>
> OK, will
>
> On 7/16/10 1:52 PM, "Sean Kelly" wrote:
>
> OK, I svn rm'd it and then logged onto eos.apache.org and its mirrors and
> byte-edited the svn db and the filesystem journal to destroy all references
> to the query module just in case someone tries to revive it.
&g
88J) wrote:
> Super +1, let's drop it!
>
>
> On 7/16/10 12:54 PM, "Sean Kelly" wrote:
>
> Should we even bother with the "query" component?
Should we even bother with the "query" component?
It has two .java files, one is an exception, the other is a pointless little
multi-threaded profile & product client. It has some documentation for the
query servlet, but no one uses that anymore since web-grid provides profile &
product interfa
Should we even bother with the "query" component?
It has two .java files, one is an exception, the other is a pointless little
multi-threaded profile & product client. It has some documentation for the
query servlet, but no one uses that anymore since web-grid provides profile &
product interfa
In order to get OODT-16 (OODT website) done, I'm having to get all the code in
working order as well, since Maven generates the website and won't proceed if
it can't get past compilation or tests. That's taking quite a bit of time since
there are thousands of minuscule i's to dot and t's to cros
> Some projects have jpl.eda directories instead of gov.nasa.jpl. I still need
> a special pass to handle them (specifically: 'product', 'profile', 'query',
> 'xmlquery') but I have a question: Do we want to maintain the 'eda' legacy --
> i.e.: should we create o/a/eda as well as o/a/oodt, or do
> Hey Sean,
Which Seán did you mean? (Checking OODT-3 shows it unassigned.)
--Seán
PS: The Brotherhood (www.ibos.org) is pleased at that there are three Seáns on
this project already.
I see mention of the Python integration, so it looks fabulous to me! ^_^
Seriously: +1.
--k
On 2010.Apr.2, at 8.34p, Mattmann, Chris A (388J) wrote:
> OK, cleanified, and addified. Let me know what you guys think. I'm +1 for
> what's in there right now. Others, feel free to contribute and men
Oh greaat. ^_^
On 2010.Mar.22, at 8.30a, Mattmann, Chris A (388J) wrote:
> Thanks dude. When we nail down what we're releasing and how for
> 0.1-incubating I still nominate you to be RM! ;)
OK guys, thanks for the explanations.
I've removed the 1.0.0 release files and metadata from the Cheese Shop and
updated svn repository as well. It's as if this "release" never happened.
On 2010.Mar.21, at 10.19p, Justin Erenkrantz wrote:
> On Sun, Mar 21, 2010 at 5:3
Erenkrantz wrote:
> On Sun, Mar 21, 2010 at 3:19 PM, Sean Kelly (JIRA) wrote:
>> 1.0.0 release
>> http://pypi.python.org/packages/source/o/oodt/oodt-1.0.0.tar.gz
>
> What does "release" mean in this context? -- justin
Awesome. Thanks for the discussion and advice.
Take care,
Sean.
Hey guys:
Getting OODT out of the shackles of Caltech intellectual property and into open
source is undoubtedly one of the best things we could ever do for the software
package. And the fact that we've got such a clear-headed champion to herald it
into the Apache Incubator is a real honor.
How
42 matches
Mail list logo
