You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2012/03/27 18:40:30 UTC
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk: .classpath
.project .settings/org.eclipse.core.resources.prefs .settings/org.eclipse.jdt.core.prefs
src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
On 27/03/12 16:45, rvesse@apache.org wrote:
> Author: rvesse
> Date: Tue Mar 27 15:45:38 2012
> New Revision: 1305876
>
> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev
> Log:
> Minor typo fix to error message in QueryEngineHttp
>
> Modified:
> incubator/jena/Jena2/ARQ/trunk/.classpath
> incubator/jena/Jena2/ARQ/trunk/.project
> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs
> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs
> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Rob, this sets ARQ to be a m2e project. I guess that was unintended?
May I revert it to a plain Eclispe project for now?
Come the code reorg, when the projects can get their names aligned, we
can try using m2e if the project cross-linking works for everyone (e.g.
you need all the project open, I don't see how a quick bug version of
one module works)
Andy
Re: Build and timestamps
Posted by Robert Vesse <rv...@yarcdata.com>.
Thanks Andy
On Mar 29, 2012, at 2:02 AM, Andy Seaborne wrote:
> On 29/03/12 08:17, Andy Seaborne wrote:
>> On 28/03/12 22:59, Robert Vesse wrote:
>>> Nice find :-)
>>>
>>> Will stop Eclipse complaining at me so much
>>>
>>> Rob
>>
>> I'll take that as a "go ahead and make the changes" so I'll start to
>> sweep through the projects and remove antrun. I don't know of, or at
>> least can't recall, any places it used for anything else [*]
>
> Done.
>
> Core, ARQ, TDB, Fuseki, SDB.
>
>>
>> Andy
>>
>> [*] There again I came a comment on some string code that said
>> "do it this way because of Java 1.3" recently.
>>
>> [**] Bother - SDB does not build via maven but does in Eclipse.
>
> It turns out Java7 added an abstract method above java.sql.DataSource SDB has DataSourceSDB inherits from DataSource. Jiggling around and suppressing all warnings results in code that compiles cleanly in Java6 and Java7.
>
> Andy
Re: Build and timestamps
Posted by Andy Seaborne <an...@apache.org>.
On 29/03/12 08:17, Andy Seaborne wrote:
> On 28/03/12 22:59, Robert Vesse wrote:
>> Nice find :-)
>>
>> Will stop Eclipse complaining at me so much
>>
>> Rob
>
> I'll take that as a "go ahead and make the changes" so I'll start to
> sweep through the projects and remove antrun. I don't know of, or at
> least can't recall, any places it used for anything else [*]
Done.
Core, ARQ, TDB, Fuseki, SDB.
>
> Andy
>
> [*] There again I came a comment on some string code that said
> "do it this way because of Java 1.3" recently.
>
> [**] Bother - SDB does not build via maven but does in Eclipse.
It turns out Java7 added an abstract method above java.sql.DataSource
SDB has DataSourceSDB inherits from DataSource. Jiggling around and
suppressing all warnings results in code that compiles cleanly in Java6
and Java7.
Andy
Re: Build and timestamps
Posted by Andy Seaborne <an...@apache.org>.
On 28/03/12 22:59, Robert Vesse wrote:
> Nice find :-)
>
> Will stop Eclipse complaining at me so much
>
> Rob
I'll take that as a "go ahead and make the changes" so I'll start to
sweep through the projects and remove antrun. I don't know of, or at
least can't recall, any places it used for anything else [*]
Andy
[*] There again I came a comment on some string code that said
"do it this way because of Java 1.3" recently.
[**] Bother - SDB does not build via maven but does in Eclipse.
> On Mar 28, 2012, at 2:20 PM, Andy Seaborne wrote:
>
>> On 28/03/12 22:03, Andy Seaborne wrote:
>>>
>>>>> I also get m2e errors - the antrun plugin is "not covered by lifecycle
>>>>> configuration"
>>>>>
>>>>
>>>> You can fix that by using the QuickFix suggestion and ignoring that
>>>> goal. That just means if you want that goal to run, you have to use
>>>> the command line maven [1]. Below is a diff to apply that fix to ARQ.
>>>> I've been debating checking this in for all the projects, as it will
>>>> only affect those running m2e.
>>>
>>> The alternative is to not need antrun -- it exists only to get the
>>> timestamp in the way that used to be recommended.
>>>
>>> Maven now has property:
>>> maven.build.timestamp
>>> which takes a format. Just the XSD format is sufficient.
>>>
>>> <maven.build.timestamp.format
>>>> yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
>>>
>>> Andy
>>
>> ... which does not work.
>>
>> http://jira.codehaus.org/browse/MRESOURCES-99
>>
>> is still broken in maven 3.0.4.
>>
>> The workaround works.
>>
>> Andy
>>
>> ==== arq-properties.xml:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
>>
>> <properties version="1.0">
>> <comment>ARQ System Properties</comment>
>> <entry key="com.hp.hpl.jena.sparql.version">${project.version}</entry>
>> <entry key="com.hp.hpl.jena.sparql.build.datetime">${arq.buildDateTime}</entry>
>> </properties>
>>
>> ==== POM patch:
>>
>> ### Eclipse Workspace Patch 1.0
>> #P ARQ
>> Index: pom.xml
>> ===================================================================
>> --- pom.xml (revision 1305900)
>> +++ pom.xml (working copy)
>> @@ -48,6 +48,8 @@
>> <ver.httpclient>4.1.2</ver.httpclient>
>> <ver.httpcore>4.1.3</ver.httpcore>
>> <ver.commons-codec>1.5</ver.commons-codec>
>> +<maven.build.timestamp.format>yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
>> +<arq.buildDateTime>${maven.build.timestamp}</arq.buildDateTime>
>> </properties>
>>
>> <dependencies>
>> @@ -102,11 +104,6 @@
>> </dependencies>
>>
>> <build>
>> -<!-- The filter file is written by antrun -->
>> -<filters>
>> -<filter>${project.basedir}/target/filter.properties</filter>
>> -</filters>
>> -
>> <resources>
>> <resource>
>> <filtering>false</filtering>
>> @@ -201,39 +198,6 @@
>> <artifactId>maven-resources-plugin</artifactId>
>> </plugin>
>>
>> -<plugin>
>> -<groupId>org.apache.maven.plugins</groupId>
>> -<artifactId>maven-antrun-plugin</artifactId>
>> -<executions>
>> -<execution>
>> -<id>ant-timestamp</id>
>> -<phase>initialize</phase>
>> -<configuration>
>> -<target>
>> -<mkdir dir="${project.basedir}/target" />
>> -<tstamp>
>> -<format property="build.time.xsd" pattern="yyyy-MM-dd'T'HH:mm:ssZ" />
>> -<format property="build.time.txt" pattern="yyyy-MM-dd HH:mm z" />
>> -</tstamp>
>> -<!-- Do not indent (it does not work) -->
>> -<echo file="${project.basedir}/target/filter.properties">
>> -#begin
>> -build.time.xsd=${build.time.xsd}
>> -build.time.txt=${build.time.txt}
>> -#end
>> -</echo>
>> -<echo message="version=${project.version}" />
>> -<echo message="build.time=${build.time.txt}" />
>> -</target>
>> -</configuration>
>> -<goals>
>> -<goal>run</goal>
>> -</goals>
>> -</execution>
>> -<!-- Another task, another execution -->
>> -</executions>
>> -</plugin>
>> -
>> <!--
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>
Re: Build and timestamps
Posted by Robert Vesse <rv...@yarcdata.com>.
Nice find :-)
Will stop Eclipse complaining at me so much
Rob
On Mar 28, 2012, at 2:20 PM, Andy Seaborne wrote:
> On 28/03/12 22:03, Andy Seaborne wrote:
>>
>>>> I also get m2e errors - the antrun plugin is "not covered by lifecycle
>>>> configuration"
>>>>
>>>
>>> You can fix that by using the QuickFix suggestion and ignoring that
>>> goal. That just means if you want that goal to run, you have to use
>>> the command line maven [1]. Below is a diff to apply that fix to ARQ.
>>> I've been debating checking this in for all the projects, as it will
>>> only affect those running m2e.
>>
>> The alternative is to not need antrun -- it exists only to get the
>> timestamp in the way that used to be recommended.
>>
>> Maven now has property:
>> maven.build.timestamp
>> which takes a format. Just the XSD format is sufficient.
>>
>> <maven.build.timestamp.format
>> >yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
>>
>> Andy
>
> ... which does not work.
>
> http://jira.codehaus.org/browse/MRESOURCES-99
>
> is still broken in maven 3.0.4.
>
> The workaround works.
>
> Andy
>
> ==== arq-properties.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
>
> <properties version="1.0">
> <comment>ARQ System Properties</comment>
> <entry key="com.hp.hpl.jena.sparql.version">${project.version}</entry>
> <entry key="com.hp.hpl.jena.sparql.build.datetime">${arq.buildDateTime}</entry>
> </properties>
>
> ==== POM patch:
>
> ### Eclipse Workspace Patch 1.0
> #P ARQ
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 1305900)
> +++ pom.xml (working copy)
> @@ -48,6 +48,8 @@
> <ver.httpclient>4.1.2</ver.httpclient>
> <ver.httpcore>4.1.3</ver.httpcore>
> <ver.commons-codec>1.5</ver.commons-codec>
> + <maven.build.timestamp.format>yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
> + <arq.buildDateTime>${maven.build.timestamp}</arq.buildDateTime>
> </properties>
>
> <dependencies>
> @@ -102,11 +104,6 @@
> </dependencies>
>
> <build>
> - <!-- The filter file is written by antrun -->
> - <filters>
> - <filter>${project.basedir}/target/filter.properties</filter>
> - </filters>
> -
> <resources>
> <resource>
> <filtering>false</filtering>
> @@ -201,39 +198,6 @@
> <artifactId>maven-resources-plugin</artifactId>
> </plugin>
>
> - <plugin>
> - <groupId>org.apache.maven.plugins</groupId>
> - <artifactId>maven-antrun-plugin</artifactId>
> - <executions>
> - <execution>
> - <id>ant-timestamp</id>
> - <phase>initialize</phase>
> - <configuration>
> - <target>
> - <mkdir dir="${project.basedir}/target" />
> - <tstamp>
> - <format property="build.time.xsd" pattern="yyyy-MM-dd'T'HH:mm:ssZ" />
> - <format property="build.time.txt" pattern="yyyy-MM-dd HH:mm z" />
> - </tstamp>
> - <!-- Do not indent (it does not work) -->
> - <echo file="${project.basedir}/target/filter.properties">
> -#begin
> -build.time.xsd=${build.time.xsd}
> -build.time.txt=${build.time.txt}
> -#end
> - </echo>
> - <echo message="version=${project.version}" />
> - <echo message="build.time=${build.time.txt}" />
> - </target>
> - </configuration>
> - <goals>
> - <goal>run</goal>
> - </goals>
> - </execution>
> - <!-- Another task, another execution -->
> - </executions>
> - </plugin>
> -
> <!--
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
Build and timestamps
Posted by Andy Seaborne <an...@apache.org>.
On 28/03/12 22:03, Andy Seaborne wrote:
>
>>> I also get m2e errors - the antrun plugin is "not covered by lifecycle
>>> configuration"
>>>
>>
>> You can fix that by using the QuickFix suggestion and ignoring that
>> goal. That just means if you want that goal to run, you have to use
>> the command line maven [1]. Below is a diff to apply that fix to ARQ.
>> I've been debating checking this in for all the projects, as it will
>> only affect those running m2e.
>
> The alternative is to not need antrun -- it exists only to get the
> timestamp in the way that used to be recommended.
>
> Maven now has property:
> maven.build.timestamp
> which takes a format. Just the XSD format is sufficient.
>
> <maven.build.timestamp.format
> >yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
>
> Andy
... which does not work.
http://jira.codehaus.org/browse/MRESOURCES-99
is still broken in maven 3.0.4.
The workaround works.
Andy
==== arq-properties.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties version="1.0">
<comment>ARQ System Properties</comment>
<entry key="com.hp.hpl.jena.sparql.version">${project.version}</entry>
<entry
key="com.hp.hpl.jena.sparql.build.datetime">${arq.buildDateTime}</entry>
</properties>
==== POM patch:
### Eclipse Workspace Patch 1.0
#P ARQ
Index: pom.xml
===================================================================
--- pom.xml (revision 1305900)
+++ pom.xml (working copy)
@@ -48,6 +48,8 @@
<ver.httpclient>4.1.2</ver.httpclient>
<ver.httpcore>4.1.3</ver.httpcore>
<ver.commons-codec>1.5</ver.commons-codec>
+
<maven.build.timestamp.format>yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
+ <arq.buildDateTime>${maven.build.timestamp}</arq.buildDateTime>
</properties>
<dependencies>
@@ -102,11 +104,6 @@
</dependencies>
<build>
- <!-- The filter file is written by antrun -->
- <filters>
- <filter>${project.basedir}/target/filter.properties</filter>
- </filters>
-
<resources>
<resource>
<filtering>false</filtering>
@@ -201,39 +198,6 @@
<artifactId>maven-resources-plugin</artifactId>
</plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-antrun-plugin</artifactId>
- <executions>
- <execution>
- <id>ant-timestamp</id>
- <phase>initialize</phase>
- <configuration>
- <target>
- <mkdir dir="${project.basedir}/target" />
- <tstamp>
- <format property="build.time.xsd"
pattern="yyyy-MM-dd'T'HH:mm:ssZ" />
- <format property="build.time.txt" pattern="yyyy-MM-dd
HH:mm z" />
- </tstamp>
- <!-- Do not indent (it does not work) -->
- <echo file="${project.basedir}/target/filter.properties">
-#begin
-build.time.xsd=${build.time.xsd}
-build.time.txt=${build.time.txt}
-#end
- </echo>
- <echo message="version=${project.version}" />
- <echo message="build.time=${build.time.txt}" />
- </target>
- </configuration>
- <goals>
- <goal>run</goal>
- </goals>
- </execution>
- <!-- Another task, another execution -->
- </executions>
- </plugin>
-
<!--
<plugin>
<groupId>org.apache.maven.plugins</groupId>
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk: .classpath
.project .settings/org.eclipse.core.resources.prefs .settings/org.eclipse.jdt.core.prefs
src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Posted by Andy Seaborne <an...@apache.org>.
>> I also get m2e errors - the antrun plugin is "not covered by lifecycle
>> configuration"
>>
>
> You can fix that by using the QuickFix suggestion and ignoring that
> goal. That just means if you want that goal to run, you have to use
> the command line maven [1]. Below is a diff to apply that fix to ARQ.
> I've been debating checking this in for all the projects, as it will
> only affect those running m2e.
The alternative is to not need antrun -- it exists only to get the
timestamp in the way that used to be recommended.
Maven now has property:
maven.build.timestamp
which takes a format. Just the XSD format is sufficient.
<maven.build.timestamp.format
>yyyy-MM-dd'T'HH:mm:ssZ</maven.build.timestamp.format>
Andy
>
> -Stephen
>
> [1] m2e requires a "Lifecycle Mapping" be created for each Maven
> plugin that you want to use. This enforces that the plugin is working
> with Eclipse resources instead of directly with file handles. This is
> necessary for the plugin to play well with incremental compilation
> among other things. "Ignore" works well when it's not something that
> needs to be run a lot, and you can therefore do it manually if it is
> needed. The other option is "Execute", but that apparently is tricky.
> A bunch of info at [2].
>
> [2] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
>
>
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 1305481)
> +++ pom.xml (working copy)
> @@ -258,6 +258,39 @@
> -->
>
> </plugins>
> +<pluginManagement>
> + <plugins>
> + <!--This plugin's configuration is used to store Eclipse m2e
> settings only. It has no influence on the Maven build itself.-->
> + <plugin>
> + <groupId>org.eclipse.m2e</groupId>
> + <artifactId>lifecycle-mapping</artifactId>
> + <version>1.0.0</version>
> + <configuration>
> + <lifecycleMappingMetadata>
> + <pluginExecutions>
> + <pluginExecution>
> + <pluginExecutionFilter>
> + <groupId>
> + org.apache.maven.plugins
> + </groupId>
> + <artifactId>
> + maven-antrun-plugin
> + </artifactId>
> + <versionRange>[1.6,)</versionRange>
> + <goals>
> + <goal>run</goal>
> + </goals>
> + </pluginExecutionFilter>
> + <action>
> + <ignore></ignore>
> + </action>
> + </pluginExecution>
> + </pluginExecutions>
> + </lifecycleMappingMetadata>
> + </configuration>
> + </plugin>
> + </plugins>
> +</pluginManagement>
> </build>
>
> <reporting>
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk:
.classpath .project .settings/org.eclipse.core.resources.prefs
.settings/org.eclipse.jdt.core.prefs src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Posted by Stephen Allen <sa...@apache.org>.
On Tue, Mar 27, 2012 at 9:48 AM, Andy Seaborne <an...@apache.org> wrote:
> On 27/03/12 17:40, Andy Seaborne wrote:
>>
>> On 27/03/12 16:45, rvesse@apache.org wrote:
>>>
>>> Author: rvesse
>>> Date: Tue Mar 27 15:45:38 2012
>>> New Revision: 1305876
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev
>>> Log:
>>> Minor typo fix to error message in QueryEngineHttp
>>>
>>> Modified:
>>> incubator/jena/Jena2/ARQ/trunk/.classpath
>>> incubator/jena/Jena2/ARQ/trunk/.project
>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs
>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs
>>>
>>> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
>>>
>>
>> Rob, this sets ARQ to be a m2e project. I guess that was unintended?
>>
>> May I revert it to a plain Eclispe project for now?
>>
>> Come the code reorg, when the projects can get their names aligned, we
>> can try using m2e if the project cross-linking works for everyone (e.g.
>> you need all the project open, I don't see how a quick bug version of
>> one module works)
>>
m2e works pretty well for me with cross-linking the various Jena
projects. The key is to make sure you've specified the correct
dependency versions to make Eclipse pick up the linking. It will also
fall back to the jar in your repository if you close one of the
dependency projects, or use a different version than the project you
have open.
>
>
> I also get m2e errors - the antrun plugin is "not covered by lifecycle
> configuration"
>
You can fix that by using the QuickFix suggestion and ignoring that
goal. That just means if you want that goal to run, you have to use
the command line maven [1]. Below is a diff to apply that fix to ARQ.
I've been debating checking this in for all the projects, as it will
only affect those running m2e.
-Stephen
[1] m2e requires a "Lifecycle Mapping" be created for each Maven
plugin that you want to use. This enforces that the plugin is working
with Eclipse resources instead of directly with file handles. This is
necessary for the plugin to play well with incremental compilation
among other things. "Ignore" works well when it's not something that
needs to be run a lot, and you can therefore do it manually if it is
needed. The other option is "Execute", but that apparently is tricky.
A bunch of info at [2].
[2] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
Index: pom.xml
===================================================================
--- pom.xml (revision 1305481)
+++ pom.xml (working copy)
@@ -258,6 +258,39 @@
-->
</plugins>
+ <pluginManagement>
+ <plugins>
+ <!--This plugin's configuration is used to store Eclipse m2e
settings only. It has no influence on the Maven build itself.-->
+ <plugin>
+ <groupId>org.eclipse.m2e</groupId>
+ <artifactId>lifecycle-mapping</artifactId>
+ <version>1.0.0</version>
+ <configuration>
+ <lifecycleMappingMetadata>
+ <pluginExecutions>
+ <pluginExecution>
+ <pluginExecutionFilter>
+ <groupId>
+ org.apache.maven.plugins
+ </groupId>
+ <artifactId>
+ maven-antrun-plugin
+ </artifactId>
+ <versionRange>[1.6,)</versionRange>
+ <goals>
+ <goal>run</goal>
+ </goals>
+ </pluginExecutionFilter>
+ <action>
+ <ignore></ignore>
+ </action>
+ </pluginExecution>
+ </pluginExecutions>
+ </lifecycleMappingMetadata>
+ </configuration>
+ </plugin>
+ </plugins>
+ </pluginManagement>
</build>
<reporting>
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk: .classpath
.project .settings/org.eclipse.core.resources.prefs .settings/org.eclipse.jdt.core.prefs
src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Posted by Andy Seaborne <an...@apache.org>.
On 27/03/12 17:48, Andy Seaborne wrote:
> On 27/03/12 17:40, Andy Seaborne wrote:
>> On 27/03/12 16:45, rvesse@apache.org wrote:
>>> Author: rvesse
>>> Date: Tue Mar 27 15:45:38 2012
>>> New Revision: 1305876
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev
>>> Log:
>>> Minor typo fix to error message in QueryEngineHttp
>>>
>>> Modified:
>>> incubator/jena/Jena2/ARQ/trunk/.classpath
>>> incubator/jena/Jena2/ARQ/trunk/.project
>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs
>>>
>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs
>>> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
>>>
>>>
>>
>> Rob, this sets ARQ to be a m2e project. I guess that was unintended?
>>
>> May I revert it to a plain Eclispe project for now?
>>
>> Come the code reorg, when the projects can get their names aligned, we
>> can try using m2e if the project cross-linking works for everyone (e.g.
>> you need all the project open, I don't see how a quick bug version of
>> one module works)
>>
>> Andy
>
> I also get m2e errors - the antrun plugin is "not covered by lifecycle
> configuration"
>
> Andy
Done for now ... the I'm an m2e flag gets set quite deeply. Just
resetting the .settings, .project and .classpath did not work - Eclipse
still had some state that it was m2e-ish that was not in the files. (It
survived restart as well. I have no idea where else such state is kept!)
Andy
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk:
.classpath .project .settings/org.eclipse.core.resources.prefs
.settings/org.eclipse.jdt.core.prefs
src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Posted by Robert Vesse <rv...@yarcdata.com>.
Sorry, I usually check in via Tortoise and don't check any changes to those files
As this was a quick edit I did command line checkin forgetting it would send the project files as well
Rob
On Mar 27, 2012, at 10:01 AM, Robert Vesse wrote:
> Sorry yes that was unintentional
>
> Please revert appropriately, I believe m2e doesn't support ant run at all currently
>
> Rob
>
> On Mar 27, 2012, at 9:48 AM, Andy Seaborne wrote:
>
>> On 27/03/12 17:40, Andy Seaborne wrote:
>>> On 27/03/12 16:45, rvesse@apache.org wrote:
>>>> Author: rvesse
>>>> Date: Tue Mar 27 15:45:38 2012
>>>> New Revision: 1305876
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev
>>>> Log:
>>>> Minor typo fix to error message in QueryEngineHttp
>>>>
>>>> Modified:
>>>> incubator/jena/Jena2/ARQ/trunk/.classpath
>>>> incubator/jena/Jena2/ARQ/trunk/.project
>>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs
>>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs
>>>> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
>>>>
>>>
>>> Rob, this sets ARQ to be a m2e project. I guess that was unintended?
>>>
>>> May I revert it to a plain Eclispe project for now?
>>>
>>> Come the code reorg, when the projects can get their names aligned, we
>>> can try using m2e if the project cross-linking works for everyone (e.g.
>>> you need all the project open, I don't see how a quick bug version of
>>> one module works)
>>>
>>> Andy
>>
>> I also get m2e errors - the antrun plugin is "not covered by lifecycle configuration"
>>
>> Andy
>
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk:
.classpath .project .settings/org.eclipse.core.resources.prefs
.settings/org.eclipse.jdt.core.prefs
src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Posted by Robert Vesse <rv...@yarcdata.com>.
Sorry yes that was unintentional
Please revert appropriately, I believe m2e doesn't support ant run at all currently
Rob
On Mar 27, 2012, at 9:48 AM, Andy Seaborne wrote:
> On 27/03/12 17:40, Andy Seaborne wrote:
>> On 27/03/12 16:45, rvesse@apache.org wrote:
>>> Author: rvesse
>>> Date: Tue Mar 27 15:45:38 2012
>>> New Revision: 1305876
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev
>>> Log:
>>> Minor typo fix to error message in QueryEngineHttp
>>>
>>> Modified:
>>> incubator/jena/Jena2/ARQ/trunk/.classpath
>>> incubator/jena/Jena2/ARQ/trunk/.project
>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs
>>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs
>>> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
>>>
>>
>> Rob, this sets ARQ to be a m2e project. I guess that was unintended?
>>
>> May I revert it to a plain Eclispe project for now?
>>
>> Come the code reorg, when the projects can get their names aligned, we
>> can try using m2e if the project cross-linking works for everyone (e.g.
>> you need all the project open, I don't see how a quick bug version of
>> one module works)
>>
>> Andy
>
> I also get m2e errors - the antrun plugin is "not covered by lifecycle configuration"
>
> Andy
Re: svn commit: r1305876 - in /incubator/jena/Jena2/ARQ/trunk: .classpath
.project .settings/org.eclipse.core.resources.prefs .settings/org.eclipse.jdt.core.prefs
src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
Posted by Andy Seaborne <an...@apache.org>.
On 27/03/12 17:40, Andy Seaborne wrote:
> On 27/03/12 16:45, rvesse@apache.org wrote:
>> Author: rvesse
>> Date: Tue Mar 27 15:45:38 2012
>> New Revision: 1305876
>>
>> URL: http://svn.apache.org/viewvc?rev=1305876&view=rev
>> Log:
>> Minor typo fix to error message in QueryEngineHttp
>>
>> Modified:
>> incubator/jena/Jena2/ARQ/trunk/.classpath
>> incubator/jena/Jena2/ARQ/trunk/.project
>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.core.resources.prefs
>> incubator/jena/Jena2/ARQ/trunk/.settings/org.eclipse.jdt.core.prefs
>> incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
>>
>
> Rob, this sets ARQ to be a m2e project. I guess that was unintended?
>
> May I revert it to a plain Eclispe project for now?
>
> Come the code reorg, when the projects can get their names aligned, we
> can try using m2e if the project cross-linking works for everyone (e.g.
> you need all the project open, I don't see how a quick bug version of
> one module works)
>
> Andy
I also get m2e errors - the antrun plugin is "not covered by lifecycle
configuration"
Andy