Be sure to issue
svn update
before the "mvn release:perform". This can fix some types of errors,
even though it prints nothing and an "svn status" command appears to
show the project up to date.
-Ken
Chris Graham wrote:
Ok, it is attempting to check out this:
http://svn.warpspeed.com.au/
e the 'svn move ...' command to rename the directory or did
you do it directly on the file system for your working copy?
If you did the second your working copy will not have correct subversion
metadata.
Ken Tanaka wrote:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I did use 'svn move src/main/conf src/main/config' for the rename.
(Although I have been caught by using the regular mv before.)
-Ken
Dennis Lundberg wrote:
Did you use the 'svn move ...' command to rename the directory or did
you do it directly on the file system for your working copy?
If yo
Hi,
I had an error using mvn release:prepare after I had created a
src/main/conf directory under SubVersion, then renamed it
src/main/config to match the Maven 2 convention. I'm not sure if I'm not
following a Maven or SubVersion convention, or if this is a bug.
The workaround, noted in the
Geoffrey Wiseman wrote:
On Fri, Aug 1, 2008 at 11:00 AM, DOMINGUEZ Felipe <
[EMAIL PROTECTED]> wrote:
I am new to Maven, and I am a bit confuse about the porpuse of directory
src/main/config porpuse
...
Can any body clarify the usage of src/main/config and what is maven
approach f
I was thinking the same thing myself. I searched at the archive
http://www.nabble.com/Maven---Users-f178.html
for "timestamp" and the one of the better threads seems to be
http://www.nabble.com/Can-I-get-a-timestamp--tf3183791s177.html#a8836362
-Ken
Wayne Fay wrote:
This comes up pretty often,
I recommend installing with a version number. If the jar is version 2.3,
but they released it as just "useful.jar", I would install it as
"useful-2.3.jar"
If their website or documentation doesn't give a version, but a release
date, you might use "useful-2006.01.23.jar".
Failing all that, you can
opment cycle and the use of plugins for
> extensibility. For all other stuff I missed, just consult 'em here in the
> mailing list. :)
>
> Cheers!
> Nap
>
> On 3/1/06, Ken Tanaka <[EMAIL PROTECTED]> wrote:
>
>> I have a documentation question:
>>
>&g
I have a documentation question:
At the bottom of the page
http://maven.apache.org/using/bestpractices.html
is a section called "Getting ready for Maven 2." I take this to mean
that the page above is for Maven 1. Does any of it apply to Maven 2?
Thanks,
Ken
--
= Enterprise Data Services Divisio
I'm new to maven and didn't find this in the archive, but it seems that
${basedir} is not documented. It seems to be set to the directory of the
project.xml file. Is this always the case? and are there
reasons/techniques to change basedir?
I eventually tried adding to project.xml:
erro
10 matches
Mail list logo
