[jira] [Issue Comment Edited] (FELIX-3031) maven3 deployment fails where maven2 works

["Henrik Niehaus (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128268#comment-13128268 ] 

Henrik Niehaus edited comment on FELIX-3031 at 10/15/11 8:11 PM:
-----------------------------------------------------------------

I'm getting the same error message. The problem seems to be, that the deployed jar contains a timestamp for unique snapshots. The jar in the local repo is named <bundle>-<version>-SNAPSHOT.jar . The SNAPSHOT keyword is used instead of timestamp. That's why, the lookup in the local repo fails.

I have replaced the URIs in ObrDeploy, so that the build result is used instead of the file in the local repository. This solves the problem for me. PLease have a look at the patch in obr_deploy.diff.

Best regards
Henrik
                
      was (Author: hampelratte):
    I'm getting the same error message. The problem seems to be, that the deployed jar contains a timestamp for unique snapshots. The jar in the local repo is named <bundle>-<version>-SNAPSHOT.jar . The SNAPSHOT keyword is used instead of timestamp. That's why, the lookup in the local repo fails.

I have replaced the URIs in ObrDeploy, so that the build result is used instead of the file in the local repository. This solves the problem for me.
                  
> maven3 deployment fails where maven2 works
> ------------------------------------------
>
>                 Key: FELIX-3031
>                 URL: https://issues.apache.org/jira/browse/FELIX-3031
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>            Reporter: Markus Joschko
>         Attachments: mvn3bug.zip, obr_deploy.diff
>
>
> I want to deploy a bundle to a remote obr. I have configured the
> bundle-plugin to use the default repository (which is a
> filebased repository). Everything worked fine with maven 2. Now that I
> switched to maven 3 I get the following error:
> [INFO] --- maven-bundle-plugin:2.3.5:deploy (default-deploy) @ test ---
> [INFO] LOCK file:///var/www/repository/repository.xml
> [INFO] Downloading repository.xml
> [INFO] Computed bundle uri: http://localhost/repository/example/test/1.0-SNAPSHOT/test-1.0-20110711.152943-4.jar
> [ERROR] file doesn't exist: file:/home/markus/.m2/repository/example/test/1.0-SNAPSHOT/test-1.0-20110711.152943-4.jar
> [INFO] Writing OBR metadata
> [INFO] Uploading repository.xml
> [INFO] UNLOCK file:///var/www/repository/repository.xml
> The bundle plugin tries to retrieve the jar file from my local
> repository. However the maven deploy plugin has also picked up the
> remote repository and deployed the bundle in that repository
> and not in my local repository.
> That's different to maven2. When building with maven2 the bundle is
> deployed in my local and in my remote repository by the deploy
> plugin.
> No idea what has changed (maybe I miss some configuration here?), but
> for me it looks like the bundle plugin should pick up the bundle from
> the default deploy repository instead of the local repository?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira