org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 has declared org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent

[Anders Hammar]

Hi,

In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 uses org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty sure that you'd agree that having a released artifact depend on a snapshot is bad, right? The problem I'm having (and a few of my developers have been fighting) is that it makes Nexus plugin development a pain. When declaring Forge a remote repo, we've declared it as only a release repo.

Could this be fixed? If you don't want to update the pom of org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please release a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct pom? And yes, you also need to release org.codehaus.swizzle:swizzle-parent.

/Anders

[Anders Hammar]

It's even more complicated, I've noticed. Even if Forge is declared as both release AND snapshot repo it doesn't work. I had to add Codehaus's Snapshot repo as well.

/Anders

On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:

Hi,

In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 uses org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty sure that you'd agree that having a released artifact depend on a snapshot is bad, right? The problem I'm having (and a few of my developers have been fighting) is that it makes Nexus plugin development a pain. When declaring Forge a remote repo, we've declared it as only a release repo.

Could this be fixed? If you don't want to update the pom of org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please release a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct pom? And yes, you also need to release org.codehaus.swizzle:swizzle-parent.

/Anders

[Brian Demers-2]

Anders, thanks for catching that, we can clean that up, someone must of released this manually I assume.

https://issues.sonatype.org/browse/NEXUS-3120

On Dec 17, 2009, at 7:48 AM, Anders Hammar wrote:

It's even more complicated, I've noticed. Even if Forge is declared as both release AND snapshot repo it doesn't work. I had to add Codehaus's Snapshot repo as well.

/Anders

On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:

Hi,

In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 uses org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty sure that you'd agree that having a released artifact depend on a snapshot is bad, right? The problem I'm having (and a few of my developers have been fighting) is that it makes Nexus plugin development a pain. When declaring Forge a remote repo, we've declared it as only a release repo.

Could this be fixed? If you don't want to update the pom of org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please release a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct pom? And yes, you also need to release org.codehaus.swizzle:swizzle-parent.

/Anders

[Brian Fox]

Is Nexus using that version of the jar? The release plugin should have
blocked everything because of that.

On Thu, Dec 17, 2009 at 9:26 AM, Brian Demers <[hidden email]> wrote:

> Anders, thanks for catching that, we can clean that up, someone must of
> released this manually I assume.
> https://issues.sonatype.org/browse/NEXUS-3120
> On Dec 17, 2009, at 7:48 AM, Anders Hammar wrote:
>
> It's even more complicated, I've noticed. Even if Forge is declared as both
> release AND snapshot repo it doesn't work. I had to add Codehaus's Snapshot
> repo as well.
>
> /Anders
>
> On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:
>>
>> Hi,
>>
>> In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 uses
>> org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty sure
>> that you'd agree that having a released artifact depend on a snapshot is
>> bad, right? The problem I'm having (and a few of my developers have been
>> fighting) is that it makes Nexus plugin development a pain. When declaring
>> Forge a remote repo, we've declared it as only a release repo.
>>
>> Could this be fixed? If you don't want to update the pom of
>> org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please release
>> a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct pom? And
>> yes, you also need to release org.codehaus.swizzle:swizzle-parent.
>>
>> /Anders
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Damian Bradicich]

We have resolved the issue on nexus trunk, plexus-swizzle (which nexus depends on) now has dependency on

 

g: org.codehaus.swizzle

a: swizzle-jira

v: 1.3.3-SONATYPE-221  (where 221 is the svn rev of the build)

 

which itself, now has proper parent

 

g: org.codehaus.swizzle

a: swizzle-parent

v: 1-SONATYPE-221

 

Both of these artifacts are in r.s.o. and should be accessible by the Forge group you had been using

 

Let me know if you have problems

 

Thanks

 

Damian

On Thu, Dec 17, 2009 at 9:38 AM, Brian Fox <[hidden email]> wrote:

Is Nexus using that version of the jar? The release plugin should have
blocked everything because of that.

On Thu, Dec 17, 2009 at 9:26 AM, Brian Demers <[hidden email]> wrote:
> Anders, thanks for catching that, we can clean that up, someone must of
> released this manually I assume.
> https://issues.sonatype.org/browse/NEXUS-3120
> On Dec 17, 2009, at 7:48 AM, Anders Hammar wrote:
>
> It's even more complicated, I've noticed. Even if Forge is declared as both
> release AND snapshot repo it doesn't work. I had to add Codehaus's Snapshot
> repo as well.
>
> /Anders
>
> On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:
>>
>> Hi,
>>
>> In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 uses
>> org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty sure
>> that you'd agree that having a released artifact depend on a snapshot is
>> bad, right? The problem I'm having (and a few of my developers have been
>> fighting) is that it makes Nexus plugin development a pain. When declaring
>> Forge a remote repo, we've declared it as only a release repo.
>>
>> Could this be fixed? If you don't want to update the pom of
>> org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please release
>> a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct pom? And
>> yes, you also need to release org.codehaus.swizzle:swizzle-parent.
>>
>> /Anders
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Anders Hammar]

Yes, swizzle-jira-1.3.3-sonatype-2.jar is included in Nexus 1.4.0 and 1.4.1.
Our plugin does not have a direct dependency to this artifact. It is a transitive dependency from either nexus-plugin-api or nexus-rest-api (v1.4.0/1.4.1). I don't have a dev environment at my access right now so I can't tell which one.

Something is fishy, isn't it?

/Anders

On Thu, Dec 17, 2009 at 15:38, Brian Fox <[hidden email]> wrote:

Is Nexus using that version of the jar? The release plugin should have
blocked everything because of that.

On Thu, Dec 17, 2009 at 9:26 AM, Brian Demers <[hidden email]> wrote:
> Anders, thanks for catching that, we can clean that up, someone must of
> released this manually I assume.
> https://issues.sonatype.org/browse/NEXUS-3120
> On Dec 17, 2009, at 7:48 AM, Anders Hammar wrote:
>
> It's even more complicated, I've noticed. Even if Forge is declared as both
> release AND snapshot repo it doesn't work. I had to add Codehaus's Snapshot
> repo as well.
>
> /Anders
>
> On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:
>>
>> Hi,
>>
>> In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2 uses
>> org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty sure
>> that you'd agree that having a released artifact depend on a snapshot is
>> bad, right? The problem I'm having (and a few of my developers have been
>> fighting) is that it makes Nexus plugin development a pain. When declaring
>> Forge a remote repo, we've declared it as only a release repo.
>>
>> Could this be fixed? If you don't want to update the pom of
>> org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please release
>> a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct pom? And
>> yes, you also need to release org.codehaus.swizzle:swizzle-parent.
>>
>> /Anders
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Brian Fox]

The new one is released, so in your project just include a depMgt
entry on the corrected version and you should be ok.

On Thu, Dec 17, 2009 at 3:06 PM, Anders Hammar <[hidden email]> wrote:

> Yes, swizzle-jira-1.3.3-sonatype-2.jar is included in Nexus 1.4.0 and 1.4.1.
> Our plugin does not have a direct dependency to this artifact. It is a
> transitive dependency from either nexus-plugin-api or nexus-rest-api
> (v1.4.0/1.4.1). I don't have a dev environment at my access right now so I
> can't tell which one.
>
> Something is fishy, isn't it?
>
> /Anders
>
>
> On Thu, Dec 17, 2009 at 15:38, Brian Fox <[hidden email]> wrote:
>>
>> Is Nexus using that version of the jar? The release plugin should have
>> blocked everything because of that.
>>
>> On Thu, Dec 17, 2009 at 9:26 AM, Brian Demers <[hidden email]>
>> wrote:
>> > Anders, thanks for catching that, we can clean that up, someone must of
>> > released this manually I assume.
>> > https://issues.sonatype.org/browse/NEXUS-3120
>> > On Dec 17, 2009, at 7:48 AM, Anders Hammar wrote:
>> >
>> > It's even more complicated, I've noticed. Even if Forge is declared as
>> > both
>> > release AND snapshot repo it doesn't work. I had to add Codehaus's
>> > Snapshot
>> > repo as well.
>> >
>> > /Anders
>> >
>> > On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:
>> >>
>> >> Hi,
>> >>
>> >> In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2
>> >> uses
>> >> org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty
>> >> sure
>> >> that you'd agree that having a released artifact depend on a snapshot
>> >> is
>> >> bad, right? The problem I'm having (and a few of my developers have
>> >> been
>> >> fighting) is that it makes Nexus plugin development a pain. When
>> >> declaring
>> >> Forge a remote repo, we've declared it as only a release repo.
>> >>
>> >> Could this be fixed? If you don't want to update the pom of
>> >> org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please
>> >> release
>> >> a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct
>> >> pom? And
>> >> yes, you also need to release org.codehaus.swizzle:swizzle-parent.
>> >>
>> >> /Anders
>> >>
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Anders Hammar]

Yep, works ok.

Thanx,
/A

On Thu, Dec 17, 2009 at 22:12, Brian Fox <[hidden email]> wrote:

The new one is released, so in your project just include a depMgt
entry on the corrected version and you should be ok.

On Thu, Dec 17, 2009 at 3:06 PM, Anders Hammar <[hidden email]> wrote:
> Yes, swizzle-jira-1.3.3-sonatype-2.jar is included in Nexus 1.4.0 and 1.4.1.
> Our plugin does not have a direct dependency to this artifact. It is a
> transitive dependency from either nexus-plugin-api or nexus-rest-api
> (v1.4.0/1.4.1). I don't have a dev environment at my access right now so I
> can't tell which one.
>
> Something is fishy, isn't it?
>
> /Anders
>
>
> On Thu, Dec 17, 2009 at 15:38, Brian Fox <[hidden email]> wrote:
>>
>> Is Nexus using that version of the jar? The release plugin should have
>> blocked everything because of that.
>>
>> On Thu, Dec 17, 2009 at 9:26 AM, Brian Demers <[hidden email]>
>> wrote:
>> > Anders, thanks for catching that, we can clean that up, someone must of
>> > released this manually I assume.
>> > https://issues.sonatype.org/browse/NEXUS-3120
>> > On Dec 17, 2009, at 7:48 AM, Anders Hammar wrote:
>> >
>> > It's even more complicated, I've noticed. Even if Forge is declared as
>> > both
>> > release AND snapshot repo it doesn't work. I had to add Codehaus's
>> > Snapshot
>> > repo as well.
>> >
>> > /Anders
>> >
>> > On Thu, Dec 17, 2009 at 13:42, Anders Hammar <[hidden email]> wrote:
>> >>
>> >> Hi,
>> >>
>> >> In the Forge repo, org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2
>> >> uses
>> >> org.codehaus.swizzle:swizzle-parent:1-SNAPSHOT as parent. I'm pretty
>> >> sure
>> >> that you'd agree that having a released artifact depend on a snapshot
>> >> is
>> >> bad, right? The problem I'm having (and a few of my developers have
>> >> been
>> >> fighting) is that it makes Nexus plugin development a pain. When
>> >> declaring
>> >> Forge a remote repo, we've declared it as only a release repo.
>> >>
>> >> Could this be fixed? If you don't want to update the pom of
>> >> org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-2, could you please
>> >> release
>> >> a org.codehaus.swizzle:swizzle-jira:1.3.3-sonatype-3 with a correct
>> >> pom? And
>> >> yes, you also need to release org.codehaus.swizzle:swizzle-parent.
>> >>
>> >> /Anders
>> >>
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]