I was going to comment on http://issues.apache.org/jira/browse/ODE-729,
but I think having discussions
on the mailing list works better then in jira. So I'm going to add this
thread and add 2 more pain-points
1. There can be issues between ruby and java if somehow the bit versions
used are out of sync (32 vs 64 bit). It simply blows up without much
detail as to what happened. So much easier to use 1 environment (java).
Yeah I know you will tell me to use jruby.
2. Adhereing to an Apache standard build tool and environment. Maven
forces a common layout, build and release process.
3. Tooling support. I can get my IDE setup easily using a maven-eclipse
plugin.
4. Dependency management. Projects that consume ODE (i.e. Riftsaw) need
to know the dependency, compile, runtime and test. Maven does this for
me and it makes it easy for me to display it, again though plugins into
my IDE.
5. I have a hard time running multiple buildr versions. I have 1.2.10
working now, but as soon as I also install 1.3.x, then 1.2.10 breaks as
some gem dependency gets skrewed up. Which forces me to painstakingly
remove gems until 1.2.10 works again.
6. I like a minimal build; have it just work, by convention of the
layout of the project, maven done right does not 'get-in-the-way', and I
only have to worry about bugs in one build tool; not in two.
7. Check the mailing list to see how many people having issues getting
their build going.
thx,
--Kurt
Jeff Yu wrote:
here are couple issues that I had (before I talked about my current task)
1. I knew buildr is quite new, but the adoption is really an issue. The
adoption means the plugins, and the work that I need to do. I remembered
that one task that I was working on is to try to push the artifacts into
maven snapshot repository, which is webdav protocol. Simply I just couldn't
find a 'just works' plugin for me to do so. In the end, I used the
maven-ant-task to do the publish, as I had a problem by using buildr against
our repo, I tried the way as Alex Boisvert pointed out in buildr maillist,
couldn't work against our repo, quite frustrating.
2. It requires developer to learn Ruby. I know it sounds interesting to
learn a new language, but sometimes I just want to make my build system just
works and easily been understood.
3. It also depends on specific library version. If you go to the
.gem/ruby/1.8/gems/buildr-1.3.5/addon/buildr directory, take xmlbeans.rb as
an example, it depends on a specific xmlbeans version, what if I used a
different version in my own project, does it require me to update this to
make these version consistent. same goes to the hibernate.rb etc.
4. Don't have enough documentation for how to write an addon, how did the
buildr work underlie, like I still didn't understand in the dao-hibernate
module, how the mvn-hibernate.xml was used when I run 'buildr publish'.
.....
other comments inline.
On Wed, Dec 9, 2009 at 9:12 AM, Alexis Midon <[email protected]> wrote:
Hi Jeff,
What are your pain points?
see my above
how does your task look like? Do you know you can easily reuse Ant tasks
from Buildr?
I belive my task would be like the openjpa.rb, one thing I need to
understand is do I need to put my *.rb into the buildr's addon directory? or
where should I put? sorry if it sounds obvious. I knew it last time when I
work on the buidr with my maven snapshot repo. I didn't try it this time as
I want to do it like what openjpa.rb or hibernate.rb did now. But I will try
it again some time.
see $ode/tasks/derby.rake for instance.
The learning might feel steep but once you passed that point, you'll see
how
crazy it is to write Maven plugins.
It seems that I didn't pass that point yet. :(
-Jeff
Alexis
On Thu, Dec 3, 2009 at 6:37 AM, Jeff Yu <[email protected]> wrote:
+1.
It really adds a steep learning curve for newcomers to contribute to ODE.
I
don't know how long it will take me to write the task to use Hibernate
builtin tool to generate ddl from the JPA's annotation. :-(, wish someone
else could help me on this task.
-Jeff
On Thu, Dec 3, 2009 at 9:53 PM, Kurt T Stam <[email protected]> wrote:
Tammo van Lessen wrote:
On 03.12.2009 14:41, Jeff Yu wrote:
Hi Tammo,
It WORKS great with buildr 1.3.4. ;-)
Do you know any reason that why I would get 'segmentation fault'
against
JDK1.6? I am seeing this quite frequently, but just for 1.3.5, I
believe
it
is same for buildr 1.2.10
No, sorry. I had them a year ago on a linux machine. I though that it
was related to the ruby-java bridge, but that's just wild guessing.
Using JRuby might help.
Tammo
Yeah I believe the issue is mixing the bit (32/64) versions between
ruby
and java. I have it all working on my machine - and have given it 6
months
to get used to - but have to say I'm not a huge fan of using ruby and
buildr. It's a very fragile setup, and it increases the number of links
in
the chain. I think 20% of all msgs on the user/dev list are about this
particular issue..
my 2 cents
--Kurt
