You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Andreas Sahlbach <an...@gmail.com> on 2005/10/16 16:12:25 UTC
Beta3 Build
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Beta3 Build
Posted by Brett Porter <br...@apache.org>.
There are no snapshots in release builds (this is verified by the
release plugin), and quite often the release is done with a clean local
repository.
- Brett
Rafal Krzewski wrote:
> Grzegorz Slowikowski wrote:
>
>> 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.
>
>
> Well, you can get the same source's easily as it was written too many
> times in this thread. Unfortunately, it seems that you need to have a
> verbatim copy of Brett's local repository at the time the release was
> made to replicate the build! SNAPSHOT dependencies (and beta3 projects
> conatins such) and build repeatability don't mix. Period.
>
> I am not sure if it is possible/practical to pin down dependency
> versions in the whole source tree at the time of the release, but if not
> this is going to be a permanent source of frustration to people making
> homebrew builds.
>
> R.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Beta3 Build
Posted by Rafal Krzewski <Ra...@caltha.pl>.
Grzegorz Slowikowski wrote:
> 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.
Well, you can get the same source's easily as it was written too many
times in this thread. Unfortunately, it seems that you need to have a
verbatim copy of Brett's local repository at the time the release was
made to replicate the build! SNAPSHOT dependencies (and beta3 projects
conatins such) and build repeatability don't mix. Period.
I am not sure if it is possible/practical to pin down dependency
versions in the whole source tree at the time of the release, but if not
this is going to be a permanent source of frustration to people making
homebrew builds.
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Beta3 Build
Posted by Grzegorz Slowikowski <gs...@op.pl>.
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" <an...@gmail.com>
To: "Maven Developers List" <de...@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 <an...@gmail.com>
Date: 17.10.2005 10:10
Subject: Re: Beta3 Build
To: Maven Developers List <de...@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 <br...@apache.org>:
> 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 <an...@gmail.com>:
>
> > 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Andreas Sahlbach
--
Andreas Sahlbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Fwd: Beta3 Build
Posted by Brett Porter <br...@apache.org>.
I'm going to post a more comprehensive response about reorganising SVN
and rewriting the bootstrap to be more compatible with this technique.
What will be needed is a Wagon implementation for Gentoo, however, so
that installed packages can be used as a remote repository.
Alternatively, the packaging process could install these into a file://
repository on the system somewhere.
So the objectives we have:
1) build m2 with m2 (this is already possible, but I think now that 2.0
is out this should be the primary technique)
2) build source distros (these won't include plugins, and will build as
above)
3) bootstrap without an m2 installation
4) bootstrap without dependencies (ie, build plexus etc from sources
before m2)
- Brett
Rafal Krzewski wrote:
> Andreas Sahlbach wrote:
>
>> The Gentoo guys prefer to build every open source project by
>> themselves. Besides: building and installing a two, strictly separated
>> steps, so no writing into the system is allowed (and will be prevented
>> by the sandboxshell) during the build.
>
>
> IMHO even if the sources of m2 beta3 were compilable, your build would
> be hardly a sandboxed one. Note that m2 will download more than 150
> binary packages from the Internet, use them as build dependencies and
> later use them at runtime too.
>
> The whole point about maven is that it comes in two pieces - an
> application, and a collection of binary packages amassed by maven
> developers and users.
>
> For a completly sandboxed build you would have to compile all of these
> packages from source (a formidable task, especially some of those may
> reuqire maven2 to be built!), assemble a repository and make it
> available through a local web server, and use it as the remote
> repository for the bootstrap.
>
> Your complaints about buildable beta release are vaild, but the whole
> idea of buliding m2 the Gentoo way seems to me ill advised. There is a
> serious incompatibility of philosophy here. If someone wants to do Java
> development on a Gentoo system, they can do it the Java way, not
> necessarily the Gentoo way, right?
>
> regards,
> R.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Fwd: Beta3 Build
Posted by Rafal Krzewski <Ra...@caltha.pl>.
Andreas Sahlbach wrote:
> The Gentoo guys prefer to build every open source project by
> themselves. Besides: building and installing a two, strictly separated
> steps, so no writing into the system is allowed (and will be prevented
> by the sandboxshell) during the build.
IMHO even if the sources of m2 beta3 were compilable, your build would
be hardly a sandboxed one. Note that m2 will download more than 150
binary packages from the Internet, use them as build dependencies and
later use them at runtime too.
The whole point about maven is that it comes in two pieces - an
application, and a collection of binary packages amassed by maven
developers and users.
For a completly sandboxed build you would have to compile all of these
packages from source (a formidable task, especially some of those may
reuqire maven2 to be built!), assemble a repository and make it
available through a local web server, and use it as the remote
repository for the bootstrap.
Your complaints about buildable beta release are vaild, but the whole
idea of buliding m2 the Gentoo way seems to me ill advised. There is a
serious incompatibility of philosophy here. If someone wants to do Java
development on a Gentoo system, they can do it the Java way, not
necessarily the Gentoo way, right?
regards,
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Fwd: Beta3 Build
Posted by Andreas Sahlbach <an...@gmail.com>.
Thanks for the reply Kenney!
But if you read what I have written in my first mail to this, you will
see that I've done exactly what you have proposed and it failed
miserably. And yes, for some strange reasons, there are no source code
distributions for the releases.
The Gentoo guys prefer to build every open source project by
themselves. Besides: building and installing a two, strictly separated
steps, so no writing into the system is allowed (and will be prevented
by the sandboxshell) during the build.
All what I want is to recreate the build that you have made for the
beta3. As you can see in my original mail, if I get the source from
subversion using the beta3 tag, the build fails during the
build/download of the plugins.
Andreas
2005/10/19, Kenney Westerhof <ke...@apache.org>:
> On Wed, 19 Oct 2005, Andreas Sahlbach wrote:
>
> Don't give up that easily!
>
> First, Trygvis is already working on creating a debian source package;
> there might be some stuff you can re-use (contact him if he doesn't
> respond to this: trygvis@codehaus.org).
>
> Second, maven2 is hosted at apache in a subversion repository [1]. We use
> branches and tags. You can just check out the beta-3 tag [2] and work with
> that code (put together the info in 1 and 2 for the correct svn url for
> the tag). I don't think we ever released full source archives of maven2
> because everybody can check out the source.
>
> Hope this helps, and sorry there wasn't any reply - we might have thought
> people could figure out for themselves :)
>
> -- Kenney
>
> [1] http://maven.apache.org/maven2/source-repository.html
> [2] http://svn.apache.org/viewcvs.cgi/maven/components/tags/maven-2.0-beta-3/
>
>
> > 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 <an...@gmail.com>
> > Date: 17.10.2005 10:10
> > Subject: Re: Beta3 Build
> > To: Maven Developers List <de...@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 <br...@apache.org>:
> > > 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 <an...@gmail.com>:
> > >
> > > > 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: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Andreas Sahlbach
> >
> >
> > --
> > Andreas Sahlbach
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Andreas Sahlbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Fwd: Beta3 Build
Posted by Kenney Westerhof <ke...@apache.org>.
On Wed, 19 Oct 2005, Andreas Sahlbach wrote:
Don't give up that easily!
First, Trygvis is already working on creating a debian source package;
there might be some stuff you can re-use (contact him if he doesn't
respond to this: trygvis@codehaus.org).
Second, maven2 is hosted at apache in a subversion repository [1]. We use
branches and tags. You can just check out the beta-3 tag [2] and work with
that code (put together the info in 1 and 2 for the correct svn url for
the tag). I don't think we ever released full source archives of maven2
because everybody can check out the source.
Hope this helps, and sorry there wasn't any reply - we might have thought
people could figure out for themselves :)
-- Kenney
[1] http://maven.apache.org/maven2/source-repository.html
[2] http://svn.apache.org/viewcvs.cgi/maven/components/tags/maven-2.0-beta-3/
> 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 <an...@gmail.com>
> Date: 17.10.2005 10:10
> Subject: Re: Beta3 Build
> To: Maven Developers List <de...@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 <br...@apache.org>:
> > 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 <an...@gmail.com>:
> >
> > > 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: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> Andreas Sahlbach
>
>
> --
> Andreas Sahlbach
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Fwd: Beta3 Build
Posted by Andreas Sahlbach <an...@gmail.com>.
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 <an...@gmail.com>
Date: 17.10.2005 10:10
Subject: Re: Beta3 Build
To: Maven Developers List <de...@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 <br...@apache.org>:
> 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 <an...@gmail.com>:
>
> > 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Andreas Sahlbach
--
Andreas Sahlbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Beta3 Build
Posted by Andreas Sahlbach <an...@gmail.com>.
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 <br...@apache.org>:
> 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 <an...@gmail.com>:
>
> > 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Andreas Sahlbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Beta3 Build
Posted by Brett Porter <br...@apache.org>.
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 <an...@gmail.com>:
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Beta3 Build
Posted by Rafal Krzewski <Ra...@caltha.pl>.
Andreas Sahlbach wrote:
> 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.
Luckily those problems do not carry over to projects that are build by
maven. It's just the matter of being consistent and using _your_ version
numbers and SCM tags right.
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org