Hi,

I don't know if this is a topic to be treated on this list but here come my
thoughts...

a) maven:

if you used the tapestry maven archetype to create the project that you 're
currently working at... you 're almost done.., in fact... if you 're running
your t5 applicaction using the maven jetty plugin... well you 're done.

b) subversion:

you could just upload (import) your project into a svn structure (it's good
to know and apply the trunk/tags/branches directory structure) using any svn
client (e.g.: tortoise svn on windows or just svn on command line at linux).

AFAIK Maven and SVN integration is not needed to share a maven project...
it's needed only if you want to deal with automatic releases, in which case
you would need to search through the "maven release" and "maven scm"
plugin's site/mailing list.

hope that helps...

cheers.

Nicolás.-


On Mon, Aug 22, 2011 at 6:28 AM, captain_rhino <
graeme.kitc...@axa-travel-insurance.com> wrote:

> I've been building a tapestry prototype over the last few weeks for a new
> project.
>
> I've been happily building away and running through jetty.
>
> Now has come the time that other developer(s) are going top have to work on
> the project.
>
> I am no expert in Maven but on a high level how would I integrate my
> tapestry project with subserversion and maven.  Should I just be checking
> into subversion certain directories that my fellow developers can then
> check
> out?  Or is there something in Maven that enables me to do this easily?
>
> If someone could point me in the right direction it would be much
> appreciated.
>
> regards&thanks
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry-integration-with-Maven-and-subversion-tp4722727p4722727.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to