11:22 p.m.
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Priority: Minor
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=comments#action_12379438 ]
Dan Allen commented on JBSEAM-1532:
-----------------------------------
Can we piggy back off the Maven 2 work to have this either auto-generated?
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:48 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=comments#action_12379444 ]
Pete Muir commented on JBSEAM-1532:
-----------------------------------
Why?
I can if desired (when the maven dependency plugin releases alpha5) write an ant target
that will give you a tree report of the current transitive dependency tree.
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=comments#action_12379450 ]
Dan Allen commented on JBSEAM-1532:
-----------------------------------
That will work perfectly. This issue is just about communication. We want to let people
know what Seam uses. Since Maven 2 is designed to give that report, we have a winner.
I just want to clarify that this issue is important for various Sarbanes-Oxley related
reasons. System administrators need to know what libraries and one versions are used
without having to extract jar files and reverse engineer. The initiative to integrate
Maven 2 dependencies was a very important to satisfy this need.
Add the Ant target and we can close off this issue.
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=comments#action_12379451 ]
Dan Allen commented on JBSEAM-1532:
-----------------------------------
Boy that was some bad typing. Let me try again:
That will work perfectly. This issue is just about communication. We want to let people
know what libraries Seam depends on. Since Maven 2 is designed to give that report, we
have a winner.
I just want to clarify that this issue is important for various Sarbanes-Oxley related
initiatives. It is also important to help developers and sysadmins to reconcile
dependencies on libraries already used by projects. They should not have to extract jar
files and reverse engineer them. The initiative to integrate Maven 2 dependencies was a
very important one to satisfy all of these needs.
Add the Ant target and we can close off this issue.
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Priority: Minor
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=all ]
Pete Muir updated JBSEAM-1532:
------------------------------
Issue Type: Task (was: Feature Request)
Component/s: (was: Documentation)
Fix Version/s: 2.0.x
Assignee: Pete Muir
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Task
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.x
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:50 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=all ]
Pete Muir updated JBSEAM-1532:
------------------------------
Component/s: Build
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Task
Components: Build
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.0.x
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=all ]
Pete Muir updated JBSEAM-1532:
------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.x)
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Task
Components: Build
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.1.0.GA
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:36 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1532) include jar-versions.xml file
[ http://jira.jboss.com/jira/browse/JBSEAM-1532?page=all ]
Pete Muir closed JBSEAM-1532.
-----------------------------
Resolution: Done
Finally done. Run ant dependencyReport to generate /dependency-report.txt which is an
ASCII tree of dependencies (groupId, artifactId, scope, version) for each Seam module.
Dependency chapter discusses common dependencies.
include jar-versions.xml file
-----------------------------
Key: JBSEAM-1532
URL: http://jira.jboss.com/jira/browse/JBSEAM-1532
Project: JBoss Seam
Issue Type: Task
Components: Build
Affects Versions: 1.3.0.ALPHA
Environment: seam CVS HEAD
Reporter: Dan Allen
Assigned To: Pete Muir
Priority: Minor
Fix For: 2.1.0.GA
Original Estimate: 4 hours
Remaining Estimate: 4 hours
It would be so helpful if a jar-versions.xml file could be kept up to date in the root of
the seam source code to track the versions of the bundle libraries, in the absence of
other solutions. This idea comes from the JBoss AS, which uses this file to communicate
the versions of libraries used.
Documenting the versions helps:
1. developers, who may find challenge in combining APIs of libraries without knowing the
version
2. users who are unable to determine the contents of what they downloaded
3. for legal reasons, just in case there are differences in licenses amongst releases of
third party products, to protect seam itself as well as integrators of seam.
With all that said, the better solution is to use ant-ivy or maven2 to get the jar files
out of the source code. But I digress.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6168
days inactive
6393
days old
8 comments
2 participants
participants (2)
-
Dan Allen (JIRA) -
Pete Muir (JIRA)