Maven modularized build only works on OS's that support symbolic links

[GoogleCodeExporter]

I think the multi-module layout is a needlessly complex if not outright bad 
idea.  That said, the current build mechanism for the multiple modules only 
works on OS's that support symbolic linking.  Fortunately there's another way 
to specify source includes and excludes in the compiler plugin in the POM.  
Attached is a patch file that allows one to drop the symbolic links and build 
the multiple modules on any environment

Original issue reported on code.google.com by jheric...@gmail.com on 12 Apr 2010 at 8:15

Attachments:

• patch.txt

[GoogleCodeExporter]

Original comment by kevinb@google.com on 27 Jan 2011 at 2:05

• Added labels: Type-Task

[GoogleCodeExporter]

Christian, any thoughts on this?

Original comment by fry@google.com on 28 Jul 2011 at 5:16

[GoogleCodeExporter]

Original comment by fry@google.com on 28 Jul 2011 at 5:17

• Changed state: Triaged

[GoogleCodeExporter]

Original comment by fry@google.com on 16 Feb 2012 at 7:17

• Changed state: Acknowledged

[GoogleCodeExporter]

Actually, we can close this, as we made a decision a long time ago to not do 
multiple modules (where we meant modules broken by major java pacakges, like 
collect, base, annotation, etc. )

At present, we have "guava" as a module, which is fine, and some additional 
modules but they don't use symbolic links.

Original comment by cgruber@google.com on 30 Mar 2012 at 3:58

[GoogleCodeExporter]

Original comment by cgruber@google.com on 30 Mar 2012 at 4:02

• Changed state: Obsolete

[GoogleCodeExporter]

This issue has been migrated to GitHub.

It can be found at https://github.com/google/guava/issues/<id>

Original comment by cgdecker@google.com on 1 Nov 2014 at 4:15

• Added labels: MigratedToGitHub

[GoogleCodeExporter]

Original comment by cgdecker@google.com on 3 Nov 2014 at 9:10

• Added labels: Restrict-AddIssueComment-Commit