6:21 a.m.
Most esteemed developers,
I was developing some patches for Hibernate Search but as I work on it on my own
I don't have much time for it; currently some problems about the move to Maven
have completely killed my productivity.
I have found some reference on your website;
The maven guide looks good: http://www.hibernate.org/422.html
but l would appreciate some more information for the eclipse users.
(are you all IDEA users?)
Specifically I have difficulty to understand how to set the correct JDK:
A) cache-jbosscache2 requires JDK5 (for many reasons)
B) org.hibernate.test.ops.MergeTest requires JDK5, as it is using
autoboxing since commit 14610.
C) core is needing jdk1.4, but if I use JDK5 to fix A&B it doesn't
compile because
BlobImpl, ResultSetWrapper, SerializableBlob should implement new
methods that were added in the latest interface versions.
So I didn't understand how other developers are having their project compile;
should I try setting a "mixed JDK" environment? Looks ugly.
Is it possible these problems are related to some maven setting I got wrong?
Currently I disabled jbosscache2, changed the source code of MergeTest
and switched to JDK1.4,
but would like to hear you opinion about it.
Also I actually need jbosscache2 :-(
thanks in advance,
Sanne
12:03 p.m.
Hi Sanne,
I just updated core to the latest and ran 'mvn clean install'. Everything
worked fine. Admittedly I had to disable
the doc profile in the master pom, because the docbook generation failed,
but that's a different issue. I am using maven 2.0.9 and JDK 1.5.0_06.
Maybe someone can make sense of the exception I get during documentation
generation:
[INFO] [jdocbook:translate {execution: default}]
[INFO] Processing translation [fr-FR]
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] unable to obtain appropriate runtime environment
CreateProcess: po2xml
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_
mapping.xml
D:\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
error=2
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.jboss.maven.shared.process.ExecutionException: unable to obtain
appropriate runtime environment
...
Caused by: java.io.IOException: CreateProcess: po2xml
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_mapping.xml
D:\Hardy\work\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
error=2
Do your Hibernate Search changes effect the core as well? With the latest
changes you don't have compile the core
anymore to build Hibernate Search. All the dependencies are managed with
ivy. Of course if your patches effect the core you will have to still do
it ;-) JDK5 should be fine though.
--Hardy
11:44 p.m.
Currently the docbook plugin relies on some system tools for dealing
with translations. You would need the GNU GetText toolset and the KDE
poxml toolset installed to do full doc builds.
Or you could disable docs in the build by using -
DdisableDistribution=true That essentially skips the documentation
and distribution modules.
On May 15, 2008, at 12:03 PM, Hardy Ferentschik wrote:
Hi Sanne,
I just updated core to the latest and ran 'mvn clean install'.
Everything worked fine. Admittedly I had to disable
the doc profile in the master pom, because the docbook generation
failed, but that's a different issue. I am using maven 2.0.9 and JDK
1.5.0_06.
Maybe someone can make sense of the exception I get during
documentation generation:
[INFO] [jdocbook:translate {execution: default}]
[INFO] Processing translation [fr-FR]
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] unable to obtain appropriate runtime environment
CreateProcess: po2xml D:\hibernate\core\documentation\manual\src\main
\docbook\en-US\content\association_
mapping.xml D:\hibernate\core\documentation\manual\src\main\docbook
\fr-FR\content\association_mapping.po
error=2
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.jboss.maven.shared.process.ExecutionException: unable to obtain
appropriate runtime environment
...
Caused by: java.io.IOException: CreateProcess: po2xml D:\hibernate
\core\documentation\manual\src\main\docbook\en-US\content
\association_mapping.xml D:\Hardy\work\hibernate\core\documentation
\manual\src\main\docbook\fr-FR\content\association_mapping.po error=2
Do your Hibernate Search changes effect the core as well? With the
latest changes you don't have compile the core
anymore to build Hibernate Search. All the dependencies are managed
with ivy. Of course if your patches effect the core you will have to
still do it ;-) JDK5 should be fine though.
--Hardy
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
-----------------------------
Steve Ebersole
Project Lead
http://hibernate.org
steve(a)hibernate.org
11:51 a.m.
Thanks for all the tips,
Still I'm unable to build the Hibernate Search project, even using a
clean checkout and
a fresh maven 2.0.9 repository; using JDK 1.5.0_15-b04.
I'm on Linux (LFS), and have installed the software mentioned by Steve Ebersole.
I don't really need Hibernate Core (although it was really useful to
have all projects configured
and linked in eclipse as dependencies), but I need to build it as the
latest Search trunk depends
on latest Core tag; I want to avoid the "please send me a built jar" approach.
I am collecting some of the problems I found:
1)To create an eclipse project for Core, I had to disable the
m2eclipse maven plugin, manually select all source
directories, download all jar dependencies and force source level to 1.5.
2)Annotations
Even when producing the Core distfiles using maven from command line,
not all dependent projects
find it in the repository, I had to re-register the jar using:
mvn install:install-file -DgroupId=org.hibernate
-DartifactId=hibernate -Dversion=3.3.0.CR1 -Dpackaging=jar -Dfile=
I don't really understood the problem, is it possible that different
projects give a different name to it?
3) EntityManager
After having registered annotations, I find out that building
entitymanager produces an empty jar
registered in my maven repository; no errors, just no compiled classes
in the jar.
4)Search
Even when skipping or manually resolving the other issues, to build
Search there is a
dependency on lucene 2.3.1 but the URL appears to be wrong;
I don't know how it finds the url, but he is downloading
http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lu...
(the signature) instead of
http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lu...
And the same problem for "lucene-parent".
Also before 3.3.0CR1 I could link the projects together instead of making
jars, so it was easy to navigate the source to make experiments and could skip
all building activities until test phases.
I know you are all quite busy, I can help myself (slowly) but my main
concern is to understand if these problems are
A) known, due the fact nobody completed the migration to maven.
B) You all tested only on IDEA
C) my environment is completely broken
regarding option C, I deleted my workspace and all maven repository,
fresh checkout and repeated all tests.. no luck.
regards,
Sanne
2008/5/16 Steve Ebersole <steve(a)hibernate.org>:
Currently the docbook plugin relies on some system tools for dealing
with
translations. You would need the GNU GetText toolset and the KDE poxml
toolset installed to do full doc builds.
Or you could disable docs in the build by using -DdisableDistribution=true
That essentially skips the documentation and distribution modules.
On May 15, 2008, at 12:03 PM, Hardy Ferentschik wrote:
> Hi Sanne,
>
> I just updated core to the latest and ran 'mvn clean install'. Everything
> worked fine. Admittedly I had to disable
> the doc profile in the master pom, because the docbook generation failed,
> but that's a different issue. I am using maven 2.0.9 and JDK 1.5.0_06.
>
> Maybe someone can make sense of the exception I get during documentation
> generation:
>
> [INFO] [jdocbook:translate {execution: default}]
> [INFO] Processing translation [fr-FR]
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] unable to obtain appropriate runtime environment
> CreateProcess: po2xml
> D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_
> mapping.xml
>
D:\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
> error=2
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.jboss.maven.shared.process.ExecutionException: unable to obtain
> appropriate runtime environment
> ...
> Caused by: java.io.IOException: CreateProcess: po2xml
>
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_mapping.xml
>
D:\Hardy\work\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
> error=2
>
>
> Do your Hibernate Search changes effect the core as well? With the latest
> changes you don't have compile the core
> anymore to build Hibernate Search. All the dependencies are managed with
> ivy. Of course if your patches effect the core you will have to still do it
> ;-) JDK5 should be fine though.
>
>
> --Hardy
>
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
-----------------------------
Steve Ebersole
Project Lead
http://hibernate.org
steve(a)hibernate.org
12:01 p.m.
Also before 3.3.0CR1 I could link the projects together instead of
making
jars, so it was easy to navigate the source to make experiments and could skip
all building activities until test phases.
I could do this the last time too...but I wondered my self how these things gets
done in the maven world (e.g. not depend on the repository jar but just depend on the
project to get the speed an incremental IDE can give you)
I know you are all quite busy, I can help myself (slowly) but my
main
concern is to understand if these problems are
A) known, due the fact nobody completed the migration to maven.
B) You all tested only on IDEA
C) my environment is completely broken
I think it is a mix - i'm the "eclipse guy" on the team and I just
haven't had the time
to integrate with 3.3.x yet ;(
/max
regarding option C, I deleted my workspace and all maven repository,
fresh checkout and repeated all tests.. no luck.
regards,
Sanne
2008/5/16 Steve Ebersole <steve(a)hibernate.org>:
> Currently the docbook plugin relies on some system tools for dealing with
> translations. You would need the GNU GetText toolset and the KDE poxml
> toolset installed to do full doc builds.
>
> Or you could disable docs in the build by using -DdisableDistribution=true
> That essentially skips the documentation and distribution modules.
>
> On May 15, 2008, at 12:03 PM, Hardy Ferentschik wrote:
>
>> Hi Sanne,
>>
>> I just updated core to the latest and ran 'mvn clean install'.
Everything
>> worked fine. Admittedly I had to disable
>> the doc profile in the master pom, because the docbook generation failed,
>> but that's a different issue. I am using maven 2.0.9 and JDK 1.5.0_06.
>>
>> Maybe someone can make sense of the exception I get during documentation
>> generation:
>>
>> [INFO] [jdocbook:translate {execution: default}]
>> [INFO] Processing translation [fr-FR]
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] unable to obtain appropriate runtime environment
>> CreateProcess: po2xml
>>
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_
>> mapping.xml
>>
D:\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
>> error=2
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.jboss.maven.shared.process.ExecutionException: unable to obtain
>> appropriate runtime environment
>> ...
>> Caused by: java.io.IOException: CreateProcess: po2xml
>>
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_mapping.xml
>>
D:\Hardy\work\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
>> error=2
>>
>>
>> Do your Hibernate Search changes effect the core as well? With the latest
>> changes you don't have compile the core
>> anymore to build Hibernate Search. All the dependencies are managed with
>> ivy. Of course if your patches effect the core you will have to still do it
>> ;-) JDK5 should be fine though.
>>
>>
>> --Hardy
>>
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
> -----------------------------
> Steve Ebersole
>
> Project Lead
> http://hibernate.org
> steve(a)hibernate.org
>
>
>
>
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
12:20 p.m.
2008/5/16 Max Rydahl Andersen <max.andersen(a)redhat.com>:
> Also before 3.3.0CR1 I could link the projects together instead
of making
> jars, so it was easy to navigate the source to make experiments and could skip
> all building activities until test phases.
I could do this the last time too...but I wondered my self how these things gets
done in the maven world (e.g. not depend on the repository jar but just depend on the
project to get the speed an incremental IDE can give you)
So, nice to hear that: I was thinking it was just me being a newbie with maven;
I think I'll maintain my own project configuration.
Maven is really cool to get all those dependencies I'm not really
interested in, but I prefer to have plain sources for the projects
were I want to work on.
> I know you are all quite busy, I can help myself (slowly) but my main
> concern is to understand if these problems are
> A) known, due the fact nobody completed the migration to maven.
> B) You all tested only on IDEA
> C) my environment is completely broken
I think it is a mix - i'm the "eclipse guy" on the team and I just
haven't had the time
to integrate with 3.3.x yet ;(
BTW thanks for the new JBoss developer studio, I finally have a 64bit
version working, very nice!
Sanne
/max
> regarding option C, I deleted my workspace and all maven repository,
> fresh checkout and repeated all tests.. no luck.
>
> regards,
> Sanne
>
> 2008/5/16 Steve Ebersole <steve(a)hibernate.org>:
>> Currently the docbook plugin relies on some system tools for dealing with
>> translations. You would need the GNU GetText toolset and the KDE poxml
>> toolset installed to do full doc builds.
>>
>> Or you could disable docs in the build by using -DdisableDistribution=true
>> That essentially skips the documentation and distribution modules.
>>
>> On May 15, 2008, at 12:03 PM, Hardy Ferentschik wrote:
>>
>>> Hi Sanne,
>>>
>>> I just updated core to the latest and ran 'mvn clean install'.
Everything
>>> worked fine. Admittedly I had to disable
>>> the doc profile in the master pom, because the docbook generation failed,
>>> but that's a different issue. I am using maven 2.0.9 and JDK 1.5.0_06.
>>>
>>> Maybe someone can make sense of the exception I get during documentation
>>> generation:
>>>
>>> [INFO] [jdocbook:translate {execution: default}]
>>> [INFO] Processing translation [fr-FR]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] FATAL ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] unable to obtain appropriate runtime environment
>>> CreateProcess: po2xml
>>>
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_
>>> mapping.xml
>>>
D:\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
>>> error=2
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Trace
>>> org.jboss.maven.shared.process.ExecutionException: unable to obtain
>>> appropriate runtime environment
>>> ...
>>> Caused by: java.io.IOException: CreateProcess: po2xml
>>>
D:\hibernate\core\documentation\manual\src\main\docbook\en-US\content\association_mapping.xml
>>>
D:\Hardy\work\hibernate\core\documentation\manual\src\main\docbook\fr-FR\content\association_mapping.po
>>> error=2
>>>
>>>
>>> Do your Hibernate Search changes effect the core as well? With the latest
>>> changes you don't have compile the core
>>> anymore to build Hibernate Search. All the dependencies are managed with
>>> ivy. Of course if your patches effect the core you will have to still do it
>>> ;-) JDK5 should be fine though.
>>>
>>>
>>> --Hardy
>>>
>>>
>>>
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>>
>> -----------------------------
>> Steve Ebersole
>>
>> Project Lead
>> http://hibernate.org
>> steve(a)hibernate.org
>>
>>
>>
>>
>>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
1:01 p.m.
On May 16, 2008, at 11:51 AM, Sanne Grinovero wrote:
I know you are all quite busy, I can help myself (slowly) but my main
concern is to understand if these problems are
A) known, due the fact nobody completed the migration to maven.
B) You all tested only on IDEA
C) my environment is completely broken
I only use IntelliJ, so this is perhaps a
possibility. I did ask Max
to verify that the overall structure/layout would work with eclipse.
He said it did, but that was many moons ago now.
I even forget the details now. Perhaps I used the command line
eclipse generation (mvn eclipse:eclipse) and sent that to Max to
test. Do you recall Max?
-----------------------------
Steve Ebersole
Project Lead
http://hibernate.org
steve(a)hibernate.org
1:10 p.m.
Steve Ebersole wrote:
I even forget the details now. Perhaps I used the command line eclipse
generation (mvn eclipse:eclipse) and sent that to Max to test. Do you
recall Max?
That's the only way I've ever been able to build /trunk in Eclipse.
But, the last time was also many moons ago...
-CB
1:46 a.m.
>
> I know you are all quite busy, I can help myself (slowly) but my main
> concern is to understand if these problems are
> A) known, due the fact nobody completed the migration to maven.
> B) You all tested only on IDEA
> C) my environment is completely broken
I only use IntelliJ, so this is perhaps a possibility. I did ask Max
to verify that the overall structure/layout would work with eclipse.
He said it did, but that was many moons ago now.
I even forget the details now. Perhaps I used the command line
eclipse generation (mvn eclipse:eclipse) and sent that to Max to
test. Do you recall Max?
I just used normal project import and setup the dependencies manually and it worked (back
then).
/max
4:47 p.m.
On May 16, 2008, at 13:51, Sanne Grinovero wrote:
3) EntityManager
After having registered annotations, I find out that building
entitymanager produces an empty jar
registered in my maven repository; no errors, just no compiled classes
in the jar.
Annotations, EntityManager, Validator, Search, commons-annotations,
jpa-api do not use maven for type build system.
You still need to use ant jar or whatever. Ivy is finding the
dependencies for you.
The ant build system does not publish the things to the maven repo.
4)Search
Even when skipping or manually resolving the other issues, to build
Search there is a
dependency on lucene 2.3.1 but the URL appears to be wrong;
I don't know how it finds the url, but he is downloading
http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lu...
(the signature) instead of
http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lu...
And the same problem for "lucene-parent".
I think you use mvn something rather than ant something
Also before 3.3.0CR1 I could link the projects together instead of
making
jars, so it was easy to navigate the source to make experiments and
could skip
all building activities until test phases.
The way I solve that is to manually link the various projects in the
IDE.
I know you are all quite busy, I can help myself (slowly) but my main
concern is to understand if these problems are
A) known, due the fact nobody completed the migration to maven.
B) You all tested only on IDEA
C) my environment is completely broken
regarding option C, I deleted my workspace and all maven repository,
fresh checkout and repeated all tests.. no luck.
regards,
Sanne
2008/5/16 Steve Ebersole <steve(a)hibernate.org>:
> Currently the docbook plugin relies on some system tools for
> dealing with
> translations. You would need the GNU GetText toolset and the KDE
> poxml
> toolset installed to do full doc builds.
>
> Or you could disable docs in the build by using -
> DdisableDistribution=true
> That essentially skips the documentation and distribution modules.
>
> On May 15, 2008, at 12:03 PM, Hardy Ferentschik wrote:
>
>> Hi Sanne,
>>
>> I just updated core to the latest and ran 'mvn clean install'.
>> Everything
>> worked fine. Admittedly I had to disable
>> the doc profile in the master pom, because the docbook generation
>> failed,
>> but that's a different issue. I am using maven 2.0.9 and JDK
>> 1.5.0_06.
>>
>> Maybe someone can make sense of the exception I get during
>> documentation
>> generation:
>>
>> [INFO] [jdocbook:translate {execution: default}]
>> [INFO] Processing translation [fr-FR]
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] unable to obtain appropriate runtime environment
>> CreateProcess: po2xml
>> D:\hibernate\core\documentation\manual\src\main\docbook\en-US
>> \content\association_
>> mapping.xml
>> D:\hibernate\core\documentation\manual\src\main\docbook\fr-FR
>> \content\association_mapping.po
>> error=2
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.jboss.maven.shared.process.ExecutionException: unable to obtain
>> appropriate runtime environment
>> ...
>> Caused by: java.io.IOException: CreateProcess: po2xml
>> D:\hibernate\core\documentation\manual\src\main\docbook\en-US
>> \content\association_mapping.xml
>> D:\Hardy\work\hibernate\core\documentation\manual\src\main\docbook
>> \fr-FR\content\association_mapping.po
>> error=2
>>
>>
>> Do your Hibernate Search changes effect the core as well? With the
>> latest
>> changes you don't have compile the core
>> anymore to build Hibernate Search. All the dependencies are
>> managed with
>> ivy. Of course if your patches effect the core you will have to
>> still do it
>> ;-) JDK5 should be fine though.
>>
>>
>> --Hardy
>>
>>
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
> -----------------------------
> Steve Ebersole
>
> Project Lead
> http://hibernate.org
> steve(a)hibernate.org
>
>
>
>
>
5:02 p.m.
On Fri, 16 May 2008 18:51:27 +0200, Sanne Grinovero
<sanne.grinovero(a)gmail.com> wrote:
Thanks for all the tips,
Still I'm unable to build the Hibernate Search project, even using a
clean checkout and
a fresh maven 2.0.9 repository; using JDK 1.5.0_15-b04.
I'm on Linux (LFS), and have installed the software mentioned by Steve
Ebersole.
I don't understand. Hibernate Search is still using Ant (with Ivy) for the
build.
If you just want to build Hibernate Search you don't even need maven. I
know there
is a POM in the top level directory, but this is not a working maven POM
as such.
The ant to maven mirgration is still a open Jira issue within Hibernate
Search. In fact
I believe it is assigned to me. So far I was waiting for the core
migration to be finished.
Maybe it is a good time to start now ;-)
Anyways, the ant build works fine. However, I choose
to not depend on 'latest' version defined for commons-annotations,
annotations and entity manager.
I changed ivy.xml to depend on deployed versions from the jboss repo. If
you stick with 'latest' you
WILL have to build these modules locally.
I don't really need Hibernate Core (although it was really useful
to
have all projects configured
and linked in eclipse as dependencies), but I need to build it as the
latest Search trunk depends
on latest Core tag; I want to avoid the "please send me a built jar"
approach.
I prefer to attach the source bundles to the appropriate jar artifacts.
There is an option
in the m2eclipse plugin (in case you are using it) to download the source
bundles together with the dependencies.
1)To create an eclipse project for Core, I had to disable the
m2eclipse maven plugin, manually select all source
directories, download all jar dependencies and force source level to 1.5.
I seem to have more luck. I updated to the latest versin of the plugin and
then just used the import function
to import the full monty. It worked fine, except of a little problem with
the antlr generated source files.
I updated the wiki page you mentioned: http://www.hibernate.org/422.html
Regarding annotations and entiry manager - I believe they also still use
Ant as build tool. Really only the core
got migrated to maven yet - correct me from wrong here. I actually haven't
build these projects/modules for quite a while. I think for our sanities
sake it would be great if we could migrater all projects/modules asap. I
think a lot of people are confused right now.
1:48 a.m.
I don't understand. Hibernate Search is still using Ant (with
Ivy) for the
build.
If you just want to build Hibernate Search you don't even need maven. I
know there
is a POM in the top level directory, but this is not a working maven POM
as such.
The ant to maven mirgration is still a open Jira issue within Hibernate
Search. In fact
I believe it is assigned to me. So far I was waiting for the core
migration to be finished.
Maybe it is a good time to start now ;-)
Anyways, the ant build works fine. However, I choose
to not depend on 'latest' version defined for commons-annotations,
annotations and entity manager.
I changed ivy.xml to depend on deployed versions from the jboss repo. If
you stick with 'latest' you
WILL have to build these modules locally.
And this is the part i don't understand....does everyone really go around manually
calling ant/mvn in the subprojects to get the jar and then be able to build based
on latest ?
Sound really tedius...
/max
2:29 a.m.
Thanks to everybody, you were all very helpful;
all your thoughts together made me clarify the situation
and I got a partially useful workspace now.
(still no search build but now I understand how to proceed)
I'll write down what to do if anyone had to repeat this:
1)for Core you have to checkout the whole tree, but this doesn't represent
a single project but a tree of projects; the result in eclipse is a list of
interdependent projects.
Also this makes it possible to use different java source versions in
different source directories.
Don't use m2eclipse to enable maven
on the checkout, but use
File->Import->General->Maven Projects
Note the plural: "Projects" this is going to generate the complete tree
of projects and link them together.
This process is going to fail if you didn't size the heap for maven,
I needed to set it to 512MB.
2)The other Hibernate packages (EntityManager, Annotations, Search...)
are more tricky: they have a misleading pom there, but you should use
the ant build. Unfortunately some links needed by Ivy are currently broken:
this is what caused all the trouble, you probably have the jars still in
the ivy cache.
Now at least I know I have to fix the Ivy dependencies, and not to expect
the maven to work ;-)
Emmanuel, I would suggest to reopen HSEARCH-1919 ?
I volunteer to write some instructions in the wiki, if someone points me
to the most appropriate page.
thanks again,
Sanne
6:57 a.m.
On May 17, 2008, at 04:29, Sanne Grinovero wrote:
2)The other Hibernate packages (EntityManager, Annotations,
Search...)
are more tricky: they have a misleading pom there, but you should use
the ant build. Unfortunately some links needed by Ivy are currently
broken:
this is what caused all the trouble, you probably have the jars
still in
the ivy cache.
Now at least I know I have to fix the Ivy dependencies, and not to
expect
the maven to work ;-)
Emmanuel, I would suggest to reopen HSEARCH-1919 ?
Tell me what you mean by some links needed by Ivy are currently
broken. What does it say?
7:55 a.m.
OK I found the problem and fixed it as part of the SLF4J migration
It was due to a misconfiguration of ivy.xml in entitymanager and a
stale ivy cache.
You might have to clean your ivy cache rm -fR ~/.ivy/cache
Emmanuel
On May 17, 2008, at 08:57, Emmanuel Bernard wrote:
On May 17, 2008, at 04:29, Sanne Grinovero wrote:
> 2)The other Hibernate packages (EntityManager, Annotations,
> Search...)
> are more tricky: they have a misleading pom there, but you should use
> the ant build. Unfortunately some links needed by Ivy are currently
> broken:
> this is what caused all the trouble, you probably have the jars
> still in
> the ivy cache.
> Now at least I know I have to fix the Ivy dependencies, and not to
> expect
> the maven to work ;-)
> Emmanuel, I would suggest to reopen HSEARCH-1919 ?
Tell me what you mean by some links needed by Ivy are currently
broken. What does it say?
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
6:34 p.m.
2008/5/17 Emmanuel Bernard <emmanuel(a)hibernate.org>:
OK I found the problem and fixed it as part of the SLF4J migration
It was due to a misconfiguration of ivy.xml in entitymanager and a stale ivy
cache.
You might have to clean your ivy cache rm -fR ~/.ivy/cache
Emmanuel
Hi Emmanuel, thanks for helping.
All problems are solved now! I can resume hacking
on my favorite project :-)
Sanne
3:05 p.m.
This is unfortunate.
These glitches were expected, and we will fix them as they pop up.
Though as Hardy said, the new HSearch build system is independent of
Hibernate Core. All the needed libraries are downloaded in build/lib/
core and build/lib/test
IM me if you need more help.
AFAIK JBoss Cache 2 is JDK 5 only, that explains the reason why the
module requires jdk 5 as well
On May 15, 2008, at 08:21, Sanne Grinovero wrote:
Most esteemed developers,
I was developing some patches for Hibernate Search but as I work on
it on my own
I don't have much time for it; currently some problems about the
move to Maven
have completely killed my productivity.
I have found some reference on your website;
The maven guide looks good: http://www.hibernate.org/422.html
but l would appreciate some more information for the eclipse users.
(are you all IDEA users?)
Specifically I have difficulty to understand how to set the correct
JDK:
A) cache-jbosscache2 requires JDK5 (for many reasons)
B) org.hibernate.test.ops.MergeTest requires JDK5, as it is using
autoboxing since commit 14610.
C) core is needing jdk1.4, but if I use JDK5 to fix A&B it doesn't
compile because
BlobImpl, ResultSetWrapper, SerializableBlob should implement new
methods that were added in the latest interface versions.
So I didn't understand how other developers are having their project
compile;
should I try setting a "mixed JDK" environment? Looks ugly.
Is it possible these problems are related to some maven setting I
got wrong?
Currently I disabled jbosscache2, changed the source code of MergeTest
and switched to JDK1.4,
but would like to hear you opinion about it.
Also I actually need jbosscache2 :-(
thanks in advance,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
5837
days inactive
5839
days old
16 comments
6 participants
participants (6)
-
Chris Bredesen -
Emmanuel Bernard -
Hardy Ferentschik -
Max Rydahl Andersen -
Sanne Grinovero -
Steve Ebersole