[MAGNOLIA-341] Magnolia SVN doesn't compile under Mac OS X without a little modification Created: 22/Apr/05 Updated: 26/Jul/05 Resolved: 26/Jul/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Ludovic Maître | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mac OS X only |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
As documented in the last url of this post, the Magnolia build file should not include a dependency versus tools.jar under Mac OS X. Actually, one must comment this dependency for Magnolia 2.1 to build without error under Mac OS X. This is very specific to the platform, so the simple fact that this is documented here should be enough to resolve the bug, and perhaps this is not easy to do under maven (AFAIK we cannot add dependency in a platform specific way under maven [and i understand that since Java is multiplatform by essence]). |
| Comments |
| Comment by Ludovic Maître [ 22/Apr/05 ] |
|
Sorry wrong url, missing "l" at the end: |
| Comment by Fabrizio Giustina [ 22/Apr/05 ] |
|
Hi Ludovic, which is the jar in MacOsX containing the javac classes?
I don't have a way to test a build with OSX, if you can look for the javac jar I can give you more instructions... |
| Comment by Stuart Piltch [ 22/Apr/05 ] |
|
The classes that are usually found in tools.jar on other platforms are found by javac on MacOS X without having to add a jar file to the classpath explicitly (they're already in the default classpath on jdk 1.4.1 and up). So, commenting out the tools.jar dependency in project.xml works fine (as Ludovic mentioned). I've had no problem with maven builds on MacOS X with that simply modification. For scripts that rely on a tools.jar and can't easily be rewritten to not have one, a workaround is to use classes.jar instead. case "`uname`" in TOOLS_JAR="${JAVA_HOME}/lib/tools.jar" This is what the maven startup script does: Of course the new MacOS X Tiger with JDK 5 is coming out next week, so this may all change. |
| Comment by Fabrizio Giustina [ 21/Jul/05 ] |
|
fixed by removing the tools.jar dependency at all. |
| Comment by Boris Kraft [ 26/Jul/05 ] |
|
reassigned to RC3 |