Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [iam-dev] Question about the builder and a workspace with projects with nested modules

MavenProjectManager.getMavenProject will return null if project is in
error, so yes, you need to check that case


On Wed, Jun 10, 2009 at 1:19 AM, kcordero<kcordero@xxxxxxxx> wrote:
> Hi,
>
> I'm currently looking at 265956 - Exception on incremental builder if the
> pom contains errors.  In my workspace, I have archiva (nested modules at
> more than one level) and a completely separate simple Java project.  I get
> the error when I add a non-existent dependency in the POM in the simple
> Java project.  It fails at this line in BuilderUtil, method
> getChildProjects.
>
> EqualsBuilder eb =
>       new EqualsBuilder().append( mavenProject.getGroupId(),
> parent.getGroupId() ).append( mavenProject.getArtifactId(),
>                parent.getArtifactId() ).append( mavenProject.getVersion(),
> parent.getVersion() );
>
> When the error occurs, mavenProject is null, when it's supposed to contain
> the simple Java project.
>
> I was wondering, should mavenProject ever be null?  If mavenProject can be
> null, do we proceed with the rest of the build or stop the build at that
> point?
>
> thanks,
> Korina
> _______________________________________________
> iam-dev mailing list
> iam-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/iam-dev
>


Back to the top