[jira] Commented: (MPDF-7) Relative images are not recognised in sub folders
[ http://jira.codehaus.org/browse/MPDF-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172085#action_172085 ] Lukas Theussl commented on MPDF-7: -- The second version (with ../) does work for me, can you attach the -X output, maybe you are not using the latest snapshot? I'll have a look to fix the first issue. Relative images are not recognised in sub folders - Key: MPDF-7 URL: http://jira.codehaus.org/browse/MPDF-7 Project: Maven 2.x PDF Plugin Issue Type: Bug Affects Versions: 1.0 Environment: Maven 2.1.0, Windows XP Pro, Java 1.6 Reporter: Marco Huber Attachments: pdf-test.zip If parts of the documentation located in sub folders under the apt folder images are not recognised Example: (file under apt/administration/overview.apt) // SNIPPED START Following the overview [./../images/overview.png] // SNIPPED END The created html pages are correct. If I create the pdf I got ERROR [org.apache.fop.fo.FONode:83] 2009-04-03 11:35:05,250 - Image not found: ./../images/overview.png I enclosed an sample project that shows the issue. -- 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: (MWAR-189) webResources filtering replaced ${jdbc.url} by ${pom.url}
[
http://jira.codehaus.org/browse/MWAR-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172090#action_172090
]
Joël Royer commented on MWAR-189:
-
It's OK with version 2.1-beta-1!
Thanks!
webResources filtering replaced ${jdbc.url} by ${pom.url}
-
Key: MWAR-189
URL: http://jira.codehaus.org/browse/MWAR-189
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-2
Environment: Maven 2.1.0 / Java SE 1.6.0_13
Reporter: Joël Royer
I'm using webResources filtering and I'm surprised to see a variable
${jdbc.url] to be replaced by ${pom.url}.
My application is based on Spring 2.5 and my applicationConfig.xml contains
some variables which will be replaced at runtime., not build time.
But for an unknown reason, the war plugin replaced this variable with the
${pom.url} variable.
I have this code in my pom.xml:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
filteringtrue/filtering
directorysrc/main/webapp/directory
includes
include**/*.xml/include
/includes
/resource
/webResources
/configuration
/plugin
{code}
--
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: (MWAR-189) webResources filtering replaced ${jdbc.url} by ${pom.url}
[
http://jira.codehaus.org/browse/MWAR-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MWAR-189.
-
Assignee: Olivier Lamy
Resolution: Not A Bug
webResources filtering replaced ${jdbc.url} by ${pom.url}
-
Key: MWAR-189
URL: http://jira.codehaus.org/browse/MWAR-189
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-2
Environment: Maven 2.1.0 / Java SE 1.6.0_13
Reporter: Joël Royer
Assignee: Olivier Lamy
I'm using webResources filtering and I'm surprised to see a variable
${jdbc.url] to be replaced by ${pom.url}.
My application is based on Spring 2.5 and my applicationConfig.xml contains
some variables which will be replaced at runtime., not build time.
But for an unknown reason, the war plugin replaced this variable with the
${pom.url} variable.
I have this code in my pom.xml:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
filteringtrue/filtering
directorysrc/main/webapp/directory
includes
include**/*.xml/include
/includes
/resource
/webResources
/configuration
/plugin
{code}
--
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] Updated: (MPDF-7) Relative images are not recognised in sub folders
[ http://jira.codehaus.org/browse/MPDF-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Huber updated MPDF-7: --- Attachment: output.log I attached the output. As far I can see I use version 1.0-20090309.102020-2. Its the latest in the snapshot repo of apache. Relative images are not recognised in sub folders - Key: MPDF-7 URL: http://jira.codehaus.org/browse/MPDF-7 Project: Maven 2.x PDF Plugin Issue Type: Bug Affects Versions: 1.0 Environment: Maven 2.1.0, Windows XP Pro, Java 1.6 Reporter: Marco Huber Attachments: output.log, pdf-test.zip If parts of the documentation located in sub folders under the apt folder images are not recognised Example: (file under apt/administration/overview.apt) // SNIPPED START Following the overview [./../images/overview.png] // SNIPPED END The created html pages are correct. If I create the pdf I got ERROR [org.apache.fop.fo.FONode:83] 2009-04-03 11:35:05,250 - Image not found: ./../images/overview.png I enclosed an sample project that shows the issue. -- 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: (MPDF-7) Relative images are not recognised in sub folders
[ http://jira.codehaus.org/browse/MPDF-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172134#action_172134 ] Lukas Theussl commented on MPDF-7: -- That's the correct version. FYI, I just deployed a new snapshot that uses the latest doxia snapshots which fixes some minor issues. However, I do not understand why you get the same warning twice (Image not found: ./../images/overview.png), but nothing about ../images/overview.png. Did you check whether an image is actually included in the pdf? I only get one warning and the second image is in the pdf. Relative images are not recognised in sub folders - Key: MPDF-7 URL: http://jira.codehaus.org/browse/MPDF-7 Project: Maven 2.x PDF Plugin Issue Type: Bug Affects Versions: 1.0 Environment: Maven 2.1.0, Windows XP Pro, Java 1.6 Reporter: Marco Huber Attachments: output.log, pdf-test.zip If parts of the documentation located in sub folders under the apt folder images are not recognised Example: (file under apt/administration/overview.apt) // SNIPPED START Following the overview [./../images/overview.png] // SNIPPED END The created html pages are correct. If I create the pdf I got ERROR [org.apache.fop.fo.FONode:83] 2009-04-03 11:35:05,250 - Image not found: ./../images/overview.png I enclosed an sample project that shows the issue. -- 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] Moved: (MNG-4124) mvn --version returns OS name: windows nt (unknown)
[ http://jira.codehaus.org/browse/MNG-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Connolly moved MVERSIONS-27 to MNG-4124: Complexity: Intermediate Key: MNG-4124 (was: MVERSIONS-27) Project: Maven 2 (was: Maven 2.x Versions Plugin) mvn --version returns OS name: windows nt (unknown) -- Key: MNG-4124 URL: http://jira.codehaus.org/browse/MNG-4124 Project: Maven 2 Issue Type: Bug Reporter: Josef Stadelmann Priority: Minor C:\mvn --version Maven version: 2.0.10 Java version: 1.5.0_09 OS name: windows nt (unknown) version: 6.0 arch: x86 Family: windows C:\ that is what I get when I run mvn from a Microsoft Windows Vista System Josef -- 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-2418) Keys changed for com.cedarsoft (and eu.cedarsoft)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172145#action_172145 ] Johannes Schneider commented on MAVENUPLOAD-2418: - Yes I can: c2:16:74:66:a7:55:32:ca:4e:2c:96:01:97:02:39:a5 Keys changed for com.cedarsoft (and eu.cedarsoft) - Key: MAVENUPLOAD-2418 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2418 Project: Maven Upload Requests Issue Type: Task Reporter: Johannes Schneider Assignee: Brian Fox I migrated my server (to nexus) and changed the keys. Therefore the synchronization failed for group com.cedarsoft and eu.cedarsoft. It is no longer necessary to synchronize eu.cedarsoft since new bundles will only be released using com.cedarsoft. I will create another issue. The bundle URL has changed. -- 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: (MRELEASE-435) Problem with release:prepare for a multimodule project using continuum
Problem with release:prepare for a multimodule project using continuum -- Key: MRELEASE-435 URL: http://jira.codehaus.org/browse/MRELEASE-435 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-9 Environment: Linux, continuum, svn 1.5.2 Reporter: Lionel Champalaune I configured my release plugin as this in my project using the last 2.0 beta 9 release: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration remoteTaggingtrue/remoteTagging /configuration /plugin My project look like this Project\ pom.xml SubProject1\ pom.xml SubProject2\ pom.xml Using continuum I prepared the release and I still have the error: [ERROR] org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/svn/tags/Version/Project/SubProject1/pom.xml' already exists at org.apache.maven.shared.release.phase.ScmTagPhase.execute(ScmTagPhase.java:99) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:107) at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:43) at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) The Version repository doesn't not exist at the end Do I miss something with continuum and the new release plugin? It works well for single module (but it was already working with the previous release-plugin version) Is there an issue on that problem because it seems that the entire bugs related to svn 1.5.0 are closed. Thanks Regards Lionel -- 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-2419) eu.cedarsoft is outdated
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2419. -- Resolution: Fixed eu.cedarsoft is outdated Key: MAVENUPLOAD-2419 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2419 Project: Maven Upload Requests Issue Type: Wish Reporter: Johannes Schneider Assignee: Brian Fox It is no longer necessary to synchronize eu.cedarsoft since new bundles will only be released using com.cedarsoft. The Bundle URL is outdated. Original issue: http://jira.codehaus.org/browse/MAVENUPLOAD-1705 -- 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-2418) Keys changed for com.cedarsoft (and eu.cedarsoft)
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172149#action_172149
]
Brian Fox commented on MAVENUPLOAD-2418:
Everything is fixed but you need to add the maven key to the authorized_keys
for the mavensync account.
{noformat}
[ma...@sonatype03 m2-sync]$ ssh mavens...@maven.cedarsoft.com
The authenticity of host 'maven.cedarsoft.com (78.47.151.149)' can't be
established.
RSA key fingerprint is c2:16:74:66:a7:55:32:ca:4e:2c:96:01:97:02:39:a5.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'maven.cedarsoft.com' (RSA) to the list of known
hosts.
mavens...@maven.cedarsoft.com's password:
{noformat}
The key is here:
http://www.ibiblio.org/maven/id_dsa.pub
Keys changed for com.cedarsoft (and eu.cedarsoft)
-
Key: MAVENUPLOAD-2418
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2418
Project: Maven Upload Requests
Issue Type: Task
Reporter: Johannes Schneider
Assignee: Brian Fox
I migrated my server (to nexus) and changed the keys.
Therefore the synchronization failed for group com.cedarsoft and eu.cedarsoft.
It is no longer necessary to synchronize eu.cedarsoft since new bundles
will only be released using com.cedarsoft. I will create another issue.
The bundle URL has changed.
--
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-2414) Request sync swingjavabuilderext svn repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2414. -- Resolution: Fixed Request sync swingjavabuilderext svn repo - Key: MAVENUPLOAD-2414 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2414 Project: Maven Upload Requests Issue Type: Wish Reporter: Alexandre Navarro Assignee: Brian Fox Hi, I'm a developer swingjavabuilderext. Can you synchronize my svn release repo, there is no repo inside poms or dependencies not in Central? This is the line to add to csv conf com.kenai.swingjavabuilderext,/home/maven/repository-staging/to-ibiblio/maven-svn,svn,Alexandre Navarro,schumn...@free.fr,,https://kenai.com/svn/swingjavabuilderext~others/maven/release-repository; Thanks in advance, Alexandre Navarro -- 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-2420) Please add a com.sourcetohtml project to maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172151#action_172151 ] Brian Fox commented on MAVENUPLOAD-2420: Where can i easily see the contents of the sync repo without first rsyncing? Please add a com.sourcetohtml project to maven repository - Key: MAVENUPLOAD-2420 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2420 Project: Maven Upload Requests Issue Type: Wish Reporter: Jiri Celak Please add following line to https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv com.sourcetohtml,mavens...@web.sourceforge.net:/home/users/j/ji/jirkacelak/userweb/htdocs/maven2,rsync_ssh,Jiri Celak,j...@celak.net,, To prove I own the domain, please either go to http://www.whois.net/whois/sourcetohtml.com or to project web site http://www.sourcetohtml.com -- 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-2418) Keys changed for com.cedarsoft (and eu.cedarsoft)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172158#action_172158 ] Johannes Schneider commented on MAVENUPLOAD-2418: - Yes, thanks for pointing that out. Had a typo within the file Keys changed for com.cedarsoft (and eu.cedarsoft) - Key: MAVENUPLOAD-2418 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2418 Project: Maven Upload Requests Issue Type: Task Reporter: Johannes Schneider Assignee: Brian Fox I migrated my server (to nexus) and changed the keys. Therefore the synchronization failed for group com.cedarsoft and eu.cedarsoft. It is no longer necessary to synchronize eu.cedarsoft since new bundles will only be released using com.cedarsoft. I will create another issue. The bundle URL has changed. -- 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-455) scm:changelog command does not pick up svn changes when author has spaces
scm:changelog command does not pick up svn changes when author has spaces - Key: SCM-455 URL: http://jira.codehaus.org/browse/SCM-455 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-svn Affects Versions: 1.2 Environment: Maven 2.0.10 Reporter: Todd Thiessen Attachments: scm-author.patch If the author of a change has spaces in it, the scmLchangelog does not pick up this change. I have reproduced this with svn. I have not tried with other providers. I have done a detailed analysis of the problem and have a fix. The file which parses the changelog output is: scm\maven-scm-providers\maven-scm-providers-svn\maven-scm-provider-svnexe\src\main\java\org\apache\maven\scm\provider\svn\svnexe\command\changelog\SvnChangeLogConsumer.java This file uses a regular expression which does not recognize a regular expression which contains spaces in the author's name. The regular expression expects the author to be in a userID kind of format. So, for example, if the author of a change was thiessen, then the command mvn scm:changelog would pick up this change. However, if the author was Todd Thiessen, the change which be skipped entirely. As far as my understanding goes, svn:author is simply a property and makes no statement that the author MUST be in userID format. SVN users are free to change the author as they see fit using SVN hooks. This is reasonable since often the userID isn't very readable to a human reader. Thus putting in the author's full name is very helpful. Note that this issue has downstream effects in that it affects the change log plugin: http://maven.apache.org/plugins/maven-changelog-plugin/ I have submitted a patch with a resolution to this. The patch simply treats the author portion of an svn log command as text. It does not mandate that the author must be in a certain format. The patch includes junit tests cases which reproduce the problem and also the changes to the main code to fix it. -- 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-2418) Keys changed for com.cedarsoft (and eu.cedarsoft)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2418. -- Resolution: Fixed Looks better now. Keys changed for com.cedarsoft (and eu.cedarsoft) - Key: MAVENUPLOAD-2418 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2418 Project: Maven Upload Requests Issue Type: Task Reporter: Johannes Schneider Assignee: Brian Fox I migrated my server (to nexus) and changed the keys. Therefore the synchronization failed for group com.cedarsoft and eu.cedarsoft. It is no longer necessary to synchronize eu.cedarsoft since new bundles will only be released using com.cedarsoft. I will create another issue. The bundle URL has changed. -- 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: (MCHANGELOG-94) Changelog report does not pick up svn changes when author has spaces
Changelog report does not pick up svn changes when author has spaces Key: MCHANGELOG-94 URL: http://jira.codehaus.org/browse/MCHANGELOG-94 Project: Maven 2.x Changelog Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Todd Thiessen This bug is caused by a bug in the scm project. Please see http://jira.codehaus.org/browse/SCM-455 for further details. When/if the scm bug is fixed, the change log plugin would have to be updated to point to the SCM release where it is fixed. -- 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-2420) Please add a com.sourcetohtml project to maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172163#action_172163 ] Jiri Celak commented on MAVENUPLOAD-2420: - Just go to http://jirkacelak.users.sourceforge.net/maven2/ I have added there .htaccess so you can easily browse the content hope it will not cause issues with the rsynch? Please add a com.sourcetohtml project to maven repository - Key: MAVENUPLOAD-2420 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2420 Project: Maven Upload Requests Issue Type: Wish Reporter: Jiri Celak Assignee: Brian Fox Please add following line to https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv com.sourcetohtml,mavens...@web.sourceforge.net:/home/users/j/ji/jirkacelak/userweb/htdocs/maven2,rsync_ssh,Jiri Celak,j...@celak.net,, To prove I own the domain, please either go to http://www.whois.net/whois/sourcetohtml.com or to project web site http://www.sourcetohtml.com -- 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-2420) Please add a com.sourcetohtml project to maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2420. -- Resolution: Fixed Looks ok. I would strongly suggest you use gpg to sign the artifacts though. See here for more info: http://maven.apache.org/developers/release/releasing.html Please add a com.sourcetohtml project to maven repository - Key: MAVENUPLOAD-2420 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2420 Project: Maven Upload Requests Issue Type: Wish Reporter: Jiri Celak Assignee: Brian Fox Please add following line to https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv com.sourcetohtml,mavens...@web.sourceforge.net:/home/users/j/ji/jirkacelak/userweb/htdocs/maven2,rsync_ssh,Jiri Celak,j...@celak.net,, To prove I own the domain, please either go to http://www.whois.net/whois/sourcetohtml.com or to project web site http://www.sourcetohtml.com -- 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: (MRRESOURCES-36) ${project.build.sourceEncoding} not honoured.
[
http://jira.codehaus.org/browse/MRRESOURCES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MRRESOURCES-36.
Resolution: Fixed
Patches applied. Thanks Christian.
${project.build.sourceEncoding} not honoured.
-
Key: MRRESOURCES-36
URL: http://jira.codehaus.org/browse/MRRESOURCES-36
Project: Maven 2.x Remote Resources Plugin
Issue Type: New Feature
Affects Versions: 1.0
Environment: Maven version: 2.0.9
Java version: 1.6.0_07
OS name: linux version: 2.6.27.6-workstation arch: i386 Family: unix
Reporter: Christian Schulte
Assignee: Jason van Zyl
Priority: Blocker
Attachments: MRRESOURCES-36, MRRESOURCES-36-2,
MRRESOURCES-36-3.patch, MRRESOURCES-36-4.patch, MRRESOURCES-36-4.zip
Velocity has its own default encoding (ISO-8859-1) when reading templates and
does not honour the current environment setting. Also the plugin ignores any
source encoding which leads to encoding issues for any non-ASCII resources.
The attached patch adds a new mojo parameter sourceEncoding which defaults to
${project.build.sourceEncoding} and makes copying and appending to resources
encoding aware.
--
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: (MRRESOURCES-36) ${project.build.sourceEncoding} not honoured.
[
http://jira.codehaus.org/browse/MRRESOURCES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl reopened MRRESOURCES-36:
--
${project.build.sourceEncoding} not honoured.
-
Key: MRRESOURCES-36
URL: http://jira.codehaus.org/browse/MRRESOURCES-36
Project: Maven 2.x Remote Resources Plugin
Issue Type: New Feature
Affects Versions: 1.0
Environment: Maven version: 2.0.9
Java version: 1.6.0_07
OS name: linux version: 2.6.27.6-workstation arch: i386 Family: unix
Reporter: Christian Schulte
Assignee: Jason van Zyl
Priority: Blocker
Fix For: 1.0.1
Attachments: MRRESOURCES-36, MRRESOURCES-36-2,
MRRESOURCES-36-3.patch, MRRESOURCES-36-4.patch, MRRESOURCES-36-4.zip
Velocity has its own default encoding (ISO-8859-1) when reading templates and
does not honour the current environment setting. Also the plugin ignores any
source encoding which leads to encoding issues for any non-ASCII resources.
The attached patch adds a new mojo parameter sourceEncoding which defaults to
${project.build.sourceEncoding} and makes copying and appending to resources
encoding aware.
--
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] Updated: (MRRESOURCES-36) ${project.build.sourceEncoding} not honoured.
[
http://jira.codehaus.org/browse/MRRESOURCES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MRRESOURCES-36:
-
Affects Version/s: (was: 1.0-alpha-6)
(was: 1.0-alpha-5)
(was: 1.0-alpha-4)
(was: 1.0-beta-2)
(was: 1.0-alpha-3)
(was: 1.0-alpha-2)
(was: 1.0-alpha-1)
Fix Version/s: 1.0.1
${project.build.sourceEncoding} not honoured.
-
Key: MRRESOURCES-36
URL: http://jira.codehaus.org/browse/MRRESOURCES-36
Project: Maven 2.x Remote Resources Plugin
Issue Type: New Feature
Affects Versions: 1.0
Environment: Maven version: 2.0.9
Java version: 1.6.0_07
OS name: linux version: 2.6.27.6-workstation arch: i386 Family: unix
Reporter: Christian Schulte
Assignee: Jason van Zyl
Priority: Blocker
Fix For: 1.0.1
Attachments: MRRESOURCES-36, MRRESOURCES-36-2,
MRRESOURCES-36-3.patch, MRRESOURCES-36-4.patch, MRRESOURCES-36-4.zip
Velocity has its own default encoding (ISO-8859-1) when reading templates and
does not honour the current environment setting. Also the plugin ignores any
source encoding which leads to encoding issues for any non-ASCII resources.
The attached patch adds a new mojo parameter sourceEncoding which defaults to
${project.build.sourceEncoding} and makes copying and appending to resources
encoding aware.
--
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: (MRRESOURCES-36) ${project.build.sourceEncoding} not honoured.
[
http://jira.codehaus.org/browse/MRRESOURCES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MRRESOURCES-36.
Resolution: Fixed
${project.build.sourceEncoding} not honoured.
-
Key: MRRESOURCES-36
URL: http://jira.codehaus.org/browse/MRRESOURCES-36
Project: Maven 2.x Remote Resources Plugin
Issue Type: New Feature
Affects Versions: 1.0
Environment: Maven version: 2.0.9
Java version: 1.6.0_07
OS name: linux version: 2.6.27.6-workstation arch: i386 Family: unix
Reporter: Christian Schulte
Assignee: Jason van Zyl
Priority: Blocker
Fix For: 1.0.1
Attachments: MRRESOURCES-36, MRRESOURCES-36-2,
MRRESOURCES-36-3.patch, MRRESOURCES-36-4.patch, MRRESOURCES-36-4.zip
Velocity has its own default encoding (ISO-8859-1) when reading templates and
does not honour the current environment setting. Also the plugin ignores any
source encoding which leads to encoding issues for any non-ASCII resources.
The attached patch adds a new mojo parameter sourceEncoding which defaults to
${project.build.sourceEncoding} and makes copying and appending to resources
encoding aware.
--
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: (MRRESOURCES-38) Remove inadvertent dependency on MavenReportException in maven-reporting-api
[ http://jira.codehaus.org/browse/MRRESOURCES-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl reopened MRRESOURCES-38: -- Remove inadvertent dependency on MavenReportException in maven-reporting-api Key: MRRESOURCES-38 URL: http://jira.codehaus.org/browse/MRRESOURCES-38 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 1.1 This creates a coupling to the reporting API which is not necessary. -- 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] Updated: (MRRESOURCES-38) Remove inadvertent dependency on MavenReportException in maven-reporting-api
[ http://jira.codehaus.org/browse/MRRESOURCES-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MRRESOURCES-38: - Fix Version/s: (was: 1.1) 1.0.1 Remove inadvertent dependency on MavenReportException in maven-reporting-api Key: MRRESOURCES-38 URL: http://jira.codehaus.org/browse/MRRESOURCES-38 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 1.0.1 This creates a coupling to the reporting API which is not necessary. -- 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: (MRRESOURCES-38) Remove inadvertent dependency on MavenReportException in maven-reporting-api
[ http://jira.codehaus.org/browse/MRRESOURCES-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MRRESOURCES-38. Resolution: Fixed Remove inadvertent dependency on MavenReportException in maven-reporting-api Key: MRRESOURCES-38 URL: http://jira.codehaus.org/browse/MRRESOURCES-38 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 1.0.1 This creates a coupling to the reporting API which is not necessary. -- 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] Updated: (MRRESOURCES-35) ClassCastException
[ http://jira.codehaus.org/browse/MRRESOURCES-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MRRESOURCES-35: - Fix Version/s: 1.0.1 ClassCastException -- Key: MRRESOURCES-35 URL: http://jira.codehaus.org/browse/MRRESOURCES-35 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Christian Schulte Assignee: Jason van Zyl Priority: Blocker Fix For: 1.0.1 Attachments: MRRESOURCES-35.patch Having a dependency with versionRELEASE/version gives ClassCastException. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.model.Repository [INFO] [INFO] Trace java.lang.ClassCastException: org.apache.maven.model.Repository at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.mergeMetadata(DefaultRepositoryMetadataManager.java:193) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:166) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:49) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:129) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:557) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:250) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:505) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:466) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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: (MRRESOURCES-35) ClassCastException
[ http://jira.codehaus.org/browse/MRRESOURCES-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MRRESOURCES-35. Resolution: Fixed Patch applied. Thanks Christian. ClassCastException -- Key: MRRESOURCES-35 URL: http://jira.codehaus.org/browse/MRRESOURCES-35 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Christian Schulte Assignee: Jason van Zyl Priority: Blocker Fix For: 1.0.1 Attachments: MRRESOURCES-35.patch Having a dependency with versionRELEASE/version gives ClassCastException. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.maven.model.Repository [INFO] [INFO] Trace java.lang.ClassCastException: org.apache.maven.model.Repository at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.mergeMetadata(DefaultRepositoryMetadataManager.java:193) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:166) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:49) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:129) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:557) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:250) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:505) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665) at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:466) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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] Updated: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MNG-4112: --- Fix Version/s: 3.0-alpha-3 2.1.1 Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier Fix For: 2.1.1, 3.0-alpha-3 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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: (MRRESOURCES-30) When comparing organizations, don't compare the url
[ http://jira.codehaus.org/browse/MRRESOURCES-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172171#action_172171 ] Jason van Zyl commented on MRRESOURCES-30: -- So is this a won't fix? When comparing organizations, don't compare the url --- Key: MRRESOURCES-30 URL: http://jira.codehaus.org/browse/MRRESOURCES-30 Project: Maven 2.x Remote Resources Plugin Issue Type: Bug Affects Versions: 1.0-alpha-6, 1.0-beta-2 Reporter: Dennis Lundberg Attachments: NOTICE The OrganizationComparator in ProcessRemoteResourcesMojo takes into account both the organization's name *and* url. This leads to strange generated NOTICE files, like the one attached, which comes from a slightly modified trunk of commons-validator. I feel that the comparator should be changed so that it only compares the name of the organization. An alternative way would be to have two configurable comparators to choose from. I'm willing to do the coding, but want to solicit other's opinions first. Also see discussions here: https://issues.apache.org/jira/browse/COMMONSSITE-21 -- 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-2406) Request for automatic mirror of SourceForge project Chop-chop HTTP Client
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172173#action_172173 ] Brian Fox commented on MAVENUPLOAD-2406: Please sign your artifacts: http://chop-chophttpcl.sourceforge.net/maven2/net/sourceforge/chopchophttpclient/chopchophttpclient/0.9.0/ See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Request for automatic mirror of SourceForge project Chop-chop HTTP Client - Key: MAVENUPLOAD-2406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2406 Project: Maven Upload Requests Issue Type: Wish Reporter: Rodney Beede Assignee: Brian Fox net.sourceforge.chopchophttpclient,mavens...@web.sourceforge.net:/home/groups/c/ch/chop-chophttpcl/htdocs/maven2,rsync_ssh,Rodney Beede,sourceforge+mavencent...@rodneybeede.com -- 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-2402) Auto sync expectj.sf.net/m2repo with central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172175#action_172175 ] Brian Fox commented on MAVENUPLOAD-2402: Please make sure your artifacts are properly signed. See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Also, i might suggest changing the artifactId to all lowercase, this will save users a lot of trouble down the road. Auto sync expectj.sf.net/m2repo with central repository --- Key: MAVENUPLOAD-2402 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2402 Project: Maven Upload Requests Issue Type: Wish Reporter: Johan Walles Assignee: Brian Fox net.sourceforge.expectj,mavens...@web.sourceforge.net:/home/groups/e/ex/expectj/htdocs/m2repo,rsync_ssh,Johan Walles,johan.wal...@gmail.com,, As can be seen on http://sourceforge.net/projects/expectj, I'm one of the admins for the project. -- 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-2405) Sync jitr.org release repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172174#action_172174 ] Brian Fox commented on MAVENUPLOAD-2405: Please paste a link where i can view the repository contents, and make sure the artifacts are signed properly: See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Sync jitr.org release repository Key: MAVENUPLOAD-2405 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2405 Project: Maven Upload Requests Issue Type: Wish Reporter: Josh Devins org.jitr,mavens...@web.sourceforge.net:/home/groups/j/ji/jitr/htdocs/repositories/release,rsync_ssh,Josh Devins,joshdev...@jitr.org,, -- 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-2382) Sync my repository to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172176#action_172176 ] Brian Fox commented on MAVENUPLOAD-2382: Make sure the artifacts are signed. See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Get a proper group id and include a link to the repository that is browsable so i can verify the contents. Sync my repository to the central repository Key: MAVENUPLOAD-2382 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2382 Project: Maven Upload Requests Issue Type: Wish Reporter: Alex Eagle Assignee: Brian Fox args4j,rs...@jakeherringbone.com:/srv/m2repo,rsync_ssh,Alex Eagle,alexea...@google.com,, Note, I am working on a project in the google-maven-repository that depends on args4j. To upload that project, you require that I have no repository/ tags, so I need to upload args4j to the central repository. I have communicated with Kohsuke (the author of args4j and Hudson) about this and gotten his blessing to upload. The files are copied from http://download.java.net/maven/2/args4j/ with the scmurl//scm and license/ tags added, as the Maven documentation requires. -- 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-2396) Please automatically sync the ProtoJ repository with the maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172178#action_172178 ] Brian Fox commented on MAVENUPLOAD-2396: Please make sure the artifacts are properly signed. See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Also include a browseable url of the repository so I can validate the contents ahead of rsync. Please automatically sync the ProtoJ repository with the maven central repository - Key: MAVENUPLOAD-2396 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2396 Project: Maven Upload Requests Issue Type: Wish Reporter: Ashley Williams Assignee: Brian Fox I am the owner of ProtoJ. com.google.code.protoj,mavens...@web.sourceforge.net:/home/groups/p/pr/protojrepo/mavensync,rsync_ssh,Ashley Williams,ashpub...@mac.com,, -- 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-2398) Repository sync request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172177#action_172177 ] Brian Fox commented on MAVENUPLOAD-2398: Please make sure the artifacts are properly signed. See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Also include a browseable url of the repository so I can validate the contents ahead of rsync. Repository sync request --- Key: MAVENUPLOAD-2398 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2398 Project: Maven Upload Requests Issue Type: Wish Reporter: Oran Kelly Assignee: Brian Fox com.adenki,mavens...@web.sourceforge.net:/home/groups/s/sm/smppapi/htdocs/maven-repo,rsync_ssh,Oran Kelly,or...@users.sourceforge.net,, Whois link showing me as the owner of adenki.com: http://www.whois.net/whois/adenki.com -- 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-2401) rsync of 3rd party project to maven repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172179#action_172179 ] Brian Fox commented on MAVENUPLOAD-2401: Prepare the rest of the information requested in the jira and also Please make sure the artifacts are properly signed. See here for details on how it should be done: http://maven.apache.org/developers/release/releasing.html Also include a browseable url of the repository so I can validate the contents ahead of rsync. rsync of 3rd party project to maven repo Key: MAVENUPLOAD-2401 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2401 Project: Maven Upload Requests Issue Type: Wish Reporter: Lothar Hegebart We want to publish the maven artifacts of a friends project (groupid de.pudig.dmachinery) which is developed/hosted on our infrastructure. As our servers domain is adorsys.de this would be a 3rd party project according to the guidelines (http://maven.apache.org/guides/mini/guide-central-repository-upload.html). So we seek approval for the upload. In case you want to contact him: stefan.pudig AT pudig.de or stefan.pudig AT adorsys.de The bundle url is just a dummy, as it doesnt fit our request. Thanks for your help. -- 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-2421) Upload of AspectJ 1.6.4
Upload of AspectJ 1.6.4 --- Key: MAVENUPLOAD-2421 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2421 Project: Maven Upload Requests Issue Type: Wish Reporter: Andy Clement Hi, please can you upload AspectJ 1.6.4. I left it so long to raise a jira for 1.6.3 upload (because I thought i'd be able to get it done automatically) that now I have both that release and this release that need an upload - sorry about that. -- 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: (MECLIPSE-368) Dependency configuration in DependencyManagement with exclusions is ignored
[ http://jira.codehaus.org/browse/MECLIPSE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172182#action_172182 ] Henri Tremblay commented on MECLIPSE-368: - Any news on this one? It is really annoying and there's a patch and test case attached. I would have expect it sooner :-( Dependency configuration in DependencyManagement with exclusions is ignored --- Key: MECLIPSE-368 URL: http://jira.codehaus.org/browse/MECLIPSE-368 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: Core : Dependencies resolution and build path (.classpath) Affects Versions: 2.4 Environment: Ubuntu Linux 7.10 Reporter: jh Attachments: exclusion-example-20080116.zip, MECLIPSE-368.patch A transitive dependency which is defined in the DependencyManagement section with exclusions does not take these exclusions into account when generating an eclipse classpath. Example: - childProject has a dependency 'acegi-security-tiger' - parentProject has a dependencyManagement section that defines the version and the exclusions - acegi-security-tiger has a transitive dependency to acegi-security - parentProject has defined acegi-security and a number of exclusions one of which is spring-remoting 1.2.7 - childProject's classpath ends up with spring-remoting 1.2.7 as dependency - we are using spring 2.5.1 which does not have spring-remoting If I check dependencies with dependency:tree -Dscope=null the dependency resolving of acegi-security-tiger stops with acegi-security and no other transitive dependencies are added (all are excluded) Workaround is to add acegi-security in childProject's pom. Main concern here is that dependency resolution in the eclipse plugin seems to be different from the dependency plugin. -- 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: (MNG-4112) Set property containing the currently executing maven version.
[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172183#action_172183 ] Jason van Zyl commented on MNG-4112: I'll take a look later this week. There are two branches with lots of changes including the embedder, but this is not hard to add but the embedder is not the right place. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: http://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 Issue Type: Improvement Reporter: Paul Gier Fix For: 2.1.1, 3.0-alpha-3 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- 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-2406) Request for automatic mirror of SourceForge project Chop-chop HTTP Client
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172195#action_172195 ] Rodney Beede commented on MAVENUPLOAD-2406: --- I've signed all the release files with GPG. I just used the gpg plug-in for Maven instead of the release plug-in. My public key can be accessed via a link on the project's website. http://chop-chophttpcl.sourceforge.net/ Request for automatic mirror of SourceForge project Chop-chop HTTP Client - Key: MAVENUPLOAD-2406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2406 Project: Maven Upload Requests Issue Type: Wish Reporter: Rodney Beede Assignee: Brian Fox net.sourceforge.chopchophttpclient,mavens...@web.sourceforge.net:/home/groups/c/ch/chop-chophttpcl/htdocs/maven2,rsync_ssh,Rodney Beede,sourceforge+mavencent...@rodneybeede.com -- 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-2406) Request for automatic mirror of SourceForge project Chop-chop HTTP Client
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172193#action_172193 ] Rodney Beede commented on MAVENUPLOAD-2406: --- I read the details for release, but I ran into some difficulties. My project is not an apache.org project so I don't store its SCM via Apache's staging system. Do you need a copy of my public gpg key somewhere even though this isn't a project directly hosted by Apache? Where should I upload the gpg signatures to? Should they be mixed into my http://chop-chophttpcl.sourceforge.net/maven2/net/sourceforge/chopchophttpclient/chopchophttpclient/0.9.1/ folder? Request for automatic mirror of SourceForge project Chop-chop HTTP Client - Key: MAVENUPLOAD-2406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2406 Project: Maven Upload Requests Issue Type: Wish Reporter: Rodney Beede Assignee: Brian Fox net.sourceforge.chopchophttpclient,mavens...@web.sourceforge.net:/home/groups/c/ch/chop-chophttpcl/htdocs/maven2,rsync_ssh,Rodney Beede,sourceforge+mavencent...@rodneybeede.com -- 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-2386) Dozer 5.0 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172197#action_172197 ] Stephan Kleine commented on MAVENUPLOAD-2386: - Could you please process this asap or point out any problems that prevent you from doing so? The latest Dozer jars I found in any Maven repository where v4.4 which dates from 12/27/2008 :/ Dozer 5.0 Upload Key: MAVENUPLOAD-2386 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2386 Project: Maven Upload Requests Issue Type: Task Reporter: Matt Tierney Attachments: dozer-5.0-bundle.jar Dozer is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types. Dozer supports simple property mapping, complex type mapping, bi-directional mapping, implicit-explicit mapping, as well as recursive mapping. This includes mapping collection attributes that also need mapping at the element level. Dozer not only supports mapping between attribute names, but also converting between types. Many conversion scenarios are supported out of the box, but Dozer also allows you to specify custom conversions via XML. The mapper is used any time you need to take one type of Java Bean and map it to another type of Java Bean. Most field mapping can be done automatically by Dozer using reflection, but any custom mapping can be predescribed in XML format. Mapping is bi-directional so only one relationship between classes needs defining. If any property names on both objects are the same you do not even need to do any explicit property mapping for these fields. Thanks in advance! -- 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-2406) Request for automatic mirror of SourceForge project Chop-chop HTTP Client
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172199#action_172199 ] Brian Fox commented on MAVENUPLOAD-2406: Ok that looks good. Yes you should push your key out to a public server, otherwise people can't validate the signature. Request for automatic mirror of SourceForge project Chop-chop HTTP Client - Key: MAVENUPLOAD-2406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2406 Project: Maven Upload Requests Issue Type: Wish Reporter: Rodney Beede Assignee: Brian Fox net.sourceforge.chopchophttpclient,mavens...@web.sourceforge.net:/home/groups/c/ch/chop-chophttpcl/htdocs/maven2,rsync_ssh,Rodney Beede,sourceforge+mavencent...@rodneybeede.com -- 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-2406) Request for automatic mirror of SourceForge project Chop-chop HTTP Client
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2406. -- Resolution: Fixed Request for automatic mirror of SourceForge project Chop-chop HTTP Client - Key: MAVENUPLOAD-2406 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2406 Project: Maven Upload Requests Issue Type: Wish Reporter: Rodney Beede Assignee: Brian Fox net.sourceforge.chopchophttpclient,mavens...@web.sourceforge.net:/home/groups/c/ch/chop-chophttpcl/htdocs/maven2,rsync_ssh,Rodney Beede,sourceforge+mavencent...@rodneybeede.com -- 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: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent
[ http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172207#action_172207 ] Noel Keating commented on MRELEASE-317: --- It seems that the CheckDependencySnapshotsPhase includes the parent artifact as part of it check, but the RewritePomPhases (AbstractRewritePomsPhase.rewriteParent) does not consider the resolvedSnapshotDependencies when transforming the pom file. So even though you are asked to set the parent to released, a SNAPSHOT parent is committed. release:prepare should fail if any pom depends on SNAPSHOT parent - Key: MRELEASE-317 URL: http://jira.codehaus.org/browse/MRELEASE-317 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Environment: maven-2.0.8 java-1.6 Reporter: Petr Kozelka Priority: Critical Currently the release plugin happily releases a pom that declares a SNAPSHOT version of parent. Such a release is exposed to a danger of irreproducibility: 1.) on another machine 2.) at another time (parent may significantly change in the meantime) While it can be sometimes convenient, it is, as I am quite sure, a bad behavior. -- 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] Updated: (MRELEASE-317) release:prepare should fail if any pom depends on SNAPSHOT parent
[ http://jira.codehaus.org/browse/MRELEASE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noel Keating updated MRELEASE-317: -- Attachment: MRELEASE-317.patch.txt This patch adds code to check the resolvedSnapshotDependencies in AbstractRewritePomsPhase.rewriteParent(...), (plus a test case) release:prepare should fail if any pom depends on SNAPSHOT parent - Key: MRELEASE-317 URL: http://jira.codehaus.org/browse/MRELEASE-317 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Environment: maven-2.0.8 java-1.6 Reporter: Petr Kozelka Priority: Critical Attachments: MRELEASE-317.patch.txt Currently the release plugin happily releases a pom that declares a SNAPSHOT version of parent. Such a release is exposed to a danger of irreproducibility: 1.) on another machine 2.) at another time (parent may significantly change in the meantime) While it can be sometimes convenient, it is, as I am quite sure, a bad behavior. -- 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-2417) Sync maven-scm-provider-svnjava from code.google.com
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MAVENUPLOAD-2417. - Resolution: Fixed fix in rev 762498 Sync maven-scm-provider-svnjava from code.google.com Key: MAVENUPLOAD-2417 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2417 Project: Maven Upload Requests Issue Type: Bug Reporter: Olivier Lamy Assignee: Olivier Lamy Line to add : com.google.scm.svnjava,/home/maven/repository-staging/to-ibiblio/maven-svn,svn,Olivier Lamy,ol...@apache.org,,http://maven-scm-provider-svnjava.googlecode.com/svn/repository/release/; 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-2398) Repository sync request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172214#action_172214 ] Oran Kelly commented on MAVENUPLOAD-2398: - Browsable repository URL: http://smppapi.sourceforge.net/maven-repo/ The repo is now updated with GPG signatures for the artifacts. My key is uploaded to http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x5E35D35E Repository sync request --- Key: MAVENUPLOAD-2398 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2398 Project: Maven Upload Requests Issue Type: Wish Reporter: Oran Kelly Assignee: Brian Fox com.adenki,mavens...@web.sourceforge.net:/home/groups/s/sm/smppapi/htdocs/maven-repo,rsync_ssh,Oran Kelly,or...@users.sourceforge.net,, Whois link showing me as the owner of adenki.com: http://www.whois.net/whois/adenki.com -- 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: (MECLIPSE-547) Maven Eclipse plugin 2.6 with AJDT changes are not backwards compatible.
Maven Eclipse plugin 2.6 with AJDT changes are not backwards compatible. Key: MECLIPSE-547 URL: http://jira.codehaus.org/browse/MECLIPSE-547 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: AJDT support Affects Versions: 2.6 Reporter: Tan Quach Priority: Minor Since upgrading to version 2.6 of the plugin, my projects are all now failing because of this issue: http://jira.codehaus.org/browse/MECLIPSE-544 I understand there is a workaround but now, i have to go through all of my projects to add this configuration element. It would better if the addition for AJDT support was not so disruptive to existing projects. Could we not have the default configuration to be the workaround? (e.g. use default ajdtVersionnone/ajdtVersion) -- 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: (MECLIPSE-200) Please add support for the AJDT plugin
[ http://jira.codehaus.org/browse/MECLIPSE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172218#action_172218 ] Tan Quach commented on MECLIPSE-200: I agree with Alexander, and I've created a new issue: http://jira.codehaus.org/browse/MECLIPSE-547 Please add support for the AJDT plugin -- Key: MECLIPSE-200 URL: http://jira.codehaus.org/browse/MECLIPSE-200 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: AJDT support Affects Versions: 2.2 Reporter: Eric Berry Assignee: Arnaud Heritier Fix For: 2.6 Attachments: ajdt.patch, maven-eclipse-plugin.zip, maven-eclipse-plugin.zip Please add support for the AJDT plugin. I have modified the eclipse plugin for our site with the needed changes. I have attached the modifications that I made for someone to look at and incorporate into the plugin. -- 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: (MERCURY-108) jetty transport leaks threads
jetty transport leaks threads - Key: MERCURY-108 URL: http://jira.codehaus.org/browse/MERCURY-108 Project: Mercury Issue Type: Bug Reporter: Oleg Gusakov Assignee: Oleg Gusakov After a call to the transport, httpClient instance is left as a daemon thread. Several hundred calls run VM out of memory -- 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: (MERCURY-108) jetty transport leaks threads
[ http://jira.codehaus.org/browse/MERCURY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172223#action_172223 ] Oleg Gusakov commented on MERCURY-108: -- as temp. workaround - adding close() method to the repository reader/writer - to at least stop some of the theads jetty transport leaks threads - Key: MERCURY-108 URL: http://jira.codehaus.org/browse/MERCURY-108 Project: Mercury Issue Type: Bug Affects Versions: 1.0-alpha-6 Reporter: Oleg Gusakov Assignee: Oleg Gusakov After a call to the transport, httpClient instance is left as a daemon thread. Several hundred calls run VM out of memory -- 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] Updated: (MERCURY-108) jetty transport leaks threads
[ http://jira.codehaus.org/browse/MERCURY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MERCURY-108: - Affects Version/s: 1.0-alpha-6 jetty transport leaks threads - Key: MERCURY-108 URL: http://jira.codehaus.org/browse/MERCURY-108 Project: Mercury Issue Type: Bug Affects Versions: 1.0-alpha-6 Reporter: Oleg Gusakov Assignee: Oleg Gusakov After a call to the transport, httpClient instance is left as a daemon thread. Several hundred calls run VM out of memory -- 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-2417) Sync maven-scm-provider-svnjava from code.google.com
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez reopened MAVENUPLOAD-2417: - Assignee: Carlos Sanchez (was: Olivier Lamy) needs to be checked out in the server Sync maven-scm-provider-svnjava from code.google.com Key: MAVENUPLOAD-2417 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2417 Project: Maven Upload Requests Issue Type: Bug Reporter: Olivier Lamy Assignee: Carlos Sanchez Line to add : com.google.scm.svnjava,/home/maven/repository-staging/to-ibiblio/maven-svn,svn,Olivier Lamy,ol...@apache.org,,http://maven-scm-provider-svnjava.googlecode.com/svn/repository/release/; 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-2396) Please automatically sync the ProtoJ repository with the maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172229#action_172229 ] Ashley Williams commented on MAVENUPLOAD-2396: -- Ok the repo is now browsable at this url: http://protojrepo.sourceforge.net/mavensync/ and the new bundle url is: com.google.code.protoj,mavens...@web.sourceforge.net:/home/groups/p/pr/protojrepo/htdocs/mavensync,rsync_ssh,Ashley Williams,ashpub...@mac.com,, Can you give me a pointer on how to generate the gpg files given that I am deploying using the maven ant tasks - my project is ant based. Thanks. Please automatically sync the ProtoJ repository with the maven central repository - Key: MAVENUPLOAD-2396 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2396 Project: Maven Upload Requests Issue Type: Wish Reporter: Ashley Williams Assignee: Brian Fox I am the owner of ProtoJ. com.google.code.protoj,mavens...@web.sourceforge.net:/home/groups/p/pr/protojrepo/mavensync,rsync_ssh,Ashley Williams,ashpub...@mac.com,, -- 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: (MERCURY-108) jetty transport leaks threads
[ http://jira.codehaus.org/browse/MERCURY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172232#action_172232 ] Oleg Gusakov commented on MERCURY-108: -- removed the read() lead, write to follow .. jetty transport leaks threads - Key: MERCURY-108 URL: http://jira.codehaus.org/browse/MERCURY-108 Project: Mercury Issue Type: Bug Affects Versions: 1.0-alpha-6 Reporter: Oleg Gusakov Assignee: Oleg Gusakov After a call to the transport, httpClient instance is left as a daemon thread. Several hundred calls run VM out of memory -- 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-2396) Please automatically sync the ProtoJ repository with the maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172234#action_172234 ] Brian Fox commented on MAVENUPLOAD-2396: I'm not able to access that url: http://protojrepo.sourceforge.net/mavensync/ You can use the gpg tool to sign the artifacts directly, there is probably an ant task to do it as well, but i'm not sure. Please automatically sync the ProtoJ repository with the maven central repository - Key: MAVENUPLOAD-2396 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2396 Project: Maven Upload Requests Issue Type: Wish Reporter: Ashley Williams Assignee: Brian Fox I am the owner of ProtoJ. com.google.code.protoj,mavens...@web.sourceforge.net:/home/groups/p/pr/protojrepo/mavensync,rsync_ssh,Ashley Williams,ashpub...@mac.com,, -- 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-2398) Repository sync request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MAVENUPLOAD-2398. -- Resolution: Fixed Repository sync request --- Key: MAVENUPLOAD-2398 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2398 Project: Maven Upload Requests Issue Type: Wish Reporter: Oran Kelly Assignee: Brian Fox com.adenki,mavens...@web.sourceforge.net:/home/groups/s/sm/smppapi/htdocs/maven-repo,rsync_ssh,Oran Kelly,or...@users.sourceforge.net,, Whois link showing me as the owner of adenki.com: http://www.whois.net/whois/adenki.com -- 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-2396) Please automatically sync the ProtoJ repository with the maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172242#action_172242 ] Ashley Williams commented on MAVENUPLOAD-2396: -- I was in the middle of recreating the repo when you tried to connect, the url should be fine now. Looks like I'll have to sign each and every file in the repo by hand for now. I'll see if there's any way I can hook into the maven plugin programmatically to do this but I'm not optimistic. Please automatically sync the ProtoJ repository with the maven central repository - Key: MAVENUPLOAD-2396 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2396 Project: Maven Upload Requests Issue Type: Wish Reporter: Ashley Williams Assignee: Brian Fox I am the owner of ProtoJ. com.google.code.protoj,mavens...@web.sourceforge.net:/home/groups/p/pr/protojrepo/mavensync,rsync_ssh,Ashley Williams,ashpub...@mac.com,, -- 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-2396) Please automatically sync the ProtoJ repository with the maven central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172244#action_172244 ] Brian Fox commented on MAVENUPLOAD-2396: something like find . | xargs -iFILE gpg --clearsign FILE in each of your folders should do it for you in 2 shots (once in each folder with artifacts) Please automatically sync the ProtoJ repository with the maven central repository - Key: MAVENUPLOAD-2396 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2396 Project: Maven Upload Requests Issue Type: Wish Reporter: Ashley Williams Assignee: Brian Fox I am the owner of ProtoJ. com.google.code.protoj,mavens...@web.sourceforge.net:/home/groups/p/pr/protojrepo/mavensync,rsync_ssh,Ashley Williams,ashpub...@mac.com,, -- 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-2417) Sync maven-scm-provider-svnjava from code.google.com
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=172254#action_172254 ] Carlos Sanchez commented on MAVENUPLOAD-2417: - The server does teh update but you have to manually do the initial checkout The groupId should be com.google.code.maven-scm-provider-svnjava Sync maven-scm-provider-svnjava from code.google.com Key: MAVENUPLOAD-2417 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2417 Project: Maven Upload Requests Issue Type: Bug Reporter: Olivier Lamy Assignee: Olivier Lamy Line to add : com.google.scm.svnjava,/home/maven/repository-staging/to-ibiblio/maven-svn,svn,Olivier Lamy,ol...@apache.org,,http://maven-scm-provider-svnjava.googlecode.com/svn/repository/release/; 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
