All,
For the developers out there who are currently being affected by this
issue -- there is a very temporary work-around, if you really need to
rebuild/reinstall DSpace immediately.
***WARNING:*** This workaround is NOT RECOMMENDED for non-developers or
anyone who is uncomfortable with XML editing. This is an UNSUPPORTED
change, but it will allow you to build DSpace again while we continue to
work on a permanent fix.
The temporary work-around is to make a small modification to DSpace's
[dspace-source]/pom.xml (NOTE: This is the top-level-folder pom.xml,
NOT the one in [dspace-source]/dspace/pom.xml). This top-level pom.xml
should have a "<name>DSpace Parent POM</name>" near the top of it. If
you don't see that, then you are modifying the wrong pom.xml.
In that top-level pom.xml, you will need to add a new <repository> tag
underneath the existing <repositories> tag as follows. You will see a
few existing <repository> tags are already under the existing
<repositories> tag. Just add the new tag directly after the existing
<repository> tags.
<repositories>
...(Some existing contents will already be here. Leave it alone.)...
<!-- TEMPORARY FIX FOR DSPACE MAVEN ISSUES - PLEASE REMOVE THIS
ONCE ISSUES ARE RESOLVED. -->
<repository>
<id>maven.dspace.org-release</id>
<name>DSpace Maven Release Repository</name>
<url>http://maven.dspace.org/release</url>
<releases>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</releases>
<snapshots>
<enabled>false</enabled>
<updatePolicy>never</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
</repository>
<!-- END TEMPORARY FIX -->
</repositories>
This new <repository> tag will tell Maven to temporarily use our
http://maven.dspace.org/release/ Code Repository. This will allow you
to successfully build DSpace 1.5.x through 1.6.x, as the Maven settings
in this code repository have not been compromised.
Once you've added this tag, you can rebuild by using:
mvn -U clean package
(The -U option will force your local Maven cache to update itself with
the settings provided by the newly added <repository> tag above.)
Once we've resolved this issue for everyone, you are encouraged to
*remove* this <repository> tag -- it should not be considered a
permanent change. It's just a temporary workaround for this issue.
I hope this helps! Again, we'll let you all know as soon as these issues
are resolved.
- Tim
On 11/9/2010 11:56 AM, Tim Donohue wrote:
> All,
>
> First off, let me apologize in advance to anyone who has encountered
> DSpace Maven build issues yesterday or today. These build errors
> sometimes occur when running 'mvn package' and look similar to the
> following:
>
> "[INFO] Failed to resolve artifact.
>
> Couldn't find a version in [1.7.0.1] to match range [1.6.0.0,1.7.0.0)
> org.dspace:dspace-api-lang:jar:null"
>
> Unfortunately, our global DSpace Maven settings were accidentally messed
> up yesterday, through no real fault of our own. Essentially, this
> occurred via a series of issues located during our attempt to release
> DSpace 1.7.0 Release Candidate 1.
>
> During our release, we discovered our old route of getting DSpace Maven
> build packages published worldwide was unfortunately discontinued
> without our knowledge (the third party service we were using just
> stopped syncing with our servers without notifying us).
>
> Because our old release process was ceased, over the past few days we
> quickly migrated to a different route of publishing Maven releases via
> SonaType (http://www.sonatype.com/), so that we could try to release
> DSpace 1.7.0 Release Candidate 1 in time for this week's DSpace 1.7
> Testathon.
>
> This new route via SonaType has now unfortunately backfired on us, as
> SonaType accidentally overwrote our global Maven settings for past
> versions of DSpace software. This means that re-building/re-installing
> of all 1.5.x and 1.6.x versions is likely affected (unless you happen to
> have a local cache of the previous Maven settings to work from).
>
> (Please note: Although this affects re-building / re-installing of
> DSpace 1.5.x and 1.6.x versions, it will not affect the stability of
> your currently running DSpace repository. Your existing DSpace
> repository will continue to function as normal -- you will just be
> unable to rebuild DSpace if you are doing local development work.)
>
> We are currently working with SonaType to try to resolve these issues
> for everyone. We apologize for the inconvenience -- it is obviously
> affecting us all. We hope to have this resolved as soon as possible.
>
> I'll send an update to this notice as soon as we've come to a resolution.
>
> - Tim
>
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
