You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by Ross Gardler <rg...@apache.org> on 2010/03/03 19:42:37 UTC
Building with new connector sub project (was Re: Google summer of
code 2010)
On 03/03/2010 18:37, Suhothayan Sriskandarajah wrote:
> On 3 March 2010 02:56, Ross Gardler<rg...@apache.org> wrote:
...
>> Please note I just moved all the connector code into it's own sub-project
>> (see /connector/java) please update from svn.
>>
>> If you have any problems building please let us know as I've changed the
>> build system in a number of ways.
>>
>>
> yes i'm having some problem when i build the latest one
> when building the dependencies it says...
> org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT: not found
> please help me
Have you done a complete svn update?
How are you trying to build?
Ross
Re: Building with new connector sub project (was Re: Google summer of
code 2010)
Posted by Suhothayan Sriskandarajah <su...@gmail.com>.
On 4 March 2010 00:33, Suhothayan Sriskandarajah <su...@gmail.com>wrote:
>
>
> On 4 March 2010 00:12, Ross Gardler <rg...@apache.org> wrote:
>
>> On 03/03/2010 18:37, Suhothayan Sriskandarajah wrote:
>>
>>> On 3 March 2010 02:56, Ross Gardler<rg...@apache.org> wrote:
>>>
>>
>> ...
>>
>> Please note I just moved all the connector code into it's own sub-project
>>>> (see /connector/java) please update from svn.
>>>>
>>>> If you have any problems building please let us know as I've changed the
>>>> build system in a number of ways.
>>>>
>>>>
>>>> yes i'm having some problem when i build the latest one
>>> when building the dependencies it says...
>>> org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT: not found
>>> please help me
>>>
>>
>> Have you done a complete svn update?
>>
>> yes, some days before i did a svn checkout and i was able to build it with
> no problem.
>
> and now i took another svn co and now i have this problem even after a
> complete new svn checkout!
>
>
>> How are you trying to build?
>>
>
> i just typed "ant" in the trunk directory
>
> and when resolving dependencies it fails with the above error massage.
>
> suho
>
>
this was the actual massage..
:: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve] module not found:
org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT
[ivy:resolve] ==== local: tried
[ivy:resolve] -- artifact
org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT!wookieJavaConnector.jar:
[ivy:resolve]
/home/suho/.m2/repository/org/apache/incubator/wookieJavaConnector/0.1.0-SNAPSHOT/wookieJavaConnector-0.1.0-SNAPSHOT.jar
[ivy:resolve] ==== wookie-local: tried
[ivy:resolve] -- artifact
org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT!wookieJavaConnector.jar:
[ivy:resolve]
/home/suho/proj/wookie1/trunk/ant/lib/wookieJavaConnector-0.1.0-SNAPSHOT.jar
[ivy:resolve] ==== public: tried
[ivy:resolve]
http://repo1.maven.org/maven2/org/apache/incubator/wookieJavaConnector/0.1.0-SNAPSHOT/wookieJavaConnector-0.1.0-SNAPSHOT.pom
[ivy:resolve] -- artifact
org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT!wookieJavaConnector.jar:
[ivy:resolve]
http://repo1.maven.org/maven2/org/apache/incubator/wookieJavaConnector/0.1.0-SNAPSHOT/wookieJavaConnector-0.1.0-SNAPSHOT.jar
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] :: UNRESOLVED DEPENDENCIES ::
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] ::
org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT: not found
[ivy:resolve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
BUILD FAILED
/home/suho/proj/wookie1/trunk/ant/ivy-common.xml:61: impossible to resolve
dependencies:
resolve failed - see output for details
>
>> Ross
>>
>
>
Re: Building with new connector sub project (was Re: Google summer of
code 2010)
Posted by Suhothayan Sriskandarajah <su...@gmail.com>.
thanks,
now i got it build.
Suho
On 4 March 2010 15:17, Ross Gardler <rg...@apache.org> wrote:
> On 04/03/2010 09:35, Ross Gardler wrote:
>
> It looks like somone has stomped over my recent ANT commits. I just did
>> an SVN update and I am now reproducing this problem.
>>
>
> I should not be so quick as to blame other people. It's a bug in my build
> scripts that was not manifesting itself until I did a clean build.
>
> Scotts recent work has compounded the problem. Here's your workaround while
> I work on a fix:
>
> run
>
> ant pre-compile-core
>
> This will build and deploy the Java connector framework
>
> cd parser/java
> ant publish-local
>
> This will build and deploy the Parse module
>
> cd ../..
> ant
>
> I'll commit a fix for this ASAP
>
> Ross
>
Re: Refreshing sub-projects?
Posted by Ross Gardler <rg...@apache.org>.
Appologies for not getting back to you on this yet.
I can confirm there is a problem with the build process, I have found
what should be the solution in the IVY docs, but it isn't working for me
yet.
Now my baby daughter has arrived so I am not sure when I will fix this
properly.
I suggest adding a temporary fix that deletes the cache data for the two
modules before they are built. If I recall correctly there is an ivy
property for getting at the cache directory.
I'll come back to this when I can.
Ross
On 05/03/2010 17:00, Scott Wilson wrote:
>
> On 5 Mar 2010, at 16:01, Ross Gardler wrote:
>
>> On 05/03/2010 14:29, Scott Wilson wrote:
>>> I made some changes to the parser sub-project code, however whenever I
>>> run Wookie with "ant clean-db run" the updated parser code isn't used -
>>> is there anything I should do to ensure that Wookie runs with the latest
>>> snapshot of sub-project jars rather than an earlier cached version?
>>
>> What is your current workflow?
>>
>> If you:
>>
>> - edit a subproject
>> - "ant publish-local" in the subproject
>> - "ant clean-db run" (see NOTE 1)
>>
>> You will (should?) be running with the latest snapshot.
>
> OK, I've tried this but I still get the cached subproject build. The
> subproject clearly has recompiled, but the main Wookie run command
> doesn't pick it up.
>
> The only way I've managed to get it to refresh is to manually delete the
> jar from ~/.ant/cache (or I could clean the whole cache but I really
> don't want to do that)
>
>> We could force the publish-local step from the core build script, but
>> forcing a compilation of all sub-projects just to run Wookie adds an
>> unnecessary step to the process. If we do add it then I would want it
>> to be configurable from local.build.properties
>>
>> In most IDEs you can add the publish-local step to the standard build
>> process of the IDE and thus remove the need to manually publish.
>>
>> Ross
>>
>> NOTE did you notice that clean-db is no longer necessary if you set
>> "initDB=false" in the local.build.properties. Now you only need to do
>> clean-db if you want to start from a fresh install.
>
> D'oh no I hadn't!
Re: Refreshing sub-projects?
Posted by Scott Wilson <sc...@gmail.com>.
On 5 Mar 2010, at 16:01, Ross Gardler wrote:
> On 05/03/2010 14:29, Scott Wilson wrote:
>> I made some changes to the parser sub-project code, however
>> whenever I
>> run Wookie with "ant clean-db run" the updated parser code isn't
>> used -
>> is there anything I should do to ensure that Wookie runs with the
>> latest
>> snapshot of sub-project jars rather than an earlier cached version?
>
> What is your current workflow?
>
> If you:
>
> - edit a subproject
> - "ant publish-local" in the subproject
> - "ant clean-db run" (see NOTE 1)
>
> You will (should?) be running with the latest snapshot.
OK, I've tried this but I still get the cached subproject build. The
subproject clearly has recompiled, but the main Wookie run command
doesn't pick it up.
The only way I've managed to get it to refresh is to manually delete
the jar from ~/.ant/cache (or I could clean the whole cache but I
really don't want to do that)
> We could force the publish-local step from the core build script,
> but forcing a compilation of all sub-projects just to run Wookie
> adds an unnecessary step to the process. If we do add it then I
> would want it to be configurable from local.build.properties
>
> In most IDEs you can add the publish-local step to the standard
> build process of the IDE and thus remove the need to manually publish.
>
> Ross
>
> NOTE did you notice that clean-db is no longer necessary if you set
> "initDB=false" in the local.build.properties. Now you only need to
> do clean-db if you want to start from a fresh install.
D'oh no I hadn't!
Re: Refreshing sub-projects?
Posted by Ross Gardler <rg...@apache.org>.
On 05/03/2010 14:29, Scott Wilson wrote:
> I made some changes to the parser sub-project code, however whenever I
> run Wookie with "ant clean-db run" the updated parser code isn't used -
> is there anything I should do to ensure that Wookie runs with the latest
> snapshot of sub-project jars rather than an earlier cached version?
What is your current workflow?
If you:
- edit a subproject
- "ant publish-local" in the subproject
- "ant clean-db run" (see NOTE 1)
You will (should?) be running with the latest snapshot.
We could force the publish-local step from the core build script, but
forcing a compilation of all sub-projects just to run Wookie adds an
unnecessary step to the process. If we do add it then I would want it to
be configurable from local.build.properties
In most IDEs you can add the publish-local step to the standard build
process of the IDE and thus remove the need to manually publish.
Ross
NOTE did you notice that clean-db is no longer necessary if you set
"initDB=false" in the local.build.properties. Now you only need to do
clean-db if you want to start from a fresh install.
Refreshing sub-projects?
Posted by Scott Wilson <sc...@gmail.com>.
I made some changes to the parser sub-project code, however whenever I
run Wookie with "ant clean-db run" the updated parser code isn't used
- is there anything I should do to ensure that Wookie runs with the
latest snapshot of sub-project jars rather than an earlier cached
version?
S
Re: Building with new connector sub project (was Re: Google summer
of code 2010)
Posted by Ross Gardler <rg...@apache.org>.
On 04/03/2010 11:55, Raido Kuli wrote:
> BUILD FAILED
> C:\Dev\wookie\build.xml:78: Basedir C:\Dev\wookie\${wookie.parser.w3c.dir}\java
> does not exist
I forgot to commit build.properties. Now done.
Thanks for the heads up.
>
> After creating property -> <property name="wookie.parser.w3c.dir"
> value="parser" />
value="parser/java"
(although I added to build.properties rather than to the build script.
Ross
>
> BUILD FAILED
> C:\Dev\wookie\ant\ivy-java-common.xml:94: Compile failed; see the compiler error
> output for details.
>
>
>
>
> On Thu, Mar 4, 2010 at 1:27 PM, Ross Gardler<rg...@apache.org> wrote:
>> On 04/03/2010 11:08, Ross Gardler wrote:
>>>
>>> On 04/03/2010 11:01, Scott Wilson wrote:
>>>
>>>> Thanks Ross - I copied the connector framework build scripts for the
>>>> parser so duplicated the same issue.
>>>
>>> Actually there are two problems with your new sub-project.
>>>
>>> The first is the error I created when doing the connector subproject
>>> (testing a fix now), the second was that you need to instruct core to
>>> build and locally deploy any sub-projects prior to compilation.
>>>
>>> This is done in /build.xml as follows:
>>
>> I've now committed a fix for these issues. Note the previously pasted
>> snippet for building sub projects is a little different now. It reads:
>>
>> <target name="local-publish-subprojects">
>> <!-- localy publish sub-projects -->
>> <ant dir="${wookie.connector.dir}/java" target="publish-local"
>> inheritAll="false"/>
>> <ant dir="${wookie.parser.w3c.dir}/java" target="publish-local"
>> inheritAll="false"/>
>> </target>
>>
>> When we add any sub project we need to add an appropriate line to the above.
>>
>> If anyone is interested, the problem was that I previously added a
>> pre-compile-core target that was called as part of the compile-core target.
>> However, this was being called after the ivy:resolve rather than before it.
>> I have no idea why I did this with an ant-call rather than a dependency,
>> call it a minor aberation.
>>
>> Anyway, we now have "local-publish-subprojects" and "pre-compile-core"
>> targets.
>>
>> I've also added some logging messages to make it easier to track what is
>> going on given that there are now multiple calls to each target for various
>> sub projects.
>>
>> Ross
>>
Re: Building with new connector sub project (was Re: Google summer of
code 2010)
Posted by Raido Kuli <ra...@gmail.com>.
BUILD FAILED
C:\Dev\wookie\build.xml:78: Basedir C:\Dev\wookie\${wookie.parser.w3c.dir}\java
does not exist
After creating property -> <property name="wookie.parser.w3c.dir"
value="parser" />
BUILD FAILED
C:\Dev\wookie\ant\ivy-java-common.xml:94: Compile failed; see the compiler error
output for details.
On Thu, Mar 4, 2010 at 1:27 PM, Ross Gardler <rg...@apache.org> wrote:
> On 04/03/2010 11:08, Ross Gardler wrote:
>>
>> On 04/03/2010 11:01, Scott Wilson wrote:
>>
>>> Thanks Ross - I copied the connector framework build scripts for the
>>> parser so duplicated the same issue.
>>
>> Actually there are two problems with your new sub-project.
>>
>> The first is the error I created when doing the connector subproject
>> (testing a fix now), the second was that you need to instruct core to
>> build and locally deploy any sub-projects prior to compilation.
>>
>> This is done in /build.xml as follows:
>
> I've now committed a fix for these issues. Note the previously pasted
> snippet for building sub projects is a little different now. It reads:
>
> <target name="local-publish-subprojects">
> <!-- localy publish sub-projects -->
> <ant dir="${wookie.connector.dir}/java" target="publish-local"
> inheritAll="false"/>
> <ant dir="${wookie.parser.w3c.dir}/java" target="publish-local"
> inheritAll="false"/>
> </target>
>
> When we add any sub project we need to add an appropriate line to the above.
>
> If anyone is interested, the problem was that I previously added a
> pre-compile-core target that was called as part of the compile-core target.
> However, this was being called after the ivy:resolve rather than before it.
> I have no idea why I did this with an ant-call rather than a dependency,
> call it a minor aberation.
>
> Anyway, we now have "local-publish-subprojects" and "pre-compile-core"
> targets.
>
> I've also added some logging messages to make it easier to track what is
> going on given that there are now multiple calls to each target for various
> sub projects.
>
> Ross
>
Re: Building with new connector sub project (was Re: Google summer
of code 2010)
Posted by Ross Gardler <rg...@apache.org>.
On 04/03/2010 11:08, Ross Gardler wrote:
> On 04/03/2010 11:01, Scott Wilson wrote:
>
>> Thanks Ross - I copied the connector framework build scripts for the
>> parser so duplicated the same issue.
>
> Actually there are two problems with your new sub-project.
>
> The first is the error I created when doing the connector subproject
> (testing a fix now), the second was that you need to instruct core to
> build and locally deploy any sub-projects prior to compilation.
>
> This is done in /build.xml as follows:
I've now committed a fix for these issues. Note the previously pasted
snippet for building sub projects is a little different now. It reads:
<target name="local-publish-subprojects">
<!-- localy publish sub-projects -->
<ant dir="${wookie.connector.dir}/java" target="publish-local"
inheritAll="false"/>
<ant dir="${wookie.parser.w3c.dir}/java" target="publish-local"
inheritAll="false"/>
</target>
When we add any sub project we need to add an appropriate line to the above.
If anyone is interested, the problem was that I previously added a
pre-compile-core target that was called as part of the compile-core
target. However, this was being called after the ivy:resolve rather than
before it. I have no idea why I did this with an ant-call rather than a
dependency, call it a minor aberation.
Anyway, we now have "local-publish-subprojects" and "pre-compile-core"
targets.
I've also added some logging messages to make it easier to track what is
going on given that there are now multiple calls to each target for
various sub projects.
Ross
Re: Building with new connector sub project (was Re: Google summer
of code 2010)
Posted by Ross Gardler <rg...@apache.org>.
On 04/03/2010 11:01, Scott Wilson wrote:
> Thanks Ross - I copied the connector framework build scripts for the
> parser so duplicated the same issue.
Actually there are two problems with your new sub-project.
The first is the error I created when doing the connector subproject
(testing a fix now), the second was that you need to instruct core to
build and locally deploy any sub-projects prior to compilation.
This is done in /build.xml as follows:
<target name="pre-compile-core">
<!-- localy publish sub-projects -->
<ant dir="${wookie.connector.dir}/java" target="publish-local"
inheritAll="false"/>
<ant dir="${wookie.parser.w3c.dir}/java" target="publish-local"
inheritAll="false"/>
</target>
I'll add this with my fix when fully tested.
Ross
Re: Building with new connector sub project (was Re: Google summer of code 2010)
Posted by Scott Wilson <sc...@gmail.com>.
On 4 Mar 2010, at 09:47, Ross Gardler wrote:
> On 04/03/2010 09:35, Ross Gardler wrote:
>
>> It looks like somone has stomped over my recent ANT commits. I just
>> did
>> an SVN update and I am now reproducing this problem.
>
> I should not be so quick as to blame other people. It's a bug in my
> build scripts that was not manifesting itself until I did a clean
> build.
>
> Scotts recent work has compounded the problem. Here's your
> workaround while I work on a fix:
>
> run
>
> ant pre-compile-core
>
> This will build and deploy the Java connector framework
>
> cd parser/java
> ant publish-local
>
> This will build and deploy the Parse module
>
> cd ../..
> ant
>
> I'll commit a fix for this ASAP
Thanks Ross - I copied the connector framework build scripts for the
parser so duplicated the same issue.
>
> Ross
Re: Building with new connector sub project (was Re: Google summer
of code 2010)
Posted by Ross Gardler <rg...@apache.org>.
On 04/03/2010 09:35, Ross Gardler wrote:
> It looks like somone has stomped over my recent ANT commits. I just did
> an SVN update and I am now reproducing this problem.
I should not be so quick as to blame other people. It's a bug in my
build scripts that was not manifesting itself until I did a clean build.
Scotts recent work has compounded the problem. Here's your workaround
while I work on a fix:
run
ant pre-compile-core
This will build and deploy the Java connector framework
cd parser/java
ant publish-local
This will build and deploy the Parse module
cd ../..
ant
I'll commit a fix for this ASAP
Ross
Re: Building with new connector sub project (was Re: Google summer
of code 2010)
Posted by Ross Gardler <rg...@apache.org>.
On 03/03/2010 19:03, Suhothayan Sriskandarajah wrote:
> On 4 March 2010 00:12, Ross Gardler<rg...@apache.org> wrote:
>
>> On 03/03/2010 18:37, Suhothayan Sriskandarajah wrote:
>>
>>> On 3 March 2010 02:56, Ross Gardler<rg...@apache.org> wrote:
>>>
>>
>> ...
>>
>> Please note I just moved all the connector code into it's own sub-project
>>>> (see /connector/java) please update from svn.
>>>>
>>>> If you have any problems building please let us know as I've changed the
>>>> build system in a number of ways.
>>>>
>>>>
>>>> yes i'm having some problem when i build the latest one
>>> when building the dependencies it says...
>>> org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT: not found
>>> please help me
>>>
>>
>> Have you done a complete svn update?
>>
>> yes, some days before i did a svn checkout and i was able to build it with
> no problem.
>
> and now i took another svn co and now i have this problem even after a
> complete new svn checkout!
>
>
>> How are you trying to build?
>>
>
> i just typed "ant" in the trunk directory
>
> and when resolving dependencies it fails with the above error massage.
It looks like somone has stomped over my recent ANT commits. I just did
an SVN update and I am now reproducing this problem.
I'll get back to you ASAP.
Ross
Re: Building with new connector sub project (was Re: Google summer of
code 2010)
Posted by Suhothayan Sriskandarajah <su...@gmail.com>.
On 4 March 2010 00:12, Ross Gardler <rg...@apache.org> wrote:
> On 03/03/2010 18:37, Suhothayan Sriskandarajah wrote:
>
>> On 3 March 2010 02:56, Ross Gardler<rg...@apache.org> wrote:
>>
>
> ...
>
> Please note I just moved all the connector code into it's own sub-project
>>> (see /connector/java) please update from svn.
>>>
>>> If you have any problems building please let us know as I've changed the
>>> build system in a number of ways.
>>>
>>>
>>> yes i'm having some problem when i build the latest one
>> when building the dependencies it says...
>> org.apache.incubator#wookieJavaConnector;0.1.0-SNAPSHOT: not found
>> please help me
>>
>
> Have you done a complete svn update?
>
> yes, some days before i did a svn checkout and i was able to build it with
no problem.
and now i took another svn co and now i have this problem even after a
complete new svn checkout!
> How are you trying to build?
>
i just typed "ant" in the trunk directory
and when resolving dependencies it fails with the above error massage.
suho
> Ross
>