> 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
>>
>> 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
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
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
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 so
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
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 thre
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...
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 complete
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 no
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
>
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..
> 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 mav
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
> 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 te
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/h
> 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 s
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
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
19 matches
Mail list logo
