[jira] Commented: (MRELEASE-159) Support a pattern to generate the release tag

2009-08-12 Thread Michael Wenig (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186783#action_186783
 ] 

Michael Wenig commented on MRELEASE-159:


is it possible to integrate this patch in the version 2.0-beta-10 and release 
it?

It's a bit urgent at my current customer...

Thanks Michael

 Support a pattern to generate the release tag
 -

 Key: MRELEASE-159
 URL: http://jira.codehaus.org/browse/MRELEASE-159
 Project: Maven 2.x Release Plugin
  Issue Type: New Feature
  Components: prepare
Affects Versions: 2.0-beta-4
Reporter: Joerg Schaible
 Attachments: MRELEASE-159-PATCH-update.diff.gz, 
 MRELEASE-159-PATCH.diff.gz


 The release-plugin uses currently the pattern artifactId-version to 
 create the version tag. A configuration element would be fine to support 
 different requirements for release tags (in our case v_version, since 
 with svn the module is already part of the path).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MECLIPSE-208) Implicit dependencies are not resolved when using make-artifacts with stripQualifier=false

2009-08-12 Thread Jochen Wiedmann (JIRA)

[ 
http://jira.codehaus.org/browse/MECLIPSE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186784#action_186784
 ] 

Jochen Wiedmann commented on MECLIPSE-208:
--

Workaround: Use the -DstripQualifier=true parameter. Maps the version numbers 
from 3.5.0-vSomething to 3.5.0.


 Implicit dependencies are not resolved when using make-artifacts with 
 stripQualifier=false
 --

 Key: MECLIPSE-208
 URL: http://jira.codehaus.org/browse/MECLIPSE-208
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
  Components: PDE support
Affects Versions: 2.3
 Environment: Windows XP, Eclipse 3.3 M4
Reporter: Chad Moats
 Attachments: MECLIPSE-208-maven-eclipse-plugin.patch, 
 MECLIPSE-208-maven-eclipse-plugin.patch


 When using qualifiers with the make-artifacts goal, implict dependencies 
 cannot be resolved because they fall outside the version range used.  This 
 issue was found when trying to deploy Eclipse 3.3 M4 to my local repository 
 while retaining the qualifier.  For example, the org.eclipse.core.runtime pom 
 that is gernerated states that it depends on org.eclipse.equinox.app using 
 the range of [1.0.0,2.0.0).  The actual version number of the 
 org.eclipse.equinox.app is 1.0.0-v.  Using a qualifier means that the 
 version actually falls before the 1.0.0-2.0.0 range.  The following error is 
 logged:
 Couldn't find a version in [1.0.0-v20061208] to match range [1.0.0,2.0.0)
   org.eclipse.equinox:org.eclipse.equinox.app:jar:null

-- 
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-2552) JUnit 4.7

2009-08-12 Thread Simon Brandhof (JIRA)
JUnit 4.7
-

 Key: MAVENUPLOAD-2552
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2552
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Simon Brandhof
 Attachments: junit-4.7-bundle.jar

Please upload this new version.

-- 
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-4293) Extend Mojo API to allow resolution of both compile and runtime dependencies

2009-08-12 Thread Benjamin Bentmann (JIRA)
Extend Mojo API to allow resolution of both compile and runtime dependencies


 Key: MNG-4293
 URL: http://jira.codehaus.org/browse/MNG-4293
 Project: Maven 2
  Issue Type: Improvement
  Components: Plugin API, Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: Benjamin Bentmann
Priority: Minor


Right now, only {...@requiresdependencyresolution compile|runtime|test}} is 
supported. However, {{runtime}} is no superset of {{compile}} but plugins 
occasionally need both scopes. To better support those use cases, a new 
resolution scope {{compile+runtime}} will be introduced. See also [\[DISCUSS\] 
Extend Mojo API to allow for resolution of multiple dependency 
scopes|http://markmail.org/message/2z4vlqhxm6qb4owk]

-- 
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-4293) Extend Mojo API to allow resolution of both compile and runtime dependencies

2009-08-12 Thread Benjamin Bentmann (JIRA)

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

Benjamin Bentmann closed MNG-4293.
--

 Assignee: Benjamin Bentmann
   Resolution: Fixed
Fix Version/s: 3.0-alpha-3

Done in [r803422|http://svn.apache.org/viewvc?view=revrevision=803422].

 Extend Mojo API to allow resolution of both compile and runtime dependencies
 

 Key: MNG-4293
 URL: http://jira.codehaus.org/browse/MNG-4293
 Project: Maven 2
  Issue Type: Improvement
  Components: Plugin API, Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: Benjamin Bentmann
Assignee: Benjamin Bentmann
Priority: Minor
 Fix For: 3.0-alpha-3


 Right now, only {...@requiresdependencyresolution compile|runtime|test}} is 
 supported. However, {{runtime}} is no superset of {{compile}} but plugins 
 occasionally need both scopes. To better support those use cases, a new 
 resolution scope {{compile+runtime}} will be introduced. See also 
 [\[DISCUSS\] Extend Mojo API to allow for resolution of multiple dependency 
 scopes|http://markmail.org/message/2z4vlqhxm6qb4owk]

-- 
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: (MPDF-26) Add report generation in PDF

2009-08-12 Thread Vincent Siveton (JIRA)

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

Vincent Siveton closed MPDF-26.
---

  Assignee: Vincent Siveton
Resolution: Fixed

Restored backward compatibility with mvn 2.0.x in 
[r803437|http://svn.apache.org/viewvc?rev=803437view=rev], snapshot deployed.


 Add report generation in PDF
 

 Key: MPDF-26
 URL: http://jira.codehaus.org/browse/MPDF-26
 Project: Maven 2.x PDF Plugin
  Issue Type: Improvement
Affects Versions: 1.0
Reporter: Vincent Siveton
Assignee: Vincent Siveton
 Fix For: 1.1


 Using MavenReport#generate(org.codehaus.doxia.sink.Sink, Locale)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (MCHANGELOG-100) Bump to Doxia 1.1.1

2009-08-12 Thread Vincent Siveton (JIRA)
Bump to Doxia 1.1.1
---

 Key: MCHANGELOG-100
 URL: http://jira.codehaus.org/browse/MCHANGELOG-100
 Project: Maven 2.x Changelog Plugin
  Issue Type: Task
Affects Versions: 2.1
Reporter: Vincent Siveton




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (MCHANGELOG-99) Invalid generated HTML reports

2009-08-12 Thread Vincent Siveton (JIRA)
Invalid generated HTML reports
--

 Key: MCHANGELOG-99
 URL: http://jira.codehaus.org/browse/MCHANGELOG-99
 Project: Maven 2.x Changelog Plugin
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Vincent Siveton


Generated reports like [1] are invalids according the W3C validator

[1] http://maven.apache.org/plugins/maven-changelog-plugin/changelog.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: (MRELEASE-159) Support a pattern to generate the release tag

2009-08-12 Thread Dave Copeland (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186822#action_186822
 ] 

Dave Copeland commented on MRELEASE-159:


Michael - if you are desperate and don't want to wait, you can use it now with 
a bit of elbow grease (this is what we're doing where I work):

 # checkout the 2.0-beta-9 via 
https://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.0-beta-9 
(you need both the release manager and the release plugin, which this url will 
get you)
 # apply the patch
 # Change the {{groupId}} and {{version}} in *all three* poms (this helps you 
deploy it later)
 # build everything
 # deploy these files to your local maven repo
 # Change your poms that reference the release plugin to reference the one you 
built via the new {{groupId}} and the new {{version}}

 Support a pattern to generate the release tag
 -

 Key: MRELEASE-159
 URL: http://jira.codehaus.org/browse/MRELEASE-159
 Project: Maven 2.x Release Plugin
  Issue Type: New Feature
  Components: prepare
Affects Versions: 2.0-beta-4
Reporter: Joerg Schaible
 Attachments: MRELEASE-159-PATCH-update.diff.gz, 
 MRELEASE-159-PATCH.diff.gz


 The release-plugin uses currently the pattern artifactId-version to 
 create the version tag. A configuration element would be fine to support 
 different requirements for release tags (in our case v_version, since 
 with svn the module is already part of the path).

-- 
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: (MRELEASE-159) Support a pattern to generate the release tag

2009-08-12 Thread Dave Copeland (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186822#action_186822
 ] 

Dave Copeland edited comment on MRELEASE-159 at 8/12/09 8:35 AM:
-

Michael - if you are desperate and don't want to wait, you can use it now with 
a bit of elbow grease (this is what we're doing where I work):

 # checkout the 2.0-beta-9 via 
https://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.0-beta-9 
(you need both the release manager and the release plugin, which this url will 
get you)
 # apply the patch (the latest of the two; I don't have perms to delete the bad 
one)
 # Change the {{groupId}} and {{version}} in *all three* poms (this helps you 
deploy it later)
 # build everything
 # deploy these files to your local maven repo
 # Change your poms that reference the release plugin to reference the one you 
built via the new {{groupId}} and the new {{version}}

  was (Author: davetron5000):
Michael - if you are desperate and don't want to wait, you can use it now 
with a bit of elbow grease (this is what we're doing where I work):

 # checkout the 2.0-beta-9 via 
https://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.0-beta-9 
(you need both the release manager and the release plugin, which this url will 
get you)
 # apply the patch
 # Change the {{groupId}} and {{version}} in *all three* poms (this helps you 
deploy it later)
 # build everything
 # deploy these files to your local maven repo
 # Change your poms that reference the release plugin to reference the one you 
built via the new {{groupId}} and the new {{version}}
  
 Support a pattern to generate the release tag
 -

 Key: MRELEASE-159
 URL: http://jira.codehaus.org/browse/MRELEASE-159
 Project: Maven 2.x Release Plugin
  Issue Type: New Feature
  Components: prepare
Affects Versions: 2.0-beta-4
Reporter: Joerg Schaible
 Attachments: MRELEASE-159-PATCH-update.diff.gz, 
 MRELEASE-159-PATCH.diff.gz


 The release-plugin uses currently the pattern artifactId-version to 
 create the version tag. A configuration element would be fine to support 
 different requirements for release tags (in our case v_version, since 
 with svn the module is already part of the path).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MRELEASE-159) Support a pattern to generate the release tag

2009-08-12 Thread Michael Wenig (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186830#action_186830
 ] 

Michael Wenig commented on MRELEASE-159:


Hi Dave,

thanks for this workaround - that's exactly the one I have to make but leads to 
some discussions :-) If there would be a new beta in the next weeks we could 
avoid that...

And as the patch is still there and working I think it should be possible with 
only little effort to apply it officially

Regards Michael

 Support a pattern to generate the release tag
 -

 Key: MRELEASE-159
 URL: http://jira.codehaus.org/browse/MRELEASE-159
 Project: Maven 2.x Release Plugin
  Issue Type: New Feature
  Components: prepare
Affects Versions: 2.0-beta-4
Reporter: Joerg Schaible
 Attachments: MRELEASE-159-PATCH-update.diff.gz, 
 MRELEASE-159-PATCH.diff.gz


 The release-plugin uses currently the pattern artifactId-version to 
 create the version tag. A configuration element would be fine to support 
 different requirements for release tags (in our case v_version, since 
 with svn the module is already part of the path).

-- 
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-4294) File ownership on tarball is set

2009-08-12 Thread Stephen Pack (JIRA)
File ownership on tarball is set


 Key: MNG-4294
 URL: http://jira.codehaus.org/browse/MNG-4294
 Project: Maven 2
  Issue Type: Bug
  Components: General
Affects Versions: 2.2.1
Reporter: Stephen Pack
Priority: Minor


File ownership was set on the 2.2.1 tarball.  When untarring as root with 
default flags, this results in file ownership assigned unexpectedly.

Tarballs for other versions have ownership of 0:0.

[r...@ipvmds01 share]# tar -tvf apache-maven-2.2.1-bin.tar.gz
-rw-r--r-- jdcasey/jdcasey 37854 2009-07-21 17:14:15 
apache-maven-2.2.1/boot/classworlds-1.1.jar
-rw-r--r-- 501/501 12933 2009-08-06 14:11:25 
apache-maven-2.2.1/LICENSE.txt
-rw-r--r-- 501/501   923 2009-08-06 14:11:25 
apache-maven-2.2.1/NOTICE.txt
-rw-r--r-- 501/501  2532 2009-08-06 14:11:25 
apache-maven-2.2.1/README.txt
-rw-r--r-- jdcasey/jdcasey   158 2009-08-06 14:18:08 
apache-maven-2.2.1/bin/m2.conf
-rw-r--r-- jdcasey/jdcasey  5915 2009-08-06 14:18:08 
apache-maven-2.2.1/bin/mvn.bat
-rw-r--r-- jdcasey/jdcasey  6100 2009-08-06 14:18:08 
apache-maven-2.2.1/bin/mvnDebug.bat
-rwxr-xr-x jdcasey/jdcasey  4562 2009-08-06 14:18:08 apache-maven-2.2.1/bin/mvn
-rwxr-xr-x jdcasey/jdcasey  4743 2009-08-06 14:18:08 
apache-maven-2.2.1/bin/mvnDebug
drwxrwxrwx 501/501 0 2009-08-06 14:11:25 apache-maven-2.2.1/conf/
-rwxrwxrwx 501/501 10205 2009-08-06 14:11:25 
apache-maven-2.2.1/conf/settings.xml
-rwxrwxrwx 501/501   3151139 2009-08-06 14:18:06 
apache-maven-2.2.1/lib/maven-2.2.1-uber.jar

[r...@ipvmds01 share]# tar -tvf apache-maven-2.1.0-bin.tar.gz
drwxr-xr-x 0/0   0 2009-03-18 14:04:52 apache-maven-2.1.0/conf/
-rw-r--r-- 0/0   37854 2009-03-18 11:01:38 
apache-maven-2.1.0/boot/classworlds-1.1.jar
-rw-r--r-- 0/0   11358 2009-03-18 14:04:52 
apache-maven-2.1.0/LICENSE.txt
-rw-r--r-- 0/0 609 2009-03-18 14:04:52 apache-maven-2.1.0/NOTICE.txt
-rw-r--r-- 0/02532 2009-03-18 14:04:52 apache-maven-2.1.0/README.txt
-rw-r--r-- 0/0 145 2009-03-18 14:11:57 
apache-maven-2.1.0/bin/m2.conf
-rw-r--r-- 0/05915 2009-03-18 14:11:57 
apache-maven-2.1.0/bin/mvn.bat
-rw-r--r-- 0/06100 2009-03-18 14:11:57 
apache-maven-2.1.0/bin/mvnDebug.bat
-rwxr-xr-x 0/04562 2009-03-18 14:11:57 apache-maven-2.1.0/bin/mvn
-rwxr-xr-x 0/04743 2009-03-18 14:11:57 
apache-maven-2.1.0/bin/mvnDebug
-rw-r--r-- 0/0   10224 2009-03-18 14:04:52 
apache-maven-2.1.0/conf/settings.xml
-rw-r--r-- 0/0 3230334 2009-03-18 14:11:56 
apache-maven-2.1.0/lib/maven-2.1.0-uber.jar

[r...@ipvmds01 share]# tar -tvf  apache-maven-2.0.10-bin.tar.gz
drwxr-xr-x 0/0   0 2009-02-09 20:52:16 apache-maven-2.0.10/conf/
-rw-r--r-- 0/0   11560 2009-02-09 20:52:16 
apache-maven-2.0.10/LICENSE.txt
-rw-r--r-- 0/0 620 2009-02-09 20:52:16 
apache-maven-2.0.10/NOTICE.txt
-rw-r--r-- 0/02610 2009-02-09 20:52:16 
apache-maven-2.0.10/README.txt
-rw-r--r-- 0/01124 2009-02-09 20:52:16 
apache-maven-2.0.10/bin/m2.bat
-rw-r--r-- 0/0 145 2009-02-09 20:52:16 
apache-maven-2.0.10/bin/m2.conf
-rw-r--r-- 0/05899 2009-02-09 20:52:16 
apache-maven-2.0.10/bin/mvn.bat
-rw-r--r-- 0/06082 2009-02-09 20:52:16 
apache-maven-2.0.10/bin/mvnDebug.bat
-rwxr-xr-x 0/01092 2009-02-09 20:52:16 apache-maven-2.0.10/bin/m2
-rwxr-xr-x 0/04562 2009-02-09 20:52:16 apache-maven-2.0.10/bin/mvn
-rwxr-xr-x 0/04735 2009-02-09 20:52:16 
apache-maven-2.0.10/bin/mvnDebug
-rw-r--r-- 0/09948 2009-02-09 20:52:16 
apache-maven-2.0.10/conf/settings.xml
-rw-r--r-- 0/0 2300936 2009-02-09 20:57:51 
apache-maven-2.0.10/lib/maven-2.0.10-uber.jar
-rw-r--r-- 0/0   37854 2009-02-09 20:19:22 
apache-maven-2.0.10/boot/classworlds-1.1.jar

-- 
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: (MEV-635) Bad checksums for com.google.inject.** 2.0

2009-08-12 Thread Max Bowsher (JIRA)
Bad checksums for com.google.inject.** 2.0
--

 Key: MEV-635
 URL: http://jira.codehaus.org/browse/MEV-635
 Project: Maven Evangelism
  Issue Type: Bug
  Components: Checksum Failure
Reporter: Max Bowsher


The checksums for the 2.0 versions of ALL artifacts under groupId 
com.google.inject and children are invalid.

-- 
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: (MJAVADOC-253) HTTP PROXY DOES NOT WORK ANY MORE

2009-08-12 Thread Mohan K (JIRA)
HTTP PROXY DOES NOT WORK ANY MORE
-

 Key: MJAVADOC-253
 URL: http://jira.codehaus.org/browse/MJAVADOC-253
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.6
 Environment: Maven 2.0.9
JDK5 (Sun)
Reporter: Mohan K
Priority: Critical


It appears the update of Wagon Provider in 2.6 is not compatible with Maven 
2.0.x. Here is the
email snippet as posted to maven users group (no responses)
I am using Maven 2.0.9 and maven-javadoc-plugin 2.6. I have the links 
configured in my
plugin config. Now all resolution of external links fail (we are behind a proxy 
*not* NTLM)
with this:

Aug 12, 2009 12:02:31 AM 
org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
INFO: ntlm authentication scheme selected
Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.HttpMethodDirector 
authenticate

The wagon provider appears to have been upgraded to 1.0-beta-6 in the 
maven-javadoc-plugin 2.6
(as opposed to 1.0-beta-2 in 2.5). I seem to remember that (maybe it is wrong) 
that wagon 1.0-beta-6
requires Maven 2.1.x and above? If that is the case, I don't understand how the 
plugin was released with
prerequisite of 2.0.9? 
Is there a workaround to disable the default ntlm auth scheme via a magical 
system property? 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: (MJAVADOC-253) HTTP PROXY DOES NOT WORK ANY MORE

2009-08-12 Thread Mohan K (JIRA)

[ 
http://jira.codehaus.org/browse/MJAVADOC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186835#action_186835
 ] 

Mohan K commented on MJAVADOC-253:
--

Sorry, it appears my CAPS LOCK was on when entering the title ;)

 HTTP PROXY DOES NOT WORK ANY MORE
 -

 Key: MJAVADOC-253
 URL: http://jira.codehaus.org/browse/MJAVADOC-253
 Project: Maven 2.x Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.6
 Environment: Maven 2.0.9
 JDK5 (Sun)
Reporter: Mohan K
Priority: Critical

 It appears the update of Wagon Provider in 2.6 is not compatible with Maven 
 2.0.x. Here is the
 email snippet as posted to maven users group (no responses)
 I am using Maven 2.0.9 and maven-javadoc-plugin 2.6. I have the links 
 configured in my
 plugin config. Now all resolution of external links fail (we are behind a 
 proxy *not* NTLM)
 with this:
 Aug 12, 2009 12:02:31 AM 
 org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
 INFO: ntlm authentication scheme selected
 Aug 12, 2009 12:02:31 AM org.apache.commons.httpclient.HttpMethodDirector 
 authenticate
 The wagon provider appears to have been upgraded to 1.0-beta-6 in the 
 maven-javadoc-plugin 2.6
 (as opposed to 1.0-beta-2 in 2.5). I seem to remember that (maybe it is 
 wrong) that wagon 1.0-beta-6
 requires Maven 2.1.x and above? If that is the case, I don't understand how 
 the plugin was released with
 prerequisite of 2.0.9? 
 Is there a workaround to disable the default ntlm auth scheme via a magical 
 system property? 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: (MDEP-161) dependy:resolve-plugins doesn't output to file when using outputFile parameter

2009-08-12 Thread Nedko Hristov (JIRA)

[ 
http://jira.codehaus.org/browse/MDEP-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186838#action_186838
 ] 

Nedko Hristov commented on MDEP-161:


I came upon the same problem. The documentation specifies that the option is 
valid and working:
http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#outputFile
I tried both full and relative paths and neither works correctly. Unfortunately 
the description does not provide any examles. A workaround will be to use the 
following command for generating output:
mvn dependency:tree  foo.txt
Unfortunately that will include the unnecessary extra reactor information that 
you probably don't need.

 dependy:resolve-plugins doesn't output to file when using outputFile parameter
 --

 Key: MDEP-161
 URL: http://jira.codehaus.org/browse/MDEP-161
 Project: Maven 2.x Dependency Plugin
  Issue Type: Bug
  Components: resolve-plugins
Affects Versions: 2.0
 Environment: $ mvn --version
 Maven version: 2.0.8
 Java version: 1.6.0_03
 OS name: linux version: 2.6.22-14-generic arch: i386 Family: unix
Reporter: Basil James Whitehouse III
Assignee: Brian Fox

 The dependency:tree and dependency:resolve goals output to file when there's 
 an outputFile parameter.  The 
 [documentation|http://maven.apache.org/plugins/maven-dependency-plugin/resolve-plugins-mojo.html#outputFile|documented]
  for resolve-plugins indicates it's possible, but running {{mvn 
 dependency:resolve-plugins -DoutputFile=plugin-dep.txt}} only outputs to the 
 console.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MWAR-164) Support for specifying which encoding to use when filtering resources

2009-08-12 Thread Ognjen Blagojevic (JIRA)

[ 
http://jira.codehaus.org/browse/MWAR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186839#action_186839
 ] 

Ognjen Blagojevic commented on MWAR-164:


Herve is right. Perhaps using project.build.sourceEncoding as a default value 
is a good idea.

Plus a Boolean parameter (searchEncodingInFiles) which will specify to open 
XML/JSP/HTML... files to look for specified encoding. This is of course harder 
to implement and less valuable, so maybe could be separate bug?

project.build.sourceEncoding covers most use cases, I think.

Regards,
Ognjen

 Support for specifying which encoding to use when filtering resources
 -

 Key: MWAR-164
 URL: http://jira.codehaus.org/browse/MWAR-164
 Project: Maven 2.x WAR Plugin
  Issue Type: Improvement
Affects Versions: 2.1-alpha-1
Reporter: kai lilleby
 Fix For: 2.1


 Quoting Hervé:
 {quote}
 Maven filtering provides an encoding parameter to set encoding used when
 reading/writing files. But war plugin uses null value, which means platform
 encoding... Sorry, encoding support won't be totally free ;)
 I added TODOs in the code.
 For web.xml and container config XML file, I set encoding to UTF-8, which is a
 better default value than platform encoding.
 For other filtered resources, you'll need to add an encoding attribute to
 o.a.m.model.Resource class, to let the user define which encoding he wants to
 use when filtering. Perhaps using project.build.sourceEncoding as a default
 value is a good idea.
 Seems like this is worth a Jira issue to track this new feature.
 {quote}

-- 
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-2553) nexus.openqa.org - central sync

2009-08-12 Thread Patrick Lightbody (JIRA)
nexus.openqa.org - central sync


 Key: MAVENUPLOAD-2553
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2553
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Patrick Lightbody


I've added the maven key to ~/.ssh/authorized_keys. The CSV entry is:

org.seleniumhq,maven-central-r...@openqa.org:/opt/nexus/sonatype-work/nexus/storage/releases,rsync_ssh,Patrick
 Lightbody,patr...@lightbody.net,,


-- 
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-2550) Please sync org.jamon

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2550.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Please sync org.jamon
 -

 Key: MAVENUPLOAD-2550
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2550
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Ian Robertson
Assignee: Carlos Sanchez

 org.jamon,ja...@jamon.org:/home/jamon/maven2,rsync_ssh,Ian 
 Robertson,ian.b.robert...@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-2551) xslthl (net.sf.xslthl) upload

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2551.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 xslthl (net.sf.xslthl) upload
 -

 Key: MAVENUPLOAD-2551
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2551
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Cedric Pronzato
Assignee: Carlos Sanchez

 Hello,
 I am developer in the xslthl project and I would like to have our repository 
 synced with maven central repository.
 net.sf.xslthl,mavens...@web.sourceforge.net:/home/groups/x/xs/xslthl/htdocs/maven/repository,rsync_ssh,Cedric
  Pronzato,mi...@users.sourceforge.net,,
 Regards,
 Cedric,

-- 
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-2548) Upload artifact for Google AppEngine to version 1.2.2

2009-08-12 Thread Carlos Sanchez (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186848#action_186848
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2548:
-

please read 
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

 Upload artifact for Google AppEngine to version 1.2.2
 -

 Key: MAVENUPLOAD-2548
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2548
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Oleg Taranenko

 Original was filed to MGAE
 http://jira.codehaus.org/browse/MGAE-3

-- 
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-2547) 'Sync my repo' request

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2547.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 'Sync my repo' request
 --

 Key: MAVENUPLOAD-2547
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2547
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Edvin Syse
Assignee: Carlos Sanchez

 no.tornado.brap,mavens...@brap.tornado.no:/home/brap/webapps/maven/repository,rsync_ssh,Edvin
  Syse,ed...@sysedata.no,,

-- 
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-2549) Please upload JCaptcha4Struts2 v2.0.1

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2549.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Please upload JCaptcha4Struts2 v2.0.1
 -

 Key: MAVENUPLOAD-2549
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2549
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Yohan Liyanage
Assignee: Carlos Sanchez
 Attachments: jcaptcha4struts2-2.0.1-bundle.jar


 http://jcaptcha4struts2.googlecode.com/files/jcaptcha4struts2-2.0.1-bundle.jar
 http://code.google.com/p/jcaptcha4struts2/
 http://code.google.com/p/jcaptcha4struts2/people/list
 I am the owner and developer of JCaptcha4Struts2 project, a plugin for struts 
 2. 
 My project uses the groupId com.google.code.jcaptcha4struts2.
 You may find my name (yohanliyanage) in the above mentioned project page.  
 Please upload the bundle to maven central repo. 
 Thanks a lot !

-- 
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-2491) XQParser Upload request

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2491.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 XQParser Upload request
 ---

 Key: MAVENUPLOAD-2491
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2491
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Damien Abos
Assignee: Carlos Sanchez
 Attachments: xqparser-1.0-bundle.jar


 I'm the developer of xqparser sourceforge project, please upload!
 Thanks you :)
 leejin (Damien Abos)

-- 
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-2541) jt400-full-6.5.1-bundle

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2541.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 jt400-full-6.5.1-bundle
 ---

 Key: MAVENUPLOAD-2541
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2541
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Jeff Lee
Assignee: Carlos Sanchez
 Attachments: jt400-6.4-bundle.jar, jt400-6.5.1-bundle.jar


 https://sourceforge.net/projects/jt400
 http://jt400.sourceforge.net/
 http://jt400.sourceforge.net/team.html
 The IBM Toolbox for Java (also known as JTOpen) is a library of Java classes 
 supporting the client/server and internet programming models to a system 
 running OS/400, i5/OS, or IBM i. The classes can be used by Java applets, 
 servlets, and applications to easily access OS/400, i5/OS, and IBM i data and 
 resources.

-- 
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-2554) Uploading proguard 4.4 to The Central Repository

2009-08-12 Thread Peter Janes (JIRA)
Uploading proguard 4.4 to The Central Repository


 Key: MAVENUPLOAD-2554
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2554
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Peter Janes
Assignee: Carlos Sanchez


Please Upload the latest version to Repository. The last version (posted by me) 
in repository is 4.2

http://pyx4j.com/downloads/proguard-4.3-bundle.jar

http://proguard.sourceforge.net/

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It 
removes unused classes, fields, methods, and attributes. It then optimizes the 
bytecode. It then renames the remaining classes, fields, and methods using 
short meaningless names. Finally, it preverifies the processed code for Java 6 
or for Java Micro Edition.

Changes in 4.3:
- Added class merging.
- Added static single assignment analysis.
- Added support for annotation and enumeration
  class types in configuration.
- Refined shrinking of fields in case of unusual
  -keepclassmembers options.
- Added simplification of tail recursion calls.
- Added new peephole optimizations.
- Fixed optimization of unused variable
  initializations causing negative stack sizes.
- Fixed optimization of unusual initialization
  code causing NullPointerExceptions.
- Fixed optimization of half-used long and double
  parameters.
- Fixed processing of complex generics signatures.
- Working around suspected java compiler bug with
  parameter annotations on constructors of
  non-static inner classes.
- Fixed obfuscation of classes with inner classes
  whose names are preserved.
- Fixed access of protected methods in repackaged
  classes.
- Added options -classobfuscationdictionary and
  -packageobfuscationdictionary.
- Adapting more types of resource file names based on
  obfuscation.
- Extended warnings about incorrect dependencies.
- Added start-up scripts and build scripts.
- Updated documentation and examples

-- 
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-2546) Upload LESS for Java

2009-08-12 Thread Carlos Sanchez (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186850#action_186850
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2546:
-

you need to remove the repositories section in the pom

 Upload LESS for Java
 

 Key: MAVENUPLOAD-2546
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2546
 Project: Maven Upload Requests
  Issue Type: Task
Reporter: Rostislav Hristov

 LESS extends CSS with: variables, mixins, operations and nested rules. Best 
 of all, LESS uses existing CSS syntax.
 LESS for Java is a Maven 2 artifact that wraps the original LESS sources and 
 makes them available to Java developers thanks to JRuby. The project provides 
 a straightforward access to the LESS API and simple integration in web 
 applications.

-- 
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-2552) JUnit 4.7

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2552.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 JUnit 4.7
 -

 Key: MAVENUPLOAD-2552
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2552
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Simon Brandhof
Assignee: Carlos Sanchez
 Attachments: junit-4.7-bundle.jar


 Please upload this new version.

-- 
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-2553) nexus.openqa.org - central sync

2009-08-12 Thread Patrick Lightbody (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186846#action_186846
 ] 

Patrick Lightbody commented on MAVENUPLOAD-2553:


Is removing that stuff just some sort of manual process? Would be nice if there 
were some way to automate that...

 nexus.openqa.org - central sync
 

 Key: MAVENUPLOAD-2553
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2553
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Patrick Lightbody
Assignee: Carlos Sanchez

 I've added the maven key to ~/.ssh/authorized_keys. The CSV entry is:
 org.seleniumhq,maven-central-r...@openqa.org:/opt/nexus/sonatype-work/nexus/storage/releases,rsync_ssh,Patrick
  Lightbody,patr...@lightbody.net,,

-- 
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-2553) nexus.openqa.org - central sync

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2553.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

Remember for new releases to remove the repository and pluginRepository entries 
in the poms

 nexus.openqa.org - central sync
 

 Key: MAVENUPLOAD-2553
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2553
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Patrick Lightbody
Assignee: Carlos Sanchez

 I've added the maven key to ~/.ssh/authorized_keys. The CSV entry is:
 org.seleniumhq,maven-central-r...@openqa.org:/opt/nexus/sonatype-work/nexus/storage/releases,rsync_ssh,Patrick
  Lightbody,patr...@lightbody.net,,

-- 
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-2542) jt400-full-6.3-bundle

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2542.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 jt400-full-6.3-bundle
 -

 Key: MAVENUPLOAD-2542
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2542
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Jeff Lee
Assignee: Carlos Sanchez
 Attachments: jt400-6.2-bundle.jar, jt400-6.3-bundle.jar


 https://sourceforge.net/projects/jt400
 http://jt400.sourceforge.net/
 http://jt400.sourceforge.net/team.html
 The IBM Toolbox for Java (also known as JTOpen) is a library of Java classes 
 supporting the client/server and internet programming models to a system 
 running OS/400, i5/OS, or IBM i. The classes can be used by Java applets, 
 servlets, and applications to easily access OS/400, i5/OS, and IBM i data and 
 resources.

-- 
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-2543) jt400-full-6.1-bundle

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2543.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 jt400-full-6.1-bundle
 -

 Key: MAVENUPLOAD-2543
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2543
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Jeff Lee
Assignee: Carlos Sanchez
 Attachments: jt400-6.1-bundle.jar


 https://sourceforge.net/projects/jt400
 http://jt400.sourceforge.net/
 http://jt400.sourceforge.net/team.html
 The IBM Toolbox for Java (also known as JTOpen) is a library of Java classes 
 supporting the client/server and internet programming models to a system 
 running OS/400, i5/OS, or IBM i. The classes can be used by Java applets, 
 servlets, and applications to easily access OS/400, i5/OS, and IBM i data and 
 resources.

-- 
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-2554) Uploading proguard 4.4 to The Central Repository

2009-08-12 Thread Peter Janes (JIRA)

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

Peter Janes closed MAVENUPLOAD-2554.


Resolution: Fixed

Sorry, I thought clone would allow me to edit the issue before it was 
submitted.  New one coming shortly.

 Uploading proguard 4.4 to The Central Repository
 

 Key: MAVENUPLOAD-2554
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2554
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Peter Janes
Assignee: Carlos Sanchez

 Please Upload the latest version to Repository. The last version (posted by 
 me) in repository is 4.2
 http://pyx4j.com/downloads/proguard-4.3-bundle.jar
 http://proguard.sourceforge.net/
 ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It 
 removes unused classes, fields, methods, and attributes. It then optimizes 
 the bytecode. It then renames the remaining classes, fields, and methods 
 using short meaningless names. Finally, it preverifies the processed code for 
 Java 6 or for Java Micro Edition.
 Changes in 4.3:
 - Added class merging.
 - Added static single assignment analysis.
 - Added support for annotation and enumeration
   class types in configuration.
 - Refined shrinking of fields in case of unusual
   -keepclassmembers options.
 - Added simplification of tail recursion calls.
 - Added new peephole optimizations.
 - Fixed optimization of unused variable
   initializations causing negative stack sizes.
 - Fixed optimization of unusual initialization
   code causing NullPointerExceptions.
 - Fixed optimization of half-used long and double
   parameters.
 - Fixed processing of complex generics signatures.
 - Working around suspected java compiler bug with
   parameter annotations on constructors of
   non-static inner classes.
 - Fixed obfuscation of classes with inner classes
   whose names are preserved.
 - Fixed access of protected methods in repackaged
   classes.
 - Added options -classobfuscationdictionary and
   -packageobfuscationdictionary.
 - Adapting more types of resource file names based on
   obfuscation.
 - Extended warnings about incorrect dependencies.
 - Added start-up scripts and build scripts.
 - Updated documentation and examples

-- 
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-2371) JWBF

2009-08-12 Thread Carlos Sanchez (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186854#action_186854
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2371:
-

then you cant use those groupIds, you need to use net.sourceforge.jwbf and sub 
groups

ie. net.sourceforge.jwbf.core
net.sourceforge.jwbf.mediawiki

 JWBF
 

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

 net.sourceforge.jwbf,mavens...@web.sourceforge.net:/home/groups/j/jw/jwbf/m2repo-release,rsync_ssh,eldurloki,eldurl...@users.sourceforge.net,,

-- 
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-2516) maven replacer plugin

2009-08-12 Thread Carlos Sanchez (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186855#action_186855
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2516:
-

you need to use a fully qualified groupId like 
com.google.code.maven-replacer-plugin

 maven replacer plugin
 -

 Key: MAVENUPLOAD-2516
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2516
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Steven Baker

 http://maven-replacer-plugin.googlecode.com/files/maven-replacer-plugin-1.0.0-bundle.jar
 I have an open source simple text replacing plugin I would like added.

-- 
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-2525) Cathcart

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2525.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Cathcart
 

 Key: MAVENUPLOAD-2525
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2525
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Steven Hale
Assignee: Carlos Sanchez

 net.sf.cathcart,mavens...@web.sourceforge.net:/home/groups/c/ca/cathcart/htdocs/m2-repo,rsync_ssh,Steven
  Hale,swordl...@users.sourceforge.net,,

-- 
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-2483) Version jdk6-2.0 of UISpec4J

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2483.
---

  Assignee: Carlos Sanchez
Resolution: Incomplete

 Version jdk6-2.0 of UISpec4J
 

 Key: MAVENUPLOAD-2483
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2483
 Project: Maven Upload Requests
  Issue Type: New Feature
Reporter: Pascal Pratmarty
Assignee: Carlos Sanchez
 Attachments: uispec4j-jdk6-2.0-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-2522) Uploading into Maven repository

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2522.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Uploading into Maven repository
 ---

 Key: MAVENUPLOAD-2522
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2522
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Pavel Ponec
Assignee: Carlos Sanchez

 Thank you, 
 Paul

-- 
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-2534) JSON.simple maven bundle upload

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2534.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 JSON.simple maven bundle upload
 ---

 Key: MAVENUPLOAD-2534
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2534
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Yidong Fang
Assignee: Carlos Sanchez

 http://json-simple.googlecode.com/files/json-simple-1.1-bundle.jar
 http://code.google.com/p/json-simple
 I am owner of JSON.simple. Please upload. 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-2482) Version jdk5-2.0 of UISpec4J

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2482.
---

  Assignee: Carlos Sanchez
Resolution: Incomplete

 Version jdk5-2.0 of UISpec4J
 

 Key: MAVENUPLOAD-2482
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2482
 Project: Maven Upload Requests
  Issue Type: New Feature
Reporter: Pascal Pratmarty
Assignee: Carlos Sanchez
 Attachments: uispec4j-jdk5-2.0-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-2536) libvirt Java bindings uploads

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2536.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 libvirt Java bindings uploads
 -

 Key: MAVENUPLOAD-2536
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2536
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Daniel Veillard
Assignee: Carlos Sanchez

 We would like to get autosync from the given URL, so no bundle the CVS is 
 below : 
 org.libvirt,rsync://libvirt.org/maven2,rsync,Daniel 
 Veillard,dan...@veillard.com,,
 with the goal of having it sync'ed automatically on the centra repository.
 The git repository is on libvirt.org and you should be able to verify that 
 I'm so far
 the main contributor. I hope the request is okay, feel free to correct me if 
 needed.
   thanks in advance,
 Daniel

-- 
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-2528) Please add latest version of rabbitmq-client library 1.6.0

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2528.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Please add latest version of rabbitmq-client library 1.6.0
 --

 Key: MAVENUPLOAD-2528
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2528
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Gavin Bong
Assignee: Carlos Sanchez

 http://www.rabbitmq.com/releases/rabbitmq-java-client/v1.6.0/amqp-client-1.6.0-bundle.jar
 http://www.rabbitmq.com/java-client.html 
 The latest release 1.6.0 is out. Please upload! Thanks a million.

-- 
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-2497) gwt-mvc 0.2.0-gwt1.5

2009-08-12 Thread Carlos Sanchez (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186853#action_186853
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2497:
-

don't know how you generated it, but the jar is now empty 

 gwt-mvc 0.2.0-gwt1.5
 

 Key: MAVENUPLOAD-2497
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2497
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: François Wauquier
 Attachments: gwt-mvc-0.2.0-gwt-1.5.jar


 http://code.google.com/p/gwt-mvc/
 http://gwt-mvc.googlecode.com/svn/trunk/gwt-mvc/releases/gwt-mvc-0.2.0-gwt-1.5.jar

-- 
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-2519) Upload Smack 3.1.0

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2519.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Upload Smack 3.1.0
 --

 Key: MAVENUPLOAD-2519
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2519
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Niklas Gustavsson
Assignee: Carlos Sanchez

 This JAR is developed by Ignite Realtime, and not by me. However, Ignite has 
 not shown any great interest in uploading Smack to Maven central: 
 http://www.igniterealtime.org/community/message/164751
 And, this is merely an upgrade of the already existing releases, so the 
 groupId should be fine I hope.

-- 
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-2518) netbeans ant tasks for creating netbeans modules (as shipped with netbeans 6.7)

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2518.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 netbeans ant tasks for creating netbeans modules (as shipped with netbeans 
 6.7)
 ---

 Key: MAVENUPLOAD-2518
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2518
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Milos Kleint
Assignee: Carlos Sanchez
 Attachments: tasks67.jar


 netbeans ant tasks to create netbeans modules.
 the jar is coming straight from the netbeans binary download of NetBeans 6.0 
 FCS. The jar is located at netbeans/harness/tasks.jar in the binary distro.
 It's required by the nbm-maven-plugin from codehaus.org
 released under dual license CDDL 1.0 + GPL 2.0 with classpath exception
 I'm technically not a developer of the ant tasks, but I'm a Netbeans.org 
 contributor for 8 years , employed by Sun Microsystems.

-- 
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-2506) javax.servlet.servlet-api-2.3 sources are wrong

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2506.
---

  Assignee: Carlos Sanchez
Resolution: Incomplete

 javax.servlet.servlet-api-2.3 sources are wrong
 ---

 Key: MAVENUPLOAD-2506
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2506
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Jaan Vajakas
Assignee: Carlos Sanchez

 The sources JAR
 http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar
 does not contain e.g. the interface javax.servlet.Filter.
 It seems that the 2.3 version has accidentally gotten its sources from 2.2. 
 At least the hashes of servlet-api-2.3-sources.jar and 
 servlet-api-2.2-sources.jar are identical:
 http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar.sha1
 http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/servlet/servlet-api/2.2/servlet-api-2.2-sources.jar.sha1

-- 
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-2496) gwt-mvc 0.2.1-gwt-1.6

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2496.
---

  Assignee: Carlos Sanchez
Resolution: Incomplete

you need to remove the repositories section in the pom

 gwt-mvc 0.2.1-gwt-1.6
 -

 Key: MAVENUPLOAD-2496
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2496
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: François Wauquier
Assignee: Carlos Sanchez
 Attachments: gwt-mvc-0.2.1-gwt-1.6.jar


 http://code.google.com/p/gwt-mvc/
 http://gwt-mvc.googlecode.com/svn/trunk/gwt-mvc/releases/gwt-mvc-0.2.1-gwt-1.6.jar

-- 
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-2457) Maven Config Processor 1.6 Upload Request

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2457.
---

  Assignee: Carlos Sanchez
Resolution: Won't Fix

 Maven Config Processor 1.6 Upload Request
 -

 Key: MAVENUPLOAD-2457
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2457
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Leandro
Assignee: Carlos Sanchez

 Hi, I'm leader developer of the Maven Config Processor Plugin and would like 
 to upload the version 1.6 of the plugin to the Maven Central 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-2521) Upload Smackx 3.1.0

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2521.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Upload Smackx 3.1.0
 ---

 Key: MAVENUPLOAD-2521
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2521
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Niklas Gustavsson
Assignee: Carlos Sanchez

 This JAR is developed by Ignite Realtime, and not by me. However, Ignite has 
 not shown any great interest in uploading Smack to Maven central:
 http://www.igniterealtime.org/community/message/164751
 And, this is merely an upgrade of the already existing releases, so the 
 groupId should be fine I hope.

-- 
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-2469) http://www.chenillekit.org

2009-08-12 Thread Carlos Sanchez (JIRA)

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

Carlos Sanchez closed MAVENUPLOAD-2469.
---

  Assignee: Carlos Sanchez
Resolution: Incomplete

 http://www.chenillekit.org
 --

 Key: MAVENUPLOAD-2469
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2469
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Sven Homburg
Assignee: Carlos Sanchez

 org.chenillekit,rs...@www.chenillekit.org:m2repo/releases,rsync_ssh,Sven
  Homburg,hombu...@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-2387) Transitive dependencies in eclipse jdt core are broken

2009-08-12 Thread Brian Fox (JIRA)

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

Brian Fox closed MAVENUPLOAD-2387.
--

  Assignee: Brian Fox  (was: Carlos Sanchez)
Resolution: Won't Fix

It is and should have never been allowed in that way, however we can't remove 
things once they are there, nor change them. So there isn't much to be done 
here.

 Transitive dependencies in eclipse jdt core are broken
 --

 Key: MAVENUPLOAD-2387
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2387
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Dave Syer
Assignee: Brian Fox

 Transitive dependencies in eclipse jdt core are broken.  I can 
 MAVENUPLOAD-1795 that the JDT core JAR was uploaded (the version number does 
 not match the actual one in the repo, so maybe that is part of the problem - 
 the repo has 3.3.0-v_771).  This JAR has dependencies and transitive 
 dependencies that (quite sensibly) use version ranges.  But the ranges do not 
 match any deployed versions of the dependencies, so if you try to use it you 
 get, for example
 Caused by: 
 org.apache.maven.artifact.versioning.OverConstrainedVersionException: 
 Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
   org.eclipse.equinox:app:jar:null
 There seems to be an issue with the form of the version in the app artifact.  
 It looks like it might match, but clearly doesn't.

-- 
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-2111) SAT4J bundles ready for inclusion in Maven Central repository

2009-08-12 Thread Brian Fox (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186858#action_186858
 ] 

Brian Fox commented on MAVENUPLOAD-2111:


Since you obviously have a maven build, why not just deploy to a repo and get 
it synced. You can use ours: 
http://nexus.sonatype.org/oss-repository-hosting.html

 SAT4J bundles ready for inclusion in Maven Central repository
 -

 Key: MAVENUPLOAD-2111
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2111
 Project: Maven Upload Requests
  Issue Type: New Feature
Reporter: Daniel Le Berre
Assignee: Jason van Zyl
 Attachments: pom.xml


 I am the leader of the SAT4J project.
 SAT4J will be used in the next release of Maven to manage dependencies, in a 
 way similar to Eclipse p2.
 Here are bundles of SAT4J core and SAT4J pb ready to be consumed by Maven 
 developers (Oleg and Jason).
 The version is 2.0.1 and not 2.0.0 since I fixed two small issues in that 
 code, that will not affect the current 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: (MAVENUPLOAD-2552) JUnit 4.7

2009-08-12 Thread Simon Brandhof (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186859#action_186859
 ] 

Simon Brandhof commented on MAVENUPLOAD-2552:
-

A great thank for your quickness !

 JUnit 4.7
 -

 Key: MAVENUPLOAD-2552
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2552
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Simon Brandhof
Assignee: Carlos Sanchez
 Attachments: junit-4.7-bundle.jar


 Please upload this new version.

-- 
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-2548) Upload artifact for Google AppEngine to version 1.2.2

2009-08-12 Thread Oleg Taranenko (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186860#action_186860
 ] 

Oleg Taranenko commented on MAVENUPLOAD-2548:
-

Sorry, I'm a little bit stuck. I'm not a google developer, and I have not 
access to the project sources. And therefore I can't imagine what against mvn 
repository:bundle should be executed. May be borrow existed pom.xml from 
version 1.2.1? Please advise or/and correct the above document.

 Upload artifact for Google AppEngine to version 1.2.2
 -

 Key: MAVENUPLOAD-2548
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2548
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Oleg Taranenko

 Original was filed to MGAE
 http://jira.codehaus.org/browse/MGAE-3

-- 
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-2548) Upload artifact for Google AppEngine to version 1.2.2

2009-08-12 Thread Carlos Sanchez (JIRA)

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186862#action_186862
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2548:
-

you need to provide a jar with the following contents
the jar you want to upload
the pom file 

 Upload artifact for Google AppEngine to version 1.2.2
 -

 Key: MAVENUPLOAD-2548
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2548
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Oleg Taranenko

 Original was filed to MGAE
 http://jira.codehaus.org/browse/MGAE-3

-- 
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: (MASSEMBLY-442) no way to avoid using detected user/group information for files and directories in tarballs

2009-08-12 Thread John Casey (JIRA)
no way to avoid using detected user/group information for files and directories 
in tarballs
---

 Key: MASSEMBLY-442
 URL: http://jira.codehaus.org/browse/MASSEMBLY-442
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.2-beta-4
Reporter: John Casey
Priority: Critical




-- 
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-442) no way to avoid using detected user/group information for files and directories in tarballs

2009-08-12 Thread John Casey (JIRA)

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

John Casey updated MASSEMBLY-442:
-

Fix Version/s: 2.2-beta-5

 no way to avoid using detected user/group information for files and 
 directories in tarballs
 ---

 Key: MASSEMBLY-442
 URL: http://jira.codehaus.org/browse/MASSEMBLY-442
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.2-beta-4
Reporter: John Casey
Priority: Critical
 Fix For: 2.2-beta-5




-- 
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-2555) Uploading proguard 4.4 to the central repository

2009-08-12 Thread Peter Janes (JIRA)
Uploading proguard 4.4 to the central repository


 Key: MAVENUPLOAD-2555
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2555
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Peter Janes


Please upload the latest version (4.4) to central. The last version (posted by 
Vlad Skarzhevskyy) is 4.3.

(Vlad writes: I'm simpily doing other stuff nowdays so if you take care of it 
it would be really nice.)

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It 
removes unused classes, fields, methods, and attributes. It then optimizes the 
bytecode. It then renames the remaining classes, fields, and methods using 
short meaningless names. Finally, it preverifies the processed code for Java 6 
or for Java Micro Edition.

Version 4.4

* Added new peephole optimizations.
* Added option -optimizations for fine-grained configuration of 
optimizations.
* Added option -adaptclassstrings for adapting string constants that 
correspond to obfuscated classes.
* Added option -keeppackagenames for keeping specified package names from 
being obfuscated.
* Added option -keepdirectories for keeping specified directory entries in 
output jars.
* Extended options -dontnote and -dontwarn for fine-grained configuration 
of notes and warnings.
* Added option -regex in ReTrace, for specifying alternative regular 
expressions to parse stack traces.
* Extended renaming of resource files based on obfuscation.
* Improved inlining of constant parameters and removal of unused parameters.
* Avoiding bug in IBM's JVM for JSE, in optimization step.
* Avoiding ArrayIndexOutOfBoundsException in optimization step.
* Fixed configuration with annotations that are not preserved themselves.
* Fixed preverification of invocations of super constructors with arguments 
containing ternary operators.
* Fixed processing of unreachable exception handlers.
* Fixed merging of exception classes.
* Fixed repeated method inlining.
* Fixed inlining of finally blocks surrounded by large try blocks, compiled 
with JDK 1.4 or earlier.
* Fixed optimization of complex finally blocks, compiled with JDK 1.4 or 
earlier.
* Fixed obfuscation of anonymous class names, if EnclosingMethod attributes 
are being kept.
* Fixed obfuscation of inner class names in generic types.
* Fixed decoding of UTF-8 strings containing special characters.
* Fixed copying of debug information and annotations when merging classes.
* Fixed writing out of unknown attributes.
* Fixed updating manifest files with split lines.
* Updated documentation and examples.

-- 
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-422) Error editing a Starteam file

2009-08-12 Thread Rick Marry (JIRA)

[ 
http://jira.codehaus.org/browse/SCM-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186885#action_186885
 ] 

Rick Marry commented on SCM-422:


Will this patch be applied in the near future?  I am having the same exact 
issue with the starteam provider.

 Error editing a Starteam file
 -

 Key: SCM-422
 URL: http://jira.codehaus.org/browse/SCM-422
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-starteam
Affects Versions: 1.1
 Environment: Maven 2.0.9, Windows XP, jre 1.5, Borland Starteam 2008
Reporter: Ausiàs Armesto
 Attachments: starteam-edit-patch.txt, starteam-edit-patch2.txt


 Hello,
 I am trying to use the maven-release-plugin against the Borland Starteam SCM 
 provider and during the execution of release:prepare the goal throws an 
 errror because it maven-release-plugin has no access to edit pom file. Here I 
 show you the message error.
 [INFO] [release:prepare]
 [INFO] Resuming release from phase 'rewrite-poms-for-release'
 [INFO] Transforming 'Project Example'...
 [INFO] Working directory: 
 C:\StarteamServer\StarteamProject\StarteamView\ProjectExample
 [INFO] Command line: stcmd lck -x -nologo -stop -p 
 u...@starteamserver:StarteamPort/StarteamProject/StarteamProject/ProjectExample
  -fp C:\StarteamServer\StarteamProject\StarteamView\ProjectExample -l pom.xml
 [WARNING] Unknown edit ouput: Folder: SRRU  (working directory: 
 C:\StarteamServer\StarteamProject\StarteamView\ProjectExample)
 [WARNING] Unknown edit ouput: pom.xml: Locked
 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Error writing POM: C:\IS\ISEJEMPLO\DYC\ispob\SRRU\pom.xml (Acces 
 denied)
 [INFO] 
 
 [INFO] For more information, run Maven with the -e switch
 [INFO] 
 
 [INFO] Total time: 11 seconds
 [INFO] Finished at: Mon Oct 20 13:50:30 CEST 2008
 [INFO] Final Memory: 7M/14M
 [INFO] 
 
 I have realized that the maven-release-plugin uses the following starteam 
 command:
 stcmd lck -x -nologo -stop -p 
 user:passw...@starteamserver:StarteamPort/StarteamProject/StarteamProject/ProjectExample
  -fp C:\StarteamServer\StarteamProject\StarteamView\ProjectExample -l pom.xml
 This command doesn't work if the Starteam project has checked the policy : 
 Mark unlocked working files read-only. This policy makes any file checked 
 out as a read-only file in the working directory. An when a lock operation is 
 performed changes the flag to allow writing to it. When a unlock operation is 
 perform changes again the flag to restrict the read-only access.
 The correction to the command is just add to the end the argument -rw as is 
 shown below:
 stcmd lck -x -nologo -stop -p 
 user:passw...@starteamserver:StarteamPort/StarteamProject/StarteamProject/ProjectExample
  -fp C:\StarteamServer\StarteamProject\StarteamView\ProjectExample -l -rw 
 pom.xml
 Here I provide the patch for the StarteamEditCommand.java and the fix for the 
 test case
 Do you want me to provide also the patch for the StarteamUnEditCommand.java?

-- 
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-4295) version ranges are not resolved from snapshot only repositories

2009-08-12 Thread Stephen Connolly (JIRA)
version ranges are not resolved from snapshot only repositories
---

 Key: MNG-4295
 URL: http://jira.codehaus.org/browse/MNG-4295
 Project: Maven 2
  Issue Type: Bug
  Components: Artifacts and Repositories
Affects Versions: 2.2.1, 2.2.0, 2.1.0, 2.1.0-M1, 2.0.10, 2.0.9, 2.0.8, 
2.0.7, 2.0.6
Reporter: Stephen Connolly
Priority: Minor
 Attachments: mversions-19.tar.gz

If a repository is defined like:

  repositories
repository
  id.../id
  name.../name
  url/url
  releases
enabledfalse/enabled
  /releases
/repository
  /repositories

Then the following call chain results with no versions being resolved from this 
repository

We ask the ArtifactMetadataSource to give us a list of available versions... 
that is this method:

http://maven.apache.org/ref/current/xref/org/apache/maven/project/artifact/MavenMetadataSource.html#495

This method creates a RepositoryMetadata object of type:

http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/ArtifactRepositoryMetadata.html#31

This metadata object is passed to the RepositoryMetadataManager:

http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.html#58

Which asks the RepositoryMetadata object if it is a snapshot...

http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/DefaultRepositoryMetadataManager.html#69

but our metadata object can never be a snapshot:

http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/repository/metadata/ArtifactRepositoryMetadata.html#81

So the end result is that we never look in non-release repositories...

To verify, run the attached test case like so

mvn clean verify -Dusernum=2 

This will fail as the repository is disabled for releases, while

mvn clean verify -Dusernum=3

Will pass, the only change being that the remote repository is now enabled for 
releases

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (MAVENUPLOAD-2556) Please sync with my repo

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


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


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

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

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

Thanks. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (MDEP-226) Improve documentation for dependency:copy artifactItem element

2009-08-12 Thread GubeSpam (JIRA)
Improve documentation for dependency:copy artifactItem element
--

 Key: MDEP-226
 URL: http://jira.codehaus.org/browse/MDEP-226
 Project: Maven 2.x Dependency Plugin
  Issue Type: Wish
  Components: copy
Reporter: GubeSpam
Assignee: Brian Fox


This ticket applies to the documentation on the project site: 
http://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html

Please update the page to provide the correct element name destFileName 
instead of destFile given in the artifactItems description

It would also be helpful if a full section was given to artifactItems, 
explaining what each of the elements (eg. location, destFileName, markerFile) 
means


-- 
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: (MSHADE-47) Shade misses class references stored as strings during relocation

2009-08-12 Thread Adam Rosien (JIRA)

[ 
http://jira.codehaus.org/browse/MSHADE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186903#action_186903
 ] 

Adam Rosien commented on MSHADE-47:
---

Relocating string contents should be optional, it's definitely something one 
wouldn't expect! 

 Shade misses class references stored as strings during relocation
 -

 Key: MSHADE-47
 URL: http://jira.codehaus.org/browse/MSHADE-47
 Project: Maven 2.x Shade Plugin
  Issue Type: Bug
Reporter: Steve Ebersole
Assignee: Daniel Kulp
 Attachments: boom.tar.gz


 http://anonsvn.jboss.org/repos/hibernate/cglib/trunk/pom.xml
 http://opensource.atlassian.com/projects/hibernate/browse/HHH-3504

-- 
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-4296) allow core extensions configure new classrealms

2009-08-12 Thread Igor Fedorenko (JIRA)
allow core extensions configure new classrealms
---

 Key: MNG-4296
 URL: http://jira.codehaus.org/browse/MNG-4296
 Project: Maven 2
  Issue Type: Improvement
  Components: Class Loading
Affects Versions: 3.0
Reporter: Igor Fedorenko
 Attachments: ClassRealmManagerDelegate.diff

Both m2e and tycho configure maven core classrealm to include additional JAR 
files and need a way to make classes from these additional JAR files to be 
accessible by maven plugins. Attached patch introduces new 
ClassRealmManagerDelegate, which can be used by m2e and tycho to contribute 
this kind of configuration to the core.

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