[jira] Commented: (MWAR-165) Finiky filter include expressions to filter web.xml
[ http://jira.codehaus.org/browse/MWAR-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144622#action_144622 ] Stephane Nicoll commented on MWAR-165: -- Mmm. And it is specific to WEB-INF or any directory? > Finiky filter include expressions to filter web.xml > > > Key: MWAR-165 > URL: http://jira.codehaus.org/browse/MWAR-165 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.1-alpha-1 > Environment: Ubuntu 8.04 Linux, JDK 1.6_07 >Reporter: Alex Karasulu > > Include expressions which directly reference the WEB-INF in tag > does not match the web.xml file to filter it. If you go one step up and then > wild card down for XML files it works. For example this did not work: > src/main/webapp/WEB-INF > > web.xml > > The following include pattern variations do not work either: >*.xml >**/*.xml >*/*.xml >*/web.xml >**/web.xml > But this does work: > src/main/webapp > > **/web.xml > > as well as **/*.xml etc. -- 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-2171) Please synchronize for apithefire-0.1.2
Please synchronize for apithefire-0.1.2 --- Key: MAVENUPLOAD-2171 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2171 Project: Maven Upload Requests Issue Type: Task Reporter: Chew Boon Aik "org.apithefire","[EMAIL PROTECTED]:/var/www/apithefire.org/m2repo","rsync_ssh","Chew Boon Aik","[EMAIL PROTECTED]",, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-396) git provider implements scm update
[ http://jira.codehaus.org/browse/SCM-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144628#action_144628 ] Olivier Lamy commented on SCM-396: -- partially implemented in rev 684464. TODO finish correct implementation of ScmFileStatus. > git provider implements scm update > --- > > Key: SCM-396 > URL: http://jira.codehaus.org/browse/SCM-396 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-git >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1 > > -- 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: (MPLUGIN-132) Don't encourage users to use "mvn -up" to update plugins
[
http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144630#action_144630
]
Vincent Siveton commented on MPLUGIN-132:
-
Fixed in r684473. Could you update the German bundle?
> Don't encourage users to use "mvn -up" to update plugins
>
>
> Key: MPLUGIN-132
> URL: http://jira.codehaus.org/browse/MPLUGIN-132
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 2.4.2
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.4.3
>
>
> Originally reported by Wendy on IRC:
> {noformat}
> 5:42 PM wsmoak bentmann: where does
> http://maven.apache.org/plugins/maven-war-plugin-2.1-alpha-2/plugin-info.html
> come from?
> 5:42 PM wsmoak it says to run 'mvn -up' which isn't going to work in 2.0.9+
> {noformat}
> More precisely, the generated "Plugin Documentation" says
> {noformat}
> You could run 'mvn -up' to get the latest version of this plugin
> {noformat}
> This only works for RELEASE/LATEST versions, which is now considered bad
> practice and has already been disabled for common plugins by locking them
> down in the super POM. Hence, we should update the documentation and remove
> this suggestion. The one and only way to get a particular plugin version is
> to explicitly specify it in the POM.
> As Vincent further pointed out, this needs also to be addressed in the
> announcment mail template given in [Releasing A Maven
> Project|http://maven.apache.org/developers/release/releasing.html].
--
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: (MPLUGIN-132) Don't encourage users to use "mvn -up" to update plugins
[
http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MPLUGIN-132.
---
Assignee: Vincent Siveton
Resolution: Fixed
Thanks!
> Don't encourage users to use "mvn -up" to update plugins
>
>
> Key: MPLUGIN-132
> URL: http://jira.codehaus.org/browse/MPLUGIN-132
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 2.4.2
>Reporter: Benjamin Bentmann
>Assignee: Vincent Siveton
>Priority: Minor
> Fix For: 2.4.3
>
>
> Originally reported by Wendy on IRC:
> {noformat}
> 5:42 PM wsmoak bentmann: where does
> http://maven.apache.org/plugins/maven-war-plugin-2.1-alpha-2/plugin-info.html
> come from?
> 5:42 PM wsmoak it says to run 'mvn -up' which isn't going to work in 2.0.9+
> {noformat}
> More precisely, the generated "Plugin Documentation" says
> {noformat}
> You could run 'mvn -up' to get the latest version of this plugin
> {noformat}
> This only works for RELEASE/LATEST versions, which is now considered bad
> practice and has already been disabled for common plugins by locking them
> down in the super POM. Hence, we should update the documentation and remove
> this suggestion. The one and only way to get a particular plugin version is
> to explicitly specify it in the POM.
> As Vincent further pointed out, this needs also to be addressed in the
> announcment mail template given in [Releasing A Maven
> Project|http://maven.apache.org/developers/release/releasing.html].
--
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: (MPLUGIN-132) Don't encourage users to use "mvn -up" to update plugins
[
http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144632#action_144632
]
Benjamin Bentmann commented on MPLUGIN-132:
---
Updated German bundle in
[r684476|http://svn.apache.org/viewvc?view=rev&revision=684476], feel free to
close Vincent.
> Don't encourage users to use "mvn -up" to update plugins
>
>
> Key: MPLUGIN-132
> URL: http://jira.codehaus.org/browse/MPLUGIN-132
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
>Affects Versions: 2.4.2
>Reporter: Benjamin Bentmann
>Priority: Minor
> Fix For: 2.4.3
>
>
> Originally reported by Wendy on IRC:
> {noformat}
> 5:42 PM wsmoak bentmann: where does
> http://maven.apache.org/plugins/maven-war-plugin-2.1-alpha-2/plugin-info.html
> come from?
> 5:42 PM wsmoak it says to run 'mvn -up' which isn't going to work in 2.0.9+
> {noformat}
> More precisely, the generated "Plugin Documentation" says
> {noformat}
> You could run 'mvn -up' to get the latest version of this plugin
> {noformat}
> This only works for RELEASE/LATEST versions, which is now considered bad
> practice and has already been disabled for common plugins by locking them
> down in the super POM. Hence, we should update the documentation and remove
> this suggestion. The one and only way to get a particular plugin version is
> to explicitly specify it in the POM.
> As Vincent further pointed out, this needs also to be addressed in the
> announcment mail template given in [Releasing A Maven
> Project|http://maven.apache.org/developers/release/releasing.html].
--
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-2028) Sync Compass maven repository with the central maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144637#action_144637 ] Carlos Sanchez commented on MAVENUPLOAD-2028: - ssh [EMAIL PROTECTED] asks for password > Sync Compass maven repository with the central maven repository > --- > > Key: MAVENUPLOAD-2028 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2028 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Shay Banon >Assignee: Carlos Sanchez > > "org.compass-project","rsync://repo.compass-project.org","rsync","Shay > Banon","[EMAIL PROTECTED]",, -- 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-2154) upload maven-ckjm-plugin please
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2154. --- Assignee: Carlos Sanchez Resolution: Fixed > upload maven-ckjm-plugin please > --- > > Key: MAVENUPLOAD-2154 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2154 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Nicolas Dordet >Assignee: Carlos Sanchez > > "net.sourceforge.ckjm","[EMAIL > PROTECTED]:/home/groups/c/ck/ckjm/htdocs/m2repo","rsync_ssh","Nicolas > Dordet","[EMAIL PROTECTED]",, -- 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-2153) Please sync JODConverter
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2153. --- Assignee: Carlos Sanchez Resolution: Fixed > Please sync JODConverter > > > Key: MAVENUPLOAD-2153 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2153 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Mirko Nasato >Assignee: Carlos Sanchez > > "org.openoffice","[EMAIL > PROTECTED]:/home/groups/j/jo/jodconverter/maven2","rsync_ssh","Mirko > Nasato","[EMAIL PROTECTED]",, > "net.sf.jodconverter","[EMAIL > PROTECTED]:/home/groups/j/jo/jodconverter/maven2","rsync_ssh","Mirko > Nasato","[EMAIL PROTECTED]",, > Note: "org.openoffice" is for 4 JARs included in the OpenOffice.org > distribution that are required by JODConverter. While I obviously don't own > the openoffice.org domain, I've been doing those Maven releases for a while > with permission from the OOo team: > http://qa.openoffice.org/issues/show_bug.cgi?id=71358 -- 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-2157) Sync with org.jlibrary's repository to put org.jlibrary to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2157. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync with org.jlibrary's repository to put org.jlibrary to the central > repository > - > > Key: MAVENUPLOAD-2157 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2157 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Roman Puchkovskiy >Assignee: Carlos Sanchez > > "org.jlibrary","[EMAIL > PROTECTED]:/home/groups/j/jl/jlibrary/htdocs/m2repo","rsync_ssh","Roman > Puchkovskiy","[EMAIL PROTECTED]",, > The whois for jlibrary.org domain may be found here: > http://whois.domaintools.com/jlibrary.org > It proves that Martin Perez controls the jlibrary.org domain. > This (http://sourceforge.net/project/memberlist.php?group_id=95837) proves > that Martin Perez is the Project Manager of the jLibrary project and I (Roman > Puchkovskiy) is one of jLibrary's developers. -- 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-2158) Sync'ing BlueCove with repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2158. --- Assignee: Carlos Sanchez Resolution: Fixed > Sync'ing BlueCove with repository > - > > Key: MAVENUPLOAD-2158 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2158 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Vlad Skarzhevskyy >Assignee: Carlos Sanchez > Attachments: m2-sync-net.sf.bluecove.sh > > > Would be nice if rsync created. > "net.sf.bluecove","[EMAIL PROTECTED]::maven2-release","rsync","Vlad > Skarzhevskyy","[EMAIL PROTECTED]",, > This is the same as for all other projects sync'ing from this build server. > (org.microemu and com.pyx4me) > The directory > http://www.pyx4me.com/maven2-release/net/sf/bluecove/bluecove/ already > contains previously published artifacts, hope this is not a problem. > The next BlueCove release would have 3 jars/modules instead of one as it used > to before, so creating rsync looks like right option. > The project is published on sf http://sourceforge.net/projects/bluecove/ so > we are going to keep old groupId net.sf.bluecove -- 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-2116) Please add MigLayout to the auto rsynced list.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2116. --- Resolution: Fixed > Please add MigLayout to the auto rsynced list. > -- > > Key: MAVENUPLOAD-2116 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Mikael Grev >Assignee: Carlos Sanchez > > "miglayout","rsync://[EMAIL PROTECTED]/maven/releases","rsync",Mikael > Grev,[EMAIL PROTECTED],, > The password is "maven". > MigLayout is a LayoutManager for Swing & SWT. It is the #1 RFE for being > added to SWT and #10 RFE for being added to the Java SDK. > I own MiGInfoCom AB which owns MigLayout. > Cheers, > Mikael Grev -- 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-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:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2164. --- Assignee: Carlos Sanchez Resolution: Fixed > 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","[EMAIL > PROTECTED]:/home/groups/s/su/sulky/htdocs/repository",,"rsync_ssh","Joern > Huxhorn","[EMAIL PROTECTED]",, > "de.huxhorn.lilith","[EMAIL > PROTECTED]:/home/groups/l/li/lilith/htdocs/repository",,"rsync_ssh","Joern > Huxhorn","[EMAIL PROTECTED]",, > 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-2163) Maven GWT plugin 1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2163. --- Assignee: Carlos Sanchez Resolution: Fixed > Maven GWT plugin 1.0 > > > Key: MAVENUPLOAD-2163 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2163 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Maxim Gordienko >Assignee: Carlos Sanchez > > "net.sf.mgp","[EMAIL > PROTECTED]:/home/groups/m/mg/mgp/htdocs/releases","rsync_ssh","Maxim > Gordienko","[EMAIL PROTECTED]",, -- 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-2167) xLightweb - repo sync job
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2167. --- Assignee: Carlos Sanchez Resolution: Fixed > xLightweb - repo sync job > - > > Key: MAVENUPLOAD-2167 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2167 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jani >Assignee: Carlos Sanchez > Attachments: xLightweb.txt > > > Hello, > please setup a repo sync job. Please see attached sync file > Thanks > Gregor -- 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-2168) xLightweb - repo sync job
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2168. --- Assignee: Carlos Sanchez Resolution: Duplicate > xLightweb - repo sync job > - > > Key: MAVENUPLOAD-2168 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2168 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jani >Assignee: Carlos Sanchez > Attachments: xLightweb.txt > > > Hello, > please setup a repo sync job. Please see attached sync file > Thanks > Gregor -- 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-2171) Please synchronize for apithefire-0.1.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2171. --- Assignee: Carlos Sanchez Resolution: Fixed > Please synchronize for apithefire-0.1.2 > --- > > Key: MAVENUPLOAD-2171 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2171 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Chew Boon Aik >Assignee: Carlos Sanchez > > "org.apithefire","[EMAIL > PROTECTED]:/var/www/apithefire.org/m2repo","rsync_ssh","Chew Boon > Aik","[EMAIL PROTECTED]",, -- 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-2159) Clean Out Incorrectly Synced Atrifacts
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144638#action_144638 ] Carlos Sanchez commented on MAVENUPLOAD-2159: - no, you need to make a list of files that should be deleted > Clean Out Incorrectly Synced Atrifacts > -- > > Key: MAVENUPLOAD-2159 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2159 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Ben Hood > > The first few times that you synced your mirror with the source rsync mirror > for com.rabbitmq, I had made a few mistakes with the packaging, so these > failed attempts are still on the main mirror. > Is there an option to run rsync with the --delete option so that the old > cruft does not build up? -- 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-2156) Mockito 1.5 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2156. --- Assignee: Carlos Sanchez Resolution: Fixed > Mockito 1.5 upload request > -- > > Key: MAVENUPLOAD-2156 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2156 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Igor Czechowski >Assignee: Carlos Sanchez > > http://mockito.googlecode.com/svn/branches/1.5/maven/mockito-core-1.5-bundle.jar > http://mockito.googlecode.com/svn/branches/1.5/maven/mockito-all-1.5-bundle.jar > http://code.google.com/p/mockito/ > http://code.google.com/u/iczechowski/ > I'm a project member in Mockito, please upload these two bundles. -- 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-2160) typica 1.3 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144639#action_144639 ] Carlos Sanchez commented on MAVENUPLOAD-2160: - The groupId should be com.google.code.typica > typica 1.3 release > -- > > Key: MAVENUPLOAD-2160 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2160 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David Kavanagh > Attachments: typica-1.3-bundle.jar > > > Several users of my library have requested that it be available via a maven > repo. This is my first attempt at submitting typica. Hopefully, I'll automate > in the future. -- 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-2155) jedit-syntax upload to Maven central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2155. --- Assignee: Carlos Sanchez Resolution: Fixed > jedit-syntax upload to Maven central repo > - > > Key: MAVENUPLOAD-2155 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2155 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Andrus Adamchik >Assignee: Carlos Sanchez > > We are using jedit-syntax package from SourceForge at Apache Cayenne, so I'd > like to upload it to the central maven repo. I assembled the bundles based on > the sourceforge 2.2.2 release and posted them here: > http://www.objectstyle.org/downloads/cayenne/maven-bundles/jedit-syntax-2.2.2-bundle.jar > http://www.objectstyle.org/downloads/cayenne/maven-bundles/jedit-syntax-2.2.2-javadoc.jar > http://www.objectstyle.org/downloads/cayenne/maven-bundles/jedit-syntax-2.2.2-sources.jar > Thanks! > Andrus Adamchik -- 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-2161) Please upload jSSLutils 0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2161. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload jSSLutils 0.4 > --- > > Key: MAVENUPLOAD-2161 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2161 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Bruno Harbulot >Assignee: Carlos Sanchez > > Hello, I'm the developer and project owner of jsslutils. Could you please > upload this project in the repository? > There is a test dependency to: > * com.googlecode.jsslutils:jsslutils-test-certificates:1.0.1 > > http://jsslutils.googlecode.com/files/jsslutils-test-certificates-1.0.1-bundle.jar > * com.googlecode.jsslutils:jsslutils-test-helpers:0.4 > > http://jsslutils.googlecode.com/files/jsslutils-test-helpers-0.4-bundle.jar > Thank you. > Bruno. -- 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-2128) Please upload Gson library to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2128. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload Gson library to the central repository > > > Key: MAVENUPLOAD-2128 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2128 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Inderjeet Singh >Assignee: Carlos Sanchez > > This package is also automatically published at the following maven > repository: > http://google-gson.googlecode.com/svn/mavenrepo/ > I (inder123 id at code.google.com)am the owner of this project ( > http://code.google.com/p/google-gson ). Please upload. > Can it be somehow synced automatically with this? I investigated somewhat > regarding ssh or rsync access to code.google.com but could not find anything. -- 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-2172) Upload oval-1.30
Upload oval-1.30 Key: MAVENUPLOAD-2172 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2172 Project: Maven Upload Requests Issue Type: Task Reporter: Sebastian T OVal is a pragmatic and extensible validation framework for any kind of Java objects (not only JavaBeans). Constraints can be configured with annotations, POJOs or XML. Custom constraints can be expressed in pure Java or by using scripting languages such as JavaScript, Groovy, BeanShell, OGNL, MVEL or Ruby. Besides simple object validation OVal implements Programming by Contract features by utilizing AspectJ based aspects. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html 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] Updated: (MASSEMBLY-345) a"ppxml attribute is required" error when making ears with the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tahchiev updated MASSEMBLY-345: - Attachment: AbstractAssemblyMojo-345.patch This is the first part of the patch. > a"ppxml attribute is required" error when making ears with the assembly plugin > -- > > Key: MASSEMBLY-345 > URL: http://jira.codehaus.org/browse/MASSEMBLY-345 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: all >Reporter: Petar Tahchiev > Attachments: AbstractAssemblyMojo-345.patch > > > So what I am doing is trying to make ears with the assembly plugin. For > instance here is my assembly descriptor: > > > src > > ear > > > > false > > ** > > > > > > But instead, I get the following exception: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive src: appxml > attribute is required > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > 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:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:368) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:136) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > ... 18 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: appxml attribute > is required > at > org.codehaus.plexus.archiver.ear.EarArchiver.initZipOutputStream(EarArchiver.java:90) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:340) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:249) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:762) > at > org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:496) > at > org.apache.maven.plugin.assembly.
[jira] Updated: (MASSEMBLY-345) a"ppxml attribute is required" error when making ears with the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tahchiev updated MASSEMBLY-345: - Attachment: AssemblyConfiguration-345.patch The second part of the patch. > a"ppxml attribute is required" error when making ears with the assembly plugin > -- > > Key: MASSEMBLY-345 > URL: http://jira.codehaus.org/browse/MASSEMBLY-345 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: all >Reporter: Petar Tahchiev > Attachments: AbstractAssemblyMojo-345.patch, > AssemblyConfiguration-345.patch, DefaultAsemblyArchiver-345.patch > > > So what I am doing is trying to make ears with the assembly plugin. For > instance here is my assembly descriptor: > > > src > > ear > > > > false > > ** > > > > > > But instead, I get the following exception: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive src: appxml > attribute is required > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > 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:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:368) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:136) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > ... 18 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: appxml attribute > is required > at > org.codehaus.plexus.archiver.ear.EarArchiver.initZipOutputStream(EarArchiver.java:90) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:340) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:249) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:762) > at > org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArch
[jira] Updated: (MASSEMBLY-345) a"ppxml attribute is required" error when making ears with the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petar Tahchiev updated MASSEMBLY-345: - Attachment: DefaultAsemblyArchiver-345.patch The third part of the patch. > a"ppxml attribute is required" error when making ears with the assembly plugin > -- > > Key: MASSEMBLY-345 > URL: http://jira.codehaus.org/browse/MASSEMBLY-345 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: all >Reporter: Petar Tahchiev > Attachments: AbstractAssemblyMojo-345.patch, > AssemblyConfiguration-345.patch, DefaultAsemblyArchiver-345.patch > > > So what I am doing is trying to make ears with the assembly plugin. For > instance here is my assembly descriptor: > > > src > > ear > > > > false > > ** > > > > > > But instead, I get the following exception: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive src: appxml > attribute is required > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > 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:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create > assembly: Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:368) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: org.apache.maven.plugin.assembly.archive.ArchiveCreationException: > Error creating assembly archive src: appxml attribute is required > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:136) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) > ... 18 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: appxml attribute > is required > at > org.codehaus.plexus.archiver.ear.EarArchiver.initZipOutputStream(EarArchiver.java:90) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:340) > at > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:249) > at > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:762) > at > org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArch
[jira] Commented: (SCM-374) maven-scm-providers-git is missing some testdata
[ http://jira.codehaus.org/browse/SCM-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144651#action_144651 ] Olivier Lamy commented on SCM-374: -- no news on that point. btw all tests pass currently in the git provider. IMHO we can close it or move it to 1.2. > maven-scm-providers-git is missing some testdata > > > Key: SCM-374 > URL: http://jira.codehaus.org/browse/SCM-374 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: linux fedora-8, git-1.5.3.3., git-1.5.4 >Reporter: Mark Struberg >Assignee: Jason van Zyl > Fix For: 1.1 > > Attachments: git-diff-testlogs.patch, > maven-scm-providers-git-testdata.patch > > > It seems that something has gone missing by moving the > maven-scm-providers-git plugin from git to SVN. > I checked out the SVN version and compared it to my git repo. > It seems that the test/resource/git/ ... /*.log files have been ignored. > This files contain the testdata for testing the various commandline output > consumers for the git executable. > The appending patch does contain all missing files plus a small change in the > way the base command is constructed. > Tests and TCK successfully passed. -- 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: (MINVOKER-50) Filter all POMs that are relevant to the forked build
Filter all POMs that are relevant to the forked build
-
Key: MINVOKER-50
URL: http://jira.codehaus.org/browse/MINVOKER-50
Project: Maven 2.x Invoker Plugin
Issue Type: New Feature
Affects Versions: 1.2
Reporter: Benjamin Bentmann
Imagine a multi module project:
{noformat}
mod2-parent/
mod1/
pom.xml
mod1-parent/
pom.xml
mod2/
pom.xml
pom.xml (aggregator of mod1 and mod2)
{noformat}
When the Invoker Plugin is configured to run the build on
{{mod2-parent/pom.xml}}, i.e. do a reactor build, none of the POMs in the sub
directories are filtered, only the reactor root POM is. This makes it hard for
those POMs to reference the artifact under test via [EMAIL PROTECTED]@}} or
similar. Possible workaround is using system properties but this is cumbersome.
My initial assumption is we could analyze the executed POM's model and
recursively follow modules/parents to locate the other POMs that will
participate in the invoked reactor build to filter these, too. This in turn
would require to
- either rewrite all models to reference the {{interpolated-pom.xml}}
- or simply retain the original file name of the POM which is of couse only
possible when cloning the projects
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-374) maven-scm-providers-git is missing some testdata
[ http://jira.codehaus.org/browse/SCM-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144652#action_144652 ] Dennis Lundberg commented on SCM-374: - Brett mentioned that he disabled some tests, so that might be the reason they pass. > maven-scm-providers-git is missing some testdata > > > Key: SCM-374 > URL: http://jira.codehaus.org/browse/SCM-374 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: linux fedora-8, git-1.5.3.3., git-1.5.4 >Reporter: Mark Struberg >Assignee: Jason van Zyl > Fix For: 1.1 > > Attachments: git-diff-testlogs.patch, > maven-scm-providers-git-testdata.patch > > > It seems that something has gone missing by moving the > maven-scm-providers-git plugin from git to SVN. > I checked out the SVN version and compared it to my git repo. > It seems that the test/resource/git/ ... /*.log files have been ignored. > This files contain the testdata for testing the various commandline output > consumers for the git executable. > The appending patch does contain all missing files plus a small change in the > way the base command is constructed. > Tests and TCK successfully passed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-374) maven-scm-providers-git is missing some testdata
[ http://jira.codehaus.org/browse/SCM-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144653#action_144653 ] Olivier Lamy commented on SCM-374: -- ok I will search :-). btw I have tested the git provider with the release plugin and all looks. Tests are in this git-hub repos : http://github.com/olamy/ One repo with a simple project, one with a project with modules. I have tested on the following os : - windows (with the windows cli). - cygwin cli. - linux (ubuntu). - mac (thanks to tcurdt for testing time). Then I have tested the update command implementation (see SCM-396) with continuum and it build too. > maven-scm-providers-git is missing some testdata > > > Key: SCM-374 > URL: http://jira.codehaus.org/browse/SCM-374 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: linux fedora-8, git-1.5.3.3., git-1.5.4 >Reporter: Mark Struberg >Assignee: Jason van Zyl > Fix For: 1.1 > > Attachments: git-diff-testlogs.patch, > maven-scm-providers-git-testdata.patch > > > It seems that something has gone missing by moving the > maven-scm-providers-git plugin from git to SVN. > I checked out the SVN version and compared it to my git repo. > It seems that the test/resource/git/ ... /*.log files have been ignored. > This files contain the testdata for testing the various commandline output > consumers for the git executable. > The appending patch does contain all missing files plus a small change in the > way the base command is constructed. > Tests and TCK successfully passed. -- 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: (SCM-374) maven-scm-providers-git is missing some testdata
[ http://jira.codehaus.org/browse/SCM-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144653#action_144653 ] olamy edited comment on SCM-374 at 8/10/08 2:28 PM: --- ok I will search :-). btw I have tested the git provider with the release plugin and all looks fine. Tests are in this git-hub repos : http://github.com/olamy/ One repo with a simple project, one with a project with modules. I have tested on the following os : - windows (with the windows cli). - cygwin cli. - linux (ubuntu). - mac (thanks to tcurdt for testing time). Then I have tested the update command implementation (see SCM-396) with continuum and it works fine too. was (Author: olamy): ok I will search :-). btw I have tested the git provider with the release plugin and all looks. Tests are in this git-hub repos : http://github.com/olamy/ One repo with a simple project, one with a project with modules. I have tested on the following os : - windows (with the windows cli). - cygwin cli. - linux (ubuntu). - mac (thanks to tcurdt for testing time). Then I have tested the update command implementation (see SCM-396) with continuum and it build too. > maven-scm-providers-git is missing some testdata > > > Key: SCM-374 > URL: http://jira.codehaus.org/browse/SCM-374 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: linux fedora-8, git-1.5.3.3., git-1.5.4 >Reporter: Mark Struberg >Assignee: Jason van Zyl > Fix For: 1.1 > > Attachments: git-diff-testlogs.patch, > maven-scm-providers-git-testdata.patch > > > It seems that something has gone missing by moving the > maven-scm-providers-git plugin from git to SVN. > I checked out the SVN version and compared it to my git repo. > It seems that the test/resource/git/ ... /*.log files have been ignored. > This files contain the testdata for testing the various commandline output > consumers for the git executable. > The appending patch does contain all missing files plus a small change in the > way the base command is constructed. > Tests and TCK successfully passed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-374) maven-scm-providers-git is missing some testdata
[ http://jira.codehaus.org/browse/SCM-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144656#action_144656 ] Olivier Lamy commented on SCM-374: -- ok here [rev 653981|http://fisheye6.atlassian.com/browse/~author=brett/maven/scm/trunk/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-git-commons/pom.xml?r1=645182&r2=653981] > maven-scm-providers-git is missing some testdata > > > Key: SCM-374 > URL: http://jira.codehaus.org/browse/SCM-374 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: linux fedora-8, git-1.5.3.3., git-1.5.4 >Reporter: Mark Struberg >Assignee: Jason van Zyl > Fix For: 1.1 > > Attachments: git-diff-testlogs.patch, > maven-scm-providers-git-testdata.patch > > > It seems that something has gone missing by moving the > maven-scm-providers-git plugin from git to SVN. > I checked out the SVN version and compared it to my git repo. > It seems that the test/resource/git/ ... /*.log files have been ignored. > This files contain the testdata for testing the various commandline output > consumers for the git executable. > The appending patch does contain all missing files plus a small change in the > way the base command is constructed. > Tests and TCK successfully passed. -- 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: (MAVENUPLOAD-2160) typica 1.3 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kavanagh updated MAVENUPLOAD-2160: Attachment: typica-1.3-bundle.jar Updated with the proper groupID > typica 1.3 release > -- > > Key: MAVENUPLOAD-2160 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2160 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: David Kavanagh > Attachments: typica-1.3-bundle.jar, typica-1.3-bundle.jar > > > Several users of my library have requested that it be available via a maven > repo. This is my first attempt at submitting typica. Hopefully, I'll automate > in the future. -- 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-374) maven-scm-providers-git is missing some testdata
[ http://jira.codehaus.org/browse/SCM-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-374. Resolution: Fixed fix in rev 684588 > maven-scm-providers-git is missing some testdata > > > Key: SCM-374 > URL: http://jira.codehaus.org/browse/SCM-374 > Project: Maven SCM > Issue Type: Bug >Affects Versions: 1.1 > Environment: linux fedora-8, git-1.5.3.3., git-1.5.4 >Reporter: Mark Struberg >Assignee: Olivier Lamy > Fix For: 1.1 > > Attachments: git-diff-testlogs.patch, > maven-scm-providers-git-testdata.patch > > > It seems that something has gone missing by moving the > maven-scm-providers-git plugin from git to SVN. > I checked out the SVN version and compared it to my git repo. > It seems that the test/resource/git/ ... /*.log files have been ignored. > This files contain the testdata for testing the various commandline output > consumers for the git executable. > The appending patch does contain all missing files plus a small change in the > way the base command is constructed. > Tests and TCK successfully passed. -- 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-396) git provider implements scm update
[ http://jira.codehaus.org/browse/SCM-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-396. Resolution: Fixed fixed in rev 684601. > git provider implements scm update > --- > > Key: SCM-396 > URL: http://jira.codehaus.org/browse/SCM-396 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-git >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.1 > > -- 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: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties
[ http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144679#action_144679 ] Brett Porter commented on SUREFIRE-511: --- why is a new field needed? Could the type of the existing one be changed? > Proposal to use java Map for surefire's systemProperties > - > > Key: SUREFIRE-511 > URL: http://jira.codehaus.org/browse/SUREFIRE-511 > Project: Maven Surefire > Issue Type: Improvement > Components: plugin >Affects Versions: 2.4.3 >Reporter: Dan Tran > Attachments: SUREFIRE-511.patch > > > There is a known problem documented at > http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html > where maven properties other than java String are not able to pass into > surefire > This is mainly because systemProperties is mapped to java Properties class. > However if we map it to java Map > the problem solves. > see > http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire > for details. > So I would like to propose that we deprecate "systemProperties" and introduce > a new one "systemPropertyVariables" to use java Map ( similar to surefire's > environmentVariables" > Thoughts? -- 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-2173) Please upload Functional Java 2.12
Please upload Functional Java 2.12 -- Key: MAVENUPLOAD-2173 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2173 Project: Maven Upload Requests Issue Type: Wish Reporter: Tom Adams http://functionaljava.org/ http://projects.workingmouse.com/public/functionaljava/tags/2.12/etc/CONTRIBUTORS I'm a contributor on this project, please upload. This bundle is also automatically published at the following maven repository: http://projects.workingmouse.com/public/functionaljava/maven/. Automatically grabbing this would be great, but it appears your central repo syncing doesn't work for HTTP URLs. -- 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: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties
[ http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144681#action_144681 ] Dan Tran commented on SUREFIRE-511: --- We cant not just switch the type, since the xml presentation in pom are different between Map and Properties. propertyName propertyValue versus propertyValue > Proposal to use java Map for surefire's systemProperties > - > > Key: SUREFIRE-511 > URL: http://jira.codehaus.org/browse/SUREFIRE-511 > Project: Maven Surefire > Issue Type: Improvement > Components: plugin >Affects Versions: 2.4.3 >Reporter: Dan Tran > Attachments: SUREFIRE-511.patch > > > There is a known problem documented at > http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html > where maven properties other than java String are not able to pass into > surefire > This is mainly because systemProperties is mapped to java Properties class. > However if we map it to java Map > the problem solves. > see > http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire > for details. > So I would like to propose that we deprecate "systemProperties" and introduce > a new one "systemPropertyVariables" to use java Map ( similar to surefire's > environmentVariables" > Thoughts? -- 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: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties
[ http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144682#action_144682 ] Brett Porter commented on SUREFIRE-511: --- right... I actually prefer the second format so it'd be a good switch, but OTOH changing it just to workaround what is probably a Maven bug (since it should know to toString() values as they are populated) feels a bit wrong. > Proposal to use java Map for surefire's systemProperties > - > > Key: SUREFIRE-511 > URL: http://jira.codehaus.org/browse/SUREFIRE-511 > Project: Maven Surefire > Issue Type: Improvement > Components: plugin >Affects Versions: 2.4.3 >Reporter: Dan Tran > Attachments: SUREFIRE-511.patch > > > There is a known problem documented at > http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html > where maven properties other than java String are not able to pass into > surefire > This is mainly because systemProperties is mapped to java Properties class. > However if we map it to java Map > the problem solves. > see > http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire > for details. > So I would like to propose that we deprecate "systemProperties" and introduce > a new one "systemPropertyVariables" to use java Map ( similar to surefire's > environmentVariables" > Thoughts? -- 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: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties
[ http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144688#action_144688 ] Dan Tran commented on SUREFIRE-511: --- Are you +1 with the switch? I think in the term, new plugin should not use Properties any way since it is too verbose, The Map format is shorter. > Proposal to use java Map for surefire's systemProperties > - > > Key: SUREFIRE-511 > URL: http://jira.codehaus.org/browse/SUREFIRE-511 > Project: Maven Surefire > Issue Type: Improvement > Components: plugin >Affects Versions: 2.4.3 >Reporter: Dan Tran > Attachments: SUREFIRE-511.patch > > > There is a known problem documented at > http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html > where maven properties other than java String are not able to pass into > surefire > This is mainly because systemProperties is mapped to java Properties class. > However if we map it to java Map > the problem solves. > see > http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire > for details. > So I would like to propose that we deprecate "systemProperties" and introduce > a new one "systemPropertyVariables" to use java Map ( similar to surefire's > environmentVariables" > Thoughts? -- 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: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties
[
http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144691#action_144691
]
Benjamin Bentmann commented on SUREFIRE-511:
We could also have a look at Plexus: {{Properties}} IS_A {{Map}} so why
shouldn't it accept the same kind of POM configuration?
> Proposal to use java Map for surefire's systemProperties
> -
>
> Key: SUREFIRE-511
> URL: http://jira.codehaus.org/browse/SUREFIRE-511
> Project: Maven Surefire
> Issue Type: Improvement
> Components: plugin
>Affects Versions: 2.4.3
>Reporter: Dan Tran
> Attachments: SUREFIRE-511.patch
>
>
> There is a known problem documented at
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
> where maven properties other than java String are not able to pass into
> surefire
> This is mainly because systemProperties is mapped to java Properties class.
> However if we map it to java Map
> the problem solves.
> see
> http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire
> for details.
> So I would like to propose that we deprecate "systemProperties" and introduce
> a new one "systemPropertyVariables" to use java Map ( similar to surefire's
> environmentVariables"
> Thoughts?
--
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: (SUREFIRE-511) Proposal to use java Map for surefire's systemProperties
[ http://jira.codehaus.org/browse/SUREFIRE-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144693#action_144693 ] Dan Tran commented on SUREFIRE-511: --- Dont think it is wise to fix Properties to accept the current Map XML presentation, since it will break lots of existing configuration, unless we make it smart enough to understand both which also mean introduceing other regression in the core IMHO > Proposal to use java Map for surefire's systemProperties > - > > Key: SUREFIRE-511 > URL: http://jira.codehaus.org/browse/SUREFIRE-511 > Project: Maven Surefire > Issue Type: Improvement > Components: plugin >Affects Versions: 2.4.3 >Reporter: Dan Tran > Attachments: SUREFIRE-511.patch > > > There is a known problem documented at > http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html > where maven properties other than java String are not able to pass into > surefire > This is mainly because systemProperties is mapped to java Properties class. > However if we map it to java Map > the problem solves. > see > http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/it/surefire > for details. > So I would like to propose that we deprecate "systemProperties" and introduce > a new one "systemPropertyVariables" to use java Map ( similar to surefire's > environmentVariables" > Thoughts? -- 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
