@sebb About the duplicated JARs in our binary packages: Those JARs are different from the JARs in WEB-INF/lib or Server's lib. Those JARs are signed by a certificate and used by a Java Web-Start application. This Web-Start application is the Screensharing/Recording client during conference sessions in OpenMeetings. That is why those JARs are duplicated in different folders. I don't think we will change anything about that, the signed JARs for the client and the Web-Applications JARs should stay in different folders. There might be a way to virtually make the JARs from the server's lib folder available for the Web-Start application but I don't think mixing those JARs will have a good effect on how easy it is for 3th party to understand which JARs are necessary for the Web-Start client. End users might for example use their own certificate to sign those JARs to get rid of WebStarts warning box. If we obfuscate the path to the JARs by mixing them there will be no additional value for the end user.
Sebastian 2012/6/26 sebb <seb...@gmail.com> > On 26 June 2012 14:46, Kevan Miller <kevan.mil...@gmail.com> wrote: > > > > On Jun 26, 2012, at 9:40 AM, sebb wrote: > > > >> On 26 June 2012 13:28, seba.wag...@gmail.com <seba.wag...@gmail.com> > wrote: > >>> Thanks for the feedback and review so far! > >>> > >>> About correct attribution of ASF JARs > >>> Do they need a reference in the LICENSE file at all ? > >> > >> The recipient of the package needs to be able to quickly find the > >> license associated with all jars, so I would say yes. > >> > >>> Must the name of the JAR file be _exactly_ mentioned in the LICENSE > file? > >>> For example: > >>> > http://svn.apache.org/viewvc/incubator/openmeetings/tags/2.0RC2/LICENSE?view=markup > >>> Line: 206 > >>> "For GlassFish components / activation.jar" > >>> => Do we need to write "activation-jar-1.1.jar" instead of > "activation.jar" > >>> ? > >> > >> Yes, because licenses may change between versions. > > > > I've seen 'activation-jar-x.x.jar' used to good effect. In either case, > the key would be that the license must be validated when the version is > changed and when the release is being generated/reviewed. As long as that > occurs an explicit name or a suitably descriptive name would be sufficient… > > If the license is not tied to the specific jar version in the LICENSE > file, then this info will have to be held elsewhere to ensure that > version changes can be properly validated by the committers. Keeping > the version in the LICENSE file is very simple, and is helpful both to > the end-user and the reviewer. > > > --kevan > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com
