[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2015-01-02 Thread Robert Scholte (JIRA)

 [ 
https://jira.codehaus.org/browse/MDEPLOY-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MDEPLOY-183.
--

   Resolution: Won't Fix
Fix Version/s: (was: waiting-for-feedback)
 Assignee: Robert Scholte

> Add a delay before deployAtEnd
> --
>
> Key: MDEPLOY-183
> URL: https://jira.codehaus.org/browse/MDEPLOY-183
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.1
>Reporter: Matthew Jones
>Assignee: Robert Scholte
>Priority: Minor
> Attachments: DeployMojoSleep.patch
>
>
> The deployAtEnd is a great feature but I've had to make this modification to 
> allow for a short wait time before deployment in order to make a few 
> adjustments to files that were created during the build process. It really 
> saved me a lot of headache just being able to get in and fix things manually.
> New parameter
> deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)


[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2014-12-28 Thread Matthew Jones (JIRA)

[ 
https://jira.codehaus.org/browse/MDEPLOY-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359821#comment-359821
 ] 

Matthew Jones commented on MDEPLOY-183:
---

I haven't had any problems in months with gpg signing or anything else that 
caused me to have to use this to manually do anything. So I'm not even using it 
anymore. I don't know what was causing those problems back then but probably 
nobody else would need this.

> Add a delay before deployAtEnd
> --
>
> Key: MDEPLOY-183
> URL: https://jira.codehaus.org/browse/MDEPLOY-183
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.1
>Reporter: Matthew Jones
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: DeployMojoSleep.patch
>
>
> The deployAtEnd is a great feature but I've had to make this modification to 
> allow for a short wait time before deployment in order to make a few 
> adjustments to files that were created during the build process. It really 
> saved me a lot of headache just being able to get in and fix things manually.
> New parameter
> deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)


[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2014-12-28 Thread Karl-Heinz Marbaise (JIRA)

 [ 
https://jira.codehaus.org/browse/MDEPLOY-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl-Heinz Marbaise updated MDEPLOY-183:


Fix Version/s: waiting-for-feedback

> Add a delay before deployAtEnd
> --
>
> Key: MDEPLOY-183
> URL: https://jira.codehaus.org/browse/MDEPLOY-183
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.1
>Reporter: Matthew Jones
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: DeployMojoSleep.patch
>
>
> The deployAtEnd is a great feature but I've had to make this modification to 
> allow for a short wait time before deployment in order to make a few 
> adjustments to files that were created during the build process. It really 
> saved me a lot of headache just being able to get in and fix things manually.
> New parameter
> deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)


[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2014-06-29 Thread Robert Scholte (JIRA)

[ 
https://jira.codehaus.org/browse/MDEPLOY-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348968#comment-348968
 ] 

Robert Scholte commented on MDEPLOY-183:


I'd prefer not to introduce workarounds in this plugin for other plugins. I 
don't mind having a look at the MGPG issues as long as they have a valid 
testcase to reproduce their issue and preferably with a patch to fix it. If you 
*really* need that timeout, I'd suggest to use the maven-antrun-plugin to do a 
sleep.

> Add a delay before deployAtEnd
> --
>
> Key: MDEPLOY-183
> URL: https://jira.codehaus.org/browse/MDEPLOY-183
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.1
>Reporter: Matthew Jones
>Priority: Minor
> Attachments: DeployMojoSleep.patch
>
>
> The deployAtEnd is a great feature but I've had to make this modification to 
> allow for a short wait time before deployment in order to make a few 
> adjustments to files that were created during the build process. It really 
> saved me a lot of headache just being able to get in and fix things manually.
> New parameter
> deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)


[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2014-06-29 Thread Matthew Jones (JIRA)

[ 
https://jira.codehaus.org/browse/MDEPLOY-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348962#comment-348962
 ] 

Matthew Jones commented on MDEPLOY-183:
---

Hmm, I'm not sure. For more detail what I was specifically having to fix up 
were errors caused by the maven gpg plugin which runs after the packaging 
phase. There is a patch MGPG-43 that fixes that to run in a different phase but 
that isn't applied. This may also be related to MGPG-33 (or at least someone 
else in the comments on that was having a problem). I do have more than one key 
and for some reason the gpg plugin was signing 1-2 out of ~500 artifacts 
incorrectly. Then these would upload to sonatype where it would get a signature 
validation exception. This sign-and-deploy calls the deployer.deploy and gets 
the signatures setup for deployment.

I'd found that I had time while larger artifacts (jars) were uploading (slow 
connection) to manually run gpg to find all of the incorrect signatures and 
update them to be correct before they were uploaded and it worked. Using this 
"deployAtEnd" worked even better, and adding in a slight wait was all that was 
needed to make it completely automated to verify signatures and resign the 
invalid ones.

I was not able to figure out why these artifacts were not being signed 
correctly during the maven process and it "seemed" completely random. Sometimes 
it would be one jar, another times a war, another times a pom. It seemed like a 
threading issue, where somehow artifacts were being overwritten after they were 
signed, but I couldn't see that from the logs and even with -T 1 it didn't 
change anything. But actually running the plugin with the sign-and-deploy made 
it quite a bit *easier* to actually deploy everything to nexus/sonatype than 
not using it and trying to upload it manually.

Perhaps next time around, I'll be able to figure out why it wasn't signing 
right, maybe it won't happen. at all and everything will be fine.

> Add a delay before deployAtEnd
> --
>
> Key: MDEPLOY-183
> URL: https://jira.codehaus.org/browse/MDEPLOY-183
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.1
>Reporter: Matthew Jones
>Priority: Minor
> Attachments: DeployMojoSleep.patch
>
>
> The deployAtEnd is a great feature but I've had to make this modification to 
> allow for a short wait time before deployment in order to make a few 
> adjustments to files that were created during the build process. It really 
> saved me a lot of headache just being able to get in and fix things manually.
> New parameter
> deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)


[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2014-06-29 Thread Robert Scholte (JIRA)

[ 
https://jira.codehaus.org/browse/MDEPLOY-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348961#comment-348961
 ] 

Robert Scholte commented on MDEPLOY-183:


{quote}... in order to make a few adjustments to files that were created during 
the build process.{quote}
This should have happened *before* the package phase. The result of the 
packaging-plugin (m-jar-p, m-war-p, m-ear-p, etc) is the bundle being 
"installed" and "deployed", right?

> Add a delay before deployAtEnd
> --
>
> Key: MDEPLOY-183
> URL: https://jira.codehaus.org/browse/MDEPLOY-183
> Project: Maven Deploy Plugin
>  Issue Type: Improvement
>  Components: deploy:deploy
>Affects Versions: 2.8.1
>Reporter: Matthew Jones
>Priority: Minor
> Attachments: DeployMojoSleep.patch
>
>
> The deployAtEnd is a great feature but I've had to make this modification to 
> allow for a short wait time before deployment in order to make a few 
> adjustments to files that were created during the build process. It really 
> saved me a lot of headache just being able to get in and fix things manually.
> New parameter
> deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)


[jira] (MDEPLOY-183) Add a delay before deployAtEnd

2014-06-27 Thread Matthew Jones (JIRA)
Matthew Jones created MDEPLOY-183:
-

 Summary: Add a delay before deployAtEnd
 Key: MDEPLOY-183
 URL: https://jira.codehaus.org/browse/MDEPLOY-183
 Project: Maven Deploy Plugin
  Issue Type: Improvement
  Components: deploy:deploy
Affects Versions: 2.8.1
Reporter: Matthew Jones
Priority: Minor
 Attachments: DeployMojoSleep.patch

The deployAtEnd is a great feature but I've had to make this modification to 
allow for a short wait time before deployment in order to make a few 
adjustments to files that were created during the build process. It really 
saved me a lot of headache just being able to get in and fix things manually.

New parameter
deployAtEndSleep - ms to sleep before deploying at end.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)