Details
Improvement
Description
Specifically, for the 1.8 release we should:
1. Update the commons-beanutils.jar to v1.7.0. Note that the Licenses&Versions.html file in the /lib dir states that it is already 1.7.0, but in fact the .jar is 1.6.0.
2. Update the jstl.jar from v1.1 to v 1.1.2.
3. Update the commons-discovery.jar from v0.2 to v0.4. Note that the Licenses&Versions.html file in the /lib dir states that it is already 0.4, but in fact the .jar is v0.2.
In all cases we must verify that the upgraded versions support our platforms (JSF 1.1, JDK 1.4, etc.). Also, the Licenses&Version.html file in the /lib directory must be updated to indicate the correct version information for any files that are changed (or not in cases where the version is currently incorrect).
Issue Links
- blocks
-
ICE-3497
Add Maven .pom files to ICEfaces release bundles
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | jardependencyversions.ods [ 11490 ] |
| Summary | use correct versions of dependent jars for ICEfaces distribution | Update dependent libraries in ICEfaces distribution to better support Maven |
| Salesforce Case | [] | |
| Fix Version/s | 1.8RC1 [ 10143 ] | |
| Assignee Priority | P1 | |
| Description | Documentation on the dependent jars is not always correct with what is specified within the jar (see attached spreadsheet). Sometimes when the version specified in /lib/versions-license.html is the same as within the jar, that version is not available on any maven repository (not a GA or final version?). We should ensure that the versions we use can also be specified using maven. |
Documentation on the dependent jars is not always correct with what is specified within the jar (see attached spreadsheet). Sometimes when the version specified in /lib/versions-license.html is the same as within the jar, that version is not available on any maven repository (not a GA or final version?). We should ensure that the versions we use can also be specified using maven. Specifically, for the 1.8 release we should: 1. Update the commons-beanutils.jar to v1.7.0. Note that the Licenses&Versions.html file in the /lib dir states that it is already 1.7.0, but in fact the .jar is 1.6.0. 2. Update the jstl.jar from v1.1 to v 1.1.2. 3. Update the commons-discovery.jar from v0.2 to v0.4. Note that the Licenses&Versions.html file in the /lib dir states that it is already 0.4, but in fact the .jar is v0.2. In all cases we must verify that the upgraded versions support our platforms (JSF 1.1, JDK 1.4, etc.). Also, the Licenses&Version.html file in the /lib directory must be updated to indicate the correct version information for any files that are changed (or not in cases where the version is currently incorrect). |
| Security | Private [ 10001 ] | |
| Assignee | Deryk Sinotte [ deryk.sinotte ] |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #18267 | Fri Jan 30 15:56:29 MST 2009 | deryk.sinotte | |
| Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/lib/jstl.jar
MODIFY
/icefaces/trunk/icefaces/lib/commons-discovery.jar
MODIFY
/icefaces/trunk/icefaces/lib/commons-beanutils.jar
|
I've updated the following libraries to the following versions:
commons-beanutils.jar from 1.6 to 1.8
jstl.jar from 1.1 to 1.1.2
commons-discover.jar from 0.2 to 0.4
A full build on the trunk did not reveal any issues. Please let me know if there are any regressions or problems with the above changes.
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #18269 | Mon Feb 02 08:29:55 MST 2009 | deryk.sinotte | |
| Files Changed | ||||
|
MODIFY
/icefaces/trunk/icefaces/lib/versions-licenses.html
|
I've updated the noted .jar files and ensured that the versions-licenses.html file accurately reflects those changes.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Build.xml's need general update.
After few small changes build.xml's can support Maven naming convention for library files like jsf-api-1.2.11 etc. and variants for java1.4-1.5 etc. So creating and updating of Icefaces maven pom's is much easier.
I'm using such modified build.xml's for a long time without any problem.
By the way. I think that is good time to make true domain maven.icefaces.org as an location of Icefaces version and revision ... for peoples not interested in sources.
From the other hand ... many libraries used by Icefaces 1.8DR3 are compiled with java 1.5 and 1.6 and probably will not work under original java 1.4. I think that further support of 1.4 is not needed
@Krashan
If there are changes that would be valuable to the build.xml files to would make them better, please open a separate JIRA and then specify the changes and/or attach modified versions of the files that we can look at and possibly use.
We are still considering how best to handle the demand for Maven. Thank you for your input.
As for 1.4, we do still have valued customers that need support for that version of the platform so we cannot migrate away with our current products (1.7.x, 1.8.x). However, we are now starting on the ICEfaces 2.0 development path and will likely only support 1.5+ going forward with that release.
The only available jar on any of the maven2 repositories (that I can see) for commons-beanutils is 1.8.0.BETA, so perhaps we should revert to 1.7.0 version until 1.8.0 is established
jstl can be successfully updated to 1.2 version (not 1.1.2)
Maven library location
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>jstl</artifactId>
<version>1.2</version> <!-1.1.0 update to 1.2->
</dependency>
| Fix Version/s | 1.8 [ 10161 ] | |
| Assignee Priority | P1 |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Deryk Sinotte [ deryk.sinotte ] |
spreadsheet with conflicts in dependency jars.