Maven build file - generation of OSX, Windows, Linux files

[Chris H.]

I waited for several new commits to be made by other people and I entered the

Code: Select all

svn update

`
and it looks like I can update without problems:

Code: Select all

Macintosh:ForgeSVN chrish$ svn update
U    src/forge/card/cardFactory/CardFactory_Sorceries.java
U    src/forge/card/cardFactory/CardFactoryUtil.java
U    src/forge/card/abilityFactory/AbilityFactory_Copy.java
A    res/cardsfolder/sway_of_the_stars.txt
A    res/cardsfolder/lyzolda_the_blood_witch.txt
U    res/cardsfolder/slumbering_tora.txt
U    res/cardsfolder/rite_of_replication.txt
Updated to revision 9400.
Macintosh:ForgeSVN chrish$


[Chris H.]

OK, I made a small edit to the CHANGES.txt file and then I did a

Code: Select all

svn update

`
command and get the following, hope it helps:

Code: Select all

Macintosh:ForgeSVN chrish$ svn update
U    src/forge/card/cardFactory/CardFactory_Sorceries.java
U    src/forge/card/cardFactory/CardFactoryUtil.java
U    src/forge/card/abilityFactory/AbilityFactory_Copy.java
A    res/cardsfolder/sway_of_the_stars.txt
A    res/cardsfolder/lyzolda_the_blood_witch.txt
U    res/cardsfolder/slumbering_tora.txt
U    res/cardsfolder/rite_of_replication.txt
Updated to revision 9400.
Macintosh:ForgeSVN chrish$ svn commit
svn: Commit failed (details follow):
svn: Could not use external editor to fetch log message; consider setting the $SVN_EDITOR environment variable or using the --message (-m) or --file (-F) options
svn: None of the environment variables SVN_EDITOR, VISUAL or EDITOR are set, and no 'editor-cmd' run-time configuration option was found
Macintosh:ForgeSVN chrish$


[Chris H.]

This may not help and it may provide one too many data points and I apologize in advance if this is not useful.

Over the last several days I have been getting a lot of these when I attempt to synchronize with the SVN using Eclipse:

Error validating server certificate for https://cardforge.googlecode.com:443:
- Unknown certificate issuer
Fingerprint: da:b3:df:aa:55:73:ac:65:04:70:78:8e:ed:dd:a9:be:40:a8:64:81
Distinguished name: Google Inc, US

[jendave]

Ok. Good. try

Code: Select all

svn commit -m "Test Run"

That will try to commit a file with "Test Run" as the comment

[Chris H.]

Hmm. Not good. Everything looks correct yet you are not connecting to SVN from Maven. Could you send me a copy of the Maven output? At least the last few pages. at this point, I will have to hope something pops out.

`
Give me the exact commands that you want me to enter into the terminal after I CD to my ForgeSVN project folder.

I will pm you the entire log from the terminal. There may of may not be anything there for you to see but we might as well try.

I think we are getting close to figuring this out. It is a shame that it is turning into such a puzzle.

[jendave]

This may not help and it may provide one too many data points and I apologize in advance if this is not useful.

Over the last several days I have been getting a lot of these when I attempt to synchronize with the SVN using Eclipse:

Error validating server certificate for https://cardforge.googlecode.com:443:
- Unknown certificate issuer
Fingerprint: da:b3:df:aa:55:73:ac:65:04:70:78:8e:ed:dd:a9:be:40:a8:64:81
Distinguished name: Google Inc, US

Yes. This is helpful. It shows that indeed your connection to SVN is broken. I have seen you make commits however. How often do you get this error?

[Chris H.]

Ok. Good. try

Code: Select all

svn commit -m "Test Run"

That will try to commit a file with "Test Run" as the comment

`
OK, this causes the following dialog box to appear asking a good question in reference to my keychain:

`

[jendave]

Hmm. Not good. Everything looks correct yet you are not connecting to SVN from Maven. Could you send me a copy of the Maven output? At least the last few pages. at this point, I will have to hope something pops out.

`
Give me the exact commands that you want me to enter into the terminal after I CD to my ForgeSVN project folder.

I will pm you the entire log from the terminal. There may of may not be anything there for you to see but we might as well try.

I think we are getting close to figuring this out. It is a shame that it is turning into such a puzzle.

you may as well do a svn update and do the full

Code: Select all

mvn -U clean install release:prepare release:perform

Send me the resultant output. Leave out the "--batch-mode". It will require you to hit <return> a few times in order to accept some defaults, but I want to eliminate it as a potential problem.

[jendave]

Ok. Good. try

Code: Select all

svn commit -m "Test Run"

That will try to commit a file with "Test Run" as the comment

`
OK, this causes the following dialog box to appear asking a good question in reference to my keychain:

`

Click "always Allow" You may have to type in your Mac login password (not google)

[Chris H.]

This may not help and it may provide one too many data points and I apologize in advance if this is not useful.

Over the last several days I have been getting a lot of these when I attempt to synchronize with the SVN using Eclipse:

Error validating server certificate for https://cardforge.googlecode.com:443:
- Unknown certificate issuer
Fingerprint: da:b3:df:aa:55:73:ac:65:04:70:78:8e:ed:dd:a9:be:40:a8:64:81
Distinguished name: Google Inc, US

Yes. This is helpful. It shows that indeed your connection to SVN is broken. I have seen you make commits however. How often do you get this error?

`
Once or twice a month I will get a few of these in a row and I can either accept them temporarily or permanently. I get a few of these in a row and then several weeks will go by without any of these showing up.

This happens as a somewhat rare event given the number of commits that I make. They started shortly after I received commit status from Dennis.

[Chris H.]

Click "always Allow" You may have to type in your Mac login password (not google)

`
OK, the commit went through and is now rev 9402.

Code: Select all

Macintosh:ForgeSVN chrish$ svn commit -m "Test Run"
Sending        CHANGES.txt
Transmitting file data .
Committed revision 9402.
Macintosh:ForgeSVN chrish$


[jendave]

Ok. Let's try this again

Code: Select all

mvn clean install release:prepare release:perform

you will have to hit <return> a few times to accept the default version numbers for the release (hopefully it gets that far)

[Chris H.]

Ok. Let's try this again

Code: Select all

mvn clean install release:prepare release:perform

you will have to hit <return> a few times to accept the default version numbers for the release (hopefully it gets that far)

`
I got far enough to hit return a few times. Let me leave the list from the terminal here since a pm may not show up until much latter.

I will have to zip the text first as it is too long for a message.

[Chris H.]

you may also want to look at this page
http://mszalbach.blogspot.com/2011/02/m ... it_05.html

You can pass your username and password via the command line. You may have to look in you $HOME/.subversion/config file to check that your password is not being stored somewhere else.

`
Found the config file that you mentioned and it appears that the username and password may be stored in the keychain?

Code: Select all

### This file configures various client-side behaviors.
###
### The commented-out examples below are intended to demonstrate
### how to use this file.

### Section for authentication and authorization customizations.
[auth]
### Set password stores used by Subversion. They should be
### delimited by spaces or commas. The order of values determines
### the order in which password stores are used.
### Valid password stores:
###   gnome-keyring        (Unix-like systems)
###   kwallet              (Unix-like systems)
###   keychain             (Mac OS X)
###   windows-cryptoapi    (Windows)
# password-stores = keychain
###
### The rest of this section in this file has been deprecated.
### Both 'store-passwords' and 'store-auth-creds' can now be
### specified in the 'servers' file in your config directory.
### Anything specified in this section is overridden by settings
### specified in the 'servers' file.
###
### Set store-passwords to 'no' to avoid storing passwords in the
### auth/ area of your config directory.  It defaults to 'yes',
### but Subversion will never save your password to disk in
### plaintext unless you tell it to (see the 'servers' file).
### Note that this option only prevents saving of *new* passwords;
### it doesn't invalidate existing passwords.  (To do that, remove
### the cache files by hand as described in the Subversion book.)
# store-passwords = no
### Set store-auth-creds to 'no' to avoid storing any subversion
### credentials in the auth/ area of your config directory.
### It defaults to 'yes'.  Note that this option only prevents
### saving of *new* credentials;  it doesn't invalidate existing
### caches.  (To do that, remove the cache files by hand.)
# store-auth-creds = no

### Section for configuring external helper applications.
[helpers]
### Set editor-cmd to the command used to invoke your text editor.
###   This will override the environment variables that Subversion
###   examines by default to find this information ($EDITOR,
###   et al).
# editor-cmd = editor (vi, emacs, notepad, etc.)
### Set diff-cmd to the absolute path of your 'diff' program.
###   This will override the compile-time default, which is to use
###   Subversion's internal diff implementation.
# diff-cmd = diff_program (diff, gdiff, etc.)
### Set diff3-cmd to the absolute path of your 'diff3' program.
###   This will override the compile-time default, which is to use
###   Subversion's internal diff3 implementation.
# diff3-cmd = diff3_program (diff3, gdiff3, etc.)
### Set diff3-has-program-arg to 'yes' if your 'diff3' program
###   accepts the '--diff-program' option.
# diff3-has-program-arg = [yes | no]
### Set merge-tool-cmd to the command used to invoke your external
### merging tool of choice. Subversion will pass 4 arguments to
### the specified command: base theirs mine merged
# merge-tool-cmd = merge_command

### Section for configuring tunnel agents.
[tunnels]
### Configure svn protocol tunnel schemes here.  By default, only
### the 'ssh' scheme is defined.  You can define other schemes to
### be used with 'svn+scheme://hostname/path' URLs.  A scheme
### definition is simply a command, optionally prefixed by an
### environment variable name which can override the command if it
### is defined.  The command (or environment variable) may contain
### arguments, using standard shell quoting for arguments with
### spaces.  The command will be invoked as:
###   <command> <hostname> svnserve -t
### (If the URL includes a username, then the hostname will be
### passed to the tunnel agent as <user>@<hostname>.)  If the
### built-in ssh scheme were not predefined, it could be defined
### as:
# ssh = $SVN_SSH ssh
### If you wanted to define a new 'rsh' scheme, to be used with
### 'svn+rsh:' URLs, you could do so as follows:
# rsh = rsh
### Or, if you wanted to specify a full path and arguments:
# rsh = /path/to/rsh -l myusername
### On Windows, if you are specifying a full path to a command,
### use a forward slash (/) or a paired backslash (\\) as the
### path separator.  A single backslash will be treated as an
### escape for the following character.

### Section for configuring miscelleneous Subversion options.
[miscellany]
### Set global-ignores to a set of whitespace-delimited globs
### which Subversion will ignore in its 'status' output, and
### while importing or adding files and directories.
### '*' matches leading dots, e.g. '*.rej' matches '.foo.rej'.
# global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo
#   *.rej *~ #*# .#* .*.swp .DS_Store
### Set log-encoding to the default encoding for log messages
# log-encoding = latin1
### Set use-commit-times to make checkout/update/switch/revert
### put last-committed timestamps on every file touched.
# use-commit-times = yes
### Set no-unlock to prevent 'svn commit' from automatically
### releasing locks on files.
# no-unlock = yes
### Set mime-types-file to a MIME type registry file, used to
### provide hints to Subversion's MIME type auto-detection
### algorithm.
# mime-types-file = /path/to/mime.types
### Set preserved-conflict-file-exts to a whitespace-delimited
### list of patterns matching file extensions which should be
### preserved in generated conflict file names.  By default,
### conflict files use custom extensions.
# preserved-conflict-file-exts = doc ppt xls od?
### Set enable-auto-props to 'yes' to enable automatic properties
### for 'svn add' and 'svn import', it defaults to 'no'.
### Automatic properties are defined in the section 'auto-props'.
# enable-auto-props = yes
### Set interactive-conflicts to 'no' to disable interactive
### conflict resolution prompting.  It defaults to 'yes'.
# interactive-conflicts = no

### Section for configuring automatic properties.
[auto-props]
### The format of the entries is:
###   file-name-pattern = propname[=value][;propname[=value]...]
### The file-name-pattern can contain wildcards (such as '*' and
### '?').  All entries which match (case-insensitively) will be
### applied to the file.  Note that auto-props functionality
### must be enabled, which is typically done by setting the
### 'enable-auto-props' option.
# *.c = svn:eol-style=native
# *.cpp = svn:eol-style=native
# *.h = svn:eol-style=native
# *.dsp = svn:eol-style=CRLF
# *.dsw = svn:eol-style=CRLF
# *.sh = svn:eol-style=native;svn:executable
# *.txt = svn:eol-style=native
# *.png = svn:mime-type=image/png
# *.jpg = svn:mime-type=image/jpeg
# Makefile = svn:eol-style=native

[jendave]

no obvious problems from the output. It is definitely a problem with SVN not Maven however.
At the very least, you have the two built packages in your target directory.

Try

Code: Select all

mvn clean release:clean
Revert the changed pom.xml file 'svn revert pom.xml' should do it.
mvn clean install release:prepare release:perform -Dusername="<user>" -Dpassword="<pw>"
where the username and password are you googlecode creds. I would use the "" since you will have an '@' in the username

Also, do you mind if I do a release to CardForge Google? It works on my GoogleCode site "http://arcane.googlecode.com" but I noticed a discrepancy between my Keychain settings for both sites. I would want to do a test.