Thanks for the help;
>> >>Q1) How can we employ the concept of a quarantine directory.
>> Wouldn't changing ${maven.build.dir} do it ?
>> I'm not sure what you want to do there ...
The way our current builds work, is that the binaries are built into a
quarantine directory. If the tests pass, then the quarantine directory gets
copied to dist/latest.
This means that at no point in time does the dist/latest get "broken".
Perhaps a postGoal will achieve the same effect.
>> >>Q2) How can we run maven so that all the src is fetched (the libs are
>> >kind-of taken care of by maven - but for C++ we have to do it
ourselves)
>> There is an Ant CVS task. It should be pretty easy to use that
>> in a preGoal.
Ok. A preGoal for java:compile would do the trick, no?
>> >Q3) How can we run maven so that the build is done in a different
directory
>> >each time (ie, there is no danger of pollution from a previous run).
Call
>> >form ant?
>> >
>> I would use a <preGoal> to the goal you need to run like this:
OK. I guess what I want to do is run the whole maven build from that
timestamped directory.
I think I have answered my own question there - I need a new goal - that
creates that directory and runs maven from there..
>> >Q4) How can we make sure that local repository is in synch with the
remote
>> >repository (is there a way to "clean" the local repository?)
>> Use snapshot dependencies. Those are downloaded every time Maven runs.
I guess what I want to do is make sure is that a batch build is done "from
scratch".
I want to ensure that the build is not affected by because there are
locally installed jars that dont exist in the remote repository.
I guess I can write a preGoal to delete it.
>> >Q5) How can we integrate the versioning into the Maven build
(incrementing
>> >the version number etc) (pre and post goals perhaps?)
>> >
>> Again, I'm not sure about what you want to do there ...
>> But, again, I suggest that you use the CVS task to commit the file, in a
>> postGoal this time ! ;-)
I have ant tasks that manipulate a version.properties file that and a
timestamp.properties file.
I might turn this into a plugin if nothing similar exists.
One target :
<target name="incrementMajorVersion">
<propertyfile file="${working.dir}/${build.dir}/version.properties"
comment="Version File">
<entry key="build.number" type="int" default="0" operation="+"/>
<entry key="version.major" type="int" default="0" operation="+"/>
<entry key="version.minor" value="0"/>
</propertyfile>
</target>
Thanks again.
(Sorry for the huge footer that my company insists on appending.... not
much I can do about it ...)
-Nick
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
--
To unsubscribe, e-mail: <mailto:turbine-maven-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-maven-user-help@;jakarta.apache.org>
