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

Need help on building to macosx dist #113

Closed
mechazod opened this issue Aug 26, 2016 · 8 comments
Closed

Need help on building to macosx dist #113

mechazod opened this issue Aug 26, 2016 · 8 comments

Comments

@mechazod
Copy link

mechazod commented Aug 26, 2016 •
edited
Loading

screen shot 2016-08-26 at 10 28 40 am
@damencho
Copy link
Member

Please use the mailinglist before opening issues.
Read the beginning of the ant build.xml file, there are instructions you are missing.

@mechazod
Copy link
Author

@damencho yes, I'm figure out how to build, thanks for closing the issue. 👍

@benjumanji
Copy link

benjumanji commented Sep 3, 2016 •
edited
Loading

@damencho For the record, while you might enjoy closing peoples issues with rtfm the fact is that the readme emblazoned across the front of the repo is wrong because it points to a guide that will lead to people bumping into exactly this issue, which is that your build has bad hygiene.

Thank you @mechazod for raising this, because between you and @damencho I now have a working build, and I didn't have to work too hard to achieve that.

@benjumanji
Copy link

Actually I spoke too soon. I assumed the instructions in the build.xml would yield a working build.

Running mvn dependency:get -DartifactId=maven-ant-tasks -DgroupId=org.apache.maven -Dversion=2.1.3 lands me with an error. It turns out that mvn dependency:get -DartifactId=maven-ant-tasks -DgroupId=org.apache.maven -Dversion=2.1.3 -DrepoUrl=http://repo1.maven.apache.org/maven2 actually gets maven to play nicely. Even having done that, and having a populated .m2 running the suggested ant command doesn't work. Please reopen as your build instructions are broken and that is an issue.

@benjumanji
Copy link

benjumanji commented Sep 3, 2016 •
edited
Loading

It seems that the build behaves a bit better with a later ant. Thanks for nothing Centos 7. It still fails.

BUILD FAILED
/home/ben/src/thirdparty/jicofo/build.xml:54: Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:jar': Cannot find parent: org.sonatype.oss:oss-parent for project: com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:jar:1.0_jdk5 for project com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:jar:1.0_jdk5
  com.googlecode.concurrentlinkedhashmap:concurrentlinkedhashmap-lru:jar:1.0_jdk5

from the specified remote repositories:
  jitsi-maven-repository-snapshots (https://github.com/jitsi/jitsi-maven-repository/raw/master/snapshots/),
  jitsi-maven-repository-releases (https://github.com/jitsi/jitsi-maven-repository/raw/master/releases/),
  central (http://repo1.maven.org/maven2),
  sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots)

Path to dependency: 
    1) org.jitsi:jicofo:jar:1.0-SNAPSHOT
    2) org.igniterealtime:tinder:jar:1.2.3

@benjumanji
Copy link

benjumanji commented Sep 3, 2016 •
edited
Loading

~/.m2/repository/org/sonatype/oss/oss-parent/3/oss-parent-3.pom

contains

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

I can see why this would be a problem.

@damencho
Copy link
Member

damencho commented Sep 3, 2016

The build is working fine, as a lot of developers are using it.
The later is a known maven problem we face from time to time, and you need to remove that file or any file that had this wrong content.
I'm closing issues as the first Readme file on all of the project says, please send a mail to the mailinglist and if we (as developers) decide this is a bug, problem or feature that is worth tracking we kindly ask the user to create the issue. Otherwise every user question becomes an open issue, and it is hard to maintain something uptodate.

@benjumanji
Copy link

I dunno. I have deleted my entire maven cache. I have tried building inside
a container, and inside of a fresh vms. I can't get it working. I'm not
particularly invested in this project so I'm not going to pursue it any
further but if you guys want to tell yourself you have a healthy build go
right ahead.

Peace.

On Sat, 3 Sep 2016, 20:34 Дамян Минков, notifications@github.com wrote:

The build is working fine, as a lot of developers are using it.
The later is a known maven problem we face from time to time, and you need
to remove that file or any file that had this wrong content.
I'm closing issues as the first Readme file on all of the project says,
please send a mail to the mailinglist and if we (as developers) decide this
is a bug, problem or feature that is worth tracking we kindly ask the user
to create the issue. Otherwise every user question becomes an open issue,
and it is hard to maintain something uptodate.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#113 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AARufYgKb26awVRBiLLkhKE7ws7iP5luks5qmcvZgaJpZM4Jtr7Y
.

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
3 participants
@benjumanji @damencho @mechazod