I have a question about how to combine the structure of source/resource files
as required by Maven and as suggested by version control. Of course you're
familiar with the Maven structure, and the structure of the version control
is often PROJECT/{trunk,branches,tags}
How would an example of the hierarchy of source folders and files therefore
look in the version control repository for source? Would the first level in
the hierarchy (topmost level) be PROJECT, or would it be
{trunk,branches,tags} further subdivided by project?
(I ask this question assuming multiple projects, branches, and tags.)
Is this layout flexible, or do Maven's usual rules for directory structure
dictate a certain layout when combined with version control layouts?
lightbulb432 wrote:
>
> What's the difference between Maven and version control repositories when
> you're using both? Maven has its repository, but so does my version
> control.
>
> As I'm fairly new to this, could somebody explain the division of
> responsibility between Maven and version control specifically? e.g. Once
> you've organized your project in the Maven hierarchy, what do you do then?
> What to do about JARs which are in the Maven repository?
>
> Is it possible to version everything in Maven using source control,
> including the library repository?
>
--
View this message in context:
http://www.nabble.com/Maven-vs-source-control-tf3221731s177.html#a8968901
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
