You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Brian Eaton <be...@google.com> on 2008/04/21 19:34:14 UTC
how scary is the build now?
I've avoided looking at the Shindig build for the past week or so. Is
the refactoring over? Do things more or less work again?
Re: how scary is the build now?
Posted by Raymond Auge <ra...@liferay.com>.
+1
:)
On Mon, 2008-04-21 at 20:18 +0200, Santiago Gala wrote:
> El lun, 21-04-2008 a las 10:34 -0700, Brian Eaton escribió:
> > I've avoided looking at the Shindig build for the past week or so. Is
> > the refactoring over? Do things more or less work again?
>
> LOL :) (/me roughly did the same, and I'm thinking about raising my head
> off the parapet and take a look too)
>
Raymond Augé
Software Engineer
Liferay, Inc.
Enterprise. Open Source. For Life.
Re: how scary is the build now?
Posted by Ross Gardler <rg...@apache.org>.
I'm pleased to report that the build worked for me on my windows +
Cygwin test machine (this was Windows 2000 though - yes, I still have
one of those, I love the blue screens ;-).
Ross
Louis Ryan wrote:
> Sorry about all that, I was pretty sure I was up to date ...
>
> On Tue, Apr 22, 2008 at 8:02 AM, Ross Gardler <rg...@apache.org> wrote:
>
>> Tupshin Harper wrote:
>>
>>> Ross Gardler wrote:
>>>
>>>> Failed tests:
>>>> testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
>>>>
>>>> Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] There are test failures.
>>>>
>>>>
>>>>
>>> I just tried this on both Windows (first), and Linux (second). I
>>> experienced that exact problem when building on Windows Vista, and had no
>>> problem building on Linux, so unless there was a checkin in between my
>>> attempts on the two platforms, it looks like a OS specific problem.
>>>
>>
>> Ok, thanks for the info. I'll track down the problem soon and provide a
>> patch for windows machines.
>>
>> Ross
>>
>
Re: how scary is the build now?
Posted by Louis Ryan <lr...@google.com>.
Sorry about all that, I was pretty sure I was up to date ...
On Tue, Apr 22, 2008 at 8:02 AM, Ross Gardler <rg...@apache.org> wrote:
> Tupshin Harper wrote:
>
> > Ross Gardler wrote:
> >
> > >
> > > Failed tests:
> > > testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
> > >
> > > Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
> > >
> > > [INFO]
> > > ------------------------------------------------------------------------
> > > [ERROR] BUILD FAILURE
> > > [INFO]
> > > ------------------------------------------------------------------------
> > > [INFO] There are test failures.
> > >
> > >
> > >
> > I just tried this on both Windows (first), and Linux (second). I
> > experienced that exact problem when building on Windows Vista, and had no
> > problem building on Linux, so unless there was a checkin in between my
> > attempts on the two platforms, it looks like a OS specific problem.
> >
>
>
> Ok, thanks for the info. I'll track down the problem soon and provide a
> patch for windows machines.
>
> Ross
>
Re: how scary is the build now?
Posted by Ross Gardler <rg...@apache.org>.
Tupshin Harper wrote:
> Ross Gardler wrote:
>>
>> Failed tests:
>> testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
>>
>> Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] There are test failures.
>>
>>
>
> I just tried this on both Windows (first), and Linux (second). I
> experienced that exact problem when building on Windows Vista, and had
> no problem building on Linux, so unless there was a checkin in between
> my attempts on the two platforms, it looks like a OS specific problem.
Ok, thanks for the info. I'll track down the problem soon and provide a
patch for windows machines.
Ross
Re: how scary is the build now?
Posted by Tupshin Harper <th...@livejournalinc.com>.
Ross Gardler wrote:
>
> Failed tests:
> testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
>
> Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
>
I just tried this on both Windows (first), and Linux (second). I
experienced that exact problem when building on Windows Vista, and had
no problem building on Linux, so unless there was a checkin in between
my attempts on the two platforms, it looks like a OS specific problem.
-Tupshin
Re: how scary is the build now?
Posted by JiWoong Chung <op...@gmail.com>.
In such case, I usually skip the test
using
mvn -Dmaven.test.skip=true package
I think that kinds of failure only happens in windows. It works well with
ubuntu Feisty
Is there any problem in CachedContentFetcherTest ?
- Jiwoong Chung
2008/4/22 Ross Gardler <rg...@apache.org>:
> Cassie wrote:
>
> > I checked in the last piece today and updated all of the READMEs.
> > Everything is stable and the following instructions are what you want:
> >
> > cd java
> > mvn package
> > cd gadgets (or social-api or server)
> > mvn jetty:run-war
> >
> > jetty will run in any of the three java dirs. /gadgets will build the
> > gadget rendering server, /social-api will build the social data aka
> > restful api server, and /server will build both. Use /server to run
> > the samplecontainer.
> >
> > Thanks for your patience while we worked it out :)
> >
>
> Hmmm...
>
> It's not worked out for me, any hints on the below build...
>
> $ pwd
> /cygdrive/c/projects/shindig/java/gadgets
>
> $ svn up
> At revision 650322.
>
> $ svn st
> [blank response]
>
> $ mvn package
> [INFO] Scanning for projects...
> [INFO] -----------------------------------------------------------------
> ---
> [INFO] Building Apache Shindig Java Gadget Server
> [INFO] task-segment: [package]
>
> <snip/>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
>
> <snip/>
>
> Results :
>
> Failed tests:
> testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
>
> Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
>
>
Re: how scary is the build now?
Posted by Santiago Gala <sa...@gmail.com>.
El mar, 22-04-2008 a las 00:59 +0100, Ross Gardler escribió:
> Cassie wrote:
> > I checked in the last piece today and updated all of the READMEs.
> > Everything is stable and the following instructions are what you want:
> >
> > cd java
> > mvn package
> > cd gadgets (or social-api or server)
> > mvn jetty:run-war
> >
> > jetty will run in any of the three java dirs. /gadgets will build the
> > gadget rendering server, /social-api will build the social data aka
> > restful api server, and /server will build both. Use /server to run
> > the samplecontainer.
> >
> > Thanks for your patience while we worked it out :)
>
> Hmmm...
>
> It's not worked out for me, any hints on the below build...
>
> $ pwd
> /cygdrive/c/projects/shindig/java/gadgets
>
> $ svn up
> At revision 650322.
>
> $ svn st
> [blank response]
>
> $ mvn package
> [INFO] Scanning for projects...
> [INFO] -----------------------------------------------------------------
> ---
> [INFO] Building Apache Shindig Java Gadget Server
> [INFO] task-segment: [package]
>
> <snip/>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
>
> <snip/>
>
> Results :
>
> Failed tests:
> testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
>
> Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
>
A different one here:
mvn clean
...
cd java
mvn package
...
/home/sgala/newcode/git-shindig3/java/social-api/src/main/java/org/apache/shindig/social/samplecontainer/XmlStateFileFetcher.java:[6,33] cannot find symbol
symbol : class RemoteContentFetcher
location: package org.apache.shindig.gadgets
Regards
Santiago
--
Santiago Gala
http://memojo.com/~sgala/blog/
Re: how scary is the build now?
Posted by Ross Gardler <rg...@apache.org>.
Cassie wrote:
> I checked in the last piece today and updated all of the READMEs.
> Everything is stable and the following instructions are what you want:
>
> cd java
> mvn package
> cd gadgets (or social-api or server)
> mvn jetty:run-war
>
> jetty will run in any of the three java dirs. /gadgets will build the
> gadget rendering server, /social-api will build the social data aka
> restful api server, and /server will build both. Use /server to run
> the samplecontainer.
>
> Thanks for your patience while we worked it out :)
Hmmm...
It's not worked out for me, any hints on the below build...
$ pwd
/cygdrive/c/projects/shindig/java/gadgets
$ svn up
At revision 650322.
$ svn st
[blank response]
$ mvn package
[INFO] Scanning for projects...
[INFO] -----------------------------------------------------------------
---
[INFO] Building Apache Shindig Java Gadget Server
[INFO] task-segment: [package]
<snip/>
-------------------------------------------------------
T E S T S
-------------------------------------------------------
<snip/>
Results :
Failed tests:
testDontCache(org.apache.shindig.gadgets.CachedContentFetcherTest)
Tests run: 224, Failures: 1, Errors: 0, Skipped: 0
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
Try removing the the load on startup elements from the web.xml
oauth.xml is fetched from a URL which loops back into the server
(remote fectcher), in jetty the file servlet doesn't come up first by
default, so its not there.
Its my fault, I added load on startup to a patch I did when I was
doing some Guice config to force it to load immediately.
Ian
On 22 Apr 2008, at 11:25, Cassie wrote:
> build should be good.
> the only thing left to fix is the fact that when you run java/
> server it gets
> an exception from oauth because it can't find the oauth.xml file. I
> don't
> know why this is happening yet.
>
> - cassie
>
>
> On Tue, Apr 22, 2008 at 10:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>
>>
>> Ian
>>
>>
>>
>> On 22 Apr 2008, at 05:53, Brian Eaton wrote:
>>
>>> A couple of questions:
>>> - Anybody tried eclipse yet? I was able to import java/pom.xml as a
>>> maven project into eclipse, but needed to add a bunch of
>>> dependencies
>>> before the build would work. Am I doing something wrong, or am I
>>> just
>>> a trail blazer? I suspect it may be both.
>>>
>>
>>
>> Have you tried
>>
>> cd shindig/java
>>
>> mvn eclipse:eclipse
>>
>> and then import the projects into eclipse ?
>>
>> This will generate the .classpath and .project files correctly for
>> you.
>> When you want a new dep, add it to the pom and repeat the
>>
>> mvn eclipse:eclipse
>>
>> It also adds the transitive dependencies so is much faster than hand
>> editing eclipse properties. You can also ask it to get the source
>> jars and
>> link them into the classpath.
>>
>>
>>
>>> - I'm hating on maven. Is this the best it can do, or are we
>>> using it
>>> wrong? Things that should be simple, like updating a dependency for
>>> the project or updating the project version number, appear to
>>> require
>>> hand editing multiple pom.xml files in multiple places. I
>>> counted the
>>> phrase "1-SNAPSHOT" on 14 lines in 5 files.
>>>
>>
>> Dependencies,
>> We should have a dependency management statement in the base pom that
>> contains the version numbers of everything we use (except internal
>> references) so that we dont have to remember or update version
>> numbers.
>>
>> We might also consider putting all the standard plugin config and
>> repo
>> information in the base pom.
>>
>>
>> SNAPSHOT
>> the maven-release-plugin automates the tagging, version change,
>> release
>> process and deployment to the external maven repo.
>>
>> Not editing required
>>
>>
>> When set up properly.... it saves a huge amount of time, and makes
>> it much
>> much easier for others to use the outputs. No more chasing bugs
>> because you
>> have managed to package the wrong version of a dependency in
>> production.
>>
>>
>>
>>
Re: how scary is the build now?
Posted by Cassie <do...@google.com>.
Ah, no worries. It wouldn't have happened at all without your help :)
The good news is that it worked!
So everything should be good now...
- Cassie
On Tue, Apr 22, 2008 at 3:01 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> (I should add.... sorry )
> Ian
>
>
>
> On 22 Apr 2008, at 11:25, Cassie wrote:
>>
>> build should be good.
>> the only thing left to fix is the fact that when you run java/server it
>> gets
>> an exception from oauth because it can't find the oauth.xml file. I don't
>> know why this is happening yet.
>>
>> - cassie
>>
>>
>> On Tue, Apr 22, 2008 at 10:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>>
>>>
>>> Ian
>>>
>>>
>>>
>>> On 22 Apr 2008, at 05:53, Brian Eaton wrote:
>>>
>>>> A couple of questions:
>>>> - Anybody tried eclipse yet? I was able to import java/pom.xml as a
>>>> maven project into eclipse, but needed to add a bunch of dependencies
>>>> before the build would work. Am I doing something wrong, or am I just
>>>> a trail blazer? I suspect it may be both.
>>>>
>>>
>>>
>>> Have you tried
>>>
>>> cd shindig/java
>>>
>>> mvn eclipse:eclipse
>>>
>>> and then import the projects into eclipse ?
>>>
>>> This will generate the .classpath and .project files correctly for you.
>>> When you want a new dep, add it to the pom and repeat the
>>>
>>> mvn eclipse:eclipse
>>>
>>> It also adds the transitive dependencies so is much faster than hand
>>> editing eclipse properties. You can also ask it to get the source jars
>>> and
>>> link them into the classpath.
>>>
>>>
>>>
>>>> - I'm hating on maven. Is this the best it can do, or are we using it
>>>> wrong? Things that should be simple, like updating a dependency for
>>>> the project or updating the project version number, appear to require
>>>> hand editing multiple pom.xml files in multiple places. I counted the
>>>> phrase "1-SNAPSHOT" on 14 lines in 5 files.
>>>>
>>>
>>> Dependencies,
>>> We should have a dependency management statement in the base pom that
>>> contains the version numbers of everything we use (except internal
>>> references) so that we dont have to remember or update version numbers.
>>>
>>> We might also consider putting all the standard plugin config and repo
>>> information in the base pom.
>>>
>>>
>>> SNAPSHOT
>>> the maven-release-plugin automates the tagging, version change, release
>>> process and deployment to the external maven repo.
>>>
>>> Not editing required
>>>
>>>
>>> When set up properly.... it saves a huge amount of time, and makes it
>>> much
>>> much easier for others to use the outputs. No more chasing bugs because
>>> you
>>> have managed to package the wrong version of a dependency in production.
>>>
>>>
>>>
>>>
>
>
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
(I should add.... sorry )
Ian
On 22 Apr 2008, at 11:25, Cassie wrote:
> build should be good.
> the only thing left to fix is the fact that when you run java/
> server it gets
> an exception from oauth because it can't find the oauth.xml file. I
> don't
> know why this is happening yet.
>
> - cassie
>
>
> On Tue, Apr 22, 2008 at 10:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>
>>
>> Ian
>>
>>
>>
>> On 22 Apr 2008, at 05:53, Brian Eaton wrote:
>>
>>> A couple of questions:
>>> - Anybody tried eclipse yet? I was able to import java/pom.xml as a
>>> maven project into eclipse, but needed to add a bunch of
>>> dependencies
>>> before the build would work. Am I doing something wrong, or am I
>>> just
>>> a trail blazer? I suspect it may be both.
>>>
>>
>>
>> Have you tried
>>
>> cd shindig/java
>>
>> mvn eclipse:eclipse
>>
>> and then import the projects into eclipse ?
>>
>> This will generate the .classpath and .project files correctly for
>> you.
>> When you want a new dep, add it to the pom and repeat the
>>
>> mvn eclipse:eclipse
>>
>> It also adds the transitive dependencies so is much faster than hand
>> editing eclipse properties. You can also ask it to get the source
>> jars and
>> link them into the classpath.
>>
>>
>>
>>> - I'm hating on maven. Is this the best it can do, or are we
>>> using it
>>> wrong? Things that should be simple, like updating a dependency for
>>> the project or updating the project version number, appear to
>>> require
>>> hand editing multiple pom.xml files in multiple places. I
>>> counted the
>>> phrase "1-SNAPSHOT" on 14 lines in 5 files.
>>>
>>
>> Dependencies,
>> We should have a dependency management statement in the base pom that
>> contains the version numbers of everything we use (except internal
>> references) so that we dont have to remember or update version
>> numbers.
>>
>> We might also consider putting all the standard plugin config and
>> repo
>> information in the base pom.
>>
>>
>> SNAPSHOT
>> the maven-release-plugin automates the tagging, version change,
>> release
>> process and deployment to the external maven repo.
>>
>> Not editing required
>>
>>
>> When set up properly.... it saves a huge amount of time, and makes
>> it much
>> much easier for others to use the outputs. No more chasing bugs
>> because you
>> have managed to package the wrong version of a dependency in
>> production.
>>
>>
>>
>>
Re: how scary is the build now?
Posted by Cassie <do...@apache.org>.
build should be good.
the only thing left to fix is the fact that when you run java/server it gets
an exception from oauth because it can't find the oauth.xml file. I don't
know why this is happening yet.
- cassie
On Tue, Apr 22, 2008 at 10:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>
> Ian
>
>
>
> On 22 Apr 2008, at 05:53, Brian Eaton wrote:
>
>> A couple of questions:
>> - Anybody tried eclipse yet? I was able to import java/pom.xml as a
>> maven project into eclipse, but needed to add a bunch of dependencies
>> before the build would work. Am I doing something wrong, or am I just
>> a trail blazer? I suspect it may be both.
>>
>
>
> Have you tried
>
> cd shindig/java
>
> mvn eclipse:eclipse
>
> and then import the projects into eclipse ?
>
> This will generate the .classpath and .project files correctly for you.
> When you want a new dep, add it to the pom and repeat the
>
> mvn eclipse:eclipse
>
> It also adds the transitive dependencies so is much faster than hand
> editing eclipse properties. You can also ask it to get the source jars and
> link them into the classpath.
>
>
>
>> - I'm hating on maven. Is this the best it can do, or are we using it
>> wrong? Things that should be simple, like updating a dependency for
>> the project or updating the project version number, appear to require
>> hand editing multiple pom.xml files in multiple places. I counted the
>> phrase "1-SNAPSHOT" on 14 lines in 5 files.
>>
>
> Dependencies,
> We should have a dependency management statement in the base pom that
> contains the version numbers of everything we use (except internal
> references) so that we dont have to remember or update version numbers.
>
> We might also consider putting all the standard plugin config and repo
> information in the base pom.
>
>
> SNAPSHOT
> the maven-release-plugin automates the tagging, version change, release
> process and deployment to the external maven repo.
>
> Not editing required
>
>
> When set up properly.... it saves a huge amount of time, and makes it much
> much easier for others to use the outputs. No more chasing bugs because you
> have managed to package the wrong version of a dependency in production.
>
>
>
>
Re: how scary is the build now?
Posted by Brian Eaton <be...@google.com>.
On Thu, Apr 24, 2008 at 6:34 PM, David Primmer <da...@gmail.com> wrote:
> The issue with the gadgets project is that eclipse cannot have a
> source reference that is below it's root project folder. you can't
> tell it../../. And to fix it, you have to create an external folder
> link with a absolute path in your filesystem. As brian has done. This
> is all because the javascript and other stuff is two levels below the
> root of the eclipse project.
I didn't need to do any manual hacking, I just used the eclipse maven
plugin and said "Create project from existing source", then enabled
dependency management.
It just works.
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
If features, javascript etc had poms, mvn eclipse:eclipse might
generate project files, or it is possible to exclude items from
classpath.
Ian
On 25 Apr 2008, at 02:34, David Primmer wrote:
> I agree that with our current pom's, there's no way you can configure
> this to work in eclipse and have it be portable. Those maven commands
> will not create an eclipse project rooted in trunk/ it will make
> projects for
> /trunk/java/gadgets
> /trunk/java/social-api
> /trunk/java/common
>
> The issue with the gadgets project is that eclipse cannot have a
> source reference that is below it's root project folder. you can't
> tell it../../. And to fix it, you have to create an external folder
> link with a absolute path in your filesystem. As brian has done. This
> is all because the javascript and other stuff is two levels below the
> root of the eclipse project.
>
> The only way to solve this that I can see would be to alter our pom's
> so that a root eclipse project is created by the mvn eclipse:m2eclipse
> in trunk/ and from what i've read of the docs, that will automatically
> find the child projects and add them as sub projects in eclipse. All
> deps happy. no manual linking on every new workspace. Anybody know how
> to do that?
>
> davep
>
>
> On Thu, Apr 24, 2008 at 5:55 PM, Brian Eaton <be...@google.com>
> wrote:
>> That cut the number of errors from around 100 to 9:
>>
>> Project 'gadgets' is missing required source folder:
>> '/home/beaton/sb/shindig/config' gadgets Build path
>> Project 'gadgets' is missing required source folder:
>> '/home/beaton/sb/shindig/features' gadgets Build path
>> Project 'gadgets' is missing required source folder:
>> '/home/beaton/sb/shindig/javascript' gadgets Build path
>> Project 'shindig-server' is missing required source folder:
>> '/home/beaton/sb/shindig/config' shindig-server
>> Build path
>> Project 'shindig-server' is missing required source folder:
>> '/home/beaton/sb/shindig/features' shindig-server
>> Build path
>> Project 'shindig-server' is missing required source folder:
>> '/home/beaton/sb/shindig/javascript' shindig-server
>> Build path
>> The project cannot be built until build path errors are
>> resolved gadgets
>> The project cannot be built until build path errors are
>> resolved shindig-server
>> The project was not built since it depends on gadgets, which has
>> build
>> path errors social-api
>>
>> I don't have a strong preference for my approach to getting things
>> working in eclipse, or mvn eclipse:eclipse, or mvn
>> eclipse:m2eclipse,
>> except that mine is the only way I can get to work. =)
>>
>> Cheers,
>> Brian
>>
>>
>>
>> On Tue, Apr 22, 2008 at 1:40 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>>> Ahh, M2_REPO not defined ?
>>>
>>> you need to got to goto
>>> Preferences -> Java -> Apperance -> Build Path -> Classpath
>>> variables
>>>
>>> and then create a new variable M2_REPO pointing to
>>>
>>> the folder ~/.m2/repository
>>>
>>> Thats on Unix, I am not certain where the local Maven 2 repo is
>>> on Windows.
>>>
>>>
>>>
>>> Ian
>>>
>>>
>>>
>>>
>>>
>>> On 22 Apr 2008, at 17:16, Brian Eaton wrote:
>>>
>>>> On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>>>>
>>>>> Have you tried
>>>>>
>>>>> cd shindig/java
>>>>>
>>>>> mvn eclipse:eclipse
>>>>>
>>>>> and then import the projects into eclipse ?
>>>>>
>>>>
>>>> Yes. It doesn't work. I get bunches of 'Unbound classpath' and
>>>> 'Project X is missing required java project Y' errors.
>>>>
>>>
>>>
>>
Re: how scary is the build now?
Posted by David Primmer <da...@gmail.com>.
I agree that with our current pom's, there's no way you can configure
this to work in eclipse and have it be portable. Those maven commands
will not create an eclipse project rooted in trunk/ it will make
projects for
/trunk/java/gadgets
/trunk/java/social-api
/trunk/java/common
The issue with the gadgets project is that eclipse cannot have a
source reference that is below it's root project folder. you can't
tell it../../. And to fix it, you have to create an external folder
link with a absolute path in your filesystem. As brian has done. This
is all because the javascript and other stuff is two levels below the
root of the eclipse project.
The only way to solve this that I can see would be to alter our pom's
so that a root eclipse project is created by the mvn eclipse:m2eclipse
in trunk/ and from what i've read of the docs, that will automatically
find the child projects and add them as sub projects in eclipse. All
deps happy. no manual linking on every new workspace. Anybody know how
to do that?
davep
On Thu, Apr 24, 2008 at 5:55 PM, Brian Eaton <be...@google.com> wrote:
> That cut the number of errors from around 100 to 9:
>
> Project 'gadgets' is missing required source folder:
> '/home/beaton/sb/shindig/config' gadgets Build path
> Project 'gadgets' is missing required source folder:
> '/home/beaton/sb/shindig/features' gadgets Build path
> Project 'gadgets' is missing required source folder:
> '/home/beaton/sb/shindig/javascript' gadgets Build path
> Project 'shindig-server' is missing required source folder:
> '/home/beaton/sb/shindig/config' shindig-server Build path
> Project 'shindig-server' is missing required source folder:
> '/home/beaton/sb/shindig/features' shindig-server Build path
> Project 'shindig-server' is missing required source folder:
> '/home/beaton/sb/shindig/javascript' shindig-server Build path
> The project cannot be built until build path errors are resolved gadgets
> The project cannot be built until build path errors are resolved shindig-server
> The project was not built since it depends on gadgets, which has build
> path errors social-api
>
> I don't have a strong preference for my approach to getting things
> working in eclipse, or mvn eclipse:eclipse, or mvn eclipse:m2eclipse,
> except that mine is the only way I can get to work. =)
>
> Cheers,
> Brian
>
>
>
> On Tue, Apr 22, 2008 at 1:40 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> > Ahh, M2_REPO not defined ?
> >
> > you need to got to goto
> > Preferences -> Java -> Apperance -> Build Path -> Classpath variables
> >
> > and then create a new variable M2_REPO pointing to
> >
> > the folder ~/.m2/repository
> >
> > Thats on Unix, I am not certain where the local Maven 2 repo is on Windows.
> >
> >
> >
> > Ian
> >
> >
> >
> >
> >
> > On 22 Apr 2008, at 17:16, Brian Eaton wrote:
> >
> > > On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> > >
> > > > Have you tried
> > > >
> > > > cd shindig/java
> > > >
> > > > mvn eclipse:eclipse
> > > >
> > > > and then import the projects into eclipse ?
> > > >
> > >
> > > Yes. It doesn't work. I get bunches of 'Unbound classpath' and
> > > 'Project X is missing required java project Y' errors.
> > >
> >
> >
>
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
Ahh ok, I need to exclude config, features and javascript from the
eclipse project creation, sorry.
either m2eclipse is fine to use for those with the m2 eclipse plugin.
I have tended not to install plugins, since in other projects I am
running out of permgen space and heap when I load up eclipse
completely (permgen >512m currently).....
so my preference is eclipse:eclipse.
I am in the process of doing a patch to the poms, SHINDIG-207, so I
will try and fix this at the same time.
Ian
On 25 Apr 2008, at 01:55, Brian Eaton wrote:
> That cut the number of errors from around 100 to 9:
>
> Project 'gadgets' is missing required source folder:
> '/home/beaton/sb/shindig/config' gadgets Build path
> Project 'gadgets' is missing required source folder:
> '/home/beaton/sb/shindig/features' gadgets Build path
> Project 'gadgets' is missing required source folder:
> '/home/beaton/sb/shindig/javascript' gadgets Build path
> Project 'shindig-server' is missing required source folder:
> '/home/beaton/sb/shindig/config' shindig-server Build path
> Project 'shindig-server' is missing required source folder:
> '/home/beaton/sb/shindig/features' shindig-server Build path
> Project 'shindig-server' is missing required source folder:
> '/home/beaton/sb/shindig/javascript' shindig-server Build path
> The project cannot be built until build path errors are resolved
> gadgets
> The project cannot be built until build path errors are resolved
> shindig-server
> The project was not built since it depends on gadgets, which has build
> path errors social-api
>
> I don't have a strong preference for my approach to getting things
> working in eclipse, or mvn eclipse:eclipse, or mvn eclipse:m2eclipse,
> except that mine is the only way I can get to work. =)
>
> Cheers,
> Brian
>
> On Tue, Apr 22, 2008 at 1:40 PM, Ian Boston <ie...@tfd.co.uk> wrote:
>> Ahh, M2_REPO not defined ?
>>
>> you need to got to goto
>> Preferences -> Java -> Apperance -> Build Path -> Classpath
>> variables
>>
>> and then create a new variable M2_REPO pointing to
>>
>> the folder ~/.m2/repository
>>
>> Thats on Unix, I am not certain where the local Maven 2 repo is
>> on Windows.
>>
>>
>>
>> Ian
>>
>>
>>
>>
>>
>> On 22 Apr 2008, at 17:16, Brian Eaton wrote:
>>
>>> On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>>>
>>>> Have you tried
>>>>
>>>> cd shindig/java
>>>>
>>>> mvn eclipse:eclipse
>>>>
>>>> and then import the projects into eclipse ?
>>>>
>>>
>>> Yes. It doesn't work. I get bunches of 'Unbound classpath' and
>>> 'Project X is missing required java project Y' errors.
>>>
>>
>>
Re: how scary is the build now?
Posted by Brian Eaton <be...@google.com>.
That cut the number of errors from around 100 to 9:
Project 'gadgets' is missing required source folder:
'/home/beaton/sb/shindig/config' gadgets Build path
Project 'gadgets' is missing required source folder:
'/home/beaton/sb/shindig/features' gadgets Build path
Project 'gadgets' is missing required source folder:
'/home/beaton/sb/shindig/javascript' gadgets Build path
Project 'shindig-server' is missing required source folder:
'/home/beaton/sb/shindig/config' shindig-server Build path
Project 'shindig-server' is missing required source folder:
'/home/beaton/sb/shindig/features' shindig-server Build path
Project 'shindig-server' is missing required source folder:
'/home/beaton/sb/shindig/javascript' shindig-server Build path
The project cannot be built until build path errors are resolved gadgets
The project cannot be built until build path errors are resolved shindig-server
The project was not built since it depends on gadgets, which has build
path errors social-api
I don't have a strong preference for my approach to getting things
working in eclipse, or mvn eclipse:eclipse, or mvn eclipse:m2eclipse,
except that mine is the only way I can get to work. =)
Cheers,
Brian
On Tue, Apr 22, 2008 at 1:40 PM, Ian Boston <ie...@tfd.co.uk> wrote:
> Ahh, M2_REPO not defined ?
>
> you need to got to goto
> Preferences -> Java -> Apperance -> Build Path -> Classpath variables
>
> and then create a new variable M2_REPO pointing to
>
> the folder ~/.m2/repository
>
> Thats on Unix, I am not certain where the local Maven 2 repo is on Windows.
>
>
>
> Ian
>
>
>
>
>
> On 22 Apr 2008, at 17:16, Brian Eaton wrote:
>
> > On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> >
> > > Have you tried
> > >
> > > cd shindig/java
> > >
> > > mvn eclipse:eclipse
> > >
> > > and then import the projects into eclipse ?
> > >
> >
> > Yes. It doesn't work. I get bunches of 'Unbound classpath' and
> > 'Project X is missing required java project Y' errors.
> >
>
>
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
Ahh, M2_REPO not defined ?
you need to got to goto
Preferences -> Java -> Apperance -> Build Path -> Classpath variables
and then create a new variable M2_REPO pointing to
the folder ~/.m2/repository
Thats on Unix, I am not certain where the local Maven 2 repo is on
Windows.
Ian
On 22 Apr 2008, at 17:16, Brian Eaton wrote:
> On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>> Have you tried
>>
>> cd shindig/java
>>
>> mvn eclipse:eclipse
>>
>> and then import the projects into eclipse ?
>
> Yes. It doesn't work. I get bunches of 'Unbound classpath' and
> 'Project X is missing required java project Y' errors.
Re: how scary is the build now?
Posted by Brian Eaton <be...@google.com>.
On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> Have you tried
>
> cd shindig/java
>
> mvn eclipse:eclipse
>
> and then import the projects into eclipse ?
Yes. It doesn't work. I get bunches of 'Unbound classpath' and
'Project X is missing required java project Y' errors.
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
I have commented on 207, I will have a look at a patch for the base
pom to add plugin dependencies and check that a release would work
tomorrow (if no one else gets there first)
Ian
On 22 Apr 2008, at 18:49, Brian Eaton wrote:
> On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
>> Dependencies,
>> We should have a dependency management statement in the base pom
>> that
>> contains the version numbers of everything we use (except internal
>> references) so that we dont have to remember or update version
>> numbers.
>
> I think I figured out how to do this, patch attached:
> https://issues.apache.org/jira/browse/SHINDIG-207
>
> I also documented how I got Eclipse and maven to play nicely together.
> mvn eclipse:eclipse has never worked for me, so somebody else will
> have to document how that works.
>
>> We might also consider putting all the standard plugin config and
>> repo
>> information in the base pom.
>
> This sounds like a great idea.
>
>> SNAPSHOT
>> the maven-release-plugin automates the tagging, version change,
>> release
>> process and deployment to the external maven repo.
>>
>> Not editing required
>
> This also sounds like a great idea.
Re: how scary is the build now?
Posted by Brian Eaton <be...@google.com>.
On Tue, Apr 22, 2008 at 1:19 AM, Ian Boston <ie...@tfd.co.uk> wrote:
> Dependencies,
> We should have a dependency management statement in the base pom that
> contains the version numbers of everything we use (except internal
> references) so that we dont have to remember or update version numbers.
I think I figured out how to do this, patch attached:
https://issues.apache.org/jira/browse/SHINDIG-207
I also documented how I got Eclipse and maven to play nicely together.
mvn eclipse:eclipse has never worked for me, so somebody else will
have to document how that works.
> We might also consider putting all the standard plugin config and repo
> information in the base pom.
This sounds like a great idea.
> SNAPSHOT
> the maven-release-plugin automates the tagging, version change, release
> process and deployment to the external maven repo.
>
> Not editing required
This also sounds like a great idea.
Re: how scary is the build now?
Posted by Ian Boston <ie...@tfd.co.uk>.
Ian
On 22 Apr 2008, at 05:53, Brian Eaton wrote:
> A couple of questions:
> - Anybody tried eclipse yet? I was able to import java/pom.xml as a
> maven project into eclipse, but needed to add a bunch of dependencies
> before the build would work. Am I doing something wrong, or am I just
> a trail blazer? I suspect it may be both.
Have you tried
cd shindig/java
mvn eclipse:eclipse
and then import the projects into eclipse ?
This will generate the .classpath and .project files correctly for you.
When you want a new dep, add it to the pom and repeat the
mvn eclipse:eclipse
It also adds the transitive dependencies so is much faster than hand
editing eclipse properties. You can also ask it to get the source
jars and link them into the classpath.
>
> - I'm hating on maven. Is this the best it can do, or are we using it
> wrong? Things that should be simple, like updating a dependency for
> the project or updating the project version number, appear to require
> hand editing multiple pom.xml files in multiple places. I counted the
> phrase "1-SNAPSHOT" on 14 lines in 5 files.
Dependencies,
We should have a dependency management statement in the base pom that
contains the version numbers of everything we use (except internal
references) so that we dont have to remember or update version numbers.
We might also consider putting all the standard plugin config and
repo information in the base pom.
SNAPSHOT
the maven-release-plugin automates the tagging, version change,
release process and deployment to the external maven repo.
Not editing required
When set up properly.... it saves a huge amount of time, and makes it
much much easier for others to use the outputs. No more chasing bugs
because you have managed to package the wrong version of a dependency
in production.
Re: how scary is the build now?
Posted by Cassie <do...@google.com>.
Look's like all the breakages are just because Louis's change was
outdated. I'll fix them now...
On Tue, Apr 22, 2008 at 6:53 AM, Brian Eaton <be...@google.com> wrote:
> On Mon, Apr 21, 2008 at 3:11 PM, Cassie <do...@google.com> wrote:
>> I checked in the last piece today and updated all of the READMEs.
>> Everything is stable and the following instructions are what you want:
>>
>> cd java
>> mvn package
>> cd gadgets (or social-api or server)
>> mvn jetty:run-war
>
> Been there, done that, saw the build choke and die.
>
> There's a fix for one build break attached to
> https://issues.apache.org/jira/browse/SHINDIG-206.
>
> When I run jetty in java/gadgets, mvn jetty:run-war works. (Hooray!
> No way I'm actually going to try testing the server yet.)
>
> When I run jetty in java/social-api, mvn jetty:run-war appears to
> work, but throws a Guice exception that looks like it might be fatal:
> 1) Error at org.apache.shindig.gadgets.BasicRemoteContentFetcher.<init>(BasicRemoteContentFetcher.java:64):
> Binding to org.apache.shindig.gadgets.ContentCache not found. No
> bindings to that type were found.
>
> When I run jetty in java/server, the build chokes and dies for reasons
> I don't understand, but appear maven and/or pom related:
>
> Missing:
> ----------
> 1) org.apache.shindig:social-api:jar:1-SNAPSHOT
>
>
> A couple of questions:
> - Anybody tried eclipse yet? I was able to import java/pom.xml as a
> maven project into eclipse, but needed to add a bunch of dependencies
> before the build would work. Am I doing something wrong, or am I just
> a trail blazer? I suspect it may be both.
>
> - I'm hating on maven. Is this the best it can do, or are we using it
> wrong? Things that should be simple, like updating a dependency for
> the project or updating the project version number, appear to require
> hand editing multiple pom.xml files in multiple places. I counted the
> phrase "1-SNAPSHOT" on 14 lines in 5 files.
>
Re: how scary is the build now?
Posted by Brian Eaton <be...@google.com>.
On Mon, Apr 21, 2008 at 3:11 PM, Cassie <do...@google.com> wrote:
> I checked in the last piece today and updated all of the READMEs.
> Everything is stable and the following instructions are what you want:
>
> cd java
> mvn package
> cd gadgets (or social-api or server)
> mvn jetty:run-war
Been there, done that, saw the build choke and die.
There's a fix for one build break attached to
https://issues.apache.org/jira/browse/SHINDIG-206.
When I run jetty in java/gadgets, mvn jetty:run-war works. (Hooray!
No way I'm actually going to try testing the server yet.)
When I run jetty in java/social-api, mvn jetty:run-war appears to
work, but throws a Guice exception that looks like it might be fatal:
1) Error at org.apache.shindig.gadgets.BasicRemoteContentFetcher.<init>(BasicRemoteContentFetcher.java:64):
Binding to org.apache.shindig.gadgets.ContentCache not found. No
bindings to that type were found.
When I run jetty in java/server, the build chokes and dies for reasons
I don't understand, but appear maven and/or pom related:
Missing:
----------
1) org.apache.shindig:social-api:jar:1-SNAPSHOT
A couple of questions:
- Anybody tried eclipse yet? I was able to import java/pom.xml as a
maven project into eclipse, but needed to add a bunch of dependencies
before the build would work. Am I doing something wrong, or am I just
a trail blazer? I suspect it may be both.
- I'm hating on maven. Is this the best it can do, or are we using it
wrong? Things that should be simple, like updating a dependency for
the project or updating the project version number, appear to require
hand editing multiple pom.xml files in multiple places. I counted the
phrase "1-SNAPSHOT" on 14 lines in 5 files.
Re: how scary is the build now?
Posted by Cassie <do...@google.com>.
I checked in the last piece today and updated all of the READMEs.
Everything is stable and the following instructions are what you want:
cd java
mvn package
cd gadgets (or social-api or server)
mvn jetty:run-war
jetty will run in any of the three java dirs. /gadgets will build the
gadget rendering server, /social-api will build the social data aka
restful api server, and /server will build both. Use /server to run
the samplecontainer.
Thanks for your patience while we worked it out :)
- Cassie
On Mon, Apr 21, 2008 at 8:47 PM, Lieven Dekeyser <li...@netlog.com> wrote:
> On 21 Apr 2008, at 20:18, Santiago Gala wrote:
>
>> El lun, 21-04-2008 a las 10:34 -0700, Brian Eaton escribió:
>>>
>>> I've avoided looking at the Shindig build for the past week or so. Is
>>> the refactoring over? Do things more or less work again?
>>
>> LOL :) (/me roughly did the same, and I'm thinking about raising my head
>> off the parapet and take a look too)
>
> I've been using a revision from a few weeks ago too, but updated today after
> Cassie updated the readme files. It all seems to work fine now (guice
> modules are great!), but of course shindig trunk remains a moving target.
>
> It might be useful to create tags every now and then, especially before
> major refactoring.
>
> Lieven Dekeyser
> Desktop Application Developer
>
> Netlog NV
> Emile Braunplein 18
> B-9000 Ghent
> Belgium
>
>
>
>
Re: how scary is the build now?
Posted by Lieven Dekeyser <li...@netlog.com>.
On 21 Apr 2008, at 20:18, Santiago Gala wrote:
> El lun, 21-04-2008 a las 10:34 -0700, Brian Eaton escribió:
>> I've avoided looking at the Shindig build for the past week or so.
>> Is
>> the refactoring over? Do things more or less work again?
>
> LOL :) (/me roughly did the same, and I'm thinking about raising my
> head
> off the parapet and take a look too)
I've been using a revision from a few weeks ago too, but updated today
after Cassie updated the readme files. It all seems to work fine now
(guice modules are great!), but of course shindig trunk remains a
moving target.
It might be useful to create tags every now and then, especially
before major refactoring.
Lieven Dekeyser
Desktop Application Developer
Netlog NV
Emile Braunplein 18
B-9000 Ghent
Belgium
Re: how scary is the build now?
Posted by Santiago Gala <sa...@gmail.com>.
El lun, 21-04-2008 a las 10:34 -0700, Brian Eaton escribió:
> I've avoided looking at the Shindig build for the past week or so. Is
> the refactoring over? Do things more or less work again?
LOL :) (/me roughly did the same, and I'm thinking about raising my head
off the parapet and take a look too)
--
Santiago Gala
http://memojo.com/~sgala/blog/