And the maven compiler won't work either - you get a "[ERROR] Don't resolve expressions during indexing!" exception if you attempt to re-use a step (even within the original file).
You can replicate with a feature similar to the below (usage "mvn clean test-compile", if you only have the first scenario in the feature, the compile works. When you have the second one, mapped to the steps from the first, it breaks):
Feature: Test
Scenario: Test something
Calculator calculator
int result
Given A calendar
calculator = new Calculator
When I add "2" and "3"
result = calculator.Add(args.first.toInt, args.second.toInt)
Then I should get "5"
result should be args.first.toInt
Scenario: Test something else
Given A calendar
When I add "3" and "10"
Then I should get "15"