First comments from a newbee
François Mireaux <[email protected]> Mon, 11 Aug 2003 17:30:34 +0200
| Newsgroups | gmane.comp.krysalis.user |
|---|---|
| Message-ID | <006501c3601d$825459b0$0815040a@lerins> |
I have downloaded Krysalis-Version last week, and here are some questions and comments on
(in realtive arbitrary order) :
- the download link (under "Community") was difficult to find for me
- what tool to read the XML documentation ? (I guess it's Forrest which
need Cocoon ...). An HTML version with the binary package could be friendly.
- VersionTool said it use a file d:\version.constraints which don't
exists. I found this file int src/main but modifications have no effect on
VersionTool. After some time and tries, it seems that VersionTool uses the version.constraints of the jar file. Is it the only way ? What if no jar file ?
- "VersionTool" -c says that it don't find the version of
org.apache.commons.logging with the jar file in classpath and version
information in the manifest file. The source file "Resolver.java" seems
strange :
=================================
public VersionInformation resolve(
AnnotationScratchpad pad,
VersionIdentifier identifier)
throws VersionException {
VersionInformation candidateInfo = null;
VersionLoadContext loadContext = m_stampLoader.load(pad, identifier);
if (null == loadContext)
m_packageLoader.load(pad, identifier);
=================================
last line seems to be better with : "loadContext = m_packageLoader.load(pad, identifier);"
Well, nothing change, because package information in PackageVersionLoader is loaded trought Package.getPackage() which return "null" if the package was not already in use by one classe.
(I wonder if I have not see something about this problem somewhere in the Krysalis site...).
Right now, constraints management without modification of packages (if possible) is my first interest for Krysalis-Version.
F. Mireaux
BPA
West Park Bat. A
21, Rue de l'Industrie
69530 Brignais FRANCE
Tél : +33 04 72 31 80 37
Fax : +33 04 72 31 80 31