[
https://jira.duraspace.org/browse/DS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue resolved DS-788.
----------------------------
Resolution: Fixed
Fix Version/s: (was: 1.8.0)
1.7.1
This issue was discussed in the DSpace Developers Meeting on April 20, 2011:
It was decided that we'll close this issue, as the developers all agree we
should just require Maven 2.2 or above. However, we will be opening up a
separate JIRA issue around Maven 3 issues, as we need to resolve problems with
building DSpace using Maven 3.
Full discussion:
[20:09] <tdonohue> DSpace 1.7.0 only builds properly for Maven 2.2.0 or above :
DS-788
[20:09] <stuartlewis> But not, IIRC, 3.0+ ?
[20:09] <stuartlewis> So currently only 2.2.x?
[20:09] <tdonohue> Right -- actually that is the case, I think there are some
issues with Maven 3 as well
[20:10] <mhwood> 2.2 minimum is documented for the reported version.
[20:10] <tdonohue> so, currently we are supporting a very minimal range of
2.2.x only
[20:10] <stuartlewis> I think I updated the doco recently to mention not 3.
[20:10] <richardrodgers> I believe this was an issue for some one who wanted a
strict Debian dist that hadn't got there
[20:10] <stuartlewis> Yep:
https://wiki.duraspace.org/display/DSDOC/Installation#Installation-ApacheMaven2.2.x%28Javabuildtool%29
[20:10] <stuartlewis> Known issue with Maven 2.0.x and Maven 3.x and DSpace
1.7.0
[20:10] <stuartlewis> DSpace 1.7.0 does not build properly when using Maven
2.0.x or Maven 3.x. This is a known issue. The quick fix is to use Maven 2.2.x.
More information on this issue can be found in the following JIRA issue: DS-788.
[20:11] <mdiggory> Yes, currently only 2.2.x
[20:11] <stuartlewis> Apple Mac's now default to 3.0 out the box, so support
for 3 would be great
[20:11] <mdiggory> We need to clean up a few poms
[20:11] <tdonohue> Right. I guess my questions are: (1) Are we all OK with
requiring 2.2.x or above. (2) Is someone working on fixes to Maven 3, so that
it will work?
[20:12] <mdiggory> I expect we should do 3.0 for DSpace 1.8.0
[20:12] <mdiggory> grahamtriggs has captured the requirements already
[20:12] <tdonohue> Any volunteers for 3.0 support?
[20:12] <richardrodgers> I'm OK - with limited resources we should look at 3.0
over 2.0x issues
[20:12] <mdiggory> some "module" inclusion conventions changed
[20:13] <tdonohue> OK. I recommend we close DS-788, and then create a new issue
around Maven 3.0 issues (and find a volunteer to tackle in time for 1.8.0)
[20:13] <mdiggory> we know what the issue is, but the solution is dependent on
decisions we make about where and how we will manage dspace modules and the
dspace-parent pom
[20:14] <mdiggory> the problem is that dspace-parent and dspace poms duplicate
the includion of dspace-xxxx modules
[20:14] <mdiggory> and that doesn't work in 3.0
[20:15] <tdonohue> Ok. makes sense. don't want to dig into this too deeply now.
mdiggory or grahamtriggs would one of you be willing to create a new ticket
around 3.0 issues and schedule for 1.8.0?
[20:15] <grahamtriggs1> as we essentially know what needs to be done for 3.0
(and it does work with a few minor modifications to the poms), I would suggest
assigning to Robin (as release co-ordinator), just as it needs someone to
ensure that it's followed up for 1.8
[20:15] <mdiggory> an interim solution may be to disable the "all" profile when
building dspace.pom
[20:15] <mdiggory> and visavi
[20:16] <tdonohue> I'm gonna move on, in essence of time. I'll create a ticket
placeholder for 3.0 then (if no one else beats me to it) and close DS-788
> DSpace 1.7.0 only builds properly for Maven 2.2.0 or above
> ----------------------------------------------------------
>
> Key: DS-788
> URL: https://jira.duraspace.org/browse/DS-788
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.7.0
> Reporter: Tim Donohue
> Fix For: 1.7.1
>
>
> From an email thread on dspace-tech mailing list:
> http://www.mail-archive.com/[email protected]/msg12821.html
> For Maven 2.0.x versions, DSpace 1.7.0 doesn't build 100% properly. Although
> no errors occur during a Maven build, the following directory is not created
> properly:
> [dspace-src]/dspace/target/dspace-1.7.0-build/webapps/
> Rather than seeing a separate folder for each webapplication, all webapp
> files are jumbled together in the top level folder. The problem seems to be
> that the maven-war-plugin is not copying the webapps properly to that folder.
> There are two know "quick fixes" to this issue:
> (1) Install Maven 2.2.x -- it works properly
> OR
> (2) Manually copy the webapps from their
> [dspace-src]/dspace/modules/[webapp-name]/target/ directory. So, for
> example, the XMLUI webapp is built properly to the path:
> [dspace-src]/dspace/modules/xmlui/target/xmlui-1.7.0/ If you manually copy
> the webapp to the proper location, everything should work fine.
> For the time being, this is a "known issue" with DSpace 1.7.0. The
> developers will need to determine if we should continue to support Maven
> 2.0.x, or if we require an upgrade to Maven 2.2.x or above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
