You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 14, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 14, 2023. It is now read-only.
Revise our maven url sources in the ros plugin@talregev is using the list below. I do not believe we need to add the rep.maven.xxx or central.maven.xxx - these should be automatically picked up by mavenCentral(). The jfrog is the standout one there - what is in that?
from jforg we can pull all the jars dependencies:
this dependencies alredy was in ours github maven repository so i added this links that it will update from here and not from github.
make sure after that migration, android_core still compile.
I try to do this, and i get an conflict with old jar: com.springsource.org.apache.commons.codec:1.3.0
yes :)
need to understand how get rid of this.
I try also compile javaros_core with new jars apache.directory.studio dependencies too but it didn't help.
I think need also to re-create all the messages and rosjava_messages with new dependencies
can you check it?
If you succeeded that will be great. and you will need to update maven_repository sooner that you thought. can
Activity
talregev commentedon Feb 11, 2015
from jforg we can pull all the jars dependencies:
this dependencies alredy was in ours github maven repository so i added this links that it will update from here and not from github.
http://repo.jfrog.org/artifactory/libs-releases/org/apache/commons/com.springsource.org.apache.commons.codec/
http://repo.jfrog.org/artifactory/libs-releases/org/apache/commons/com.springsource.org.apache.commons.httpclient/
http://repo.jfrog.org/artifactory/libs-releases/org/apache/commons/com.springsource.org.apache.commons.io/
http://repo.jfrog.org/artifactory/libs-releases/org/apache/commons/com.springsource.org.apache.commons.lang/
http://repo.jfrog.org/artifactory/libs-releases/org/apache/commons/com.springsource.org.apache.commons.logging/
http://repo.jfrog.org/artifactory/libs-releases/org/apache/commons/com.springsource.org.apache.commons.net/
in github it found here:
https://github.com/rosjava/rosjava_mvn_repo/tree/master/org/apache/commons
talregev commentedon Feb 19, 2015
it better to switch to apache.directory.studio instead com.springsource.org
like @DmitryDzz has done in his fix
i will write down the links again:
i will change that at rosjave_bootstrap and rosjava_core, and i will see if it pass all the tests.
stonier commentedon Feb 20, 2015
Started migration in rosjava_bootstrap. Will hold off on the others for now till we're sure it's all working.
Also - rosjava_core is a problem -
org.apache.commons.netisn't in the directory studio group.talregev commentedon Feb 20, 2015
can you add this links to manven repository?
talregev commentedon Feb 20, 2015
make sure after that migration, android_core still compile.
I try to do this, and i get an conflict with old jar: com.springsource.org.apache.commons.codec:1.3.0
stonier commentedon Feb 20, 2015
Ah, this thing:
revert move to mavenCentral for apache artifacts, see #40.
talregev commentedon Feb 20, 2015
yes :)
need to understand how get rid of this.
I try also compile javaros_core with new jars apache.directory.studio dependencies too but it didn't help.
I think need also to re-create all the messages and rosjava_messages with new dependencies
can you check it?
If you succeeded that will be great. and you will need to update maven_repository sooner that you thought. can
can you ask @DmitryDzz how he solve this issue?
talregev commentedon Feb 20, 2015
i added you on gtalk. so if you available to talk ....
DmitryDzz commentedon Feb 20, 2015
I've been watching you 8-)
I didn't try to solve this issue. My project is on hold for a while. I believe I'll come back in a month. Sorry.
talregev commentedon Feb 20, 2015
it ok :)
talregev commentedon Feb 23, 2015
you can close this issue:
#37