7:10 p.m.
This page is a good example ...
https://fedoraproject.org/wiki/Alfresco
... of what we are going to need for all of you.
I'm planning to send out an email to the general developers list
(fedora-devel-list), inviting packagers who are interested in ISV
software to assist with the packaging efforts. They benefit from the
dependency list.
Getting out this list of dependencies is the first step[1] in getting
software packaged. I encourage you to post whatever you have so far to
the wiki so that others can read and assist.[2]
If you need any assistance with the wiki, please contact me. Using the
general format of https://fedoraproject.org/wiki/Vendor_Name is a good
place to start gathering content. Let us know when you get something
posted!
Thanks - Karsten
[1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
[2] The work on the Alfresco page was a back-and-forth effort between
subject matter experts of Alfresco, Fedora, and Java. There is
expertise that can help when the details are visible to them.
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
8:41 p.m.
Karsten 'quaid' Wade wrote:
This page is a good example ...
https://fedoraproject.org/wiki/Alfresco
... of what we are going to need for all of you.
I'm planning to send out an email to the general developers list
(fedora-devel-list), inviting packagers who are interested in ISV
software to assist with the packaging efforts. They benefit from the
dependency list.
Getting out this list of dependencies is the first step[1] in getting
software packaged. I encourage you to post whatever you have so far to
the wiki so that others can read and assist.[2]
If you need any assistance with the wiki, please contact me. Using the
general format of https://fedoraproject.org/wiki/Vendor_Name is a good
place to start gathering content. Let us know when you get something
posted!
Thanks - Karsten
[1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
[2] The work on the Alfresco page was a back-and-forth effort between
subject matter experts of Alfresco, Fedora, and Java. There is
expertise that can help when the details are visible to them.
------------------------------------------------------------------------
_______________________________________________
Fedora-isv-sig-list mailing list
Fedora-isv-sig-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
Karsten and others,
This is great work! Can't wait to see more.
Jason
--
Jason Hibbets, RHCE
RHX & ISV Marketing Specialist
Office - 919.754.4181
Red Hat :: 1801 Varsity Drive :: Raleigh, NC 27606
IT executives: Red Hat #1 in value. Again.
http://www.redhat.com/promo/vendor/
1:28 p.m.
Rather than create a second page for JasperServer, I created a page
intended to list all of the JAR files we need. This way we can note where
multiple projects use overlapping JARs.
https://fedoraproject.org/wiki/Java_JAR_dependencies
Regards,
Matt
-----Original Message-----
From: fedora-isv-sig-list-bounces(a)redhat.com
[mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Karsten
'quaid' Wade
Sent: Monday, 08 September, 2008 17:11
To: fedora-isv-sig-list
Subject: dependencies page
This page is a good example ...
https://fedoraproject.org/wiki/Alfresco
... of what we are going to need for all of you.
I'm planning to send out an email to the general developers list
(fedora-devel-list), inviting packagers who are interested in ISV software
to assist with the packaging efforts. They benefit from the dependency
list.
Getting out this list of dependencies is the first step[1] in getting
software packaged. I encourage you to post whatever you have so far to
the wiki so that others can read and assist.[2]
If you need any assistance with the wiki, please contact me. Using the
general format of https://fedoraproject.org/wiki/Vendor_Name is a good
place to start gathering content. Let us know when you get something
posted!
Thanks - Karsten
[1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
[2] The work on the Alfresco page was a back-and-forth effort between
subject matter experts of Alfresco, Fedora, and Java. There is expertise
that can help when the details are visible to them.
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
2:42 p.m.
Matthew Dahlman wrote:
Rather than create a second page for JasperServer, I created a page
intended to list all of the JAR files we need. This way we can note where
multiple projects use overlapping JARs.
https://fedoraproject.org/wiki/Java_JAR_dependencies
I could give you (not next week, I will be travelling) the ones we need
for JBoss AS too. However, my database does not have versions in the
jar names, they are in a separate column.
Also, I noticed that 1/2 of the things you list as not in Jpackage are
in JPackage 5.0 (the WIP new release).
For instance, activation is JAF, any "jaf" package will have it. Same
for mail.jar
The Spring 2.x is the spring2 package.
jsf, jstl, are there, from glassfish-*
I am sure we have a full antlr as JBoss AS uses it. AXIS is also
complete. It may be a difference in the name of the JARs
W.r.t. wsdl4j, xerces and xalan these are just versions mismatches. I'd
strongly recommend that JasperSoft would spend the time necessary to
update these components as they are using very ancient versions and this
makes maintainability very difficult (these communities don't have these
under their radar for quite some time).
I think I will find a way to create a page for JPackage with a JAR to
package mapping, and with a version column. I have to ask our host to
create a database instance for me. (note: unversioned JAR file names
seems to be the more current practice, Sun likes it and it is compatible
with maven, so I will list them that way).
Regards to all. See you in one week.
Fernando
Regards,
Matt
-----Original Message-----
From: fedora-isv-sig-list-bounces(a)redhat.com
[mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Karsten
'quaid' Wade
Sent: Monday, 08 September, 2008 17:11
To: fedora-isv-sig-list
Subject: dependencies page
This page is a good example ...
https://fedoraproject.org/wiki/Alfresco
.. of what we are going to need for all of you.
I'm planning to send out an email to the general developers list
(fedora-devel-list), inviting packagers who are interested in ISV software
to assist with the packaging efforts. They benefit from the dependency
list.
Getting out this list of dependencies is the first step[1] in getting
software packaged. I encourage you to post whatever you have so far to
the wiki so that others can read and assist.[2]
If you need any assistance with the wiki, please contact me. Using the
general format of https://fedoraproject.org/wiki/Vendor_Name is a good
place to start gathering content. Let us know when you get something
posted!
Thanks - Karsten
[1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
[2] The work on the Alfresco page was a back-and-forth effort between
subject matter experts of Alfresco, Fedora, and Java. There is expertise
that can help when the details are visible to them.
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41
_______________________________________________
Fedora-isv-sig-list mailing list
Fedora-isv-sig-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
3:29 p.m.
That's great news to hear that many jars are already in JPackage 5.0 (the
WIP new release). I didn't notice this possibility as I looked at the
JPackage site. I'll update my lists.
Regarding the old jars, I agree. In many (most?) cases we can probably
just drop in the newer jar and test to make sure JasperServer still works.
In the worst case scenario where dropping in the new jar breaks our app,
I'm not sure that I'll be able to get JasperServer to update. Allocating
resources to fix something that isn't broken is often tough. Anyway, I
won't worry about this yet; we've got plenty of bridges to cross before
this one.
Regards,
Matt
-----Original Message-----
From: Fernando Nasser [mailto:fnasser@redhat.com]
Sent: Friday, 19 September, 2008 12:42
To: Matthew Dahlman
Cc: 'fedora-isv-sig-list'
Subject: Re: dependencies page
Matthew Dahlman wrote:
Rather than create a second page for JasperServer, I created a page
intended to list all of the JAR files we need. This way we can note
where multiple projects use overlapping JARs.
https://fedoraproject.org/wiki/Java_JAR_dependencies
I could give you (not next week, I will be travelling) the ones we need
for JBoss AS too. However, my database does not have versions in the jar
names, they are in a separate column.
Also, I noticed that 1/2 of the things you list as not in Jpackage are in
JPackage 5.0 (the WIP new release).
For instance, activation is JAF, any "jaf" package will have it. Same
for mail.jar
The Spring 2.x is the spring2 package.
jsf, jstl, are there, from glassfish-*
I am sure we have a full antlr as JBoss AS uses it. AXIS is also
complete. It may be a difference in the name of the JARs
W.r.t. wsdl4j, xerces and xalan these are just versions mismatches. I'd
strongly recommend that JasperSoft would spend the time necessary to
update these components as they are using very ancient versions and this
makes maintainability very difficult (these communities don't have these
under their radar for quite some time).
I think I will find a way to create a page for JPackage with a JAR to
package mapping, and with a version column. I have to ask our host to
create a database instance for me. (note: unversioned JAR file names
seems to be the more current practice, Sun likes it and it is compatible
with maven, so I will list them that way).
Regards to all. See you in one week.
Fernando
Regards,
Matt
-----Original Message-----
From: fedora-isv-sig-list-bounces(a)redhat.com
[mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Karsten
'quaid' Wade
Sent: Monday, 08 September, 2008 17:11
To: fedora-isv-sig-list
Subject: dependencies page
This page is a good example ...
https://fedoraproject.org/wiki/Alfresco
.. of what we are going to need for all of you.
I'm planning to send out an email to the general developers list
(fedora-devel-list), inviting packagers who are interested in ISV
software to assist with the packaging efforts. They benefit from the
dependency list.
Getting out this list of dependencies is the first step[1] in getting
software packaged. I encourage you to post whatever you have so far
to the wiki so that others can read and assist.[2]
If you need any assistance with the wiki, please contact me. Using
the general format of https://fedoraproject.org/wiki/Vendor_Name is a
good place to start gathering content. Let us know when you get
something posted!
Thanks - Karsten
[1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
[2] The work on the Alfresco page was a back-and-forth effort between
subject matter experts of Alfresco, Fedora, and Java. There is
expertise that can help when the details are visible to them.
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41
_______________________________________________
Fedora-isv-sig-list mailing list
Fedora-isv-sig-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
7:30 p.m.
Fernando,
I have updated the dependencies page to include your comments and to
update the JAR files that will be used by the next release of
JasperServer.
Do you have any additional comments about the JARs in "Dependencies Not
Already in JPackage"?
-Matt
-----Original Message-----
From: fedora-isv-sig-list-bounces(a)redhat.com
[mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Matthew
Dahlman
Sent: Friday, 19 September, 2008 13:30
To: 'Fernando Nasser'
Cc: 'fedora-isv-sig-list'
Subject: RE: dependencies page
That's great news to hear that many jars are already in JPackage 5.0 (the
WIP new release). I didn't notice this possibility as I looked at the
JPackage site. I'll update my lists.
Regarding the old jars, I agree. In many (most?) cases we can probably
just drop in the newer jar and test to make sure JasperServer still works.
In the worst case scenario where dropping in the new jar breaks our app,
I'm not sure that I'll be able to get JasperServer to update. Allocating
resources to fix something that isn't broken is often tough. Anyway, I
won't worry about this yet; we've got plenty of bridges to cross before
this one.
Regards,
Matt
-----Original Message-----
From: Fernando Nasser [mailto:fnasser@redhat.com]
Sent: Friday, 19 September, 2008 12:42
To: Matthew Dahlman
Cc: 'fedora-isv-sig-list'
Subject: Re: dependencies page
Matthew Dahlman wrote:
Rather than create a second page for JasperServer, I created a page
intended to list all of the JAR files we need. This way we can note
where multiple projects use overlapping JARs.
https://fedoraproject.org/wiki/Java_JAR_dependencies
I could give you (not next week, I will be travelling) the ones we need
for JBoss AS too. However, my database does not have versions in the jar
names, they are in a separate column.
Also, I noticed that 1/2 of the things you list as not in Jpackage are in
JPackage 5.0 (the WIP new release).
For instance, activation is JAF, any "jaf" package will have it. Same
for mail.jar
The Spring 2.x is the spring2 package.
jsf, jstl, are there, from glassfish-*
I am sure we have a full antlr as JBoss AS uses it. AXIS is also
complete. It may be a difference in the name of the JARs
W.r.t. wsdl4j, xerces and xalan these are just versions mismatches. I'd
strongly recommend that JasperSoft would spend the time necessary to
update these components as they are using very ancient versions and this
makes maintainability very difficult (these communities don't have these
under their radar for quite some time).
I think I will find a way to create a page for JPackage with a JAR to
package mapping, and with a version column. I have to ask our host to
create a database instance for me. (note: unversioned JAR file names
seems to be the more current practice, Sun likes it and it is compatible
with maven, so I will list them that way).
Regards to all. See you in one week.
Fernando
Regards,
Matt
-----Original Message-----
From: fedora-isv-sig-list-bounces(a)redhat.com
[mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Karsten
'quaid' Wade
Sent: Monday, 08 September, 2008 17:11
To: fedora-isv-sig-list
Subject: dependencies page
This page is a good example ...
https://fedoraproject.org/wiki/Alfresco
.. of what we are going to need for all of you.
I'm planning to send out an email to the general developers list
(fedora-devel-list), inviting packagers who are interested in ISV
software to assist with the packaging efforts. They benefit from the
dependency list.
Getting out this list of dependencies is the first step[1] in getting
software packaged. I encourage you to post whatever you have so far
to the wiki so that others can read and assist.[2]
If you need any assistance with the wiki, please contact me. Using
the general format of https://fedoraproject.org/wiki/Vendor_Name is a
good place to start gathering content. Let us know when you get
something posted!
Thanks - Karsten
[1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
[2] The work on the Alfresco page was a back-and-forth effort between
subject matter experts of Alfresco, Fedora, and Java. There is
expertise that can help when the details are visible to them.
--
Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41
_______________________________________________
Fedora-isv-sig-list mailing list
Fedora-isv-sig-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
_______________________________________________
Fedora-isv-sig-list mailing list
Fedora-isv-sig-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
8:54 p.m.
Found a couple more for you:
/home/projects/jpackage/dist/5.0/generic/free/RPMS/geronimo-jta-1.1-api-1.2-9.jpp5.noarch.rpm
from a package called geronimo-specs has the JTA API, which I believe
are the JARs you need. This is in JPackage.
The jdtcore.jar comes from the 'eclipse' package, which is already in
Fedora, probably in an eclipse-jdt subpackage. Look at something like:
/usr/share/eclipse/plugins/org.eclipse.jdt.core*/jdtcore.jar
Also, I believe the jbpm* stuff is from us (JBoss). If this is the
case, we even have a package to one version of jbpm-jpdl that we have
contributed to them.
/home/projects/jpackage/dist/5.0/generic/free/RPMS/jboss-jbpm-jpdl-3.2.0-1.jpp5.noarch.rpm
that has both jbpm-identity.jar and jbpm-jpdl.jar
It is even the right version, except that the jbpm-jpdl-3.2-patched.jar
used by Alfresco seems to imply some local modification.
The other JARs I don't recognize from the top of my head. I need to get
that JPackage JAR database going so we can search more easily. One of
these days....
P.S.: I do recognize jai, but I don't think there is an Open Source
version of JAI. The preoject I kew depended on this had to undergo a
major refactoring to remove that dependency (upstream, in their
community). AFAIR it was fop.
Best regards,
Fernando
Matthew Dahlman wrote:
Fernando,
I have updated the dependencies page to include your comments and to
update the JAR files that will be used by the next release of
JasperServer.
Do you have any additional comments about the JARs in "Dependencies Not
Already in JPackage"?
-Matt
-----Original Message-----
From: fedora-isv-sig-list-bounces(a)redhat.com
[mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Matthew
Dahlman
Sent: Friday, 19 September, 2008 13:30
To: 'Fernando Nasser'
Cc: 'fedora-isv-sig-list'
Subject: RE: dependencies page
That's great news to hear that many jars are already in JPackage 5.0 (the
WIP new release). I didn't notice this possibility as I looked at the
JPackage site. I'll update my lists.
Regarding the old jars, I agree. In many (most?) cases we can probably
just drop in the newer jar and test to make sure JasperServer still works.
In the worst case scenario where dropping in the new jar breaks our app,
I'm not sure that I'll be able to get JasperServer to update. Allocating
resources to fix something that isn't broken is often tough. Anyway, I
won't worry about this yet; we've got plenty of bridges to cross before
this one.
Regards,
Matt
-----Original Message-----
From: Fernando Nasser [mailto:fnasser@redhat.com]
Sent: Friday, 19 September, 2008 12:42
To: Matthew Dahlman
Cc: 'fedora-isv-sig-list'
Subject: Re: dependencies page
Matthew Dahlman wrote:
> Rather than create a second page for JasperServer, I created a page
> intended to list all of the JAR files we need. This way we can note
> where multiple projects use overlapping JARs.
>
> https://fedoraproject.org/wiki/Java_JAR_dependencies
>
>
I could give you (not next week, I will be travelling) the ones we need
for JBoss AS too. However, my database does not have versions in the jar
names, they are in a separate column.
Also, I noticed that 1/2 of the things you list as not in Jpackage are in
JPackage 5.0 (the WIP new release).
For instance, activation is JAF, any "jaf" package will have it. Same
for mail.jar
The Spring 2.x is the spring2 package.
jsf, jstl, are there, from glassfish-*
I am sure we have a full antlr as JBoss AS uses it. AXIS is also
complete. It may be a difference in the name of the JARs
W.r.t. wsdl4j, xerces and xalan these are just versions mismatches. I'd
strongly recommend that JasperSoft would spend the time necessary to
update these components as they are using very ancient versions and this
makes maintainability very difficult (these communities don't have these
under their radar for quite some time).
I think I will find a way to create a page for JPackage with a JAR to
package mapping, and with a version column. I have to ask our host to
create a database instance for me. (note: unversioned JAR file names
seems to be the more current practice, Sun likes it and it is compatible
with maven, so I will list them that way).
Regards to all. See you in one week.
Fernando
> Regards,
> Matt
>
> -----Original Message-----
> From: fedora-isv-sig-list-bounces(a)redhat.com
> [mailto:fedora-isv-sig-list-bounces@redhat.com] On Behalf Of Karsten
> 'quaid' Wade
> Sent: Monday, 08 September, 2008 17:11
> To: fedora-isv-sig-list
> Subject: dependencies page
>
> This page is a good example ...
>
> https://fedoraproject.org/wiki/Alfresco
>
> .. of what we are going to need for all of you.
>
> I'm planning to send out an email to the general developers list
> (fedora-devel-list), inviting packagers who are interested in ISV
> software to assist with the packaging efforts. They benefit from the
> dependency list.
>
> Getting out this list of dependencies is the first step[1] in getting
> software packaged. I encourage you to post whatever you have so far
> to the wiki so that others can read and assist.[2]
>
> If you need any assistance with the wiki, please contact me. Using
> the general format of https://fedoraproject.org/wiki/Vendor_Name is a
> good place to start gathering content. Let us know when you get
> something posted!
>
> Thanks - Karsten
>
> [1] https://fedoraproject.org/wiki/SIGs/ISV#What_next.3F
>
> [2] The work on the Alfresco page was a back-and-forth effort between
> subject matter experts of Alfresco, Fedora, and Java. There is
> expertise that can help when the details are visible to them.
>
> --
> Karsten Wade, Sr. Developer Community Mgr.
> Dev Fu : http://developer.redhatmagazine.com
> Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41
>
> _______________________________________________
> Fedora-isv-sig-list mailing list
> Fedora-isv-sig-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
>
_______________________________________________
Fedora-isv-sig-list mailing list
Fedora-isv-sig-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list
5687
days inactive
5715
days old
isv-sig@lists.fedoraproject.org
6 comments
4 participants
participants (4)
-
Fernando Nasser -
Jason Hibbets -
Karsten Wade -
Matthew Dahlman