You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Robert Vesse <rv...@cray.com> on 2011/10/31 20:54:59 UTC
Importing Maven Projects into Eclipse
Hi All
Is there any documentation on importing the maven projects into Eclipse, when I try and do this I get a bunch of errors about dependencies.
I also find that even from the command line I cannot do a mvn install easily because the artifacts appear to be referring to variables e.g ${ver.jena}
When did this change because a few weeks ago I could run mvn install etc from the command line fine without any issues just based on a fresh checkout which is what I've just done today.
Is there any documentation on how to get all these variables set appropriately?
Regards,
Rob Vesse
Re: Importing Maven Projects into Eclipse
Posted by Andy Seaborne <an...@apache.org>.
On 31/10/11 20:27, Ian Dickinson wrote:
> Hi Rob,
> On 31/10/11 19:54, Robert Vesse wrote:
>
>> Is there any documentation on importing the maven projects into
>> Eclipse, when I try and do this I get a bunch of errors about
>> dependencies.
> We need to update the Eclipse instructions for the new Maven structure.
> It's also an area that is fluctuating, as we're adapting the Jena build
> process to the Apache requirements.
>
> The basic thing you need is to check out JenaTop trunk as a peer of the
> Jena project you're trying to build (Core, ARQ, TDB, etc). If you look
> in the pom.xml for JenaTop, that's where you'll find the missing
> variables. The JenaTop pom is referred to from the pom's of the other
> projects, e.g:
>
> <parent>
> <groupId>org.apache.jena</groupId>
> <artifactId>jena-top</artifactId>
> <version>0-incubating-SNAPSHOT</version>
> <relativePath>../JenaTop/pom.xml</relativePath>
> </parent>
>
>
>> I also find that even from the command line I cannot do a mvn install
>> easily because the artifacts appear to be referring to variables e.g
>> ${ver.jena} When did this change
> Basically it's changing live, as we try to get ready to build Apache
> artifacts. However, adding JenaTop should solve your immediate issues.
>
> Sorry that you've been inconvenienced by the changes!
>
> Ian
>
>
There are checked-in Eclipse projects.
if you do
mvn dependency:resolve dependency:sources
all the necessary stuff should be installed in your maven repository.
Several projects have "mvn-update" scripts. But you need JenaTop
checked out until that is stable.
You need to set M2_REPO in Eclipse to your repository.
Andy
Re: Importing Maven Projects into Eclipse
Posted by Andy Seaborne <an...@apache.org>.
On 01/11/11 11:10, Thorsten Möller wrote:
...
> BTW, as this is (once again) a Maven related thread: I get a few warnings at build time caused by use of deprecated features, see below. Warnings want go away by nature, isn't it.
>
> ARQ:
> [WARNING] DEPRECATED [tasks]: Use target instead
> [INFO] [antrun:run {execution: ant-timestamp}]
> [WARNING] Parameter tasks is deprecated, use target instead
> [INFO] Executing tasks
>
> Jena:
> [WARNING] DEPRECATED [tasks]: Use target instead
> [INFO] [antrun:run {execution: default}]
> [WARNING] Parameter tasks is deprecated, use target instead
> [INFO] Executing tasks
I haven't had time to track down why these occur - do you know?
>
> More serious, however, is that Junit tests for ARQ/trunk[rev1195889] do not pass on my machine (Maven 2.2.1, Java 1.6.0_26, OSX 10.6.8). Seems to be a locale-specific issue, see https://issues.apache.org/jira/browse/JENA-150.
Fixed (I hope - please test) - see JIRA.
Andy
Re: Importing Maven Projects into Eclipse
Posted by Thorsten Möller <th...@unibas.ch>.
Am 01.11.2011 um 10:03 schrieb Andy Seaborne:
> On 31/10/11 21:35, Andy Seaborne wrote:
>> On 31/10/11 20:49, Thorsten Möller wrote:
>>> Incidentally, I did a fresh checkout yesterday and stumbled upon this
>>> point as well. With the current POM one is forced to checkout JenaTop
>>> as a sibling even when one just wants Jena, ARQ, or any other Jena
>>> project. I suggest removing the relativePath property as this will
>>> resolve the issue (parent POM will be downloaded automatically from
>>> Maven Central if not already in the local Maven repository). The
>>> relativePath property should only be set if it is anyway necessary
>>> (for whatever reason) to do a complete checkout of all
>>> modules/projects. I can file a Jira request in case you agree.
>>>
>>> Thorsten
>>
>> It's a temporary necessity while we get the POM structure for the first
>> releases (minimal change to system structure) working, i.e. JenaTop is
>> changing to get a system working. It'll go away sometime, maybe soon.
>
> To be clear "it'll go away" refers to <relativePath>
... which is what I understood. Thanks.
BTW, as this is (once again) a Maven related thread: I get a few warnings at build time caused by use of deprecated features, see below. Warnings want go away by nature, isn't it.
ARQ:
[WARNING] DEPRECATED [tasks]: Use target instead
[INFO] [antrun:run {execution: ant-timestamp}]
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks
Jena:
[WARNING] DEPRECATED [tasks]: Use target instead
[INFO] [antrun:run {execution: default}]
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks
More serious, however, is that Junit tests for ARQ/trunk[rev1195889] do not pass on my machine (Maven 2.2.1, Java 1.6.0_26, OSX 10.6.8). Seems to be a locale-specific issue, see https://issues.apache.org/jira/browse/JENA-150.
Thorsten
Re: Importing Maven Projects into Eclipse
Posted by Andy Seaborne <an...@apache.org>.
On 31/10/11 21:35, Andy Seaborne wrote:
> On 31/10/11 20:49, Thorsten Möller wrote:
>> Incidentally, I did a fresh checkout yesterday and stumbled upon this
>> point as well. With the current POM one is forced to checkout JenaTop
>> as a sibling even when one just wants Jena, ARQ, or any other Jena
>> project. I suggest removing the relativePath property as this will
>> resolve the issue (parent POM will be downloaded automatically from
>> Maven Central if not already in the local Maven repository). The
>> relativePath property should only be set if it is anyway necessary
>> (for whatever reason) to do a complete checkout of all
>> modules/projects. I can file a Jira request in case you agree.
>>
>> Thorsten
>
> It's a temporary necessity while we get the POM structure for the first
> releases (minimal change to system structure) working, i.e. JenaTop is
> changing to get a system working. It'll go away sometime, maybe soon.
To be clear "it'll go away" refers to <relativePath>
>
> Andy
Re: Importing Maven Projects into Eclipse
Posted by Paolo Castagna <ca...@googlemail.com>.
Andy Seaborne wrote:
> On 01/11/11 07:51, Paolo Castagna wrote:
>> Hi Andy
>>
>> Andy Seaborne wrote:
>>> It's a temporary necessity while we get the POM structure for the
>>> first releases (minimal change to system structure) working, i.e.
>>> JenaTop is changing to get a system working. It'll go away sometime,
>>> maybe soon.
>>
>> Having a common parent pom for the all the Jena modules is not a bad
>> idea.
>>
>> The problems related to JenaTop are mainly caused by the fact that it has
>> not been released yet and therefore it is not present in Maven central.
>>
>> When that happens, there should be no problems like the ones Rob is
>> experiencing and we have a place where we can put common stuff without
>> repeating it over and over across the different modules.
>>
>> What are the advantages in removing JenaTop?
>
> "it" is the <relativePath> in JenaTop.
Great.
> When we have the new build system, JenaTop or something like it, will
> module coordination.
>
> I'm aiming to get any sort of release done and redesigning the build
> structure isn't necessary for that.
Ack
Paolo
>
> Andy
Re: Importing Maven Projects into Eclipse
Posted by Andy Seaborne <an...@apache.org>.
On 01/11/11 07:51, Paolo Castagna wrote:
> Hi Andy
>
> Andy Seaborne wrote:
>> It's a temporary necessity while we get the POM structure for the
>> first releases (minimal change to system structure) working, i.e.
>> JenaTop is changing to get a system working. It'll go away sometime,
>> maybe soon.
>
> Having a common parent pom for the all the Jena modules is not a bad idea.
>
> The problems related to JenaTop are mainly caused by the fact that it has
> not been released yet and therefore it is not present in Maven central.
>
> When that happens, there should be no problems like the ones Rob is
> experiencing and we have a place where we can put common stuff without
> repeating it over and over across the different modules.
>
> What are the advantages in removing JenaTop?
"it" is the <relativePath> in JenaTop.
When we have the new build system, JenaTop or something like it, will
module coordination.
I'm aiming to get any sort of release done and redesigning the build
structure isn't necessary for that.
Andy
Re: Importing Maven Projects into Eclipse
Posted by Paolo Castagna <ca...@googlemail.com>.
Hi Andy
Andy Seaborne wrote:
> It's a temporary necessity while we get the POM structure for the first
> releases (minimal change to system structure) working, i.e. JenaTop is
> changing to get a system working. It'll go away sometime, maybe soon.
Having a common parent pom for the all the Jena modules is not a bad idea.
The problems related to JenaTop are mainly caused by the fact that it has
not been released yet and therefore it is not present in Maven central.
When that happens, there should be no problems like the ones Rob is
experiencing and we have a place where we can put common stuff without
repeating it over and over across the different modules.
What are the advantages in removing JenaTop?
Paolo
>
> Andy
Re: Importing Maven Projects into Eclipse
Posted by Andy Seaborne <an...@apache.org>.
On 31/10/11 20:49, Thorsten Möller wrote:
> Incidentally, I did a fresh checkout yesterday and stumbled upon this
> point as well. With the current POM one is forced to checkout JenaTop
> as a sibling even when one just wants Jena, ARQ, or any other Jena
> project. I suggest removing the relativePath property as this will
> resolve the issue (parent POM will be downloaded automatically from
> Maven Central if not already in the local Maven repository). The
> relativePath property should only be set if it is anyway necessary
> (for whatever reason) to do a complete checkout of all
> modules/projects. I can file a Jira request in case you agree.
>
> Thorsten
It's a temporary necessity while we get the POM structure for the first
releases (minimal change to system structure) working, i.e. JenaTop is
changing to get a system working. It'll go away sometime, maybe soon.
Andy
Re: Importing Maven Projects into Eclipse
Posted by Thorsten Möller <th...@unibas.ch>.
Am 31.10.2011 um 21:27 schrieb Ian Dickinson:
> Hi Rob,
> On 31/10/11 19:54, Robert Vesse wrote:
>
>> Is there any documentation on importing the maven projects into
>> Eclipse, when I try and do this I get a bunch of errors about
>> dependencies.
> We need to update the Eclipse instructions for the new Maven structure. It's also an area that is fluctuating, as we're adapting the Jena build process to the Apache requirements.
>
> The basic thing you need is to check out JenaTop trunk as a peer of the Jena project you're trying to build (Core, ARQ, TDB, etc). If you look in the pom.xml for JenaTop, that's where you'll find the missing variables. The JenaTop pom is referred to from the pom's of the other projects, e.g:
>
> <parent>
> <groupId>org.apache.jena</groupId>
> <artifactId>jena-top</artifactId>
> <version>0-incubating-SNAPSHOT</version>
> <relativePath>../JenaTop/pom.xml</relativePath>
> </parent>
Incidentally, I did a fresh checkout yesterday and stumbled upon this point as well. With the current POM one is forced to checkout JenaTop as a sibling even when one just wants Jena, ARQ, or any other Jena project. I suggest removing the relativePath property as this will resolve the issue (parent POM will be downloaded automatically from Maven Central if not already in the local Maven repository). The relativePath property should only be set if it is anyway necessary (for whatever reason) to do a complete checkout of all modules/projects. I can file a Jira request in case you agree.
Thorsten
>
>
>> I also find that even from the command line I cannot do a mvn install
>> easily because the artifacts appear to be referring to variables e.g
>> ${ver.jena} When did this change
> Basically it's changing live, as we try to get ready to build Apache artifacts. However, adding JenaTop should solve your immediate issues.
>
> Sorry that you've been inconvenienced by the changes!
>
> Ian
>
>
> --
> ____________________________________________________________
> Ian Dickinson Epimorphics Ltd, Bristol, UK
> mailto:ian@epimorphics.com http://www.epimorphics.com
> cell: +44-7786-850536 landline: +44-1275-399069
> ------------------------------------------------------------
> Epimorphics Ltd. is a limited company registered in England
> (no. 7016688). Registered address: Court Lodge, 105 High St,
> Portishead, Bristol BS20 6PT, UK
>
Re: Importing Maven Projects into Eclipse
Posted by Ian Dickinson <ia...@epimorphics.com>.
Hi Rob,
On 31/10/11 19:54, Robert Vesse wrote:
> Is there any documentation on importing the maven projects into
> Eclipse, when I try and do this I get a bunch of errors about
> dependencies.
We need to update the Eclipse instructions for the new Maven structure.
It's also an area that is fluctuating, as we're adapting the Jena build
process to the Apache requirements.
The basic thing you need is to check out JenaTop trunk as a peer of the
Jena project you're trying to build (Core, ARQ, TDB, etc). If you look
in the pom.xml for JenaTop, that's where you'll find the missing
variables. The JenaTop pom is referred to from the pom's of the other
projects, e.g:
<parent>
<groupId>org.apache.jena</groupId>
<artifactId>jena-top</artifactId>
<version>0-incubating-SNAPSHOT</version>
<relativePath>../JenaTop/pom.xml</relativePath>
</parent>
> I also find that even from the command line I cannot do a mvn install
> easily because the artifacts appear to be referring to variables e.g
> ${ver.jena} When did this change
Basically it's changing live, as we try to get ready to build Apache
artifacts. However, adding JenaTop should solve your immediate issues.
Sorry that you've been inconvenienced by the changes!
Ian
--
____________________________________________________________
Ian Dickinson Epimorphics Ltd, Bristol, UK
mailto:ian@epimorphics.com http://www.epimorphics.com
cell: +44-7786-850536 landline: +44-1275-399069
------------------------------------------------------------
Epimorphics Ltd. is a limited company registered in England
(no. 7016688). Registered address: Court Lodge, 105 High St,
Portishead, Bristol BS20 6PT, UK
Re: Importing Maven Projects into Eclipse
Posted by Damian Steer <d....@bristol.ac.uk>.
On 31 Oct 2011, at 19:54, Robert Vesse wrote:
> Hi All
Hi Rob,
> Is there any documentation on importing the maven projects into Eclipse, when I try and do this I get a bunch of errors about dependencies.
IIRC you can just do:
$ mvn eclipse:eclipse
but I'm not an eclipse user, and have not enjoyed the maven / eclipse experience in the past. See [1] and [2]? They appear to think eclipse IAM shows promise.
(Netbeans and IntelliJ can just open maven projects directly)
> I also find that even from the command line I cannot do a mvn install easily because the artifacts appear to be referring to variables e.g ${ver.jena}
> When did this change because a few weeks ago I could run mvn install etc from the command line fine without any issues just based on a fresh checkout which is what I've just done today.
>
> Is there any documentation on how to get all these variables set appropriately?
You need to check out JenaTop:
$ svn co https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaTop/trunk JenaTop
Damian
[1] <http://maven.apache.org/guides/mini/guide-ide-eclipse.html>
[2] <http://maven.apache.org/eclipse-plugin.html>