On Wed, 2003-06-18 at 22:35, Aslak Helles�y wrote: > I haven't tested it yet. If XJavaDoc is included in the distro, it > should be versioned 1.0.1 (without SNAPSHOT) and tagged in CVS. Has this > been done?
The 1.2 stuff still uses xjavadoc 1.0; that's the version that's in the xjavadoc.version property in build.properties, and that's the version that it downloads from the repository if it can't find the sources. So that's the version the dist zip should include IMO. If, in fact, there's stuff in the XJD HEAD that's needed in XDT 1.2, then we should wait for the XJD 1.0.1 release before building the beta :-) But I thought we already did that, which was why we did the XJD 1.0 release? On a separate note, I assume XDoclet2 is using xjavadoc 1.0.1-SNAPSHOT? Where is that specified, though? I don't see any dependency entry for it in its project.xml. > And has XDoclet been tagged? Looks like it to me. There's a "XDoclet-v1-2beta3" tag appeared on the files in the xdoclet module. Strangely, it's also appeared on the xjavadoc module sources too; now that that's maintained & released separately there's no need to tag them too, is there? So long as we know which XJD release version XDT 1.2b3 is built against (and we do, from the properties file), we could fetch the relevant sources from its CVS based on that. In fact, if it's the current XJD head (i.e. 1.0.1-SNAPSHOT) that's been tagged, then that's inconsistent with the version specified in the XDoclet sources! Plus, the binary dist files may differ from what you'd get from building the source dist files, which defeats the purpose of having them... The dist files should be created by a clean build of a separate copy of the sources, checked out based on the tag after the tagging has been done. That's the safest way to ensure that anyone building it for themselves (e.g. for security/audit purposes, since we don't sign the jars or produce MD5 checksums of the dist files) will end up with the same jars we're using, so less scope for strange unreproduceable bugs being raised in JIRA or on the mailing lists. Also, it makes it less important if people continue committing stuff while the release is going on, since once the tagging has been done that's set in stone and won't be affected by the subsequent checkins. Andrew. > > Aslak > > > > > > > BOGAERT Mathias wrote: > > > >> Guys, > >> > >> Could you test the 1.2 beta 3 release on SourceForge right now? > >> I didn't announce this one yet. It is just the CVS from last night, > >> containing XJavaDoc and some Hibernate fixes. > >> > >> Thanks, > >> > >> Mathias ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
