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).
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Field||Original Value||New Value|
|Summary||Update some external artifact dependencies to more recent or general available versions||Update some external artifact dependencies to more recent and general available versions|