date:20080708


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

Vincent Siveton updated MPIR-111:
-

Summary: Make Classifier and Optional column in dependencies report 
optional in the renderer  (was: Make Classifier and Optional column in 
dependies report optional in the renderer)

 Make Classifier and Optional column in dependencies report optional in the 
 renderer
 -

 Key: MPIR-111
 URL: http://jira.codehaus.org/browse/MPIR-111
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Vincent Siveton
 Fix For: 2.1


 Actually, Classifier and Optional columns are always presents. It should be 
 better to add them only if they have different values.

-- 
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: (DOXIA-247) unable to parse document when the last character is '}'

2008-07-08 Thread David Delbecq (JIRA)

unable to parse document when the last character is '}'
---

 Key: DOXIA-247
 URL: http://jira.codehaus.org/browse/DOXIA-247
 Project: Maven Doxia
  Issue Type: Bug
Affects Versions: 1.0-alpha-11
Reporter: David Delbecq


When last character of a document is '}', maven doxia issues a, array out of 
bound exception. It tries to get next character to find out if we found a '}}' 
pair, but doesn't check bounds of document:
{code}
org.apache.maven.doxia.parser.ParseException: String index out of range: 14
at 
org.apache.maven.doxia.module.confluence.ConfluenceParser.parse(ConfluenceParser.java:139)

Caused by: java.lang.StringIndexOutOfBoundsException: String index out of 
range: 14
at java.lang.String.charAt(String.java:558)
at 
org.apache.maven.doxia.module.confluence.parser.ParagraphBlockParser.visit(ParagraphBlockParser.java:134)
at 
org.apache.maven.doxia.module.confluence.ConfluenceParser.parse(ConfluenceParser.java:103)
at 
org.apache.maven.doxia.module.confluence.ConfluenceParser.parse(ConfluenceParser.java:131)
{code}

testcase:
{code:title=AppTest.java|borderStyle=solid}
package org.apache.doxia.test.BUGTestCase;

import java.io.StringReader;

/**
 * Unit test for simple App.
 */
public class AppTest 
extends TestCase
{
/**
 * Create the test case
 *
 * @param testName name of the test case
 */
public AppTest( String testName )
{
super( testName );
}

/**
 * @return the suite of tests being tested
 */
public static Test suite()
{
return new TestSuite( AppTest.class );
}

/**
 * Rigourous Test :-)
 * @throws ParseException 
 */
public void testEndBracket() throws ParseException
{
String document = Test +
\n\n* list1+
\n\n* list2+
\n\n* list2+
\n{pre}123{/pre}; 
StringWriter writer = new StringWriter();
ConfluenceParser parser = new ConfluenceParser();
XhtmlSink sink = new XhtmlSink(writer);
/* parsing with additional space at end works*/
parser.parse(new StringReader(document+ ), sink);
assertTrue(generated document should have a size 
0,writer.toString().length()0);
/* parsing with document ending in } fails*/
try{
parser.parse(new StringReader(document), sink);
} catch (Exception e){
e.printStackTrace();
fail(parsing with document ending in } should not 
fails);
}
assertTrue(generated document should have a size 
0,writer.toString().length()0);
}
/**
 * Rigourous Test :-)
 * @throws ParseException 
 */
public void testEndBracketInList() throws ParseException
{
String document1 = Test +
\n\n* list1+
\n\n* list2+
\n\n* list2{pre}123{/pre} +
\n123;
String document2 = Test +
\n\n* list1+
\n\n* list2+
\n\n* list2{pre}123{/pre}+
\n123;
StringWriter writer = new StringWriter();
ConfluenceParser parser = new ConfluenceParser();
XhtmlSink sink = new XhtmlSink(writer);
/* parsing with additional space at end of list item works*/
parser.parse(new StringReader(document1), sink);
assertTrue(generated document should have a size 
0,writer.toString().length()0);
/* parsing with end of list item ending in } fails*/
try{
parser.parse(new StringReader(document2), sink);
} catch (Exception e){
e.printStackTrace();
fail(parsing with end of list item ending in } should 
not fails);
}
assertTrue(generated document should have a size 
0,writer.toString().length()0);
}
}
{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: (MECLIPSE-459) missing artifact references with pde mode enabled

2008-07-08 Thread Gopalakrishnan U (JIRA)

[
http://jira.codehaus.org/browse/MECLIPSE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141038#action_141038
]

Gopalakrishnan U commented on MECLIPSE-459:
---

Oops! Just figured out that the patch doesn't work. needs more work.

missing artifact references with pde mode enabled
-

Key: MECLIPSE-459
URL: http://jira.codehaus.org/browse/MECLIPSE-459
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path, PDE
support
Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1
Environment: Maven version: 2.0.9
Java version: 1.5.0_11
OS name: linux version: 2.6.15-51-686 arch: i386 Family: unix
Reporter: Benjamin Voigt
Priority: Critical
Attachments: pde_dep_missing.zip

Some artifacts are not referenced after executing mvn eclipse:eclipse and
having pde mode enabled. The strange thing is, that this does only happen for
particluar versions of an artifact.
Two artifacts that I found with this problem are jetty (org.mortbay.jetty)
and slf4j-log4j12 (org.slf4j-log4j12). Jetty versions beyond 6.1.5 work with
pde enabled, higher versions do not. Same for slf4j-log4j12 versions = 1.1.0.
Attached is an example project demonstrating the problem. Turn pde mode
on/off in the pom and execute mvn eclipse:eclipse.

[jira] Closed: (MPIR-111) Make Classifier and Optional column in dependencies report optional in the renderer


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

Vincent Siveton closed MPIR-111.


  Assignee: Vincent Siveton
Resolution: Fixed

fixed in r674775, snapshot deployed

 Make Classifier and Optional column in dependencies report optional in the 
 renderer
 -

 Key: MPIR-111
 URL: http://jira.codehaus.org/browse/MPIR-111
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Vincent Siveton
Assignee: Vincent Siveton
 Fix For: 2.1


 Actually, Classifier and Optional columns are always presents. It should be 
 better to add them only if they have different values.

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

[jira] Created: (MPIR-112) Dependency Listings is too big

Dependency Listings is too big
--

 Key: MPIR-112
 URL: http://jira.codehaus.org/browse/MPIR-112
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
  Components: dependencies
Affects Versions: 2.1
Reporter: Vincent Siveton
 Fix For: 2.1


We need to reduce the size of the Dependency Listings. 

-- 
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: (MPIR-112) Dependency Listings is too big


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

Vincent Siveton updated MPIR-112:
-

Fix Version/s: 2.1

 Dependency Listings is too big
 --

 Key: MPIR-112
 URL: http://jira.codehaus.org/browse/MPIR-112
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
  Components: dependencies
Affects Versions: 2.1
Reporter: Vincent Siveton
 Fix For: 2.1


 We need to reduce the size of the Dependency Listings. 

-- 
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-2141) Updated version of JSON Java code from www.json.org

2008-07-08 Thread Michael Tamm (JIRA)

Updated version of JSON Java code from www.json.org
---

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


There have been some changes since the last release: 
http://repo1.maven.org/maven2/org/json/json/20070829

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

[jira] Commented: (MNG-2205) provided scope dependencies must be transitive

2008-07-08 Thread Alexandre Sauve (JIRA)


[ 
http://jira.codehaus.org/browse/MNG-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141086#action_141086
 ] 

Alexandre Sauve commented on MNG-2205:
--

I think that 'provided' transitive dependencies are important!  The case that 
comes to my mind is OSGi and Eclipse development.  You need a certain 
class/package in order to compile your code; however that same package will be 
available on the runtime environment as a bundle.  You don't want to start 
adding this jar as an embed library into your bundle!  You want to embed only 
those that are runtime/compile dependencies.

However since 'provided' is NOT transitive you would have to list all the 
dependencies this bundle you depend on has in your POM!  Not exactly a step 
forward from Maven 1.  You would like to pull in these bundle dependencies just 
for the need of compilation (and actually you would what them in the manifest 
file too).

So in the end for OSGi and Eclipse transitive provided dependencies would be a 
really nice thing to have!

 provided scope dependencies must be transitive
 

 Key: MNG-2205
 URL: http://jira.codehaus.org/browse/MNG-2205
 Project: Maven 2
  Issue Type: Bug
  Components: Dependencies
Reporter: David Boden
Priority: Critical
 Fix For: 2.1


 A provided scope dependency can also be thought of as compile-only.
 Project A requires Sybase JConnect on the runtime classpath. Project A 
 declares a provided dependency on Sybase JConnect.
 Project B depends upon Project A. Project B declares a compile dependency 
 on Project A.
 Project C depends upon Project B. Project C declares a compile dependency 
 on Project B.
 C
 | - compile dependency
 B
 | - compile dependency
 A
 | - provided dependency
 Sybase JConnect
 So, does Project C transitively depend on Sybase JConnect. Yes, of course! 
 The provided dependency needs to be transitive.
 Ultimately, when Project C gets deployed, Sybase JConnect needs to be 
 somewhere on the runtime classpath in order for the application to function. 
 It's valid for Project C to assume that Sybase JConnect is available and use 
 JDBC all over the Project C code. Project C is safe to do this because it can 
 happily deduce that Sybase JConnect will be there in the runtime environment 
 because Project A NEEDS IT.
 I've got Use Cases all over my aggregated build which make it absolutely 
 critical and common sense that provided scope dependencies are transitive. 
 For the (very rare) odd case where you don't want to inherit provided 
 dependencies, you can exclude/ them.

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

[jira] Updated: (MNG-2873) Unable to find transitive dependencies when they have been relocated.

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

John Casey updated MNG-2873:

Fix Version/s: (was: 2.0.10)
2.0.11

pushing this until we can get a test to reliably reproduce it.

Unable to find transitive dependencies when they have been relocated.
-

Key: MNG-2873
URL: http://jira.codehaus.org/browse/MNG-2873
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.0.5
Reporter: Micah Whitacre
Fix For: 2.0.11

I have two projects A and B. Project A is dependent on B. Project B has
compile time on project C which is deployed to a repository, repository1.
The newest version, 2.0, of project C has since been relocated from
oldGroupId to newGroupId. The relocation POMs are working correctly and
Project B is able to be built successfully. Project A is not dependent on
anything from repository1 it does not list that repository in its own
repositories/ section. When building project A, it tries to resolve the
dependencies of B which includes C. However I am currently getting errors
when it tries to resolve the C. Below is an example of this error occurring.
As you can see the list of remote repositories does not display repository1
as one of the repositories that was checked despite the fact that Project B
listed it in its POM.
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.
No versions are present in the repository for the artifact with a range [1,)
oldGroupId:projectC:jar:null
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
repo2 (http://repo.some-repo.com/repo)
If I change project B to not use a range but to instead depend on a
non-relocated version of project C everything works fine and I do not get
this issue at all. The other and more correct solution to this issue is to
update project B to use the new groupIds however it forces me to release
project B immediately since all older released versions of B are broken by
using the old groupIds an this issue.

[jira] Work started: (MNG-3654) [regression] unable to build ServiceMix 3 - IndexOutOfBoundsException in mergeDeterministicBuildElements


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

Work on MNG-3654 started by John Casey.

 [regression] unable to build ServiceMix 3 - IndexOutOfBoundsException in 
 mergeDeterministicBuildElements
 

 Key: MNG-3654
 URL: http://jira.codehaus.org/browse/MNG-3654
 Project: Maven 2
  Issue Type: Bug
  Components: POM
Affects Versions: 2.0.10, 2.1-alpha-1
Reporter: Brett Porter
Assignee: John Casey
 Fix For: 2.0.10, 2.1-alpha-1


 in https://svn.apache.org/repos/asf/servicemix/smx3/trunk, run mvn compile.
 Result (before build begins):
 java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
   at java.util.ArrayList.RangeCheck(ArrayList.java:546)
   at java.util.ArrayList.get(ArrayList.java:321)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.mergeDeterministicBuildElements(DefaultMavenProjectBuilder.java:1112)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:998)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:879)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199)
   at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:576)
   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:459)
   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:532)
   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:532)
   at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:363)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)

-- 
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: (MDOCCK-12) @Override let QDOX fail for this plugin

2008-07-08 Thread Dennis Lundberg (JIRA)


[ 
http://jira.codehaus.org/browse/MDOCCK-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141093#action_141093
 ] 

Dennis Lundberg commented on MDOCCK-12:
---

Can you give us a sample file that we can use for testing?

 @Override let QDOX fail for this plugin
 ---

 Key: MDOCCK-12
 URL: http://jira.codehaus.org/browse/MDOCCK-12
 Project: Maven 2.x Documentation Checker Plugin
  Issue Type: Bug
Affects Versions: 1.0-beta-2
 Environment: Win XP 
Reporter: MTStorm
Priority: Minor

 The plugin fails when QDox hit @Override. Here is the stacktrace:
 [INFO] Trace
 com.thoughtworks.qdox.parser.ParseException: syntax error @[33,5] in  ...my 
 java file
 at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504)
 at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610)
 at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488)
 at 
 com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296)
 at 
 com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
 at 
 com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308)
 at 
 com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
 at 
 com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
 at 
 com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362)
 at 
 org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477)
 at 
 org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69)
 at 
 org.apache.maven.plugin.docck.CheckPluginDocumentationMojo.checkPackagingSpecificDocumentation(CheckPluginDocumentationMojo.java:67)
 at 
 org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.checkProject(AbstractCheckDocumentationMojo.java:319)
 at 
 org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.execute(AbstractCheckDocumentationMojo.java:149)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 [INFO] 
 
 [INFO] Total time: 12 seconds
 [INFO] Finished at: Wed Jun 04 10:40:35 CEST 2008
 [INFO] Final Memory: 10M/19M
 [INFO] 
 

-- 
This message is automatically generated by JIRA.
-
If you think it

[jira] Created: (MAVENUPLOAD-2142) Rsync XCluder repo

2008-07-08 Thread Manos Batsis (JIRA)

Rsync XCluder repo
--

 Key: MAVENUPLOAD-2142
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2142
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Manos Batsis
 Attachments: gr.abiss.xcluder.sh

Attached an sh script to rsync the xcluder release repo to maven central. 
Thanks!

Manos

-- 
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-3654) [regression] unable to build ServiceMix 3 - IndexOutOfBoundsException in mergeDeterministicBuildElements


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

John Casey closed MNG-3654.
---

Resolution: Fixed

 [regression] unable to build ServiceMix 3 - IndexOutOfBoundsException in 
 mergeDeterministicBuildElements
 

 Key: MNG-3654
 URL: http://jira.codehaus.org/browse/MNG-3654
 Project: Maven 2
  Issue Type: Bug
  Components: POM
Affects Versions: 2.0.10, 2.1-alpha-1
Reporter: Brett Porter
Assignee: John Casey
 Fix For: 2.0.10, 2.1-alpha-1


 in https://svn.apache.org/repos/asf/servicemix/smx3/trunk, run mvn compile.
 Result (before build begins):
 java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
   at java.util.ArrayList.RangeCheck(ArrayList.java:546)
   at java.util.ArrayList.get(ArrayList.java:321)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.mergeDeterministicBuildElements(DefaultMavenProjectBuilder.java:1112)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:998)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:879)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:507)
   at 
 org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:199)
   at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:576)
   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:459)
   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:532)
   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:532)
   at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:363)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)

-- 
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] Work started: (MNG-3511) Review fix for MNG-2166

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

Work on MNG-3511 started by John Casey.

Review fix for MNG-2166
---

Key: MNG-3511
URL: http://jira.codehaus.org/browse/MNG-3511
Project: Maven 2
Issue Type: Improvement
Components: Command Line
Affects Versions: 2.0.8
Reporter: Benjamin Bentmann
Assignee: John Casey
Priority: Minor
Fix For: 2.0.10

Attachments: no-goal-help.patch

As requested by Brett in MNG-3276, here a new issue. My relevant comment over
at the other issue:
I still consider the output from Maven quite unhelpful in this case. Please
consider that Maven is just a tool/utility for developers and hence not
everybody out there will spend time to get through the documentation. Some
peoply simply want to use Maven, not understand how it works.
The Ant scripts that I am trying to replace in our organization all provided
some help about the current project and the available targets using the echo
task when the default target was executed. This allowed newbies to quickly
figure out how to perform build steps without ever reading the Ant manual.
Surely, once you know Maven's lifecycle you never need such help targets but
especially old Ant geeks need some easy way of migrating into Maven land.
The attached patch should provide the following console output:
{noformat}
[INFO] Scanning for projects...
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO]
You must specify at least one goal or lifecycle phase to perform build steps.
The following list illustrates some commonly used build commands:
mvn clean
Deletes any build output (e.g. class files or JARs).
mvn test
Runs the unit tests for the project.
mvn install
Copies the project artifacts into your local repository.
mvn deploy
Copies the project artifacts into the remote repository.
mvn site
Creates project documentation (e.g. reports or Javadoc).
Please see
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
for a complete description of available lifecycle phases.
Use mvn -? to show general usage information about Maven's command line.
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 1 second
[INFO] Finished at: Mon Oct 22 20:48:42 EDT 2007
[INFO] Final Memory: 1M/4M
[INFO]

{noformat}
This output is intended to show further comon use-cases than just install.
Besides, the user is pointed to a concrete URL with helpful information for
his actual need (personally, I consider pointing people at home pages as
helpful as telling to use Google... information should be found, not searched)

[jira] Closed: (MNG-3511) Review fix for MNG-2166

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

John Casey closed MNG-3511.
---

Resolution: Fixed
Fix Version/s: 2.1-alpha-1

Review fix for MNG-2166
---

Attachments: no-goal-help.patch

[ERROR] BUILD FAILURE
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 1 second
[INFO] Finished at: Mon Oct 22 20:48:42 EDT 2007
[INFO] Final Memory: 1M/4M
[INFO]

[jira] Commented: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI

2008-07-08 Thread M. Rohrmoser (JIRA)

[
http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141113#action_141113
]

M. Rohrmoser commented on MSITE-159:

Workaround: replace one of the characters of the external/absolute URL with
it's url-encoded form, e.g. a . (dot) within the servername with %2e.

This seems to prevent substitution.

Absolute URI rendered as relative URI if absolute URI related to domain of
POM URI
--

Key: MSITE-159
URL: http://jira.codehaus.org/browse/MSITE-159
Project: Maven 2.x Site Plugin
Issue Type: Bug
Components: relative links
Reporter: Ted Husted

Under site-beta5
if the POM references a URI like
urlhttp://struts.apache.org/url
absolute URLs used in the site.xml file are converted to relative references.
For example a reference to to http://struts.apache.org/1.x; becomes 1.x,
and a reference to
just http://struts.apache.org; becomes an empty string.
If the documentation is being used offline, there are many cases when we want
to refer people back to the website, to be sure the current information is
used. The best use case is a download page that determines the mirror via
CGI.
Another use case is referring to a sister site in the domain, that might
refer to another version. If used locally, the other site might not be in the
relative location.
Switching back to beta4 cures the behavior, and absolute URIs remain
absolute, as expected.

[jira] Commented: (MASSEMBLY-144) wont put files in top level directory

2008-07-08 Thread Basil James Whitehouse III (JIRA)


[ 
http://jira.codehaus.org/browse/MASSEMBLY-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141116#action_141116
 ] 

Basil James Whitehouse III commented on MASSEMBLY-144:
--

I think this has to do with includeBaseDirectory being false and the output 
directory being / .

A workaround that I discovered is to set the output directory to . (dot):
{code:xml}
assembly
idbug-example/id
formats
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
files
file
sourceTODO.txt/source
outputDirectory./outputDirectory
/file
/files
/assembly
{code}

 wont put files in top level directory
 -

 Key: MASSEMBLY-144
 URL: http://jira.codehaus.org/browse/MASSEMBLY-144
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.1
 Environment: Windows XP using maven 2.0.4. I think I am using 
 assembly 2.1 as that is the only version I could find in my ~/.m2 directory.
Reporter: Alan Kent
Assignee: John Casey
Priority: Minor
 Fix For: 2.2-beta-1


 I am relatively new to Maven so hopefully this is not a silly mistake, but 
 the following assembly XML file will NOT include the TODO.txt file. If you 
 put the file into a subdirectory (using 
 outputDirectorya/b/c/outputDirectory or by setting 
 includeBaseDirectorytrue/includeBaseDirectory) then the file will appear 
 in the ZIP file. This is at least non-intuitive, but feels like a bug to me. 
 assembly
 idbug-example/id
 formats
 formatzip/format
 /formats
 includeBaseDirectoryfalse/includeBaseDirectory
 files
 file
 sourceTODO.txt/source
 outputDirectory//outputDirectory
 /file
 /files
 /assembly

-- 
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: (MARTIFACT-29) DefaultWagonManager checks all remote repositories

2008-07-08 Thread Igor Fedorenko (JIRA)

DefaultWagonManager checks all remote repositories
--

 Key: MARTIFACT-29
 URL: http://jira.codehaus.org/browse/MARTIFACT-29
 Project: Maven Artifact
  Issue Type: Bug
Affects Versions: 3.0-alpha-1
Reporter: Igor Fedorenko
 Attachments: martifact-unecessary-remote-lookup.diif

DefaultWagonManager will attempt to download artifact from all remote 
repositories even if the artifact is available from the first repository.

-- 
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: (MARTIFACT-29) DefaultWagonManager checks all remote repositories

2008-07-08 Thread Jason van Zyl (JIRA)


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

Jason van Zyl updated MARTIFACT-29:
---

Fix Version/s: 3.0-alpha-1

 DefaultWagonManager checks all remote repositories
 --

 Key: MARTIFACT-29
 URL: http://jira.codehaus.org/browse/MARTIFACT-29
 Project: Maven Artifact
  Issue Type: Bug
Affects Versions: 3.0-alpha-1
Reporter: Igor Fedorenko
Assignee: Jason van Zyl
 Fix For: 3.0-alpha-1

 Attachments: martifact-unecessary-remote-lookup.diif


 DefaultWagonManager will attempt to download artifact from all remote 
 repositories even if the artifact is available from the first repository.

-- 
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: (MARTIFACT-29) DefaultWagonManager checks all remote repositories

2008-07-08 Thread Jason van Zyl (JIRA)


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

Jason van Zyl closed MARTIFACT-29.
--

Resolution: Fixed

 DefaultWagonManager checks all remote repositories
 --

 Key: MARTIFACT-29
 URL: http://jira.codehaus.org/browse/MARTIFACT-29
 Project: Maven Artifact
  Issue Type: Bug
Affects Versions: 3.0-alpha-1
Reporter: Igor Fedorenko
Assignee: Jason van Zyl
 Fix For: 3.0-alpha-1

 Attachments: martifact-unecessary-remote-lookup.diif


 DefaultWagonManager will attempt to download artifact from all remote 
 repositories even if the artifact is available from the first repository.

-- 
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: (MARTIFACT-29) DefaultWagonManager checks all remote repositories

2008-07-08 Thread Jason van Zyl (JIRA)


[ 
http://jira.codehaus.org/browse/MARTIFACT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141132#action_141132
 ] 

Jason van Zyl commented on MARTIFACT-29:


Patch applied.

 DefaultWagonManager checks all remote repositories
 --

 Key: MARTIFACT-29
 URL: http://jira.codehaus.org/browse/MARTIFACT-29
 Project: Maven Artifact
  Issue Type: Bug
Affects Versions: 3.0-alpha-1
Reporter: Igor Fedorenko
Assignee: Jason van Zyl
 Fix For: 3.0-alpha-1

 Attachments: martifact-unecessary-remote-lookup.diif


 DefaultWagonManager will attempt to download artifact from all remote 
 repositories even if the artifact is available from the first repository.

-- 
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] Work started: (MNG-3380) MavenMetadataSource retrieves ResolutionGroup without consulting ManagedVersionMap, is problem when relocation


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

Work on MNG-3380 started by John Casey.

 MavenMetadataSource retrieves ResolutionGroup without consulting 
 ManagedVersionMap, is problem when relocation
 --

 Key: MNG-3380
 URL: http://jira.codehaus.org/browse/MNG-3380
 Project: Maven 2
  Issue Type: Bug
  Components: Dependencies
Affects Versions: 2.0.8
Reporter: luke w patterson
Assignee: John Casey
 Fix For: 2.0.10

 Attachments: MNG-3380-integration-test.zip, 
 MNG-3380-maven-artifact.patch, patch.txt, repo.zip


 Consider the following scenario:
 project
   modelVersion4.0.0/modelVersion
   groupIdroot-groupId/groupId
   artifactIdroot-artifactId/artifactId
   version1/version
   dependencies
 dependency
   groupIddirect-dependency-groupId/groupId
   artifactIddirect-dependency-artifactId/artifactId
   version1/version
 /dependency
   /dependencies
   dependencyManagement
 dependencies
   dependency
 groupIdtransitive-dependency-new-groupId/groupId
 artifactIdtransitive-dependency-artifactId/artifactId
 version2/version
   /dependency
 /dependencies
   /dependencyManagement
 /project
   project
 modelVersion4.0.0/modelVersion
 groupIddirect-dependency-groupId/groupId
 artifactIddirect-dependency-artifactId/artifactId
 version1/version
 dependencies
   dependency
 groupIdtransitive-dependency-old-groupId/groupId
 artifactIdtransitive-dependency-artifactId/artifactId
 version1/version
   /dependency
 /dependencies
   /project   

 project
   modelVersion4.0.0/modelVersion
   groupIdtransitive-dependency-old-groupId/groupId
   artifactIdtransitive-dependency-artifactId/artifactId
   version1/version
   distributionManagement
 relocation
   groupIdtransitive-dependency-new-groupId/groupId
 /relocation
   /distributionManagement
 /project   
 project
   modelVersion4.0.0/modelVersion
   groupIdtransitive-dependency-new-groupId/groupId
   artifactIdtransitive-dependency-artifactId/artifactId
   version1/version
   dependencies
 dependency
   groupIdother-groupId/groupId
   artifactIdother-artifactId-a/artifactId
   version1/version
 /dependency
   /dependencies
 /project
 project
   modelVersion4.0.0/modelVersion
   groupIdtransitive-dependency-new-groupId/groupId
   artifactIdtransitive-dependency-artifactId/artifactId
   version2/version
   dependencies
 dependency
   groupIdother-groupId/groupId
   artifactIdother-artifactId-a/artifactId
   version1/version
 /dependency
 dependency
   groupIdother-groupId/groupId
   artifactIdother-artifactId-b/artifactId
   version1/version
 /dependency
   /dependencies
 /project   

 --
 actual dependency:tree 
 
  root-groupId:root-artifactId:jar:1
  \- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile
 \- 
 transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile
  (version managed from 1)
\- other-groupId:other-artifactId-a:jar:1:compile   
 -- 
 expected dependency:tree 
 
  root-groupId:root-artifactId:jar:1
  \- direct-dependency-groupId:direct-dependency-artifactId:jar:1:compile
 \- 
 transitive-dependency-new-groupId:transitive-dependency-artifactId:jar:2:compile
  (version managed from 1)
\- other-groupId:other-artifactId-a:jar:1:compile
\- other-groupId:other-artifactId-b:jar:1:compile -- missing from 
 actual result
 -- 
  
 As you can see from the listing above, 
 other-groupId:other-artifactId-b:jar:1:compile is missing from the dependency 
 list.  
 I have attached the zipped repo which was used when generating the 
 dependency:tree listings shown above.  I also attached a crude temporary 
 patch which my team is currently using to resolve this issue.  After ignoring 
 whitespace changes, it is about 10 lines different.
 Thanks,
 Luke

-- 
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-2105) Uploading proguard 4.2 to The Central Repository


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

Carlos Sanchez closed MAVENUPLOAD-2105.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Uploading proguard 4.2 to The Central Repository
 

 Key: MAVENUPLOAD-2105
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2105
 Project: Maven Upload Requests
  Issue Type: Task
Reporter: Vlad Skarzhevskyy
Assignee: Carlos Sanchez

 Please Upload the latest version to Repository. The last version (posted by 
 me) in repository is 4.1
 http://pyx4j.com/downloads/proguard-4.2-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.2:
 * Refined data flow analysis in optimization step.
 * Fixed handling of exceptions when inlining subroutines.
 * Fixed inlining of incompatible code constructs between different java 
 versions.
 * Fixed computation of local variable frame size.
 * Fixed optimization of infinite loops.
 * Fixed optimization of subroutine invocations.
 * Fixed optimization of floating point remainder computations.
 * Fixed removal of unused parameters in method descriptors containing 
 arrays of longs or doubles.
 * Added undocumented java system properties maximum.inlined.code.length 
 (default is 8) and maximum.resulting.code.length (defaults are 8000 for JSE 
 and 2000 for JME), for expert users who read release notes.
 * Fixed processing of generic types in Signature attributes in shrinking 
 and optimization steps.
 * Fixed processing of inner class names in Signature attributes in 
 obfuscation step.
 * Improved adapting resource file names following obfuscated class names.
 * Fixed interpretation of package names in GUI.
 * Fixed default settings for Xlets in GUI.
 * 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] Closed: (MAVENUPLOAD-2133) Please add jpp to repository


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

Carlos Sanchez closed MAVENUPLOAD-2133.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Please add jpp to repository
 

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

 net.sourceforge.jpp,[EMAIL 
 PROTECTED]:/home/groups/j/jp/jpp/repository/release,rsync_ssh,Ivan 
 Szkiba,[EMAIL PROTECTED],,

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

[jira] Closed: (MAVENUPLOAD-2116) Please add MigLayout to the auto rsynced list.


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

Carlos Sanchez closed MAVENUPLOAD-2116.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Please add MigLayout to the auto rsynced list.
 --

 Key: MAVENUPLOAD-2116
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116
 Project: Maven Upload Requests
  Issue Type: New Feature
Reporter: Mikael Grev
Assignee: Carlos Sanchez

 miglayout,rsync://[EMAIL PROTECTED]/maven/releases,rsync,Mikael 
 Grev,[EMAIL PROTECTED],,
 The password is maven.
 MigLayout is a LayoutManager for Swing  SWT. It is the #1 RFE for being 
 added to SWT and #10 RFE for being added to the Java SDK.
 I own MiGInfoCom AB which owns MigLayout.
 Cheers,
 Mikael Grev

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

[jira] Commented: (MAVENUPLOAD-2142) Rsync XCluder repo


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=141157#action_141157
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2142:
-

please check updated instructions at 
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

 Rsync XCluder repo
 --

 Key: MAVENUPLOAD-2142
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2142
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Manos Batsis
 Attachments: gr.abiss.xcluder.sh


 Attached an sh script to rsync the xcluder release repo to maven central. 
 Thanks!
 Manos

-- 
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-2108) Uploading antenna 1.0.2 to The Central Repository


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

Carlos Sanchez closed MAVENUPLOAD-2108.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Uploading antenna 1.0.2 to The Central Repository
 -

 Key: MAVENUPLOAD-2108
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2108
 Project: Maven Upload Requests
  Issue Type: Task
Reporter: Vlad Skarzhevskyy
Assignee: Carlos Sanchez

 Please Upload the latest version to Repository. The last version (posted by 
 me) in repository is 0.9.14
 The antenna project provides a set of Ant tasks for developing J2ME/MIDP 
 applications based on the J2ME Wireless Toolkit.
 Maven plugin exists (j2me-maven-plugin) to use this library in maven build.

-- 
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-2113) maven-license-plugin-1.3.1 upload request


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

Carlos Sanchez closed MAVENUPLOAD-2113.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 maven-license-plugin-1.3.1 upload request
 -

 Key: MAVENUPLOAD-2113
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2113
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Mathieu Carbou
Assignee: Carlos Sanchez
 Attachments: maven-license-plugin-1.3.1-bundle.jar


 http://maven-license-plugin.googlecode.com/files/maven-license-plugin-1.3.1-bundle.jar
 http://code.google.com/p/maven-license-plugin/
 I'm the developer of the maven license plugin, please upload!
 Mathieu Carbou.

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

[jira] Commented: (MNG-3380) MavenMetadataSource retrieves ResolutionGroup without consulting ManagedVersionMap, is problem when relocation