jruby is a "bad" maven citizen
------------------------------

                 Key: JRUBY-4675
                 URL: http://jira.codehaus.org/browse/JRUBY-4675
             Project: JRuby
          Issue Type: Improvement
    Affects Versions: JRuby 1.x+
            Reporter: kristian meier
            Assignee: Thomas E Enebo
         Attachments: 
0001-make-jruby.jar-a-better-maven-citizen-on-the-pom-lev.patch

I restrict myself to the part which effects users of that maven artifact 
jruby.jar and leave away the "nice to have" parts.

with this artifact you can not use another version of joda library without 
ending up with two joda libraries in the classpath. dito for the jline library.

the provided scope is only for compile and test time and these dependencies are 
not transitive, i.e. they do NOT contribute to the classpath for any maven 
build using the artifact. since ant is building the jar they are just not 
needed beside maybe for book keeping.

once the 3rd party libs got fixed I can use this jar to compile my code against 
it. but the moment I need I newer version of any of the "implicit" dependencies 
like jffi I face the same problem as with the 3rd party libraries but here the 
problem with the "provided" scope spawns over all the jruby artifacts. as an 
interim solution one can resolve the "provided" transitive dependencies hull 
manually and declare them as deps in jruby.jar artifact (which is already done 
- just leave out the scope). 

the last step is NOT to include the classes which are part of the dependencies 
- exception are the ASM classes.

if the jruby.jar became a nice maven citizen I can use it the usual way to 
compile my classes against jruby but I still miss one thing for runtime: 
jruby-home.jar

with this new artifact I would have all I need for a nice maven setup using 
jruby. and this jruby-home.jar can have a new release when I new version for 
rubygems comes out (a current blocker with jruby-complete.jar and latest 
version of bundler !!). my ant skills are many years dormant so I skipped the 
patch for jruby-home.

last thing I realized is that the org.objectweb.asm package gets not mapped as 
in the jruby-complete.jar - I guess the purpose of repacking is also true for 
jruby.jar


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to