This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 201936 - Source level settings not inherited into child poms in maven project
Summary: Source level settings not inherited into child poms in maven project
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.0.1
Hardware: Macintosh (x86) Mac OS X
: P3 normal with 1 vote (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-10 22:38 UTC by huima
Modified: 2011-10-12 21:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample project set (2.49 KB, application/zip)
2011-10-12 21:49 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description huima 2011-09-10 22:38:26 UTC
In Jboss's GateIn portal project there is source level set up in root pom and different modules and projects use that as a parent.

Source level setting of:

 <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>2.3.2</version>
            <configuration>
               <source>1.6</source>
               <target>1.6</target>
            </configuration>
</plugin>

Is not inherited in Netbeans IDE settings, which means that IDE thinks that projects have source level of 1.3 - forcing the user to manually update the source/binary flag to 1.6 in every project.

SHould be able to replicate in a simple example project.
Comment 1 Jesse Glick 2011-10-12 21:49:14 UTC
Created attachment 111954 [details]
Sample project set
Comment 2 Jesse Glick 2011-10-12 21:51:45 UTC
Working fine for me in a 7.1 dev build. "Source/Target Level" in the GUI of the child module displays the setting inherited from the parent POM, command-line builds work, editor uses appropriate source level. If you have a project which does not appear to be working correctly, please provide details to reproduce.