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

[Chris H.]

Are there any other files lingering in the forge directory such as "release.properties" or pom.xml.backup? Check the version number of forge that appears in the pom.xml. It may have been iterated to 1.0.0. It should be 1.0.0-SNAPSHOT. Make sure to revert the pom.xml if that is the case. The line in the error log saying "[INFO] Building Forge 1.0.0" does not look right. It should say "[INFO] Building Forge 1.0.0-SNAPSHOT" at that point. Is there a way to communicate in realtime? You can PM me with contact info if you'd like.

`
My pom.xml file in my local ForgeSVN project states:

Code: Select all

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>forge</groupId>
    <artifactId>forge</artifactId>
    <packaging>jar</packaging>
    <name>Forge</name>
    <version>1.0.0</version>

[jendave]

Your pom.xml needs to be reverted back to what is in SVN. The failed release:prepare release:perform, stripped off the "SNAPSHOT" but was not able to complete the build. I was able to replicate the same error you had and had to rollback my pom.xml to the SVN version.

[Chris H.]

Are there any other files lingering in the forge directory such as "release.properties" or pom.xml.backup? Check the version number of forge that appears in the pom.xml. It may have been iterated to 1.0.0. It should be 1.0.0-SNAPSHOT. Make sure to revert the pom.xml if that is the case. The line in the error log saying "[INFO] Building Forge 1.0.0" does not look right. It should say "[INFO] Building Forge 1.0.0-SNAPSHOT" at that point. Is there a way to communicate in realtime? You can PM me with contact info if you'd like.

`
My pom.xml file in my local ForgeSVN project states:

Code: Select all

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>forge</groupId>
    <artifactId>forge</artifactId>
    <packaging>jar</packaging>
    <name>Forge</name>
    <version>1.0.0</version>

`
OK, I figured out how to revert the pom.xml file and I opened it in Eclipse and it now says:

Code: Select all

<version>1.0.0-SNAPSHOT</version>

`
Let me try this again as it appears that I am getting closer to success.

[Chris H.]

This is good actually. Your pom.xml needs to revert back to what is in SVN. The failed release:prepare release:perform, stripped off the "SNAPSHOT" but was not able to complete the build. I was able to replicate the same error you had and had to rollback my pom.xml to the SVN version.

`
Agreed, solvable problems are a good thing.

[jendave]

Let me try this again as it appears that I am getting closer to success.

I appreciate your patience. I'll admit that Maven has a steep learning/setup curve, but once it gets going, Maven is a great build tool.

[Chris H.]

Just o let you know, if there were a problem with your authentication with Google, you would receive message like this:

Code: Select all

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project forge: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: Commit failed (details follow):
[ERROR] svn: MKACTIVITY of '/svn/!svn/act/995dddf5-f489-4d34-a77d-35bf02a34e78': authorization failed: Could not authenticate to server: rejected Basic challenge (https://cardforge.googlecode.com)


`
Yep, I just got that message so apparently my GoogleCode.com Password is not being accepted.

I went to my GoogleCode.com -> profile -> settings and copied what was listed on this page. So I will now try the gmail password.

[jendave]

Remember to do the 'mvn clean release:clean' and revert the pom.xml file. I am concerned that something else is wrong. The 'GoogleCode.com -> profile -> settings' username and password should work. Maybe the settings.xml file is not getting picked up. The settings.xml file should be in your /Users/yourname/.m2 directory. Also double check your username in the settings.xml file. I had to include "@gmail.com" on the end for it to work.

[jendave]

If you are still having problems do a

Code: Select all

 mvn help:effective-settings

This will report the settings.xml that maven is using. It should show your google creds

[Chris H.]

If you are still having problems do a

Code: Select all

 mvn help:effective-settings

This will report the settings.xml that maven is using. It should show your google creds

`
looks good to me but I might be missing something...

Code: Select all

[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Forge 1.0.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-help-plugin:2.1.1:effective-settings (default-cli) @ forge ---
[INFO]
Effective user-specific configuration settings:

<?xml version="1.0" encoding="UTF-8"?>
<!-- ====================================================================== -->
<!--                                                                        -->
<!-- Generated by Maven Help Plugin on 2011-06-08T12:47:05                  -->
<!-- See: http://maven.apache.org/plugins/maven-help-plugin/                -->
<!--                                                                        -->
<!-- ====================================================================== -->

<!-- ====================================================================== -->
<!--                                                                        -->
<!-- Effective Settings for 'chrish' on 'Macintosh.local'             -->
<!--                                                                        -->
<!-- ====================================================================== -->

<settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd">
  <localRepository xmlns="http://maven.apache.org/SETTINGS/1.1.0">/Users/chrish/.m2/repository</localRepository>
  <servers xmlns="http://maven.apache.org/SETTINGS/1.1.0">
    <server>
      <username>chris.mtg.h@gmail.com</username>
      <password>***</password>
      <id>googlecode</id>
    </server>
  </servers>
  <pluginGroups xmlns="http://maven.apache.org/SETTINGS/1.1.0">
    <pluginGroup>org.apache.maven.plugins</pluginGroup>
    <pluginGroup>org.codehaus.mojo</pluginGroup>
  </pluginGroups>
</settings>

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.418s
[INFO] Finished at: Wed Jun 08 12:47:05 EDT 2011
[INFO] Final Memory: 6M/81M
[INFO] ------------------------------------------------------------------------

[jendave]

Ok. That looks good. You may want to make sure the command line SVN is properly authenticating. Try using the terminal window and going to the forge directory and trying

Code: Select all

svn update

It should just update. Sometimes however, it will ask for accept, deny, accept permanently? If so, accept permanently "p".

[jendave]

On second thought, you have to do a 'svn commit'. Ugh. that may be a bit trickier

[Chris H.]

Ok. That looks good. You may want to make sure the command line SVN is properly authenticating. Try using the terminal window and going to the forge directory and trying

Code: Select all

svn update

It should just update. Sometimes however, it will ask for accept, deny, accept permanently? If so, accept permanently "p".

`
I ran that command without any problems:

Macintosh:ForgeSVN chrish$ svn update
At revision 9397.
Macintosh:ForgeSVN chrish$

[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.

Are you able to do a 'svn commit' from the command line?

[jendave]

On the svn commit, you will need to modify a file and then try to commit it to SVN. If you do 'svn commit' and there are no files to commit it will not do/test anything.

[jendave]

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.