Hello, This is an email to update the community on the status of the language-packs addon for DSpace and its location in the current dspace-1_5_x release process.
We've moved language-packs out of the Sourceforge SVN repository and in the dspace-sandbox repository where it is now available with the "dspace-xmlui-lang" Addon for localizations in Manakin. In this relocation we also changed the name of the project to be inline with the other Maven subprojects in the DSpace ecosystem. language-packs is now called "dspace-api-lang", though it still contains both dspace- api localizations and dspace-jspui localizations. You can now find these two projects with their own release track and svn project spaces in the following location: DSpace API/JSP-UI Localizations: https://dspace-sandbox.googlecode.com/svn/modules/dspace-api-lang/trunk XML-UI Localizations: https://dspace-sandbox.googlecode.com/svn/modules/dspace-xmlui-lang/ trunk In preparation for the 1.5 release these projects have a different versioning scheme and release schedule We have made initial releases here: https://dspace-sandbox.googlecode.com/svn/modules/dspace-api-lang/ tags/dspace-api-lang-1.5.0.0 https://dspace-sandbox.googlecode.com/svn/modules/dspace-xmlui-lang/ tags/dspace-xmlui-lang-1.5.0.0 The version number on these Addons has four sections major.minor [.maintenance[.build]] This allows the Languages to have an incremental release cycle that is higher frequency to that of the DSpace project endorsed addons in the SF svn repo. In the dspace-parent pom, there are dependencyManagment ranges on these Addons that allow for version ranges to be used. > <!-- DSpace Localization Packages --> > <dependency> > <groupId>org.dspace</groupId> > <artifactId>dspace-api-lang</artifactId> > <version>[1.5.0.0,1.6.0.0)</version> > </dependency> > <dependency> > <groupId>org.dspace</groupId> > <artifactId>dspace-xmlui-lang</artifactId> > <version>[1.5.0.0,1.6.0.0)</version> > <type>war</type> > </dependency> These allow for the dspace-xxx-lang projects to be released and updates delivered into your dspace build without having to alter anything locally in DSpace. To update your localizations one simple would run: mvn -U package Forcing maven to go out and look for the latest released versions of these Addons when building. We can now allow for more community involvement in maintaining these projects being they are in the sandbox and under a separate Access Control than the DSpace endorsed SVN repository at Sourceforge. Cheers, Mark Diggory ~~~~~~~~~~~~~ Mark R. Diggory - DSpace Developer and Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
