You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by David Zeleznik <dz...@ilog.com> on 2003/04/01 19:28:44 UTC
Bootstrap build info
Hi,
After using beta8 for several weeks, I tried unsuccessfully several times to
build Maven from source. In the end, I discovered that if you have a
${user.home}/build.properties file, this must be deleted or temporarilly
renamed before starting the bootstrap build. This crucial bit of info is
missing from the docs at http://maven.apache.org/start/bootstrap.html. In my
case, I had an overridden maven.repo.local property pointing to my beta8
repo cache. This seemed to be the culprit that was causing the bootstrap
builds to fail. In the end, it seems safest just to make sure that you do
not have any $user.home/build.properties file before starting the build.
Maybe someone can update the docs?
--------------------------------------
David Zeleznik
ILOG - Changing the rules of business
mailto:dzeleznik@ilog.com
http://www.ilog.com
--------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Bootstrap build info
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-04-01 at 16:13, David Zeleznik wrote:
> Hi Jason,
>
> I have done some more testing. FYI, my environment is Win2000, Ant 1.5.2,
> and jUnit 3.8.1.
Almost all the core developers point their local repo somewhere other
than the default as it's very annoying to have to download everything
during every bootstrap. I've had a pointer to my local repo, which is
outside the maven home directory, far prior to the release of beta-8 and
have never experienced any problems. I believe Dion and Bob do the same
thing. I would venture to say the problem is on your end.
>
>
> jvz.
>
> Jason van Zyl
> jason@zenplex.com
> http://tambora.zenplex.org
>
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>
> -- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Bootstrap build info
Posted by David Zeleznik <dz...@ilog.com>.
> Maybe you have no ant-optional-x.y.jar in that repo??? Or a bad
> one....try
> blowing it away.
Thanks so much! Indeed, the ant-optional-1.5.1.jar in my repo was corrupted
and only 224K (should be 640K). Not sure how that happened and why I never
noticed it during a month of daily maven usage. Doesn't matter, my bootstrap
builds are fine now.
Regards,
--------------------------------------
David Zeleznik
ILOG - Changing the rules of business
mailto:dzeleznik@ilog.com
http://www.ilog.com
--------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Bootstrap build info
Posted by di...@multitask.com.au.
Maybe you have no ant-optional-x.y.jar in that repo??? Or a bad one....try
blowing it away.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
"David Zeleznik" <dz...@ilog.com> wrote on 02/04/2003 07:13:18 AM:
> Hi Jason,
>
> I have done some more testing. FYI, my environment is Win2000, Ant
1.5.2,
> and jUnit 3.8.1.
>
> > > > > After using beta8 for several weeks, I tried unsuccessfully
> > > > several times to
> > > > > build Maven from source. In the end, I discovered that if you
have a
> > > > > ${user.home}/build.properties file, this must be deleted or
> > temporarilly
> > > > > renamed before starting the bootstrap build.
> > > >
> > > > No, it does not. I have a ~/build.properties file and I bootstrap
all
> > > > the time.
> > >
> > > Are you defining maven.repo.local to point to a directory other than
> > > $MAVEN_HOME/repository? This seemed to be the problem for me.
> >
> > Yes I am.
>
> Yes, I confirm. I am able to point maven.repo.local to an initially
empty
> directory and the bootstrap builds okay. However, if maven.repo.local
points
> to the local repo I was using with beta8, then I get the following
failure
> building the plugins:
>
> [echo]
> +------------------------------------------------------------------+
> [echo] |
> |
> [echo] | B U I L D I N G T H E P L U G I N S
> |
> [echo] |
> |
> [echo]
> +------------------------------------------------------------------+
> [echo]
> [exec] java.lang.reflect.InvocationTargetException
> [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [exec] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
> sorImpl.java:39)
> [exec] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
> hodAccessorImpl.java:25)
> [exec] at java.lang.reflect.Method.invoke(Method.java:324)
> [exec] at com.werken.forehead.Forehead.run(Forehead.java:543)
> [exec] at com.werken.forehead.Forehead.main(Forehead.java:573)
> [exec] Caused by: java.lang.NoClassDefFoundError:
> org/apache/tools/ant/task
> defs/optional/junit/FormatterElement$TypeAttribute
> [exec] at
> org.apache.commons.jelly.tags.ant.AntTagLibrary.<clinit>(AntT
> agLibrary.java:120)
> [exec] at
> org.apache.maven.jelly.tags.jeez.JeezTagLibrary.<init>(JeezTa
> gLibrary.java:32)
> [exec] at
> org.apache.maven.jelly.tags.jeez.MavenJeezTagLibrary.<init>(M
> avenJeezTagLibrary.java:73)
> [exec] at
> org.apache.maven.jelly.MavenJellyContext.initializeContext(Ma
> venJellyContext.java:141)
> [exec] at
> org.apache.maven.jelly.MavenJellyContext.<init>(MavenJellyCon
> text.java:104)
> [exec] at
> org.apache.maven.MavenUtils.createContext(MavenUtils.java:806
> )
> [exec] at
> org.apache.maven.MavenUtils.createContext(MavenUtils.java:738
> )
> [exec] at
> org.apache.maven.cli.App.initializeRootContext(App.java:342)
> [exec] at org.apache.maven.cli.App.initialize(App.java:281)
> [exec] at org.apache.maven.cli.App.doMain(App.java:447)
> [exec] at org.apache.maven.cli.App.main(App.java:1080)
> [exec] ... 6 more
> [echo]
> [echo]
> +------------------------------------------------------------------+
>
> The bootstrap build ignores this initial error and continues until it
later
> trips over its own feet trying to build itself:
>
> [echo]
> +------------------------------------------------------------------+
> [echo] |
> |
> [echo] | B U I L D I N G M A V E N W I T H I T S E L F
> |
> [echo] |
> |
> [echo]
> +------------------------------------------------------------------+
> [echo]
> [exec] java.lang.reflect.InvocationTargetException
> [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [exec] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
> sorImpl.java:39)
> [exec] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
> hodAccessorImpl.java:25)
> [exec] at java.lang.reflect.Method.invoke(Method.java:324)
> [exec] at com.werken.forehead.Forehead.run(Forehead.java:543)
> [exec] at com.werken.forehead.Forehead.main(Forehead.java:573)
> [exec] Caused by: java.lang.NoClassDefFoundError:
> org/apache/tools/ant/task
> defs/optional/junit/FormatterElement$TypeAttribute
> [exec] at
> org.apache.commons.jelly.tags.ant.AntTagLibrary.<clinit>(AntT
> agLibrary.java:120)
> [exec] at
> org.apache.maven.jelly.tags.jeez.JeezTagLibrary.<init>(JeezTa
> gLibrary.java:32)
> [exec] at
> org.apache.maven.jelly.tags.jeez.MavenJeezTagLibrary.<init>(M
> avenJeezTagLibrary.java:73)
> [exec] at
> org.apache.maven.jelly.MavenJellyContext.initializeContext(Ma
> venJellyContext.java:141)
> [exec] at
> org.apache.maven.jelly.MavenJellyContext.<init>(MavenJellyCon
> text.java:104)
> [exec] at
> org.apache.maven.MavenUtils.createContext(MavenUtils.java:806
> )
> [exec] at
> org.apache.maven.MavenUtils.createContext(MavenUtils.java:738
> )
> [exec] at
> org.apache.maven.cli.App.initializeRootContext(App.java:342)
> [exec] at org.apache.maven.cli.App.initialize(App.java:281)
> [exec] at org.apache.maven.cli.App.doMain(App.java:447)
> [exec] at org.apache.maven.cli.App.main(App.java:1080)
> [exec] ... 6 more
>
> The only thing I can guess is that some dependency cached by beta8 in my
> local repo is somehow satisfying a beta9 dependency, but is incompatible
> with it. Note, that when I do a bootstrap build against my beta8 local
repo,
> I do not see any new downloads from ibiblio. I hope this helps pinpoint
the
> issue for you. Regards,
>
> --------------------------------------
> David Zeleznik
> ILOG - Changing the rules of business
> mailto:dzeleznik@ilog.com
> http://www.ilog.com
> --------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Bootstrap build info
Posted by David Zeleznik <dz...@ilog.com>.
Hi Jason,
I have done some more testing. FYI, my environment is Win2000, Ant 1.5.2,
and jUnit 3.8.1.
> > > > After using beta8 for several weeks, I tried unsuccessfully
> > > several times to
> > > > build Maven from source. In the end, I discovered that if you have a
> > > > ${user.home}/build.properties file, this must be deleted or
> temporarilly
> > > > renamed before starting the bootstrap build.
> > >
> > > No, it does not. I have a ~/build.properties file and I bootstrap all
> > > the time.
> >
> > Are you defining maven.repo.local to point to a directory other than
> > $MAVEN_HOME/repository? This seemed to be the problem for me.
>
> Yes I am.
Yes, I confirm. I am able to point maven.repo.local to an initially empty
directory and the bootstrap builds okay. However, if maven.repo.local points
to the local repo I was using with beta8, then I get the following failure
building the plugins:
[echo]
+------------------------------------------------------------------+
[echo] |
|
[echo] | B U I L D I N G T H E P L U G I N S
|
[echo] |
|
[echo]
+------------------------------------------------------------------+
[echo]
[exec] java.lang.reflect.InvocationTargetException
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[exec] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at com.werken.forehead.Forehead.run(Forehead.java:543)
[exec] at com.werken.forehead.Forehead.main(Forehead.java:573)
[exec] Caused by: java.lang.NoClassDefFoundError:
org/apache/tools/ant/task
defs/optional/junit/FormatterElement$TypeAttribute
[exec] at
org.apache.commons.jelly.tags.ant.AntTagLibrary.<clinit>(AntT
agLibrary.java:120)
[exec] at
org.apache.maven.jelly.tags.jeez.JeezTagLibrary.<init>(JeezTa
gLibrary.java:32)
[exec] at
org.apache.maven.jelly.tags.jeez.MavenJeezTagLibrary.<init>(M
avenJeezTagLibrary.java:73)
[exec] at
org.apache.maven.jelly.MavenJellyContext.initializeContext(Ma
venJellyContext.java:141)
[exec] at
org.apache.maven.jelly.MavenJellyContext.<init>(MavenJellyCon
text.java:104)
[exec] at
org.apache.maven.MavenUtils.createContext(MavenUtils.java:806
)
[exec] at
org.apache.maven.MavenUtils.createContext(MavenUtils.java:738
)
[exec] at
org.apache.maven.cli.App.initializeRootContext(App.java:342)
[exec] at org.apache.maven.cli.App.initialize(App.java:281)
[exec] at org.apache.maven.cli.App.doMain(App.java:447)
[exec] at org.apache.maven.cli.App.main(App.java:1080)
[exec] ... 6 more
[echo]
[echo]
+------------------------------------------------------------------+
The bootstrap build ignores this initial error and continues until it later
trips over its own feet trying to build itself:
[echo]
+------------------------------------------------------------------+
[echo] |
|
[echo] | B U I L D I N G M A V E N W I T H I T S E L F
|
[echo] |
|
[echo]
+------------------------------------------------------------------+
[echo]
[exec] java.lang.reflect.InvocationTargetException
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[exec] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[exec] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:324)
[exec] at com.werken.forehead.Forehead.run(Forehead.java:543)
[exec] at com.werken.forehead.Forehead.main(Forehead.java:573)
[exec] Caused by: java.lang.NoClassDefFoundError:
org/apache/tools/ant/task
defs/optional/junit/FormatterElement$TypeAttribute
[exec] at
org.apache.commons.jelly.tags.ant.AntTagLibrary.<clinit>(AntT
agLibrary.java:120)
[exec] at
org.apache.maven.jelly.tags.jeez.JeezTagLibrary.<init>(JeezTa
gLibrary.java:32)
[exec] at
org.apache.maven.jelly.tags.jeez.MavenJeezTagLibrary.<init>(M
avenJeezTagLibrary.java:73)
[exec] at
org.apache.maven.jelly.MavenJellyContext.initializeContext(Ma
venJellyContext.java:141)
[exec] at
org.apache.maven.jelly.MavenJellyContext.<init>(MavenJellyCon
text.java:104)
[exec] at
org.apache.maven.MavenUtils.createContext(MavenUtils.java:806
)
[exec] at
org.apache.maven.MavenUtils.createContext(MavenUtils.java:738
)
[exec] at
org.apache.maven.cli.App.initializeRootContext(App.java:342)
[exec] at org.apache.maven.cli.App.initialize(App.java:281)
[exec] at org.apache.maven.cli.App.doMain(App.java:447)
[exec] at org.apache.maven.cli.App.main(App.java:1080)
[exec] ... 6 more
The only thing I can guess is that some dependency cached by beta8 in my
local repo is somehow satisfying a beta9 dependency, but is incompatible
with it. Note, that when I do a bootstrap build against my beta8 local repo,
I do not see any new downloads from ibiblio. I hope this helps pinpoint the
issue for you. Regards,
--------------------------------------
David Zeleznik
ILOG - Changing the rules of business
mailto:dzeleznik@ilog.com
http://www.ilog.com
--------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Bootstrap build info
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-04-01 at 13:13, David Zeleznik wrote:
> > > After using beta8 for several weeks, I tried unsuccessfully
> > several times to
> > > build Maven from source. In the end, I discovered that if you have a
> > > ${user.home}/build.properties file, this must be deleted or temporarilly
> > > renamed before starting the bootstrap build.
> >
> > No, it does not. I have a ~/build.properties file and I bootstrap all
> > the time.
>
> Are you defining maven.repo.local to point to a directory other than
> $MAVEN_HOME/repository? This seemed to be the problem for me.
Yes I am.
> --------------------------------------
> David Zeleznik
> ILOG - Changing the rules of business
> mailto:dzeleznik@ilog.com
> http://www.ilog.com
> --------------------------------------
>
>
> > > This crucial bit of info is
> > > missing from the docs at
> > http://maven.apache.org/start/bootstrap.html. In my
> > > case, I had an overridden maven.repo.local property pointing to my beta8
> > > repo cache. This seemed to be the culprit that was causing the bootstrap
> > > builds to fail. In the end, it seems safest just to make sure
> > that you do
> > > not have any $user.home/build.properties file before starting the build.
> > > Maybe someone can update the docs?
> > >
> > > --------------------------------------
> > > David Zeleznik
> > > ILOG - Changing the rules of business
> > > mailto:dzeleznik@ilog.com
> > > http://www.ilog.com
> > > --------------------------------------
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > --
> > jvz.
> >
> > Jason van Zyl
> > jason@zenplex.com
> > http://tambora.zenplex.org
> >
> > In short, man creates for himself a new religion of a rational
> > and technical order to justify his work and to be justified in it.
> >
> > -- Jacques Ellul, The Technological Society
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Bootstrap build info
Posted by David Zeleznik <dz...@ilog.com>.
> > After using beta8 for several weeks, I tried unsuccessfully
> several times to
> > build Maven from source. In the end, I discovered that if you have a
> > ${user.home}/build.properties file, this must be deleted or temporarilly
> > renamed before starting the bootstrap build.
>
> No, it does not. I have a ~/build.properties file and I bootstrap all
> the time.
Are you defining maven.repo.local to point to a directory other than
$MAVEN_HOME/repository? This seemed to be the problem for me.
--------------------------------------
David Zeleznik
ILOG - Changing the rules of business
mailto:dzeleznik@ilog.com
http://www.ilog.com
--------------------------------------
> > This crucial bit of info is
> > missing from the docs at
> http://maven.apache.org/start/bootstrap.html. In my
> > case, I had an overridden maven.repo.local property pointing to my beta8
> > repo cache. This seemed to be the culprit that was causing the bootstrap
> > builds to fail. In the end, it seems safest just to make sure
> that you do
> > not have any $user.home/build.properties file before starting the build.
> > Maybe someone can update the docs?
> >
> > --------------------------------------
> > David Zeleznik
> > ILOG - Changing the rules of business
> > mailto:dzeleznik@ilog.com
> > http://www.ilog.com
> > --------------------------------------
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> --
> jvz.
>
> Jason van Zyl
> jason@zenplex.com
> http://tambora.zenplex.org
>
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>
> -- Jacques Ellul, The Technological Society
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Bootstrap build info
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-04-01 at 12:28, David Zeleznik wrote:
> Hi,
>
> After using beta8 for several weeks, I tried unsuccessfully several times to
> build Maven from source. In the end, I discovered that if you have a
> ${user.home}/build.properties file, this must be deleted or temporarilly
> renamed before starting the bootstrap build.
No, it does not. I have a ~/build.properties file and I bootstrap all
the time.
> This crucial bit of info is
> missing from the docs at http://maven.apache.org/start/bootstrap.html. In my
> case, I had an overridden maven.repo.local property pointing to my beta8
> repo cache. This seemed to be the culprit that was causing the bootstrap
> builds to fail. In the end, it seems safest just to make sure that you do
> not have any $user.home/build.properties file before starting the build.
> Maybe someone can update the docs?
>
> --------------------------------------
> David Zeleznik
> ILOG - Changing the rules of business
> mailto:dzeleznik@ilog.com
> http://www.ilog.com
> --------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org