My only objection to putting the version number in the <name> is that becomes one more thing to maintain when the release number changes.
On 11/7/06, andyhot <[EMAIL PROTECTED]> wrote:
Howard Lewis Ship wrote: > Sounds fine to me. I think Tapestry 5 is already on the right track: > > <name>Tapestry Core Library</name> doh... i did the change in the 4.1 pom, but now i can't easily tell if i have 4.1 or 5 open... they're both named "Tapestry Core Library" :( Is "Tapestry 4.1 Core Library" out of the question? > > On 11/7/06, andyhot <[EMAIL PROTECTED]> wrote: >> >> Anyone minds making the (project) names in all pom.xml >> a bit more descriptive? >> i.e. >> 'Tapestry Core Library' instead of 'Core Library' >> >> Mevenide uses that value to name the projects within the IDE... >> And anyway, i don't mind adding tapestry everywhere. >> >> -- >> Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr >> Tapestry / Tacos developer >> Open Source / J2EE Consulting >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
