Re: Closing Incubator Depot Incubation
Nick Chalko wrote: Nicola Ken Barozzi wrote: How should I proceed from here? (no guidelines for this yet) Encourage Any courage anyone to copy the code and continue development somewhere else with any ASF compatible license. Don' ask just do it. Post a note on the general@incubator.apache.org list they want. On a personal note. I will move to Krysalis the minimum amount of code needed to support version stamp ant task. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: Closing Incubator Depot Incubation
Nicola Ken Barozzi wrote: How should I proceed from here? (no guidelines for this yet) Any courage anyone to copy the code and continue development somewhere else with any ASF compatible license. Don' ask just do it. Post a note on the general@incubator.apache.org list they want. On a personal note. I will move to Krysalis the minimum amount of code needed to support version stamp ant task. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Where should version go
Where shall we move version ? Krysalis ? Commons ? R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: Is it worth continuing?
Nicola Ken Barozzi wrote: It's some time that there is no active development on this project. I'm sad to write this, but I don't think that things will change soon enough. Apache wants communities, and I don't see one here (yet). I wanted to try and help but I have no time, and without proper documentation and energy to pursue this, we are not going anywhere. Therefore I propose to drop the incubation of Depot in the Apache Incubator and go back to Krysalis. As an alternative/addition we could donate the code that is here to Maven, where there is actually a repository system that is being actively managed. While I have a new job that is using some of this. I alos do not have much time to support it. I agree it should probably go back to Krysalis. Pain to move the code around. but oh well. smime.p7s Description: S/MIME Cryptographic Signature
Depot at work
I never seem to be able to sell depot at work. At work putting the jars into CVS always seems to when out. At work people don't like to trust the Internet to find jars. Perhaps I could put some effort into writting depot code to manage a CVS repository Think of the use case of What functions would we need to have for CVS backed repository. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: svn commit: rev 54910 - incubator/depot/trunk/version
[EMAIL PROTECTED] wrote: Author: mmay Date: Sat Oct 16 00:18:13 2004 New Revision: 54910 Modified: incubator/depot/trunk/version/build.xml Log: Using now the right repository for makeantlet, furthermore renamed makeantlet-0.3 through makeantlet-0.3-antlet, like it is named in the repository Ahh yes, I released that publishing antlets with just projectname-version.jar would conflict with the normal project jar. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: [GUMP@brutus]: Project depot-update (in module depot) failed
Markus M. May wrote: Hello, is this a problem of antlets or a problem of depot?? I am not sure about this. Probably we should remove the usage of this attribute, shouldn't we? Markus... version-stamp: BUILD FAILED /home/gump/.antworks/antlets/depot-version-0.1.1/xbuild.xml:46: version-stamp doesn't support the overWrite attribute Depot changed, so I need to update the antlet. I thought I did. This is a deopt thing.
resent Re: ant dependencies task
Looks great. Depot is an excellent place for this. We have a very similar task except it builds a fileset. Id looks like this. repository id=maven url=http://www.ibiblio.org/maven/; remote=true / repository id=nickchalko-sandbox url=http://cvs.apache.org/~nickchalko/SNAPSHOTS/; remote=true / cachedset id=depot-version.dependent.jars artifact name=servletapi ext=jar version=2.3 repository=maven / artifact name=junit ext=jar version=3.8 repository=maven / artifact name=ant ext=jar version=1.6 repository=maven / /cachedset Where can I see yor code, I am very interested in what you did. I had a lot of trouble using the ant FileSet the way I wanted to. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Compatibility thoughts
Giving my Compatibility question some thought I came to the realization. There are three kinds of changes that can be made wrt compatibility because there is two direction of compatibility. Backwards compatible and forwards compatible. In the common major.minor.point structure Increment the major number mean non compatible change. Incrementing the minor number means backwards compatible (old code will work with the new, but code using new features will not work with old) Incrementing the point number is forwards and backwards compatible. The public interface should not change at all on point changes. So to answer my question, No isCompatible is not symmetric. a.isCompatible(b) does not imply that b.isCompatible(a) R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: Distribution
Nick Chalko wrote: Here is a what the generated bash script looks like #! /bin/sh # Autogenerated script to execute the java class # org.apache.depot.update.tool.DownloaderTool NOTE: There is not a ASL 2 on the generated files, We will have to fix this. smime.p7s Description: S/MIME Cryptographic Signature
Re: Call generated classes VersionStamp
Adam R. B. Jack wrote: On Fri, 6 Aug 2004, Nick Chalko wrote: I think we should call generated version classes VersionStamp. This should reduce confusion with our Version interface. FWIIW: The naming of 'Version' was used because the discovery code was designed with the end-user (not us) in mind. Folks out there have classes they call Version thay we wanted to pick up. That said, we could teach it more aliases. BTW: What (really) is the difference between VersionMarker and VersionStamp? We need to get out terminology correct, I agree, I just don't have the answers... Here is what he ave now The Version interface is an abstraction of a version. Version's can be compared and tested for compatible. MersionMarker interface is composite of a Version along it a VersionIdentifier (package name) VersionStamp is neither. It does not implement either interface. It has a collection of use preformated strings for display. It also has enough information to dynamically generate a Version or VersionMarker. (btw we need to ensure VersionStamp.getLongVersion and VersionStamp.getAttributes is enough to generate a VersionMarker) VersionStamp is a standalone Class. R, Nick regards, Adam
Re: [GUMP@brutus]: depot/depot-version failed
Adam, Cleaning up my VersionData, mismatch ? Good to see movement in Depot. Adam Jack wrote: http://brutus.apache.org/gump/public/depot/depot-version/index.html [javac] /usr/local/gump/public/workspace/depot/version/src/java/org/apache/depot/version/util/jar/JarManifestHelper.java [javac] /usr/local/gump/public/workspace/depot/version/src/java/org/apache/depot/version/version/Version.java [javac] /usr/local/gump/public/workspace/depot/version/src/java/org/apache/depot/version/VersionManager.java:44: incompatible types [javac] found : org.apache.depot.version.impl.data.VersionData [javac] required: org.apache.depot.version.Version [javac] return VersionFormatFactory.createDefaultVersionFormat().parseVersion(versionString); [javac] ^ [javac] 1 error BUILD FAILED /home/gump/.antworks/antlets/java-0.1/xbuild.xml:81: Compile failed; see the compiler error output for details. at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938) at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:95) at org.apache.tools.ant.Task.perform(Task.java:366) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1221) at org.apache.tools.ant.Project.executeTarget(Project.java:1191) at org.apache.tools.ant.Project.executeTargets(Project.java:1060) at org.apache.tools.ant.Main.runBuild(Main.java:673) at org.apache.tools.ant.Main.startAnt(Main.java:188) at org.apache.tools.ant.Main.start(Main.java:151) at org.apache.tools.ant.Main.main(Main.java:241) Total time: 9 seconds - To subscribe to this information via syndicated feeds: RSS: http://brutus.apache.org/gump/public/depot/depot-version/rss.xml Atom: http://brutus.apache.org/gump/public/depot/depot-version/atom.xml -- Gump E-mail Identifier (within run) #17. Produced by Gump 2.1.0-alpha-0002. [Run (20040721 08:09:12, brutus:brutus-public:20040721 08:09:12)] http://brutus.apache.org/gump/public/index.html http://brutus.apache.org/gump/public/options.html -- Apache Gump http://gump.apache.org/ [Instance: brutus] smime.p7s Description: S/MIME Cryptographic Signature
Status Report
Is a my first take on a status report for the board in (cwiki format)
!!2004-07-18
{{{
1). Is the STATUS file up to date?
No
2). Any legal, cross-project or personal issues that still need to be
addressed?
No, all files licensed, all commiters have singed CLA
3). What has been done for incubation since the last report?
* Site update.
* PAckages renamed to depot
4). Plans and expectations for the next period?
* Delete unused under developed code.
* Complete Download manger for use by gump and others.
* Support directory artifacts for use by antworks and others.
5). Any recommendations for how incubation could run more smoothly for you?
n/a
}}}
Re: Status Report
Adam R. B. Jack wrote:
Thanks for doing this Nick, I appreciate you taking it on, 'cos it needs to
be done. I'm not sure what good cwiki format does me, ought it just be on a
wiki (so we can help by adding to it?)
It is an excerpt from the source to
http://incubator.apache.org/projects/depot.html
but yes a wiki page would be good also.
What am I missing? What do you want
from us?
Any thing else I should mention otherwise I will send to to
general@incubator.apache.org
regards
Adam
- Original Message -
From: Nick Chalko [EMAIL PROTECTED]
To: Depot Development [EMAIL PROTECTED]
Sent: Sunday, July 18, 2004 5:27 PM
Subject: Status Report
Is a my first take on a status report for the board in (cwiki format)
!!2004-07-18
{{{
1). Is the STATUS file up to date?
No
2). Any legal, cross-project or personal issues that still need to be
addressed?
No, all files licensed, all commiters have singed CLA
3). What has been done for incubation since the last report?
* Site update.
* PAckages renamed to depot
4). Plans and expectations for the next period?
* Delete unused under developed code.
* Complete Download manger for use by gump and others.
* Support directory artifacts for use by antworks and others.
5). Any recommendations for how incubation could run more smoothly for
you?
n/a
}}}
Re: UpdaterConfig
Adam R. B. Jack wrote: like I said already, I am browsing through the API and adding JavaDoc to some classes. Right now I have a problem concerning the UpdaterConfig. This class is called all over the API and should provide basic configuration for the application. But right now, I am pretty unsure, how this configuration is provided to the calling classes. That was (is?) a nice experiment by Anou. Basically we wanted some form of 'ant types' (configuration in XML) but outside of Ant. The configuration file is read, and named configured objects are stored in a registry (by namespaced name). I think it works, but has some usage issues, so right now I'm kinda hoping to leave it on the side, until we find time to work on it. I do like the idea. My preference is to CUT what is not being used. If there is not a test case that exercise this, ask about it on the list and then we can kill it. R, Nick
Re: Download Manager
Markus M. May wrote:
Hello, here are some ideas for the Download-Manager. What do you think?
- how to unit test this, without a download? - not possible, so the
internet connection should be up and running for the testcase
For test check the files into cvs and use a repo url of
file:///${basedir}/src/test-repo
R,
Nick
Re: Refactoring (for merge) and APIs
Nicola Ken Barozzi wrote: Adam R. B. Jack wrote: It will not be trivial, +1. Shouldn't be to difficult using IDEA. Eclipse can do the work also. It isn't so much the mechanics, more the mental shift (since they aren't quite the same things today). It'll mean a few other class name changes is my guess. Anyways, anybody else pro this change? +1 +1
Re: classloader was: Moving forward or letting go
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 over the version/download/security stuff. I don't agree here, Nick, classloading is part of artifact handling, albeit in the JVM. It can and IMHO should live as a Depot subproject. I withdraw my -1, Classloading as a separate project does make sense for Depot. I should have used a -0 at worst. R, Nick
Re: classloader was: Moving forward or letting go
Niclas Hedhman wrote: am -1 for directly handling classloading. Then please provide an answer to the question; How do you intend to provide generic meta information to the Depot client, and how is that meta information generated and handed to Depot prior to publishing the artifacts? And secondly; Who should be responsible to define the classloader concern, expressed in generic meta information? Since I suspect the answers to the above is Not Depot's concern and Not Depot, then I am sorry to say that Depot future is very bleak, and I doubt it will receive any support from Avalon. I hope the not Depot's concern stems from the lack of understanding the problem at hand, and that you will gain that insight sooner or later. For me the target use case for depot has always been managing artifacts needed to build. So class loaders beyond setting a path resource in ant has never been a needed task. Handling a chain of dependencies is something that we would like to do but it has never been a pressing concern. For the most part I scratch what itches, and jars for an ant build itches me all the time, so that is where I scratch. I understand some of what avalon is doing with downloading needed jars for an application server. Here is the pieces of code I think can be useful to avalon. * Version, o Marking o Comparing o Computability, * Downloading. o Maintaining a local cache of jars o Updating a local cache of jars o getting the best jar available. o mirrors * Security o verify md5 signatures o verify other signatures. Having outside user of our API would be great. Our API has gotten really FAT and needs cleaning. If you are interested in investigating using our API I will be happy to help. For the future of Depot, I think it is important to try to produce the smallest useful set of tools possible, not the biggest. 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 over the version/download/security stuff. In a perfect world would would the depot API as used in your class loader look like ? File theJar = depot.getResource(log4j,1.2, booleanGetDepenetedProjects); ? The issue chained dependencies is important, and I think gump can be of assistance. However gump only reflects the current state and we need access to the dependencies for other versions as well. So work on the Meta info is a place we can share efforts. But it is a goal for Depot to work, at least in a basic/default way WITHOUT any separate meta info. What do you see as the common ground for us to participate on ? R, Nick
Re: svn commit: rev 21562 - incubator/depot/trunk/version
[EMAIL PROTECTED] wrote: Author: nicolaken Date: Mon Jun 21 14:37:08 2004 New Revision: 21562 Modified: incubator/depot/trunk/version/build.xml Log: Get version to build using Ant. Modified: incubator/depot/trunk/version/build.xml == --- incubator/depot/trunk/version/build.xml (original) +++ incubator/depot/trunk/version/build.xml Mon Jun 21 14:37:08 2004 @@ -68,6 +68,7 @@ fileset dir=. include name=lib/*.jar / /fileset + pathelement path=../common/build/depot-common/classes/ /path !-- note this must be after the java antlet-- The other choice is to copy the common.jar in the the lib dir.
Re: [GUMP@lsd]: depot/depot-update failed
Gump caught me in the middle of a a fix. It will be cleaned up before I
go to bed.
Adam Jack wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project depot-update has an issue affecting its community integration.
This issue affects 4 projects.
The following are affected:
- depot-update-ant-sample-httpclient : Depot -- repository tools and more...
- depot-update-ant-sample-jdk : Depot -- repository tools and more...
- depot-update-ant-sample-vfs : Depot -- repository tools and more...
- depot-update-test : Depot -- repository tools and more...
The current state is 'Failed', for reason 'Build Failed'
Full details are available at:
http://lsd.student.utwente.nl/gump/depot/depot-update/index.html
That said, some snippets follow:
Gump provided these annotations:
- Info - Sole jar [depot-update-gump-20040521.jar] identifier set to project
name
- Info - Dependency on ant exists, no need to add for property ant.home.
- Info - Enable verbose output, due to 3 previous error(s).
- Info - Failed with reason build failed
- Info - Enable debug output, due to build failure.
Gump performed this work:
http://lsd.student.utwente.nl/gump/depot/depot-update/gump_work/build_depot_depot-update.html
Work Name: build_depot_depot-update (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 13 seconds
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -verbose -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -DDATE_STAMP=20040521 -f build.xml gump
[Working Directory: /data3/gump/depot/update]
CLASSPATH : /usr/java/j2sdk1.4.2_04/lib/tools.jar:/data3/gump/depot/update/build/depot-home/classes:/data3/gump/ant/dist/lib/ant-stylebook.jar:/data3/gump/ant/dist/lib/ant-jmf.jar:/data3/gump/ant/dist/lib/ant-swing.jar:/data3/gump/ant/dist/lib/ant-junit.jar:/data3/gump/ant/dist/lib/ant-launcher.jar:/data3/gump/ant/dist/lib/ant-xalan2.jar:/data3/gump/ant/dist/lib/ant-trax.jar:/data3/gump/ant/dist/lib/ant.jar:/data3/gump/ant/dist/lib/ant-nodeps.jar:/data3/gump/depot/version/dist/depot-version-gump-20040521.jar:/data3/gump/depot/common/dist/depot-common-gump-20040521.jar:/data3/gump/antworks-importer/dist/antworks-importer-0.1-gump-20040521.jar:/data3/gump/jakarta-servletapi/dist/lib/servlet.jar:/data3/gump/jakarta-regexp/build/jakarta-regexp-20040521.jar:/data3/gump/ant/bootstrap/lib/ant-launcher.jar:/data3/gump/ant/bootstrap/lib/ant.jar:/data3/gump/jakarta-commons/httpclient/dist/commons-httpclient.jar:/data3/gump/jakarta-commons/codec/dist/commons-codec-20040521.jar:/data3/gump/jakarta-commons/logging/dist/commons-logging.jar:/data3/gump/jakarta-commons/logging/dist/commons-logging-api.jar:/data3/gump/commons-vfs/target/commons-vfs-20040521.jar-
[javac] CachedResourceFileSet(CachedResourceSet updateSet) {
[javac] ^
[javac] /data3/gump/depot/update/src/java/org/apache/depot/update/ant/CachedResourceSetExportTask.java:83: cannot resolve symbol
[javac] symbol : class CachedResourceSet
[javac] location: class org.apache.depot.update.ant.CachedResourceSetExportTask
[javac] CachedResourceSet cachedResourceSet = (CachedResourceSet) getProject()
[javac] ^
[javac] /data3/gump/depot/update/src/java/org/apache/depot/update/ant/CachedResourceSetExportTask.java:83: cannot resolve symbol
[javac] symbol : class CachedResourceSet
[javac] location: class org.apache.depot.update.ant.CachedResourceSetExportTask
[javac] CachedResourceSet cachedResourceSet = (CachedResourceSet) getProject()
[javac]^
[javac] /data3/gump/depot/update/src/java/org/apache/depot/update/ant/ResourceElement.java:181: cannot resolve symbol
[javac] symbol : class RepositoryElement
[javac] location: class org.apache.depot.update.ant.ResourceElement
[javac] RepositoryElement repositoryElement = (RepositoryElement) project
[javac] ^
[javac] /data3/gump/depot/update/src/java/org/apache/depot/update/ant/ResourceElement.java:181: cannot resolve symbol
[javac] symbol : class RepositoryElement
[javac] location: class org.apache.depot.update.ant.ResourceElement
[javac] RepositoryElement repositoryElement = (RepositoryElement) project
[javac]^
[javac] /data3/gump/depot/update/src/java/org/apache/depot/update/ant/ResourceElement.java:232: cannot resolve symbol
[javac] symbol : method getFirstResource (org.apache.depot.update.query.ResourceResult)
[javac] location: class org.apache.depot.update.ant.AntUtils
[javac] resource = AntUtils.getFirstResource(res);
[javac]
Re: [Fwd: Re: subscribe depot-dev@incubator.apache.org]
Thank you Adam and I have started working on the other errors you listed Thank you for pointing them out. A fresh set of eyes does wonders. R, Nick Neeme Praks wrote: As a first thing on my quest to get more publicity for Depot, I added it to Gmane! ;-) Original Message Subject: Re: subscribe [EMAIL PROTECTED] Date: Thu, 13 May 2004 18:59:38 +0200 From: [EMAIL PROTECTED] (Nicolas Bareil) To: [EMAIL PROTECTED] Newsgroups: gmane.discuss.subscribe References: [EMAIL PROTECTED] On Thu, 13 May 2004, [EMAIL PROTECTED] wrote: #gmane.comp.apache.incubator.depot-dev [EMAIL PROTECTED] developers list of Apache Depot - integrated tools for automating downloading, publishing and managing the contents of different repository implementations ezmlm dummy url=http://incubator.apache.org/depot/ Request from 194.204.29.178 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8). Subscription messages for the requested mailing lists have been sent. The resulting groups will be created when the first message arrives from the mailing lists.
Wow Only Tests failed
Good progress, only the test are failing. and that is what tests are for R, Nick
Re: http://incubator.apache.org/depot/index.html
Working on it now. Adam R. B. Jack wrote: Would somebody mind updating this? [My version of forrest isn't new enough, and to get a new one I'll need to download forrest from SVN over modem, which I don't have time for this morning. The main reason I want it is because the closed left menu (projects) looks empty, and we look like we have an empty project. http://incubator.apache.org/depot/index.html I've added a table of our three sub-projects so folks can get some insights, and perhaps get interested. regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Re: http://incubator.apache.org/depot/index.html
Done. Nick Chalko wrote: Working on it now. Adam R. B. Jack wrote: Would somebody mind updating this? [My version of forrest isn't new enough, and to get a new one I'll need to download forrest from SVN over modem, which I don't have time for this morning. The main reason I want it is because the closed left menu (projects) looks empty, and we look like we have an empty project. http://incubator.apache.org/depot/index.html I've added a table of our three sub-projects so folks can get some insights, and perhaps get interested. regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Cached set export
The cached set export task is now working The junit build.xml test called testExport1 exports this xml. chachedresourceset id=test1 resource name=helloworld version=1.1 href=file://C:/workspace/depot-update/src/resources/test/repo/helloworld/jars/helloworld-1.1.jar/ /chachedresourceset Tomorrow I will work on the xslt that generates a use-cached-resources-build.xml. As always improvements are always welcome. Especially for task/type names. R, Nick
Re: Fw: cvs commit: gump/project depot.xml
Adam R. B. Jack wrote:
+depend project=xmlunit/
Cool, but what does it do what do we use it for? Just curious.
JUnit asserts for XML
I use it to assert that the XML content of two files are equal.
Like this.
/**
* Test the exporting of cached set test1.
*
*/
public void testExport1() throws FileNotFoundException, SAXException,
IOException, ParserConfigurationException {
try {
executeTarget(testExport1);
File generatedFile = new File(build/test1-export.build.xml);
File expectedFile = new File(
src/test/org/apache/depot/update/ant/test1-export.build.xml);
assertTrue(Expected + generatedFile + to exists,
generatedFile.exists());
XMLAssert
.assertXMLEqual(Exported cached set test1,
new FileReader(expectedFile), new FileReader(
generatedFile));
} finally {
System.out.println(getOutput());
}
}
Re: URI Syntax
Discuss on [EMAIL PROTECTED] first. Michael Davey wrote: Hello, I'd like to suggest a change to the Product specifier section of the URI Syntax document: http://nagoya.apache.org/wiki/apachewiki.cgi?ASFRepository/URISyntax From: project is the project name. It is unique within an organisation. E.g: ldap, jndi, maven, commons-logging. To: project is the project name. It is unique within an organisation. If your artifact is a sub-project of a larger project, or is unique in some way, include that information in the name. For example, if your artifact is part of the bar project, which is a sub-project of foo, then your project would be named foo-bar. E.g: ldap, jndi, maven, commons-logging. Shall I update the wiki page?
Re: depot-version-antlib.xml
Perhaps we should make both available. a depot-version-antlib.xml and a depot-version-antlib-terse.xml Where the first has version-name and the other has just name with the intention of the terse being used with namespaces. I would recommend checking in the terse and using XSLT to generate the verbose. R, Nick Adam R. B. Jack wrote: Since Ant backed off namespaces (for a while) the version tasks loose the 'version:' version:stamp version:environment version:environment-check version:available version:constraint version:constraint-check I think we need to add version- to the front of them, or they clash (available) or could clash (stamp/env). Ant better ideas? regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com
Re: depot-version-antlib.xml
Adam R. B. Jack wrote: Perhaps we should make both available. Hmm, what if we have both in one file? antlib taskdef name=stamp classname=org.apache.depot.version.ant.stamp.VersionMarkerGeneratorTask/ taskdef name=version-stamp classname=org.apache.depot.version.ant.stamp.VersionMarkerGeneratorTask/ I don't know what happen in the case of a clash (I see version-available already exists this way, not as available) but I assume the first takes over. I changed that because it was overriding the standard available type. So having both does not solve the problem of conflicts. If/when namespaces get restored we'll need uses to change to version: so having version- isn't so bad, is it? Having users change their resource file seems intrusive. Lest use version-for now. When names spaces are available we can create in the terse version. The point is when used with name spaces use wont want to write version:version-stamp. and since they will be adding the name space declaration they can add the -terse suffix to the file name if they want to use the shorter task names. Thoughts? regards
Re: [GUMP@lsd]: depot/depot-update failed
Ok I fixed the jar name here and at gump.
Adam Jack wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project depot-update has an issue affecting its community integration.
This issue affects 1 projects, and has been outstanding for 2 runs.
The following are affected:
- depot-update-test : Depot -- repository tools and more...
The current state is 'Failed', for reason 'Missing Build Outputs'
Full details are available at:
http://lsd.student.utwente.nl/gump/depot/depot-update/index.html
That said, some snippets follow:
Gump provided these annotations:
- Info - Sole jar [depot-update-gump-20040429.jar] identifier set to project
name
- Info - Dependency on ant exists, no need to add for property ant.home.
- Info - Enable verbose output, due to 1 previous error(s).
- Info - Failed with reason missing build outputs
- Error - Missing Output:
/data3/gump/depot/update/target/dist/jars/depot-update-gump-20040429.jar
- Error - No such directory (where output is expected) :
/data3/gump/depot/update/target/dist/jars
Gump performed this work:
http://lsd.student.utwente.nl/gump/depot/depot-update/gump_work/build_depot_depot-update.html
Work Name: build_depot_depot-update (Type: Build)
State: Success
Elapsed: 0 hours, 0 minutes, 11 seconds
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -verbose -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -DDATE_STAMP=20040429 -f build.xml gump
[Working Directory: /data3/gump/depot/update]
-
[jar] adding entry org/apache/depot/update/util/net/select/AbstractVrlSelector.class
[jar] adding entry org/apache/depot/update/util/net/select/ChildVrlSelector.class
[jar] adding entry org/apache/depot/update/util/net/select/MatchingVrlSelector.class
[jar] adding entry org/apache/depot/update/util/net/select/ProtocolVrlSelector.class
[jar] adding entry org/apache/depot/update/util/reference/IReferenceable.class
[jar] adding entry org/apache/depot/update/util/reference/NoSuchReferenceException.class
[jar] adding entry org/apache/depot/update/util/reference/ReferenceProxy.class
[jar] adding entry org/apache/depot/update/util/reference/ReferenceTable.class
[jar] adding entry org/apache/depot/update/util/regexp/RegularExpression.class
[jar] adding entry org/apache/depot/update/util/regexp/RegularExpressionHelper.class
[jar] adding entry org/apache/depot/update/util/regexp/RegularExpressionSelector.class
[jar] adding entry org/apache/depot/update/util/security/ChkSum.class
[jar] adding entry org/apache/depot/update/util/security/HashCodeManager.class
[jar] adding entry org/apache/depot/update/util/select/AllSelector.class
[jar] adding entry org/apache/depot/update/util/select/CompositeSelector.class
[jar] adding entry org/apache/depot/update/util/select/ISelectable.class
[jar] adding entry org/apache/depot/update/util/select/ISelector.class
[jar] adding entry org/apache/depot/update/util/select/SelectionHelper.class
[jar] adding entry org/apache/depot/update/util/select/SelectorHandlerChain.class
[jar] adding entry org/apache/depot/update/util/select/logic/AndSelector.class
[jar] adding entry org/apache/depot/update/util/select/logic/BooleanSelector.class
[jar] adding entry org/apache/depot/update/util/select/logic/NotSelector.class
[jar] adding entry org/apache/depot/update/util/select/logic/OrSelector.class
[jar] adding entry org/apache/depot/update/util/text/MessageConstants.class
[jar] adding entry org/apache/depot/update/util/text/Messages.class
[jar] adding entry org/apache/depot/update/util/xml/IXMLAttribute.class
[jar] adding entry org/apache/depot/update/util/xml/XMLContext.class
[jar] adding entry org/apache/depot/update/util/xml/XMLEntryTable.class
[jar] adding entry org/apache/depot/update/util/xml/XMLException.class
[jar] adding entry org/apache/depot/update/util/xml/XMLGrouperElement.class
[jar] adding entry org/apache/depot/update/util/xml/XMLHandler.class
[jar] adding entry org/apache/depot/update/util/xml/XMLParser.class
[jar] adding entry org/apache/depot/update/util/xml/XMLTagConstants.class
[jar] adding entry org/apache/depot/update/version/Version.class
[jar] adding entry org/apache/depot/update/version/VersionHelper.class
package:
dist-jar:
[copy] depot-update-0.1-dev-20040429.jar added as
depot-update-0.1-dev-20040429.jar doesn't exist.
[copy] Copying 1 file to /data3/gump/depot/update/dist
[copy] Copying
/data3/gump/depot/update/build/depot-update/depot-update-0.1-dev-20040429.jar
to /data3/gump/depot/update/dist/depot-update-0.1-dev-20040429.jar
gump:
Property ${gump} has not been set
Re: [GUMP@lsd]: depot/depot-common-test failed
Classpath issue This should be fixed now I updated the home/work dir in gump. Adam Jack wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project depot-common-test has an issue affecting its community integration, and has been outstanding for 3 runs. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/depot/depot-common-test/index.html That said, some snippets follow: Gump provided these annotations: - Info - Enable verbose output, due to 2 previous error(s). - Info - Failed with reason build failed - Info - Enable debug output, due to build failure. - Info - Project Reports in: /data3/gump/depot/common/target/tests - Warning - No directory [/data3/gump/depot/common/target/tests] Gump performed this work: http://lsd.student.utwente.nl/gump/depot/depot-common-test/gump_work/build_depot_depot-common-test.html Work Name: build_depot_depot-common-test (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 8 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar org.apache.tools.ant.Main -verbose -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -f build.xml test [Working Directory: /data3/gump/depot/common] - /home/ajack/.antworks/antlets/junit-0.1/xbuild.xml:120: The following error occurred while executing this line: /data3/gump/depot/common/build/work/junit/test.xml:7: Test org.apache.depot.common.util.RegistryTests failed at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:536) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:385) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321) at org.apache.tools.ant.Target.performTasks(Target.java:348) at org.apache.tools.ant.Project.executeTarget(Project.java:1212) at org.apache.tools.ant.Project.executeTargets(Project.java:1060) at org.apache.tools.ant.Main.runBuild(Main.java:666) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:151) at org.apache.tools.ant.Main.main(Main.java:234) Caused by: /data3/gump/depot/common/build/work/junit/test.xml:7: Test org.apache.depot.common.util.RegistryTests failed at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.actOnTestResult(JUnitTask.java:1460) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:698) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1426) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:646) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321) at org.apache.tools.ant.Target.performTasks(Target.java:348) at org.apache.tools.ant.Project.executeTarget(Project.java:1212) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:383) ... 10 more --- Nested Exception --- /data3/gump/depot/common/build/work/junit/test.xml:7: Test org.apache.depot.common.util.RegistryTests failed at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.actOnTestResult(JUnitTask.java:1460) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:698) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1426) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:646) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321) at org.apache.tools.ant.Target.performTasks(Target.java:348) at org.apache.tools.ant.Project.executeTarget(Project.java:1212) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:383) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:321) at org.apache.tools.ant.Target.performTasks(Target.java:348) at org.apache.tools.ant.Project.executeTarget(Project.java:1212) at org.apache.tools.ant.Project.executeTargets(Project.java:1060) at org.apache.tools.ant.Main.runBuild(Main.java:666) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:151) at org.apache.tools.ant.Main.main(Main.java:234) Total time: 6 seconds - To subscribe to this information via syndicated feeds:
ASF Sytle Repostirywas: svn commit: rev 10424 - incubator/depot/trunk/update/src/java/org/apache/depot/update/repository
Lets flush out this class and have the local repository be a ASF style
on so we can start giving it some use.
As a reminder the specification is at
http://nagoya.apache.org/wiki/apachewiki.cgi?ASFRepository
[EMAIL PROTECTED] wrote:
Author: nickchalko
Date: Thu Apr 29 00:21:26 2004
New Revision: 10424
Added:
incubator/depot/trunk/update/src/java/org/apache/depot/update/repository/ApacheRepository.java
Log:
Stub of an Apache style repository.
Added: incubator/depot/trunk/update/src/java/org/apache/depot/update/repository/ApacheRepository.java
==
--- (empty file)
+++ incubator/depot/trunk/update/src/java/org/apache/depot/update/repository/ApacheRepository.java Thu Apr 29 00:21:26 2004
@@ -0,0 +1,87 @@
+/*
+ * Copyright 2004 The Apache Software Foundation
+ *
+ * Licensed under the Apache License, Version 2.0 (the License); you may not
+ * use this file except in compliance with the License. You may obtain a copy of
+ * the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS, WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations under
+ * the License.
+ */
+package org.apache.depot.update.repository;
+import java.util.List;
+import org.apache.depot.update.impl.ResourceUpdaterContext;
+import org.apache.depot.update.resource.ResourceGroup;
+import org.apache.depot.update.util.net.VirtualResourceLocator;
+import org.apache.depot.update.util.select.ISelector;
+/**
+ * An apache style repository as decribed in a
+ * href=http://nagoya.apache.org/wiki/apachewiki.cgi?ASFRepository;ASF
+ * Repository Wiki /a
+ */
+public final class ApacheRepository extends AbstractRepository {
+ /**
+ * @param id
+ */
+ public ApacheRepository(String id) {
+ super(id);
+ // TODO Auto-generated constructor stub
+ }
+ /**
+ * @param id
+ * @param root
+ */
+ public ApacheRepository(String id, VirtualResourceLocator root) {
+ super(id, root);
+ // TODO Auto-generated constructor stub
+ }
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.apache.depot.update.repository.AbstractRepository#folderForGroup(org.apache.depot.update.resource.ResourceGroup)
+ */
+ public VirtualResourceLocator folderForGroup(ResourceGroup group) {
+ // TODO Auto-generated method stub
+ return null;
+ }
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.apache.depot.update.repository.IRepository#listGroups(org.apache.depot.update.impl.ResourceUpdaterContext,
+ * org.apache.depot.update.util.select.ISelector)
+ */
+ public List listGroups(ResourceUpdaterContext context, ISelector selector)
+ throws Exception {
+ // TODO Auto-generated method stub
+ return null;
+ }
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.apache.depot.update.repository.IRepository#getManifest(org.apache.depot.update.impl.ResourceUpdaterContext,
+ * org.apache.depot.update.resource.ResourceGroup,
+ * org.apache.depot.update.util.select.ISelector)
+ */
+ public RepositoryManifest getManifest(ResourceUpdaterContext context,
+ ResourceGroup group, ISelector selector) throws Exception {
+ // TODO Auto-generated method stub
+ return null;
+ }
+ /*
+ * (non-Javadoc)
+ *
+ * @see org.apache.depot.update.repository.IRepository#listResources(org.apache.depot.update.impl.ResourceUpdaterContext,
+ * org.apache.depot.update.resource.ResourceGroup,
+ * org.apache.depot.update.util.select.ISelector)
+ */
+ public List listResources(ResourceUpdaterContext context,
+ ResourceGroup group, ISelector selector) throws Exception {
+ // TODO Auto-generated method stub
+ return null;
+ }
+}
\ No newline at end of file
Re: Loading test resources
Adam R. B. Jack wrote: Why are we using a class loader here. MD5 don't usually ship inside a jar. This is part of a unit test. Are you saying we ought just use relative path? regards, Adam Well resource usually means add to the classpath, but I see no reasons for these files to be on the classpath so I would rename the dir and use relative path or move these somewhere else.
Re: svn commit: rev 10313 - incubator/depot/trunk/common
Antlets are availavle at
http://antworks.sourceforge.net/library/antlets/
Markus M. May wrote:
Ah, what I meant was more for the Depot stuff itself. Right now, we
have in every project a lib-directory. we should at least make one for
all sub-projects.
So lets make the lib-dir another directory (${repository.dir}???) and
put our own stuff in there as well. You already introduced
depot.update.dir or something, this directory can be used, at least
when it exists.
what do you think?
BTW, not all antlets are published (especially the apache one). Can
you please publish them, so that the build is working? Right now, I
have to build all antlets myself and then I have to publish them on my
local machine, etc. Very annoying :-(
Markus
Nick Chalko wrote:
I have a sample of using Update for builds
http://svn.apache.org/repos/asf/incubator/depot/trunk/update/src/sample/build.xml
Markus M. May wrote:
Hello,
since Depot is a repository Updater we should try to introduce the
repository already in the build-files of update? What do you think?
How can we do this?
Markus
[EMAIL PROTECTED] wrote:
Author: nickchalko
Date: Tue Apr 27 09:22:34 2004
New Revision: 10313
Modified:
incubator/depot/trunk/common/build.xml
Log:
Lib dir is optional
Modified: incubator/depot/trunk/common/build.xml
==
--- incubator/depot/trunk/common/build.xml(original)
+++ incubator/depot/trunk/common/build.xmlTue Apr 27 09:22:34 2004
@@ -40,8 +40,8 @@
path id=depot-common.classpath
-fileset dir=lib
-include name=*.jar /
+fileset dir=.
+include name=lib/*.jar /
/fileset
/path
Re: svn commit: rev 10313 - incubator/depot/trunk/common
Work laptop is being funny
I will do it when I get home.
Nick Chalko wrote:
Yes scp fails on multiple attempts so I have to do them one at a time
I will publish apache now.
R,
Nick
Markus M. May wrote:
Ah, what I meant was more for the Depot stuff itself. Right now, we
have in every project a lib-directory. we should at least make one
for all sub-projects.
So lets make the lib-dir another directory (${repository.dir}???) and
put our own stuff in there as well. You already introduced
depot.update.dir or something, this directory can be used, at least
when it exists.
what do you think?
BTW, not all antlets are published (especially the apache one). Can
you please publish them, so that the build is working? Right now, I
have to build all antlets myself and then I have to publish them on
my local machine, etc. Very annoying :-(
Markus
Nick Chalko wrote:
I have a sample of using Update for builds
http://svn.apache.org/repos/asf/incubator/depot/trunk/update/src/sample/build.xml
Markus M. May wrote:
Hello,
since Depot is a repository Updater we should try to introduce the
repository already in the build-files of update? What do you think?
How can we do this?
Markus
[EMAIL PROTECTED] wrote:
Author: nickchalko
Date: Tue Apr 27 09:22:34 2004
New Revision: 10313
Modified:
incubator/depot/trunk/common/build.xml
Log:
Lib dir is optional
Modified: incubator/depot/trunk/common/build.xml
==
--- incubator/depot/trunk/common/build.xml(original)
+++ incubator/depot/trunk/common/build.xmlTue Apr 27 09:22:34
2004
@@ -40,8 +40,8 @@
path id=depot-common.classpath
-fileset dir=lib
-include name=*.jar /
+fileset dir=.
+include name=lib/*.jar /
/fileset
/path
Re: [GUMP@lsd]: depot/depot-version-test failed
I fixed this for the antlet version. Shall we move to that so we only have to keep one build.xml up to date. Adam Jack wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project depot-version-test has an issue affecting its community integration, and has been outstanding for 4 runs. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/depot/depot-version-test/index.html, however some snippets follow: - - - - - -- -- G U M P Gump provided these annotations: - Info - Enable verbose output, due to 3 previous error(s). - Info - Failed with reason build failed - Info - Enable debug output, due to build failure. - - - - - -- -- G U M P Gump performed this work: http://lsd.student.utwente.nl/gump/depot/depot-version-test/gump_work/build_depot_depot-version-test.html Work Name: build_depot_depot-version-test (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 9 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/data3/gump/xml-xerces2/java/build/xercesImpl.jar:/data3/gump/xml-xerces2/java/build/xml-apis.jar:/data3/gump/xml-commons/java/external/build/xml-apis.jar:/data3/gump/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -verbose -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -f build.xml test [Working Directory: /data3/gump/depot/version] - [copy] java/org/apache/depot/version/constraint added as java/org/apache/depot/version/constraint doesn't exist. [copy] java/org/apache/depot/version/constraint/discovery added as java/org/apache/depot/version/constraint/discovery doesn't exist. [copy] java/org/apache/depot/version/constraint/discovery/text added as java/org/apache/depot/version/constraint/discovery/text doesn't exist. [copy] java/org/apache/depot/version/context added as java/org/apache/depot/version/context doesn't exist. [copy] java/org/apache/depot/version/discovery added as java/org/apache/depot/version/discovery doesn't exist. [copy] java/org/apache/depot/version/discovery/loading added as java/org/apache/depot/version/discovery/loading doesn't exist. [copy] java/org/apache/depot/version/extension added as java/org/apache/depot/version/extension doesn't exist. [copy] java/org/apache/depot/version/formatting added as java/org/apache/depot/version/formatting doesn't exist. [copy] java/org/apache/depot/version/impl added as java/org/apache/depot/version/impl doesn't exist. [copy] java/org/apache/depot/version/impl/data added as java/org/apache/depot/version/impl/data doesn't exist. [copy] java/org/apache/depot/version/impl/sample added as java/org/apache/depot/version/impl/sample doesn't exist. [copy] java/org/apache/depot/version/interfacing added as java/org/apache/depot/version/interfacing doesn't exist. [copy] java/org/apache/depot/version/interfacing/api added as java/org/apache/depot/version/interfacing/api doesn't exist. [copy] java/org/apache/depot/version/interfacing/complex added as java/org/apache/depot/version/interfacing/complex doesn't exist. [copy] java/org/apache/depot/version/interfacing/field added as java/org/apache/depot/version/interfacing/field doesn't exist. [copy] java/org/apache/depot/version/util added as java/org/apache/depot/version/util doesn't exist. [copy] java/org/apache/depot/version/util/dom added as java/org/apache/depot/version/util/dom doesn't exist. [copy] Copying 7 files to /data3/gump/depot/version/target/tests [copy] Copying /data3/gump/depot/version/src/test/java/org/apache/depot/version/ant/constraint/constraint.xml to /data3/gump/depot/version/target/tests/java/org/apache/depot/version/ant/constraint/constraint.xml [copy] Copying /data3/gump/depot/version/src/test/antlet/build.xml to /data3/gump/depot/version/target/tests/antlet/build.xml [copy] Copying /data3/gump/depot/version/src/test/java/org/apache/depot/version/ant/constraint/constraint-check.xml to /data3/gump/depot/version/target/tests/java/org/apache/depot/version/ant/constraint/constraint-check.xml [copy] Copying /data3/gump/depot/version/src/test/antlet/build.number to /data3/gump/depot/version/target/tests/antlet/build.number [copy] Copying /data3/gump/depot/version/src/test/java/org/apache/depot/version/ant/stamp/version.xml to /data3/gump/depot/version/target/tests/java/org/apache/depot/version/ant/stamp/version.xml [copy] Copying /data3/gump/depot/version/src/test/java/org/apache/depot/version/ant/environment/environment.xml to /data3/gump/depot/version/target/tests/java/org/apache/depot/version/ant/environment/environment.xml
Re: [GUMP@lsd]: depot/depot-version-antlet-test failed
Missed the cutoff time. Both this and the depot-version-test should be
fixed now.
Adam Jack wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project depot-version-antlet-test has an issue affecting its community
integration, and has been outstanding for 5 runs. The current state is
'Failed', for reason 'Build Failed'
Full details are available at:
http://lsd.student.utwente.nl/gump/depot/depot-version-antlet-test/index.html,
however some snippets follow:
- - - - - -- -- G U M P
Gump provided these annotations:
- Info - Enable verbose output, due to 4 previous error(s).
- Info - Failed with reason build failed
- Info - Enable debug output, due to build failure.
- - - - - -- -- G U M P
Gump performed this work:
http://lsd.student.utwente.nl/gump/depot/depot-version-antlet-test/gump_work/build_depot_depot-version-antlet-test.html
Work Name: build_depot_depot-version-antlet-test (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 2 seconds
Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -verbose -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/data3/gump/ant/dist -DDATE_STAMP=20040420 -f src/test/antlet/build.xml all
[Working Directory: /data3/gump/depot/version]
-
/data3/gump/ant/dist/tools/antlet/depot-version-0.1/xbuild.xml:44: Could not create task or type of type: stamp.
Ant could not find the task or a class this task relies upon.
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
- You have misspelt 'stamp'.
Fix: check your spelling.
- The task needs an external JAR file to execute
and this is not found at the right place in the classpath.
Fix: check the documentation for dependencies.
Fix: declare the task.
- The task is an Ant optional task and the JAR file and/or libraries
implementing the functionality were not found at the time you
yourself built your installation of Ant from the Ant sources.
Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
task and make sure it contains more than merely a META-INF/MANIFEST.MF.
If all it contains is the manifest, then rebuild Ant with the needed
libraries present in ${ant.home}/lib/optional/ , or alternatively,
download a pre-built release version from apache.org
- The build file was written for a later version of Ant
Fix: upgrade to at least the latest release version of Ant
- The task is not an Ant core or optional task
and needs to be declared using taskdef.
- You are attempting to use a task defined using
presetdef or macrodef but have spelt wrong or not
defined it at the point of use
Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath
Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.
at
org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:486)
at
org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:389)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:151)
at org.apache.tools.ant.Task.perform(Task.java:362)
at org.apache.tools.ant.Target.execute(Target.java:301)
at org.apache.tools.ant.Target.performTasks(Target.java:328)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.Main.runBuild(Main.java:667)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.Main.start(Main.java:151)
at org.apache.tools.ant.Main.main(Main.java:234)
Total time: 1 second
-
To subscribe to this information via syndicated feeds:
RSS:
http://lsd.student.utwente.nl/gump/depot/depot-version-antlet-test/depot-version-antlet-test.rss
| Atom:
http://lsd.student.utwente.nl/gump/depot/depot-version-antlet-test/depot-version-antlet-test.atom
--
Gump http://gump.apache.org/
[lsd]
Re: svn commit: rev 10130 - incubator/depot/trunk/update/src/sample/src/org/apache/depot/update/sample
Change the build.xml also.
[EMAIL PROTECTED] wrote:
Author: ajack
Date: Tue Apr 20 13:05:30 2004
New Revision: 10130
Modified:
incubator/depot/trunk/update/src/sample/src/org/apache/depot/update/sample/HelloWorld.java
Log:
converted log4j to regexp.
Modified:
incubator/depot/trunk/update/src/sample/src/org/apache/depot/update/sample/HelloWorld.java
==
---
incubator/depot/trunk/update/src/sample/src/org/apache/depot/update/sample/HelloWorld.java
(original)
+++
incubator/depot/trunk/update/src/sample/src/org/apache/depot/update/sample/HelloWorld.java
Tue Apr 20 13:05:30 2004
@@ -16,14 +16,18 @@
*/
package org.apache.depot.update.sample;
-import org.apache.log4j.Category;
+import org.apache.regexp.RE;
/**
* Classic HelloWorld
*/
public class HelloWorld {
- private final static Category LOG = Category.getInstance(HelloWorld.class);
- public static void main(String[] args) {
- System.out.println(Hello World.);
+ private static RE re = null;
+
+
+ public static void main(String[] args) throws Exception {
+ re = new RE(*);
+
+ System.out.println(Hello World. + re.toString());
}
}
Re: Consistency
Adam R. B. Jack wrote: Now we have three projects here we are showing consistency problems. at many levels, from different build scripts, to different naming conventions to different directory hierarchies. That is a shame. I'll keep trying to update whatever I find, but would appreciate help from other. The main reason I am bringing up is I can't find the ant types and antlib descriptor files for update. I fear they were removed. See that version has : Adding version\src\java\depot-version Adding version\src\java\depot-version-antlib.xml Deleting version\src\java\version Deleting version\src\java\version-antlib.xml which I just renamed. These used to sit in the src\java\ant directory. Update ought have similar ones, but I can't find them. Anybody got some, or know where they might be? They might be at update\src\java\org\apache\depot\update\antlib.xml R, Nick
Re: [GUMP@lsd]: depot/depot-version-antlet failed
Adam Jack wrote: To whom it may engage... Gump provided these annotations: - Info - Failed with reason configuration failed - Error - Bad Dependency. Project: depot-antlets unknown to *this* workspace Ooops, that should say antworks-antlets
More source tree combining.
Ok I combined the version source tree, no more ant/core I also fixed the jar so it get the antlib.xml. I am using the build_antlet.xml They are working really well for me. I added an version antlet and I will try to publish it soon. Take a look at the sample usage at, https://svn.apache.org/repos/asf/incubator/depot/trunk/version/src/test/antlet/build.xml R, Nick
Re: More source tree combining.
Try revert Adam R. B. Jack wrote: I tried doing 'svn update' and I get a conflict 'cos of some file I may have changed down in ant/test (probably sandbox.chalko) that I'd not checked in. I can't seem to find a --force option to ignore this. Any thoughts? Getting used to SVN is slow going... regards Adam - Original Message - From: Adam R. B. Jack [EMAIL PROTECTED] To: Depot Development [EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 7:24 AM Subject: Re: More source tree combining. I wonder if we can achieve the discipline I was hoping for (w/o the hassle) by still building it in two parts in Gump, to ensure no ant dependencies get into non-ant work. Oh well, no biggee. Yours was the right call. I appreciate you making progress on this... regards Adam - Original Message - From: Nick Chalko [EMAIL PROTECTED] To: Depot Development [EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 12:20 AM Subject: More source tree combining. Ok I combined the version source tree, no more ant/core I also fixed the jar so it get the antlib.xml. I am using the build_antlet.xml They are working really well for me. I added an version antlet and I will try to publish it soon. Take a look at the sample usage at, https://svn.apache.org/repos/asf/incubator/depot/trunk/version/src/test/antlet/build.xml R, Nick
[Fwd: [digester] runtime version info]
---BeginMessage--- Hi, I notice that Xalan has implemented a new class: org.apache.xalan.Version with a method static String getVersion() and also a static main method which prints the version#. See: http://xml.apache.org/xalan-j/apidocs/org/apache/xalan/Version.html The comment associated with this indicates that having a Version class is the upcoming standard for providing runtime version info for apache projects. Do you think we should have a class org.apache.commons.digester.Version? Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---End Message---
svn import won't work for web site
SVN import fails on second import. It will not work for keep the website uptodate. I will have to figure out another method to use in the apache antlet.
Depot code prunning.
Version and Update are working product, the ant ruperset task functions. However the code is bloated. Way to many classes with way to many methods and constructors. It makes it really hard to figure out what to do. I think we need to aggressively cut any method or class that is not being used right now. I propose we investigate clover or some other test coverage tools, and use it to help us delete unused classes and methods. R, Nick
Depot sites.
OK we need to start getting the depot sites up. depot/site depot/ruper and depot/version. Where are we pushing the site too for now http://incubator.apahce.org/projects/depot ? How are we doing the push. Checkin the HTML into cvs ? R, Nick
skinconf.xml
I can't get the patches for skinconf to work or the tag of ruper to work for me in eclipse. Can someone apply Nicola's changes to https://svn.apache.org/repos/asf/incubator/depot/trunk/site/src/documentation/skinconf.xml R, Nick
Re: Ok, I'm in ...
Adam R. B. Jack wrote: I'm going to dedicate some time to depot. Sorry it took me so long. Feel free to let me know where you need me... Take a look at ruperset and help me make sure ruperset picks the best available by default. Right now it is just returning the first one found. R, Nick
RuperSet not gettingl latest verion
Building the sample I discover that ruper set is not downloading the best version available. I need to work on this must be an option for the query. R, Nick
RuperSet not getting latest version
I should not send emails after midnight. Nick Chalko wrote: Building the sample I discover that ruper set is not downloading the best version available. I need to work on this must be an option for the query. R, Nick
naming our jars was: [GUMP@lsd]: depot/depot-ruper failed
Adam R. B. Jack wrote:
This gump build is failing 'cos the gump metadata thinks the ruper jar is
named differently ('cos I cut-n-paste it from the version one.)
Let's try to be consistent between version and ruper. So:
Do folks want:
apache-depot-x
depot-x
x
apache-x
is another option.
I vote to be consvative and avoid conflicts.
apache-depot-x
I'm pretty ambivalence, but personally, I think the 'apache' on the jar is a
bit of a mouthful. I was dubious about depot being there, but can live with
that. I'll wait for other preferences before I pick one.
regards,
Adam
Re: MD5 Hash
Adam R. B. Jack wrote: Hmm, what makes folk think that the file could be changed without the MD5 hash file being changed also. I feel there has to be some private key from the originator, to ensure that nobody could fake both. The MD5 should always come from the authoritative source (apache.org) using https. How are we going to know what the authoritative source for a resource is. For java we could enforce a reverse domain name. ie packages like org.apache must get a md5 for an apache.org website. So, if there are such keys, how do we acquire them? How do we trust them? regards Adam
Re: svn acces
Noel fixed my access :-) But no commit notice mail yet. Perhaps it is just slow. Nick Chalko wrote: I am still having rouble commiting to svn. I have set my svn password ad svn.apache.org. Any Ideas. R, Nick
