That does work, thanks. The sources jar also now contains the compiled
code, which is odd, but isn't harming anything.
On 8/19/09 1:39 AM, Alex Boisvert wrote:
The manual way to do it would be to write,
package(:jar, :classifier => 'sources').include :from => compile.sources
I think Buildr should default to the .jar extension to follow conventions if
the project's compile language is Java, Scala or Groovy... especially
considering that we expect the .jar extension when downloading sources for
the various IDEs. I'll look into this.
alex
On Tue, Aug 18, 2009 at 8:52 PM, Jeremy Huiskamp <
[email protected]> wrote:
Hi all,
I'm building a project (let's say projectA) with buildr and deploying the
jar and sources to a maven repository. I then have a separate project
(projectB) that pulls in projectA from the repository. The problem I'm
having is that projectA is calling the source bundle
projectA-1.0.0-SNAPSHOT-sources.zip and projectB is looking for
projectA-SNAPSHOT-sources.jar, which, as I understand it, is the standard
maven way to do it.
Is there any way to get "package :sources" to name the file .jar instead of
.zip?
Thanks,
Jeremy
