[jira] [Commented] (MDEPLOY-252) Deploy current archive without creating new archive (jar, war, ear)
[ https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803353#comment-16803353 ] Ivica Mikic commented on MDEPLOY-252: - I also tried i.e. to skip default-jar goal when running "mvn install" or "mvn deploy" with the profile using "none" for it, but got the error "No primary artifact to install, installing attached artifacts instead.", in which case my jar hasn't been installed/deployed to the Maven repository at all. > Deploy current archive without creating new archive (jar, war, ear) > --- > > Key: MDEPLOY-252 > URL: https://issues.apache.org/jira/browse/MDEPLOY-252 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy >Affects Versions: 2.8.2 >Reporter: Ivica Mikic >Priority: Major > Labels: features, maven > Fix For: waiting-for-feedback > > > It would be great to be able to deploy current archive file (jar, war, ear) > without creating a new one, to preserve timestamp from previous package or > install run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEPLOY-252) Deploy current archive without creating new archive (jar, war, ear)
[ https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803264#comment-16803264 ] Ivica Mikic commented on MDEPLOY-252: - >From the Maven perspective, we normally build our Java code first with "mvn >clean package" many times during the active code change/development. This is >done either manually on the command line or within the IDE. But once testing >has passed and the code is considered reasonably stable, we want to proceed >with the "mvn install", then "mvn deploy", but keep the original archive files >in sync since there are no code changes. Isn't that reasonable? What would be >the alternative? I would still like to accomplish this somehow within the Maven life cycle, if possible. > Deploy current archive without creating new archive (jar, war, ear) > --- > > Key: MDEPLOY-252 > URL: https://issues.apache.org/jira/browse/MDEPLOY-252 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy >Affects Versions: 2.8.2 >Reporter: Ivica Mikic >Priority: Major > Labels: features, maven > Fix For: waiting-for-feedback > > > It would be great to be able to deploy current archive file (jar, war, ear) > without creating a new one, to preserve timestamp from previous package or > install run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEPLOY-252) Deploy current archive without creating new archive (jar, war, ear)
[ https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803113#comment-16803113 ] Ivica Mikic commented on MDEPLOY-252: - That's exactly what I had in mind: incremental build as part of the Maven life cycle. However, if that does not work by default, is there any other way to make it work (by using some argument values, different plugins, etc)? Would it make sense to write a new plugin to accomplish this? > Deploy current archive without creating new archive (jar, war, ear) > --- > > Key: MDEPLOY-252 > URL: https://issues.apache.org/jira/browse/MDEPLOY-252 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy >Affects Versions: 2.8.2 >Reporter: Ivica Mikic >Priority: Major > Labels: features, maven > Fix For: waiting-for-feedback > > > It would be great to be able to deploy current archive file (jar, war, ear) > without creating a new one, to preserve timestamp from previous package or > install run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEPLOY-252) Deploy current archive without creating new archive (jar, war, ear)
[ https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800642#comment-16800642 ] Ivica Mikic commented on MDEPLOY-252: - When I run "mvn clean package", new JAR or WAR or EAR is created. Assume I don't have any changes in my files, so I run "mvn install" and then "mvn deploy". At that point I don't want these files to be recreated with new timestamps, since there are no changes in the files. > Deploy current archive without creating new archive (jar, war, ear) > --- > > Key: MDEPLOY-252 > URL: https://issues.apache.org/jira/browse/MDEPLOY-252 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy >Affects Versions: 2.8.2 >Reporter: Ivica Mikic >Priority: Major > Labels: features, maven > Fix For: waiting-for-feedback > > > It would be great to be able to deploy current archive file (jar, war, ear) > without creating a new one, to preserve timestamp from previous package or > install run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEPLOY-252) Deploy current archive without creating new archive (jar, war, ear)
[ https://issues.apache.org/jira/browse/MDEPLOY-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795185#comment-16795185 ] Ivica Mikic commented on MDEPLOY-252: - Here is my usual sequence of Maven build commands. First I run "mvn clean package" many times as I work on my code. Once my code is complete, I run "mvn install" then "mvn deploy", however, I noticed that Maven creates a new JAR, WAR or EAR files even though I don't have code changes and I don't specify "clean". I expect that Maven would just use previously created archived files (JAR, WAR, EAR) and "install" them to our local repository or "deploy" them to our global repository. In a nutshell, I don't want to have different timestamps of the JAR, WAR, EAR files that I deployed on Java application servers after "mvn clean package" and those saved in Maven repositories after "mvn install" or "mvn deploy". > Deploy current archive without creating new archive (jar, war, ear) > --- > > Key: MDEPLOY-252 > URL: https://issues.apache.org/jira/browse/MDEPLOY-252 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy >Affects Versions: 2.8.2 >Reporter: Ivica Mikic >Priority: Major > Labels: features, maven > Fix For: waiting-for-feedback > > > It would be great to be able to deploy current archive file (jar, war, ear) > without creating a new one, to preserve timestamp from previous package or > install run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MDEPLOY-252) Deploy current archive without creating new archive (jar, war, ear)
Ivica Mikic created MDEPLOY-252: --- Summary: Deploy current archive without creating new archive (jar, war, ear) Key: MDEPLOY-252 URL: https://issues.apache.org/jira/browse/MDEPLOY-252 Project: Maven Deploy Plugin Issue Type: New Feature Components: deploy:deploy Affects Versions: 2.8.2 Reporter: Ivica Mikic It would be great to be able to deploy current archive file (jar, war, ear) without creating a new one, to preserve timestamp from previous package or install run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
