Build failed using Maven
Closed this issue · 5 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1.Open project with Netbeans 6.8 or 6.9rc2 as Maven project
2.select the project
3.Issue command clean install
Used a console as well trying to build.
What is the expected output? What do you see instead?
Expected for the build to finish successfully. Instead, i get
[ERROR]COMPILATION ERROR :
details attached.
What version of the product are you using? On what operating system? What
JRE version?
Using latest trunk version of seaglass.
Using Windows 7 32bit
Java: 1.6.0_18; Java HotSpot(TM) Client VM 16.0-b13
Maven 2.2.1 or Maven 3
Please provide any additional information below.
Tried the build with command line only and have exactly the same result.
I attached the build process. The warning are okay, but there are errors about
classes that are not available. However I have checked the JDK and they are
there. So have no idea why they are not visible during a maven build.
Original issue reported on code.google.com by Martin.Jozef@gmail.com on 12 Jun 2010 at 12:56
Attachments:
GoogleCodeExporter commented
Fixed in new Trunk.
Original comment by kahuxtable on 12 Jun 2010 at 1:13
- Changed state: Fixed
GoogleCodeExporter commented
I found the source of the problem. It turns out that, when building your
project with pure maven on console only, it will not compile since you rely on
JDK dependency. By default maven discourages us from using JDK specific API.
While your project worked in Eclipse with maven plugin, it does not work
outside of this environment. However this can be fixed sealy. It's a small
enhancement to the pom.xml. Just add
<compilerArguments>
<bootclasspath>${java.home}\lib\rt.jar</bootclasspath>
</compilerArguments>
to <configuration> tag in your maven-compiler-plugin. I have attached a patch.
Then it compiles and creates the jar without any problem.
Original comment by Martin.Jozef@gmail.com on 14 Jun 2010 at 2:51
Attachments:
GoogleCodeExporter commented
Interesting. Apple has a different structure for their class libraries. It
works fine from the command line on my Mac. I'll look further into this.
Original comment by kahuxtable on 14 Jun 2010 at 5:32
- Changed state: Started
GoogleCodeExporter commented
Okay, I added a profile for mac that specifies its rt (classes.jar) which is in
a different location and actually not needed. I then specified
${java.home}/lib/rt.jar for everything else. Why must Windows users use
backslashes for directories in Java, when it's platform independent and Windows
is the only system in the world that uses backslashes for directories. (A
terrible idea.)
Original comment by kahuxtable on 14 Jun 2010 at 6:53
GoogleCodeExporter commented
This issue was closed by revision r1532.
Original comment by kahuxtable on 14 Jun 2010 at 6:56
- Changed state: Fixed