You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2011/03/08 00:58:59 UTC
[jira] Commented: (JS2-1245) Update some external artifact
dependencies to more recent and general available versions
[ https://issues.apache.org/jira/browse/JS2-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003708#comment-13003708 ]
Ate Douma commented on JS2-1245:
--------------------------------
All external artifacts for jetspeed-2 portal and j2-admin projects now can be resolved through default maven central repository.
Used portals apps and portals bridges projects are next to review if certain dependencies might need updating to more general available versions.
> Update some external artifact dependencies to more recent and general available versions
> ----------------------------------------------------------------------------------------
>
> Key: JS2-1245
> URL: https://issues.apache.org/jira/browse/JS2-1245
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Project Build
> Affects Versions: 2.2.2
> Reporter: Ate Douma
> Assignee: Ate Douma
> Priority: Minor
> Fix For: 2.2.2
>
>
> We have some external artifact dependencies which are not (or no longer) available from maven central repository, or patched versions of never/not yet released versions.
> While going through the work for JS2-1227 (maven 3 build support) I looked again a bit at these and determined that most cases can be resolved.
> Right now I've got the portal project "cleaned up" already locally, just need a bit more testing on the upgrade of javolution to 5.2.6 (build and test works fine).
> Other updates/upgrades I've pending concerns mockrunner, castor, ddlutils (through runtime patching of the 1.0 release) and integrating the openid-step2 (com.google.step2) "fork" as normal jetspeed-2 artifact in the build.
> With these pending changes the portal project can be build against only the current maven central repository.
> After this, I'll go check the j2-admin and used portals apps projects and see if those also can be made current against maven central (not sure yet).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org