Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051108.093002.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051108.093002.txt
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051108.213000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051108.213000.txt
build breaks when updating project info
---
Key: CONTINUUM-429
URL: http://jira.codehaus.org/browse/CONTINUUM-429
Project: Continuum
Type: Bug
Components: continuum-site
Versions: 1.0
Environment: - Windows XP / Linux
[ http://jira.codehaus.org/browse/CONTINUUM-429?page=all ]
Emmanuel Venisse closed CONTINUUM-429:
--
Resolution: Duplicate
fixed with CONTINUM-391
build breaks when updating project info
---
Key:
[ http://jira.codehaus.org/browse/CONTINUUM-429?page=all ]
Emmanuel Venisse updated CONTINUUM-429:
---
Comment: was deleted
build breaks when updating project info
---
Key: CONTINUUM-429
URL:
[ http://jira.codehaus.org/browse/CONTINUUM-429?page=comments#action_50418
]
Emmanuel Venisse commented on CONTINUUM-429:
fixed with CONTINUUM-391
build breaks when updating project info
---
Key:
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Jerome Lacoste updated MNG-1130:
Attachment: MNG-1130_jar-sign-verify.diff
Updated patch.
Support jar signing.
Key: MNG-1130
URL:
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Jerome Lacoste updated MNG-1130:
Attachment: MNG-1130_jar-sign-verify.diff
Even better when I don't forget the documentation... Updated the updated patch.
Support jar signing.
[ http://jira.codehaus.org/browse/MNG-1355?page=all ]
Edwin Punzalan updated MNG-1355:
Attachment: MNG-1355-maven-project.patch
I'm attaching a fix to prevent the infinite loop and also improve the
validation of the project descriptor.
Infinity Loop
[ http://jira.codehaus.org/browse/MNG-1355?page=all ]
Edwin Punzalan updated MNG-1355:
Attachment: (was: MNG-1355-maven-project.patch)
Infinity Loop in DefaultMavenProjectBuilder.assembleLineage
Surefire XML Report not well formed on NPE
--
Key: MNG-1454
URL: http://jira.codehaus.org/browse/MNG-1454
Project: Maven 2
Type: Bug
Components: maven-surefire-plugin
Versions: 2.0
Reporter: Kenney Westerhof
[ http://jira.codehaus.org/browse/MNG-1355?page=all ]
Edwin Punzalan updated MNG-1355:
Attachment: MNG-1355-maven-project.patch
Infinity Loop in DefaultMavenProjectBuilder.assembleLineage
---
brett,
svn properties ;-)
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: brett
Date: Tue Nov 8 00:08:58 2005
New Revision: 331723
URL: http://svn.apache.org/viewcvs?rev=331723view=rev
Log:
add preliminary testimonials
Added:
maven/site/trunk/src/site/apt/testimonials.apt (with props)
[ http://jira.codehaus.org/browse/MNG-1379?page=comments#action_50291 ]
fabrizio giustina commented on MNG-1379:
The eclipse plugin in svn has been modified by replacing the path for
system-scope artifacts with the path returned by
[ http://jira.codehaus.org/browse/MEV-185?page=comments#action_50292 ]
Fabrice BELLINGARD commented on MEV-185:
Avalon, Logkit and Log4J are not required when using commons-logging. That's
why they need to be set as optional.
And I read a post from
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/08-Nov-2005_04.30.47/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
[ http://jira.codehaus.org/browse/MEV-183?page=comments#action_50293 ]
Yann Le Du commented on MEV-183:
The changes are not effective on ibiblio... Maybe the directories need a
touch or something ?
Move common-test to its correct directory
Incorrect license type listed for SVN on Maven SCM site
---
Key: SCM-70
URL: http://jira.codehaus.org/browse/SCM-70
Project: Maven SCM
Type: Bug
Environment: Any
Reporter: Harald Ommang
Priority: Trivial
[ http://jira.codehaus.org/browse/MEV-183?page=comments#action_50296 ]
Edwin Punzalan commented on MEV-183:
May take up to 4hours from time of commit.
Move common-test to its correct directory
-
Key:
[ http://jira.codehaus.org/browse/MNG-1408?page=comments#action_50308 ]
Steve Metcalfe commented on MNG-1408:
-
I've had this problem too. Here's what i've found:
Line 207 of DependenciesTask: filename = localRepo.pathOf(artifact)
Returns (in my case):
[
http://jira.codehaus.org/browse/MPANNOUNCEMENT-19?page=comments#action_50310 ]
Felipe Leme commented on MPANNOUNCEMENT-19:
---
On a second thought, there are more places where those restrictions should be
ignored - for instance, if the project
[ http://jira.codehaus.org/browse/MNG-1158?page=comments#action_50313 ]
Dave Sag commented on MNG-1158:
---
this error in the PMD plugin is a blocker for me. also i need a way to get PMD
to generate XML output.
PMD should use sensible default rulesets
[ http://jira.codehaus.org/browse/MNG-1430?page=comments#action_50315 ]
Dan Allen commented on MNG-1430:
I don't believe that the plugin should leave out the project natures and
builders simply because they *might* change. What is to say that the natures
[ http://jira.codehaus.org/browse/MNG-1158?page=comments#action_50314 ]
Dave Sag commented on MNG-1158:
---
Looking at the src of PMD's ant plugin it doesn't seem too hard to bring the
maven 2 plugin up to speed.
[ http://jira.codehaus.org/browse/MPANNOUNCEMENT-19?page=all ]
Felipe Leme closed MPANNOUNCEMENT-19:
-
Resolution: Fixed
Failing when the version is missing should be optional
--
[
http://jira.codehaus.org/browse/MPANNOUNCEMENT-5?page=comments#action_50318 ]
Felipe Leme commented on MPANNOUNCEMENT-5:
--
Gary,
Do you mean the message should have an a href tag pointing to the issue, as
it happens on the changes-reports.html?
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/08-Nov-2005_08.30.39/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
Possible NPE in DefaultArtifactResolver
---
Key: MNG-1455
URL: http://jira.codehaus.org/browse/MNG-1455
Project: Maven 2
Type: Bug
Components: maven-artifact
Versions: 2.0
Environment: Ubuntu /Windows 2000
skipping tests faq
--
Key: MNG-1456
URL: http://jira.codehaus.org/browse/MNG-1456
Project: Maven 2
Type: New Feature
Reporter: Matthew Pocock
Priority: Trivial
Could we have an faq entry that says which -D option to set to skip tests?
Missing dependencies for slide-webdavlib
Key: MEV-190
URL: http://jira.codehaus.org/browse/MEV-190
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Mark Hobson
Unsure who's responsible for this
Xdoclet refers to missing version of commons-logging
Key: MEV-191
URL: http://jira.codehaus.org/browse/MEV-191
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: mike perham
[ http://jira.codehaus.org/browse/MNG-1171?page=comments#action_50324 ]
Jason van Zyl commented on MNG-1171:
The standard naming convention is maven-foo-plugin and we've been using it
for a long time.
I wish there was a recommended way of naming
[ http://jira.codehaus.org/browse/MNG-1171?page=all ]
Jason van Zyl closed MNG-1171:
--
Resolution: Fixed
I wish there was a recommended way of naming plugins
Key: MNG-1171
URL:
[ http://jira.codehaus.org/browse/MNG-1171?page=comments#action_50325 ]
Vincent Massol commented on MNG-1171:
-
Hi Jason,
AFAIK the naming convention for external plugins is *-maven-plugin and not
maven-*-plugin which is reserved for the maven-provided
when a schedule is disabled or deleted, it continue to run until I restart
continuum
Key: CONTINUUM-428
URL: http://jira.codehaus.org/browse/CONTINUUM-428
Project: Continuum
Type:
[ http://jira.codehaus.org/browse/CONTINUUM-428?page=all ]
Emmanuel Venisse closed CONTINUUM-428:
--
Resolution: Fixed
Fixed.
when a schedule is disabled or deleted, it continue to run until I restart
continuum
[ http://jira.codehaus.org/browse/CONTINUUM-378?page=all ]
Emmanuel Venisse closed CONTINUUM-378:
--
Resolution: Cannot Reproduce
Fix Version: (was: 1.0.1)
I can't reproduce it. I think your problem was due to a non deletion of
maven embedder completely offline on request.
-
Key: MNG-1457
URL: http://jira.codehaus.org/browse/MNG-1457
Project: Maven 2
Type: Bug
Components: maven-embedder
Reporter: Milos Kleint
I'm using the embedder to
[ http://jira.codehaus.org/browse/MNG-1457?page=comments#action_50329 ]
Milos Kleint commented on MNG-1457:
---
when the data loads I need to be able to figure that something is not really
correct with the setup. Example:
To display dependencies of the
error/warning handling in embedder
---
Key: MNG-1458
URL: http://jira.codehaus.org/browse/MNG-1458
Project: Maven 2
Type: Bug
Components: maven-embedder
Reporter: Milos Kleint
Error messaging. I have no idea how to handle
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051108.153001.txt
guide for creating ejb and corresponding ejb client JAR
---
Key: MNG-1459
URL: http://jira.codehaus.org/browse/MNG-1459
Project: Maven 2
Type: Task
Components: documentation - guides
Reporter: Jason van Zyl
tar.bz2 gives error on untar
Key: MNG-1460
URL: http://jira.codehaus.org/browse/MNG-1460
Project: Maven 2
Type: Bug
Versions: 2.0
Environment: Mac OS X 10.3.9 with tar installed by Fink
Reporter: Jan Dockx
Priority:
[ http://jira.codehaus.org/browse/CONTINUUM-407?page=all ]
Emmanuel Venisse updated CONTINUUM-407:
---
Description:
screen after DeleteNotifier, AddNotifier and similar actions of the project
View page should return you to the project view page, not
Unfortunately this has the side effect of requiring the user to generate
the manifest.mf by hand since m2 cannot discriminate between truly
provided dependencies like j2ee.jar and dependencies marked as provided
just to exclude them from the war. I would prefer to see a solution
which allows for
[ http://jira.codehaus.org/browse/MNG-1320?page=comments#action_50331 ]
John Casey commented on MNG-1320:
-
I updated the behavior on TransferFailedException only, so when the resource
simply 404's on the remote side, it should still be fine.
Build failed
[ http://jira.codehaus.org/browse/MNG-1320?page=all ]
John Casey updated MNG-1320:
Description:
Build failed due to an empty or corrupt metadata file in the repository.
Possibly had a network error whilst downloading the metadata file. The stack
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051108.160001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051108.160001.txt
[ http://jira.codehaus.org/browse/MNG-1038?page=comments#action_50334 ]
Fabrice BELLINGARD commented on MNG-1038:
-
It seems that the patch hasn't been applied yet... When will the war plugin be
released with these bug fixes? It is still in beta
[ http://jira.codehaus.org/browse/MNG-1320?page=all ]
John Casey closed MNG-1320:
---
Resolution: Fixed
the private resolveAlways(..) method throws TransferFailedException after
blacklisting the repository. When caught in the resolve(..) method, this
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051108.163000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051108.163000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[ http://jira.codehaus.org/browse/MNG-1171?page=comments#action_50340 ]
Brian Bonner commented on MNG-1171:
---
FWIW, When I opened this up, I had only been working with Maven2 for a little
while and Maven2 was still in Beta3. Since then, I've observed what
[ http://jira.codehaus.org/browse/MEV-192?page=all ]
Tomislav Stojcevich updated MEV-192:
Attachment: axis-1.3.pom.patch
Here is the patch file with the dependencies.
AXIS 1.3 is missing dependencies
AXIS 1.3 is missing dependencies
Key: MEV-192
URL: http://jira.codehaus.org/browse/MEV-192
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Tomislav Stojcevich
Attachments: axis-1.3.pom.patch
--
EAR plugin ignores application XML setting
--
Key: MNG-1461
URL: http://jira.codehaus.org/browse/MNG-1461
Project: Maven 2
Type: Bug
Components: maven-ear-plugin
Versions: 2.0
Reporter: mike perham
In
assembly:assembly forks a lifecycle and cannot be used in a reactor
environment. Need a new mojo suitable for this environment,
---
Key: MNG-1462
URL:
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/08-Nov-2005_12.30.52/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
best practices: plugin inheritance for a multi project build
Key: MNG-1463
URL: http://jira.codehaus.org/browse/MNG-1463
Project: Maven 2
Type: Task
Components: best practices
Reporter: Jason van
Eclipse loses Sysdeo Is Tomcat Project setting after mvn eclipse:eclipse
--
Key: MNGECLIPSE-5
URL: http://jira.codehaus.org/browse/MNGECLIPSE-5
Project: Maven 2.x Plug-in for Eclipse
Type: Bug
[ http://jira.codehaus.org/browse/MPECLIPSE-106?page=all ]
Eugene Kuleshov moved MNGECLIPSE-5 to MPECLIPSE-106:
Key: MPECLIPSE-106 (was: MNGECLIPSE-5)
Project: maven-eclipse-plugin (was: Maven 2.x Plug-in for Eclipse)
[ http://jira.codehaus.org/browse/MNG-1462?page=all ]
Jerome Lacoste updated MNG-1462:
Attachment: MNG-1462-attached_mojo_for_assembly_plugin.diff
This fixes it for me. I just moved all the code to an abstract class, and
created a new mojo with the
Is this correct? This is obviously an m2 plugin issue, so why did you
move it to MPECLIPSE?
-Lukas
Eugene Kuleshov (JIRA) wrote:
[ http://jira.codehaus.org/browse/MPECLIPSE-106?page=all ]
Eugene Kuleshov moved MNGECLIPSE-5 to MPECLIPSE-106:
[ http://jira.codehaus.org/browse/MRM-25?page=all ]
Carlos Sanchez moved MNG-1383 to MRM-25:
Component: (was: repository-tools)
Complexity: (was: Intermediate)
Workflow: jira (was: Maven)
Key: MRM-25 (was: MNG-1383)
[ http://jira.codehaus.org/browse/MRM-25?page=all ]
Carlos Sanchez updated MRM-25:
--
Description:
The attached patches will allow uploading of java sources to m1/m2 repositories
Patches for:
- deploy-bundle: handles upload bundles with sources and move
[ http://jira.codehaus.org/browse/SCM-67?page=all ]
Dan Tran updated SCM-67:
Attachment: SCM-67.diff
Patch
Ability to remove none scm files during scm:update command
--
Key: SCM-67
Javadoc:jar goal executes for non-Java projects
---
Key: MNG-1464
URL: http://jira.codehaus.org/browse/MNG-1464
Project: Maven 2
Type: Bug
Components: maven-javadoc-plugin
Reporter: David Jackman
Attachments:
[ http://jira.codehaus.org/browse/MNG-1310?page=all ]
John Casey updated MNG-1310:
Description:
What about adding a installtrue/install to the config to install all
produced artifacts (as AttachedArtifacts) ?
Feel free to also review MNG-1251 as I
[ http://jira.codehaus.org/browse/MNG-1463?page=comments#action_50349 ]
Wim Deblauwe commented on MNG-1463:
---
This is the mail of Chris:
Greetings,
I am looking for guidance on POM inheritance. I know that I can set up a
build system where all common
[ http://jira.codehaus.org/browse/SCM-63?page=all ]
Dan Tran updated SCM-63:
Attachment: SCM-63.diff
refactor checkout mojo and have bootrap mojo the inherit and call the checkout
method
Missing scm:bootstrap mojo
[ http://jira.codehaus.org/browse/MNG-1310?page=comments#action_50351 ]
John Casey commented on MNG-1310:
-
Just reading the attached patch...why do we want to stop using assembly.getId()
as a classifier for the attached artifact?
Support installation of
Maven not able to find setter for MavenProjectHelper property
-
Key: MNG-1465
URL: http://jira.codehaus.org/browse/MNG-1465
Project: Maven 2
Type: Bug
Reporter: David Jackman
This might really be a
[ http://jira.codehaus.org/browse/MNG-1461?page=comments#action_50352 ]
Stephane Nicoll commented on MNG-1461:
--
You are right, it's not used anywhere.
As a workaround:
#1 Check the documentation:
[ http://jira.codehaus.org/browse/MNG-1444?page=comments#action_50353 ]
Stephane Nicoll commented on MNG-1444:
--
You are right, thanks for reporting this to us.
Need to include DirectoryScanner in EAR plugin ; I'll take care of that.
excluding
[ http://jira.codehaus.org/browse/MEV-182?page=all ]
Carlos Sanchez closed MEV-182:
--
Assign To: Carlos Sanchez
Resolution: Duplicate
MEV-110
Replace ${pom.currentVersion} with ${pom.version} in apache-ldapber-provider
[ http://jira.codehaus.org/browse/MEV-181?page=all ]
Carlos Sanchez closed MEV-181:
--
Assign To: Carlos Sanchez
Resolution: Duplicate
MEV-110
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
[ http://jira.codehaus.org/browse/MEV-180?page=all ]
Carlos Sanchez closed MEV-180:
--
Assign To: Carlos Sanchez
Resolution: Duplicate
MEV-110
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
[ http://jira.codehaus.org/browse/MNG-1461?page=comments#action_50357 ]
mike perham commented on MNG-1461:
--
Stephane, thanks. Unfortunately I'm limited by my IDE, IBM's Rational Software
Architect, to keeping the META-INF contents off the project basedir
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051108.194500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051108.194500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[ http://jira.codehaus.org/browse/MNG-1449?page=all ]
Giorgio Gallo reopened MNG-1449:
I'm very sorry to insist...
I didn't explained well: a jar file is generated even if there are no sources
or resources in the project.
Maven creates jar for a
[ http://jira.codehaus.org/browse/MNG-1461?page=comments#action_50360 ]
Stephane Nicoll commented on MNG-1461:
--
Mike,
If you are limited by you IDE (I don't get you on this BTW), change the
earSourceDirectory settings
[ http://jira.codehaus.org/browse/MNG-1449?page=all ]
Giorgio Gallo updated MNG-1449:
---
Attachment: MNG-1449.zip
Attached a .zip containing a maven project wich should not (IMHO) generate any
jar
Maven creates jar for a project without java sources
[ http://jira.codehaus.org/browse/MNG-1461?page=comments#action_50363 ]
Stephane Nicoll commented on MNG-1461:
--
Ok OK I got your problem. You have to place META-INF info in some src/some-dir.
I will see if I can do something about this too. You will
[ http://jira.codehaus.org/browse/MEV-192?page=all ]
Tomislav Stojcevich updated MEV-192:
Attachment: axis-1.3.pom.patch
Please use this second attached patch. The first was missing the
javax.activation which I don't use but somebody might.
AXIS
[ http://jira.codehaus.org/browse/MNG-1461?page=comments#action_50365 ]
mike perham commented on MNG-1461:
--
Well, RSA sees that myEar is an EAR project (via an eclipse nature in .project)
and expects the application.xml file to be in myEar/META-INF.
Ant dependencies task does not work with multiple repositories
--
Key: MNG-1466
URL: http://jira.codehaus.org/browse/MNG-1466
Project: Maven 2
Type: Bug
Components: maven-artifact-ant
Versions:
[ http://jira.codehaus.org/browse/CONTINUUM-407?page=all ]
Emmanuel Venisse closed CONTINUUM-407:
--
Resolution: Fixed
Fix Version: (was: 1.1)
1.0.1
Fixed.
screen after adding/removing a build definition or notifier
Support separate generation of WAR's manifest.mf
Key: MNG-1467
URL: http://jira.codehaus.org/browse/MNG-1467
Project: Maven 2
Type: New Feature
Components: maven-war-plugin
Versions: 2.0
Reporter: mike
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051108.203000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051108.203000.txt
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50370 ]
Jeff Lee commented on MAVENUPLOAD-578:
--
The official IBM product name is IBM Toolbox for Java, and the web page is
http://www.ibm.com/servers/eserver/iseries/toolbox/
The
eclipse:eclipse goal ignoring systemPath in scope system
Key: MPECLIPSE-107
URL: http://jira.codehaus.org/browse/MPECLIPSE-107
Project: maven-eclipse-plugin
Type: Bug
Environment: win XP, JDK 1.5, Maven 2
[ http://jira.codehaus.org/browse/MNG-1310?page=comments#action_50372 ]
Jerome Lacoste commented on MNG-1310:
-
I reran my build by disabling my patch to this issue and here's the results.
By keeping the assembly.getId(), the artifacts get deployed as
[ http://jira.codehaus.org/browse/SCM-67?page=all ]
Emmanuel Venisse closed SCM-67:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Applied.
Ability to remove none scm files during scm:update command
[ http://jira.codehaus.org/browse/MEV-185?page=all ]
Carlos Sanchez closed MEV-185:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Fixed in all the poms in the repo
commons-logging-1.0.4 POM dependencies not using optional properly
[ http://jira.codehaus.org/browse/SCM-63?page=all ]
Emmanuel Venisse closed SCM-63:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Applied. Thanks
Missing scm:bootstrap mojo
Key: SCM-63
URL:
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/08-Nov-2005_04.30.55/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL
[ http://jira.codehaus.org/browse/SCM-67?page=comments#action_50377 ]
Emmanuel Venisse commented on SCM-67:
-
Do we need to add this system property in continuum in DefaultContinuumScm?
Ability to remove none scm files during scm:update command
[ http://jira.codehaus.org/browse/SCM-70?page=all ]
Emmanuel Venisse closed SCM-70:
---
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0-beta-1
Fixed
Incorrect license type listed for SVN on Maven SCM site
best practices: version management in multi project builds
--
Key: MNG-1468
URL: http://jira.codehaus.org/browse/MNG-1468
Project: Maven 2
Type: Bug
Components: best practices
Reporter: Jason van Zyl
[ http://jira.codehaus.org/browse/MPECLIPSE-107?page=all ]
fabrizio giustina closed MPECLIPSE-107:
---
Assign To: fabrizio giustina
Resolution: Fixed
this is related to the m2 eclipse plugin
deplicate of the (fixed in svn) issue MNG-1324
Convert ${pom.currentVersion} to ${pom.version}
---
Key: MRM-26
URL: http://jira.codehaus.org/browse/MRM-26
Project: Maven Repository Manager
Type: Bug
Components: repository-converter
Versions: 1.0
1 - 100 of 130 matches
Mail list logo
