Apache Directory Project - Maven build failure

Author

Maven build failure

Norbet Reilly

2006-04-27, 6:46 am

I've started getting the following exception every time I do a "mvn
install" (or "mvn assembly:assembly") in any directory, in a dev
directory which has previously been working.

After the initial failure I tried a full "svn up" and tried to rebuild
but get the same failure.

Is anyone else seeing this, or have any suggestions about what I should do =
next?

I'm running with JDK 1.4.2_11 and Maven 2.0.2.

Thanks

[INFO] --------------------------------------------------------------------=
-----
---
[INFO] Building Apache MINA Core API
[INFO] task-segment: [install]
[INFO] --------------------------------------------------------------------=
-----
---
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D

[echo] W A R N I N G
[echo] -------------
[echo]
[echo] Build with 1.4 jvm will not include modules:
[echo]
[echo] o mina-filter-ssl
[echo] o mina-integration-spring
[echo] o mina-examples
[echo]
[echo] Use JDK 1.5 to make sure these modules build.
[echo] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D

[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] --------------------------------------------------------------------=
-----
---
[ERROR] FATAL ERROR
[INFO] --------------------------------------------------------------------=
-----
---
[INFO] null
[INFO] --------------------------------------------------------------------=
-----
---
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.project.injection.DefaultProfileInjector.inject=
Plugi
ns(DefaultProfileInjector.java:147)
at org.apache.maven.project.injection.DefaultProfileInjector.inject=
Build
(DefaultProfileInjector.java:134)
at org.apache.maven.project.injection.DefaultProfileInjector.inject=
(Defa
ultProfileInjector.java:80)
at org.apache.maven.project.DefaultMavenProjectBuilder.injectActive=
Profi
les(DefaultMavenProjectBuilder.java:1035)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLine=
age(D
efaultMavenProjectBuilder.java:836)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLine=
age(D
efaultMavenProjectBuilder.java:1000)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(Defaul=
tMave
nProjectBuilder.java:593)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRep=
osito
ry(DefaultMavenProjectBuilder.java:353)
at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(M=
avenM
etadataSource.java:102)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recu=
rse(D
efaultArtifactCollector.java:282)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector.coll=
ect(D
efaultArtifactCollector.java:67)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resol=
veTra
nsitively(DefaultArtifactResolver.java:223)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resol=
veTra
nsitively(DefaultArtifactResolver.java:211)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resol=
veTra
nsitively(DefaultArtifactResolver.java:182)
at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContain=
erIsC
omplete(DefaultPluginManager.java:611)
at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(D=
efaul
tPluginManager.java:522)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(Default=
Plugi
nManager.java:393)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals=
(Defa
ultLifecycleExecutor.java:531)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalW=
ithLi
fecycle(DefaultLifecycleExecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(=
Defau
ltLifecycleExecutor.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalA=
ndHan
dleFailures(DefaultLifecycleExecutor.java:303)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskS=
egmen
ts(DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Defa=
ultLi
fecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor=
Impl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod=
Acces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:3=
15)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java=
:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] --------------------------------------------------------------------=
-----
---
[INFO] Total time: 1 minute 33 seconds
[INFO] Finished at: Thu Apr 27 17:42:18 EST 2006
[INFO] Final Memory: 7M/14M
[INFO] --------------------------------------------------------------------=
-----
---

Stefan Zoerner

2006-04-27, 6:46 am

> After the initial failure I tried a full "svn up" and tried to rebuild
but get the same failure.
> Is anyone else seeing this, or have any suggestions about what I should
do next?
> I'm running with JDK 1.4.2_11 and Maven 2.0.2.

Hi Norbet!

I had comparable problems last week. After changing to Maven 2.0.4 they
disappeared, but I don not know whether it is common/recommended to use
this mvn version here.
Greetings from Hamburg,
Stefan

---

SPEAKER @ JAX 2006
Conference on Java, XML, Web Services
May 8-12, 2006
Rhein-Main-Hallen Wiesbaden
www.jax.de

Norbet Reilly

2006-04-28, 1:11 am

Thanks, that fixed my problem ... but also raised my level of concern
about a build tool that auto-updates to plugins that apparently aren't
compatible with their host executable.

I like the shared repository idea in Maven2 but have to admit to being
bamboozled by various plug-in issues, especially as they are "pushed"
on you every time you build, rather then at a time when you feel like
taking a risk.

Perhaps if I understood how it worked better I could find some config
changes that would support a safer "pull" model.

....enough rambling...

thanks again

Emmanuel Lecharny

2006-04-28, 1:11 am

Norbet Reilly a écrit :
Hi Norbet,

>Thanks, that fixed my problem ... but also raised my level of concern
>about a build tool that auto-updates to plugins that apparently aren't
>compatible with their host executable.
>
>I like the shared repository idea in Maven2 but have to admit to being
>bamboozled by various plug-in issues, especially as they are "pushed"
>on you every time you build, rather then at a time when you feel like
>taking a risk.
>
>Perhaps if I understood how it worked better I could find some config
>changes that would support a safer "pull" model.
>
>...enough rambling...
>
>
Well, M2 was a great move in the right direction (because M1 was really
difficult to manage and was slow). I admit that this road could seem
bumpy - and, yes, it's uncomfortable - but I like to think that in a few
months (weeks ?) those problems will be just bad memories.

I don't like either to upgrade a version (2.0.3 in my case) just because
a plugin has problem, but look : since we migrated to M2, back in
december as far as I remember, this was the first time we had serious
issue with it, and it was fixed quickly. The error was that we didn't
pushed a mail "***WARNING*** M2 -> upgrade to 2.0.3/4". That was the
mistake. Our fault...

However, we are still in the process of fixing bugs, adding code,
closing the 1.0 version, and it's not easy to keep an eye on every
little moving part. I'm understand those "Ant is the best", or "Maven
sucks", or whatever <rant/>, but, let me tell you : writing ant scripts
in place of Maven will cost us a hell *lot* of energy, and as far as I
can see using it on a daily basis, Maven 2 is doing the job right now.
And it does it well. Those guy at Maven have done a tremendous work to
improve it, and they will for sure improve it continuously in the next
months, and, hopefully, years.

Trust me, I understand your concern more than you can think, but I also
think that M2 only need few things to become a tool you like working
with. It's like a wild horse : M1 was really wild, and M2 is the same
horse with a saddle on it : we can have a ride with it, and may be enjoy
it, even if from time to time it can throw you to the ground.

Last thing, here is a book you can download :
http://www.mergere.com/m2book_download.jsp It has been released three
days ago. It can help.

Hope it helps ;)

Emmanuel Lécharny

Norbet Reilly

2006-04-28, 1:11 pm

Hi Emmanuel,

Thanks for your insights. I certainly wouldn't count myself in the
"ant rules" camp by any means, and agree M2 is streets ahead of M1. I
like a lot of what M2 provides, but have this nagging concern about
it's "push" nature as I mentioned in my previous posting.

It seems to me that while you aren't in explicit control of when
things are updated you are being asked to be very trusting indeed, not
withstanding that people are taking every precaution not to break
things. Using an admittedly loose analogy it seems to me sort of like
what would happen if Subversion asynchronously updated your source
code without you making an explicit decision that it was a convenient
time to do an "svn up".

Anyway I'm no maven power-user by any means, so I'm talking from a
position of ignorance and very limitted experience... and I know this
thread is off topic anyway so I'll say no more... Let me say finally
I'm not meaning to insult the ApacheDS or M2 crews in any way, but was
just thinking out loud so to speak.

Thanks for the link to the book as well!