If you have problems with the build on windows it might be due to
tools.jar
If so, I have seen a fix for that in jackrabbit, I will be online
from 8pm GMT+1 tonight, so if you attach the log of
mvn -X
or
mvn -X -Prun
depending on which one fails I can have a look, and see if I cant fix
it.
Ian
On 25 Apr 2008, at 16:58, Cassie wrote:
it would be great if you could try this patch on windows:
https://issues.apache.org/jira/browse/SHINDIG-207
this is a further cleanup by Ian Boston which will change the way
we build
and run for hopefully the last time.
once patched, i believe in the base java dir you just:
mvn
mvn -Prun
this will probably be checked in soon, so let's make sure it works for
windows.
thanks for your help!
- Cassie
On Fri, Apr 25, 2008 at 5:48 PM, Michael Angerman
<[EMAIL PROTECTED]> wrote:
Cassie,
Thanks for the heads up on common directory, and its future use...
Turns out I do have a Windows machine and YES I am seeing the
problem you mention...
I will track down the JIRA issue number -- and see if I can figure
out
what the problem may be... Deleting the common directory and its
dependencies fixed the build problem I was seeing on Windows, so
I will research further and see what I come up with...
This has been working for me and others and has been failing on
windows
machines. We have a jira filed for the windows issue and will
fix it onc
we
know what the problem is.
On Fri, Apr 25, 2008 at 2:15 AM, Cassie <[EMAIL PROTECTED]> wrote:
Michael - The common directory is a new directory we are about to
put
code
in. Right now the social-api module depends on the gadgets module
which
is
bad. Once we do some refactoring there will be code in the common
directory
and the dependencies will be cleaned up.
Anyway, this shouldn't cause you any problems.. and if it is, we
need to
fix
the real problem instead of removing the common dependency.
This has been working for me and others and has been failing on
windows
machines. We have a jira filed for the windows issue and will fix
it onc
we
know what the problem is.
Thanks.
- Cassie
On Fri, Apr 25, 2008 at 6:45 AM, Michael Angerman
<[EMAIL PROTECTED]>
wrote:
In a previous post about one hour ago,
I showed where the current instructions where breaking,
so I decided to fix the problem by doing the following...
The following steps work on Revision 651482
I am able to get the build to work by doing the following...
Delete the common directory -- there is NO code in there anyway...
java/pom.xml REMOVE <module>common</module>
gadgets/pom.xml REMOVE
<dependency>
<version>1-SNAPSHOT</version>
<groupId>${pom.groupId}</groupId>
<artifactId>shindig-common</artifactId>
</dependency>
social-api/pom.xml REMOVE
<dependency>
<version>1-SNAPSHOT</version>
<groupId>${pom.groupId}</groupId>
<artifactId>shindig-common</artifactId>
</dependency>
Then do the following steps to get the build to work and the
server to
come
up...
*Just to be on the safe side for testing
completely delete your maven repository
before starting this process....
*
cd java
mvn package
cd gadgets
mvn jetty:run-war
At this point I ran all of the samples and they worked fine...
Thanks,
Michael I Angerman
Albuquerque, New Mexico
