Closed GoogleCodeExporter closed 9 years ago
I take that bake; pom.xml from default branch has only the one broken
dependency;
from store branch, there are 5 broken dependencies: artifactIds gdata-sites,
gdata-
sites-meta, gdata-spreadsheet-meta, gdata-client-meta and jtidy are all broken.
Original comment by jamezpol...@gmail.com
on 29 Sep 2009 at 6:11
I've just realised that there were more wrong dependencies than I had realised.
Everything listed under <groupId>com.google.gdata</groupId> is invalid;
http://repo1.maven.org/maven2/com/google has no subfolder gdata.
I hadn't noticed earlier as I've manually installed some of these dependencies
(by
downloading and unpacking http://gdata-java-client.googlecode.com/files/gdata-
src.java-1.38.0.zip and then pointing maven at the relevant jars)
Original comment by jamezpol...@gmail.com
on 29 Sep 2009 at 6:53
It turns out that only a small change is required in the pom.xml in the store
branch:
polleyj@ppgnte-ubiq43:~/src/gcode/google-sites-liberation$ hg diff
diff -r 66a17bc52273 pom.xml
--- a/pom.xml Fri Sep 25 19:13:27 2009 -0500
+++ b/pom.xml Tue Sep 29 17:29:17 2009 +1000
@@ -7,7 +7,7 @@
<artifactId>google</artifactId>
<version>1</version>
</parent>
- <groupId>com.google.gdata</groupId>
+ <groupId>com.google.sites</groupId>
<artifactId>google-sites-liberation</artifactId>
<name>Google Sites Liberation</name>
<version>1.0</version>
@@ -145,9 +145,9 @@
<version>1.4.1</version>
</dependency>
<dependency>
- <groupId>jtidy</groupId>
- <artifactId>jtidy</artifactId>
- <version>r820</version>
+ <groupId>org.hibernate</groupId>
+ <artifactId>jtidy-r8</artifactId>
+ <version>21122004</version>
<optional>false</optional>
</dependency>
</dependencies>
polleyj@ppgnte-ubiq43:~/src/gcode/google-sites-liberation$
However, this assumes that you've installed by hand the many dependencies from
com.google.gdata. This should be noted in the build instructions, when they are
created.
Original comment by jamezpol...@gmail.com
on 29 Sep 2009 at 7:32
All of the missing dependencies are in the locally checked in repository. It
is a known
issue that they are not in the central repository, but not necessarily one that
should be
assigned to this project. We hope to work with that team to get their jars
checked in.
Original comment by gk5...@kickstyle.net
on 1 Oct 2009 at 8:30
This was actually a simple enough thing to fix, so I just added the reference
to the local
repository in the pom for the time being.
Original comment by gk5...@kickstyle.net
on 1 Oct 2009 at 9:59
Original comment by gk5...@kickstyle.net
on 1 Oct 2009 at 9:59
Original issue reported on code.google.com by
jamezpol...@gmail.com
on 29 Sep 2009 at 6:05