[jira] (SCM-720) Add a 'push' goal

2013-05-16 Thread Fabrizio Giudici (JIRA) 
Fabrizio Giudici created SCM-720:


 Summary: Add a 'push' goal
 Key: SCM-720
 URL: https://jira.codehaus.org/browse/SCM-720
 Project: Maven SCM
  Issue Type: Bug
Reporter: Fabrizio Giudici


I've been using for a couple of years a Maven release process where artifacts 
are first deployed to a local directory and Mercurial/Git changes are not 
pushed. This makes it possible to roll back all the changes in case of testing, 
when either the remote SCM repo or Maven repo are not reachable for a transient 
network error, etc., as well as just retry pushing/deploying the artifacts 
without re-running the whole release cycle.

Final pushing and deploying are performed by re-running Maven with a specified 
profile. I'm able to perform hg/git push by invoking their executables with the 
proper parameters by means of the antrun-plugin, but it's cumbersome. It would 
be so much better to just invoke scm:push.

Of course I'm aware that this needs implementation through all the providers. 
For distributed SCMs, push must be a full push (e.g. Git should push also 
tags); for non distributed SCMs, such as Subversion, the goals should just do 
nothing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRELEASE-695) tagNameFormat with @{project.version} tags the SNAPSHOT version

2011-07-21 Thread Fabrizio Giudici (JIRA) 

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

Fabrizio Giudici commented on MRELEASE-695:
---

BTW, I've downgraded to 2.1 as well. It's very unfortunate than a RFE which 
seems not to difficult to implement took almost 5 years to be implemented 
broken (just a consideration, not bashing anyone).

> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release 
> with the following pom:
> 
> org.apache.maven.plugins
> maven-release-plugin
> 
> true
> clean install verify
> clean install javadoc:javadoc assembly:assembly 
> deploy
> -P${release.profiles} 
> -DaltDeploymentRepository="${altDeploymentRepository}"
> @{project.version}
> 
> 
> but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MRELEASE-695) tagNameFormat with @{project.version} tags the SNAPSHOT version

2011-07-14 Thread Fabrizio Giudici (JIRA) 
tagNameFormat with @{project.version} tags the SNAPSHOT version
---

 Key: MRELEASE-695
 URL: https://jira.codehaus.org/browse/MRELEASE-695
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
Affects Versions: 2.2
Reporter: Fabrizio Giudici


The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with 
the following pom:


org.apache.maven.plugins
maven-release-plugin

true
clean install verify
clean install javadoc:javadoc assembly:assembly 
deploy
-P${release.profiles} 
-DaltDeploymentRepository="${altDeploymentRepository}"
@{project.version}




but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MGPG-17) password is specified, but still promting

2010-02-28 Thread Fabrizio Giudici (JIRA) 

[ 
http://jira.codehaus.org/browse/MGPG-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211952#action_211952
 ] 

Fabrizio Giudici commented on MGPG-17:
--

My problem is similar, in a batch environment, but it's intermittent. Sometimes 
it takes the password specified by the property, other times it fails about not 
being able to use /dev/tty (which is obvious, since it's a batch run, but the 
bug is that it doesn't use the password specified in the property). I'm seeing 
the "obsolete option" warning too.

> password is specified, but still promting
> -
>
> Key: MGPG-17
> URL: http://jira.codehaus.org/browse/MGPG-17
> Project: Maven 2.x GPG Plugin
>  Issue Type: Bug
>Affects Versions: 1.0-alpha-4
> Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 08:04:01-0500)
> Java version: 1.6.0_15
> Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.27.29-0.1-default" arch: "i386" Family: "unix"
> gpg (GnuPG) 2.0.9
> on OpenSUSE 11.1
>Reporter: Albert Kurucz
>
> Using
> mvn verify -Dgpg.passphrase=thephrase
> with thephrase replaced with the real one.
> When it get to signing, it still promts.
> It is critical, because this prompt repeats with all the 100 modules of the 
> project.
> Problem maybe related to updates/changes of gpg software.
> Related warning message:
> gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect
> can't connect to `/home/albert_kurucz/.gnupg/S.gpg-agent': No such file or 
> directory

-- 
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: (MAVENUPLOAD-2745) TheseFoolishThings moved to Sonatype

2010-02-23 Thread Fabrizio Giudici (JIRA) 

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211391#action_211391
 ] 

Fabrizio Giudici commented on MAVENUPLOAD-2745:
---

Thanks.

> TheseFoolishThings moved to Sonatype
> 
>
> Key: MAVENUPLOAD-2745
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2745
> Project: Maven Upload Requests
>  Issue Type: Task
>Reporter: Fabrizio Giudici
>
> From now on, artifacts for TheseFoolishThings won't be ever published to the 
> repo at:
> https://kenai.com/svn/tidalwave~maven-repo/release/2/it/tidalwave/thesefoolishthings/thesefoolishthings/
> but to the free Sonatype hosting, whose sync-to-Central feature will be used 
> to sync stuff to the Central Repository. The whole repo at kenai will be shut 
> down. 
> I suppose I have to tell you, so you remove the project from the list of 
> things that you periodically sync.

-- 
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] Created: (MAVENUPLOAD-2745) TheseFoolishThings moved to Sonatype

2010-02-16 Thread Fabrizio Giudici (JIRA) 
TheseFoolishThings moved to Sonatype


 Key: MAVENUPLOAD-2745
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2745
 Project: Maven Upload Requests
  Issue Type: Task
Reporter: Fabrizio Giudici


>From now on, artifacts for TheseFoolishThings won't be ever published to the 
>repo at:

https://kenai.com/svn/tidalwave~maven-repo/release/2/it/tidalwave/thesefoolishthings/thesefoolishthings/

but to the free Sonatype hosting, whose sync-to-Central feature will be used to 
sync stuff to the Central Repository. The whole repo at kenai will be shut 
down. 

I suppose I have to tell you, so you remove the project from the list of things 
that you periodically sync.

-- 
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: (MAVENUPLOAD-2743) Project TheseFoolishThings is failing sync

2010-02-14 Thread Fabrizio Giudici (JIRA) 

 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fabrizio Giudici closed MAVENUPLOAD-2743.
-

Resolution: Fixed

Now the artifacts have appeared.

> Project TheseFoolishThings is failing sync
> --
>
> Key: MAVENUPLOAD-2743
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2743
> Project: Maven Upload Requests
>  Issue Type: Bug
>Reporter: Fabrizio Giudici
>
> The project has been successfully synced a few months ago and versions 1.0.1 
> through 1.0.5 (November) were successfully synced to central. Yesterday I 
> released 1.0.6 but I don't see it yet on Central - and I didn't receive any 
> error notification.
> Please let me know.

-- 
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] Created: (MAVENUPLOAD-2743) Project TheseFoolishThings is failing sync

2010-02-14 Thread Fabrizio Giudici (JIRA) 
Project TheseFoolishThings is failing sync
--

 Key: MAVENUPLOAD-2743
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2743
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Fabrizio Giudici


The project has been successfully synced a few months ago and versions 1.0.1 
through 1.0.5 (November) were successfully synced to central. Yesterday I 
released 1.0.6 but I don't see it yet on Central - and I didn't receive any 
error notification.

Please let me know.

-- 
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: (SCM-491) release:perform with Mercurial performs a full hg clone from the remote repository

2009-10-29 Thread Fabrizio Giudici (JIRA) 

[ 
http://jira.codehaus.org/browse/SCM-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196604#action_196604
 ] 

Fabrizio Giudici commented on SCM-491:
--

I've found a workaround: 
http://weblogs.java.net/blog/fabriziogiudici/archive/2009/10/29/fixing-two-problems-maven-mercurial-hudson

> release:perform with Mercurial performs a full hg clone from the remote 
> repository
> --
>
> Key: SCM-491
> URL: http://jira.codehaus.org/browse/SCM-491
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-mercurial (hg)
>Reporter: Fabrizio Giudici
>
> Hello.
> When executing a release:perform, Maven forces hg to perform a clone of the 
> remote repository in the target/checkout directory:
> [INFO] EXECUTING: /bin/sh -c cd /home/hudson/Builds/jrawio~TEST/target && hg 
> clone -r 1.5.4 https://@kenai.com/hg/jrawio~src 
> /home/hudson/Builds/jrawio~TEST/target/checkout
> Hg repos can be huge (even gigabytes) and thus operation causes a waste of 
> bandwidth (and of time). It seems that the most obvious thing to do is to 
> clone from the local copy in the main directory (e.g. hg clone -r 1.5.4 ..) 
> and if you need to do a laster push you can explicitly specify the URL of the 
> remote repository to the hg push command.

-- 
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: (MJAVADOC-268) performance problem in AbstractJavadocMojo.getModulesLinks()

2009-10-13 Thread Fabrizio Giudici (JIRA) 

[ 
http://jira.codehaus.org/browse/MJAVADOC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194532#action_194532
 ] 

Fabrizio Giudici commented on MJAVADOC-268:
---

I'm the author of forceten - please use "hg up -C 65db9b4e5077" to get a 
version with the 2.6, as I'm temporarily reverting the project to use 2.5.

> performance problem in AbstractJavadocMojo.getModulesLinks()
> 
>
> Key: MJAVADOC-268
> URL: http://jira.codehaus.org/browse/MJAVADOC-268
> Project: Maven 2.x Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.6
> Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_13
> Java home: /home/mkleint/javatools/jdk1.6.0_13/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.29.6-desktop-2mnb" arch: "i386" Family: "unix"
>Reporter: Milos Kleint
>Priority: Critical
> Attachments: javadoc.patch
>
>
> The getModulesLinks() method is unacceptably slow under certain conditions:
> 1. project's url is defined
> 2. one or more projects in reactor do not have any java sources and are not 
> of "pom" packaging.
> For such projects the apidocs/ output folder is never created resulting in 
> repeated invokation of a forked javadoc goal. It's more severe with high 
> number of modules in reactor and high number of modules without any java 
> sources.
> as an example checkout "hg clone https://hg.kenai.com/hg/forceten~src";
> The immediate problem is in the apidocsFile.exists() condition that 
> re-triggers the forked invokation. The attached patch fixes that. However it 
> looks suspicitions that the method is being called repeatedly for each module 
> at all. Maybe the aborting condition at the start of the method body is wrong 
> (I was not able to decypher that)
> workaround is to use 2.5 or not to specify the url in pom.xml or set the 
> detectOfflineLinks parameter to "false".

-- 
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: (MAVENUPLOAD-2556) Please sync with my repo

2009-08-21 Thread Fabrizio Giudici (JIRA) 

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188008#action_188008
 ] 

Fabrizio Giudici commented on MAVENUPLOAD-2556:
---

Just a though: I'm guessing whether there's a way to make your life easier. 
Perhaps I could set up another Tidalwave Repo only for syncing to the Central 
Repo. I'd only publish stuff that is ready for you. In this case, however, we 
have to change the sync settings for BetterBeansBinding. Let me know.

> Please sync with my repo
> 
>
> Key: MAVENUPLOAD-2556
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2556
> Project: Maven Upload Requests
>  Issue Type: Wish
>Reporter: Fabrizio Giudici
>
> I'm Fabrizio Giudici, developer of BetterBeansBinding 
> (betterbeansbinding.kenai.com) and I want to sync my repo to the Central 
> Maven Repo.
> "it.tidalwave.betterbeansbinding","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Fabrizio
>  
> Giudici","fabrizio.giud...@tidalwave.it",,"https://kenai.com/svn/tidalwave~maven-repo/release/2/";
> Proof of ownership for the tidalwave.it domain: http://www.tidalwave.it/people
> Thanks. 

-- 
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: (MAVENUPLOAD-2556) Please sync with my repo

2009-08-21 Thread Fabrizio Giudici (JIRA) 

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188006#action_188006
 ] 

Fabrizio Giudici commented on MAVENUPLOAD-2556:
---

It depends on how your syncer works: the project under it/tidalwave/imageio 
can't be deployed to the Central Repo since it has dependencies on stuff that 
is not in the Central Repo. I'm working on that, but it seems a long issue and 
anyway other projects will be soon published to the Tidalwave Repo that 
probably won't be ever ready for the Central Repo. If your syncer is able to 
filter out projects that are not ready without any side effect, you can sync 
the whole repo.

> Please sync with my repo
> 
>
> Key: MAVENUPLOAD-2556
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2556
> Project: Maven Upload Requests
>  Issue Type: Wish
>Reporter: Fabrizio Giudici
>
> I'm Fabrizio Giudici, developer of BetterBeansBinding 
> (betterbeansbinding.kenai.com) and I want to sync my repo to the Central 
> Maven Repo.
> "it.tidalwave.betterbeansbinding","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Fabrizio
>  
> Giudici","fabrizio.giud...@tidalwave.it",,"https://kenai.com/svn/tidalwave~maven-repo/release/2/";
> Proof of ownership for the tidalwave.it domain: http://www.tidalwave.it/people
> Thanks. 

-- 
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] Created: (SCM-491) release:perform with Mercurial performs a full hg clone from the remote repository

2009-08-18 Thread Fabrizio Giudici (JIRA) 
release:perform with Mercurial performs a full hg clone from the remote 
repository
--

 Key: SCM-491
 URL: http://jira.codehaus.org/browse/SCM-491
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-mercurial (hg)
Reporter: Fabrizio Giudici


Hello.

When executing a release:perform, Maven forces hg to perform a clone of the 
remote repository in the target/checkout directory:

[INFO] EXECUTING: /bin/sh -c cd /home/hudson/Builds/jrawio~TEST/target && hg 
clone -r 1.5.4 https://@kenai.com/hg/jrawio~src 
/home/hudson/Builds/jrawio~TEST/target/checkout

Hg repos can be huge (even gigabytes) and thus operation causes a waste of 
bandwidth (and of time). It seems that the most obvious thing to do is to clone 
from the local copy in the main directory (e.g. hg clone -r 1.5.4 ..) and if 
you need to do a laster push you can explicitly specify the URL of the remote 
repository to the hg push command.

-- 
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] Created: (MAVENUPLOAD-2556) Please sync with my repo

2009-08-12 Thread Fabrizio Giudici (JIRA) 
Please sync with my repo


 Key: MAVENUPLOAD-2556
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2556
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Fabrizio Giudici


I'm Fabrizio Giudici, developer of BetterBeansBinding 
(betterbeansbinding.kenai.com) and I want to sync my repo to the Central Maven 
Repo.

"it.tidalwave.betterbeansbinding","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Fabrizio
 
Giudici","fabrizio.giud...@tidalwave.it",,"https://kenai.com/svn/tidalwave~maven-repo/release/2/";

Proof of ownership for the tidalwave.it domain: http://www.tidalwave.it/people

Thanks. 

-- 
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] Created: (MAVENUPLOAD-2527) Please sync with my repo

2009-07-22 Thread Fabrizio Giudici (JIRA) 
Please sync with my repo


 Key: MAVENUPLOAD-2527
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2527
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Fabrizio Giudici


I'm Fabrizio Giudici, developer of TheseFoolishThings 
(thesefoolishthings.kenai.com) and I want to sync my repo to the Central Maven 
Repo.

"it.tidalwave.thesefoolishthings","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Fabrizio
 
Giudici","fabrizio.giud...@tidalwave.it",,"https://kenai.com/svn/tidalwave~maven-repo/release/2/";
 

Proof of ownership for the tidalwave.it domain: http://www.tidalwave.it/people

Thanks.



-- 
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