[jira] Reopened: (MAVENUPLOAD-2261) Automatic upload of mockito versions.
[ https://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Brakkee reopened MAVENUPLOAD-2261: --- We have seen that the mockito rsync has stopped working. The last successful rsync was last year on 29th of December. Now we want to get a new release out. Can you re-enable the rsync again (at least once to get the release out)? > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: https://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee >Assignee: Carlos Sanchez > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-186) Active profiles are not carried through into the release descriptor
[ http://jira.codehaus.org/browse/MRELEASE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230488#action_230488 ] Erik Brakkee commented on MRELEASE-186: --- This is currently still an issue. I first have to do release:prepare, then edit some poms for the correct versions and after that do a release:perform. > Active profiles are not carried through into the release descriptor > --- > > Key: MRELEASE-186 > URL: http://jira.codehaus.org/browse/MRELEASE-186 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.0-beta-4 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > When using a profile for a release it is not passed on in the > release.properties so it's not executed in the perform goal. -- 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()
[ http://jira.codehaus.org/browse/MJAVADOC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228721#action_228721 ] Erik Brakkee commented on MJAVADOC-268: --- I can also confirm it still exists in version 2.7. Reverting back to 2.5 solves the problem, however with only drawback which is that there is no multi-module javadoc available for the overall site. At least my site generation time reduces now from 45 minutes to about 7. > 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 >Assignee: Vincent Siveton >Priority: Critical > Fix For: 2.6.1 > > 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: (MSITE-479) stage-deploy re-run's all javadoc's for every module
[
http://jira.codehaus.org/browse/MSITE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228720#action_228720
]
Erik Brakkee commented on MSITE-479:
This appears to be already reported and is a problem in the javadoc plugin
see http://jira.codehaus.org/browse/MJAVADOC-268
> stage-deploy re-run's all javadoc's for every module
>
>
> Key: MSITE-479
> URL: http://jira.codehaus.org/browse/MSITE-479
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Andrew Hughes
>
> When running 'mvn clean install site:site' a javadoc's report work's as
> expected...
> When running 'mvn clean install site:site site:stage-deploy
> -DstagingSiteURL=file://c:/temp/site' there is a problem with the javadoc
> report. In a multi module project each time the javadoc's report is run, it
> claims all other modules have not had the javadoc's run yet - and it runs
> them.
> Consequently, if I have the following multi-module layout..
> {noformat}
> ./project
> ./project/module-1
> ./project/module-2
> ./project/module-3
> ./project/module-4
> ./project/module-5
> ./project/module-6
> {noformat}
> For modules 1..6 it will complain that all other modules have not had their
> javadoc goal run and the javadoc plugin will run 6x6=36 times! Note that the
> log's below are for module-6.
> {noformat}
> [INFO]
>
> [INFO] Building module-6
> [INFO]
>
> ...truncated log's...
> [INFO] Generating "JavaDocs" report.
> [WARNING] Source files encoding has not been set, using platform encoding
> Cp1252, i.e. build is platform dependent!
> [ERROR] Error fetching link:
> http://java.sun.com/javase/6/docs/api/package-list. Ignored it.
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'com.acme.project:module-1:jar:0.0.1-SNAPSHOT'. Trying to invoke it...
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'com.acme.project:module-2:jar:0.0.1-SNAPSHOT'. Trying to invoke it...
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'com.acme.project:module-3:jar:0.0.1-SNAPSHOT'. Trying to invoke it...
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'com.acme.project:module-4:jar:0.0.1-SNAPSHOT'. Trying to invoke it...
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'com.acme.project:module-5:jar:0.0.1-SNAPSHOT'. Trying to invoke it...
> [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6.1:javadoc'
> has not be previously called for the project:
> 'com.acme.project:module-6:jar:0.0.1-SNAPSHOT'. Trying to invoke it...
> {noformat}
> The concern I have is that site:site never complains about this and it's
> output is correct, why would stage-deploy be manipulating the report
> generation?
> Hopefully this is a mis-configuration on my part :)
--
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: (MNG-4636) Deploy minimal pom at release
Deploy minimal pom at release - Key: MNG-4636 URL: http://jira.codehaus.org/browse/MNG-4636 Project: Maven 2 & 3 Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 3.0-alpha-7 Environment: All Reporter: Erik Brakkee Priority: Minor It would be good to filter poms when deploying them to a repository. A typical use case is where I want to exclude test dependencies and repository and plugin settings from a pom at deploy because they are not relevant for users. A current issue is where my productin code uses JPA 2.0 and uses hibernate for testing. In this case, the hibernate (test) dependency is not essential and can be removed. Another example are repository settings which can point to, for instance, local proxies that have no meaning outside of the development environment. Implementing this feature means that it will be possible to use local repositories for efficiency, yet still deploy them to the central maven repo. -- 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-2261) Automatic upload of mockito versions.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Brakkee closed MAVENUPLOAD-2261. - Resolution: Fixed The problems appears to be corrected now as I am seeing daily rsyncs in the server logs. > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee >Assignee: Carlos Sanchez > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- 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] Reopened: (MAVENUPLOAD-2261) Automatic upload of mockito versions.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Brakkee reopened MAVENUPLOAD-2261: --- Rsync is not working anymore. Looking at the system log file /var/log/messages, it appears that the last rsync attempt was at Jan 27th 00:41 CET. Also, there are no failed login attempts after that, so apparently the automatic rsync has stopped working. Here are the last relevant entries from the log file: Jan 25 00:40:36 shikra sshd[28364]: Accepted publickey for mockito from 38.97.124.18 port 41183 ssh2 Jan 25 00:40:39 shikra sshd[28401]: Accepted publickey for mockito from 38.97.124.18 port 41184 ssh2 Jan 26 00:44:02 shikra sshd[2145]: Accepted publickey for mockito from 38.97.124.18 port 54213 ssh2 Jan 26 00:44:06 shikra sshd[2185]: Accepted publickey for mockito from 38.97.124.18 port 54216 ssh2 Jan 27 00:41:08 shikra sshd[11529]: Accepted publickey for mockito from 38.97.124.18 port 56208 ssh2 Jan 27 00:41:12 shikra sshd[11566]: Accepted publickey for mockito from 38.97.124.18 port 56212 ssh2 > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee >Assignee: Carlos Sanchez > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- 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-2261) Automatic upload of mockito versions.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153323#action_153323 ] Erik Brakkee commented on MAVENUPLOAD-2261: --- Just to prevent questions: Note that the remote path for rsync is '/'. This path is correct because on the server side, the path is modified to a full pathname of the repository root. This is necessary to prevent access to the full filesystem on my server. > Automatic upload of mockito versions. > - > > Key: MAVENUPLOAD-2261 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Erik Brakkee > > Authenticity > = > Please contact Szczepan Faber for information about the authenticity of this > request. He is the owner of the mockito.org domain. > Also, my name will appear shortly on the mockito wiki at > http://code.google.com/p/mockito/. -- 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-2261) Automatic upload of mockito versions.
Automatic upload of mockito versions. - Key: MAVENUPLOAD-2261 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2261 Project: Maven Upload Requests Issue Type: Wish Reporter: Erik Brakkee Authenticity = Please contact Szczepan Faber for information about the authenticity of this request. He is the owner of the mockito.org domain. Also, my name will appear shortly on the mockito wiki at http://code.google.com/p/mockito/. -- 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
