Can you provide some background about how Nexus would fit into our processes?
Also, why are changes necessary back to Tapestry 5.0? What about 5.1? Shouldn't this be an issue for 5.2 and beyond? I've also been nervous about some of Maven's release plugin ... the idea that it will edit the poms and check them back into source control ... is this really what it does? On Thu, Sep 24, 2009 at 5:03 PM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Thiago H. de Paula Figueiredo: +1 (non-binding) > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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]
