|
I didn't say on themselfs!! wicket-cdapp-example should depend on Wicket and use Wickets libs if it wants to use the same libs. Only introduce new libs when wicket core doesn't have them. Developers wants to check it out from CVS. Thats how i work thats how they work. Checkout from cvs and run it. But if you have a very good distributable which is a eclipse project by itself where you can debug very vast throught the source of wicket and its examples then that is also a good option. It just should be plug'n'play. No configuration. johan Martijn Dashorst wrote: What you say is contradictionary: the projects should depend on only themselves, but they should also depend on one another ?Your friends can download the distributable for their leisure and trying purposes. That's why we create distributables for in the first place. And *THAT* isn't hard: unzip the wicket distributable to your workspace and press play. I consider CVS to be a protected interface: the world may use the interface, but has to abide to 'our rules'. This means using maven to build, also checking out the main project, etc. The distributables are the public interface: we have to abide to 'their rules'. This means that they are self contained, and should run on whatever configuration the user has (albeit limited in our support for IDE's). The minimum should be: eclipse + ant. Martijn -----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Namens Johan Compagner Verzonden: Monday, December 20, 2004 11:45 AM Aan: [EMAIL PROTECTED] Onderwerp: Re: [Wicket-develop] Dependency libraries in CVS for me the projects in cvs should depend on the projects in cvs itself (not snapshots of them) And also depend on the jars for that main project(s) so if a subproject of maven wants to use xxx.jar and the main project already has xxx.jar it should use that one instead of making its own reference. So that there is only one jar of a specific library in the wicket. I personally like to have completely selfcontained projects in eclipse (so projects depend on jars in the lib folder or on other eclipse projects) I have a few friends or mine who wanted to try wicket but getting it build and/or runned for some quick test to figure wicket out was just to hard. It should be simple: Check out wicket, checkout one of the example projects run a launch configuration (for example that starts jetty completely configured) Nothing more. johan Martijn Dashorst wrote: |
