A nice fonctionnality of Archiva but not is Nexus

[fabrice.mercier1]

Hi

I used Archiva, I migrated my company on Nexus recently, perfect choice!
However I noticed a fonctionnality lack, Nexus does not provide a way to know upstream and downstream dependencies for a specific artifact.
Users want to know that and today I can not give information.

Do you want I create a new JIRA entry ?

Fabrice

[mihobson]

2009/9/21 fabrice.mercier1 <beufmerc@...>:
>
> Hi
>
> I used Archiva, I migrated my company on Nexus recently, perfect choice!
> However I noticed a fonctionnality lack, Nexus does not provide a way to
> know upstream and downstream dependencies for a specific artifact.
> Users want to know that and today I can not give information.
>
> Do you want I create a new JIRA entry ?

See https://issues.sonatype.org/browse/NEXUS-909

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[justinedelson]

This was one of the use cases I had in mind with https://issues.sonatype.org/browse/NEXUS-221. It looks like there are a few more of this type of issue created. Can't speak for Sonatype folks, but it seems like we'd be better of creating a single User Story that encompasses all of the requirements for this "information" functionality.

---

From: Mark Hobson [mailto:markhobson@...]
Sent: Mon 9/21/2009 5:17 AM
To: nexus-user@...
Subject: Re: [nexus-user] A nice fonctionnality of Archiva but not is Nexus

2009/9/21 fabrice.mercier1 <beufmerc@...>:
>
> Hi
>
> I used Archiva, I migrated my company on Nexus recently, perfect choice!
> However I noticed a fonctionnality lack, Nexus does not provide a way to
> know upstream and downstream dependencies for a specific artifact.
> Users want to know that and today I can not give information.
>
> Do you want I create a new JIRA entry ?

See https://issues.sonatype.org/browse/NEXUS-909

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[mihobson]

2009/9/22 Edelson, Justin <Justin.Edelson@...>:
> This was one of the use cases I had in mind with
> https://issues.sonatype.org/browse/NEXUS-221. It looks like there are a few
> more of this type of issue created. Can't speak for Sonatype folks, but it
> seems like we'd be better of creating a single User Story that encompasses
> all of the requirements for this "information" functionality.

Worth linking the issues at the very least, I haven't got the
necessary permissions.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Juven Xu]

Linked, thank you.

On Tue, Sep 22, 2009 at 5:41 PM, Mark Hobson <markhobson@...> wrote:

2009/9/22 Edelson, Justin <Justin.Edelson@...>:

> This was one of the use cases I had in mind with
> https://issues.sonatype.org/browse/NEXUS-221. It looks like there are a few
> more of this type of issue created. Can't speak for Sonatype folks, but it
> seems like we'd be better of creating a single User Story that encompasses
> all of the requirements for this "information" functionality.

Worth linking the issues at the very least, I haven't got the
necessary permissions.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

--
- juven