Rhino 1.7R3 in Maven central respository
274 views
Skip to first unread message
Stephen McKamey
Jul 12, 2011, 5:42:17 PM7/12/11
to mozilla-rhino
I'd like to plead to whomever has the authority to update the Maven
central with the release build of Rhino 1.7R3. This has been a
blocking issue for years for all Maven users needing 1.7R3
functionality and it would be great to have it resolved.
The full instructions are here:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
The repository is here (notice 1.7R2 is the latest):
http://repo1.maven.org/maven2/rhino/js/
If there's anything we maven users can do to help please let us know.
Thanks in advance,
smm
central with the release build of Rhino 1.7R3. This has been a
blocking issue for years for all Maven users needing 1.7R3
functionality and it would be great to have it resolved.
The full instructions are here:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
The repository is here (notice 1.7R2 is the latest):
http://repo1.maven.org/maven2/rhino/js/
If there's anything we maven users can do to help please let us know.
Thanks in advance,
smm
felipe valdez
Jul 12, 2011, 5:43:46 PM7/12/11
to mozill...@googlegroups.com
Attila Szegedi
Jul 12, 2011, 6:16:59 PM7/12/11
to mozill...@googlegroups.com
Jeez… I'm looking at that and it's all wrong. groupId=rhino, artifactId=js, seriously? It should be groupId=org.mozilla and artifactId=rhino.
Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
Attila.
Stephen McKamey
Jul 12, 2011, 6:38:26 PM7/12/11
to mozilla-rhino
Excellent, thanks! Yeah the group/artifact IDs don't really follow
conventions but it looks like they've been that way for a long time.
Just getting the latest bits out there would be huge.
On Jul 12, 3:16 pm, Attila Szegedi <szege...@gmail.com> wrote:
> Jeez… I'm looking at that and it's all wrong. groupId=rhino, artifactId=js, seriously? It should be groupId=org.mozilla and artifactId=rhino.
>
> Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
>
> Attila.
>
> On Jul 12, 2011, at 2:42 PM, Stephen McKamey wrote:
>
>
>
>
>
>
>
> > I'd like to plead to whomever has the authority to update the Maven
> > central with the release build of Rhino 1.7R3. This has been a
> > blocking issue for years for all Maven users needing 1.7R3
> > functionality and it would be great to have it resolved.
>
> > The full instructions are here:
> >https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repos...
conventions but it looks like they've been that way for a long time.
Just getting the latest bits out there would be huge.
On Jul 12, 3:16 pm, Attila Szegedi <szege...@gmail.com> wrote:
> Jeez… I'm looking at that and it's all wrong. groupId=rhino, artifactId=js, seriously? It should be groupId=org.mozilla and artifactId=rhino.
>
> Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
>
> Attila.
>
> On Jul 12, 2011, at 2:42 PM, Stephen McKamey wrote:
>
>
>
>
>
>
>
> > I'd like to plead to whomever has the authority to update the Maven
> > central with the release build of Rhino 1.7R3. This has been a
> > blocking issue for years for all Maven users needing 1.7R3
> > functionality and it would be great to have it resolved.
>
> > The full instructions are here:
Attila Szegedi
Jul 12, 2011, 7:11:21 PM7/12/11
to mozill...@googlegroups.com
Yeah, I'll get it out. However, I'm quite firmly set on having groupId=org.mozilla and artifactId=rhino, so you guys will have to make sure to update your dependencies accordingly… This'll fortunately be a one-time thing.
Attila.
James Cook
Jul 12, 2011, 8:58:26 PM7/12/11
to mozill...@googlegroups.com
Great to hear! Changing of the group and artifact are a very small price to pay for getting this deployed via Maven.
-- jim
Stephen McKamey
Jul 14, 2011, 9:45:10 PM7/14/11
to mozilla-rhino
Looks like it was approved pretty quickly.
Looking forward to this. Thanks Attila.
Looking forward to this. Thanks Attila.
> Jeez… I'm looking at that and it's all wrong. groupId=rhino, artifactId=js, seriously? It should be groupId=org.mozilla and artifactId=rhino.
>
> Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
>
> Attila.
>
> On Jul 12, 2011, at 2:42 PM, Stephen McKamey wrote:
>
>
>
>
>
>
>
> > I'd like to plead to whomever has the authority to update the Maven
> > central with the release build of Rhino 1.7R3. This has been a
> > blocking issue for years for all Maven users needing 1.7R3
> > functionality and it would be great to have it resolved.
>
> > The full instructions are here:
> >https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repos...
>
> Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
>
> Attila.
>
> On Jul 12, 2011, at 2:42 PM, Stephen McKamey wrote:
>
>
>
>
>
>
>
> > I'd like to plead to whomever has the authority to update the Maven
> > central with the release build of Rhino 1.7R3. This has been a
> > blocking issue for years for all Maven users needing 1.7R3
> > functionality and it would be great to have it resolved.
>
> > The full instructions are here:
Murer
Jul 19, 2011, 5:50:08 PM7/19/11
to mozilla-rhino
Thanks, Attila Szegedi.
Do it please (and fix group/artiacts too).
Tell me if I can help pl.
Murer.
On Jul 12, 7:16 pm, Attila Szegedi <szege...@gmail.com> wrote:
> Jeez… I'm looking at that and it's all wrong. groupId=rhino, artifactId=js, seriously? It should be groupId=org.mozilla and artifactId=rhino.
>
> Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
>
> Attila.
>
> On Jul 12, 2011, at 2:42 PM, Stephen McKamey wrote:
>
> > I'd like to plead to whomever has the authority to update the Maven
> > central with the release build of Rhino 1.7R3. This has been a
> > blocking issue for years for all Maven users needing 1.7R3
> > functionality and it would be great to have it resolved.
>
> > The full instructions are here:
> >https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repos...
Do it please (and fix group/artiacts too).
Tell me if I can help pl.
Murer.
On Jul 12, 7:16 pm, Attila Szegedi <szege...@gmail.com> wrote:
> Jeez… I'm looking at that and it's all wrong. groupId=rhino, artifactId=js, seriously? It should be groupId=org.mozilla and artifactId=rhino.
>
> Anyway, I submitted a JIRA ticket for proper org.mozilla/rhino repo to Sonatype and will act on it once it is approved: <https://issues.sonatype.org/browse/OSSRH-1941>
>
> Attila.
>
> On Jul 12, 2011, at 2:42 PM, Stephen McKamey wrote:
>
> > I'd like to plead to whomever has the authority to update the Maven
> > central with the release build of Rhino 1.7R3. This has been a
> > blocking issue for years for all Maven users needing 1.7R3
> > functionality and it would be great to have it resolved.
>
> > The full instructions are here:
Attila Szegedi
Jul 20, 2011, 2:05:10 AM7/20/11
to mozill...@googlegroups.com
I just promoted the release on oss.sonatype.org; should appear in central Maven repo in 2-10 hours. Search for groupId=org.mozilla artifactId=rhino.
Attila.
Stephen McKamey
Jul 20, 2011, 12:40:12 PM7/20/11
to mozilla-rhino
It's up in Maven Central now! I just confirmed by purging my local
repo and it correctly grabbed:
http://repo1.maven.org/maven2/org/mozilla/rhino/
Thanks Attila. This is a huge win for Maven users.
repo and it correctly grabbed:
http://repo1.maven.org/maven2/org/mozilla/rhino/
Thanks Attila. This is a huge win for Maven users.
Dominic Mitchell
Jul 21, 2011, 1:49:09 PM7/21/11
to mozill...@googlegroups.com
Thanks hugely!
-Dom
Reply all
Reply to author
Forward
0 new messages