404 when retrieving tar.bz2 assembly artifact deployed to Archiva

[James Baldassari]

Hi,

I have a project (packaging = pom) that builds a tar.bz2 assembly in its
package phase and deploys the assembly when the project is deployed.  If
I build/deploy the project and navigate to
http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:

myArtifactId-1.0-20090708.125341-38.pom
myArtifactId-1.0-20090708.125341-38.pom.md5
myArtifactId-1.0-20090708.125341-38.pom.sha1
myArtifactId-1.0-20090708.125341-38-release.tar.bz2
myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1

I can access all of the *.pom* files without any problem, but if I
attempt to download any of the *.tar.bz2* files Archiva returns a 404.
I have verified that the file does indeed exist in the Archiva
repository on the filesystem.  If I browse to my project in Archiva
(http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.

I've searched the issue tracker and mailing lists, but I haven't seen
any issues exactly like this.  This seems to be a similar problem:
http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
to proxying Maven 1 repositories.  If anyone has any ideas about how to
fix this I would really appreciate it.  If not I guess I'll create an
issue in JIRA.

Thanks,
James Baldassari

[James Baldassari]

I created an issue for this:

http://jira.codehaus.org/browse/MRM-1215

-James


On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:

> Hi,
>
> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
> package phase and deploys the assembly when the project is deployed.  If
> I build/deploy the project and navigate to
> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
>
> myArtifactId-1.0-20090708.125341-38.pom
> myArtifactId-1.0-20090708.125341-38.pom.md5
> myArtifactId-1.0-20090708.125341-38.pom.sha1
> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
>
> I can access all of the *.pom* files without any problem, but if I
> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
> I have verified that the file does indeed exist in the Archiva
> repository on the filesystem.  If I browse to my project in Archiva
> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
>
> I've searched the issue tracker and mailing lists, but I haven't seen
> any issues exactly like this.  This seems to be a similar problem:
> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
> to proxying Maven 1 repositories.  If anyone has any ideas about how to
> fix this I would really appreciate it.  If not I guess I'll create an
> issue in JIRA.
>
> Thanks,
> James Baldassari
>
>
>
>

[Dan Tran]

exact same issue is at http://jira.codehaus.org/browse/MRM-1144

On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:

> I created an issue for this:
>
> http://jira.codehaus.org/browse/MRM-1215
>
> -James
>
>
> On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
>> Hi,
>>
>> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
>> package phase and deploys the assembly when the project is deployed.  If
>> I build/deploy the project and navigate to
>> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
>>
>> myArtifactId-1.0-20090708.125341-38.pom
>> myArtifactId-1.0-20090708.125341-38.pom.md5
>> myArtifactId-1.0-20090708.125341-38.pom.sha1
>> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
>> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
>> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
>>
>> I can access all of the *.pom* files without any problem, but if I
>> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
>> I have verified that the file does indeed exist in the Archiva
>> repository on the filesystem.  If I browse to my project in Archiva
>> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
>>
>> I've searched the issue tracker and mailing lists, but I haven't seen
>> any issues exactly like this.  This seems to be a similar problem:
>> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
>> to proxying Maven 1 repositories.  If anyone has any ideas about how to
>> fix this I would really appreciate it.  If not I guess I'll create an
>> issue in JIRA.
>>
>> Thanks,
>> James Baldassari
>>
>>
>>
>>
>
>
>

[James Baldassari]

Thanks, Dan.  I didn't see that one.


On Fri, 2009-07-10 at 17:17 -0500, Dan Tran wrote:

> exact same issue is at http://jira.codehaus.org/browse/MRM-1144
>
> On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:
> > I created an issue for this:
> >
> > http://jira.codehaus.org/browse/MRM-1215
> >
> > -James
> >
> >
> > On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
> >> Hi,
> >>
> >> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
> >> package phase and deploys the assembly when the project is deployed.  If
> >> I build/deploy the project and navigate to
> >> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
> >>
> >> myArtifactId-1.0-20090708.125341-38.pom
> >> myArtifactId-1.0-20090708.125341-38.pom.md5
> >> myArtifactId-1.0-20090708.125341-38.pom.sha1
> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
> >>
> >> I can access all of the *.pom* files without any problem, but if I
> >> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
> >> I have verified that the file does indeed exist in the Archiva
> >> repository on the filesystem.  If I browse to my project in Archiva
> >> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
> >>
> >> I've searched the issue tracker and mailing lists, but I haven't seen
> >> any issues exactly like this.  This seems to be a similar problem:
> >> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
> >> to proxying Maven 1 repositories.  If anyone has any ideas about how to
> >> fix this I would really appreciate it.  If not I guess I'll create an
> >> issue in JIRA.
> >>
> >> Thanks,
> >> James Baldassari
> >>
> >>
> >>
> >>
> >
> >
> >
>

[James Baldassari]

Hi Dan,

Could you please elaborate on the workaround you describe in MRM-1144?
You said that using the packaging type "tbz2" worked.  Do you mean that
you specified "tbz2" as the packaging type in your project's POM, or are
you referring to something in an assembly descriptor?  I'm really hoping
to find a workaround for this problem until the bug is fixed.  BTW, I
marked my issue (MRM-1215) as a dup of yours and closed it.

Thanks,
James


On Fri, 2009-07-10 at 17:17 -0500, Dan Tran wrote:

> exact same issue is at http://jira.codehaus.org/browse/MRM-1144
>
> On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:
> > I created an issue for this:
> >
> > http://jira.codehaus.org/browse/MRM-1215
> >
> > -James
> >
> >
> > On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
> >> Hi,
> >>
> >> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
> >> package phase and deploys the assembly when the project is deployed.  If
> >> I build/deploy the project and navigate to
> >> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
> >>
> >> myArtifactId-1.0-20090708.125341-38.pom
> >> myArtifactId-1.0-20090708.125341-38.pom.md5
> >> myArtifactId-1.0-20090708.125341-38.pom.sha1
> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
> >>
> >> I can access all of the *.pom* files without any problem, but if I
> >> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
> >> I have verified that the file does indeed exist in the Archiva
> >> repository on the filesystem.  If I browse to my project in Archiva
> >> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
> >>
> >> I've searched the issue tracker and mailing lists, but I haven't seen
> >> any issues exactly like this.  This seems to be a similar problem:
> >> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
> >> to proxying Maven 1 repositories.  If anyone has any ideas about how to
> >> fix this I would really appreciate it.  If not I guess I'll create an
> >> issue in JIRA.
> >>
> >> Thanks,
> >> James Baldassari
> >>
> >>
> >>
> >>
> >
> >
> >
>

[Dan Tran]

I rename tar.bz2 to tbz2 during upload

-Dan


On Fri, Jul 10, 2009 at 5:08 PM, James Baldassari<james@...> wrote:

> Hi Dan,
>
> Could you please elaborate on the workaround you describe in MRM-1144?
> You said that using the packaging type "tbz2" worked.  Do you mean that
> you specified "tbz2" as the packaging type in your project's POM, or are
> you referring to something in an assembly descriptor?  I'm really hoping
> to find a workaround for this problem until the bug is fixed.  BTW, I
> marked my issue (MRM-1215) as a dup of yours and closed it.
>
> Thanks,
> James
>
>
> On Fri, 2009-07-10 at 17:17 -0500, Dan Tran wrote:
>> exact same issue is at http://jira.codehaus.org/browse/MRM-1144
>>
>> On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:
>> > I created an issue for this:
>> >
>> > http://jira.codehaus.org/browse/MRM-1215
>> >
>> > -James
>> >
>> >
>> > On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
>> >> Hi,
>> >>
>> >> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
>> >> package phase and deploys the assembly when the project is deployed.  If
>> >> I build/deploy the project and navigate to
>> >> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
>> >>
>> >> myArtifactId-1.0-20090708.125341-38.pom
>> >> myArtifactId-1.0-20090708.125341-38.pom.md5
>> >> myArtifactId-1.0-20090708.125341-38.pom.sha1
>> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
>> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
>> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
>> >>
>> >> I can access all of the *.pom* files without any problem, but if I
>> >> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
>> >> I have verified that the file does indeed exist in the Archiva
>> >> repository on the filesystem.  If I browse to my project in Archiva
>> >> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
>> >>
>> >> I've searched the issue tracker and mailing lists, but I haven't seen
>> >> any issues exactly like this.  This seems to be a similar problem:
>> >> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
>> >> to proxying Maven 1 repositories.  If anyone has any ideas about how to
>> >> fix this I would really appreciate it.  If not I guess I'll create an
>> >> issue in JIRA.
>> >>
>> >> Thanks,
>> >> James Baldassari
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>
>
>

[James Baldassari]

Thanks for the tip, Dan.  First I tried renaming the file during upload
using the Maven wagon plugin in the deploy phase, but I didn't know how
to insert the unique snapshot version into the destination file name.

Then I tried setting <attach>false</attach> in the assembly plugin
config, using the Ant plugin to rename all target/*.tar.bz2 to
target/*.tbz2 in the install phase, and then using the
deploy:deploy-file plugin/goal in the deploy phase to upload the
correctly named assembly to Archiva.  This seems to be working, and I'm
getting unique snapshot versions too.  Is this how you're doing the
renaming?  Is there a simpler way?

Thanks,
James


On Fri, 2009-07-10 at 21:02 -0500, Dan Tran wrote:

> I rename tar.bz2 to tbz2 during upload
>
> -Dan
>
>
> On Fri, Jul 10, 2009 at 5:08 PM, James Baldassari<james@...> wrote:
> > Hi Dan,
> >
> > Could you please elaborate on the workaround you describe in MRM-1144?
> > You said that using the packaging type "tbz2" worked.  Do you mean that
> > you specified "tbz2" as the packaging type in your project's POM, or are
> > you referring to something in an assembly descriptor?  I'm really hoping
> > to find a workaround for this problem until the bug is fixed.  BTW, I
> > marked my issue (MRM-1215) as a dup of yours and closed it.
> >
> > Thanks,
> > James
> >
> >
> > On Fri, 2009-07-10 at 17:17 -0500, Dan Tran wrote:
> >> exact same issue is at http://jira.codehaus.org/browse/MRM-1144
> >>
> >> On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:
> >> > I created an issue for this:
> >> >
> >> > http://jira.codehaus.org/browse/MRM-1215
> >> >
> >> > -James
> >> >
> >> >
> >> > On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
> >> >> Hi,
> >> >>
> >> >> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
> >> >> package phase and deploys the assembly when the project is deployed.  If
> >> >> I build/deploy the project and navigate to
> >> >> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
> >> >>
> >> >> myArtifactId-1.0-20090708.125341-38.pom
> >> >> myArtifactId-1.0-20090708.125341-38.pom.md5
> >> >> myArtifactId-1.0-20090708.125341-38.pom.sha1
> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
> >> >>
> >> >> I can access all of the *.pom* files without any problem, but if I
> >> >> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
> >> >> I have verified that the file does indeed exist in the Archiva
> >> >> repository on the filesystem.  If I browse to my project in Archiva
> >> >> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
> >> >>
> >> >> I've searched the issue tracker and mailing lists, but I haven't seen
> >> >> any issues exactly like this.  This seems to be a similar problem:
> >> >> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
> >> >> to proxying Maven 1 repositories.  If anyone has any ideas about how to
> >> >> fix this I would really appreciate it.  If not I guess I'll create an
> >> >> issue in JIRA.
> >> >>
> >> >> Thanks,
> >> >> James Baldassari
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>

[Dan Tran]

did you try deploy:deploy-file?

-Dan

On Sat, Jul 11, 2009 at 1:07 PM, James Baldassari<james@...> wrote:

> Thanks for the tip, Dan.  First I tried renaming the file during upload
> using the Maven wagon plugin in the deploy phase, but I didn't know how
> to insert the unique snapshot version into the destination file name.
>
> Then I tried setting <attach>false</attach> in the assembly plugin
> config, using the Ant plugin to rename all target/*.tar.bz2 to
> target/*.tbz2 in the install phase, and then using the
> deploy:deploy-file plugin/goal in the deploy phase to upload the
> correctly named assembly to Archiva.  This seems to be working, and I'm
> getting unique snapshot versions too.  Is this how you're doing the
> renaming?  Is there a simpler way?
>
> Thanks,
> James
>
>
> On Fri, 2009-07-10 at 21:02 -0500, Dan Tran wrote:
>> I rename tar.bz2 to tbz2 during upload
>>
>> -Dan
>>
>>
>> On Fri, Jul 10, 2009 at 5:08 PM, James Baldassari<james@...> wrote:
>> > Hi Dan,
>> >
>> > Could you please elaborate on the workaround you describe in MRM-1144?
>> > You said that using the packaging type "tbz2" worked.  Do you mean that
>> > you specified "tbz2" as the packaging type in your project's POM, or are
>> > you referring to something in an assembly descriptor?  I'm really hoping
>> > to find a workaround for this problem until the bug is fixed.  BTW, I
>> > marked my issue (MRM-1215) as a dup of yours and closed it.
>> >
>> > Thanks,
>> > James
>> >
>> >
>> > On Fri, 2009-07-10 at 17:17 -0500, Dan Tran wrote:
>> >> exact same issue is at http://jira.codehaus.org/browse/MRM-1144
>> >>
>> >> On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:
>> >> > I created an issue for this:
>> >> >
>> >> > http://jira.codehaus.org/browse/MRM-1215
>> >> >
>> >> > -James
>> >> >
>> >> >
>> >> > On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
>> >> >> Hi,
>> >> >>
>> >> >> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
>> >> >> package phase and deploys the assembly when the project is deployed.  If
>> >> >> I build/deploy the project and navigate to
>> >> >> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
>> >> >>
>> >> >> myArtifactId-1.0-20090708.125341-38.pom
>> >> >> myArtifactId-1.0-20090708.125341-38.pom.md5
>> >> >> myArtifactId-1.0-20090708.125341-38.pom.sha1
>> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
>> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
>> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
>> >> >>
>> >> >> I can access all of the *.pom* files without any problem, but if I
>> >> >> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
>> >> >> I have verified that the file does indeed exist in the Archiva
>> >> >> repository on the filesystem.  If I browse to my project in Archiva
>> >> >> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
>> >> >>
>> >> >> I've searched the issue tracker and mailing lists, but I haven't seen
>> >> >> any issues exactly like this.  This seems to be a similar problem:
>> >> >> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
>> >> >> to proxying Maven 1 repositories.  If anyone has any ideas about how to
>> >> >> fix this I would really appreciate it.  If not I guess I'll create an
>> >> >> issue in JIRA.
>> >> >>
>> >> >> Thanks,
>> >> >> James Baldassari
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>>
>
>
>

[James Baldassari]

Yes, I was able to get it working with deploy:deploy-file.  Thanks for
all your help, Dan.

-James


On Sat, 2009-07-11 at 17:51 -0500, Dan Tran wrote:

> did you try deploy:deploy-file?
>
> -Dan
>
> On Sat, Jul 11, 2009 at 1:07 PM, James Baldassari<james@...> wrote:
> > Thanks for the tip, Dan.  First I tried renaming the file during upload
> > using the Maven wagon plugin in the deploy phase, but I didn't know how
> > to insert the unique snapshot version into the destination file name.
> >
> > Then I tried setting <attach>false</attach> in the assembly plugin
> > config, using the Ant plugin to rename all target/*.tar.bz2 to
> > target/*.tbz2 in the install phase, and then using the
> > deploy:deploy-file plugin/goal in the deploy phase to upload the
> > correctly named assembly to Archiva.  This seems to be working, and I'm
> > getting unique snapshot versions too.  Is this how you're doing the
> > renaming?  Is there a simpler way?
> >
> > Thanks,
> > James
> >
> >
> > On Fri, 2009-07-10 at 21:02 -0500, Dan Tran wrote:
> >> I rename tar.bz2 to tbz2 during upload
> >>
> >> -Dan
> >>
> >>
> >> On Fri, Jul 10, 2009 at 5:08 PM, James Baldassari<james@...> wrote:
> >> > Hi Dan,
> >> >
> >> > Could you please elaborate on the workaround you describe in MRM-1144?
> >> > You said that using the packaging type "tbz2" worked.  Do you mean that
> >> > you specified "tbz2" as the packaging type in your project's POM, or are
> >> > you referring to something in an assembly descriptor?  I'm really hoping
> >> > to find a workaround for this problem until the bug is fixed.  BTW, I
> >> > marked my issue (MRM-1215) as a dup of yours and closed it.
> >> >
> >> > Thanks,
> >> > James
> >> >
> >> >
> >> > On Fri, 2009-07-10 at 17:17 -0500, Dan Tran wrote:
> >> >> exact same issue is at http://jira.codehaus.org/browse/MRM-1144
> >> >>
> >> >> On Fri, Jul 10, 2009 at 11:47 AM, James Baldassari<james@...> wrote:
> >> >> > I created an issue for this:
> >> >> >
> >> >> > http://jira.codehaus.org/browse/MRM-1215
> >> >> >
> >> >> > -James
> >> >> >
> >> >> >
> >> >> > On Wed, 2009-07-08 at 09:52 -0500, James Baldassari wrote:
> >> >> >> Hi,
> >> >> >>
> >> >> >> I have a project (packaging = pom) that builds a tar.bz2 assembly in its
> >> >> >> package phase and deploys the assembly when the project is deployed.  If
> >> >> >> I build/deploy the project and navigate to
> >> >> >> http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/ I see:
> >> >> >>
> >> >> >> myArtifactId-1.0-20090708.125341-38.pom
> >> >> >> myArtifactId-1.0-20090708.125341-38.pom.md5
> >> >> >> myArtifactId-1.0-20090708.125341-38.pom.sha1
> >> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2
> >> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.md5
> >> >> >> myArtifactId-1.0-20090708.125341-38-release.tar.bz2.sha1
> >> >> >>
> >> >> >> I can access all of the *.pom* files without any problem, but if I
> >> >> >> attempt to download any of the *.tar.bz2* files Archiva returns a 404.
> >> >> >> I have verified that the file does indeed exist in the Archiva
> >> >> >> repository on the filesystem.  If I browse to my project in Archiva
> >> >> >> (http://myarchivaserver/archiva/browse/myGroupId/myArtifactId/1.0-SNAPSHOT), I see a link called "Distribution-bzip" in the Downloads section in the  upper right.  This links to http://myarchivaserver/archiva/repository/internal/myGroupId/myArtifactId/1.0-SNAPSHOT/myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, which does not exist.  However, if I manually rename myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip in the Archiva repository (and similarly rename the checksum files), I can download the tar.bz2 file, and the project that depends on it can also access it.  So it seems like Archiva is translating requests for myArtifactId-1.0-20090708.125341-38-release.tar.bz2 to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip, but when the archive is deployed to Archiva it isn't renamed to myArtifactId-1.0-20090708.125341-38-release.distribution-bzip.
> >> >> >>
> >> >> >> I've searched the issue tracker and mailing lists, but I haven't seen
> >> >> >> any issues exactly like this.  This seems to be a similar problem:
> >> >> >> http://jira.codehaus.org/browse/MRM-1200 but it looks like it's related
> >> >> >> to proxying Maven 1 repositories.  If anyone has any ideas about how to
> >> >> >> fix this I would really appreciate it.  If not I guess I'll create an
> >> >> >> issue in JIRA.
> >> >> >>
> >> >> >> Thanks,
> >> >> >> James Baldassari
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>

[Dan Tran]

btw, you can use the upload feature from archiva as well. I dont use
deploy:deploy-file any more

-D