Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
maven plugin to handle rubygems in a maven way. including support for rspec, rails, cucumber, rake, etc
Java Ruby HTML JavaScript Other

Merge pull request #70 from leonidv/m2e-compatible

Adds compability with m2e (eclipse maven support)
latest commit 3f1242b601
@mkristian mkristian authored
Failed to load latest commit information.
bundler-maven-plugin [maven-release-plugin] prepare for next development iteration
cucumber-maven-plugin [maven-release-plugin] prepare for next development iteration
gem-assembly-descriptors [maven-release-plugin] prepare for next development iteration
gem-extension [maven-release-plugin] prepare for next development iteration
gem-maven-plugin add jars-lock mojo
gem-parent-mojo [maven-release-plugin] prepare for next development iteration
gem-proxy Forgot to filter out windows-only versions of gems
gem-with-jar-extension [maven-release-plugin] prepare for next development iteration
integration-tests [maven-release-plugin] prepare for next development iteration
jruby-maven-plugin Adds compability with m2e (eclipse maven support)
minitest-maven-plugin [maven-release-plugin] prepare for next development iteration
parent-mojo Add m2e plugins ignore.
rails3-maven-plugin Add m2e plugins ignore.
rake-maven-plugin [maven-release-plugin] prepare for next development iteration
rspec-maven-plugin [maven-release-plugin] prepare for next development iteration
ruby-tools when launching java do not add -client to the arguments
runit-maven-plugin [maven-release-plugin] prepare for next development iteration
tests-parent-mojo [maven-release-plugin] prepare for next development iteration
.gitignore cleanup
History.txt updated
README.md remark on how to run tests
TODO one more
eclipse-code-style.xml eclipse code style defintion
license.txt whitespaces
pom.xml [maven-release-plugin] prepare for next development iteration

README.md

jruby maven plugins

Build Status

gem artifacts

there is maven repository with torquebox.org which delivers gem (only ruby and java platform) from rubygems.org as gem-artifacts. adding this repository to pom.xml (or settings.xml) enables maven to use gem-artifacts like this

<repositories>
  <repository>
    <id>rubygems-release</id>
    <url>http://rubygems-proxy.torquebox.org/releases</url>
  </repository>
</repositories>
. . .
<dependency>
  <groupId>rubygems</groupId>
  <artifactId>compass</artifactId>
  <version>0.12.2</version>
  <type>gem</type>
</dependency>

now maven will resolve the transient dependencies of the compass gem and downloads the artifact (includng the gem file) into the local repository.

the next question is how to use those artfacts:

installing gems into you project directory

just add the gem-maven-plugin in your pom and execute the 'initialize'. that will install the gem artfacts and its depdencencies into 'target/rubygems'

<build>
  <plugins>
    <plugin>
      <groupId>de.saumya.mojo</groupId>
      <artifactId>gem-maven-plugin</artifactId>
      <version>${jruby.plugins.version}</version>
      <executions>
        <execution>
          <goals>
            <goal>initialize</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
  </plugins>
</build>

the will added as test-resource in way that you can use them with ScriptingContainer (from jruby) - see src/test/java/org/example/javasass/JavaSassTest.java from integration tests.

example: execute bin/compass from the compass gem

add the following to you pom

<plugin>
  <groupId>de.saumya.mojo</groupId>
  <artifactId>gem-maven-plugin</artifactId>
  <version>@project.parent.version@</version>
  <executions>
    <execution>
      <goals>
        <goal>exec</goal>
      </goals>
      <phase>compile</phase>
      <configuration>
        <execArgs>${project.build.directory}/rubygems/bin/compass compile ${basedir}/src/main/webapp/resources/sass</execArgs>
      </configuration>
    </execution>
  </executions>

this will execute compass from the compass gem during the compile phase. you can further isolate the gems by moving the dependency from root level into the plugin.

<plugin>
  <groupId>de.saumya.mojo</groupId>
  <artifactId>gem-maven-plugin</artifactId>
    <version>@project.parent.version@</version>
    <executions>
      <execution>
        <goals>
          <goal>exec</goal>
        </goals>
        <phase>compile</phase>
        <configuration>
          <execArgs>${project.build.directory}/rubygems/bin/compass compile ${basedir}/src/main/webapp/resources/sass</execArgs>
        </configuration>
      </execution>
    </executions>
    <dependencies>
      <dependency>
        <groupId>rubygems</groupId>
        <artifactId>compass</artifactId>
        <version>0.12.2</version>
        <type>gem</type>
      </dependency>
    </dependencies>
  </plugin>

see also gem-maven-plugin/src/it/execute-compass-with-gems-from-plugin

more examples

for more example look into the integration test of the various plugins

running the intergration tests

mvn clean install -Pintegration-test -Pall

contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

meta-fu

enjoy :)

Something went wrong with that request. Please try again.