On 03/31/2011 10:56 PM, Kalle Korhonen wrote:
What's the value of having that available at runtime? I know you are
not a fan of Maven, but I've always thought that the dependency report
does a decent job explaining the dependencies, their sizes,
relationships and licenses at build time.
If I understand it correctly, the problem is that many licenses require
a notice to be displayed in the application. Typically this is is either
output on the console or provided in a "about" dialog somewhere.
The way we handled this in Geomajas is to collect these messages from
all modules (using Spring) and both output them on the console at
startup and provide a service which can be queried for inclusion in the
about page.
Kind regards,
Joachim
Kalle
On Thu, Mar 31, 2011 at 11:08 AM, Howard Lewis Ship<[email protected]> wrote:
I was just thinking about how to properly distribute licences (for
some third party dependencies, such as YUICompressor) ... what if
there was a core/AboutTapestry page, and a matching service.
Contributions to the service could describe the modules (such as
tapx-core) with a version number and any licence(s). Hitting
AboutTapestry would automatically display (perhaps with an accordion
interface) all the details of the application in one place.
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
