Maven build doesn't work

[GoogleCodeExporter]

What steps will reproduce the problem?
1. checkout source from google code
2. mvn package

What is the expected output? What do you see instead?

expect to get a jar with the classes in it, instead, you get an empty jar

This is due to the fact that the src is in src/java instead of the maven 
default src/main/java and there's nothing in the pom to tell it to use the 
src/java directory.

Also, the pom should list the dependencies it needs at runtime  i.e. jaxb, etc

Original issue reported on code.google.com by sysbliss on 30 Jun 2010 at 5:24

[GoogleCodeExporter]

Most probably you r using maven with source structure like src\main\java and 
src\test\java, change the settings or go with this:

Create a folder main under google-checkout-java-sdk-read-only\sdk\src and move 
existing folder(java) inside it. Create folder test under src and move 
javatests inside. At the end, do mvn clean install ;)

Original comment by shail...@gmail.com on 23 Jul 2010 at 4:19

[GoogleCodeExporter]

Add the following to your <build> section in the pom then it will attempt to 
compile without all that faffing.

      <sourceDirectory>src/java</sourceDirectory>
      <testSourceDirectory>src/javatests</testSourceDirectory>

Not that it does compile that is ... looks like some dependancies are missing.

Original comment by alainmo...@gmail.com on 2 Nov 2010 at 11:51

[GoogleCodeExporter]

Even after adding the source and test directory tags, the TRUNK version doesn't 
build using Maven or just directly in Eclipse.

The following Java classes are not found within in source control (most likely 
package is com.google.checkout.sdk.domain)

- EUArea
- DemographicData
- GiftAidOptions
- EmploymentInformation

Are these new XML tags within the next version of the API/XSD that got put into 
TRUNK?

Original comment by philip.m...@gmail.com on 11 Nov 2010 at 7:23

[GoogleCodeExporter]

I have discovered (with the help of sysbliss) that the svn repository is 
horrifically messed up ... the trunk is actually a snapshot of 2.5.1 (possibly 
even 2.5.2 since there is a tag for 2.5.1 which also fails in the same way)

However if you checkout the 2.5.0 tag which contains two folders, one 'trunk' 
and another 'sdk' both of which seem to compile correctly - once you make the 
changes that sysbliss recommended (ignore my suggested changes to the pom.xml)

How do we go about getting commit privs to this repository so that we can start 
kicking it back into shape?

Original comment by googlech...@gtempaccount.com on 13 Nov 2010 at 3:30

[GoogleCodeExporter]

I'll echo the request for commit privs.. is joining this project still 
possible, or is it entirely dead?

Original comment by peterlin...@gmail.com on 19 Jan 2011 at 8:52

[GoogleCodeExporter]

Original comment by mihai.io...@gmail.com on 28 Mar 2011 at 11:43

• Changed state: Accepted

[GoogleCodeExporter]

Issue 73 has been merged into this issue.

Original comment by mihai.io...@gmail.com on 28 Mar 2011 at 11:44

[GoogleCodeExporter]

Pulled today and was unsuccessful building, same missing dependencies.    

Original comment by licht...@gmail.com on 29 Mar 2011 at 12:30

[GoogleCodeExporter]

I don't know if someone is still using this but here's a patch for fixing the 
build:

- it removes the generated java files and generates them during the build from 
the xsd file 
- it moves the tests into the right folder to be picked up by the maven 
surefire plugin

Best regards,
Robin

Original comment by robin.br...@gmail.com on 22 Mar 2012 at 7:35

Attachments:

• fix-build.patch.gz