Matthias, I think the latest change you made to the build.xml for samples/ejb-template might be an error. At least it breaks the wizard and project templates as I had imagined them to work.
The build.xml file in the sample/ejb-template file was not actually meant to be used to create a andromda-ejb-template.zip file for the AndroMDA distribution. It was meant as an example build.xml file for an ejb project. planning that all of the materials contained in the samples/XXX-template directories would be used as templates for projects. The 'dist' targets or 'deploy' targets in template build.xml files are examples of how to do 'dist' and 'deploy' for the technologies utilized by the template. The place you probably should have put the rule for building the 'andromda-ejb-template.zip' file was probably in the sample/build.xml file. I want to say how important I think these template projects are. IMHO we have been doing an extremely poor job in this area specifically and in the usability in general. There should be at least one XXX-template sample project for every cartridge. We should not allow a cartridge to be released until that cartridge has at least one template project for it. For example, the hibernate cartridge and struts-cartridges do not have template projects. Therefore we should not do another release of AndroMDA until this has been fixed. A template project is important for two reasons: - it provides a simple unit test of the cartridge - it provides a simple example of how to used the cartridge Regarding the packaging of ZIP files: I got feed back from a few users about our collection of downloadable 'zip' files. They found it very confusing that there were so many zip files to choose from and they were uncertain about where to unzip them. I understand that big zips file have some evils, but IMHO having many zip files is worse. I have personally found it easier to build AndroMDA from CVS than download the zip files from CVS. That's definitely not the way we want it to be. The way AndroMDA should be is that if somebody were to ask one of us how to build an EJB, STRUTS, or HIBERNATE project we should be able to do the demonstrate on their machine within a very short number of minutes. Imagine yourself in the position of having to install and demonstrate AndroMDA to somebody using a brand new PC with nothing already installed on it. That is what I mean by demonstrate AndroMDA - install and use. I will volunteer to finish up the ejb-template project, but I am not very keen about doing that unless we also decide to do java-template, struts-template and hibernate-template projects. Plus we need to enforce keeping these template projects operational. For example: if someone submits a change to a cartridge then they should also test to make sure the template project for that cartridge still works. We should do these template projects before we branch. What do you guys think? > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Matthias > Bohlen > Sent: Saturday, July 05, 2003 9:39 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [Andromda-devel] Finalizing the new build system > > > Hi Tony, > > a question on your new build system: How should the typical AndroMDA > user without CVS access deal with the resulting *.zip files? > > I see the following goals: > 1) Easy and reliable unpacking of the ZIPs. > 2) Easy startup to make a sample project run. > 3) Easy re-compilation of AndroMDA from the sources inside the ZIPs, not > those from CVS. > > How can we accomplish this? We're almost there but there is still a > little way to go: > > 1) The user should be able to unzip all the files into the same > directory, without thinking about it. This requires that each ZIP > contains its own internal subdirectory, there must be almost no files in > the root directory of the ZIP. > > 2) The user should be able to unpack andromda-template-project.zip (not > existing today), adjust a property file and launch the generator. This > requires that the build script creates andromda-template-project.zip > from samples/ejb-template and includes all sources. > > 3) The user should be able to start ant in the top level directory and > the whole generator should be rebuilt. The resulting ZIPs should be > identical to the ZIPs (s)he downloaded from SF.net. This requires that > the unzipped directory structure be almost identical to the directory > structure in CVS, otherwise the scripts will become too complex. > > Another possibility (suggested by Harald Weyhing): Pack all files into > only one *.ZIP. This would make point 1) easier for the user. > > What do you think about all this? I'd like to have points 1 to 3 > fulfilled for the next 2.x release. Do you think you will have time or > should somebody help? > > Cheers... > Matthias > > --- > > Matthias Bohlen > "Consulting that helps project teams to succeed..." > http://www.mbohlen.de/ > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 > _______________________________________________ > Andromda-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/andromda-devel ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
