Adam R. B. Jack wrote:
1) Resource -> Artifact:
It will not be trivial, but we could rename Resource to be Artifact to ease
a merge with Avalon Repository (and since Artifact has started to become a
recognized term).
+1. Shouldn't be to difficult using IDEA. I'd be happy to do the work
if th
public/workspace/depot/update]
CLASSPATH :
/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/depot/update/build/depot-update/junit/classes:/usr/local/gump/public/workspace/depot/update/dist/depot-update-gump-20040622.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-styleb
etails are available at:
http://brutus.apache.org:8080/gump/depot/depot-update/index.html
That said, some snippets follow:
The following annotations were provided:
-DEBUG- Sole jar [depot-update-gump-20040622.jar] identifier set to project
name
-INFO- Dependency on ant exists, no need
Thanks, and no stress (I need to find some time for family/EMT
school/work/Gump, so I'll appreciate discussions not being too busy.)
Also, maybe I can find some time to put Depot's house in order prior to a
merge. Thanks for the impetus...
regards
Adam
- Original Message -
From: "Niclas
1) Resource -> Artifact:
It will not be trivial, but we could rename Resource to be Artifact to ease
a merge with Avalon Repository (and since Artifact has started to become a
recognized term).
BTW: I've started to create a page for terms (as Nick suggested):
http://wiki.apache.org/incubator/
On Tuesday 22 June 2004 23:14, Adam R. B. Jack wrote:
> I did a quick review (and I say quick, so please correct me where I am
> wrong). This is what I found:
Just want to give you the nod, that I am happy to see your effort, and at
large concur with your assessment.
I will comment more in detail
All,
I did a quick review (and I say quick, so please correct me where I am
wrong). This is what I found:
The Avalon codebase is simple -- and that is a major plus, no clutter, no
fuss. The approach is nicely broken into separate source directories (which
helps illustrate the separations) such as
Nicola Ken Barozzi wrote:
Niclas Hedhman wrote:
On Monday 21 June 2004 13:04, Nick Chalko wrote:
...
Classloading is a real problem in java, and an important one to tackle
but I prefer to keep the scope of Depot limited. Other project's like
Avalon can tackle the classloaders. Perhaps we can take
On Tuesday 22 June 2004 05:49, Nicola Ken Barozzi wrote:
> I get it.
>
> In essence, a single Avalon system needs to load different artifacts in
> separate classloaders during the same run.
Yes, it is not a Build time concern, but builds include the running of tests,
and some of these tests are f
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact folk at [EMAIL PROTECTED]
Project depot-update-test has an issue affecting its community integration.
Project State : '
10 matches
Mail list logo
