[jira] Created: (DOXIASITETOOLS-4) DocumentModel needs to be more general
DocumentModel needs to be more general -- Key: DOXIASITETOOLS-4 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-4 Project: Maven Doxia Site Tools Issue Type: Improvement Components: Doc renderer Affects Versions: 1.0-alpha-9 Reporter: Lukas Theussl Fix For: 1.0-beta-1 The DocumentModel needs to provide much more information in order to be useful. * DocumentMeta should provide all the information that could go on a cover page: companyLogo, projectLogo, coverProjectName, coverVersion, coverType, coverProjectCompany, coverDate * DocumentTOC needs to handle nested toc items There's probably more, this is just taken from my current needs for the pdf plugin. -- 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-152) Xdoc parser shouldn't insert anchors for section titles
Xdoc parser shouldn't insert anchors for section titles --- Key: DOXIA-152 URL: http://jira.codehaus.org/browse/DOXIA-152 Project: Maven Doxia Issue Type: Bug Components: Module - Xdoc Affects Versions: 1.0-alpha-9 Reporter: Lukas Theussl Assignee: Lukas Theussl Fix For: 1.0-beta-1 When I removed that in alpha-9 I broke some things in the site-renderer and TOCMacro (see http://tinyurl.com/26f4zh and http://tinyurl.com/2r6u4p for a discussion), so I had to revert it. I think the anchors should be inserted be a sink for a particular output format, if this is desired, not by a parser. We have to find a more general solution that hopefully doesn't break the TOCMacro. I am now seeing some consequences of this: I can't generate a pdf for the doxia site (using the sandbox fo-pdf plugin), because of duplicate anchor ids that are generated, which is exactly the same problem we had in m1: MPPDF-40 -- 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-153) when used as a maven1 proxy, Archiva should handle relocation from maven2 poms
[ http://jira.codehaus.org/browse/MRM-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-153. Resolution: Fixed Patch applied (-r576032) Thanks! :) > when used as a maven1 proxy, Archiva should handle relocation from maven2 poms > -- > > Key: MRM-153 > URL: http://jira.codehaus.org/browse/MRM-153 > Project: Archiva > Issue Type: Improvement > Environment: Archiva as a repository proxy for maven1 >Reporter: nicolas de loof >Assignee: Brett Porter >Priority: Minor > Fix For: 1.0-beta-2 > > Attachments: DefaultProxyManager.java.patch, > DefaultProxyManager.java.patch, MRM-153-test.patch, MRM-153.patch, > MRM-155.patch, MRM153-1.0-beta-2.patch, MRM153-reopened+MRM-268.patch, > MRM153-reopened.patch, patch.patch > > > When a maven1 client asks for /servletapi/jars/servletapi-2.4.jar, Archiva > converts path to the maven2 location of this artifact. As maven1 has no > relocation support, the jar is required in the repo. > Archiva can be more that a proxy : download the artifact POM, read relocation > infos, and return the relocated jar. > attached Patch add a new "applyRelocation" to DefaultProxyManager. > I've tried this code with the servletapi example, but it may be bad designed > as I just discovered maven / archiva APIs. -- 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-460) invalid cache policy
[ http://jira.codehaus.org/browse/MRM-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-460. Resolution: Fixed applied, thanks! > invalid cache policy > > > Key: MRM-460 > URL: http://jira.codehaus.org/browse/MRM-460 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: nicolas de loof >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > Attachments: cache.patch, typo.patch > > > CachedFailuresPolicy has a log typo when the requested policy is not supported > "Unknown **checksum** policyCode" > attached Patch to be applied on archiva-policies. -- 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-308) Maven1 requests are not served
[ http://jira.codehaus.org/browse/MRM-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-308. Assignee: Brett Porter Resolution: Cannot Reproduce Fix Version/s: (was: 1.0-beta-2) I think this has previously been fixed > Maven1 requests are not served > -- > > Key: MRM-308 > URL: http://jira.codehaus.org/browse/MRM-308 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 > Environment: using latest version from SVN: revision 521221 > archiva running on Tomcat-5.5.17 >Reporter: Joerg Vater >Assignee: Brett Porter > > I got one managed repository with two proxied repositories, one for our > locally built artifacts and the central repository. > When I try to retreive an artifact with maven2 path layout (e.g. > ant/ant/1.6.5/ant-1.6.5.jar) everything works fine. > When I try to retreive the same artifact with maven1 path layout > (ant/jars/ant-1.6.5.jar) the jar gets downloaded from the proxied repository > but is not delivered to the client. Client response is a 404 (s. below). In > the local directory it is stored with the maven2 path layout > -- log output: > 2007-03-22 12:20:51,278 4594195 [http-9080-Processor24] DEBUG > org.apache.maven.archiva.proxy.ProxyRequestHandler:default - Artifact > requested is: ant:ant:jar:1.6.5:runtime > 2007-03-22 12:20:51,279 4594196 [http-9080-Processor24] DEBUG > org.apache.maven.archiva.proxy.ProxyRequestHandler:default - Retrieving > ant/ant/1.6.5/ant-1.6.5.pom from ComBOTS Maven2 Repository > 2007-03-22 12:20:51,279 4594196 [http-9080-Processor24] DEBUG > org.apache.maven.archiva.proxy.ProxyRequestHandler:default - Artifact not > found in repository: ComBOTS Maven2 Repository: File: > /data/maven-repo/combots-maven2-repo/ant/ant/1.6.5/ant-1.6.5.pom does not > exist > 2007-03-22 12:20:51,281 4594198 [http-9080-Processor24] DEBUG > org.apache.maven.archiva.proxy.ProxyRequestHandler:default - Retrieving > ant/ant/1.6.5/ant-1.6.5.pom from Maven2 Central Repository > 2007-03-22 12:20:51,728 4594645 [http-9080-Processor24] DEBUG > org.apache.maven.archiva.proxy.ProxyRequestHandler:default - Successfully > downloaded > -- http response: > Error 404 Not Found > Resource in error: > http://mavenproxy:9080/archiva/repository/ant/jars/ant-1.6.5.jar/ant/jars/ant-1.6.5.jar > Exception details: > it.could.webdav.DAVException: Not found > at it.could.webdav.methods.HEAD.process(HEAD.java:52) > at it.could.webdav.methods.GET.process(GET.java:58) > at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79) > at > org.codehaus.plexus.webdav.simple.SimpleDavServerComponent.process(SimpleDavServerComponent.java:142) > at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:147) > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:111) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:8
[jira] Closed: (MRM-211) Cannot use Archiva to get Maven1 Plugins
[ http://jira.codehaus.org/browse/MRM-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-211. Assignee: Brett Porter Resolution: Fixed the patch no longer worked on trunk since it doesn't use maven-artifact, so I fixed it an alternative way and added a test > Cannot use Archiva to get Maven1 Plugins > > > Key: MRM-211 > URL: http://jira.codehaus.org/browse/MRM-211 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Reporter: nicolas de loof >Assignee: Brett Porter > Fix For: 1.0-beta-2 > > Attachments: MRM-211.patch > > > I request maven PMD plugin 1.9 using maven1 > Archiva looks into http://repo1.maven.org/maven2/maven/maven-pmd-plugin/1.9/ > and get the POM -> OK > It then searchs the Artifact as > "maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.plugin" -> NOK > Even looking at maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.jar fails : > the artifact doesn't exist ! It has a POM and a sources-jar but no binary > artifact. Maybe a m1-to-m2 repo-converter 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] Closed: (MRM-385) Maven config docs refer to /proxy urls
[ http://jira.codehaus.org/browse/MRM-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-385. Resolution: Fixed > Maven config docs refer to /proxy urls > -- > > Key: MRM-385 > URL: http://jira.codehaus.org/browse/MRM-385 > Project: Archiva > Issue Type: Improvement > Components: documentation >Reporter: Wendy Smoak >Assignee: Maria Odea Ching >Priority: Critical > Fix For: 1.0-beta-2 > > > The Maven Configuration page still refers to urls containing "/proxy". These > no longer exist. > http://maven.apache.org/archiva/guides/maven-configuration.html > Also incorporate info from: > http://docs.codehaus.org/display/MAVENUSER/Archiva+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] Issue Comment Edited: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107481 ] Piotr Tabor edited comment on MNG-1323 at 9/15/07 7:53 PM: --- MNG-1323-core-integration-tests-3.diff IT0127 rewritten to not use Ant run plugin - as Jason wished. It uses enforcer plugin instead (with new rule) to check if right dependencies are available from the plugin. was: MNG-1323-core-integration-tests-3.diff IT0127 rewritten to not use Ant run plugin - as Jason wished. It uses enforcer plugin instead (with new rulu) to check if right dependencies are available from the plugin. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.0.x > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, > MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Tabor updated MNG-1323: - Attachment: MNG-1323-core-integration-tests-3.diff MNG-1323-core-integration-tests-3.diff IT0127 rewritten to not use Ant run plugin - as Jason wished. It uses enforcer plugin instead (with new rulu) to check if right dependencies are available from the plugin. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.0.x > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, > MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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-1718) RediJedi Components Upload
RediJedi Components Upload -- Key: MAVENUPLOAD-1718 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1718 Project: maven-upload-requests Issue Type: Task Reporter: Todd Orr http://redijedi-t5-components.googlecode.com/files/redijedi-t5-components-0.0.3-bundle.jar http://redijedi.com/development/redijedi-t5-components/site/team-list.html http://redijedi.com/development/redijedi-t5-components/site/ A collection of Tapestry 5 components. -- 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-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107474 ] Piotr Tabor commented on MNG-1323: -- Patch for trunk(2.1) was commited by Jason van Zyl. Patch for 2.0.x is waiting to be commited (http://jira.codehaus.org/secure/attachment/29268/MNG-1323-components-2.0.x.diff). I hope the issue is likely to be marked as : Fix version: 2.1-alpha-1, 2.0.8 > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.0.x > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Tabor updated MNG-1323: - Attachment: MNG1323-maven-core-2.1.diff Patch for trunk (2.1) - (rev. 575973.) All integration tests pass. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 2.0.x > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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: (MJAVADOC-149) Newline in ${project.organization.name} makes javadoc fail
[
http://jira.codehaus.org/browse/MJAVADOC-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MJAVADOC-149:
---
Attachment: remove-newlines.patch
The attached patch should solve this issue. All problematic string arguments
that I know of are passed through the new helper method newlineFreeArgument().
Note that I chose to replace newlines with spaces rather than simply delete
them as a newline is actually a whitespace and separates words.
The patch also includes a unit test named "newline-test" to check for the
newline handling. It is basically a copy&paste of the existing
header-bottom-test, just extended to check some further parameters. You may
want to either delete the header-bottom-test or split the newline-test into
smaller tests if you want to check parameters individually to increase
expressiveness of test failures.
> Newline in ${project.organization.name} makes javadoc fail
> --
>
> Key: MJAVADOC-149
> URL: http://jira.codehaus.org/browse/MJAVADOC-149
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: Maven 2.0.7, JDK 1.5.0_12, Win
>Reporter: Benjamin Bentmann
> Attachments: remove-newlines.patch
>
>
> Consider the following POM snippet:
> {code}
>
> My company,
> my department
>
> {code}
> The Javadoc plugin outputs the following to the options file, using its
> default configuration:
> {code}-bottom
> 'Copyright © 2007 My company,
> my department. All Rights Reserved.'{code}
> This actually makes javadoc fail with the following errors:{code}javadoc:
> error - Illegal package name: "department."
> javadoc: error - Illegal package name: "Reserved."
> javadoc: error - Illegal package name: ""
> javadoc: warning - No source files for package my
> javadoc: warning - No source files for package All
> javadoc: warning - No source files for package Rights{code}
> Since line terminators are used as separators within the arg files, the
> Javadoc plugin should replace line terminators (in all fashions) with spaces
> before writing out any POM value so that the formatting of the XML contents
> does not matter.
--
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: (MIDEA-105) Allow modules to be grouped by parent artifactId
[ http://jira.codehaus.org/browse/MIDEA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MIDEA-105: -- Affects Version/s: (was: 2.2) 2.1 > Allow modules to be grouped by parent artifactId > > > Key: MIDEA-105 > URL: http://jira.codehaus.org/browse/MIDEA-105 > Project: Maven 2.x IDEA Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Jason Dillon > Attachments: MIDEA-105.diff > > -- 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: (ARCHETYPE-101) maven-archetype-simple 1.0 is broken
[ http://jira.codehaus.org/browse/ARCHETYPE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107448 ] Shane Isbell commented on ARCHETYPE-101: With NMaven, I verified that version maven-archetype-plugin:1.0-alpha7 works with the META-INF/archetype.xml path. > maven-archetype-simple 1.0 is broken > > > Key: ARCHETYPE-101 > URL: http://jira.codehaus.org/browse/ARCHETYPE-101 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 1.0 > Environment: Windows XP, Java(TM) SE Runtime Environment (build > 1.6.0_02-b05), maven 2.0.7 >Reporter: David J. M. Karlsen >Priority: Critical > > Archetype is broken. > Running mvn archetype:create -DgroupId=com.davidkarlsen.jmsproxy > -DartifactId=jmsproxy -DarchetypeArtifactId=maven-archetype-simple -U -cpu > results in > [INFO] Using following parameters for creating Archetype: > maven-archetype-simple:RELEASE > [INFO] > > [INFO] Parameter: groupId, Value: com.davidkarlsen.jmsproxy > [INFO] Parameter: packageName, Value: com.davidkarlsen.jmsproxy > [INFO] Parameter: package, Value: com.davidkarlsen.jmsproxy > [INFO] Parameter: artifactId, Value: jmsproxy > [INFO] Parameter: basedir, Value: C:\data > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error creating from archetype > Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Sat Sep 15 13:53:06 CEST 2007 > [INFO] Final Memory: 4M/8M > [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] Commented: (ARCHETYPE-101) maven-archetype-simple 1.0 is broken
[ http://jira.codehaus.org/browse/ARCHETYPE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107446 ] Wendy Smoak commented on ARCHETYPE-101: --- I ran into something similar recently with an NMaven archetype. The docs say that archetype.xml belongs _directly_ in META-INF: http://maven.apache.org/plugins/maven-archetype-plugin/examples/archetype.html So why is the plugin looking in META-INF/maven? David, what version of the archetype plugin are you using? > maven-archetype-simple 1.0 is broken > > > Key: ARCHETYPE-101 > URL: http://jira.codehaus.org/browse/ARCHETYPE-101 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 1.0 > Environment: Windows XP, Java(TM) SE Runtime Environment (build > 1.6.0_02-b05), maven 2.0.7 >Reporter: David J. M. Karlsen >Priority: Critical > > Archetype is broken. > Running mvn archetype:create -DgroupId=com.davidkarlsen.jmsproxy > -DartifactId=jmsproxy -DarchetypeArtifactId=maven-archetype-simple -U -cpu > results in > [INFO] Using following parameters for creating Archetype: > maven-archetype-simple:RELEASE > [INFO] > > [INFO] Parameter: groupId, Value: com.davidkarlsen.jmsproxy > [INFO] Parameter: packageName, Value: com.davidkarlsen.jmsproxy > [INFO] Parameter: package, Value: com.davidkarlsen.jmsproxy > [INFO] Parameter: artifactId, Value: jmsproxy > [INFO] Parameter: basedir, Value: C:\data > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error creating from archetype > Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Sat Sep 15 13:53:06 CEST 2007 > [INFO] Final Memory: 4M/8M > [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] Created: (ARCHETYPE-101) maven-archetype-simple 1.0 is broken
maven-archetype-simple 1.0 is broken Key: ARCHETYPE-101 URL: http://jira.codehaus.org/browse/ARCHETYPE-101 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 1.0 Environment: Windows XP, Java(TM) SE Runtime Environment (build 1.6.0_02-b05), maven 2.0.7 Reporter: David J. M. Karlsen Priority: Critical Archetype is broken. Running mvn archetype:create -DgroupId=com.davidkarlsen.jmsproxy -DartifactId=jmsproxy -DarchetypeArtifactId=maven-archetype-simple -U -cpu results in [INFO] Using following parameters for creating Archetype: maven-archetype-simple:RELEASE [INFO] [INFO] Parameter: groupId, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: packageName, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: package, Value: com.davidkarlsen.jmsproxy [INFO] Parameter: artifactId, Value: jmsproxy [INFO] Parameter: basedir, Value: C:\data [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Sat Sep 15 13:53:06 CEST 2007 [INFO] Final Memory: 4M/8M [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] Created: (MEAR-75) Incorrect file name in class path (in manifest) if specifying different bundleFileName for module
Incorrect file name in class path (in manifest) if specifying different
bundleFileName for module
-
Key: MEAR-75
URL: http://jira.codehaus.org/browse/MEAR-75
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Environment: Windows XP SP2, Maven 2.0.7, JDK 1.5.0_12
Reporter: Anders Hammar
Attachments: jbossaop-poc.zip
The file name included in the class path in the generated Manifest.mf file is
incorrect if a different bundle file name is defined in the configuration for
the ear plugin. The file name used in the class path is the original file name,
not the defined bundle file name (which is the actual file name in the created
ear).
In my POM I have:
{code:title=pom.xml|borderStyle=solid}
...
jbossaop-poc
aop
jar
...
maven-ear-plugin
true
jbossaop-poc
aop
aop-${pom.version}.aop
true
{code}
In the resulting ear file, the included artifact 'aop-1.0-SNAPSHOT.jar' has
been renamed to 'aop-1.0-SNAPSHOT.aop'. However, in the Manifest.mf (in the
ear) the class path incorrectly specifies:
Class-Path: aop-1.0-SNAPSHOT.jar
Attached is a multi-module project that should reproduce this.
--
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-1435) Release prepare not working
[ http://jira.codehaus.org/browse/CONTINUUM-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107442 ] Olivier Lamy commented on CONTINUUM-1435: - Hi Dario, Your patches look good. But it's patches and it looks you have made it with the 1.1-beta-2 tags. It will be easier to apply if you provide only one patch file and running the svn diff cli in the continuum root directory. Can you checkout the trunk and provide your patch against the trunk ? Thanks, -- Olivier > Release prepare not working > --- > > Key: CONTINUUM-1435 > URL: http://jira.codehaus.org/browse/CONTINUUM-1435 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-2 > Environment: Java 5 Update 12 > Maven 2.0.4 >Reporter: Dário Oliveros >Priority: Blocker > Fix For: 1.1-beta-3 > > Attachments: continuum-release-patch.txt, continuum-webapp-patch.txt > > > The following error occurs when trying to prepare a release of a project: > java.io.FileNotFoundException: 1/pom.xml (No such file or directory) > Note: It used to work on 1.1-beta-1 version. > I noticed that the WORKING_DIRECTORY column of the PROJECT table does not > contain the absolute path anymore. So when invoking the > project.getWorkingDirectory() method on ReleasePrepareAction class you will > get as result the relative path only. > This bug can be reproduced by doing a fresh install, adding a new Maven 2 > project and preparing its release. -- 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
