[jira] Commented: (MAVENUPLOAD-2652) Upload saxon 9.1.0.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199175#action_199175 ] Carlos Sanchez commented on MAVENUPLOAD-2652: - did you modify the jar provided by saxon? we always deploy the original ones, modified versions would need to go in your groupId > Upload saxon 9.1.0.7 > > > Key: MAVENUPLOAD-2652 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2652 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Dan Tran > > Changes to this bundle compare to 8.x > - All jars are in one project, the main on is saxon.jar, the rest is in the > form of classifiers. > This is much easier to upload when the next release available if any > - No dependencies. > - groupId is changed from net.sf.saxon to net.sourceforge.saxon > - The pom contains maven profile to show how the bundle is created > - The main saxon.jar was modified to add all required license files. > -- 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-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199173#action_199173 ] Michael Heuer commented on MAVENUPLOAD-2572: Great, thanks Carlos. > upload new version 0.8.90 of tango-icon-theme, note license and groupId have > changed > > > Key: MAVENUPLOAD-2572 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Heuer >Assignee: Carlos Sanchez > > The Tango Desktop Project exists to help create a consistent graphical user > interface experience for free and Open Source software. > The Tango icon theme is a basic set of desktop icons that follow the style > guidelines. The set has been created as a proof of concept for the style, but > works rather well as a replacement for the base theme under GNOME and KDE. -- 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-2673) Auto-sync com.pholser with Maven central repo
Auto-sync com.pholser with Maven central repo - Key: MAVENUPLOAD-2673 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2673 Project: Maven Upload Requests Issue Type: Wish Reporter: Paul Holser "com.pholser","phol...@login.geekisp.com:/home/pholser/maven","rsync_ssh","Paul Holser","phol...@alumni.rice.edu",, -- 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] Issue Comment Edited: (MPIR-171) support "TimeZones" as a timezone
[
http://jira.codehaus.org/browse/MPIR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199162#action_199162
]
Jerome Lacoste edited comment on MPIR-171 at 11/23/09 6:16 PM:
---
I've implemented a HTML version of the team-list that uses
http://js.fleegix.org/plugins/date/date
to support "String" timezones.
See http://coffeebreaks.org/tmp/mvn-mpir-171/team-list2.html for demo
the diff to the generated files is
{code}
--- team-list2.html 2009-11-24 01:07:46.0 +0100
+++ team-list.html 2009-11-23 23:38:37.0 +0100
@@ -521,29 +521,18 @@
-
-
[jira] Commented: (MPIR-171) support "TimeZones" as a timezone
[ http://jira.codehaus.org/browse/MPIR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199162#action_199162 ] Jerome Lacoste commented on MPIR-171: - I've implemented a HTML version of the team-list that uses http://js.fleegix.org/plugins/date/date to support "String" timezones. See http://coffeebreaks.org/tmp/mvn-mpir-171/team-list2.html for demo the diff to the generated files is --- team-list2.html 2009-11-24 01:07:46.0 +0100 +++ team-list.html 2009-11-23 23:38:37.0 +0100 @@ -521,29 +521,18 @@ - -
[jira] Closed: (MAVENUPLOAD-2651) Please re-upload javax.ws.rs:jsr311-api:*:1.1 on http://repo2.maven.org/maven2/ from http://download.java.net/maven/2/
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2651. --- Resolution: Fixed Assignee: Carlos Sanchez uploaded, removing the section from the pom previous version was probably copied from download.java.net > Please re-upload javax.ws.rs:jsr311-api:*:1.1 on > http://repo2.maven.org/maven2/ from http://download.java.net/maven/2/ > -- > > Key: MAVENUPLOAD-2651 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2651 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jakub Podlesak >Assignee: Carlos Sanchez > > Due to reasons described by Paul Sandoz (JSR-311 co-spec lead) in [1], we had > to update the above mentioned artifacts. > Could you please update them on the central maven repository? > - Quote from [1]: - > Previously when we distributed jsr311-api version 1.1 to the java.net maven > repo we naively thought that the spec was done and dusted. However, we had to > make some changes to accommodate integration with Servlet 3.0. > We do not anticipate any more changes. The maintenance review for 1.1 closes > on the 1st of Nov. But i need to make switch in the Jersey source now to > prepare for the release (i will send another email on that). > - End Quote - > Thanks, > ~Jakub > [1]http://markmail.org/search/?q=list%3Anet.java.dev.jersey.users+change+to+depend+on+jsr311-api+version+1.1#query:list%3Anet.java.dev.jersey.users%20change%20to%20depend%20on%20jsr311-api%20version%201.1+page:1+mid:ywxiyanw5stm53di+state:results -- 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-2164) Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199159#action_199159 ] Joern Huxhorn commented on MAVENUPLOAD-2164: Well, I've found this here: http://www.mail-archive.com/repo-maintain...@maven.apache.org/msg01599.html groupId: de.huxhorn.lilith Error: Command line executed: /bin/sh -c 'rsync --include=*/ --include=**/maven-metadata.xml* --exclude=* --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz "--rsh=ssh " [EMAIL PROTECTED]:/home/groups/l/li/lilith/htdocs/repository/de/huxhorn/lilith/ /home/maven/repository-staging/to-ibiblio/maven2/de/huxhorn/lilith/'org.codehaus.plexus.util.cli.CommandLineException: Error while executing external command, process killed.Error while executing external command, process killed.Process timeout out after 900 seconds groupId: de.huxhorn.sulky Error: Command line executed: /bin/sh -c 'rsync --include=*/ --include=**/maven-metadata.xml* --exclude=* --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz "--rsh=ssh " [EMAIL PROTECTED]:/home/groups/s/su/sulky/htdocs/repository/de/huxhorn/sulky/ /home/maven/repository-staging/to-ibiblio/maven2/de/huxhorn/sulky/'org.codehaus.plexus.util.cli.CommandLineException: Error while executing external command, process killed.Error while executing external command, process killed.Process timeout out after 900 seconds And I guessed that it was my fault because of the problem is described above. Anyway, my artifacts won't show up in the central repository. This is my repository: http://lilith.sourceforge.net/repository/de/huxhorn/lilith/de.huxhorn.lilith/ The 0.9.37 artifacts of Lilith are there since 2009-11-12, the same is the case for sulky 0.9.9. If the above isn't the problem then I really don't understand why the artifacts are not syncing. Beside all this, please remove one of the syncs (or direct them both to the lilith repo) and change my email to the one I provided above. I mistakenly left out the "users" - it should have been huxh...@users.sf.net - and the contact address is better suited anyway. I assume that I would receive an email if sync fails, right? Is it possible that my artifacts are not showing up because the old sulky repos does not contain the new versions and the new lilith versions depend on the new sulky versions? I'll rsync to the sulky repo as well right now, just to be sure. > Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith > --- > > Key: MAVENUPLOAD-2164 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2164 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Joern Huxhorn >Assignee: Carlos Sanchez > > "de.huxhorn.sulky","mavens...@shell.sourceforge.net:/home/groups/s/su/sulky/htdocs/repository",,"rsync_ssh","Joern > Huxhorn","huxh...@sf.net",, > "de.huxhorn.lilith","mavens...@shell.sourceforge.net:/home/groups/l/li/lilith/htdocs/repository",,"rsync_ssh","Joern > Huxhorn","huxh...@sf.net",, > This request is actually about two projects, sulky and lilith. > I added both URLs - as project and contributor URL. > I sincerely hope that I've done everything correctly since this is my very > first submission to the central maven repository. > I own the domain huxhorn.de as you can verify on http://www.denic.de > Therefore I also own sulky.huxhorn.de as well as lilith.huxhorn.de > I'm also the sole developer registered in the respective sourceforge projects > http://sf.net/projects/sulky > and > http://sf.net/projects/lilith > Since this form *requires* an upload bundle URL I entered a URL to the comma > separated sync file... > Please let me know if everything is OK or if somethings still wrong/missing. > Thank you. -- 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-2666) Sync open source project VRaptor 3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199158#action_199158 ] Carlos Sanchez commented on MAVENUPLOAD-2666: - we already have "br.com.caelum.seleniumdsl","mavens...@web.sourceforge.net:/home/groups/s/se/seleniumdsl/htdocs/maven","rsync_ssh","Caue Guerra","caue.gue...@caelum.com.br",, "br.com.caelum.stella","mavens...@web.sourceforge.net:/home/groups/c/ca/caelum-stella/htdocs/maven","rsync_ssh","Caue Guerra","caue.gue...@caelum.com.br",, "br.com.caelum.tubaina","mavens...@web.sourceforge.net:/home/groups/t/tu/tubaina/htdocs/maven","rsync_ssh","Luiz Real","luiz.r...@caelum.com.br",, do we need to remove them and just put the one you submitted? > Sync open source project VRaptor 3 > -- > > Key: MAVENUPLOAD-2666 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2666 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Lucas Cavalcanti > > Hi, add please add the remote server synchronization for VRaptor 3: > "br.com.caelum","mavens...@caelum.com.br:/home/mavensync/repo","rsync_ssh","Lucas > Cavalcanti","lucas.cavalca...@caelum.com.br",, > 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] Closed: (MAVENUPLOAD-2664) Please add my project "Maven Twitter Plugin" to the central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2664. --- Resolution: Fixed Assignee: Carlos Sanchez > Please add my project "Maven Twitter Plugin" to the central repo > > > Key: MAVENUPLOAD-2664 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2664 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Vineet Manohar >Assignee: Carlos Sanchez > > Following is the comma delimited version of rsync ready release repository. > The maven public key has rsync access to this account. > CSV: > "com.vineetmanohar","r...@repo.vineetmanohar.com:/home/repo/html/releases","rsync_ssh","Vineet > Manohar","vineet.mano...@gmail.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-2660) Upload of project j-oto from code.google.com
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199157#action_199157 ] Carlos Sanchez commented on MAVENUPLOAD-2660: - you need to add the md5 and sha1 checksums of the files > Upload of project j-oto from code.google.com > > > Key: MAVENUPLOAD-2660 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2660 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Eduardo Pereda > Attachments: uploadToMavenRepo.csv > > > Hi, > This is the first time I am doing an upload to maven central repo. > I followed the guide here > (http://maven.apache.org/guides/mini/guide-central-repository-upload.html) > I saw on a link > (https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv) > that several projects in code.google.com deploy their artifacts directly > from the subversion repository. > I am imitating them (or at least trying) since I don't have any rsync nor > rsync_ssh server for me. > The attached csv file has these two lines: > "com.google.code.joto","http://j-oto.googlecode.com/svn/repos/release-repository/","svn","Eduardo > Pereda","epe...@gmail.com",, > "com.google.code.joto","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Eduardo > > Pereda","epe...@gmail.com",,"http://j-oto.googlecode.com/svn/repos/release-repository/"; > I guess only one of them is valid, but I am not sure. I apologize for the > inconvenient. > Regards, > Edu > PS: I am one of the owners of j-oto project > (http://code.google.com/p/j-oto/people/list). -- 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-2663) Please sync the "autodao" repository from sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2663. --- Resolution: Fixed Assignee: Carlos Sanchez > Please sync the "autodao" repository from sourceforge.net > - > > Key: MAVENUPLOAD-2663 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2663 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Marat Radchenko >Assignee: Carlos Sanchez > > Please synch the repository of the "AutoDAO" project from sourceforge.net. > Sourceforge project: http://sourceforge.net/projects/autodao/ > Project web site: http://autodao.sourceforge.net/ > comma delimited info: > "net.sf.autodao","mavens...@web.sourceforge.net:/home/groups/a/au/autodao/htdocs/maven2/","rsync_ssh","Marat > Radchenko","ma...@slonopotamus.org",, > You can see that I am an admin of this project from the development page: > https://sourceforge.net/projects/autodao/develop > or from my personal sourceforge page: > http://sourceforge.net/users/slonopotamus > Thank you for your support! -- 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-2660) Upload of project j-oto from code.google.com
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2660. --- Resolution: Fixed Assignee: Carlos Sanchez > Upload of project j-oto from code.google.com > > > Key: MAVENUPLOAD-2660 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2660 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Eduardo Pereda >Assignee: Carlos Sanchez > Attachments: uploadToMavenRepo.csv > > > Hi, > This is the first time I am doing an upload to maven central repo. > I followed the guide here > (http://maven.apache.org/guides/mini/guide-central-repository-upload.html) > I saw on a link > (https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv) > that several projects in code.google.com deploy their artifacts directly > from the subversion repository. > I am imitating them (or at least trying) since I don't have any rsync nor > rsync_ssh server for me. > The attached csv file has these two lines: > "com.google.code.joto","http://j-oto.googlecode.com/svn/repos/release-repository/","svn","Eduardo > Pereda","epe...@gmail.com",, > "com.google.code.joto","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Eduardo > > Pereda","epe...@gmail.com",,"http://j-oto.googlecode.com/svn/repos/release-repository/"; > I guess only one of them is valid, but I am not sure. I apologize for the > inconvenient. > Regards, > Edu > PS: I am one of the owners of j-oto project > (http://code.google.com/p/j-oto/people/list). -- 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-2662) "se.grunddata.dzo","mavens...@web.sourceforge.net:/home/groups/d/dz/dzo/htdocs/m2repo","rsync_ssh","Ulf Naslund","ulf.nasl...@grunddata.se",,
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MAVENUPLOAD-2662.
---
Resolution: Fixed
Assignee: Carlos Sanchez
> "se.grunddata.dzo","mavens...@web.sourceforge.net:/home/groups/d/dz/dzo/htdocs/m2repo","rsync_ssh","Ulf
> Naslund","ulf.nasl...@grunddata.se",,
> -
>
> Key: MAVENUPLOAD-2662
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2662
> Project: Maven Upload Requests
> Issue Type: Wish
>Reporter: Ulf Näslund
>Assignee: Carlos Sanchez
>
> "se.grunddata.dzo","mavens...@web.sourceforge.net:/home/groups/d/dz/dzo/htdocs/m2repo","rsync_ssh","Ulf
> Naslund","ulf.nasl...@grunddata.se",,
> Hi!
> I have redirected the domain-name ("dzo.grunddata.se")
> to sourceforget.net. I hope this is enough "proof" that I control the domain.
> Regards
> Ulf Naslund
--
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-2659) repository synchronization
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2659. --- Resolution: Fixed Assignee: Carlos Sanchez Added the top group com.sirika > repository synchronization > -- > > Key: MAVENUPLOAD-2659 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2659 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Sami Dalouche >Assignee: Carlos Sanchez > > Hi, > Is it possible to add the following files to the list of automatically > synchronized repositories ? > "com.sirika.httpclienthelpers","rsync://developers.sirika.com/maven2/releases","rsync","Sami > Dalouche","sami.dalou...@gmail.com",, > "com.sirika.pymager","rsync://developers.sirika.com/maven2/releases","rsync","Sami > Dalouche","sami.dalou...@gmail.com",, > URLs : > http://developers.sirika.com/httpclienthelpers/ > http://developers.sirika.com/pymager-java-client/ > thanks, > Sami Dalouche > PS: I am not sure whether the previous information is enough to allow me to > use the "com.sirika.*" namespaces. If you want a more solid proof of it, I > can always upload -- 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-2658) Please upload MessAdmin 4.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199154#action_199154 ] Carlos Sanchez commented on MAVENUPLOAD-2658: - you would need to create a synchronized repo, see http://maven.apache.org/guides/mini/guide-central-repository-upload.html > Please upload MessAdmin 4.2 > --- > > Key: MAVENUPLOAD-2658 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2658 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: codehauser > Attachments: MessAdmin-4.2-bundles.zip > > > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Core-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-ClickStream-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-DiskBrowser-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Ehcache-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-JMX-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Log4J-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-ScriptExecutor-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-Serializable-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-ServletStats-4.2-bundle.jar > http://messadmin.sourceforge.net/maven2/4.2/MessAdmin-SessionKiller-4.2-bundle.jar > http://messadmin.sourceforge.net/ > http://messadmin.sourceforge.net/#%5B%5BLicense%20%2F%20Contact%5D%5D > MessAdmin is a light-weigth and non-intrusive tool for monitoring Java > HttpSession and more. Please upload! -- 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-2657) automatically sync dbmaintain
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2657. --- Resolution: Fixed Assignee: Carlos Sanchez > automatically sync dbmaintain > - > > Key: MAVENUPLOAD-2657 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2657 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Filip Neven >Assignee: Carlos Sanchez > > "org.dbmaintain","mavens...@web.sourceforge.net:/home/groups/d/db/dbmaintain/htdocs/m2-repo","rsync_ssh","Filip > Neven","filip.ne...@gmail.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-2656) Upload Stripes-1.5.2 to Maven Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2656. --- Resolution: Fixed Assignee: Carlos Sanchez > Upload Stripes-1.5.2 to Maven Repository > > > Key: MAVENUPLOAD-2656 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2656 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Ben Gunter >Assignee: Carlos Sanchez > > Could you please upload the stripes-1.5.1 bundle to the public maven > repository. 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] Closed: (MAVENUPLOAD-2655) Syncrhonize ZeroTurnaround Open Source repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2655. --- Resolution: Fixed Assignee: Carlos Sanchez > Syncrhonize ZeroTurnaround Open Source repository > - > > Key: MAVENUPLOAD-2655 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2655 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jevgeni Kabanov >Assignee: Carlos Sanchez > > We'd like to synchronize the ZeroTurnaround Open Source repository with Maven > Central. The important part for us is the JRebel Maven plugin, so if the > repository sync doesn't fit you, perhaps there are alternatives? -- 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-2653) Sync sidaof project from SF
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2653. --- Resolution: Fixed Assignee: Carlos Sanchez added using web.sourceforge.net host > Sync sidaof project from SF > --- > > Key: MAVENUPLOAD-2653 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2653 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jeff Jensen >Assignee: Carlos Sanchez > > "net.sf.sidaof", > "mavens...@frs.sourceforge.net:/home/frs/project/s/si/sidaof/releases", > "rsync_ssh", "Jeff Jensen", "jeffjen...@upstairstechnology.com",, > proof: listed as admin: > http://sourceforge.net/projects/sidaof/develop -- 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: (MNG-4466) Plugin Metaversion Compatibility
[ http://jira.codehaus.org/browse/MNG-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4466. -- Resolution: Fixed Fix Version/s: 3.0-alpha-6 Assignee: Benjamin Bentmann Strangely this somehow got back working since then it seems. Anyway, the statement stands, those metaversions should not be used. Extended the model validator in [r883537|http://svn.apache.org/viewvc?view=revision&revision=883537] to ban them. > Plugin Metaversion Compatibility > > > Key: MNG-4466 > URL: http://jira.codehaus.org/browse/MNG-4466 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0-alpha-4 >Reporter: Fernando Ribeiro >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-6 > > > According to the compatibility notes at > http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html: > "For the sake of reproducible builds, Maven 3.x no longer supports usage of > [the RELEASE and LATEST] metaversions in the POM." > LATEST is working fine for me in alpha-4. -- 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-2650) Syncing OpenFaces repository with the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199150#action_199150 ] Carlos Sanchez commented on MAVENUPLOAD-2650: - your sync was removed previously for being in error for long time and not receiving response from your side (Darya Shumilina) In your current repo you are missing the md5 and sha1 signatures, and the config should be "org.openfaces","ma...@sshrepo.openfaces.org:/home/maven/repository","rsync_ssh","Andrew Shapovalov","andrew.shapova...@teamdev.com" > Syncing OpenFaces repository with the central repository > > > Key: MAVENUPLOAD-2650 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2650 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Andrew Shapovalov > > Hi! > Please add this sync string to your scheduler: > "org.openfaces", > "ma...@sshrepo.openfaces.org:/home/maven/repository/org/openfaces/openfaces/", > "rsync_ssh", "Andrew Shapovalov", "andrew.shapova...@teamdev.com" > Sincerely, > Andrew -- 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-2648) Version 2.1-jdk15 of UISpec4J
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2648. --- Resolution: Fixed Assignee: Carlos Sanchez > Version 2.1-jdk15 of UISpec4J > - > > Key: MAVENUPLOAD-2648 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2648 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Pascal Pratmarty >Assignee: Carlos Sanchez > Attachments: uispec4j-2.1-jdk15-bundle.jar > > > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit and TestNG test > harnesses. -- 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-2647) Version jdk6-2.1 of UISpec4J
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2647. --- Resolution: Fixed Assignee: Carlos Sanchez > Version jdk6-2.1 of UISpec4J > > > Key: MAVENUPLOAD-2647 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2647 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Pascal Pratmarty >Assignee: Carlos Sanchez > Attachments: uispec4j-2.1-jdk16-bundle.jar > > > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit and TestNG test > harnesses. -- 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-2645) Please sync the "sfac" repository from sourceforge.net
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2645. --- Resolution: Fixed Assignee: Carlos Sanchez > Please sync the "sfac" repository from sourceforge.net > -- > > Key: MAVENUPLOAD-2645 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2645 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Olivier Berlanger >Assignee: Carlos Sanchez > > Please synch the repository of the "Swing Framework and Components" (SFaC) > project from sourceforge.net. > Sourceforge project: http://sourceforge.net/projects/sfac/ > Project web site: http://sfac.sourceforge.net/ > comma delimited info: > "net.sf.sfac","mavens...@web.sourceforge.net:/home/groups/s/sf/sfac/mavenRepo","rsync_ssh","Olivier > Berlanger","olivier.berlan...@rvponp.fgov.be",, > You can see that I am an admin of this project from the development page: > http://sourceforge.net/projects/sfac/develop > or from my personal sourceforge page: > http://sourceforge.net/users/berlangero/ > Thank you for your support! -- 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: (SCM-461) Support TFS as SCM Provider
[ http://jira.codehaus.org/browse/SCM-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed SCM-461. - Resolution: Fixed Fix Version/s: 1.3 provider added. Txs to Subhash and Martin! > Support TFS as SCM Provider > --- > > Key: SCM-461 > URL: http://jira.codehaus.org/browse/SCM-461 > Project: Maven SCM > Issue Type: Improvement >Affects Versions: 1.3 >Reporter: Subhash >Assignee: Mark Struberg > Fix For: 1.3 > > Attachments: scm-461-maven-scm-provider-tfs.patch > > > Support for Microsoft TFS is being added to Maven by a new scm-provider: > maven-scm-provider-tfs. The attached patch file contains the changes made to > http://svn.apache.org/repos/asf/maven/scm/trunk -- 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: (SCM-491) release:perform with Mercurial performs a full hg clone from the remote repository
[ http://jira.codehaus.org/browse/SCM-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed SCM-491. - Resolution: Fixed Fix Version/s: 1.3 this should be fixed by MRELEASE-501 Please use the localCheckout option to use a file:// clone from the local repo instead of going over the network: mvn release:perform -DlocalCheckout=true > release:perform with Mercurial performs a full hg clone from the remote > repository > -- > > Key: SCM-491 > URL: http://jira.codehaus.org/browse/SCM-491 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-mercurial (hg) >Reporter: Fabrizio Giudici >Assignee: Mark Struberg > Fix For: 1.3 > > > Hello. > When executing a release:perform, Maven forces hg to perform a clone of the > remote repository in the target/checkout directory: > [INFO] EXECUTING: /bin/sh -c cd /home/hudson/Builds/jrawio~TEST/target && hg > clone -r 1.5.4 https://@kenai.com/hg/jrawio~src > /home/hudson/Builds/jrawio~TEST/target/checkout > Hg repos can be huge (even gigabytes) and thus operation causes a waste of > bandwidth (and of time). It seems that the most obvious thing to do is to > clone from the local copy in the main directory (e.g. hg clone -r 1.5.4 ..) > and if you need to do a laster push you can explicitly specify the URL of the > remote repository to the hg push command. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2644) CSV to upload jminix to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2644. --- Resolution: Fixed Assignee: Carlos Sanchez > CSV to upload jminix to maven central > - > > Key: MAVENUPLOAD-2644 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2644 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Laurent Bovet >Assignee: Carlos Sanchez > > Please add the following synchronization: > "org.jminix","ma...@maven.jminix.org:m2repo/releases","rsync_ssh","Laurent > Bovet","lbo...@jminix.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] Closed: (MAVENUPLOAD-2643) mongo java driver
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2643. --- Resolution: Fixed Assignee: Carlos Sanchez > mongo java driver > - > > Key: MAVENUPLOAD-2643 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2643 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Eliot Horowitz >Assignee: Carlos Sanchez > > "org.mongodb","rsync://buildbot.mongodb.org/maven/","rsync","Eliot > Horowitz","el...@mongodb.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] Closed: (MAVENUPLOAD-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2572. --- Resolution: Fixed > upload new version 0.8.90 of tango-icon-theme, note license and groupId have > changed > > > Key: MAVENUPLOAD-2572 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Heuer >Assignee: Carlos Sanchez > > The Tango Desktop Project exists to help create a consistent graphical user > interface experience for free and Open Source software. > The Tango icon theme is a basic set of desktop icons that follow the style > guidelines. The set has been created as a proof of concept for the style, but > works rather well as a replacement for the base theme under GNOME and KDE. -- 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-2630) Please upload spring-json-1.2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2630. --- Resolution: Fixed Assignee: Carlos Sanchez > Please upload spring-json-1.2.1 > --- > > Key: MAVENUPLOAD-2630 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2630 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Kai Ulrich >Assignee: Carlos Sanchez > Attachments: spring-json-1.2.1-bundle.jar, > spring-json-1.2.1-bundle.jar > > > Spring Json-View adds JavaScript Object Notation (JSON) support to > Spring-MVC. It is deeply integrated into the Spring-MVC module and can be > used with a variety of standard controllers. > I'm the lead developer in spring-json, please upload! > Thanks > Kai -- 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-2615) rsync_ssh request for svenson and jcouchdb
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199145#action_199145 ] Sven Helmberger commented on MAVENUPLOAD-2615: -- Why is this issue closed? what happened to the "you'll have to wait" option? > rsync_ssh request for svenson and jcouchdb > -- > > Key: MAVENUPLOAD-2615 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2615 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Sven Helmberger >Assignee: Carlos Sanchez > > "com.google.code.svenson","mvnrs...@fforw.de:/home/mvnrsync/m2repo/releases","rsync_ssh","Sven > Helmberger","i...@fforw.de" > "com.google.code.jcouchdb","mvnrs...@fforw.de:/home/mvnrsync/m2repo/releases","rsync_ssh","Sven > Helmberger","i...@fforw.de" -- 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-511) Build error when publishing a new version of the site through the command line. Error: Embedded error: Unable to commit file. The svn command failed. svn: URL '----------' d
Build error when publishing a new version of the site through the command line.
Error: Embedded error: Unable to commit file. The svn command failed. svn: URL
'--' doesn't exist
--
Key: SCM-511
URL: http://jira.codehaus.org/browse/SCM-511
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-site
Environment: Command line, Java
Reporter: Rolan Sanchez
Priority: Minor
In declaring interdependencies by referencing project properties e.g.,
reports/${project.groupId}/${project.artifactId}/${project.version}
if a newer version of the site is created and then if try to publish it to SVN,
Maven cannot create the parent directory.
Since the parent directory does not exist in SVN, Maven does not automatically
create and publish site to SVN and an error is thrown:
" Embedded error: Unable to commit file. The svn command failed. svn: URL
'https:///svn/../trunk/www//com.ears//1.0.2-SNAPSHOT/.'
doesn't exist".
Maven expects at least parent directory to be created manually in order to
publish the site before the build.
Instead the Directory creation for the newer version should be automatic.
--
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-4466) Plugin Metaversion Compatibility
Plugin Metaversion Compatibility Key: MNG-4466 URL: http://jira.codehaus.org/browse/MNG-4466 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 3.0-alpha-4 Reporter: Fernando Ribeiro According to the compatibility notes at http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html: "For the sake of reproducible builds, Maven 3.x no longer supports usage of [the RELEASE and LATEST] metaversions in the POM." LATEST is working fine for me in alpha-4. -- 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-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Heuer reopened MAVENUPLOAD-2572: The URL above works for me. > upload new version 0.8.90 of tango-icon-theme, note license and groupId have > changed > > > Key: MAVENUPLOAD-2572 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Heuer >Assignee: Carlos Sanchez > > The Tango Desktop Project exists to help create a consistent graphical user > interface experience for free and Open Source software. > The Tango icon theme is a basic set of desktop icons that follow the style > guidelines. The set has been created as a proof of concept for the style, but > works rather well as a replacement for the base theme under GNOME and KDE. -- 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: (DOXIASITETOOLS-34) move the SiteResourceLoader from plexus-velocity to doxia-site-tools
move the SiteResourceLoader from plexus-velocity to doxia-site-tools Key: DOXIASITETOOLS-34 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-34 Project: Maven Doxia Sitetools Issue Type: Improvement Components: Site renderer Reporter: Brett Porter this class seems to have been added specifically as a hack to get *.vm files working in the site. It uses a static variable to point to a single resource no matter what is looked up. It would be better to move this to Doxia and configure it with the actual resource tree (src/site/apt, src/site/resources, etc.) and set it on the velocity component per execution if possible. -- 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-2641) NeoDatis ODB Maven Upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2641. --- Resolution: Fixed Assignee: Carlos Sanchez > NeoDatis ODB Maven Upload request > - > > Key: MAVENUPLOAD-2641 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2641 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Olivier Smadja >Assignee: Carlos Sanchez > > "org.neodatis.odb","mavens...@web.sourceforge.net:/home/groups/n/ne/neodatis-odb/htdocs/m2-repo","rsync_ssh","Olivier > Smadja","oliv...@neodatis.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] Closed: (MAVENUPLOAD-2627) Change request for groupId jena.hpl.hp.com
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2627. --- Resolution: Fixed Assignee: Carlos Sanchez > Change request for groupId jena.hpl.hp.com > -- > > Key: MAVENUPLOAD-2627 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2627 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: Andy Seaborne >Assignee: Carlos Sanchez > Attachments: com.hp.hpl.jena-csv.sh, com.hp.hpl.jena-shell.sh > > > Change request: group id "com.hp.hpl.jena" > This is a request to change the server and contact email address for the > entry for group id "com.hp.hpl.jena". > CSV form: > "com.hp.hpl.jena","mavens...@openjena.org:/var/repo","rsync_ssh","Andy > Seaborne","andy.seabo...@gmail.com",, > It is currently "mavens...@jena.hpl.hp.com:/var/repo" and > "andy.seabo...@hp.com". > I am an administrator and contributor for the sourceforge project. > The previous JIRA request was http://jira.codehaus.org/browse/MAVENUPLOAD-1943 > The HPLabs research lab responsible for the development of Jena will be > closed at the end of October as part of internal reorganisation and the > people made redundant by HP, including the active developers of Jena from HP. > We have a mutually agreed transfer plan between the developers and > HP,aprroved by HP legal. The copyright for the code will be transferred to a > non-profit 3rd party and we have applied to the Software Freedom Conservancy > to take legal ownership of the copyright. The Jena project will become a > completely open source project, with no one dominant backer. The developers > are going to a number of companies who use Jena and these companies have an > interest in Jena's continuity. > We have set up http://openjena.org/ and have moved the project infrastructure > from the machine jena.hpl.hp.com to a new server openjena.org. Otherwise the > setup is as before. The SVN and CVS repositories remain on SourceForge. > HP legal has agreed that we can continue to use the package root > "com.hp.hpl.jena" for the codebase, and because this code is used by > strategic partners of HP, e.g. Oracle, HP has an interest in the continuity. > We also want to minimise the disruption to our users. > However, this makes it hard to rigorously prove that we control the group and > artifact names with the consent of HP as domain name owner. If it would > help, I can provide confirmation from a manager with HP. Please email my HP > address andy.seabo...@hp.com and I will get a management response from an HP > address. > My JIRA account address is currently still set to andy.seabo...@hp.com and > that email address will work until the end of this month. I can be contacted > on andy.seabo...@gmail.com during this changeover - this is the contact entry > in the CVS entry. > The public Maven ssh key has been added to the > ~mavensync/.ssh/authorized_keys on the new server. > Attached: > script version > CVS version (copy of above) > Please let me know if anything is missing or if you prefer a different format > to make it easier to manage, > Thanks - Andy -- 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-2640) Please upload jgraph 5.13.0.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2640. --- Resolution: Fixed Assignee: Carlos Sanchez > Please upload jgraph 5.13.0.0 > - > > Key: MAVENUPLOAD-2640 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2640 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Andrey Razumovsky >Assignee: Carlos Sanchez > Attachments: jgraph-5.13.0.0-bundle.jar > > > Please upload jgraph 5.13.0.0 to the repo. I used "jgraph" groupId because > jgraph 5.x already exists in repo with that id, but an older version. 5.13 is > required because its license now became BSD, so we can use it here at Apache > Cayenne -- 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-2634) upload new release 1.15 to org.mentaframework
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2634. --- Resolution: Fixed Assignee: Carlos Sanchez this was already in the server > upload new release 1.15 to org.mentaframework > - > > Key: MAVENUPLOAD-2634 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2634 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Fernando Boaglio >Assignee: Carlos Sanchez > > The Mentawai goal is to be a simple, flexible, joyful and productive Java web > framework. > This is a new release with a lot of improvements . > TIA -- 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-2164) Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199140#action_199140 ] Carlos Sanchez commented on MAVENUPLOAD-2164: - I dont know what do you mean, your current settings are "de.huxhorn.lilith","mavens...@web.sourceforge.net:/home/groups/l/li/lilith/htdocs/repository","rsync_ssh","Joern Huxhorn","huxh...@sf.net",, "de.huxhorn.sulky","mavens...@web.sourceforge.net:/home/groups/s/su/sulky/htdocs/repository","rsync_ssh","Joern Huxhorn","huxh...@sf.net",, when SF changed the server we changed it for everybody are you having issues with the sync? note that seems to be an outage right now with SF, check the repo-maintainers mailing list > Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith > --- > > Key: MAVENUPLOAD-2164 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2164 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Joern Huxhorn >Assignee: Carlos Sanchez > > "de.huxhorn.sulky","mavens...@shell.sourceforge.net:/home/groups/s/su/sulky/htdocs/repository",,"rsync_ssh","Joern > Huxhorn","huxh...@sf.net",, > "de.huxhorn.lilith","mavens...@shell.sourceforge.net:/home/groups/l/li/lilith/htdocs/repository",,"rsync_ssh","Joern > Huxhorn","huxh...@sf.net",, > This request is actually about two projects, sulky and lilith. > I added both URLs - as project and contributor URL. > I sincerely hope that I've done everything correctly since this is my very > first submission to the central maven repository. > I own the domain huxhorn.de as you can verify on http://www.denic.de > Therefore I also own sulky.huxhorn.de as well as lilith.huxhorn.de > I'm also the sole developer registered in the respective sourceforge projects > http://sf.net/projects/sulky > and > http://sf.net/projects/lilith > Since this form *requires* an upload bundle URL I entered a URL to the comma > separated sync file... > Please let me know if everything is OK or if somethings still wrong/missing. > Thank you. -- 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-2615) rsync_ssh request for svenson and jcouchdb
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2615. --- Resolution: Incomplete Assignee: Carlos Sanchez > rsync_ssh request for svenson and jcouchdb > -- > > Key: MAVENUPLOAD-2615 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2615 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Sven Helmberger >Assignee: Carlos Sanchez > > "com.google.code.svenson","mvnrs...@fforw.de:/home/mvnrsync/m2repo/releases","rsync_ssh","Sven > Helmberger","i...@fforw.de" > "com.google.code.jcouchdb","mvnrs...@fforw.de:/home/mvnrsync/m2repo/releases","rsync_ssh","Sven > Helmberger","i...@fforw.de" -- 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: (MNG-4465) [regression] can't run mvn help:effective-settings when offline
[
http://jira.codehaus.org/browse/MNG-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4465.
--
Resolution: Fixed
Fix Version/s: 3.0-alpha-6
Assignee: Benjamin Bentmann
Fixed in [r883510|http://svn.apache.org/viewvc?view=revision&revision=883510].
> [regression] can't run mvn help:effective-settings when offline
> ---
>
> Key: MNG-4465
> URL: http://jira.codehaus.org/browse/MNG-4465
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 3.0-alpha-4
> Environment: Vista, JDK 1.6.0_12,
>Reporter: Fred Bricon
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-6
>
>
> When no internet access is available, certain commands fail with an error.
> {code}
> >mvn help:effective-settings -X -e
> Apache Maven 3.0-alpha-4 (r835944; 2009-11-13 19:06:31+0100)
> Java version: 1.6.0_12
> Java home: D:\Dev\Java\jdk1.6.0_12\jre
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows"
> [INFO] Error stacktraces are turned on.
> [DEBUG] Reading user settings from C:\Users\fbricon\.m2\settings.xml
> [DEBUG] Reading global settings from
> D:\Dev\maven\apache-maven-3.0-alpha-4\conf\settings.xml
> [DEBUG] Using local repository at D:\Dev\maven\repository
> [INFO] Scanning for projects...
> [DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1:
> (none)
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml
> [WARNING] Failed to retrieve org/apache/maven/plugins/maven-metadata.xml:
> Error transferring artifact.
> org.apache.maven.repository.ArtifactTransferFailedException: Error
> transferring artifact.
> at
> org.apache.maven.repository.legacy.LegacyRepositorySystem.retrieve(LegacyRepositorySystem.java:597)
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolveFromRepository(DefaultPluginPrefixResolver.java:175)
> at
> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:75)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findPluginForPrefix(DefaultLifecycleExecutor.java:1763)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1507)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateTaskSegments(DefaultLifecycleExecutor.java:828)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateProjectBuilds(DefaultLifecycleExecutor.java:718)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:236)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:239)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:102)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:421)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:156)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
> 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:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring
> file: repo1.maven.org
> at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:143)
> at
> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
> at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
> at
> org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:310)
> at
> org.apache.maven.repository.legacy.LegacyRepositorySystem.retrieve(LegacyRepositorySystem.java:591)
> ... 20 more
> Caused by: java.net.UnknownHostException: repo1.maven.org
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:519)
> at java.net.Socket.connect(Socket.java:469)
> at sun.net.NetworkClient.doConnect(NetworkCli
[jira] Closed: (MAVENUPLOAD-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2572. --- Resolution: Incomplete ERROR 404: Not Found > upload new version 0.8.90 of tango-icon-theme, note license and groupId have > changed > > > Key: MAVENUPLOAD-2572 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Heuer >Assignee: Carlos Sanchez > > The Tango Desktop Project exists to help create a consistent graphical user > interface experience for free and Open Source software. > The Tango icon theme is a basic set of desktop icons that follow the style > guidelines. The set has been created as a proof of concept for the style, but > works rather well as a replacement for the base theme under GNOME and KDE. -- 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-2350) JCaptcha 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199137#action_199137 ] Carlos Sanchez commented on MAVENUPLOAD-2350: - is it available for the source project somewhere? > JCaptcha 1.0 > > > Key: MAVENUPLOAD-2350 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2350 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Antoine Véret > > "com.octo.captcha","mavens...@web.sourceforge.net:/home/groups/j/jc/jcaptcha/maven-repo","rsync_ssh","Antoine > Veret","ave...@octo.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-2654) Please sync SureLogic Promises
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2654. --- Resolution: Fixed Assignee: Carlos Sanchez > Please sync SureLogic Promises > -- > > Key: MAVENUPLOAD-2654 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2654 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Nathan Boy >Assignee: Carlos Sanchez > > "com.surelogic","rs...@surelogic.com:/home/rsync/m2repo","rsync_ssh","Nathan > Boy","nathan@surelogic.com" > Please sync the promises project listed above. The proof of domain ownership > is that the groupId matches the domain name. Thank you for your time. -- 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-4465) [regression] can't run mvn help:effective-settings when offline
[regression] can't run mvn help:effective-settings when offline
---
Key: MNG-4465
URL: http://jira.codehaus.org/browse/MNG-4465
Project: Maven 2
Issue Type: Bug
Affects Versions: 3.0-alpha-4
Environment: Vista, JDK 1.6.0_12,
Reporter: Fred Bricon
When no internet access is available, certain commands fail with an error.
{code}
>mvn help:effective-settings -X -e
Apache Maven 3.0-alpha-4 (r835944; 2009-11-13 19:06:31+0100)
Java version: 1.6.0_12
Java home: D:\Dev\Java\jdk1.6.0_12\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading user settings from C:\Users\fbricon\.m2\settings.xml
[DEBUG] Reading global settings from
D:\Dev\maven\apache-maven-3.0-alpha-4\conf\settings.xml
[DEBUG] Using local repository at D:\Dev\maven\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1:
(none)
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml
[WARNING] Failed to retrieve org/apache/maven/plugins/maven-metadata.xml: Error
transferring artifact.
org.apache.maven.repository.ArtifactTransferFailedException: Error transferring
artifact.
at
org.apache.maven.repository.legacy.LegacyRepositorySystem.retrieve(LegacyRepositorySystem.java:597)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolveFromRepository(DefaultPluginPrefixResolver.java:175)
at
org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:75)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findPluginForPrefix(DefaultLifecycleExecutor.java:1763)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1507)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateTaskSegments(DefaultLifecycleExecutor.java:828)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateProjectBuilds(DefaultLifecycleExecutor.java:718)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:236)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:239)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:102)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:421)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:156)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
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:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring
file: repo1.maven.org
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:143)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:310)
at
org.apache.maven.repository.legacy.LegacyRepositorySystem.retrieve(LegacyRepositorySystem.java:591)
... 20 more
Caused by: java.net.UnknownHostException: repo1.maven.org
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:837)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:77
[jira] Created: (MNG-4464) Improve handling of relative paths with backslashes
Improve handling of relative paths with backslashes
---
Key: MNG-4464
URL: http://jira.codehaus.org/browse/MNG-4464
Project: Maven 2
Issue Type: Improvement
Components: POM
Affects Versions: 3.0-alpha-4, 2.2.1
Environment: Unix, Mac
Reporter: Benjamin Bentmann
Priority: Minor
Consider this snippet:
{code:xml}
..\pom.xml
{code}
Note in particular the backslash used in the path. While this path will be
properly resolved on a Windows box, it will fail to resolve the local parent on
a Unix/Mac box (as the backslash is not a separator but escape character here).
This applies to other paths in the POM as well.
For platform-independent behavior, we should either encourage the user to use
forward slashes (by means of validation warnings/errors) or have Maven convert
the paths internally.
--
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] Issue Comment Edited: (MNG-3902) Remove visibility MavenProjectBuilder#buildStandaloneSuperProject
[ http://jira.codehaus.org/browse/MNG-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199101#action_199101 ] Benjamin Bentmann edited comment on MNG-3902 at 11/23/09 11:46 AM: --- Done in [r883430|http://svn.apache.org/viewvc?view=revision&revision=883430]. To avoid code complexity due to multiple code paths, the session will still use a stub project to carry around the information (repos, properties) from external profiles during POM-less execution. However, the project builder only supports this implementation detail via general purpose method that allows to build projects from some ModelSource. was (Author: bentmann): Done in [r|http://svn.apache.org/viewvc?view=revision&revision=883430]. To avoid code complexity due to multiple code paths, the session will still use a stub project to carry around the information (repos, properties) from external profiles during POM-less execution. However, the project builder only supports this implementation detail via general purpose method that allows to build projects from some ModelSource. > Remove visibility MavenProjectBuilder#buildStandaloneSuperProject > - > > Key: MNG-3902 > URL: http://jira.codehaus.org/browse/MNG-3902 > Project: Maven 2 > Issue Type: Task >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-6 > > > This method does not need to be exposed beyond the project building code. > It's used currently in two places: > 1) To provide a default model when you execute a goal that has no POM. Here > we have to deal gracefully without its presence because there may actually be > times we need to know when there is no POM available. The null pattern here > cause the exposure of this method and propagated lots of internal logic that > can no longer differentiate when a project is present or not. > 2) To get the default remote repositories. These should be placed somewhere > else as simple values so that we don't have to invoke such a big piece of > machinery just to extract those values. > Need to find all the plugins that may rely on this method, as almost every > method in the project builder is being misused in one plugin or another. -- 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: (MNG-3902) Remove visibility MavenProjectBuilder#buildStandaloneSuperProject
[ http://jira.codehaus.org/browse/MNG-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3902. -- Resolution: Fixed Assignee: Benjamin Bentmann Done in [r|http://svn.apache.org/viewvc?view=revision&revision=883430]. To avoid code complexity due to multiple code paths, the session will still use a stub project to carry around the information (repos, properties) from external profiles during POM-less execution. However, the project builder only supports this implementation detail via general purpose method that allows to build projects from some ModelSource. > Remove visibility MavenProjectBuilder#buildStandaloneSuperProject > - > > Key: MNG-3902 > URL: http://jira.codehaus.org/browse/MNG-3902 > Project: Maven 2 > Issue Type: Task >Affects Versions: 3.0-alpha-1 >Reporter: Jason van Zyl >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-6 > > > This method does not need to be exposed beyond the project building code. > It's used currently in two places: > 1) To provide a default model when you execute a goal that has no POM. Here > we have to deal gracefully without its presence because there may actually be > times we need to know when there is no POM available. The null pattern here > cause the exposure of this method and propagated lots of internal logic that > can no longer differentiate when a project is present or not. > 2) To get the default remote repositories. These should be placed somewhere > else as simple values so that we don't have to invoke such a big piece of > machinery just to extract those values. > Need to find all the plugins that may rely on this method, as almost every > method in the project builder is being misused in one plugin or another. -- 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-4463) Version ranges cannot be used for artifacts with 'import' scope
Version ranges cannot be used for artifacts with 'import' scope
---
Key: MNG-4463
URL: http://jira.codehaus.org/browse/MNG-4463
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.2.1
Environment: Maven 2.2.1
Reporter: Rob ten Hove
Version ranges cannot be used for artifacts with {{import}} scope. If a version
range is used for such an artifact, Maven cannot find it. Looking at the
console output shows that it takes the version range as the version, without
resolving it:
{noformat}Downloading:
http://some-repo/group/artifact/[1.0.0,2.0.0)/artifact-[1.0.0,2.0.0).pom{noformat}
This is the POM snippet:
{code:xml}
group
artifact
[1.0.0,2.0.0)
pom
import
{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] Commented: (MPIR-178) some reports have inconsistent line ending style
[
http://jira.codehaus.org/browse/MPIR-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199072#action_199072
]
Jerome Lacoste commented on MPIR-178:
-
First problem is in
./src/main/java/org/apache/maven/report/projectinfo/TeamListReport.java
public void renderBody()
{
(hardcoded \n)
See also
src/main/java/org/apache/maven/report/projectinfo/dependencies/renderer/DependenciesRenderer.java
with the hardcoded JAVASCRIPT instance
As for the dependency description:
See
private void printDescriptionsAndURLs( DependencyNode node, String uid )
but there I am not sure if the sink should be responsible for converting the \n
or if the input should be sanitized before being sent as a parameter.
> some reports have inconsistent line ending style
>
>
> Key: MPIR-178
> URL: http://jira.codehaus.org/browse/MPIR-178
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies, project-team
>Affects Versions: 2.1.2
> Environment: Windows
>Reporter: Oleg Estekhin
>Priority: Minor
>
> Some of the reports generated by the plugin have inconsistent line ending
> style. I have marked dependency and team-list components as affected by
> probably other components can produce inconsistent line endings too.
> I am working on Windows so it is (somewhat) expected that files generated by
> the plugin will have the CRLF line ending, but some files will have a mixed
> line ending style due to different reasons.
> The plugin should enforce consistent line ending style in the output files.
> It is possible that this issue is not caused by the plugin itself but
> "inherited" from some of its dependencies that handle generic maven reporting
> functionality, in this case please move the issue to the appropriate maven
> component.
> Examples:
> *team-list.html*
> The following code fragment near the end of the file seems to always have the
> LF line endings:
> {code}
>
> function offsetDate(id, offset) {
> var now = new Date();
> var nowTime = now.getTime();
> var localOffset = now.getTimezoneOffset();
> var developerTime = nowTime + ( offset * 60 * 60 * 1000 )+ ( localOffset
> * 60 * 1000 );
> var developerDate = new Date(developerTime);
> document.getElementById(id).innerHTML = developerDate;
> }
> function init(){
> }
> window.onLoad = init();
>
> {code}
> This code is probably copied to the resulting report page from some string
> literal with hard-coded line ending.
> *dependencies.html*
> The dependency report contains a dependency tree that has an "I" icon that
> unhides a description of a particular dependency. The description text is
> obtained from somewhere (the dependency pom?) and copied to the
> dependencies.html as is, including its line ending style.
> For example, org.antlr:stringtemplate:jar:3.2 and antlr:antlr:jar:2.7.7
> dependencies have a description that uses LF line endings. When these
> artifacts are required either directly or indirectly then the project's
> dependencies.html will contain both CRLF for generated code and LF for
> copy-pasted descriptions.
> Check the http://maven-svn-wagon.googlecode.com/svn/site/dependencies.html,
> lines 450-464 for the specific example.
--
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-2157) Properties defined in top-level profiles.xml do no propagate to child modules
[
http://jira.codehaus.org/browse/MNG-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199071#action_199071
]
Paul Benedict commented on MNG-2157:
Since profiles.xml is not supported in Maven 3, I do not think this issue will
make further progress.
> Properties defined in top-level profiles.xml do no propagate to child modules
> -
>
> Key: MNG-2157
> URL: http://jira.codehaus.org/browse/MNG-2157
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.2
>Reporter: Jason Dillon
>Priority: Blocker
> Fix For: 2.2.x
>
>
> I have a multi-module build, and at the top-level I have a profile called
> 'release-environment', which is activated by -Denv=release.
> I need the local release build to use different values for JDBC configuration
> to run integration tests, and defined them in a profiles.xml:
> {code}
>
>
>
>
> local-release-environment
>
>
> env
> release
>
>
>
>
> mif_jason
> mif_jason
> MIF_JASON
>
>
>
>
>
> {code}
> My project looks like:
> pom.xml
> merchant/pom.xml
> merchant/core/pom.xml
> merchant/services/pom.xml
> If i put profiles.xml as a peer to pom.xml and run {{mvn clean install
> -Denv=release}} from the top-level, I get errors because the properties are
> not propagated to the merchant/core/pom.xml module.
> If I put profiles.xml as a peer to merchant/core/pom.xml and run {{mvn clean
> install -Denv=release}}, then it works as expected... properties are set as
> they are defined in profiles.xml.
> But, this is not manageable, as I need to set some properties for all of the
> modules in a multi-module build... But I don't want to use those properties
> for all Maven2 projects, so I can not really put it into ~/.m2/settings.xml
> I had expected that a top-level profiles.xml would work, but it does not. Is
> this by design, is there another recommend way to provide per-top-level
> multi-module project configuration on a local user basis (ie. no pom.xml
> modifications)?
--
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-2672) jcifs-1.3.12 upload request
jcifs-1.3.12 upload request --- Key: MAVENUPLOAD-2672 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2672 Project: Maven Upload Requests Issue Type: Wish Reporter: Michael Böckling Attachments: jcifs-1.3.12-bundle.jar Latest jcifs release. POM taken from previous release: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/samba/jcifs/jcifs/1.2.19/jcifs-1.2.19.pom This is the official build, I only added sources. -- 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: (MPIR-178) some reports have inconsistent line ending style
some reports have inconsistent line ending style
Key: MPIR-178
URL: http://jira.codehaus.org/browse/MPIR-178
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: dependencies, project-team
Affects Versions: 2.1.2
Environment: Windows
Reporter: Oleg Estekhin
Priority: Minor
Some of the reports generated by the plugin have inconsistent line ending
style. I have marked dependency and team-list components as affected by
probably other components can produce inconsistent line endings too.
I am working on Windows so it is (somewhat) expected that files generated by
the plugin will have the CRLF line ending, but some files will have a mixed
line ending style due to different reasons.
The plugin should enforce consistent line ending style in the output files. It
is possible that this issue is not caused by the plugin itself but "inherited"
from some of its dependencies that handle generic maven reporting
functionality, in this case please move the issue to the appropriate maven
component.
Examples:
*team-list.html*
The following code fragment near the end of the file seems to always have the
LF line endings:
{code}
function offsetDate(id, offset) {
var now = new Date();
var nowTime = now.getTime();
var localOffset = now.getTimezoneOffset();
var developerTime = nowTime + ( offset * 60 * 60 * 1000 )+ ( localOffset *
60 * 1000 );
var developerDate = new Date(developerTime);
document.getElementById(id).innerHTML = developerDate;
}
function init(){
}
window.onLoad = init();
{code}
This code is probably copied to the resulting report page from some string
literal with hard-coded line ending.
*dependencies.html*
The dependency report contains a dependency tree that has an "I" icon that
unhides a description of a particular dependency. The description text is
obtained from somewhere (the dependency pom?) and copied to the
dependencies.html as is, including its line ending style.
For example, org.antlr:stringtemplate:jar:3.2 and antlr:antlr:jar:2.7.7
dependencies have a description that uses LF line endings. When these artifacts
are required either directly or indirectly then the project's dependencies.html
will contain both CRLF for generated code and LF for copy-pasted descriptions.
Check the http://maven-svn-wagon.googlecode.com/svn/site/dependencies.html,
lines 450-464 for the specific example.
--
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-3954) Remove the RuntimeInfo required in the setting.mdo
[
http://jira.codehaus.org/browse/MNG-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3954:
---
Fix Version/s: (was: 3.0-alpha-5)
3.x
The {{RuntimeInfo}} related code in {{Settings}} has been deprecated but will
need to stay around for some time due to backward-compat.
> Remove the RuntimeInfo required in the setting.mdo
> --
>
> Key: MNG-3954
> URL: http://jira.codehaus.org/browse/MNG-3954
> Project: Maven 2
> Issue Type: Task
>Reporter: Jason van Zyl
>Assignee: Jason van Zyl
> Fix For: 3.x
>
>
> This addition to the code segments was required to make the release plugin
> work. Until plugins are refactored not to require the direct use of settings
> we will need to keep this around.
--
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-3782) Variable substition not performed in transitive dependency using value from active profile
[ http://jira.codehaus.org/browse/MNG-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3782: --- Fix Version/s: (was: 3.0-alpha-5) 3.x > Variable substition not performed in transitive dependency using value from > active profile > -- > > Key: MNG-3782 > URL: http://jira.codehaus.org/browse/MNG-3782 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0-alpha-1 > Environment: Java version: 1.6.0_07 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Robert Varttinen > Fix For: 3.x > > Attachments: build.log, example.zip, MavenCli.java, > MyEclipseArtifactResolver.zip, settings.xml > > > When invoking the 'mvn compile' command and a profile is active, defined in > settings.xml, a variable substitution is not performed in a transitive > dependency. > In the example provided the project to be built, C, depends on B which in its > turn depends on A. The versions of B and A to be used are defined in a > profile, the POM-files defines a variable indicating the versions. The > profile in question is defined in the settings.xml and is always active > (check with command 'mvn help:active-profiles'). The results of project A and > B are successfully built and installed in the local repository. > Invoking a build for project C using a command line parameter indicating, > 'mvn compile -Dparentversion=0.0.1-SNAPSHOT, the versions render a successful > build. The transitive dependency is resolved correctly. > This problem is also visible in Eclipse, m2eclipse, as the project C in the > example provided, does not build (error indication). The example provided > includes Eclipse projects displaying this (version 0.9.7.20081001-2217 of the > Eclipse plugin is used). > The settings.xml and a build log are provided as attachments to this 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: (MNG-2157) Properties defined in top-level profiles.xml do no propagate to child modules
[
http://jira.codehaus.org/browse/MNG-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199041#action_199041
]
Dimo Velev commented on MNG-2157:
-
Are you planning on ever fixing this issue? It has been around for over 3
years...
> Properties defined in top-level profiles.xml do no propagate to child modules
> -
>
> Key: MNG-2157
> URL: http://jira.codehaus.org/browse/MNG-2157
> Project: Maven 2
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.2
>Reporter: Jason Dillon
>Priority: Blocker
> Fix For: 2.2.x
>
>
> I have a multi-module build, and at the top-level I have a profile called
> 'release-environment', which is activated by -Denv=release.
> I need the local release build to use different values for JDBC configuration
> to run integration tests, and defined them in a profiles.xml:
> {code}
>
>
>
>
> local-release-environment
>
>
> env
> release
>
>
>
>
> mif_jason
> mif_jason
> MIF_JASON
>
>
>
>
>
> {code}
> My project looks like:
> pom.xml
> merchant/pom.xml
> merchant/core/pom.xml
> merchant/services/pom.xml
> If i put profiles.xml as a peer to pom.xml and run {{mvn clean install
> -Denv=release}} from the top-level, I get errors because the properties are
> not propagated to the merchant/core/pom.xml module.
> If I put profiles.xml as a peer to merchant/core/pom.xml and run {{mvn clean
> install -Denv=release}}, then it works as expected... properties are set as
> they are defined in profiles.xml.
> But, this is not manageable, as I need to set some properties for all of the
> modules in a multi-module build... But I don't want to use those properties
> for all Maven2 projects, so I can not really put it into ~/.m2/settings.xml
> I had expected that a top-level profiles.xml would work, but it does not. Is
> this by design, is there another recommend way to provide per-top-level
> multi-module project configuration on a local user basis (ie. no pom.xml
> modifications)?
--
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
