Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Sun, 19 Mar 2017 19:37:41 +0000 (UTC)
From: "Karl Heinz Marbaise (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12801168.1304661726000.60819.1489952261637@Atlassian.JIRA>
In-Reply-To: <JIRA.12801168.1304661726000@Atlassian.JIRA>
References: <JIRA.12801168.1304661726000@Atlassian.JIRA> <JIRA.12801168.1304661726525@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (MDEPLOY-131) use default repository when
 no url specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 19 Mar 2017 19:37:49 -0000


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

Karl Heinz Marbaise edited comment on MDEPLOY-131 at 3/19/17 7:37 PM:
----------------------------------------------------------------------

It was just an example having different artifacts attached to the same build without deploy-file...If you really need having shaded using different dependencies  you need simply make different modules of them. 
Apart from that using [slf4j means|https://www.slf4j.org/images/concrete-bindings.png] you only define a dependency to slf4j-api  and the user of that lib/jar decides what is really being used in the end. So maybe I misunderstand a thing but it sounds like the other created jars could be omitted and are not really needed...


was (Author: khmarbaise):
It was just an example having different artifacts attached to the same build without deploy-file...If you really need having shaded using different dependencies  you need simply make different modules of them. 
Apart from that using slf4j means you only define a dependency to slf4j-api  and the user of that lib/jar decides what is really being used in the end. So maybe I misunderstand a thing but it sounds like the other created jars could be omitted and are not really needed...

> use default repository when no url specified
> --------------------------------------------
>
>                 Key: MDEPLOY-131
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-131
>             Project: Maven Deploy Plugin
>          Issue Type: Improvement
>          Components: deploy:deploy-file
>            Reporter: raymond domingo
>              Labels: contributers-welcome
>         Attachments: DeployFileMojo.java, maven-deploy-useProjectRepo-20170319.patch, patch_deploy_file_mojo.diff
>
>
> When using the deploy goal there is no need to specify the url of the repository.
> When using deploy-file you DO need to specify the url. This is a problem, because during development I like to deploy to snapshot repository and when releasing i deploy to release repository and I can't add this logic to the pom.
> Thas is why I like the url paramter to become optional (backwards compatible) and add default behaviour when it is null. It should just like the deploy plugin use the default repository. Snapshot for snapshots and release for none snapshot versions.
> I added a patch file fixing this.
> I also added complete source of patched Mojo


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)