Outrigger 2.1 no longer in central maven repo?
Dawid Loubser
Downloading: http://repo1.maven.org/maven2/com/sun/jini/outrigger/2.1/outrigger-2.1.pom
Missing artifact descriptor for com.sun.jini:outrigger:jar:dl:2.1
A peek at: http://repo1.maven.org/maven2/com/sun/jini/ in your browser
confirms this. This of course used to be available (that's how I got
it in my local repo in the first place) but does anybody know what
happened to Outrigger? I fear that deployments to new machines
(without it in their repos) may no longer work.
Plan B is to put it in our company repo, but I don't think the Aether
Resolver supports maven repos with password authentication?
regards,
Dawid
Dennis Reedy
Dennis
Dawid Loubser
seeing the above warning in my logs. I wish the River project would
get their act together and start publishing to a Maven repo? (kinda
crazy that they aren't)
Dawid
On Mar 1, 3:33 pm, Dennis Reedy <dennis.re...@gmail.com> wrote:
> AFAIK, Outrigger (and any other Jini artifact) have never been pushed to central. I put outrigger and reggie in the Rio maven repository.
>
> Dennis
>
> On Mar 1, 2012, at 729AM, Dawid Loubser wrote:
>
>
>
>
>
>
>
> > Slightly off-topic: I am seeing a lot of these in my logs:
>
>
Jeff Ramsdale
by Chris Sterling:
http://search.maven.org/#search%7Cga%7C1%7Cjini
He wrote a Maven Jini Plugin years ago that could be used to start and
stop the core Jini services.
-jeff
Dennis Reedy
Thanks for that, I think that Chris's contributions are missed. I am going to deploy Apache River Jini 2.1.1. artifacts to the Rio maven 2 repository and use those as dependencies for Rio 5.0. One of the main reasons is the Jini 2.1 artifacts used the approach of "dl" classifiers for the download (client) artifacts of a service. With the conventions that we have established with Rio, the "dl" classifier no longer makes sense.
With that in mind, look for the new/old Jini 2.1.1 artifacts to be available in the Rio maven repository.
Note: I have resisted requests in the past to publish all Jini artifacts, primarily because they are not under my control. That being said, are there any Jini services (other then reggie & outrigger) that you want me to have available in the Rio maven repository?
Dennis
Dawid Loubser
> Note: I have resisted requests in the past to publish all Jini artifacts, primarily because they are not under my control. That being said, are there any Jini services (other then reggie & outrigger) that you want me to have available in the Rio maven repository?
artifacts, you should go ahead. From our perspective, the only
"standard" Jini services we use over and above what Rio already
provides is JavaSpaces (outrigger) and TransactionManager (mahalo).
regards,
Dawid
Jeff Ramsdale
Any reason you wouldn't use the River 2.2.0 artifacts? I suppose I do
think it makes sense to reformulate the River artifacts to better suit
Rio--I know I've resisted reformulations in the past. Any chance, you
think, of doing it in such a way that the River community might buy
into the structure? There's definitely more openness to change now
than in the past. On the off chance that they do accept your
contribution they might choose to make minor changes and release their
own artifacts (rather than using yours), so you might consider
addressing your artifacts in such a way that they are clearly Rio
artifacts so they wouldn't collide with a potential future River
artifact of the same release.
The service I've most often wished were available is Mahalo. But If
the other starter kit services might help people see the value of
Jini/Rio I think their inclusion should be considered (weighed against
the cost of implementation).
-jeff
Dennis Reedy
I'm not sure I understand your direction wrt the reformulation of River artifacts. What do you mean by that? My plan was to simply deploy the artifacts as is. What would you propose the reformulation be?
Dennis