maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Feys (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-185) bug with dependencyManagement section in a parent pom
Date Fri, 20 Oct 2006 07:24:21 GMT
    [ ] 
Luc Feys commented on MNGECLIPSE-185:

I experience the same problem described here. I have the following project structure (see

* master (pom only)
* budget (pom only, parent=master)
   - budget-conv (eclipse project, parent=budget)
   - budget-db (eclipse project, parent=budget)
   - budget-gui (eclipse project, parent=budget)

All modules will depend on budget-db, so I added dependency management for it in budget pom.
I have defined a maven 'm2 build' for each module (with a single goal 'install') using external
tools in eclipse, but with the addition to dependency management of budget-db, I get the above
error if I build budget-db. All other modules build fine.

If I remove the dependency management on 'budget-db' then I can build 'budget-db'. If I build
using maven from the command prompt, then budget-db builds fine, even with the dependency
management section.

I hope this was a bit clear.

> bug with dependencyManagement section in a parent pom
> -----------------------------------------------------
>                 Key: MNGECLIPSE-185
>                 URL:
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.9
>         Environment: maven 2.0.4 on Windows with eclipse 3.1
>            Reporter: Nicolas Cazottes
>         Assigned To: Eugene Kuleshov
>         Attachments:
> I have also an issue related to dependencyManagement section in parent pom with m2eclipse
plugin on windows.
> I have attached the projects that show the problem : when a project (projectD in my example)
is defined with a dependencyManagement section in the parent pom in order to allow other projects
to define its version (projectC in my example), the build in eclipse with a clean on the project
(calling the install goal) fails when creating the jar.
> The trace is the following : 
> org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling JAR
>         ...
> 	... 8 more
> Caused by: java.lang.NullPointerException
> 	at org.apache.maven.artifact.ArtifactUtils.copyArtifact(
>         ...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message