Being able to build the samples while offline would be good but it sounds like its not a trivial task to fix this, so I'd be ok with leaving fixing it till after M1.
...ant On 5/17/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Jeremy Boynes wrote: > AIUI one of the goals of the distro was that is was a complete > standalone distribution (what Ant described as the "try it out on the > train" scenario). However, the build for the samples included in it > assumes it can download artifacts from the main maven repositories which > requires the user to be online. > > The pom also has a reference to: > <repository> > <id>incubating-M1</id> > <name>incubating-M1</name> > <url>http://people.apache.org/~jsdelfino/maven2</url> > </repository> > > I don't think that it is appropriate for a distribution to have > references to a repository in someone's home directory as that is not > really a suitable long term location. > > -- > Jeremy > I agree. Good point, we should be able to build the samples offline. This triggers a number of questions for the group: - Do we want to ship with the distribution a local maven repos with the dependencies? or just Ant scripts to build the samples from the JARs in the distribution? - If we provide Ant scripts, do we want to keep both Ant and Maven build options? is there any value in showing people how to build Tuscany applications with Maven? - If we only provide Ant scripts, does it still make sense at all to have the Maven usual src/main/java src/mainresources etc. folder structure in the samples? - What should we do with BigBank, which currently requires Maven wsdljava and sdo plugins to build? don't we need Ant equivalents for these plugins? Thoughts? -- Jean-Sebastien
