solo,
When you say "backup", do you mean "commit changes to an SCM system"? Or
are you referring to actually backing up a working copy of a module that
was checked out from the SCM server (e.g. with a nightly desktop backup
system)?
On team projects, SCM commits aren't really "backups", since it is the
SCM repo that is the "one true source" of your project's source code at
any given time. Working copies are just temporary individual working
areas that allow team members to contribute changes to the repo.
If you mean SCM commits, the ignore lists are the perfect solution.
That's what they were invented for. Their primary functions are:
* preventing build artifacts from being committed to the repo
* preventing build artifacts from appearing to be "local changes", since
their presence would make it hard to tell if you had "real" local
changes at a glance (an issue that leads to team members forgetting to
commit a file or two when they change several files as part of a task)
If you are facing some issues with a backup system, I would guess that
that system could be configured to ignore certain directories as well.
And really, it probably doesn't matter that much if the build artifacts
get backed up -- they would never be mistaken for source code anyway.
-Max
solo turn wrote:
mvn clean would be a possibility ... but doing that always before
doing a backup? we'd prefer to run it independently.
but remy and max propositions help already a lot concerning verison
control. a few entries in the ignore is doable.
-solo
On 10/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
I didn't write the docs, but I can share in your difficulties. I've
flailed around at times with maven, but it gets better as you stick with
it.
I like the scm approach better because maven is tempermental about
directory layout. Yes, you can modify that, but who knows what plugins
might make assumptions about things being in their default locations. Scm
just seems less risky to me.
If I'm understanding your motivation, is 'mvn clean' not satisfactory? It
deletes all the generated resources.
Greg Vaughn
[EMAIL PROTECTED]
"solo turn" <[EMAIL PROTECTED]> wrote on 10/20/2006 02:57:52 AM:
> thanks greg,
>
> this is a very user friendly documentation ... no default values are
> there so you have to guess or code read what it stands for :)
>
> our motivation is that all files should be organised by "backup
> class", i.e. we want a simpe way to throw away all built files if
> necessary, and we do not want to backup it.
>
> also i'd consider setting one company rule " where to put all
> build/generated things would be simpler.
>
> why do you think the scm approach better? do you have a sample ignore
file?
>
> best regards,
>
> solo.
>
> On 10/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> > I've never tried configuring maven to put generated files outside of
its
> > default location, but this link
> >
http://maven.apache.org/ref/current/maven-model/maven.html#class_build
> > seems to imply it can by setting the <build><directory> element.
> >
> > I have setup both cvs and svn to ignore certain directories. Either
one
> > should work for you, but I'd recommend the scm approach. The details
will
> > depend on which scm tool you use.
> >
> > Greg Vaughn
> > [EMAIL PROTECTED]
> >
> >
> >
> > "solo turn" <[EMAIL PROTECTED]>
> > 10/18/2006 03:56 PM
> > Please respond to
> > "Maven Users List" <[email protected]>
> >
> >
> > To
> > "Maven Developers List" <[email protected]>
> > cc
> >
> > Subject
> > clear separation of source and target
> >
> >
> >
> >
> >
> >
> > hi,
> >
> > is there an easy possibility to separate source code (which we write)
> > from generated things?
> >
> > we'd prefer to keep the directory where the pom is to stay clean of
> > all built and generated things to use source code control systems
like
> > mercurial or darcs on that tree.
> >
> > is it possible to do that by:
> > * configuring maven to put generated files somewhere out of this
> > directory, or
> > * configuring the source code control by excluding a directory
resp a
> > fixed set of directories
> > ?
> >
> > -solo.
======================================================================
Confidentiality Notice: The information contained in and transmitted
with this communication is strictly confidential, is intended only for
the use of the intended recipient, and is the property of Countrywide
Financial Corporation or its affiliates and subsidiaries. If you are
not the intended recipient, you are hereby notified that any use of
the information contained in or transmitted with the communication or
dissemination, distribution, or copying of this communication is
strictly prohibited by law. If you have received this communication
in error, please immediately return this communication to the sender
and delete the original message and any copy of it in your possession.
======================================================================
---------------------------------------------------------------------
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]
