Hi I agree with you. There should be sources archive along with binaries for every released Maven version, even beta. I don't think this is to much work. When one builds binaries (probably Bret does it), he has sources that can be distributed.
Greg ----- Original Message ----- From: "Andreas Sahlbach" <[EMAIL PROTECTED]> To: "Maven Developers List" <dev@maven.apache.org> Sent: Wednesday, October 19, 2005 12:54 AM Subject: Fwd: Beta3 Build I haven't got any answer for my questions, so I have to assume that it is not possible to somehow get the source code for the beta3 build and rebuild maven2 from scratch. This is kind of funny, because I though that the ability to recreate a build in a stable development environment is one of the main requirements that a build tool should fulfill (maybe together with a source code repository). Ok then, so I will not create a gentoo build for maven2. I fear that there are a number of other Linux distributions that will have serious trouble with this kind of release tactics. Fare well guys, Andreas ---------- Forwarded message ---------- From: Andreas Sahlbach <[EMAIL PROTECTED]> Date: 17.10.2005 10:10 Subject: Re: Beta3 Build To: Maven Developers List <dev@maven.apache.org> Brett, as I said I am trying to make a gentoo build for maven2. This means that I have to build maven2 from scratch. All I have is a base unix system (together with a java sdk and some dependencies if you need it). I followed the instructions of the build page, but this failed. So, please just tell me, 1) where can I download the sourcecode for the beta3 2) how can I build it without having already maven or maven2 installed I searched the archive for these problems, but haven't found something. Actually I found too much, because searching for build problems in the archives of a build tool founds nearly everything. :-) If there is some doku somewhere I haven't found yet, I apologize. Please point me to it and I will follow the instructions myself. 2005/10/17, Brett Porter <[EMAIL PROTECTED]>: > Andreas, > > The bootstrap is not intended for tagged builds. > > Please use "m2 install" from the root projecft, and m2 assembly:assembly > from > the maven-core project. > > Note that each plugin is released individually and has their own tags - > while > there is a snapshot of the plugin code in the tag these would not be the > current releases at that time. In the near future we will be separating > them > out (see the other thread on this list). > > - Brett > > Quoting Andreas Sahlbach <[EMAIL PROTECTED]>: > > > Hi! > > > > I am trying to set up a gentoo build for maven2 Beta3, but I failed > > unfortunately. I basically > > 1) checked out the subversion tag maven-2.0-beta-3, > > 2) set the maven home directory to an empty directory, > > export M2_HOME="/var/tmp/portage/maven-2.0_beta3/work/m2_home" > > 3) set the maven repository to an empty directory > > export > > MAVEN_OPTS="-Dmaven.repo.local=/var/tmp/portage/maven- > 2.0_beta3/work/m2_repo/" > > and > > 4) called the bootstrap build (./m2-bootstrap-all.sh). > > A bunch of components were downloaded and the build started. The first > > problem was that the build bailed out here: > > ============================= cut > > ========================================== > > Building project in > > /var/tmp/portage/maven-2.0_beta3/work/maven-2.0-beta-3/maven-plugins/maven- > jar-plugin > > ... > > -------------------------------------------------------------------- > > Building project in > > /var/tmp/portage/maven-2.0_beta3/work/maven-2.0-beta-3/maven-plugins/maven- > jar-plugin > > Error reading POM: > > /var/tmp/portage/maven-2.0_beta3/work/maven-2.0-beta-3/maven-plugins/maven- > jar-plugin/pom.xml > > Exception in thread "main" java.io.FileNotFoundException: > > /var/tmp/portage/maven-2.0_beta3/work/m2_repo/org/apache/maven/maven- > archiver/2.0-beta-3-SNAPSHOT/maven-archiver-2.0-beta-3-SNAPSHOT.pom > > (No such file or directory) > > at model.ModelReader.retrievePom(ModelReader.java:513) > > at model.ModelReader.resolveDependencies(ModelReader.java:439) > > at model.ModelReader.endElement(ModelReader.java:410) > > at > > org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1720) > > at > > org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) > > at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) > > at > > org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) > > at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) > > at util.AbstractReader.parse(AbstractReader.java:63) > > at MBoot.buildProject(MBoot.java:508) > > at MBoot.run(MBoot.java:382) > > at MBoot.main(MBoot.java:124) > > ============================= cut > > ========================================== > > The snapshot directory it was trying to read was empty. > > I patched maven-jar-plugin's pom.xml to refer to 2.0-beta-3 instead of > > 2.0-beta-3-SNAPSHOT to let the build continue. After this I restarted > > the build and got another error: > > ============================= cut > > ========================================== > > Building project in > > /var/tmp/portage/maven-2.0_beta3/work/maven-2.0-beta-3/maven-plugins/maven- > plugin-plugin > > ... > > -------------------------------------------------------------------- > > Building project in > > /var/tmp/portage/maven-2.0_beta3/work/maven-2.0-beta-3/maven-plugins/maven- > plugin-plugin > > Downloading > > http://snapshots.maven.codehaus.org/maven2//org/apache/maven/plugins/maven- > plugin-parent/2.0-beta-3-SNAPSHOT/maven-metadata.xml > > WARNING: remote metadata version not found, using local: > > http://snapshots.maven.codehaus.org/maven2//org/apache/maven/plugins/maven- > plugin-parent/2.0-beta-3-SNAPSHOT/maven-metadata.xml > > (HTTP Error: 404 Not Found) > > Downloading > > http://snapshots.maven.codehaus.org/maven2//org/apache/maven/plugins/maven- > plugin-parent/2.0-beta-3-SNAPSHOT/maven-plugin-parent-2.0-beta-3-SNAPSHOT.pom > > Artifact not found at > > [http://snapshots.maven.codehaus.org/maven2//org/apache/maven/plugins/maven- > plugin-parent/2.0-beta-3-SNAPSHOT/maven-plugin-parent-2.0-beta-3-SNAPSHOT.pom] > > Error reading POM: > > /var/tmp/portage/maven-2.0_beta3/work/maven-2.0-beta-3/maven-plugins/maven- > plugin-plugin/pom.xml > > Exception in thread "main" download.DownloadFailedException: Failed to > > download > > org.apache.maven.plugins:maven-plugin-parent:2.0-beta-3-SNAPSHOT:pom > > at model.ModelReader.retrievePom(ModelReader.java:521) > > at model.ModelReader.endElement(ModelReader.java:233) > > at > > org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1720) > > at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) > > at > > org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) > > at > > org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) > > at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) > > at > > org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) > > at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) > > at util.AbstractReader.parse(AbstractReader.java:63) > > at MBoot.buildProject(MBoot.java:509) > > at MBoot.run(MBoot.java:383) > > at MBoot.main(MBoot.java:124) > > ============================= cut > > ========================================== > > > > This time the plugin could not even be found to download! At this > > point I gave up... :-( > > > > Do you guys really think, that people will trust a build tool, that > > cannot even provide a stable snapshot of it's own build? I am not > > talking about maven2 functionality. This is beta and noone will expect > > a bug free software here. But excuse me, you must be capable of > > providing a well-defined source-snapshot of your own releases! > > > > Because if you cannot provide this, then I really have to assume that, > > if I will use maven2 for my projects then I will end up in the same > > mess like you. And that's something that every professional software > > developer should try to avoid like hell. > > > > --- > > Andreas Sahlbach > > > > > > > > > > -- > > Andreas Sahlbach > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andreas Sahlbach -- Andreas Sahlbach --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
