Also I just tried the same thing but leaving "Also deploy jar's internal
POM/Generate Default POM" unchecked and had the same error. So you can
discount that option as being the problematic one ;)
On 24 September 2012 14:47, Mark Baker <[email protected]> wrote:
> Hi,
>
> It is v2.6.2 of Artifactory.
>
> The easiest way to demonstrate is to pick any .zip file and go to the
> Deploy page in the web UI webapp/deployartifact.html
>
> e.g. my-test-artifact.zip with a few jpeg images/html files.
> Fill in sensible default values for this:
> GroupId = my.test.group
> ArtifactId = my-test-artifact
> Version = 1.0-SNAPSHOT
> Type = zip
>
> Leaving "deploy as Maven Artifact" and "Also deploy jar's internal
> POM/Generate Default POM" both checked, click Deploy Artifact.
>
> We then get an error and this in the artifactory.log (below) Note that if
> you change the Type to 'foo' there is no error and the file is deployed
> successfully.
> [snip]
>
--
View this message in context:
http://forums.jfrog.org/storing-artefacts-that-are-actually-zip-files-tp7578260p7578263.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
