Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

On scala-2.8 branch, running "publish-local" action from sbt doesn't publish the jar locally, only the ivy.xml #5

Closed
LeifW opened this issue Apr 22, 2010 · 2 comments
Closed

On scala-2.8 branch, running "publish-local" action from sbt doesn't publish the jar locally, only the ivy.xml #5

LeifW opened this issue Apr 22, 2010 · 2 comments

Comments

@LeifW
Copy link
Contributor

LeifW commented Apr 22, 2010

And that ivy.xml just references a non-existant .war artifact.
This can be worked around by copying the jar file out of /target and into $HOME/.ivy2/local/com.thinkminimo.step/step_2.8.0.RC1/1.1.6-SNAPSHOT/jars/step_2.8.0.RC1.jar
and editing the ivy.xml to say the artifact is a .jar, not a .war.
@rossabaker
Copy link
Member

I suspect that this is another symptom of the sbt hack that caused Issue #3. There's a fork from Rubbish that splits Step into two projects. I think that this is the right approach -- I'm going to look into pulling this as soon as I have time.

@rossabaker
Copy link
Member

See resolution to issue #5.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LeifW @rossabaker