river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Ramsdale <jeff.ramsd...@gmail.com>
Subject Re: River jar files in mvnRepository
Date Thu, 18 Mar 2010 21:54:44 GMT
Hi Brian, Good to hear from you!

I believe these jars were posted several years ago by Chris Sterling
as part of the Maven Jini Plugin:
https://maven-jini-plugin.dev.java.net/ At the time things were
different in both the Maven and Jini worlds--a little more
free-for-all in posting artifacts to Maven and no one in the Jini
world thinking too much about Maven. I think it would be better for
Apache River to manage its own artifacts now (and I don't think Chris
plans to maintain the plugin).

I posted a Jira issue for exactly this issue:
http://issues.apache.org/jira/browse/RIVER-317 and as a result someone
posted the poms I provided to svn but no process was put into place to
apply those poms to the artifacts and deploy them to the Central
Repository. I was going to raise the issue again after the current
vote completed. Meanwhile, Dennis Reedy had some very reasonable
comments about the poms I posted. A little more discussion is probably
warranted prior to releasing the artifacts as Maven artifacts. Dennis
has some experience now with using Jini jars and Maven with the latest
Rio builds. Perhaps he'll reiterate his suggestions to the list? I'd
be glad to help out but we'll need someone on the inside to assist in
getting things deployed once we work out the pom details.

By the way, mvnrepository.com is an ad site that scrapes the real
Maven Central Repository. Helpful for searches, perhaps, but not
definitive. The real repo is at http://repo1.maven.org/maven2/ and can
be searched via http://repository.sonatype.org.

Finally, the service jars (reggie, outrigger, etc.) are under the
services dir (https://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/poms/services/)
but that's an interesting point about jini-core and jini-ext. Are
these still artifacts of the build?


On Thu, Mar 18, 2010 at 2:31 PM, Brian Murphy <btmurphy.alt@gmail.com> wrote:
> It appears that someone has uploaded a number of
> the River jar & zip files as artifacts to the mvnRepository
> site (http://mvnrepository.com/search.html?query=jsk-platform).
> That is,
> jsk-platform.jar, jsk-lib.jar, jsk-resources.jar
> jini-core.jar, jini-ext.jar,
> jini-starterkit.zip, jini-start-examples.zip
> Thanks to that person/people, by the way.
> Although poms corresponding to each of the jar files
> that are produced by a river build were created and
> checked in to the river repository
> (https://svn.apache.org/repos/asf/incubator/river/jtsk/trunk/poms),
> it appears that many of the other jar files from the
> build were not uploaded. In particular,
> start.jar, tools.jar
> reggie.jar, reggie-dl.jar
> outrigger.jar, outrigger-logstore.jar, outrigger-snaplogstore.jar
> mahalo.jar, mahalo-dl.jar
> etc.
> Was there a reason these other jar artifacts were excluded?
> (I'm not a maven user so I admit that I may be unfamiliar
> with the conventions of maven and that repository).
> If not, is there a mechanism or protocol for getting them included?
> [As a side note, for what it's worth, if folks are still using jini-core.jar
> and jini-ext.jar, they should consider no longer using those jars;
> and use jsk-platform.jar, jsk-resources.jar, and jsk-lib.jar instead.]
> Thanks for any help and/or insight regarding this issue,
> Brian

View raw message