[jira] Updated: (MAVENUPLOAD-1726) OpenDS Directory Server
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jasper Blues updated MAVENUPLOAD-1726: -- Attachment: openDS-1.0.0-build005-bundle.jar This bundle should be good to go now. > OpenDS Directory Server > --- > > Key: MAVENUPLOAD-1726 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1726 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Jasper Blues >Assignee: Carlos Sanchez > Attachments: openDS-1.0.0-build005-bundle.jar, > openDS-1.0.0-build005-bundle.jar, openDS-1.0.0-build005-bundle.jar > > > OpenDS is an open source community project building a free and comprehensive > next generation directory service. OpenDS is designed to address large > deployments, to provide high performance, to be highly extensible, and to be > easy to deploy, manage and monitor. > Team List: https://opends.dev.java.net/public/misc/bios.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] Created: (DOXIA-166) Book output ignores book, chapter and section titles
Book output ignores book, chapter and section titles Key: DOXIA-166 URL: http://jira.codehaus.org/browse/DOXIA-166 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.0-alpha-9 Reporter: Dave Syer Book output ignores book, chapter and section titles (for xhtml and doc-book at least). For PDF the chapter titles are used but not the book or sections. Maybe this is intentional (but then what are they there for in the book model)? At least there should be some configuration to switch on/off titles? -- 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: (DOXIA-160) Book output in doc-book format is not well formed
[ http://jira.codehaus.org/browse/DOXIA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110681 ] Dave Syer commented on DOXIA-160: - Update: when you put a title and author in the APT source itself +--- --- Bar Section --- Dave --- +--- then the duplicate <<>> declarations go away - still a bug but there is a workaround. But there is still no root element and the entity declaration is wrong (no system location) - I haven't found a workaround for that. > Book output in doc-book format is not well formed > - > > Key: DOXIA-160 > URL: http://jira.codehaus.org/browse/DOXIA-160 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > > I tried using the output from a book in doc-book to run it through a > postprocesing step with docbook and found that it barfed on the source > generated by doxia. Not surprising when you consider that it is not well > formed, e.g. it has two <<>> headers in it, and no root element: > +--- > > BarThis is bar > > > > SpamThis is spam > > > > +--- > When I changed it to this it worked better > +--- > "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";> > > BarThis is bar > > > SpamThis is spam > > > > +--- -- 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: (DOXIA-160) Book output in doc-book format is not well formed
[ http://jira.codehaus.org/browse/DOXIA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110686 ] Dave Syer commented on DOXIA-160: - I notice from the source code of DocBookSink 1. it has getters and setters for systemId and publicId - is there a configuration option somewhere for those? 2. it has book() and book_() methods which are non-standard for a Sink I think. It looks like book_() is used but book() is not. Shouldn't book() be used explicitly at the start of a book (and all the logic about dcotypes and everything from head() should be in book())? This would make sure that only one DOCTYPE was emitted. > Book output in doc-book format is not well formed > - > > Key: DOXIA-160 > URL: http://jira.codehaus.org/browse/DOXIA-160 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > > I tried using the output from a book in doc-book to run it through a > postprocesing step with docbook and found that it barfed on the source > generated by doxia. Not surprising when you consider that it is not well > formed, e.g. it has two <<>> headers in it, and no root element: > +--- > > BarThis is bar > > > > SpamThis is spam > > > > +--- > When I changed it to this it worked better > +--- > "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";> > > BarThis is bar > > > SpamThis is spam > > > > +--- -- 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-168) Confluence module does not allow nested formatting - e.g. a bullet cannot contain *bold* text or a [link]
Confluence module does not allow nested formatting - e.g. a bullet cannot contain *bold* text or a [link] - Key: DOXIA-168 URL: http://jira.codehaus.org/browse/DOXIA-168 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Reporter: Dave Syer Confluence module does not allow nested formatting - e.g. a bullet cannot contain *bold* text or a [link]. They are just rendered verbatim. -- 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-167) Confluence module does not create a new paragraph on an empty line
Confluence module does not create a new paragraph on an empty line -- Key: DOXIA-167 URL: http://jira.codehaus.org/browse/DOXIA-167 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-9 Reporter: Dave Syer Confluence module does not create a new paragraph on an empty line -- 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-169) Confluence module does not recognize line breaks (\\)
Confluence module does not recognize line breaks (\\) - Key: DOXIA-169 URL: http://jira.codehaus.org/browse/DOXIA-169 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-8 Reporter: Dave Syer Confluence module does not recognize line breaks (\\) -- 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-170) Confluence module should do something with non-doxia formatting
Confluence module should do something with non-doxia formatting --- Key: DOXIA-170 URL: http://jira.codehaus.org/browse/DOXIA-170 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-8 Reporter: Dave Syer These wiki formats are not recognised ??citation?? -strikethrough- +underlined+ ^superscript^ ~subscript~ -- 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: (DOXIA-167) Confluence module does not create a new paragraph on an empty line
[ http://jira.codehaus.org/browse/DOXIA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Syer closed DOXIA-167. --- Resolution: Cannot Reproduce Fix Version/s: 1.0-alpha-8 Oops. This was not valid. > Confluence module does not create a new paragraph on an empty line > -- > > Key: DOXIA-167 > URL: http://jira.codehaus.org/browse/DOXIA-167 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > Fix For: 1.0-alpha-8 > > > Confluence module does not create a new paragraph on an empty line -- 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-171) Confluence "quote" macro not recognised
Confluence "quote" macro not recognised --- Key: DOXIA-171 URL: http://jira.codehaus.org/browse/DOXIA-171 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-8 Reporter: Dave Syer The "quote" and "code" macros in Confluence should do something worthwhile in Doxia. They seem to only generate errors. -- 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: (DOXIA-167) Confluence module does not create a new paragraph on an empty line
[ http://jira.codehaus.org/browse/DOXIA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated DOXIA-167: -- Fix Version/s: (was: 1.0-alpha-8) > Confluence module does not create a new paragraph on an empty line > -- > > Key: DOXIA-167 > URL: http://jira.codehaus.org/browse/DOXIA-167 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-9 >Reporter: Dave Syer > > Confluence module does not create a new paragraph on an empty line -- 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: (MSITE-266) Schedule and release doxia 1.0-alpha-10
[ http://jira.codehaus.org/browse/MSITE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-266: -- Fix Version/s: 2.0-beta-6 > Schedule and release doxia 1.0-alpha-10 > --- > > Key: MSITE-266 > URL: http://jira.codehaus.org/browse/MSITE-266 > Project: Maven 2.x Site Plugin > Issue Type: Task > Components: doxia integration >Affects Versions: 2.0-beta-6 >Reporter: Olivier Lamy >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.0-beta-6 > > -- 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: (MRELEASE-250) release perform fails because it cannot find the distributionManagement in the base pom
[ http://jira.codehaus.org/browse/MRELEASE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James William Dumay closed MRELEASE-250. Resolution: Fixed > release perform fails because it cannot find the distributionManagement in > the base pom > --- > > Key: MRELEASE-250 > URL: http://jira.codehaus.org/browse/MRELEASE-250 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: James William Dumay > Attachments: release-perform-log.txt > > > We have specified in our base pom the distribution repository for other maven > 2 projects to inherit from. > The trouble is when we run mvn release:perform, maven compains that there was > no distributionManagement set. > I have also check that the base pom is correct and that the child pom > inherits off of the base pom correctly. A small log is attached. -- 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: (MPIR-73) Error when running task deploy en maven2.x
[ http://jira.codehaus.org/browse/MPIR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110691 ] Dennis Lundberg commented on MPIR-73: - I believe that this issue belongs in the site-plugin and occurs because of a missing property in the ResourceBundle. What locale do you have on your machine? > Error when running task deploy en maven2.x > -- > > Key: MPIR-73 > URL: http://jira.codehaus.org/browse/MPIR-73 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Reporter: Luiz Alberto da Cruz Rangel Junior > > java.lang.NullPointerException > at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:141) > at > org.apache.maven.plugins.site.AbstractSiteMojo.getAvailableLocales(AbstractSiteMojo.java:166) > at > org.apache.maven.plugins.site.SiteDescriptorAttachMojo.execute(SiteDescriptorAttachMojo.java:67) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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) -- 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-250) release perform fails because it cannot find the distributionManagement in the base pom
[ http://jira.codehaus.org/browse/MRELEASE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110692 ] Dennis Lundberg commented on MRELEASE-250: -- How was this fixed and in which version of the release-plugin? > release perform fails because it cannot find the distributionManagement in > the base pom > --- > > Key: MRELEASE-250 > URL: http://jira.codehaus.org/browse/MRELEASE-250 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: James William Dumay > Attachments: release-perform-log.txt > > > We have specified in our base pom the distribution repository for other maven > 2 projects to inherit from. > The trouble is when we run mvn release:perform, maven compains that there was > no distributionManagement set. > I have also check that the base pom is correct and that the child pom > inherits off of the base pom correctly. A small log is attached. -- 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: (DOXIA-170) Confluence module should do something with non-doxia formatting
[ http://jira.codehaus.org/browse/DOXIA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110696 ] Vincent Massol commented on DOXIA-170: -- The strikethrough and underline ones are duplicates of DOXIA-163 and DOXIA-164 > Confluence module should do something with non-doxia formatting > --- > > Key: DOXIA-170 > URL: http://jira.codehaus.org/browse/DOXIA-170 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-8 >Reporter: Dave Syer > > These wiki formats are not recognised ??citation?? -strikethrough- > +underlined+ ^superscript^ ~subscript~ -- 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: (DOXIA-162) Failure to parse paragraph line with an EOL
[
http://jira.codehaus.org/browse/DOXIA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Massol updated DOXIA-162:
-
Affects Version/s: (was: 1.0-beta-1)
1.0-alpha-9
> Failure to parse paragraph line with an EOL
> ---
>
> Key: DOXIA-162
> URL: http://jira.codehaus.org/browse/DOXIA-162
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Confluence
>Affects Versions: 1.0-alpha-9
>Reporter: Vincent Massol
>
> The confluence parser generates a TextBlock with the text " sites that are
> primarilyauthored in confluence while at the same time having the site be
> rendered ina" while parsing the following:
> {noformat}
> This the way that we would like to *translate* sites that are primarily
> authored in confluence while at the same time having the site be rendered in
> a _standard way on a static website_.
> {noformat}
> As you can see, the EOL after "primarily" isn't taken into account, nor is
> the one after "in".
--
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: (DOXIA-164) Add support for strikethroughs
[ http://jira.codehaus.org/browse/DOXIA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Massol updated DOXIA-164: - Affects Version/s: (was: 1.0-beta-1) 1.0-alpha-9 > Add support for strikethroughs > -- > > Key: DOXIA-164 > URL: http://jira.codehaus.org/browse/DOXIA-164 > Project: Maven Doxia > Issue Type: Improvement > Components: Sink API >Affects Versions: 1.0-alpha-9 >Reporter: Vincent Massol > -- 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: (DOXIA-165) Add support for macros
[ http://jira.codehaus.org/browse/DOXIA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Massol updated DOXIA-165: - Affects Version/s: (was: 1.0-beta-1) 1.0-alpha-9 > Add support for macros > -- > > Key: DOXIA-165 > URL: http://jira.codehaus.org/browse/DOXIA-165 > Project: Maven Doxia > Issue Type: Improvement > Components: Sink API >Affects Versions: 1.0-alpha-9 >Reporter: Vincent Massol > > I'd like a macro/macro_ sink method so that it's possible to convert macros > from one syntax to another. -- 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: (MPLUGIN-31) The plugin:xdoc produce a null pointer exception when no parameter is provided
[
http://jira.codehaus.org/browse/MPLUGIN-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPLUGIN-31:
---
Description:
The pluggin:xdoc return a mojo MojoDescriptor with a null parameter list when
the mojo has no parameter.
That causes a null pointer exception when converted to xdoc.
The folowing patch applied to maven-plugin-tools-2.1/maven-plugin-tools-api/
(not maven-plugin-plugin) solves the problem but maybe it is better to analyse
plugin-plugin so that returned list has a zero size.
{code}
Index:
C:/maven-plugin-tools-2.1/maven-plugin-tools-api/src/test/java/org/apache/maven/tools/plugin/generator/PluginDescriptorGeneratorTest.java
===
---
C:/maven-plugin-tools-2.1/maven-plugin-tools-api/src/test/java/org/apache/maven/tools/plugin/generator/PluginDescriptorGeneratorTest.java
(revision 525213)
+++
C:/maven-plugin-tools-2.1/maven-plugin-tools-api/src/test/java/org/apache/maven/tools/plugin/generator/PluginDescriptorGeneratorTest.java
(working copy)
@@ -106,7 +106,7 @@
assertNotNull( mojoDescriptor.isDependencyResolutionRequired() );
// check the parameter.
-checkParameter( (Parameter) mojoDescriptor.getParameters().get( 0 ) );
+// checkParameter( (Parameter) mojoDescriptor.getParameters().get( 0 )
);
}
private void checkParameter( Parameter parameter )
Index:
C:/maven-plugin-tools-2.1/maven-plugin-tools-api/src/test/java/org/apache/maven/tools/plugin/generator/AbstractGeneratorTestCase.java
===
---
C:/maven-plugin-tools-2.1/maven-plugin-tools-api/src/test/java/org/apache/maven/tools/plugin/generator/AbstractGeneratorTestCase.java
(revision 525213)
+++
C:/maven-plugin-tools-2.1/maven-plugin-tools-api/src/test/java/org/apache/maven/tools/plugin/generator/AbstractGeneratorTestCase.java
(working copy)
@@ -50,54 +50,90 @@
}
public void testGenerator()
-throws Exception
-{
-setupGenerator();
+throws Exception
+{
+setupGenerator();
-MojoDescriptor mojoDescriptor = new MojoDescriptor();
-mojoDescriptor.setGoal( "testGoal" );
-mojoDescriptor.setImplementation(
"org.apache.maven.tools.plugin.generator.TestMojo" );
-mojoDescriptor.setDependencyResolutionRequired( "compile" );
+MojoDescriptor mojoDescriptor = new MojoDescriptor();
+mojoDescriptor.setGoal( "testGoal" );
+mojoDescriptor.setImplementation(
"org.apache.maven.tools.plugin.generator.TestMojo" );
+mojoDescriptor.setDependencyResolutionRequired( "compile" );
-List params = new ArrayList();
+List params = new ArrayList();
-Parameter param = new Parameter();
-param.setExpression( "${project.build.directory}" );
-param.setName( "dir" );
-param.setRequired( true );
-param.setType( "java.lang.String" );
-param.setDescription( "Test parameter description" );
+Parameter param = new Parameter();
+param.setExpression( "${project.build.directory}" );
+param.setName( "dir" );
+param.setRequired( true );
+param.setType( "java.lang.String" );
+param.setDescription( "Test parameter description" );
-params.add( param );
+params.add( param );
-mojoDescriptor.setParameters( params );
+mojoDescriptor.setParameters( params );
-PluginDescriptor pluginDescriptor = new PluginDescriptor();
-mojoDescriptor.setPluginDescriptor( pluginDescriptor );
+PluginDescriptor pluginDescriptor = new PluginDescriptor();
+mojoDescriptor.setPluginDescriptor( pluginDescriptor );
-pluginDescriptor.addMojo( mojoDescriptor );
+pluginDescriptor.addMojo( mojoDescriptor );
-pluginDescriptor.setArtifactId( "maven-unitTesting-plugin" );
-pluginDescriptor.setGoalPrefix( "test" );
+pluginDescriptor.setArtifactId( "maven-unitTesting-plugin" );
+pluginDescriptor.setGoalPrefix( "test" );
-ComponentDependency dependency = new ComponentDependency();
-dependency.setGroupId( "testGroup" );
-dependency.setArtifactId( "testArtifact" );
-dependency.setVersion( "0.0.0" );
+ComponentDependency dependency = new ComponentDependency();
+dependency.setGroupId( "testGroup" );
+dependency.setArtifactId( "testArtifact" );
+dependency.setVersion( "0.0.0" );
-pluginDescriptor.setDependencies( Collections.singletonList(
dependency ) );
+pluginDescriptor.setDependencies( Collections.singletonList( dependency )
);
-File destinationDirectory = new File( System.getProperty(
"java.io.tmpdir" ), "testGenerator-outDir" );
-FileUtils.deleteDirectory( destinationDirectory );
-destinationDirectory.mkdir();
+File destinationDirectory = new File( System.getProperty( "java.io
[jira] Created: (DOXIA-172) Confluence parser doesn't emit bold() events for list items containing bold text
Confluence parser doesn't emit bold() events for list items containing bold text Key: DOXIA-172 URL: http://jira.codehaus.org/browse/DOXIA-172 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-9 Reporter: Vincent Massol -- 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: (DOXIA-163) Add support for underscores
[ http://jira.codehaus.org/browse/DOXIA-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Massol updated DOXIA-163: - Affects Version/s: (was: 1.0-beta-1) 1.0-alpha-9 > Add support for underscores > --- > > Key: DOXIA-163 > URL: http://jira.codehaus.org/browse/DOXIA-163 > Project: Maven Doxia > Issue Type: Improvement > Components: Sink API >Affects Versions: 1.0-alpha-9 >Reporter: Vincent Massol > -- 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: (MPLUGIN-28) Error of goal value in Plugin documentation generation
[
http://jira.codehaus.org/browse/MPLUGIN-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MPLUGIN-28:
---
Description:
in my pom, i configure maven-plugin-plugin to modify the goalPrefix value as :
...
org.codehaus.mojo
dashboard-maven-plugin
1.0-SNAPSHOT
...
...
org.apache.maven.plugins
maven-plugin-plugin
dashboard-report
the descriptor of my plugin is ok.
But when i generate the plugin's site, the generated goal in plugin-info.html
file is "dashboard:dashboard" instead of "dashboard-report:dashboard".
When i read the code, i see in AbstractGeneratorMojo class :
{code}
/**
* The goal prefix that will appear before the ":".
*
* @parameter
*/
protected String goalPrefix;
...
public void execute()
throws MojoExecutionException
{
if ( !project.getPackaging().equals( "maven-plugin" ) )
{
return;
}
String defaultGoalPrefix = PluginDescriptor.getGoalPrefixFromArtifactId(
project.getArtifactId() );
if ( goalPrefix == null )
{
goalPrefix = defaultGoalPrefix;
}
else
{
getLog().warn( "Goal prefix is: " + goalPrefix + "; Maven currently
expects it to be " + defaultGoalPrefix );
}
{code}
but when i see the PluginReport class :
{code}
protected void executeReport( Locale locale )
throws MavenReportException
{
if ( !project.getPackaging().equals( "maven-plugin" ) )
{
return;
}
String goalPrefix = PluginDescriptor.getGoalPrefixFromArtifactId(
project.getArtifactId() );
// TODO: could use this more, eg in the writing of the plugin descriptor!
PluginDescriptor pluginDescriptor = new PluginDescriptor();
pluginDescriptor.setGroupId( project.getGroupId() );
pluginDescriptor.setArtifactId( project.getArtifactId() );
pluginDescriptor.setVersion( project.getVersion() );
pluginDescriptor.setGoalPrefix( goalPrefix );
{code}
To fix this error :
- add a goal prefix parameter in the PluginReport class and do the same code
as AbstractGeneratorMojo class to retreive the goal Prefix
or
- read directly the plugin descriptor which is well generated instead of to
re-create the plugin descriptor with project parameters
was:
in my pom, i configure maven-plugin-plugin to modify the goalPrefix value as :
...
org.codehaus.mojo
dashboard-maven-plugin
1.0-SNAPSHOT
...
...
org.apache.maven.plugins
maven-plugin-plugin
dashboard-report
the descriptor of my plugin is ok.
But when i generate the plugin's site, the generated goal in plugin-info.html
file is "dashboard:dashboard" instead of "dashboard-report:dashboard".
When i read the code, i see in AbstractGeneratorMojo class :
...
/**
* The goal prefix that will appear before the ":".
*
* @parameter
*/
protected String goalPrefix;
...
public void execute()
throws MojoExecutionException
{
if ( !project.getPackaging().equals( "maven-plugin" ) )
{
return;
}
String defaultGoalPrefix = PluginDescriptor.getGoalPrefixFromArtifactId(
project.getArtifactId() );
if ( goalPrefix == null )
{
goalPrefix = defaultGoalPrefix;
}
else
{
getLog().warn( "Goal prefix is: " + goalPrefix + "; Maven currently
expects it to be " + defaultGoalPrefix );
}
.
but when i see the PluginReport class :
protected void executeReport( Locale locale )
throws MavenReportException
{
if ( !project.getPackaging().equals( "maven-plugin" ) )
{
return;
}
String goalPrefix = PluginDescriptor.getGoalPrefixFromArtifactId(
project.getArtifactId() );
// TODO: could use this more, eg in the writing of the plugin descriptor!
PluginDescriptor pluginDescriptor = new PluginDescriptor();
pluginDescriptor.setGroupId( project.getGroupId() );
pluginDescriptor.setArtifactId( project.getArtifactId() );
pluginDescriptor.setVersion( project.getVersion() );
pluginDescriptor.setGoalPrefix( goalPrefix );
To fix this error :
- add a goal prefix parameter in the PluginReport class and do the same code
as AbstractGeneratorMojo class to retreive the goal Prefix
or
- read directly the plugin descriptor which is well generated instead of to
re-create the plugin descriptor with project parameters
> Error of goal value in Plugin documentation generation
> --
>
> Key: MPLUGIN-28
> URL: http://jira.codehaus.org/browse/MPLUGIN-28
> Project: Maven 2.x Plugin Plugin
> Issue Type: Bug
> Environment: Maven 2.0.4 / Windows 2000
>Reporter: David Vicente
>Priority: Critical
>
> in my pom, i configure maven-plugin-plugin to modify the goalPrefix value as :
> ...
> org.codehaus.mojo
> dashboard-m
[jira] Commented: (DOXIA-169) Confluence module does not recognize line breaks (\\)
[ http://jira.codehaus.org/browse/DOXIA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110698 ] Vincent Massol commented on DOXIA-169: -- Dave, is this a duplicaye of DOXIA-162? > Confluence module does not recognize line breaks (\\) > - > > Key: DOXIA-169 > URL: http://jira.codehaus.org/browse/DOXIA-169 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-8 >Reporter: Dave Syer > > Confluence module does not recognize line breaks (\\) -- 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: (DOXIA-169) Confluence module does not recognize line breaks (\\)
[ http://jira.codehaus.org/browse/DOXIA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110698 ] Vincent Massol edited comment on DOXIA-169 at 10/21/07 11:38 AM: - Dave, is this a duplicate of DOXIA-162? was: Dave, is this a duplicaye of DOXIA-162? > Confluence module does not recognize line breaks (\\) > - > > Key: DOXIA-169 > URL: http://jira.codehaus.org/browse/DOXIA-169 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-8 >Reporter: Dave Syer > > Confluence module does not recognize line breaks (\\) -- 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: (DOXIA-172) Confluence parser doesn't emit bold() events for list items containing bold text
[ http://jira.codehaus.org/browse/DOXIA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110699 ] Vincent Massol commented on DOXIA-172: -- This looks similar to DOXIA-168 > Confluence parser doesn't emit bold() events for list items containing bold > text > > > Key: DOXIA-172 > URL: http://jira.codehaus.org/browse/DOXIA-172 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-9 >Reporter: Vincent Massol > -- 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: (DOXIA-170) Confluence module should do something with non-doxia formatting
[ http://jira.codehaus.org/browse/DOXIA-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110700 ] Dave Syer commented on DOXIA-170: - Strictly speaking I wouls argue that is not the case, since DOXIA-163 and DOXIA-164 are Sink API issues. I meant that the Confluence module should recognise those annotations even if it can't render them properly because of limitations in another API. > Confluence module should do something with non-doxia formatting > --- > > Key: DOXIA-170 > URL: http://jira.codehaus.org/browse/DOXIA-170 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-8 >Reporter: Dave Syer > > These wiki formats are not recognised ??citation?? -strikethrough- > +underlined+ ^superscript^ ~subscript~ -- 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: (DOXIA-169) Confluence module does not recognize line breaks (\\)
[ http://jira.codehaus.org/browse/DOXIA-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110702 ] Dave Syer commented on DOXIA-169: - No, not really. This is about the confluence markup for an explicit line ending - two backslashes (which I don't know how to write verbatim here). DOXIA-162 is definitely more urgent than this one, even though it is quite irritating. > Confluence module does not recognize line breaks (\\) > - > > Key: DOXIA-169 > URL: http://jira.codehaus.org/browse/DOXIA-169 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.0-alpha-8 >Reporter: Dave Syer > > Confluence module does not recognize line breaks (\\) -- 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-173) Support for Confluence anchor macro
Support for Confluence anchor macro
---
Key: DOXIA-173
URL: http://jira.codehaus.org/browse/DOXIA-173
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.0-alpha-8
Reporter: Dave Syer
Support for Confluence anchor macro. It looks like some work was done on it
(there is an AnchorBlock in the source code). But \{anchor:foo\} does not
produce an anchor in the rendered 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] Created: (DOXIA-174) Add something to the head() so a page can be identified
Add something to the head() so a page can be identified --- Key: DOXIA-174 URL: http://jira.codehaus.org/browse/DOXIA-174 Project: Maven Doxia Issue Type: New Feature Components: Module - Confluence Affects Versions: 1.0-alpha-8 Reporter: Dave Syer Add something to the head() so a page can be identified. Confluence doesn't really have the notion of special markup for title and author, as far as I know. If it does great - we need to support it in the Doxia parser. Even if it doesn't, the generated HTML needs to identify itself to a browser - could use the name of the Source for instance. Also the Doxia Book model likes to have some header meta data for a book. In the APT case it gets it from the header of the first section. -- 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: (MRM-265) After removing a managed repository - Browse/Search still see it
[ http://jira.codehaus.org/browse/MRM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-265. Resolution: Fixed Fixed in -r586919 - added method for deleting the artifacts in the db when a repo is deleted - also deleted repo scan statistics when the repo is deleted - created DAO that does retrieving, deleting and adding of RepositoryContentStatistics to the db - added and updated tests > After removing a managed repository - Browse/Search still see it > > > Key: MRM-265 > URL: http://jira.codehaus.org/browse/MRM-265 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Henri Yandell >Assignee: Maria Odea Ching > Fix For: 1.0-beta-3 > > > I had a repository with lots of stuff in. I removed that (but didn't delete > contents), then I added a tiny repository with a couple of jars in. When I > goto browse and search, I still see the original, now removed, repository. > Re-indexing didn't help [JIRA uses indexes for lists a lot, so I figured this > might be the case here too]. -- 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: (CONTINUUM-1519) Continuum does not respect build order for flat projects
[ http://jira.codehaus.org/browse/CONTINUUM-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110704 ] Siarhei Dudzin commented on CONTINUUM-1519: --- I've used file system in scm info, so you would need to modify it for all modules, for the rest it should work out of the box. > Continuum does not respect build order for flat projects > > > Key: CONTINUUM-1519 > URL: http://jira.codehaus.org/browse/CONTINUUM-1519 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-3 > Environment: Windows XP/2003 Server, Maven 2.0.7 >Reporter: Siarhei Dudzin >Priority: Blocker > Attachments: TEST-CONTINUUM-1519.zip > > > When adding maven 2 projects with flat project layout continuum sorts the > projects build sequence by alphabet thus braking builds. Previous version did > respect reactor build sequence and '--non-recursive' option allowed to build > flat projects independently but still in the right order. This is a very > blocking issue for us because we are forced atm to use flat project structure. -- 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-250) release perform fails because it cannot find the distributionManagement in the base pom
[ http://jira.codehaus.org/browse/MRELEASE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110705 ] James William Dumay commented on MRELEASE-250: -- This issue was due to my own wrong doing - so theres no bug. > release perform fails because it cannot find the distributionManagement in > the base pom > --- > > Key: MRELEASE-250 > URL: http://jira.codehaus.org/browse/MRELEASE-250 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: James William Dumay > Attachments: release-perform-log.txt > > > We have specified in our base pom the distribution repository for other maven > 2 projects to inherit from. > The trouble is when we run mvn release:perform, maven compains that there was > no distributionManagement set. > I have also check that the base pom is correct and that the child pom > inherits off of the base pom correctly. A small log is attached. -- 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-2290) Generated URLs in POMs of child modules
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110709
]
William Ferguson commented on MNG-2290:
---
Joerg, I'm satisfied that all my concerns raised with this issue have been
resolved by http://jira.codehaus.org/browse/MNG-3244.
Did you still want to keep it open?
> Generated URLs in POMs of child modules
> ---
>
> Key: MNG-2290
> URL: http://jira.codehaus.org/browse/MNG-2290
> Project: Maven 2
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.4
>Reporter: Joerg Schaible
> Fix For: 2.0.x
>
>
> Maven has quite some elements where a URL or a path is modified automatically
> for child POMs (the ones I am currently aware of):
> - url
> - scm/connection
> - scm/developerConnection
> - scm/url
> - distributionManagement/site/url
> While expanding this path with "/${pom.artifactId}" sounds reasonable, this
> approach fails badly for complex projects with more hierarchy levels. Suppose
> we have a directory structure like:
> * project
> ** core
> *** provider
> commons
> impl1
> In this hierarchy all POMs for _project_, _core_ and _provider_ are of
> package type _pom_, while _commons_ and _impl1_ is of type _jar_. The
> "artifactId" approach now simply assumes that all POMs in the hierarchy are
> named like the current directory. This does simply not match. Suppose those
> jar artifacts are used in an enterprise or web app. Then every artifact is
> located in one single directory and therefore the names have to be unique.
> But if you decide to take an artifact name different to the directory name,
> you have to add the definition in every POM, because the scm elements are
> simply wrong.
> An even worse scenario are components that can be provided using different
> technologies. We have a lot of such structures:
> * component
> ** jar
> ** war
> ** ear
> * *_jar_:* the core functionality
> * *_war_:* the core functionality integrated and eccessible with a web
> application
> * *_ear_:* the complete component as enterprise app, if it makes sense to
> deploy the functionality on a different app server
> _component_ has a POM of package type _pom_; _jar_, _war_ and _ear_ have POMs
> with the according package type. All of the three POMs use the same
> artifactId though. In this case not only the scm elements break, but also the
> URLs for the site, since they are all the same for all three artifacts.
> All of this could have been avoided, if the expanded part is not the
> artifactId, but the basename of the current directory. Especially for the scm
> elements, this is IMHO the only valid assumption.
> It would already help us, if this auto-expansion could be turned off to allow
> the definition of a single property in each POM for a correct interpolation
> of those values, but there seems no such option ^1^. So you *have to* add
> those elements under all circumstances into every POM.
> 1) The _tagBase_ of the release plugin does no such auto-expansion, which
> makes it quite easy to use a property for it, that can be set individually in
> every POM without adding any plugin configuration.
--
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-3203) maven should execute compiler:compile and :test-compile in separate executions, to allow separate configuration
[ http://jira.codehaus.org/browse/MNG-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3203: --- Fix Version/s: (was: 2.1-alpha-1) (was: 2.0.8) 2.0.9 bumping to 2.0.9. If we get IT tests for these before 2.0.8 is final, we can take a look > maven should execute compiler:compile and :test-compile in separate > executions, to allow separate configuration > --- > > Key: MNG-3203 > URL: http://jira.codehaus.org/browse/MNG-3203 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.0.7 >Reporter: John Casey > Fix For: 2.0.9 > > > Currently, it's impossible to configure the two default maven-compiler-plugin > mojos in the jar lifecycle (:compile and :test-compile) separately without > the configuration for one affecting both. This is because they are both > executed in the same (default) execution. We should be assigning these to > different execution id's, to allow separate configuration. -- 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-428) Japanese message resource
[ http://jira.codehaus.org/browse/MNG-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-428: -- Fix Version/s: (was: 2.0.8) 2.0.9 bumping to 2.0.9. If we get IT tests for these before 2.0.8 is final, we can take a look > Japanese message resource > - > > Key: MNG-428 > URL: http://jira.codehaus.org/browse/MNG-428 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.0-beta-1 > Environment: N/A >Reporter: Takayoshi Kimura >Priority: Minor > Fix For: 2.0.9 > > Attachments: message_ja.properites.patch > > > Now, we got message_ja.properties. -- 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-2339) ${project.*} are interpreted in the wrong place
[
http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MNG-2339:
---
Fix Version/s: (was: 2.0.8)
2.0.9
bumping to 2.0.9. If we get IT tests for these before 2.0.8 is final, we can
take a look
> ${project.*} are interpreted in the wrong place
> ---
>
> Key: MNG-2339
> URL: http://jira.codehaus.org/browse/MNG-2339
> Project: Maven 2
> Issue Type: Bug
> Components: General
>Affects Versions: 2.0.4
>Reporter: Emmanuel Venisse
>Assignee: Kenney Westerhof
>Priority: Critical
> Fix For: 2.0.9
>
>
> If a plugin use ${project.version}, this parameter is interpreted with the
> version of the current project and not the plugin version. I think we have
> the same pb with dependencies and other ${project.*}
> For a plugin in version 2.0 used in a project in version 1.0-SNAPSHOT,
> ${project.version} used in the plugin will be interpreted as 1.0-SNAPSHOT
> instead of 2.0
--
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-3221) Infinite loop in DefaultLifecycleExecutor
[
http://jira.codehaus.org/browse/MNG-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MNG-3221:
---
Fix Version/s: (was: 2.0.8)
2.0.9
bumping to 2.0.9. If we get IT tests for these before 2.0.8 is final, we can
take a look
> Infinite loop in DefaultLifecycleExecutor
> -
>
> Key: MNG-3221
> URL: http://jira.codehaus.org/browse/MNG-3221
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.7
>Reporter: Vincent Siveton
> Fix For: 2.0.9
>
> Attachments: infinite-loop.diff
>
>
> Defining this following report:
> {code:title=MyReport.java|borderStyle=solid}
> /**
> * @goal mygoal
> * @execute phase="site"
> */
> public class MyReport
> extends AbstractMavenReport{}
> {code}
> I got this following loop:
> {noformat}
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecycleExecutor.forkLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 739
> DefaultLifecycleExecutor.executeGoals(List, Stack, MavenSession,
> MavenProject) line: 530
> DefaultLifecycleExecutor.executeGoalWithLifecycle(String, Stack,
> MavenSession, Map, MavenProject, Lifecycle) line: 480
> DefaultLifecycleExecutor.forkProjectLifecycle(MojoDescriptor, Stack,
> MavenSession, MavenProject) line: 896
> DefaultLifecy
[jira] Updated: (MNG-2123) NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range
[ http://jira.codehaus.org/browse/MNG-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-2123: --- Fix Version/s: (was: 2.0.8) 2.0.9 bumping to 2.0.9. If we get IT tests for these before 2.0.8 is final, we can take a look > NullPointerException when a dependency uses version range and another uses an > actual version incompatible with that range > - > > Key: MNG-2123 > URL: http://jira.codehaus.org/browse/MNG-2123 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.2, 2.0.3, 2.0.4 >Reporter: Carlos Sanchez >Assignee: Jason van Zyl > Fix For: 2.0.9 > > Attachments: MNG-2123-maven-artifact.patch, pom.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Struts 1.2.7 depends on commons-digester 1.6 and jasperreports 1.1.1 in [1.7,) > Build fails with a null pointer exception that is not very explanatory > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - test:test:jar:1.0-SNAPSHOT > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:361) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:222) > at > org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(ResolutionNode.java:115) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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: 1 second > [INFO] Finished at: Sun Mar 05 23:26:16 PST 2006 > [INFO] Final Memory: 3M/5M > [INFO] > -- This message is automatically genera
[jira] Moved: (MENFORCER-19) Add an option to enforce dependencyManagement
[ http://jira.codehaus.org/browse/MENFORCER-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox moved MNG-2128 to MENFORCER-19: - Affects Version/s: (was: 2.0.2) (was: 2.0.3) (was: 2.0.1) (was: 2.0) Fix Version/s: (was: 2.1) Component/s: (was: Dependencies) Standard Rules Complexity: (was: Intermediate) Key: MENFORCER-19 (was: MNG-2128) Project: Maven 2.x Enforcer Plugin (was: Maven 2) > Add an option to enforce dependencyManagement > - > > Key: MENFORCER-19 > URL: http://jira.codehaus.org/browse/MENFORCER-19 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature > Components: Standard Rules >Reporter: Carlos Sanchez > > Add something to the dependencyManagement section like > true > to make build fail if a subproject uses a different version > Currently a subproject can specify the version of a dependency already > defined in dependencyManagement, which is error prone -- 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: (MRM-459) prune the distributed dependencies
[ http://jira.codehaus.org/browse/MRM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-459: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > prune the distributed dependencies > -- > > Key: MRM-459 > URL: http://jira.codehaus.org/browse/MRM-459 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-4 > > > a large number of unneeded dependencies are distributed with Archiva (or if > they are needed, we might want to review why). > For example: ant-optional (probably for jsp compiler), commons-logging impl + > slf4j + log4j, xerces, jtidy, jdom, dom4j, commons-jxpath, jaxen, jta (we > have geronimo-jat already), classworlds (we have plexus-classworlds already), > backport (we require JDK 5, no need for this). > I'm also uncertain if all the maven libraries are still needed. -- 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: (MRM-454) Index not updated after repository purge
[ http://jira.codehaus.org/browse/MRM-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-454: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Index not updated after repository purge > > > Key: MRM-454 > URL: http://jira.codehaus.org/browse/MRM-454 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-beta-1 >Reporter: Maria Odea Ching > Fix For: 1.0-beta-4 > > > Please see comments MRM-294 for more info -- 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: (MRM-547) proxy connectors: cache failures options are confusing
[ http://jira.codehaus.org/browse/MRM-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-547: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > proxy connectors: cache failures options are confusing > -- > > Key: MRM-547 > URL: http://jira.codehaus.org/browse/MRM-547 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.0-beta-4 > > > I think this should be renamed to just "failures" which can be "cached" or > "ignored", or otherwise be changed to a yes/no value for "cached failures". -- 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: (MRM-511) Maven IT 94 fails when using Archiva as a proxy
[ http://jira.codehaus.org/browse/MRM-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-511: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Maven IT 94 fails when using Archiva as a proxy > --- > > Key: MRM-511 > URL: http://jira.codehaus.org/browse/MRM-511 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > looks like a metadata bug - it fails to resolve log4j with version [1.2.9,] - > the same thing works when I stop using it as a proxy. -- 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: (MRM-548) proxy connectors: default policies are not correct on add
[ http://jira.codehaus.org/browse/MRM-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-548: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > proxy connectors: default policies are not correct on add > - > > Key: MRM-548 > URL: http://jira.codehaus.org/browse/MRM-548 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > the default for snapshots and releases is "ignored" for updates. This is > inconsistent with Maven default behaviour - should it be daily? -- 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: (MRM-481) Artifact requests with a .xml.zip extension fail with a 404 Error
[ http://jira.codehaus.org/browse/MRM-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-481: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Artifact requests with a .xml.zip extension fail with a 404 Error > - > > Key: MRM-481 > URL: http://jira.codehaus.org/browse/MRM-481 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Cédric Vidal >Priority: Critical > Fix For: 1.0-beta-4 > > Attachments: multi-dots-ext-404-error.htm > > > This issue might also apply to any multi dots extension request but I didn't > check. > Regards, > Cédric -- 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: (MRM-540) [regression] reports now show 0 results as a paged result that is empty
[ http://jira.codehaus.org/browse/MRM-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-540: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > [regression] reports now show 0 results as a paged result that is empty > --- > > Key: MRM-540 > URL: http://jira.codehaus.org/browse/MRM-540 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > in the past, I remember getting a good error message when the reports > returned 0 results, but now I just get: > Page: 1 >> > The links do nothing. > Also, I'm not sure why the text in the menu was changed to "pick report"? > It's not like one is being selected for later use, and the other menu items > under that menu are not verbs. -- 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: (MRM-531) Unable to download snapshots behind proxy with authentication
[ http://jira.codehaus.org/browse/MRM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-531: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Unable to download snapshots behind proxy with authentication > - > > Key: MRM-531 > URL: http://jira.codehaus.org/browse/MRM-531 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 > Environment: solaris 5.10, jdk1.6.0_02, proxy with basic > authentication >Reporter: Mathias Arens >Priority: Critical > Fix For: 1.0-beta-4 > > > I am able to download artifacts from several remote repositories into the > internal repository. But I cannot download any dependencies into the > snapshots repository. I always get a http-'Server redirected too many times > (20)'-error. I read that this error occurs if the proxy authentication > properties are not set correctly in the http client. I am behind a proxy with > basic authentication and an empty password. This configuration works fine for > the internal repository, but not for the snapshot repository. > Here are the logs: > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying > [cache-failures] policy with [ignored] > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to > fetch, check-failures policy set to IGNORED. > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying > [releases] policy with [disabled] > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update, > release policy does not apply for snapshot versions. > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying > [snapshots] policy with [daily] > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update > snapshots, local file does not exist. > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,988 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - > Retrieving org/apache/maven/artifact/maven-artifact/3.0-SNAPSHOT/mave > n-artifact-3.0-SNAPSHOT.pom from Apache Snapshots Repository if updated > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:09,087 > [SocketListener0-7] WARN > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Download > failure:Error transferring file > INFO | jvm 1| 2007/10/02 11:50:09 | > org.apache.maven.wagon.TransferFailedException: Error transferring file > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:94) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:566) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:434) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:143) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:286) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:243) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:147) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > INFO | jvm 1| 2007/10/02 11:50:09 | at > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.mortbay.jetty.servlet.ServletH
[jira] Updated: (MRM-458) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/MRM-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-458: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > the NOTICE file is overzealous in declaring dependencies > > > Key: MRM-458 > URL: http://jira.codehaus.org/browse/MRM-458 > Project: Archiva > Issue Type: Improvement >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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: (MRM-549) proxy connectors: no "always" option for releases and snapshots policies
[ http://jira.codehaus.org/browse/MRM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-549: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > proxy connectors: no "always" option for releases and snapshots policies > > > Key: MRM-549 > URL: http://jira.codehaus.org/browse/MRM-549 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > -- 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: (MRM-516) Search results return results for all repositories, regardless of security.
[ http://jira.codehaus.org/browse/MRM-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-516: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Search results return results for all repositories, regardless of security. > --- > > Key: MRM-516 > URL: http://jira.codehaus.org/browse/MRM-516 > Project: Archiva > Issue Type: Bug > Components: indexing >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-4 > > > The UserAllowedToSearchRepositoryPredicate needs to be finished. > It should take the current user, their RBAC roles, and filter based on the > roles available to the user. -- 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: (MRM-435) need to review repository defaults
[ http://jira.codehaus.org/browse/MRM-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-435: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > need to review repository defaults > -- > > Key: MRM-435 > URL: http://jira.codehaus.org/browse/MRM-435 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > we should review the use of the appserver path as the default location, as it > is not particularly friendly to seting up as a standalone web application. I > believe there is insufficient error handling to correct this situation if the > user forgets to first set the variables during installation. -- 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: (MRM-396) remove 'true' and 'false' from the descriptions on the repository admin page
[ http://jira.codehaus.org/browse/MRM-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-396: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > remove 'true' and 'false' from the descriptions on the repository admin page > > > Key: MRM-396 > URL: http://jira.codehaus.org/browse/MRM-396 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Priority: Trivial > Fix For: 1.0-beta-4 > > > the (/) and (x) are sufficient -- 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: (MRM-544) Cleanup index of artifacts that are no longer in the repository
[ http://jira.codehaus.org/browse/MRM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-544: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Cleanup index of artifacts that are no longer in the repository > --- > > Key: MRM-544 > URL: http://jira.codehaus.org/browse/MRM-544 > Project: Archiva > Issue Type: Bug > Components: indexing >Affects Versions: 1.0-beta-2 >Reporter: Maria Odea Ching > Fix For: 1.0-beta-4 > > > This was left out from MRM-37 -- 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: (MRM-502) Error 500 when searching an artifact by the checksum
[
http://jira.codehaus.org/browse/MRM-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Odea Ching updated MRM-502:
-
Fix Version/s: (was: 1.0-beta-3)
1.0-beta-4
> Error 500 when searching an artifact by the checksum
>
>
> Key: MRM-502
> URL: http://jira.codehaus.org/browse/MRM-502
> Project: Archiva
> Issue Type: Bug
> Components: web application
>Affects Versions: 1.0-beta-2
>Reporter: Arnaud Heritier
> Fix For: 1.0-beta-4
>
>
> Trying to search some artifacts with their checksum I receive this error :
> {code}
> HTTP ERROR: 500
> Exception in JSP: /WEB-INF/jsp/results.jsp:95
> 92:
> version="${artifactModel.version}"/>
> 93:
> 94:
> 95: groupId="${artifactModel.groupId}" artifactId="${artifactModel.artifactId}"
> 96:
> version="${artifactModel.version}" versions="${artifactModel.versions}"/>
> 97:
> 98:
> Stacktrace:
> RequestURI=/archiva/checksumSearch.action
> Powered by Jetty://
> {code}
> 4a61c9f221ebed45e4006f2f8fa0 *bsf-2.3.0.jar
> No results found
> 8d4a9cf34eb4e374b41b6b98960028d0 *jsp-api-2.0.jar
> No results found ?
> db561232e47050e15572fa0b01e08569 *jstl-2.3.jar
> No results found ?
> c2ced5f8505fe9d1cae685201e9cba07 *jstl-2.4.jar
> No results found ?
> f6cf3fde0b992589ed3d87fa9674015f *servletapi-2.4.jar
> No results found
--
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: (MRM-551) the default scan cron expression is once a day, should be hourly
[ http://jira.codehaus.org/browse/MRM-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-551: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > the default scan cron expression is once a day, should be hourly > > > Key: MRM-551 > URL: http://jira.codehaus.org/browse/MRM-551 > Project: Archiva > Issue Type: Bug > Components: system >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > 0 0 0 * * -> 0 0 * * *, I think -- 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: (MRM-509) Adding the same repository twice will be redirected to an Edit Repository page.
[ http://jira.codehaus.org/browse/MRM-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-509: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > Adding the same repository twice will be redirected to an Edit Repository > page. > --- > > Key: MRM-509 > URL: http://jira.codehaus.org/browse/MRM-509 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: Maria Catherine Tan >Assignee: Brett Porter >Priority: Minor > Fix For: 1.0-beta-4 > > > 1. Create a new repository > 2. Create another repository with the same values as #1 > No error will occur after creating #2 since this will be treated as an edit > repository action instead of a create action. -- 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: (MRM-492) repository failures can present as a 404 from proxy
[ http://jira.codehaus.org/browse/MRM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-492: - Fix Version/s: (was: 1.0-beta-3) 1.0-beta-4 > repository failures can present as a 404 from proxy > --- > > Key: MRM-492 > URL: http://jira.codehaus.org/browse/MRM-492 > Project: Archiva > Issue Type: Improvement > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter > Fix For: 1.0-beta-4 > > > if multiple repositories are a proxy source and it is not found on some, and > an error occurs on one or more - the end result is a "not found", where there > should be some indication of error in case the artifact may exist on the > repository with the error. -- 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: (MRM-544) Cleanup index of artifacts that are no longer in the repository
[ http://jira.codehaus.org/browse/MRM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-544 started by Maria Odea Ching. > Cleanup index of artifacts that are no longer in the repository > --- > > Key: MRM-544 > URL: http://jira.codehaus.org/browse/MRM-544 > Project: Archiva > Issue Type: Bug > Components: indexing >Affects Versions: 1.0-beta-2 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-beta-4 > > > This was left out from MRM-37 -- 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: (MRM-454) Index not updated after repository purge
[ http://jira.codehaus.org/browse/MRM-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-454 started by Maria Odea Ching. > Index not updated after repository purge > > > Key: MRM-454 > URL: http://jira.codehaus.org/browse/MRM-454 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-beta-1 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-beta-4 > > > Please see comments MRM-294 for more info -- 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: (MNG-2290) Generated URLs in POMs of child modules
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110776
]
Joerg Schaible edited comment on MNG-2290 at 10/22/07 12:43 AM:
I've linked the superceding issue.
was:
I've linked the superseeding issue.
> Generated URLs in POMs of child modules
> ---
>
> Key: MNG-2290
> URL: http://jira.codehaus.org/browse/MNG-2290
> Project: Maven 2
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.4
>Reporter: Joerg Schaible
> Fix For: 2.0.8
>
>
> Maven has quite some elements where a URL or a path is modified automatically
> for child POMs (the ones I am currently aware of):
> - url
> - scm/connection
> - scm/developerConnection
> - scm/url
> - distributionManagement/site/url
> While expanding this path with "/${pom.artifactId}" sounds reasonable, this
> approach fails badly for complex projects with more hierarchy levels. Suppose
> we have a directory structure like:
> * project
> ** core
> *** provider
> commons
> impl1
> In this hierarchy all POMs for _project_, _core_ and _provider_ are of
> package type _pom_, while _commons_ and _impl1_ is of type _jar_. The
> "artifactId" approach now simply assumes that all POMs in the hierarchy are
> named like the current directory. This does simply not match. Suppose those
> jar artifacts are used in an enterprise or web app. Then every artifact is
> located in one single directory and therefore the names have to be unique.
> But if you decide to take an artifact name different to the directory name,
> you have to add the definition in every POM, because the scm elements are
> simply wrong.
> An even worse scenario are components that can be provided using different
> technologies. We have a lot of such structures:
> * component
> ** jar
> ** war
> ** ear
> * *_jar_:* the core functionality
> * *_war_:* the core functionality integrated and eccessible with a web
> application
> * *_ear_:* the complete component as enterprise app, if it makes sense to
> deploy the functionality on a different app server
> _component_ has a POM of package type _pom_; _jar_, _war_ and _ear_ have POMs
> with the according package type. All of the three POMs use the same
> artifactId though. In this case not only the scm elements break, but also the
> URLs for the site, since they are all the same for all three artifacts.
> All of this could have been avoided, if the expanded part is not the
> artifactId, but the basename of the current directory. Especially for the scm
> elements, this is IMHO the only valid assumption.
> It would already help us, if this auto-expansion could be turned off to allow
> the definition of a single property in each POM for a correct interpolation
> of those values, but there seems no such option ^1^. So you *have to* add
> those elements under all circumstances into every POM.
> 1) The _tagBase_ of the release plugin does no such auto-expansion, which
> makes it quite easy to use a property for it, that can be set individually in
> every POM without adding any plugin configuration.
--
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-2290) Generated URLs in POMs of child modules
[
http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Schaible closed MNG-2290.
---
Resolution: Fixed
Fix Version/s: (was: 2.0.x)
2.0.8
I've linked the superseeding issue.
> Generated URLs in POMs of child modules
> ---
>
> Key: MNG-2290
> URL: http://jira.codehaus.org/browse/MNG-2290
> Project: Maven 2
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.4
>Reporter: Joerg Schaible
> Fix For: 2.0.8
>
>
> Maven has quite some elements where a URL or a path is modified automatically
> for child POMs (the ones I am currently aware of):
> - url
> - scm/connection
> - scm/developerConnection
> - scm/url
> - distributionManagement/site/url
> While expanding this path with "/${pom.artifactId}" sounds reasonable, this
> approach fails badly for complex projects with more hierarchy levels. Suppose
> we have a directory structure like:
> * project
> ** core
> *** provider
> commons
> impl1
> In this hierarchy all POMs for _project_, _core_ and _provider_ are of
> package type _pom_, while _commons_ and _impl1_ is of type _jar_. The
> "artifactId" approach now simply assumes that all POMs in the hierarchy are
> named like the current directory. This does simply not match. Suppose those
> jar artifacts are used in an enterprise or web app. Then every artifact is
> located in one single directory and therefore the names have to be unique.
> But if you decide to take an artifact name different to the directory name,
> you have to add the definition in every POM, because the scm elements are
> simply wrong.
> An even worse scenario are components that can be provided using different
> technologies. We have a lot of such structures:
> * component
> ** jar
> ** war
> ** ear
> * *_jar_:* the core functionality
> * *_war_:* the core functionality integrated and eccessible with a web
> application
> * *_ear_:* the complete component as enterprise app, if it makes sense to
> deploy the functionality on a different app server
> _component_ has a POM of package type _pom_; _jar_, _war_ and _ear_ have POMs
> with the according package type. All of the three POMs use the same
> artifactId though. In this case not only the scm elements break, but also the
> URLs for the site, since they are all the same for all three artifacts.
> All of this could have been avoided, if the expanded part is not the
> artifactId, but the basename of the current directory. Especially for the scm
> elements, this is IMHO the only valid assumption.
> It would already help us, if this auto-expansion could be turned off to allow
> the definition of a single property in each POM for a correct interpolation
> of those values, but there seems no such option ^1^. So you *have to* add
> those elements under all circumstances into every POM.
> 1) The _tagBase_ of the release plugin does no such auto-expansion, which
> makes it quite easy to use a property for it, that can be set individually in
> every POM without adding any plugin configuration.
--
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-428) Japanese message resource
[ http://jira.codehaus.org/browse/MNG-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110781 ] James William Dumay commented on MNG-428: - Any reason we cant just use UTF8? > Japanese message resource > - > > Key: MNG-428 > URL: http://jira.codehaus.org/browse/MNG-428 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.0-beta-1 > Environment: N/A >Reporter: Takayoshi Kimura >Priority: Minor > Fix For: 2.0.9 > > Attachments: message_ja.properites.patch > > > Now, we got message_ja.properties. -- 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-175) Confluence module does not recognise backslash as escape character
Confluence module does not recognise backslash as escape character -- Key: DOXIA-175 URL: http://jira.codehaus.org/browse/DOXIA-175 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.0-alpha-8 Reporter: Dave Syer Confluence module does not recognise backslash as escape character - it should just escape the character behind it, but actually both characters just get rendered. -- 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
