On Wed, Jul 13, 2011 at 8:14 AM, wrote:
> Hm, no, the differing timestamps resulting from the two seperate uploads
> are a problem. A build that references this library in its dependencies
> fails -- the POM isn't found:
>
> [WARNING] The POM for ::jar: is
> missing, no dependency information ava
mvn deploy:deployFile -Dfile=... -DpomFile=... -Durl=... should deploy
both the jar and the pom. If it is not doing so can you raise a JIRA.
Note that you might have to force the version of the deploy plugin as
it could be an issue with an older version,
mvn org.apache.maven.plugins:maven-deploy-
> On 07/12/2011 04:02 AM, Wendy Smoak wrote:
>> On Mon, Jul 11, 2011 at 8:15 PM, Olaf Klischat
>> wrote:
>>> mvn deploy:deploy-file -Dfile=mylib.jar DpomFile=mypom.pom
>>> -DgeneratePom=false -Durl=
>>>
>>> , it apparently just uploads the jar under the name>> from
>>> mypom.pom>-.pom.
>>
>> You me
On 07/12/2011 04:02 AM, Wendy Smoak wrote:
On Mon, Jul 11, 2011 at 8:15 PM, Olaf Klischat wrote:
mvn deploy:deploy-file -Dfile=mylib.jar DpomFile=mypom.pom
-DgeneratePom=false -Durl=
, it apparently just uploads the jar under the name-.pom.
You mentioned a timestamp, so... you're deploying a
On Mon, Jul 11, 2011 at 8:15 PM, Olaf Klischat wrote:
> mvn deploy:deploy-file -Dfile=mylib.jar DpomFile=mypom.pom
> -DgeneratePom=false -Durl=
>
> , it apparently just uploads the jar under the name mypom.pom>-.pom.
You mentioned a timestamp, so... you're deploying a snapshot? And
even though
I have a jar file and an accompanying POM file that describes the jar
file's metadata (name etc.) and dependencies, but contains no
repo/deployment info. Can I upload both files to my (Sonatype Nexus or
local/filesystem) repo so that they end up as one project/artifact, just
as they would if I
