Hi Robert, robert burrell donkin wrote: > > given that maven requires released dependencies, i suspect that these > issues are going to have to be tackled sooner or later.
No, it does not. Suppose i have a lab project "foo", that is organized on "foo-core", "foo-components" and "foo-web". Foo-web depends on foo-core and foo-components, but this does not mean that they have to be plubished anywhere. Everyone can simply checkout the entire foo project, launch maven, it will build foo-core and foo-components placing them in the local maven repository, and then build foo-web using foo-core and foo-components. If foo-core then depends on, say, commons-beanutils, that package will be distributed on public repositories and there is no problem for foo to depend on it. If then foo depends on a bar-core, which is in turn another lab project or another somehow unreleasable artifact, there are two possibilities : - user can checkout bar, build it, and then maven will find it from the local user repository - foo developer, as if it were ant, can include a folder, called for example "foo-maven-repo", with the proper structure, containing the bar artifacts, and then add in the foo pom.xml file the folder as a repository. Maven will then find bar artifacts as if they where on a public repository, while in fact they are in a local folder checked out from svn. So, maven is not a problem for this subject. Simone --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
