>
>
> Herve Boutemy schrieb am 11.10.2023 00:27 (GMT +07:00):
>
> > I tried to build the project and see the failure, but could not
> > and reading explanations did not help me
> >
> > what we need is a basic commit that works, followed by a PR upgrading Doxia
r.de
Herve Boutemy schrieb am 11.10.2023 00:27 (GMT +07:00):
> I tried to build the project and see the failure, but could not
> and reading explanations did not help me
>
> what we need is a basic commit that works, followed by a PR upgrading Doxia
> and
> that does not
I tried to build the project and see the failure, but could not
and reading explanations did not help me
what we need is a basic commit that works, followed by a PR upgrading Doxia and
that does not work with the NPE that you are saying happens
Regards,
Hervé
On 2023/10/10 02:44:08 Alexander
Reverting back to my original question, also summarised in the subject
of this thread: Why is 'this.siteTool' null and not injected properly?
If I knew how to fix that configuratively or via coding, I would no
longer need to override 'exceute()', which relies on that field being
set, as you can see
Actually, my initial message already explained the situation:
1. With 1.x, I have no issues. That was my starting point.
2. With 2.0, I had no desire to verride 'execute()'. It was simply the
only thing that helped my project to function properly again. I
would be glad to do without
I had these NPEs when I started to migrate reporting plugins and both the
plugin and the super class contained the same fields which created conflicts.
After I have removed them from the plugin and used the super ones all went
fine. In your case I would really do what Hervé proposes:
* remove y
On 2023/10/05 06:46:02 Hervé Boutemy wrote:
> improvement proposed: review appreciated
> https://github.com/apache/maven-reporting-impl/pull/24
Will try to look at the issue here and the proposed PR in the next couple of
days...
---
de that can be
> run both as goal and a maven-site's report
>
> And if you want to see how it does the job, you can look at
> maven-reporting-impl AbstractMavenReport implementation of execute() [3]:
> yes, that implementation changed, and now I remember I had to update it
> be
plementation changed, and now I remember I had to update it because of
the NPE that it could cause. You must not rewrite this code.
HTH
Hervé
[1]
https://github.com/dev-aspectj/aspectj-maven-plugin/blob/main/src/main/java/org/codehaus/mojo/aspectj/AjcReportMojo.java#L210
[2]
https://git
Hello Hervé.
Did the reproducer help you in any way?
Regards
--
Alexander Kriegisch
https://scrum-master.de
Alexander Kriegisch schrieb am 23.09.2023 10:00 (GMT +07:00):
> Hello Hervé.
>
>>> I tried to upgrade those
>>> dependencies to the most recent Doxia and Sitetools versions.
>
>> by "
Hello Hervé.
>> I tried to upgrade those
>> dependencies to the most recent Doxia and Sitetools versions.
> by "most recent", do you mean most recent from 1.x or 2.0.0-M*?
I mean 2.0.0-M*. Actually, the project works nicely and I would have
ignored the Dependabot suggestions, but all those Maven
> I tried to upgrade those
> dependencies to the most recent Doxia and Sitetools versions.
by "most recent", do you mean most recent from 1.x or 2.0.0-M*?
1.x should not cause issues
2.0.0-M*, as expected from the version number, is more risky and not yet fully
stable
Such reporting plugin codin
Hello.
I was asking this question two weeks ago. Can somebody tell me if maybe I asked
on the wrong list or in the wrong way and possible direct me elsewhere?
Thank you all. Best regards
--
Alexander Kriegisch
https://scrum-master.de
Alexander Kriegisch schrieb am 07.09.2023 09:35 (GMT +07:00)
Hello Maven community.
In a Maven plugin using old 1.x Doxia and Sitetool versions, I am getting
warnings because those again use an EOL Plexus component. The details are not
so important, the important part is that I tried to upgrade those dependencies
to the most recent Doxia and Sitetools ve
While this may have been a rookie mistake and this pom is nonsensical, they
did manage to cause an NPE in a standard plugin.
That's a bug worth tracking down, right? Better validation, better error
messages?
ay, April 18, 2023 11:29 AM
> To: Maven Users List
> Subject: Re: [External] : Re: NPE Exception with Surefire3.0.0
>
> Hi
> Do you really need the dependencies section within the plugin section?
> just use
>
>
>
> org.apa
: NPE Exception with Surefire3.0.0
Hi
Do you really need the dependencies section within the plugin section?
just use
org.apache.maven.plugins
maven-surefire-plugin
3.0.0
On Tue, 18 Apr 2023
1.9.2
> runtime
>
>
>
>
>
>
>
> Thanks,
> Sirisha
>
> -Original Message-
> From: Benjamin Marwell
> Sent: Tuesday, April 18, 2023 11:16 AM
> To: Maven Users List
> Subject:
Message-
From: Benjamin Marwell
Sent: Tuesday, April 18, 2023 11:16 AM
To: Maven Users List
Subject: [External] : Re: NPE Exception with Surefire3.0.0
Which version of Maven are you using?
Can you give us a relevant snippet of your pom.xml to reproduce the issue?
On Mon, 17 Apr 2023, 17:07
Which version of Maven are you using?
Can you give us a relevant snippet of your pom.xml to reproduce the issue?
On Mon, 17 Apr 2023, 17:07 Sirisha Alla, wrote:
> Hi All,
>
> I am using surefire 3.0.0 with Junit 5 (Jupiter-engine). However, I am
> stumbling in to the Null Pointer Exception and
Hi All,
I am using surefire 3.0.0 with Junit 5 (Jupiter-engine). However, I am
stumbling in to the Null Pointer Exception and could not trace the issue. Has
anyone faced this issue or any pointers that can help me proceed? I am using
JDK1.8.
Caused by: java.lang.NullPointerException
at org
Here is my configuration. Note I had to add the one excludes because that
is the file that causes the NPE.
com/issinc/odin/display/*.class
com/issinc/odin/messaging/event/msg/EventActionMsgs_Action.class
${project.build.outputDirectory
-generator-maven-plugin has NPE fault
json-schema-generator-maven-plugin v1.3.0 generates and NPE. Just trying
to get feedback to developers.
[ERROR] Failed to execute goal io.gravitee.maven.plugins:
json-schema-generator-maven-plugin:1.3.0:generate-json-schemas
(json-schema-generator) on project
json-schema-generator-maven-plugin v1.3.0 generates and NPE. Just trying
to get feedback to developers.
[ERROR] Failed to execute goal io.gravitee.maven.plugins:
json-schema-generator-maven-plugin:1.3.0:generate-json-schemas
(json-schema-generator) on project odin-messaging: Execution
json
Hi all,
I've a issue with one of my mojo UT with JUnit4 (MojoRule )[1].
When my UT run, the MavenProject attribute is not initialized. But
bypassing this test and running my Mojo as a real plugin in a project work
fine.
Did someone have experimented a similar issue ?
Best regards
[1]
https://gi
And also I use spock framework, not TestNG
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805616.html
Sent from the Maven - Users mailing list archive at Nabble.com
Ok, sounds good.
anyway just in case here is me reproduce on github:
https://github.com/YaroslavTir/surefile-plugin-problem
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805615.html
Sent from the Maven - Users mailing list
2014 schrieb Martin Gainty :
>
>
> > Date: Thu, 18 Sep 2014 05:12:01 -0700
> > From: yaroslav...@gmail.com
> > To: users@maven.apache.org
> > Subject: Re: Maven sure fire plugin npe problem.
> >
> > Hi all,
> > I have the same problem. I also
> Date: Thu, 18 Sep 2014 05:12:01 -0700
> From: yaroslav...@gmail.com
> To: users@maven.apache.org
> Subject: Re: Maven sure fire plugin npe problem.
>
> Hi all,
> I have the same problem. I also revert surefire plugin to the 2.12 version
> and everything begin to work.
Hi all,
I have the same problem. I also revert surefire plugin to the 2.12 version
and everything begin to work. Does you found what was wrong? Do I need to
send my "non working" example?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-n
Hi Stephen,
Thanks for your info, your solution works for me :)
Br,
Tim
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: den 27 april 2014 11:41
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.
You signup for an account on
..@ericsson.com ]
> Sent: den 26 april 2014 22:53
> To: Maven Users List
> Subject: RE: Maven sure fire plugin npe problem.
>
> Hi,
>
> After detail investigation, I can prove this is a bug of maven surefire
> plugin, after version 2.12. That means from 2.12~2.17 it met
Not sure if anyone could show me how to create a TR for this, I don't have a
JIRA account.
Br,
Tim
-Original Message-
From: Tim Wu T [mailto:tim.t...@ericsson.com]
Sent: den 26 april 2014 22:53
To: Maven Users List
Subject: RE: Maven sure fire plugin npe problem.
Hi,
After d
,
Tim
-Original Message-
From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On
Behalf Of Kristian Rosenvold
Sent: den 25 april 2014 07:42
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.
It would appear that testng is not reporting the throwable that is cau
It would appear that testng is not reporting the throwable that is cause of
the failure. You might want to try a few different testNG versions to see
if this is a recently introduced regression.
Surefire should probably not NPE on this, but gaining some insight into the
root cause is probably a
Hi everyone,
I am not sure if some of you met this problem before, we have some smoke test
in Jenkins sever, which will run some test case through maven sure fire plugin,
version is 2.17
But it will always throw an exception like this:
java.lang.NullPointerException
at
org.apache.maven.su
/MPLUGIN-185
> Maybe you can try this one too
> http://mojo.codehaus.org/license-maven-plugin/
>
> 2013/4/11 David Hoffer :
> > I have a multi-module build I'm running the license:format goal on. It
> > works fine for several modules then fails with NPE on the
>
on. It
> works fine for several modules then fails with NPE on the deployment-parent
> module which is a pom type module (we have several like that), any ideas
> why it would fail on this one?
>
> I tried versions 1.9.0 and 1.10.b1 and get the same error.
>
> [ERROR] Failed to ex
I have a multi-module build I'm running the license:format goal on. It
works fine for several modules then fails with NPE on the deployment-parent
module which is a pom type module (we have several like that), any ideas
why it would fail on this one?
I tried versions 1.9.0 and 1.10.b1 an
wiki.apache.org/confluence/display/MAVEN/InternalErrorException
--
View this message in context:
http://maven.40175.n5.nabble.com/NPE-while-auto-wiring-values-in-a-mojo-tp5079535p5079535.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
I'd like to but I no longer have time so I'll provide all necessary data when
I have time.
Thanks a lot.
Jerome
--
View this message in context:
http://maven.40175.n5.nabble.com/NPE-executing-archetype-generate-tp4961022p4961665.html
Sent from the Maven - Users mailing list
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.1:generate (default-cli)
> on project standalone-pom: null: MojoFailureException: NullPointerException
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.mav
ute(CreateProjectFromArchetypeMojo.java:207)
... 21 more
Thanks!
--
View this message in context:
http://maven.40175.n5.nabble.com/NPE-executing-archetype-generate-tp4961022p4961254.html
Sent from the Maven - Users mailing list archive at Nabble.
> Yes, I changed the stack trace because I noticed that too. I re-run the test
> and I still have that NPE. The NPE has been there for long.
You are using Nabble which a lot of us dislike since it gives a
messageboard look to what is actually an email list. So you think you
can edit a pos
Yes, I changed the stack trace because I noticed that too. I re-run the test
and I still have that NPE. The NPE has been there for long.
Thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/NPE-executing-archetype-generate-tp4961022p4961108.html
Sent from the Maven - Users
hetype:generate goal. Everything seems fine while executing it until the
> end, which produces this NPE:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.1:generate (default-cli)
> on project standalone-pom: Directory my
> -new-portlet already e
Hi,
I've created an archetype and now I'm testing it by executing the
archetype:generate goal. Everything seems fine while executing it until the
end, which produces this NPE:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.1:generate (default-cli)
Please open an issue at http://jira.codehaus.org/browse/MSITE with a
reproducible test case.
Thanks,
-Lukas
On 08/22/2011 02:18 PM, Thomas Scheffler wrote:
Hi,
after updating to version 3.0 of maven-site-plugin I get a
NullPointerException that does not occur with 3.0-beta3. How can I
figur
Hi,
after updating to version 3.0 of maven-site-plugin I get a
NullPointerException that does not occur with 3.0-beta3. How can I
figure out, what causes that? There is not clear error message so I
guess it's a bug...
Here is the last part of the log:
[DEBUG] Multipage report: 0 subreports
[
> A work around is to install the artifact by hand.
>
> But what is the solution to connect to a maven 1 repo?
Install an MRM like Nexus, Artifactory, Archiva and these problems
magically go away...
Wayne
-
To unsubscribe, e-mai
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-LegacystyleRepositories
-Robert
> From: jpye...@pdinc.us
> To: users@maven.apache.org
> Subject: RE: [maven] Troubleshooting a NPE in maven bui
> -Original Message-
> From: Jason Pyeron
> Sent: Wednesday, August 17, 2011 15:00
> To: 'Maven Users List'
> Subject: RE: [maven] Troubleshooting a NPE in maven build
>
> > >
> > > When I add
> > >
> -Original Message-
> From: Jason Pyeron
> Sent: Wednesday, August 17, 2011 14:49
> To: 'Maven Users List'
> Subject: RE: [maven] Troubleshooting a NPE in maven build
>
>
> > -Original Message-
> > From: Jason Pyeron
> > Sent
When I add
org.springframework.ws
spring-ws-security
2.0.2.RELEASE
I get a NPE (see attached log) if I comment it out it builds fine.
Where to start on this
Thanks Hervé,
I'll provide you a sample project on a jira ticket asap.
Maxime
-Original Message-
From: Hervé BOUTEMY [mailto:herve.bout...@free.fr]
Sent: Saturday,April 02,2011 2:26 AM
To: Maven Users List
Subject: Re: NPE when trying to install an archetype
I lloked at the so
I lloked at the sources: it seems you're including non-existent source
directory files.
Please open a Jira issue [1] with a sample project as attachement, and I'll fix
the plugin to give a better error message on such case.
Note in your pom.xml that specifying a version for archetype plugin and
I wonder if my mail was sent on the mailing list so I send it again, sorry if
you already receive this mail.
Hi all,
I'd like to make my own artifact/archetype and I'm facing an issue when trying
to install it, precisely when it tries to make the jar file.
Here is the output :
C:\HOMEWARE\Max
Hi all,
I'd like to make my own artifact/archetype and I'm facing an issue when trying
to install it, precisely when it tries to make the jar file.
Here is the output :
C:\HOMEWARE\Maxime\myartifact >mvn install
[INFO] Scanning for projects...
[INFO]
Hi All,
I'm trying to use maven archetypes programmatically to create a maven
project.
While I'm looking at the source code of the class *DefaultArchetypeManager*of
*archetype-common-2.0.jar*, I see possible NPEs from the
*generateProjectFromArchetype
*method and *createArchetypeFromProject *meth
t;forkMode" to "never", I don't get the error any more but several of my
tests fail because they require their own process.
Let me know if anyone has any other ideas.
--
View this message in context:
http://maven.40175.n5.nabble.com/Surefire-NPE-tp3246444p3258956.html
Sent from
Blind guess: maybe ${resource-bundle-path} is being set to a different value
when the user runs it?
On Mon, Nov 1, 2010 at 11:55 AM, Hinkle, Cameron wrote:
> Greetings,
>
> I've been using Maven and Surefire on a project for about a year now and
> have sporadically seen a problem that I've always
Greetings,
I've been using Maven and Surefire on a project for about a year now and have
sporadically seen a problem that I've always been able to get around but want
to get to the bottom of. It's a null pointer exception sometimes when I run
"mvn" and it tries to run all our tests. It happen
After disabling generation of 'Use' pages, javadoc works fine for my
project.
I removed '-use' from options file that mavan/javadoc plugin generated
and javadoc didn't throw NPE.
Setting 'use' to 'false' in maven-javadoc-plugin also works fi
Original Message-
From: Martin Gainty [mailto:mgai...@hotmail.com]
Sent: Thursday, May 20, 2010 7:21 PM
To: users@maven.apache.org
Subject: RE: javadoc throws NPE
Denis-
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
can you provide us the configuration
, ezért minket semmi felelöség nem terhelhet ezen üzenet
tartalma miatt.
> Subject: javadoc throws NPE
> Date: Thu, 20 May 2010 18:10:57 +0200
> From: denis.kranj...@srce.hr
> To: users@maven.apache.org
>
> I am trying to generate javadoc for a project but javadoc throws
I am trying to generate javadoc for a project but javadoc throws NPE
without any information.
Maven output:
Generating
C:/ci/svn/project/project-name/trunk/target/site/apidocs\package-use.htm
l...
Generating C:/ci/svn/project/project-name
/trunk/target/site/apidocs\mypackage/\package-use.ht
ml
I finally got my plugin to compile and when I try to run it on a test
project I get this NPE dump. Notice that none of this code is generated
by me. But is all part of the code that is parsing components.xml (I
think). After the dump I am including the relevant part of my
component.xml
see in the source code of DefaultMavenProjectBuilder.java, the
private member
private ArtifactRepositoryFactory artifactRepositoryFactory;
is never initialized. Hence resulting in the above mentioned NPE.
Can anyone point me how to resolve this issue?
I am using the Maven2 plugin of Torque pr
btw,
i also opend a jira issue for this:
http://jira.codehaus.org/browse/DOXIASITETOOLS-16
On Mon, Feb 16, 2009 at 10:44 AM, Valerio Schiavoni <
valerio.schiav...@gmail.com> wrote:
> After a succesfull mvn release:prepare, i tried the next step (mvn
> release:perform), and I got this stacktrace:
After a succesfull mvn release:prepare, i tried the next step (mvn
release:perform), and I got this stacktrace:
INFO] [ERROR] FATAL ERROR
[INFO] [INFO]
[INFO] [INFO] null
[INFO] [INFO]
--
When I run eclipse:eclipse on my multi-projece maven directory
structure, I get this error message. Does anybody know what the problem
might be?
C:\slbr\logging>mvn eclipse:eclipse
[INFO] Scanning for projects...
[WARNING] Overriding profile: 'os-specific-settings' (source: pom) with
new inst
that extend BaseEJB the site-plugin fails
with an NPE:
[WARNING] Unable to load parent project from repository: Failed to validate
POM for project com.acme.product:BaseEJB at Artifact [com.acme.product:Bas
eEJB:pom:1.0-SNAPSHOT]
[DEBUG] Parent project loaded ...
[DEBUG] BaseEJB: using lo
On Wed, Sep 17, 2008 at 2:08 PM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> units tests and integration tests passed on my laptop (mac os x)
> I'll do more checks on existing projects at work (for my personal devs I'm
> more often using m2eclipse)
That's probably enough.
Appreciate the check.
-
units tests and integration tests passed on my laptop (mac os x)
I'll do more checks on existing projects at work (for my personal devs I'm
more often using m2eclipse)
cheers
arnaud
On Wed, Sep 17, 2008 at 4:18 AM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 17, 2008 at 9:08 AM, Ar
On Wed, Sep 17, 2008 at 9:08 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> perfect
> thx
I'd feel happier if you could check it works in your envionment.
I've build and tested on my windows xp box and on minotaur, but since
I'm just tinkering around the edges I'm not confident I haven't
stuffed
perfect
thx
On Wed, Sep 17, 2008 at 1:07 AM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> > Then this jar will be included in the project without any problem. I
> really
> > think it's better.
> > And obviously, I'll be happy to manually test the new version once the
> > modification is applied.
>
> Then this jar will be included in the project without any problem. I really
> think it's better.
> And obviously, I'll be happy to manually test the new version once the
> modification is applied.
Fixed, with unit test as well.
I just created a zip file with no manifest and renamed to jar.
2008/9/16 Barrie Treloar <[EMAIL PROTECTED]>
> On Tue, Sep 16, 2008 at 5:45 PM, Arnaud HERITIER <[EMAIL PROTECTED]>
> wrote:
> > I don't think we are using a mocking framework like easy mock but you can
> > propose
>
I had a look in InstallPluginsMojoTest and there seems to be some
org.easymock.M
Thanks Vikramaditya, I have got this issue resolved.
Regards,
Mukta Jindal
-Original Message-
From: Vikramaditya Garg [mailto:[EMAIL PROTECTED]
Sent: 04 June 2008 16:15
To: Maven Users List
Subject: RE: Need help | Getting NPE while using "mvn install"
Please specify which
:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2008 1:30 PM
To: 'Maven Users List'
Subject: RE: Need help | Getting NPE while using "mvn install"
Everyone gets [deploy:deploy] message for the first project only.
For rest, only [install:install] is there and the jars are uploaded in
From: JINDAL, Mukta, IDC
Sent: 04 June 2008 13:22
To: 'Maven Users List'
Subject: RE: Need help | Getting NPE while using "mvn install"
>> But 'mvn install' should only install the project's artifact in your local
>> repository (~/.m2/repository/...) and no
JINDAL, Mukta, IDC schrieb:
But 'mvn install' should only install the project's artifact in your local repository
(~/.m2/repository/...) and not try to deploy it to a remote repo. >> Or have
you configured the deploy plugin in yor pom to run in the install phase, which IMHO
would be a bad prac
: Maven Users List
Subject: Re: Need help | Getting NPE while using "mvn install"
JINDAL, Mukta, IDC schrieb:
> I am using the same POM from SVN as my other team members.
> All of them are able to do "mvn install" with the same settings as mine.
> Thats why I'm more co
>> But 'mvn install' should only install the project's artifact in your local
>> repository (~/.m2/repository/...) and not try to deploy it to a remote repo.
>> >> Or have you configured the deploy plugin in yor pom to run in the install
>> phase, which IMHO would be a bad practice?
How can I
JINDAL, Mukta, IDC schrieb:
> I am using the same POM from SVN as my other team members.
> All of them are able to do "mvn install" with the same settings as mine.
> Thats why I'm more concerned...
>
Are they getting the deploy message? If so, then their config is also
stuffed up, but they have
e 2008 13:03
To: Maven Users List
Subject: Re: Need help | Getting NPE while using "mvn install"
JINDAL, Mukta, IDC schrieb:
> Thanks for the reply, Tim.
>
> I am executing "mvn install", not "mvn deploy".
>
> Al
JINDAL, Mukta, IDC schrieb:
Thanks for the reply, Tim.
I am executing "mvn install", not "mvn deploy".
But 'mvn install' should only install the project's artifact in your
local repository (~/.m2/repository/...) and not try to deploy it to a
remote repo. Or have you configured the deploy plu
JINDAL, Mukta, IDC schrieb:
> Thanks for the reply, Tim.
>
> I am executing "mvn install", not "mvn deploy".
>
> Also, I tried using scpext, but got following error:
>
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
indal
-Original Message-
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: 04 June 2008 12:16
To: Maven Users List
Subject: Re: Need help | Getting NPE while using "mvn install"
JINDAL, Mukta, IDC schrieb:
> Hi All,
Hi,
>
> I am getting following error while using &quo
JINDAL, Mukta, IDC schrieb:
Hi All,
Hi,
I am getting following error while using "mvn install" though "mvn package" is
working fine.
Judging from the stacktrace below you ran 'mvn deploy', not 'mvn
install' (see the reference to the deploy mojo). As the deploy phase is
executed after th
Hi All,
I am getting following error while using "mvn install" though "mvn package" is
working fine.
I did entire cleanup, restarted machine too.
What could be the possible reasons ?
[INFO]
[ERROR] FATAL ERROR
[INFO] ---
.
Matthew
>
> From the reported line number it must be a problem with some macro in
> an xdoc file. Can you try to track it down and attach a reproducible
> test case to jira?
>
> Thanks,
> -Lukas
>
>
> Matthew Pocock wrote:
>> Hi,
>>
>> When bui
ext:
http://www.nabble.com/NPE-on-dependecies-resolution-tp14514407s177p14514407.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
tests.
William
-Original Message-
From: sudhakar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30 October 2007 9:00 AM
To: users@maven.apache.org
Subject: [***POSSIBLE SPAM***] - NPE all of a sudden - Bayesian Filter
detected spam
All of a sudden my maven (version 2.0.6) stopped working. I'm g
Hi Jon,
You should remove the -Dmojo=describe from the command you're executing
or rather, replace 'describe' with the appropriate goal of the
dashboard-maven-plugin. The 'mojo' parameter is used to specify the goal
or the mojo of the plugin you want to describe (in this case, its the
dashboa
Would this indicate a problem with the dashboard-name-plugin?
Here is the command line:
mvn help:describe -Dmojo=describe
-DgroupId=org.codehaus.mojo-DartifactId=dashboard-maven-plugin
-Dfull=true -Dversion=
1.0-SNAPSHOT
Here is the stack trace:
java.lang.NullPointerException
at org.apach
wrote:
I am using continuum and mail notification does not work. I have a NPE
during mail sending. Can anyone help me?
Thanks
INFO | jvm 1| 2007/05/11 15:24:05 | 2007-05-11 15:24:05,344
[Thread-2] INFO ContinuumBuildExecutor:maven2 - Exit code: 0
INFO | jvm 1| 2007/05/11 15:24:05 | 2
hi,
I am using continuum and mail notification does not work. I have a NPE
during mail sending. Can anyone help me?
Thanks
INFO | jvm 1| 2007/05/11 15:24:05 | 2007-05-11 15:24:05,344
[Thread-2] INFO ContinuumBuildExecutor:maven2 - Exit code: 0
INFO | jvm 1| 2007/05/11 15:24:05
rlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
On 2007-01-03, Tom Huybrechts wrote:
> Hi folks,
>
> I'm getting aNPE when generating a site for a plugin. It looks like
> the java mojos get processed OK, but when it looks for bsh mojos
re
was being used. Which version should be used with 2.0.6?
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 01, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven-2.0.6 throws NPE in surefire
It is version 2.3 and the same version was used in both maven
1 - 100 of 178 matches
Mail list logo
