Details
-
Wish
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Though we are using ivy for resolving dependencies, not all the dependencies are resolved through IVy.
The reason is the unavailability of the appropriate version of the artifacts in the repository and the ambiguity of the version of the dependencies
At the moment beloe is the list of dependencies which are still resolved from the local lib directories.
under the lib folder
commons-cli-2.0-SNAPSHOT.jar - yet to be available in the centralized repo
kfs-0.2.2.jar - not available in the maven repo.
hsqldb-1.8.0.10.jar - latest available version is
under the lib/jsp-2.1 folder
jsp-2.1.jar - version # unknown
jsp-api-2.1.jar - version # unknown
under src/test/lib/ folder
ftplet-api-1.0.0-SNAPSHOT.jar - unavailable in the maven repo
ftpserver-server-1.0.0-SNAPSHOT.jar - unavailable in the maven repo
ftpserver-core-1.0.0-SNAPSHOT.jar - unavailable in the maven repo
mina-core-2.0.0-M2-20080407.124109-12.jar - unavailable in the maven repo
under src/contrib/chukwa/lib
json.jar - version # unknown
under src/contrib/thriftfs/lib
libthrift.jar - unavailable in the maven repo.
Thanks,
Giri
Attachments
1.
|
Resolving json.jar through ivy | Resolved | Giridharan Kesavan | |
2.
|
to downgrade commons-cli from 2.0 to 1.2 | Resolved | Devaraj Das | |
3.
|
to resolve jsp-2.1 jars through IVY | Closed | Giridharan Kesavan |