You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Shane Isbell (JIRA)" <ji...@codehaus.org> on 2007/05/03 19:42:26 UTC

[jira] Created: (NMAVEN-43) Deploy project artifacts

Deploy project artifacts 
-------------------------

                 Key: NMAVEN-43
                 URL: http://jira.codehaus.org/browse/NMAVEN-43
             Project: NMaven
          Issue Type: New Feature
            Reporter: Shane Isbell


The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (NMAVEN-43) Deploy project artifacts

Posted by "Evan Worley (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95770 ] 

Evan Worley commented on NMAVEN-43:
-----------------------------------

Shane,

I haven't seen corruption but I am curious as to what could be going on.  The only thing we changed in the assembly itself is the encoding of the VERSION-SNAPSHOT in the "informationalVersion" attribute of the AssemblyInfo.

Let me know if there is anything we can do to help the investigation.

-Evan

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (NMAVEN-43) Deploy project artifacts

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95709 ] 

Shane Isbell commented on NMAVEN-43:
------------------------------------

Applied patch to the SI_XPT branch. It works perfectly. Thanks. 

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Issue Comment Edited: (NMAVEN-43) Deploy project artifacts

Posted by "Evan Worley (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95698 ] 

Evan Worley edited comment on NMAVEN-43 at 5/11/07 6:28 PM:
------------------------------------------------------------

NMaven can now deploy dotnet libraries, and you can also deploy and resolve snapshot libraries from both remote and local repositories.

Uses AsssemblyInformationalVersion to encode the snapshot  version in AssemblyInfo

Adding maven-deploy-plugin to deploy dotnet libraries, using standard maven (java) repo layout
Adding integration tests for above


 was:
Adds snapshot/non-snapshot deploy functionality

Uses AsssemblyInformationalVersion to encode the snapshot  version in AssemblyInfo

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (NMAVEN-43) Deploy project artifacts

Posted by "Evan Worley (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evan Worley updated NMAVEN-43:
------------------------------

    Attachment: deploy-patch.txt

Adds snapshot/non-snapshot deploy functionality

Uses AsssemblyInformationalVersion to encode the snapshot  version in AssemblyInfo

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (NMAVEN-43) Deploy project artifacts

Posted by "Evan Worley (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evan Worley updated NMAVEN-43:
------------------------------

    Attachment: deploy-patch-with-license.txt

Original patch with ASF 2.0 license added

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch-with-license.txt, deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (NMAVEN-43) Deploy project artifacts

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Isbell closed NMAVEN-43.
------------------------------

    Resolution: Fixed

Feature merged into trunk.

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (NMAVEN-43) Deploy project artifacts

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95780 ] 

Shane Isbell commented on NMAVEN-43:
------------------------------------

Okay, I found the problem.  During a deploy the assembly, say NMaven.Logging-0.14-20070513.170342-4.dll,  contained the pom.xml file, not the .NET assembly. The DeployMojo is using mavenProject.getFile()  (the returned value is the pom file) as the artifact to deploy, instead of mavenProject.getArtifact().getFile() .

I will check in the change and then we should be good to go.

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (NMAVEN-43) Deploy project artifacts

Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95764 ] 

Shane Isbell commented on NMAVEN-43:
------------------------------------

I did notice a weird thing with the patch. It handles snapshots correctly and it handles deployment correctly. But when I try to deploy snapshots, the assemblies become corrupted. I am still investigating this. Anyone else seeing the same thing?

> Deploy project artifacts 
> -------------------------
>
>                 Key: NMAVEN-43
>                 URL: http://jira.codehaus.org/browse/NMAVEN-43
>             Project: NMaven
>          Issue Type: New Feature
>            Reporter: Shane Isbell
>         Attachments: deploy-patch.txt
>
>
> The user can sync their built artifacts to a Maven repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira