Build instructions for http://sadi.googlecode.com/svn/trunk/ ?
Tim rdf
I am trying to make some headway on
http://code.google.com/p/sadi/issues/detail?id=10 (i.e., adding Sesame
support)
Are there build instructions for http://sadi.googlecode.com/svn/trunk/
somewhere (specifically for within Eclipse)?
I've looked through http://code.google.com/p/sadi/w/list, but didn't
see anything that I could use.
And I didn't see a doc/ or readme.txt in my working copy.
What I've done;
* grabbed "http://sadi.googlecode.com/svn/trunk/" from
http://code.google.com/p/sadi/source/checkout
* eclipse : File > New > Project ...
* eclipse : Project from SVN
* eclipse : Create a new repository Location
* eclipse : paste "http://sadi.googlecode.com/svn/trunk" into URL field.
* eclipse : "Advanced" tab; disable "Enable Structure Detection"
* eclipse : "Check out as a project configured using the New Project Wizard"
* eclipse : "Java Project"
* eclipse: right click "sadi.service > src > main > java > ca" in
Package Explorer "Build Path > Use As Source Folder"
at that point, things look wonky. Starting with a package error:
The declared package "ca.wilkinsonlab.sadi.service" does not
match the expected package "wilkinsonlab.sadi.service"
and plenty of failed dependencies (Jena, ca.wilkinson.*, org.apache.*, javax.*).
Thanks for your consideration.
Regards,
Tim Lebo
Luke McCarthy
In your case, you actually shouldn't actually have to build any of them — you could just use sadi-service as a dependency in your own new project — but if you want to build sadi-service from scratch, you'll need the sadi.service and sadi.common projects.
It should be enough just to check those two projects out from SVN in Eclipse. They have configuration information associated with them in the repo, so you shouldn't have to edit anything after they've been checked out. If you do, something is wrong.
From what you've done so far, you should be able to open up the "SVN Repository Exploring" perspective (Window > Open Perspective > SVN Repository Exploring) and find the sadi.service and sadi.common projects under the sadi.googlecode.com repository in the left-hand panel. Right-click on a project (or select multiple projects and right-click) and choose "Check Out". The configuration should be detected automatically and the project should just build (assuming you have the Maven plugin, of course).
If you've now got a single project called "trunk" in your workspace, you can just delete that.
I'll put up a Wiki page with screenshots next week when I'm looking at the new Eclipse.
Tim rdf
> Each directory under /trunk is a separate project. Some of them build the various Maven artifacts, but some of them aren't even Java…
>
> In your case, you actually shouldn't actually have to build any of them — you could just use sadi-service as a dependency in your own new project — but if you want to build sadi-service from scratch, you'll need the sadi.service and sadi.common projects.
>
> It should be enough just to check those two projects out from SVN in Eclipse. They have configuration information associated with them in the repo, so you shouldn't have to edit anything after they've been checked out. If you do, something is wrong.
>
> From what you've done so far, you should be able to open up the "SVN Repository Exploring" perspective (Window > Open Perspective > SVN Repository Exploring) and find the sadi.service and sadi.common projects under the sadi.googlecode.com repository in the left-hand panel. Right-click on a project (or select multiple projects and right-click) and choose "Check Out". The configuration should be detected automatically and the project should just build (assuming you have the Maven plugin, of course).
I checked out sadi.service and sadi.common projects using the SVN
Repository Exploring perspective.
Both have the same dependency failures (javax.*, org.apache.*,
ca.wilkinsonlab.*, com.hp.*).
m2e 1.0 is installed, should it have grabbed the dependencies when I
checked them out?
>
> If you've now got a single project called "trunk" in your workspace, you can just delete that.
Done.
>
> I'll put up a Wiki page with screenshots next week when I'm looking at the new Eclipse.
Thanks. If you point me to it, I'll be happy to review.
Thanks again for your consideration.
Luke McCarthy
> I checked out sadi.service and sadi.common projects using the SVN
> Repository Exploring perspective.
> Both have the same dependency failures (javax.*, org.apache.*,
> ca.wilkinsonlab.*, com.hp.*).
>
> m2e 1.0 is installed, should it have grabbed the dependencies when I
> checked them out?
Yes, it should have. You could try Right-clicking on the projects and choosing Maven > Update dependencies to see if that fixes things.
I am know even more sure that you've got a different version of the Maven plugin than we've been using…
Tim rdf
> On 2012-01-07, at 12:14 PM, Tim rdf wrote:
>
>> I checked out sadi.service and sadi.common projects using the SVN
>> Repository Exploring perspective.
>> Both have the same dependency failures (javax.*, org.apache.*,
>> ca.wilkinsonlab.*, com.hp.*).
>>
>> m2e 1.0 is installed, should it have grabbed the dependencies when I
>> checked them out?
>
> Yes, it should have. You could try Right-clicking on the projects and choosing Maven > Update dependencies to see if that fixes things.
"Maven" is not an option when right-clicking on either project
("sadi.common" "sadi.service")
>
> I am know even more sure that you've got a different version of the Maven plugin than we've been using…
Sorry to cause so much trouble.
I am using Eclipse SDK 3.7.1 (just updated to the latest) and m2e
1.0.100.20110804-1717, which I installed from "Help : Install New
Software ..." and searching for maven.
Regards,
Tim
Luke McCarthy
> On Sat, Jan 7, 2012 at 3:19 PM, Luke McCarthy <lu...@elmonline.ca> wrote:
>> On 2012-01-07, at 12:14 PM, Tim rdf wrote:
>>
>>> I checked out sadi.service and sadi.common projects using the SVN
>>> Repository Exploring perspective.
>>> Both have the same dependency failures (javax.*, org.apache.*,
>>> ca.wilkinsonlab.*, com.hp.*).
>>>
>>> m2e 1.0 is installed, should it have grabbed the dependencies when I
>>> checked them out?
>>
>> Yes, it should have. You could try Right-clicking on the projects and choosing Maven > Update dependencies to see if that fixes things.
>
> "Maven" is not an option when right-clicking on either project
> ("sadi.common" "sadi.service")
Right-clicking on a project and choosing "Configure -> Convert to Maven project" seems to do the trick.
In full:
After downloading Eclipse 3.7.1 (Indigo SR 1), I had to install the SVN Team Provider (Help -> Install new software... ; select the Indigo update site ; filter by "svn" to find the SVN Team Provider) in order to access Google Code SVN repositories. Once that was installed, I was able to check out the SADI projects (Window -> Open Perspective -> SVN Repository Exploring ; File -> New -> Repository Location ; used https://sadi.googlecode.com/svn/ as the URL and my Google ID as the User/Password)
I checked out sadi.service and there were numerous build errors. I right-clicked sadi.service and chose "Configure -> Convert to Maven project". Once the Maven central indexes were updated (which took quite a while on a new virtual machine), I right-clicked the project and chose -> "Maven -> Update Dependencies..." and the required artifacts were downloaded and the build errors resolved.
I tried to record a video documenting the process, but it did not work out. I'll try again and hopefully add a link to this wiki page: http://code.google.com/p/sadi/wiki/BuildingSADI
Cheers,
Luke