Remove the versioned jar from repo#579
Conversation
This was probably added to allow running warbler directly from the repository, but versioning the jar will bloat up the size of the repository with every commit, and it will usually be behind the actual source version. Removing here and we'll deal with fallout later. Supporting changes: * spec and integration targets should build jar first. * jar must be included explicitly in gem since it is no longer versioned. * clean should wipe out the jar.
|
Sadly I am now finding this rather irritating when trying to work on jruby-rack, since I need to change warbler version constraints to verify if warbler works OK with unreleased jruby-rack 1.3. Pointing examples to a warbler git branch was convenient.
Edit: OK, I see part of the the problem now; need to structure Gemfile differently to avoid require of local gems during Rails startup, as warbler doesn't "fix" these kinds of issues in your Gemfile for you, or warn you about problems with the generated war when referring to git and path sourced gems. Broadly related to #165 and a number of duplicates. But still get the below when trying to use off a locally built warbler gem (rather than a local git reference) Edit 2: OK, second mystery solved, this is a bundler problem due to bundling into a non-vendor directory, and getting confused across multiple jruby versions. :-/ |
This was probably added to allow running warbler directly from the repository, but versioning the jar will bloat up the size of the repository with every commit, and it will usually be behind the actual source version. Removing here and we'll deal with fallout later.