Re: [hibernate-dev] Sync maven jboss repo with central repo?
Yes, I also forsee the pissing contest unfortunately. Part of the problem is that there are the same artifacts in both repositories with differing poms. Which pom is correct? This makes troubleshooting a nightmare when 2 developers are getting different results, only to finally find out that one of them had the jboss repo as an extra repo in their settings.xml, or even just once built a project that used the jboss repo and now has differing artifacts in their local repo. Bad example since version is slightly different but shouldn't be(ga compared to GA) but still shows pom differences. http://repository.jboss.org/maven2/org/hibernate/hibernate-validator/3.0.0.GA/hibernate-validator-3.0.0.GA.pom http://repo1.maven.org/maven2/org/hibernate/hibernate-validator/3.0.0.ga/hibernate-validator-3.0.0.ga.pom Maven central version has no dependencies. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync maven jboss repo with central repo?
Hi, On Fri, 16 May 2008 15:25:25 +0200, Tomislav Stojcevich <[EMAIL PROTECTED]> wrote: Bad example since version is slightly different but shouldn't be(ga compared to GA) but still shows pom differences. http://repository.jboss.org/maven2/org/hibernate/hibernate-validator/3.0.0.GA/hibernate-validator-3.0.0.GA.pom http://repo1.maven.org/maven2/org/hibernate/hibernate-validator/3.0.0.ga/hibernate-validator-3.0.0.ga.pom It gets even worse - not only does the content of the POM differ, but depending on your OS you might not even now. Since windows is case insensitive there is not difference between 'ga' and 'GA'. On Unix of course this are different versions. I got caught in this trap in a project where some people developed on windows and some on Linux and the POM got changed. It was a real pain to figure out why things were working for one part of the team and not for the others :( I wish there would be an easy way to sort this POM hell out. --Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync maven jboss repo with central repo?
> Yes, I also forsee the pissing contest unfortunately. > > Part of the problem is that there are the same artifacts in both > repositories with differing poms. Which pom is correct? I vote for the pom maintained by the dev team behind the project - anything else is an approximiation. I'm not saying our pom's are perfect, but at least they are now actively maintained. Just my additional 2 cent. /max ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync maven jboss repo with central repo?
That is IMO a maven bug... /max > Hi, > > > On Fri, 16 May 2008 15:25:25 +0200, Tomislav Stojcevich > <[EMAIL PROTECTED]> wrote: > >> Bad example since version is slightly different but shouldn't be(ga >> compared to GA) but still shows pom differences. >> http://repository.jboss.org/maven2/org/hibernate/hibernate-validator/3.0.0.GA/hibernate-validator-3.0.0.GA.pom >> http://repo1.maven.org/maven2/org/hibernate/hibernate-validator/3.0.0.ga/hibernate-validator-3.0.0.ga.pom > > It gets even worse - not only does the content of the POM differ, but > depending on your OS you might not even now. > Since windows is case insensitive there is not difference between 'ga' and > 'GA'. On Unix of course this are different versions. I got caught in this > trap in a project where some people developed on windows and some on Linux > and the POM got changed. It was a real pain to figure out why things were > working for one part of the team and not for the others :( I wish there > would be an easy way to sort this POM hell out. > > --Hardy > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync maven jboss repo with central repo?
> I vote for the pom maintained by the dev team behind the project - anything > else is an approximiation. > > I'm not saying our pom's are perfect, but at least they are now actively > maintained. > > Just my additional 2 cent. > /max > I agree 100%, I think the poms that come from the project team should be the 'correct' poms and win. This is why I'm asking for a sync to central. Without the sync, people will continue to request new versions of the hibernate artifacts added to central, their bundles may have differing poms for whatever reason, thus making the existing problem even worse. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
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/lucene-core-2.3.1.pom
(the signature) instead of
http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lucene-core-2.3.1.pom.xml
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 <[EMAIL PROTECTED]>:
> 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@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
> -
> Steve Ebersole
>
> Project Lead
> http://hibernate.org
> [EMAIL PROTECTED]
>
>
>
>
>
_
Re: [hibernate-dev] No successful builds since move to Maven
> 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 <[EMAIL PROTECTED]>:
>> 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@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>>
>> -
>> Steve Ebersole
>>
>> Project Lead
>> http://hibernate.org
>> [EMAIL PROTECTED]
>>
>>
>>
>>
>>
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
2008/5/16 Max Rydahl Andersen <[EMAIL PROTECTED]>:
>> 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 <[EMAIL PROTECTED]>:
>>> 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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>>
>>> -
>>> Steve Ebersole
>>>
>>> Project Lead
>>> http://hibernate.org
>>> [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>>
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
>
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync maven jboss repo with central repo?
Max Rydahl Andersen wrote: >> Yes, I also forsee the pissing contest unfortunately. >> >> Part of the problem is that there are the same artifacts in both >> repositories with differing poms. Which pom is correct? > > I vote for the pom maintained by the dev team behind the project - anything > else is an approximiation. > > I'm not saying our pom's are perfect, but at least they are now actively > maintained. However, there's also the "Release versions may never change once published" rule, which applies for good reasons: * If released artifacts are changed, builds depending on them are unexpectedly non-reproducible. * If released artifacts are changed, there's no mechanism for updates to happen to local repositories caching the old versions, so some people will see the old version and some the new, indefinitely. Now, arguably, both of the above would best be solved with architectural changes to Maven, but for the moment, strict adherence to "no changes to releases once deployed" is the only way to maintain a modicum of sanity. What would be nice, is for automated syncing of all *new* releases to the jboss repository to be initiated, which surely can't be that controversial? (Though there may be issues where new releases depend on things in the jboss repo that are not in the central repo, but I guess they'll need addressing on a case-by-case basis anyway.) Max. signature.asc Description: OpenPGP digital signature ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Sync maven jboss repo with central repo?
On May 16, 2008, at 12:28 PM, Max Bowsher wrote: What would be nice, is for automated syncing of all *new* releases to the jboss repository to be initiated, which surely can't be that controversial? (Though there may be issues where new releases depend on things in the jboss repo that are not in the central repo, but I guess they'll need addressing on a case-by-case basis anyway.) And this is what we requested. To have all artifacts under the org.jboss and org.hibernate groupIds to synch into the central repo. And this was many months ago. I just pinged the person responsible for that from the JBoss side (its pgier on irc max) to see how the situation looks at this point. - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
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 [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
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 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] SLF4J 1.4.2
Cool, I've almost completed the migration based on 1.4.2 A migration with no issue is like cake without ice: not worth it ;) On May 16, 2008, at 02:35, Steve Ebersole wrote: Because 1.4.2 was just released when I did that migration, as I already answered on that monsterous JBoss dev list thread ;) I have no issue with upgrading as long as no issues are created by that. On May 15, 2008, at 5:30 PM, Emmanuel Bernard wrote: Any reason why we target SLF4J 1.4.2 and not 1.5? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
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/lucene-core-2.3.1.pom
(the signature) instead of
http://repository.jboss.com/maven2/org/apache/lucene/lucene-core/2.3.1/lucene-core-2.3.1.pom.xml
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 <[EMAIL PROTECTED]>:
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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROTECTED]
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
On Fri, 16 May 2008 18:51:27 +0200, Sanne Grinovero <[EMAIL PROTECTED]> 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. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] SLF4J 1.4.2
Awesome to see two hibernate developers now spending their energy on such an important refactoring. Keep up the good work. Emmanuel Bernard wrote: Cool, I've almost completed the migration based on 1.4.2 A migration with no issue is like cake without ice: not worth it ;) On May 16, 2008, at 02:35, Steve Ebersole wrote: Because 1.4.2 was just released when I did that migration, as I already answered on that monsterous JBoss dev list thread ;) I have no issue with upgrading as long as no issues are created by that. On May 15, 2008, at 5:30 PM, Emmanuel Bernard wrote: Any reason why we target SLF4J 1.4.2 and not 1.5? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] SLF4J 1.4.2
Good to see Bill Burke being, well Bill Burke. On May 16, 2008, at 5:09 PM, Bill Burke wrote: Awesome to see two hibernate developers now spending their energy on such an important refactoring. Keep up the good work. Emmanuel Bernard wrote: Cool, I've almost completed the migration based on 1.4.2 A migration with no issue is like cake without ice: not worth it ;) On May 16, 2008, at 02:35, Steve Ebersole wrote: Because 1.4.2 was just released when I did that migration, as I already answered on that monsterous JBoss dev list thread ;) I have no issue with upgrading as long as no issues are created by that. On May 15, 2008, at 5:30 PM, Emmanuel Bernard wrote: Any reason why we target SLF4J 1.4.2 and not 1.5? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
>> >> 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 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] No successful builds since move to Maven
> 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 understanddoes 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 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
