[ http://jira.codehaus.org/browse/CONTINUUM-556?page=all ]
Trygve Laugstol closed CONTINUUM-556:
-
Resolution: Won't Fix
Do not use the issue tracking system to ask questions, subscribe and ask those
on the users mailing list. See
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.013001.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.020001.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.023001.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.030001.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.04.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.043000.txt
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.05.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060114.053000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060114.053000.txt
targetJdk parameter cannot be set in maven 2
Key: MPPMD-23
URL: http://jira.codehaus.org/browse/MPPMD-23
Project: maven-pmd-plugin
Type: Bug
Reporter: Tony Nys
My code is java 5 and has the special for-loop syntax
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: vendredi 13 janvier 2006 00:00
To: Maven Developers List
Subject: Re: [m2] Modifying project.build.sourceDirectory and executions
This is because the part of clover that runs is forked, and the project
is
Please, upload JGroups 2.2.9.1 to the ibiblio repository.
-
Key: MAVENUPLOAD-678
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-678
Project: maven-upload-requests
Type: Task
Reporter: Loïc Lefèvre
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: jeudi 12 janvier 2006 23:56
To: Maven Developers List
Subject: Re: [codehaus-confluence] Maven: best practices - testing
strategies (comment added)
Vincent Massol wrote:
There's still a need to define the
[ http://jira.codehaus.org/browse/MNG-553?page=comments#action_55698 ]
Fabrice BELLINGARD commented on MNG-553:
I just want to mention that this issue looks more than just minor (at least to
me! :)).
Indeed, I want to spread Maven 2 all over my
MKS Support
---
Key: MPCHANGELOG-80
URL: http://jira.codehaus.org/browse/MPCHANGELOG-80
Project: maven-changelog-plugin
Type: New Feature
Reporter: Christoph Jerolimov
Priority: Minor
Fix For: 1.9
Attachments: changelog-mks-support.zip
I
[ http://jira.codehaus.org/browse/MPCHANGELOG-80?page=comments#action_55702
]
Arnaud Heritier commented on MPCHANGELOG-80:
It's easier for us if :
- you checkout the plugin sources with a subversion client
- you apply your modifications and add
[ http://jira.codehaus.org/browse/MPCHANGELOG-80?page=all ]
Christoph Jerolimov updated MPCHANGELOG-80:
---
Attachment: changelog-mks.diff
MKS Support
---
Key: MPCHANGELOG-80
URL:
Please fix pom in jtds bundle at ibiblio
Key: MAVENUPLOAD-679
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-679
Project: maven-upload-requests
Type: Task
Reporter: Øystein Myhre
[ http://jira.codehaus.org/browse/MNGECLIPSE-27?page=all ]
Roland Klein closed MNGECLIPSE-27:
--
Resolution: Won't Fix
Hello Eugene,
i tested the latest revision (rev.14) with eclipse 3.1 and 3.2M4 in both
enviroments all works fine.
But than i
[ http://jira.codehaus.org/browse/MPCHANGELOG-80?page=comments#action_55707
]
Arnaud Heritier commented on MPCHANGELOG-80:
Thanks a lot.
We'll review it ASAP.
MKS Support
---
Key: MPCHANGELOG-80
URL:
Plugin uses deprecated API to retrieve JIRA issues
--
Key: MPJIRA-17
URL: http://jira.codehaus.org/browse/MPJIRA-17
Project: maven-jira-plugin
Type: Bug
Versions: 1.2
Environment: JIRA 3.4.1-#107
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060113.111500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060113.111500.txt
-
To unsubscribe,
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060113.113000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060113.113000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I'm +1 for moving maven-archiver there. If you're talking about
maven-plugin-tools-ant|model|... then I'm -1, since these constitute
core features of maven (things we brag about in maven releases :)
I've got some stuff I need to move there, but waiting for the
proprietary side to settle
[ http://jira.codehaus.org/browse/MASSEMBLY-54?page=comments#action_55711 ]
Chris Hagmann commented on MASSEMBLY-54:
Surely I can, but I have nothing in my descriptor regarding filtering. I don't
see any docs describing anything about filtering, and
Guard against the url/ element being null in the site descriptor
--
Key: DOXIA-44
URL: http://jira.codehaus.org/browse/DOXIA-44
Project: doxia
Type: Bug
Components: Decoration Model
Reporter:
+1 (binding): Brett, John, Emmanuel, Lukas, Arnaud
+1 (non-binding): Vincent S, Mike
I get this error when performing the release:
Uploading:
scpexe://repo1.maven.org/home/projects/maven/repository-staging/to-ibibl
io/maven2/org/apache/maven/plugins/maven-pmd-plugin/2.0-beta-1/maven-pmd
Looks like this isn't an option unless we can make it work on Windows...
From the documentation:
Jpam can be used on:
1. Linux x86
2. Linux x86_64, including AMD64
3. Mac OS X
4. Solaris sparc
PAM is used on Unix and Unix-like operating systems. JPAM should be
readily portable to
Please correct update site in
http://m2eclipse.codehaus.org/Installing_Maven_2.0_plugin_for_Eclipse.html
Key: MNGECLIPSE-38
URL:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060113.150001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060113.150001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060113.151503.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060113.151503.txt
-
To unsubscribe,
[ http://jira.codehaus.org/browse/MNGECLIPSE-31?page=all ]
Eugene Kuleshov updated MNGECLIPSE-31:
--
Component: Documentation
eclipse:eclipse goal can switch enabled on and off using buildcommands -
Add to documentation
[ http://jira.codehaus.org/browse/MNGECLIPSE-38?page=all ]
Eugene Kuleshov updated MNGECLIPSE-38:
--
Component: Documentation
Please correct update site in
http://m2eclipse.codehaus.org/Installing_Maven_2.0_plugin_for_Eclipse.html
+1
Lukas Theussl wrote:
Hi,
Here are some more m1 plugins that I would be ready to release:
[] maven-html2xdoc-plugin-1.4
[] maven-jalopy-plugin-1.4
[] maven-javadoc-plugin-1.8
[] maven-native-plugin-1.2
They all have still a few issues open, mainly feature requests and
enhancements, but
[ http://jira.codehaus.org/browse/MNGECLIPSE-12?page=all ]
Eugene Kuleshov closed MNGECLIPSE-12:
-
Resolution: Duplicate
Fix Version: (was: 0.0.4)
Closing issue as duplicated.
Currently Maven embedder is not using settings.xml and fix
+1*4
fabrizio
On 1/13/06, Lukas Theussl [EMAIL PROTECTED] wrote:
Hi,
Here are some more m1 plugins that I would be ready to release:
[] maven-html2xdoc-plugin-1.4
[] maven-jalopy-plugin-1.4
[] maven-javadoc-plugin-1.8
[] maven-native-plugin-1.2
They all have still a few issues open,
[ http://jira.codehaus.org/browse/MNGECLIPSE-14?page=comments#action_55717
]
Eugene Kuleshov commented on MNGECLIPSE-14:
---
From the mail list:
Subject: [m2eclipse-user] Java Project Nature is required to see Maven
menu's
Date: Fri, 16 Dec
[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=all ]
Federico Sauter updated MNGECLIPSE-30:
--
Attachment: pom.xml
Maven plugin keeps looking for non-existent apacheds-*-2.4.1 dependency
[ http://jira.codehaus.org/browse/MCHECKSTYLE-14?page=comments#action_55726
]
Hugo Palma commented on MCHECKSTYLE-14:
---
Any schedule for the release that include this patch ?
Plugin does not support using custom checkstyle XML config file
[ http://jira.codehaus.org/browse/MPJIRA-17?page=comments#action_55725 ]
Lukas Theussl commented on MPJIRA-17:
-
Indeed, the maven-jira-plugin uses the parameters 'resolutionIds',
'priorityIds' and 'statusIds', which have been deprecated in JIRA 3.3
[ http://jira.codehaus.org/browse/MPJIRA-17?page=all ]
Lukas Theussl updated MPJIRA-17:
Assign To: Lukas Theussl
Fix Version: 1.3
Plugin uses deprecated API to retrieve JIRA issues
--
[ http://jira.codehaus.org/browse/MPMD-11?page=all ]
Lukas Theussl moved MPPMD-23 to MPMD-11:
Workflow: Maven (was: jira)
Key: MPMD-11 (was: MPPMD-23)
Project: Maven 2.x Pmd Plugin (was: maven-pmd-plugin)
targetJdk parameter
[ http://jira.codehaus.org/browse/MNGECLIPSE-30?page=all ]
Eugene Kuleshov updated MNGECLIPSE-30:
--
Fix Version: 0.0.4
It could be because of the old embedder version. I'll take a look.
Maven plugin keeps looking for non-existent apacheds-*-2.4.1
POM editor
--
Key: MNGECLIPSE-39
URL: http://jira.codehaus.org/browse/MNGECLIPSE-39
Project: Maven 2.x Plug-in for Eclipse
Type: New Feature
Reporter: Eugene Kuleshov
Assigned to: Eugene Kuleshov
Fix For: 1.0.0
Form-based POM editor for the
+1
On 1/13/06, Lukas Theussl [EMAIL PROTECTED] wrote:
Hi,
Here are some more m1 plugins that I would be ready to release:
[] maven-html2xdoc-plugin-1.4
[] maven-jalopy-plugin-1.4
[] maven-javadoc-plugin-1.8
[] maven-native-plugin-1.2
They all have still a few issues open, mainly feature
Plugin-configuration editor for POM editor
--
Key: MNGECLIPSE-40
URL: http://jira.codehaus.org/browse/MNGECLIPSE-40
Project: Maven 2.x Plug-in for Eclipse
Type: New Feature
Components: POM Editor
Reporter: Eugene
[ http://jira.codehaus.org/browse/MNGECLIPSE-39?page=all ]
Eugene Kuleshov updated MNGECLIPSE-39:
--
Component: POM Editor
POM editor
--
Key: MNGECLIPSE-39
URL: http://jira.codehaus.org/browse/MNGECLIPSE-39
[ http://jira.codehaus.org/browse/MNGECLIPSE-37?page=all ]
Eugene Kuleshov reopened MNGECLIPSE-37:
---
From the m2plugin mail list:
http://m2eclipse.codehaus.org/ seems to work, but the message I attached still
persists if the plug-in has
already
[ http://jira.codehaus.org/browse/MNGECLIPSE-37?page=all ]
Eugene Kuleshov updated MNGECLIPSE-37:
--
Component: Documentation
We will update documentation (flash demo) when time permit.
If you like, you can submit a bug to Eclipse's Update Manager
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=all ]
Jesse Kuhnert updated MSUREFIRE-23:
---
Attachment: surefire-patch.txt
Support TestNG
--
Key: MSUREFIRE-23
URL: http://jira.codehaus.org/browse/MSUREFIRE-23
[ http://jira.codehaus.org/browse/MPJAVADOC-50?page=comments#action_55732 ]
Bernard Durfee commented on MPJAVADOC-50:
-
I had the same problem, turns out I had renamed my package structure, but not
updated the 'package' element in the POM. That fixed
filtering element in pom.xml ignore properties
--
Key: MRESOURCES-9
URL: http://jira.codehaus.org/browse/MRESOURCES-9
Project: Maven 2.x Resources Plugin
Type: Bug
Environment: Maven 2.0.1
Reporter: Daniel Kulp
[ http://jira.codehaus.org/browse/MPJIRA-17?page=all ]
Lukas Theussl closed MPJIRA-17:
---
Resolution: Fixed
Plugin uses deprecated API to retrieve JIRA issues
--
Key: MPJIRA-17
URL:
Updated xfire jar isn't being copied
Key: MEV-292
URL: http://jira.codehaus.org/browse/MEV-292
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Dan Diephouse
I had to update a bad copy of a jar I
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060113.193001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060113.193001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MNG-897?page=all ]
John Casey closed MNG-897:
--
Resolution: Fixed
Fix Version: 2.0.1
forgot to close this. See documentation at
http://maven.apache.org/guides/index.html, under developer documentation or
plugin
allow empty deprecation messages in plugin descriptor/annotation and document
usage of deprecation in descriptor/annotation.
Key: MNG-1962
URL:
[ http://jira.codehaus.org/browse/MNGECLIPSE-26?page=comments#action_55736
]
Dmitri Maximovich commented on MNGECLIPSE-26:
-
Leonardo,
First of all, as you noted this is not (less of) an issue with m2 build
preocess runner, because you can
I've renamed the lifecycle phases that decorate the integration-test
phase, from before- and after- to pre- and post-integration-test.
The newest build from with this change is at:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060113.151503.tar.gz
This is our new
[ http://jira.codehaus.org/browse/MNGECLIPSE-26?page=comments#action_55738
]
Eugene Kuleshov commented on MNGECLIPSE-26:
---
Also note that we should support per-project configuration and it seems the
only way to do this with maven is to actually
[ http://jira.codehaus.org/browse/MPCHANGELOG-80?page=comments#action_55740
]
Lukas Theussl commented on MPCHANGELOG-80:
--
Thanks for your contribution Christoph!
There are two things missing before we can apply your patch:
- some test cases that
Antlib attempts to download version.txt files from legacy repository.
-
Key: MNG-1963
URL: http://jira.codehaus.org/browse/MNG-1963
Project: Maven 2
Type: Bug
Components: Ant tasks
No means of preventing ant task from querying repo1.maven.org
-
Key: MNG-1964
URL: http://jira.codehaus.org/browse/MNG-1964
Project: Maven 2
Type: Bug
Components: Ant tasks
Versions: 2.0
Don't try to download SNAPSHOTs built in the same build
---
Key: MAVEN-1738
URL: http://jira.codehaus.org/browse/MAVEN-1738
Project: Maven
Type: Improvement
Components: core
Versions: 1.1-beta-2
[ http://jira.codehaus.org/browse/MNG-1390?page=comments#action_55741 ]
Grégory Joseph commented on MNG-1390:
-
I'm running into a similar issue with MOJO-239 :
My mojo is bound to the generate-sources phase, and if it adds a source root
with
[ http://jira.codehaus.org/browse/MPJAR-52?page=comments#action_55743 ]
Anna Nicotera commented on MPJAR-52:
Correction: It seems 1.6.1 has the problem too.
It seems the only way to set the manifest attributes (at least for
Implementation-Version) is
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=comments#action_55744
]
Matthew Beermann commented on MNGECLIPSE-22:
Any chance that it could be put into the scope? Heck, I'd even put a bounty on
it if that's what it takes. Our
+1
Vincent
2006/1/12, Lukas Theussl [EMAIL PROTECTED]:
Hi,
Here are some more m1 plugins that I would be ready to release:
[] maven-html2xdoc-plugin-1.4
[] maven-jalopy-plugin-1.4
[] maven-javadoc-plugin-1.8
[] maven-native-plugin-1.2
They all have still a few issues open, mainly
Vincent Massol wrote:
Yes you're right this is required (compiling, resources, packaging, etc).
For packaging I can provide an example. Imagine you're using Cactus. There's
a need to cactify the runtime WAR/EAR by adding Cactus jars inside WAR/EAR
and modifying deployment descriptors to add
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=comments#action_55745
]
Eugene Kuleshov commented on MNGECLIPSE-22:
---
We can't promise anything. It would help if you can manage to create patch or
at least capture compilation errors, save them
John Casey wrote:
I'm +1 for moving maven-archiver there. If you're talking about
maven-plugin-tools-ant|model|... then I'm -1, since these constitute
core features of maven (things we brag about in maven releases :)
We don't brag about producing jars/wars/ears? :)
The only reason I pointed
Dan,
I think this was by design. Was there a JIRA issue related to this? Can
you check SVN history to confirm it wasn't changed to that for a reason?
- Brett
[EMAIL PROTECTED] wrote:
Author: dantran
Date: Thu Jan 12 22:34:08 2006
New Revision: 368614
URL:
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=all ]
Matthew Beermann updated MNGECLIPSE-22:
---
Attachment: eclipse30_build_errors.JPG
The Plug-In fails to run under Eclipse 3.0.x and IBM Rational Developer (RAD)
md5 file generation
---
Key: MINSTALL-9
URL: http://jira.codehaus.org/browse/MINSTALL-9
Project: Maven 2.x Install Plugin
Type: Wish
Versions: 2.2
Reporter: ruel loehr
It would be nice if the install plugin created md5 files for both
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=comments#action_55750
]
Eugene Kuleshov commented on MNGECLIPSE-22:
---
Matthew, can you please just select these errors in a problems view, copy and
then paste to the text file.
The Plug-In
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=all ]
Matthew Beermann updated MNGECLIPSE-22:
---
Attachment: eclipse30_build_errors.txt
The Plug-In fails to run under Eclipse 3.0.x and IBM Rational Developer (RAD)
[ http://jira.codehaus.org/browse/MPECLIPSE-60?page=all ]
Stephane Nicoll resolved MPECLIPSE-60:
--
Resolution: Fixed
OK ; It is resolved (finally!).
The plugin downloads source archives from the remote repository. This could be
disabled, see
[ http://jira.codehaus.org/browse/MAVEN-1653?page=all ]
Lukas Theussl closed MAVEN-1653:
Resolution: Fixed
Executing the pom:validate goal on a reconstituted project.xml file using
the content from the ten minute test page produces error
[ http://jira.codehaus.org/browse/MSUREFIRE-23?page=all ]
Jesse Kuhnert updated MSUREFIRE-23:
---
Attachment: surefire-patch.txt
Support TestNG
--
Key: MSUREFIRE-23
URL: http://jira.codehaus.org/browse/MSUREFIRE-23
[ http://jira.codehaus.org/browse/MAVEN-1602?page=all ]
Lukas Theussl closed MAVEN-1602:
Resolution: Fixed
Fixed with MAVEN-1653
Directory structure for xdocs inconsistent in ten-minute-test.xml
[ http://jira.codehaus.org/browse/MPSCM-63?page=comments#action_55757 ]
Dennis Lundberg commented on MPSCM-63:
--
What is the correct way to handle this. I have found the source of the
Exception in maven-release-plugin, but I'm unsure how to handle it.
[ http://jira.codehaus.org/browse/MPSCM-62?page=comments#action_55758 ]
Dennis Lundberg commented on MPSCM-62:
--
scm:update does not use maven.scm.tag at all.
Please close this issue.
Update documentation for maven.scm.tag and scm:update to reflect
[ http://jira.codehaus.org/browse/MPSCM-63?page=comments#action_55759 ]
Lukas Theussl commented on MPSCM-63:
You can use the jelly:catch tag
(http://jakarta.apache.org/commons/jelly/tags.html). There are examples for its
use in the jira, dashboard,
[ http://jira.codehaus.org/browse/MPSCM-70?page=comments#action_55762 ]
Dennis Lundberg commented on MPSCM-70:
--
I have tried this and everything seems to work as it should. Maven is no longer
available in the cvs repository, so I used another (small)
[ http://jira.codehaus.org/browse/MPSCM-62?page=all ]
Lukas Theussl closed MPSCM-62:
--
Resolution: Incomplete
Please provide more information if you think there is something wrong.
Update documentation for maven.scm.tag and scm:update to reflect
[ http://jira.codehaus.org/browse/MPSCM-60?page=comments#action_55764 ]
Dennis Lundberg commented on MPSCM-60:
--
Running this as the reporter suggests
maven scm:parse-connection -DscmConnection=scm:cvs:pserver:[EMAIL
PROTECTED]:port:cvsroot:module
__
[ http://jira.codehaus.org/browse/MPSCM-30?page=comments#action_55766 ]
Dennis Lundberg commented on MPSCM-30:
--
maven-scm does not have support for the export command at the moment. Adding a
new goal scm:export would mean changes to maven-scm as well.
Upgrade to Jakarta Commons HttpClient 3.0.
--
Key: MAVEN-1739
URL: http://jira.codehaus.org/browse/MAVEN-1739
Project: Maven
Type: Improvement
Components: core
Versions: 1.0.2, 1.1-beta-1, 1.1-beta-2
Reporter:
[ http://jira.codehaus.org/browse/MPSCM-70?page=comments#action_55767 ]
Lukas Theussl commented on MPSCM-70:
I misunderstood this issue: it really belongs into the xdoc plugin. What the
reporter wants to say is that the instructions generated on the
[ http://jira.codehaus.org/browse/MPXDOC-187?page=all ]
Lukas Theussl moved MPSCM-70 to MPXDOC-187:
---
Key: MPXDOC-187 (was: MPSCM-70)
Project: maven-xdoc-plugin (was: maven-scm-plugin)
Fix Anonymous Access with Maven
[ http://jira.codehaus.org/browse/MPXDOC-187?page=all ]
Lukas Theussl updated MPXDOC-187:
-
Fix Version: 1.10
Fix Anonymous Access with Maven
---
Key: MPXDOC-187
URL:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060114.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060114.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MPSCM-60?page=comments#action_55768 ]
Lukas Theussl commented on MPSCM-60:
Dennis, is this feature documented somewhere on the scm plugin site? If not,
can you attach a patch?
Support to non default port in cvs
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060114.003002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
OSGi R4 core
Key: MAVENUPLOAD-680
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-680
Project: maven-upload-requests
Type: Task
Reporter: Alan Cabrera
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly
OSGi R4 compendium
--
Key: MAVENUPLOAD-681
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-681
Project: maven-upload-requests
Type: Task
Reporter: Alan Cabrera
--
This message is automatically generated by JIRA.
-
If you think it was sent
[ http://jira.codehaus.org/browse/MPLINKCHECK-10?page=all ]
Arnaud Heritier closed MPLINKCHECK-10:
--
Resolution: Fixed
Fixed with MPLINKCHECK-25
allo 303 and 304 http status to be validated
[ http://jira.codehaus.org/browse/MPLINKCHECK-25?page=all ]
Arnaud Heritier closed MPLINKCHECK-25:
--
Resolution: Fixed
Improve reporting adding more informations
--
Key: MPLINKCHECK-25
[ http://jira.codehaus.org/browse/MAVEN-1739?page=all ]
Arnaud Heritier closed MAVEN-1739:
--
Resolution: Fixed
Upgrade to Jakarta Commons HttpClient 3.0.
--
Key: MAVEN-1739
URL:
[ http://jira.codehaus.org/browse/MPLINKCHECK-24?page=all ]
Arnaud Heritier closed MPLINKCHECK-24:
--
Resolution: Fixed
Speed and stability enhancement [better usage of httpClient].
-
1 - 100 of 129 matches
Mail list logo