[
https://jira.duraspace.org/browse/DS-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22134#comment-22134
]
Tim Donohue commented on DS-881:
--------------------------------
So, just an observation (not sure if this is helpful or not, but it's something
I just realized a moment ago):
Currently in trunk (r6597), 'mvn package' does the following depending on where
you run it.
1. From [dspace-src] (root folder), 'mvn package' will build everything based
on latest installed versions in maven (i.e. it doesn't compile all the source
code, but just builds the overlays & packages up everything into
[dspace-src]/dspace/target/ as normal). So, this is a "quick build" using
pre-compiled artifacts.
2. From [dspace-src]/dspace/ (assembly folder), 'mvn package' will compile
everything from source, then build overlays & packages up everything into
[dspace-src]/dspace/target/ as normal. This is a "full build" that takes a
while to run, as everything is compiled, etc.
I just wanted to mention this. I realize why this happens, as Mark needed to
remove many of the <module> definitions from [dspace-src]/pom.xml (so that root
folder no longer references all its subfolders).
But, in a way (and taking a step back from what we've always done in the past),
it does seem slightly backwards (as Graham seems to be saying, if I understand
him correctly). I can see the point that one may expect option #1 to compile
*all the source* (as it's being run from the root folder), and expect option #2
would just be a *quick build* of pre-compiled artifacts (as it's run from a
subfolder).
Obviously, this idea does go against everything we've always done in the past
(since DSpace 1.5.x). Admittedly, I'm still a bit undecided here (as making
this sort of change would require re-educating the community on
building/compiling/customizing DSpace). But, I did want to make this
observation, in case others hadn't noticed this current behavior.
> DSpace doesn't build properly with Maven 3
> ------------------------------------------
>
> Key: DS-881
> URL: https://jira.duraspace.org/browse/DS-881
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.7.0, 1.7.1
> Reporter: Tim Donohue
> Assignee: Mark Diggory
> Fix For: 1.8.0
>
>
> DSpace currently has issues building with Maven 3.x
> This has been noted in the DSpace Documentation at:
> https://wiki.duraspace.org/display/DSDOC/Installation#Installation-ApacheMaven2.2.x%28Javabuildtool%29
> However, during the Developers Meeting on April 20, 2011, the DSpace
> Developers decided that we should resolve these Maven 3 issues for the DSpace
> 1.8.0 release.
> More information about Maven 3 issues is available in this email thread from
> dspace-devel:
> http://www.mail-archive.com/[email protected]/msg05222.html
> A similar thread about Maven 3 issues also appeared on dspace-tech:
> http://www.mail-archive.com/[email protected]/msg13610.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
