[jira] Commented: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137330#action_137330
]
Lukas Theussl commented on MSITE-332:
-
The doxia-logging-api should not be resolved at all, it can only be loaded if
you are either using site-plugin-2.0-beta-8-SNAPSHOT,
p-i-r-plugin-2.2-SNAPSHOT, or if you are running maven-2.0.10-SNAPSHOT. If this
is not the case then I am missing something. Check 'mvn dependency:tree' or run
with -X to see where it's coming from.
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
[jira] Created: (MRELEASE-351) xml declaration removed on release
xml declaration removed on release -- Key: MRELEASE-351 URL: http://jira.codehaus.org/browse/MRELEASE-351 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-7 Reporter: Johan Andrén The declarations in our pom-files are removed when we run the releaseplugin. -- 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-351) xml declaration removed on release
[ http://jira.codehaus.org/browse/MRELEASE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-351. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.0-beta-8 Duplicate of MRELEASE-221. > xml declaration removed on release > -- > > Key: MRELEASE-351 > URL: http://jira.codehaus.org/browse/MRELEASE-351 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-7 >Reporter: Johan Andrén >Assignee: Benjamin Bentmann > Fix For: 2.0-beta-8 > > > The declarations in our pom-files are > removed when we run the releaseplugin. -- 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: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137333#action_137333
]
Lukas Theussl commented on MSITE-332:
-
On the bright side, I can reproduce your original problem... :)
Following your steps with archetype:create and specifying site and pir plugins
in the created pom, I get exactly the same stacktrace as you posted above.
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
> at
> sun.io.ByteToCharConverter.getCon
[jira] Updated: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-332:
Attachment: MSITE-332.tar.gz
Attaching the test project for definiteness, I am running maven-2.0.9 btw.
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
> Attachments: MSITE-332.tar.gz
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
> at
> sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java:68)
> at sun.nio.cs.StreamDecoder$ConverterSD.(StreamDecoder.java:224)
> a
[jira] Created: (ARCHETYPE-180) Lost curly brackets when creating project from an archetype
Lost curly brackets when creating project from an archetype
---
Key: ARCHETYPE-180
URL: http://jira.codehaus.org/browse/ARCHETYPE-180
Project: Maven Archetype
Issue Type: Bug
Affects Versions: 2.0-alpha-3
Reporter: Atef Haouari
Lost curly brackets when creating project from an archetype
Exemple: #{ejbName} becomes #ejbName
--
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: (MDOCCK-12) @Override let QDOX fail for this plugin
@Override let QDOX fail for this plugin --- Key: MDOCCK-12 URL: http://jira.codehaus.org/browse/MDOCCK-12 Project: Maven 2.x Documentation Checker Plugin Issue Type: Bug Affects Versions: 1.0-beta-2 Environment: Win XP Reporter: MTStorm Priority: Minor The plugin fails when QDox hit @Override. Here is the stacktrace: [INFO] Trace com.thoughtworks.qdox.parser.ParseException: syntax error @[33,5] in ...my java file at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504) at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610) at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308) at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) at org.apache.maven.plugin.docck.CheckPluginDocumentationMojo.checkPackagingSpecificDocumentation(CheckPluginDocumentationMojo.java:67) at org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.checkProject(AbstractCheckDocumentationMojo.java:319) at org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.execute(AbstractCheckDocumentationMojo.java:149) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 12 seconds [INFO] Finished at: Wed Jun 04 10:40:35 CEST 2008 [INFO] Final Memory: 10M/19M [INFO] -- This message is automatically generated by JIRA. - If you think it 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: (MPLUGIN-114) PluginXdocGenerator NullPointerException
[ http://jira.codehaus.org/browse/MPLUGIN-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137343#action_137343 ] Marc Lustig commented on MPLUGIN-114: - using 2.4.2-SNAPSHOT, I get java.lang.NullPointerException at org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute(PluginXdocGenerator.java:96) ---> still a NPE, just one line below > PluginXdocGenerator NullPointerException > > > Key: MPLUGIN-114 > URL: http://jira.codehaus.org/browse/MPLUGIN-114 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: API >Affects Versions: 2.3 >Reporter: Garvin LeClaire >Assignee: Benjamin Bentmann > Fix For: 2.4.2 > > Attachments: pom.xml > > > When creating a site I get the following stack trace: > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute(PluginXdocGenerator.java:95) > at > org.apache.maven.plugin.plugin.PluginReport.generatePluginDocumentation(PluginReport.java:224) > at > org.apache.maven.plugin.plugin.PluginReport.executeReport(PluginReport.java:178) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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: 33 seconds > [INFO] Finished at: Wed May 14 23:36:51 EDT 2008 > [INFO] Final Memory: 41M/63M > I have tried and get the same results with version of the site plg-in back to > 2.0-beta-3 > Any suggestions?? -- 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: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137344#action_137344
]
Lukas Theussl commented on MSITE-332:
-
It only happens if there is no site.xml. It works fine with a minimal site.xml,
even if there is no encoding specified:
{code:xml}
{code}
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
> Attachments: MSITE-332.tar.gz
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
> at
> sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java:68)
[jira] Created: (SCM-384) CVS providers ignore module specified by SCM URL
CVS providers ignore module specified by SCM URL Key: SCM-384 URL: http://jira.codehaus.org/browse/SCM-384 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-cvs Affects Versions: 1.1 Reporter: Sergey Zakusov Priority: Critical If you specify a module in SCM URL, for example: scm:cvs:pserver:cvs:[EMAIL PROTECTED]:/cvsroot:samba - the module will be ignored for all commands. Expected behaviour: the specified module should be a root for all operations and if some command returns paths - the paths should be relative for specified module. -- 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-180) Lost curly brackets when creating project from an archetype
[
http://jira.codehaus.org/browse/ARCHETYPE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137345#action_137345
]
Raphaël Piéroni commented on ARCHETYPE-180:
---
May you please describe the problem a bit more...
with Steps to reproduce, expected behaviour and gotten behaviour.
Please don't forget to also attach the command line(s) you used
and the trace from the maven execution(s).
Please also consider to attahce the test project for us to reproduce.
Thanks
> Lost curly brackets when creating project from an archetype
> ---
>
> Key: ARCHETYPE-180
> URL: http://jira.codehaus.org/browse/ARCHETYPE-180
> Project: Maven Archetype
> Issue Type: Bug
>Affects Versions: 2.0-alpha-3
>Reporter: Atef Haouari
>
> Lost curly brackets when creating project from an archetype
> Exemple: #{ejbName} becomes #ejbName
--
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: (MJAR-68) multi module release fails because of test-jar
[ http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137348#action_137348 ] Michael Mattox commented on MJAR-68: I agree with Chad. We just ran into this problem. Any update? For now we're using maven.skip.exec=true. > multi module release fails because of test-jar > -- > > Key: MJAR-68 > URL: http://jira.codehaus.org/browse/MJAR-68 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: maven 2.0.5 >Reporter: Yuri Schimke > > The release plugin is failing in the prepare task > mvn release:prepare > seemingly because it can't find the test-jar that has just been built by the > previous module i.e. built within. > Are there some examples in the wild of using the test-jar on a multi module > project that does releases? > The (nasty) workaround I have for now, is to wait for the build to fail and > then > mvn install > So the test-jar (and other artifacts) are in my local repository and then > continue > mvn release:prepare -- 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: (MJAR-68) multi module release fails because of test-jar
[ http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137349#action_137349 ] werner mueller commented on MJAR-68: as mentioned above you can do a release with different preparation goals: $ mvn release:prepare -DpreparationGoals="clean install" $ mvn release:perform this is still a workaround but well it works (creating the test-jar and execute tests in depending modules) > multi module release fails because of test-jar > -- > > Key: MJAR-68 > URL: http://jira.codehaus.org/browse/MJAR-68 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: maven 2.0.5 >Reporter: Yuri Schimke > > The release plugin is failing in the prepare task > mvn release:prepare > seemingly because it can't find the test-jar that has just been built by the > previous module i.e. built within. > Are there some examples in the wild of using the test-jar on a multi module > project that does releases? > The (nasty) workaround I have for now, is to wait for the build to fail and > then > mvn install > So the test-jar (and other artifacts) are in my local repository and then > continue > mvn release:prepare -- 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: (SCM-385) AbstractCvsChangeLogCommand create a wrong command for case when startVersion == endVersion
AbstractCvsChangeLogCommand create a wrong command for case when startVersion == endVersion --- Key: SCM-385 URL: http://jira.codehaus.org/browse/SCM-385 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-cvs Affects Versions: 1.1 Environment: C:\>cvs --version Concurrent Versions System (CVS) 1.12.13a (client) Copyright (C) 2005 Free Software Foundation, Inc. Senior active maintainers include Larry Jones, Derek R. Price, and Mark D. Baushke. Please see the AUTHORS and README files from the CVS distribution kit for a complete list of contributors and copyrights. CVS may be copied only under the terms of the GNU General Public License, a copy of which can be found with the CVS distribution kit. Specify the --help option for further information about CVS C:\>cvs -H rlog Usage: cvs rlog [-lRhtNb] [-r[revisions]] [-d dates] [-s states] [-w[logins]] [files...] -l Local directory only, no recursion. -b Only list revisions on the default branch. -h Only print header. -R Only print name of RCS file. -t Only print header and descriptive text. -N Do not list tags. -S Do not print name/header if no revisions selected. -d, -r, -s, & -w have little effect in conjunction with -b, -h, -R, and -t without this option. -r[revisions] A comma-separated list of revisions to print: rev1:rev2 Between rev1 and rev2, including rev1 and rev2. rev1::rev2 Between rev1 and rev2, excluding rev1. rev:rev and following revisions on the same branch. rev:: After rev on the same branch. :revrev and previous revisions on the same branch. ::rev rev and previous revisions on the same branch. rev Just rev. branch All revisions on the branch. branch. The last revision on the branch. -d datesA semicolon-separated list of dates (D1http://svn.emforge.org/svn/emforge/maven-scm it just returns one revision named 3240 But the same algorithm does not work with CVS providers - the problem is in that AbstractCvsChangeLogCommand uses duplicated colon "::" to specify revisions, but it means that rev1 will be excluded from result: -r[revisions] A comma-separated list of revisions to print: rev1:rev2 Between rev1 and rev2, including rev1 and rev2. rev1::rev2 Between rev1 and rev2, excluding rev1. So AbstractCvsChangeLogCommand should use first variant "rev1:rev2" to specify revisions. -- 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: (MCHANGELOG-86) Error with outputEncoding parameter set to UTF-8
Error with outputEncoding parameter set to UTF-8
Key: MCHANGELOG-86
URL: http://jira.codehaus.org/browse/MCHANGELOG-86
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: Windows XP Pro SP2, Maven 2.0.9, Java SE 1.5.0 Update 15,
Subversion 1.4.6
Reporter: Joël Royer
Attachments: ScreenShot_2008-06-04_140551.png
When using UTF-8 as setting for the parameter outputEncoding, we've got this
error:
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to:
D:\devs\projects\Test\workspace\TestWebapp\target\changelog.xml
[INFO] Executing: svn --non-interactive log -v -r "{2008-05-05 11:45:19 +}:{
2008-06-05 11:45:19 +}" https://mysubversionsrv/svndev/test/trunk/TestWebapp
[INFO] Working directory: D:\devs\projects\Test\workspace\TestWebapp
[INFO] Generating "Developer Activity" report.
[INFO] Using existing changelog.xml...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error during page generation
Embedded error: Error rendering Maven report: An error occurred while parsing D:
\devs\projects\Test\workspace\TestWebapp\target\changelog.xml
Invalid byte 1 of 1-byte UTF-8 sequence.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 39 seconds
[INFO] Finished at: Wed Jun 04 13:45:23 CEST 2008
[INFO] Final Memory: 41M/63M
[INFO]
The file changelog.xml contains the good header line (), but the file is encoded with ANSI UNIX charset
--
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-177) NullPointerException generating archetype when mirrors are in settings.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137356#action_137356 ] Brian Fox commented on ARCHETYPE-177: - Just a comment on your settings setup, why not just define a mirrorOf * instead of enumerating each one? Also, in Maven 2.0.9+, you can use , to list multiple id's in a single entry. > NullPointerException generating archetype when mirrors are in settings.xml > -- > > Key: ARCHETYPE-177 > URL: http://jira.codehaus.org/browse/ARCHETYPE-177 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes, Generator > Environment: Windows XP Pro >Reporter: Frank Adcock > > When attempting to generate any archetype from the mvn archetype:generate > command I get a null pointer exception thrown if I have mirrors defined in my > settings.xml file. I believe there is a related issue where mvn package will > also get a null pointer exception if a repository specified in the project > pom does not have a matching mirror id in the settings.xml. However, the > stack trace for the archetype generation is: > Choose a number: > (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/2 > 4/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42/43/44) 15: : 6 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : java.lang.NullPointerException > null > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:579) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:227) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.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) > Caused by: org.apache.maven.plugin.MojoFailureException > at > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execu > te(CreateProjectFromArchetypeMojo.java:202) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:558) > ... 16 more > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Wed May 28 17:49:39 EST 2008 > [INFO] Final Memory: 8M/14M > [INFO] > > C:\Documents and Settings\frank\My Documents\Development\Sandbox>mvn -v > Maven version: 2.0.9 > Java version: 1.5.0_08 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > The mirrored settings from the settings.xml file are: > > > public-snapshots > public-snapshots > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public-snapshots > > > nexus-central > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public > central > > > nexus-maven-repo > > http://maven.ho.bushlife.com.au:8081/nexus/content/grou
[jira] Commented: (MCHANGELOG-86) Error with outputEncoding parameter set to UTF-8
[
http://jira.codehaus.org/browse/MCHANGELOG-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137357#action_137357
]
Joël Royer commented on MCHANGELOG-86:
--
Here an extract of my pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
...
...
org.apache.maven.plugins
maven-changelog-plugin
UTF-8
...
> Error with outputEncoding parameter set to UTF-8
>
>
> Key: MCHANGELOG-86
> URL: http://jira.codehaus.org/browse/MCHANGELOG-86
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Windows XP Pro SP2, Maven 2.0.9, Java SE 1.5.0 Update
> 15, Subversion 1.4.6
>Reporter: Joël Royer
> Attachments: ScreenShot_2008-06-04_140551.png
>
>
> When using UTF-8 as setting for the parameter outputEncoding, we've got this
> error:
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to:
> D:\devs\projects\Test\workspace\TestWebapp\target\changelog.xml
> [INFO] Executing: svn --non-interactive log -v -r "{2008-05-05 11:45:19
> +}:{
> 2008-06-05 11:45:19 +}"
> https://mysubversionsrv/svndev/test/trunk/TestWebapp
> [INFO] Working directory: D:\devs\projects\Test\workspace\TestWebapp
> [INFO] Generating "Developer Activity" report.
> [INFO] Using existing changelog.xml...
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: An error occurred while parsing
> D:
> \devs\projects\Test\workspace\TestWebapp\target\changelog.xml
> Invalid byte 1 of 1-byte UTF-8 sequence.
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 39 seconds
> [INFO] Finished at: Wed Jun 04 13:45:23 CEST 2008
> [INFO] Final Memory: 41M/63M
> [INFO]
>
> The file changelog.xml contains the good header line ( encoding="UTF-8"?>), but the file is encoded with ANSI UNIX charset
--
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: (MCHANGELOG-86) Error with outputEncoding parameter set to UTF-8
[
http://jira.codehaus.org/browse/MCHANGELOG-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137357#action_137357
]
jcmg edited comment on MCHANGELOG-86 at 6/4/08 7:14 AM:
--
Here an extract of my pom.xml:
{code:xml}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
...
...
org.apache.maven.plugins
maven-changelog-plugin
UTF-8
...
{code}
was (Author: jcmg):
Here an extract of my pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
...
...
org.apache.maven.plugins
maven-changelog-plugin
UTF-8
...
> Error with outputEncoding parameter set to UTF-8
>
>
> Key: MCHANGELOG-86
> URL: http://jira.codehaus.org/browse/MCHANGELOG-86
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Windows XP Pro SP2, Maven 2.0.9, Java SE 1.5.0 Update
> 15, Subversion 1.4.6
>Reporter: Joël Royer
> Attachments: ScreenShot_2008-06-04_140551.png
>
>
> When using UTF-8 as setting for the parameter outputEncoding, we've got this
> error:
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to:
> D:\devs\projects\Test\workspace\TestWebapp\target\changelog.xml
> [INFO] Executing: svn --non-interactive log -v -r "{2008-05-05 11:45:19
> +}:{
> 2008-06-05 11:45:19 +}"
> https://mysubversionsrv/svndev/test/trunk/TestWebapp
> [INFO] Working directory: D:\devs\projects\Test\workspace\TestWebapp
> [INFO] Generating "Developer Activity" report.
> [INFO] Using existing changelog.xml...
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: An error occurred while parsing
> D:
> \devs\projects\Test\workspace\TestWebapp\target\changelog.xml
> Invalid byte 1 of 1-byte UTF-8 sequence.
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 39 seconds
> [INFO] Finished at: Wed Jun 04 13:45:23 CEST 2008
> [INFO] Final Memory: 41M/63M
> [INFO]
>
> The file changelog.xml contains the good header line ( encoding="UTF-8"?>), but the file is encoded with ANSI UNIX charset
--
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: (MJAVADOC-195) javadoc generation on @Test(expected...) throws Exception (aggregation issue)
javadoc generation on @Test(expected...) throws Exception (aggregation issue) - Key: MJAVADOC-195 URL: http://jira.codehaus.org/browse/MJAVADOC-195 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.3 Environment: 1.5.x Reporter: Quinten Verheyen In a recent build of ours, running javadoc:javadoc on our modules gave the following exception : [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard, method start has thrown an exception java.lang.reflect.InvocationTargetException java.lang.AssertionError: cannot find method org.junit.Test.expected() at com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074) It took me some time to find out that this ONLY fails when the test is part of a module which is more then 1 level deeper then the module from wich the javadoc command is being run. To illustrate, the usage of @Test(expected=...) occured in several of our modules, one of them was directly below the root and a couple of others an extra level down. When I temporarily commented out the modules who were an extra level down, the javadoc generation succeeded, despite that fact there were still tests using @Test(expected=...). Below the configuration in our root pom.xml : org.apache.maven.plugins maven-javadoc-plugin 2.3 true http://java.sun.com/j2se/1.5.0/docs/api http://static.springframework.org/spring/docs/2.0.x/api -- 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: (MNG-3614) settings.xml active profiles executed AFTER project profiles have been loaded and activated/not activated
settings.xml active profiles executed AFTER project profiles have been loaded and activated/not activated - Key: MNG-3614 URL: http://jira.codehaus.org/browse/MNG-3614 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation, Profiles, Settings Affects Versions: 2.0.9 Environment: Solaris 5.10, ubuntu hardy x64 Reporter: Donald Abrams Priority: Minor If you have the following settings.xml in ~/.m2: userSettings true userSettings and another child pom.xml somewhere down the line has a profile with an activation like this: http://maven.apache.org/POM/4.0.0";> 4.0.0 with-something false someproperty true During run-time, the profile with-something will load before userSettings. This causes with-something to be incorrectly not activated (as the property someproperty does not exist). This can be seen with mvn help:active-profiles. I know why this is true, but it is non-intuitive and one would expect settings.xml profiles to be loaded before anything else. -- 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: (MASSEMBLY-329) Filter fail to initialize when build from parent pom while assembly is in child pom
Filter fail to initialize when build from parent pom while assembly is in child pom --- Key: MASSEMBLY-329 URL: http://jira.codehaus.org/browse/MASSEMBLY-329 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Environment: maven 2.0.9 Windows XP Reporter: Andy Yeung Attachments: project-structure.zip I have the project structure which is the same as the attached file. When I try to execute mvn package in the user-ear project directly, the filters are initialized and executed. However if I try to execute mvn package in the parent directory. The filter is gone. When I use -X options, I didn't find the log message "[DEBUG] Initializing assembly filters..." -- 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: (MPLUGIN-114) PluginXdocGenerator NullPointerException
[ http://jira.codehaus.org/browse/MPLUGIN-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137374#action_137374 ] Benjamin Bentmann commented on MPLUGIN-114: --- bq. using 2.4.2-SNAPSHOT At the time of your post, the latest snapshot dated back to April the 17th, I closed this issue May the 18th. New Snapshots have been deployed. > PluginXdocGenerator NullPointerException > > > Key: MPLUGIN-114 > URL: http://jira.codehaus.org/browse/MPLUGIN-114 > Project: Maven 2.x Plugin Tools > Issue Type: Bug > Components: API >Affects Versions: 2.3 >Reporter: Garvin LeClaire >Assignee: Benjamin Bentmann > Fix For: 2.4.2 > > Attachments: pom.xml > > > When creating a site I get the following stack trace: > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute(PluginXdocGenerator.java:95) > at > org.apache.maven.plugin.plugin.PluginReport.generatePluginDocumentation(PluginReport.java:224) > at > org.apache.maven.plugin.plugin.PluginReport.executeReport(PluginReport.java:178) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) > 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: 33 seconds > [INFO] Finished at: Wed May 14 23:36:51 EDT 2008 > [INFO] Final Memory: 41M/63M > I have tried and get the same results with version of the site plg-in back to > 2.0-beta-3 > Any suggestions?? -- 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: (MJAVADOC-195) javadoc generation on @Test(expected...) throws Exception (aggregation issue)
[ http://jira.codehaus.org/browse/MJAVADOC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137375#action_137375 ] Vincent Siveton commented on MJAVADOC-195: -- Could you test it with 2.4 and 2.5-SNAPSHOT? Also, could send us a test case? > javadoc generation on @Test(expected...) throws Exception (aggregation issue) > - > > Key: MJAVADOC-195 > URL: http://jira.codehaus.org/browse/MJAVADOC-195 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: 1.5.x >Reporter: Quinten Verheyen > > In a recent build of ours, running javadoc:javadoc on our modules gave the > following exception : > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - In doclet class com.sun.tools.doclets.standard.Standard, > method start has thrown an exception > java.lang.reflect.InvocationTargetException > java.lang.AssertionError: cannot find method org.junit.Test.expected() > at > com.sun.tools.javac.jvm.ClassReader$AnnotationDeproxy.findAccessMethod(ClassReader.java:1074) > It took me some time to find out that this ONLY fails when the test is part > of a module which is more then 1 level deeper then the module from wich the > javadoc command is being run. > To illustrate, the usage of @Test(expected=...) occured in several of our > modules, one of them was directly below the root and a couple of others an > extra level down. When I temporarily commented out the modules who were an > extra level down, the javadoc generation succeeded, despite that fact there > were still tests using @Test(expected=...). > Below the configuration in our root pom.xml : > > org.apache.maven.plugins > maven-javadoc-plugin > 2.3 > > true > > http://java.sun.com/j2se/1.5.0/docs/api > > http://static.springframework.org/spring/docs/2.0.x/api > > > -- 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: (ARCHETYPE-177) NullPointerException generating archetype when mirrors are in settings.xml
[ http://jira.codehaus.org/browse/ARCHETYPE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-177. - Resolution: Not A Bug Having mirrors is not mandatory, but if one is used, then mirrorOf is a mandatory child element of settings/mirrors/mirror. The exception thrown (NPE) not saying that problem is not an archetype plugin bug. Franck, if you are still concerned with this can you please open a new issue on the MNG's jira project explaining the problem even linking to this issue. Thanks > NullPointerException generating archetype when mirrors are in settings.xml > -- > > Key: ARCHETYPE-177 > URL: http://jira.codehaus.org/browse/ARCHETYPE-177 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes, Generator > Environment: Windows XP Pro >Reporter: Frank Adcock > > When attempting to generate any archetype from the mvn archetype:generate > command I get a null pointer exception thrown if I have mirrors defined in my > settings.xml file. I believe there is a related issue where mvn package will > also get a null pointer exception if a repository specified in the project > pom does not have a matching mirror id in the settings.xml. However, the > stack trace for the archetype generation is: > Choose a number: > (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/2 > 4/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42/43/44) 15: : 6 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : java.lang.NullPointerException > null > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:579) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:227) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.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) > Caused by: org.apache.maven.plugin.MojoFailureException > at > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execu > te(CreateProjectFromArchetypeMojo.java:202) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:558) > ... 16 more > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Wed May 28 17:49:39 EST 2008 > [INFO] Final Memory: 8M/14M > [INFO] > > C:\Documents and Settings\frank\My Documents\Development\Sandbox>mvn -v > Maven version: 2.0.9 > Java version: 1.5.0_08 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > The mirrored settings from the settings.xml file are: > > > public-snapshots > public-snapshots > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public-snapshots > > > nexus-central > > http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public >
[jira] Created: (MNG-3615) Provide Central Repository Download Statistics
Provide Central Repository Download Statistics -- Key: MNG-3615 URL: http://jira.codehaus.org/browse/MNG-3615 Project: Maven 2 Issue Type: New Feature Reporter: Daniel Gredler As Maven becomes more prevalent, fewer people download third-party libraries manually. It would be nice to get some basic download stats for repo1.maven.org, so that developers have some information about which libraries are popular (and which libraries aren't) among the Maven crowd. -- 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: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137396#action_137396
]
Michael Stevens commented on MSITE-332:
---
Thanks for the comments Lukas. You're right, and I had an error in my pom (I
had the maven-site-plugin dependency defined under , not ).
I'm glad you can recreate the original error though, good to know it's a valid
bug.
I'm using maven 2.0.7:
- doxia error caused by either p-i-r-plugin-2.2-SNAPSHOT or
site-plugin-beta-8-SNAPSHOT
- Using p-i-r-2.0.1 and site-plugin-2.0-beta-7-SNAPSHOT, the original error
occurs
- Original error goes away using p-i-r-2.0.1 and site-plugin-2.0-beta-6,
solving my problem
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
> Attachments: MSITE-332.tar.gz
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderin
[jira] Closed: (MEV-590) JSTL 1.2 not installed in repo correctly
[ http://jira.codehaus.org/browse/MEV-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Adcock closed MEV-590. Resolution: Not A Bug Thanks for the response. I was unable to configure the way you describe because I was using mirrors and the proxy agent I was using was Sonatype Nexus beta 2. This did not support legacy repositories and I was trying to figure out what was wrong that I could not get the legacy information. Sonatype has recently released a beta 3.1 for Nexus and this has overcome the mirrorOf problem by allowing the repository to represent legacy repositories as maven2 repos. > JSTL 1.2 not installed in repo correctly > > > Key: MEV-590 > URL: http://jira.codehaus.org/browse/MEV-590 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Frank Adcock > > JSTL 1.2 is located at http://repo1.maven.org/maven2/javax/servlet/jstl/1.2 > It is not referenced in the maven metadata information for the directory > http://repo1.maven.org/maven2/javax/servlet/jstl/ > It does not have any metadata information in the 1.2 directory. > There is no link to the top level jstl directory > http://repo1.maven.org/maven2/jstl/ > It appears as if it was not installed correctly into the repo. > Apologies if this is filed against the wrong project or category. -- 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: (MNG-3616) Null Pointer Exception when mirrorOf missing from mirror in settings.xml
Null Pointer Exception when mirrorOf missing from mirror in settings.xml Key: MNG-3616 URL: http://jira.codehaus.org/browse/MNG-3616 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: Frank Adcock When attempting to generate any archetype from the mvn archetype:generate command I get a null pointer exception thrown if I have mirrors defined in my settings.xml file but fail to have the mirrorOf element set. The stack trace for the archetype generation is: Choose a number: (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/2 4/25/26/27/28/29/30/31/32/33/34/35/36/37/38/39/40/41/42/43/44) 15: : 6 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] : java.lang.NullPointerException null [INFO] [INFO] Trace org.apache.maven.BuildFailureException at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:579) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:227) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) Caused by: org.apache.maven.plugin.MojoFailureException at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execu te(CreateProjectFromArchetypeMojo.java:202) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:558) ... 16 more [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Wed May 28 17:49:39 EST 2008 [INFO] Final Memory: 8M/14M [INFO] C:\Documents and Settings\frank\My Documents\Development\Sandbox>mvn -v Maven version: 2.0.9 Java version: 1.5.0_08 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" The mirrored settings from the settings.xml file are: nexus-central http://maven.ho.bushlife.com.au:8081/nexus/content/groups/public As a user you receive a null pointer exception because of something missing in the settings.xml file. At the very least you should receive an error message indicating the problem. If you can have a situation where the mirrorOf setting is optional, then it should not be throwing a null pointer exception but handling it better. -- 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: (MSITE-332) Unable to load parent project from a relative path: Could not find the model file '/pom.xml'. for project unknown
[
http://jira.codehaus.org/browse/MSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137401#action_137401
]
Lukas Theussl commented on MSITE-332:
-
And you also have no site.xml? In any case, this issue has nothing to do with
the relative path of the parent pom, the title should be changed.
> Unable to load parent project from a relative path: Could not find the model
> file '/pom.xml'. for project unknown
> --
>
> Key: MSITE-332
> URL: http://jira.codehaus.org/browse/MSITE-332
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
>Affects Versions: 2.0-beta-7
>Reporter: Michael Stevens
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-7
>
> Attachments: MSITE-332.tar.gz
>
>
> Execute site:site
> The plugin seems to look for a pom file in the directory above the project
> directory.
> This started occurring last night for us, using
> maven-site-plugin:2.0-beta-7-SNAPSHOT.
> Note that the project in question uses a parent POM, but does not specify a
> relative path.
> Here is the stack trace:
> [INFO] Unable to load parent project from a relative path: Could not find the
> model file 'c:\workdir\projects\pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] SiteToolException: Error reading default site descriptor:
> ${OUTPUTENCODING}
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> Caused by: org.apache.maven.plugin.MojoExecutionException: SiteToolException:
> Error reading default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:230)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by: org.apache.maven.doxia.tools.SiteToolException: Error reading
> default site descriptor: ${OUTPUTENCODING}
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:527)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:226)
> ... 20 more
> Caused by: java.io.UnsupportedEncodingException: ${OUTPUTENCODING}
> at sun.io.Converters.getConverterClass(Converters.java:218)
> at sun.io.Converters.newConverter(Converters.java:251)
> at
> sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java:68
[jira] Closed: (ARCHETYPE-172) calling mvn archetype:generate -DinteractiveMode=false still prompts user "Y:"
[ http://jira.codehaus.org/browse/ARCHETYPE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-172. - Resolution: Fixed Fix Version/s: 2.0-alpha-4 Fixed since revision 663372 The old way to call non interactive mode before this commit was -Darchetype.interactive It changed to -DinteractiveMode Please notice that -B (for batch mode) was usable in 2.0-alpha-3 and still remains as the main way to achieve non interactiveness. > calling mvn archetype:generate -DinteractiveMode=false still prompts user "Y:" > -- > > Key: ARCHETYPE-172 > URL: http://jira.codehaus.org/browse/ARCHETYPE-172 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Affects Versions: 2.0-alpha-2, 2.0-alpha-3 >Reporter: Jeff Campbell > Fix For: 2.0-alpha-4 > > > I have a simple script that calls maven archetype from the command line with > the full archetype command-line. The script hangs because the > archetype:generate prompts for the user to hit Y: at the command prompt even > thought I specified -DinteractiveMode=false in the script. > Expected Results: Maven archetype:generate executes with-out prompting the > user for any input when using -DinteractiveMode=false -- 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: (ARCHETYPE-171) maven-archetype-quickstart:1.0 is not configured
[ http://jira.codehaus.org/browse/ARCHETYPE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raphaël Piéroni closed ARCHETYPE-171. - Resolution: Fixed Fix Version/s: 2.0-alpha-4 Fixed since revision 663375 Here is the new behaviour: $ mvn archetype:generate -B [INFO] [archetype:generate] [INFO] Generating project in Batch mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) [WARNING] Property groupId is missing. Add -DgroupId=someValue [WARNING] Property artifactId is missing. Add -DartifactId=someValue [WARNING] Property package is missing. Add -Dpackage=someValue [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not configured > maven-archetype-quickstart:1.0 is not configured > > > Key: ARCHETYPE-171 > URL: http://jira.codehaus.org/browse/ARCHETYPE-171 > Project: Maven Archetype > Issue Type: Bug > Components: Plugin >Affects Versions: 2.0-alpha-3 > Environment: mvn 2.0.9 > jdk 1.7.0 >Reporter: Andreas Höhmann >Priority: Critical > Fix For: 2.0-alpha-4 > > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] > > [INFO] Building Maven Default Project > [INFO]task-segment: [archetype:generate] (aggregator-style) > [INFO] > > [INFO] Preparing archetype:generate > [INFO] No goals needed for project - skipping > [INFO] Setting property: classpath.resource.loader.class => > 'org.codehaus.plexus > .velocity.ContextClassLoaderResourceLoader'. > [INFO] Setting property: velocimacro.messages.on => 'false'. > [INFO] Setting property: resource.loader => 'classpath'. > [INFO] Setting property: resource.manager.logwhenfound => 'false'. > [INFO] [archetype:generate] > [INFO] Generating project in Batch mode > [INFO] No archetype defined. Using maven-archetype-quickstart > (org.apache.maven. > archetypes:maven-archetype-quickstart:1.0) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] : org.apache.maven.archetype.exception.ArchetypeNotConfigured: > Archetype > org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not configured > Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not > conf > igured > Archetype org.apache.maven.archetypes:maven-archetype-quickstart:1.0 is not > conf > igured > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Mon May 19 22:48:34 CEST 2008 > [INFO] Final Memory: 8M/15M > [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: (MJAVADOC-194) javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project
[
http://jira.codehaus.org/browse/MJAVADOC-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lois Modesitt updated MJAVADOC-194:
---
Attachment: JavaDocTestCase.zip
UseCase:
Create aggregated javadocs for both source code in the default location and
source code in an additional location. I include the "additional source code
directory"
using the "build-helper-maven-plugin" which is included in the parent pom:
JavaDocTestCase/pom.xml.
Problem:
When I run the command:
mvn javadoc:javadoc -Daggregate=true
using javadoc version 2.4, the classes in the "additional" source code directory
is not included in the aggregated javadocs.
***Using javadoc version 2.3, works correctly by including the additional
source code directory.**
Please read the file "Readme.txt" for more information about this test.
Let me know if you have any more questions.
> javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when
> aggregating a javadoc for a project
> ---
>
> Key: MJAVADOC-194
> URL: http://jira.codehaus.org/browse/MJAVADOC-194
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Lois Modesitt
> Attachments: JavaDocTestCase.zip, m209out-UsingJavadoc2.3.txt,
> m209out-UsingJavadoc2.4.txt, m209out-UsingJavadoc2.5SNAPSHOT.txt
>
>
> The javadoc does not include the "additional source" files defined using the
> "build-helper:add-source" in each of my subproject pom files when using
> javadoc plugin 2.4. The javadoc plugin 2.3 worked correctly.
> I use the "build-helper:add-source" to include additional source directories
> to the build. The additional source directories contain my generated source
> file. When I run the command using javadoc plugin version 2.4:
> mvn javadoc:javadoc -Daggregate=true
> (or have the aggregate=true specified inside of the pom) the
> "build-helper:add-source" is not run for each of the subprojects before the
> aggregated javadoc is created. Therefore the javadoc does not include the
> documentation for the files in the additional source directories.
> I also noted that the output for 2.3 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc] (aggregator-style)
> but the output for the 2.4 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc]
> I am not sure if the above output is changed between versions or if the
> "aggregator-style" is not detectd in the 2.4 version and has an influence in
> this issue.
> I have attached the log file for running my project using javadoc plugin
> version 2.3 and 2.4. Version 2.3 works and version 2.4 does not include the
> additional source files in the aggregated javadoc.
--
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: (MJAVADOC-194) javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when aggregating a javadoc for a project
[
http://jira.codehaus.org/browse/MJAVADOC-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137409#action_137409
]
lois edited comment on MJAVADOC-194 at 6/4/08 4:42 PM:
UseCase:
Create aggregated javadocs for both source code in the default location and
source code in an additional location. I include the "additional source code
directory"
using the "build-helper-maven-plugin" which is included in the parent pom:
JavaDocTestCase/pom.xml.
Problem:
When I run the command:
mvn javadoc:javadoc -Daggregate=true
using javadoc version 2.4, the classes in the "additional" source code directory
is not included in the aggregated javadocs.
***Using javadoc version 2.3, works correctly by including the additional
source code directory.**
See the attached file JavaDocTestCase.zip.
Please read the file "Readme.txt" for more information about this test.
Let me know if you have any more questions.
was (Author: lois):
UseCase:
Create aggregated javadocs for both source code in the default location and
source code in an additional location. I include the "additional source code
directory"
using the "build-helper-maven-plugin" which is included in the parent pom:
JavaDocTestCase/pom.xml.
Problem:
When I run the command:
mvn javadoc:javadoc -Daggregate=true
using javadoc version 2.4, the classes in the "additional" source code directory
is not included in the aggregated javadocs.
***Using javadoc version 2.3, works correctly by including the additional
source code directory.**
Please read the file "Readme.txt" for more information about this test.
Let me know if you have any more questions.
> javadoc 2.4 does not [build-helper:add-source {execution: add-source}] when
> aggregating a javadoc for a project
> ---
>
> Key: MJAVADOC-194
> URL: http://jira.codehaus.org/browse/MJAVADOC-194
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Lois Modesitt
> Attachments: JavaDocTestCase.zip, m209out-UsingJavadoc2.3.txt,
> m209out-UsingJavadoc2.4.txt, m209out-UsingJavadoc2.5SNAPSHOT.txt
>
>
> The javadoc does not include the "additional source" files defined using the
> "build-helper:add-source" in each of my subproject pom files when using
> javadoc plugin 2.4. The javadoc plugin 2.3 worked correctly.
> I use the "build-helper:add-source" to include additional source directories
> to the build. The additional source directories contain my generated source
> file. When I run the command using javadoc plugin version 2.4:
> mvn javadoc:javadoc -Daggregate=true
> (or have the aggregate=true specified inside of the pom) the
> "build-helper:add-source" is not run for each of the subprojects before the
> aggregated javadoc is created. Therefore the javadoc does not include the
> documentation for the files in the additional source directories.
> I also noted that the output for 2.3 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc] (aggregator-style)
> but the output for the 2.4 javadoc plugin is:
> [INFO]task-segment: [javadoc:javadoc]
> I am not sure if the above output is changed between versions or if the
> "aggregator-style" is not detectd in the 2.4 version and has an influence in
> this issue.
> I have attached the log file for running my project using javadoc plugin
> version 2.3 and 2.4. Version 2.3 works and version 2.4 does not include the
> additional source files in the aggregated javadoc.
--
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: (MECLIPSE-458) Maven webapp archetype does not create correct project
Maven webapp archetype does not create correct project -- Key: MECLIPSE-458 URL: http://jira.codehaus.org/browse/MECLIPSE-458 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Environment: Eclipse 3.3 (Europa), m2eclipse 0.9.4.200806 Reporter: Brennan Spies Attachments: m2_webapp_arch.zip Created a Maven project, selected the Maven webapp archetype. Zipped project created is attached. * Missing src/test/java, src/test/resources, and src/main/java source folders (config in Eclipse) * Actual folders are not created * No stack traces in workspace log file -- 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: (MCHECKSTYLE-97) Dependency Problem: commons-beanutils / antlr
Dependency Problem: commons-beanutils / antlr - Key: MCHECKSTYLE-97 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-97 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.2 Environment: W2K, Java 6u6, Maven 2.0.9 Reporter: André Fügenschuh Priority: Minor I guess this issue is a follow-up to *MCHECKSTYLE-90*. With version 2.2, I get the following errors running 'checkstyle:checkstyle': 1) commons-beanutils [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/commons/beanutils/Converter org.apache.commons.beanutils.Converter [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/commons/beanutils/Converter at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeCheckstyle(CheckstyleReport.java:839) at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:635) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:73) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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) Caused by: java.lang.ClassNotFoundException: org.apache.commons.beanutils.Converter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 22 more 2) antlr [INFO] [ERROR] FATAL ERROR [INFO] [INFO] antlr/CommonAST antlr.CommonAST [INFO] [INFO] Trace java.lang.NoClassDefFoundError: antlr/CommonAST at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(Real
[jira] Created: (NMAVEN-137) Reference listing in VS remains after removing a NMaven artifact
Reference listing in VS remains after removing a NMaven artifact Key: NMAVEN-137 URL: http://jira.codehaus.org/browse/NMAVEN-137 Project: NMaven Issue Type: Bug Reporter: Leopoldo Agdeppa III When selecting 'Remove NMaven Artifact from the solution explorer menu; the reference is removed from the pom, but the listing remains in the solution explorer reference list. Environment: Maestro 1.5.1 server, NMaven 0.14-maestro-1.6-M1 client -- 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: (NMAVEN-138) Code Signature not viewable from within Visual Studio
Code Signature not viewable from within Visual Studio - Key: NMAVEN-138 URL: http://jira.codehaus.org/browse/NMAVEN-138 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Reporter: Leopoldo Agdeppa III When signing the code using the procedures listed, these updates are not reflected in the IDE. Example, from solution explorer > Properties > Signing. The display for signature / keyfile is blank. Only the pom is updated in the signing by nmaven. It should also update the csproj / vbproj file such that it will reflect the changes in solution explorer > Properties > Signing -- 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: (NMAVEN-138) Code Signature not viewable from within Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leopoldo Agdeppa III updated NMAVEN-138: Attachment: screenshot-1.jpg screen shot > Code Signature not viewable from within Visual Studio > - > > Key: NMAVEN-138 > URL: http://jira.codehaus.org/browse/NMAVEN-138 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Attachments: screenshot-1.jpg > > > When signing the code using the procedures listed, these updates are not > reflected in the IDE. > Example, from solution explorer > Properties > Signing. The display for > signature / keyfile is blank. > Only the pom is updated in the signing by nmaven. It should also update the > csproj / vbproj file such that it will reflect the changes in solution > explorer > Properties > Signing -- 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: (NMAVEN-137) Reference listing in VS remains after removing a NMaven artifact
[ http://jira.codehaus.org/browse/NMAVEN-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-137: Description: When selecting 'Remove NMaven Artifact from the solution explorer menu; the reference is removed from the pom, but the listing remains in the solution explorer reference list. was: When selecting 'Remove NMaven Artifact from the solution explorer menu; the reference is removed from the pom, but the listing remains in the solution explorer reference list. Environment: Maestro 1.5.1 server, NMaven 0.14-maestro-1.6-M1 client Affects Version/s: 0.14 (Unreleased) > Reference listing in VS remains after removing a NMaven artifact > > > Key: NMAVEN-137 > URL: http://jira.codehaus.org/browse/NMAVEN-137 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Fix For: 0.14 (Unreleased) > > > When selecting 'Remove NMaven Artifact from the solution explorer menu; the > reference is removed from the pom, but the listing remains in the solution > explorer reference list. -- 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: (NMAVEN-133) VS Addin 'Configure Maven Repository' does not work if nmaven.id is not in the first profile
[ http://jira.codehaus.org/browse/NMAVEN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-133: Fix Version/s: 0.14 (Unreleased) > VS Addin 'Configure Maven Repository' does not work if nmaven.id is not in > the first profile > > > Key: NMAVEN-133 > URL: http://jira.codehaus.org/browse/NMAVEN-133 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > Depending on the contents of settings.xml, the VS Addin's "Configure Maven > Repository" can cause Visual Studio to become unresponsive. > If the first profile in settings.xml contains a repository with an id of > "nmaven.id", then things seem to be fine. That profile can even have other > repositories and/or pluginRepositories in it. > If you add a second profile to settings.xml *above* this one, selecting > "Configure Maven Repository" will immediately lock up Visual Studio. -- 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: (NMAVEN-134) VS Addin 'Configure Maven Repository' does not remember checkbox values
[ http://jira.codehaus.org/browse/NMAVEN-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-134: Fix Version/s: 0.14 (Unreleased) > VS Addin 'Configure Maven Repository' does not remember checkbox values > --- > > Key: NMAVEN-134 > URL: http://jira.codehaus.org/browse/NMAVEN-134 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > In the Visual Studio Addin, the "Configure Maven Repository" dialog box does > not remember the values of the 'Releases Enabled' and 'Snapshots Enabled' > checkboxes. > The checkboxes are always un-checked when you select "Configure Maven > Repository", even if the underlying settings.xml file says that one or both > is enabled. > (It does correctly update settings.xml based on what you select, it just > doesn't display it properly next time.) -- 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: (NMAVEN-11) Can't generate resources for an executable that contains an exe.config file
[ http://jira.codehaus.org/browse/NMAVEN-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-11: --- Fix Version/s: 0.14 (Unreleased) > Can't generate resources for an executable that contains an exe.config file > --- > > Key: NMAVEN-11 > URL: http://jira.codehaus.org/browse/NMAVEN-11 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: Windows, Microsoft Framework 2.0 >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 (Unreleased) > > > When a project that has both a src/main/resource/resgen folder and a config > file under src/main/config, the build fails with the following error: > [ERROR] NMAVEN-9000-002: Unable to generate resources: System.Exception: > NMAVEN-9000-003: Could not find exe.config file. -- 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: (NMAVEN-129) Deploy plugin documentation doesn't match behavior: -Dversion vs. -DartifactVersion
[ http://jira.codehaus.org/browse/NMAVEN-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-129: Fix Version/s: 0.14 (Unreleased) > Deploy plugin documentation doesn't match behavior: -Dversion vs. > -DartifactVersion > > > Key: NMAVEN-129 > URL: http://jira.codehaus.org/browse/NMAVEN-129 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: NMaven 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > The 'usage' page for the deploy plugin says to use -Dversion, but this > results in an error message. > http://incubator.apache.org/nmaven/0.14/plugins/maven-deploy-plugin/usage.html > C:\temp>mvn org.apache.maven.dotnet.plugins:maven-deploy-plugin:deploy-file > -Dfile=sample.dll -DgroupId=Examples -DartifactId=SampleProject -Dversion=1.0 > -Dpackaging=library -Durl=file:///tmp/repo > ... > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] One or more required plugin parameters are invalid/missing for > 'deploy:deploy-file' > [0] Inside the definition for plugin 'maven-deploy-plugin' specify the > following: > > ... > VALUE > > -OR- > on the command line, specify: '-DartifactVersion=VALUE' > Apparently it should be -DartifactVersion=1.0 > Is there some reason this needs to differ from the Java deploy plugin, which > uses -Dversion when deploying? -- 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: (NMAVEN-92) Repository plugin export-rdf should log more info
[ http://jira.codehaus.org/browse/NMAVEN-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-92: --- Fix Version/s: 0.14 (Unreleased) > Repository plugin export-rdf should log more info > - > > Key: NMAVEN-92 > URL: http://jira.codehaus.org/browse/NMAVEN-92 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) >Reporter: Wendy Smoak >Priority: Minor > Fix For: 0.14 (Unreleased) > > > The 'export-rdf' goal should print the location of the > rdf-repository-export.xml file. > For example, the output of 'mvn install' shows exactly where to find the > artifact that was created: > [INFO] Installing c:\temp\myproject\target\myproject-1.0-SNAPSHOT.jar to > C:\Documents and > Settings\wsmoak\.m2\repository\com\example\myproject\1.0-SNAPSHOT\myproject-1.0-SNAPSHOT.jar > When the "mvn > org.apache.maven.dotnet.plugins:maven-repository-plugin:export-rdf " command > completed successfully, I looked in the target directory for whatever it > might have created. > This page explains that the file lands in > ~/.m2/uac/rdfRepository/rdf-repository-export.xml > http://incubator.apache.org/nmaven/rdf-repository.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] Updated: (NMAVEN-106) NMaven Service Embedder vs Simple Call of mvn.bat using dotnet System.Diagnostics.Process
[ http://jira.codehaus.org/browse/NMAVEN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-106: Fix Version/s: 0.14 (Unreleased) > NMaven Service Embedder vs Simple Call of mvn.bat using dotnet > System.Diagnostics.Process > - > > Key: NMAVEN-106 > URL: http://jira.codehaus.org/browse/NMAVEN-106 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) > Environment: win32 >Reporter: Leopoldo Agdeppa III > Fix For: 0.14 (Unreleased) > > Attachments: vsaddin_fix.zip > > > the Current way of running nmaven in Visual Studio is through NMaven Service > Embedder running on Jetty > and commands are given through SOAP requests, then the service embedder > executes the maven command using > embedded maven > One problem on this approach is canceling an executed nmaven command in VS > I think using this approach is not too maintainable since you have to > maintain to components > One solution is to use System.Diagnostics.Process in VS for running maven > commands since mvn.bat is already adequate for running nmaven commands > in this way we only have to maintain the command executed in the process -- 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: (NMAVEN-127) Simple C# Archetype is missing a name
[ http://jira.codehaus.org/browse/NMAVEN-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-127: Fix Version/s: 0.14 (Unreleased) > Simple C# Archetype is missing a name > - > > Key: NMAVEN-127 > URL: http://jira.codehaus.org/browse/NMAVEN-127 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) > Environment: 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > Building a project created from the C# simple archetype results in: > C:\Temp\NMaven.Sample>mvn install > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - NMaven:NMaven.Sample:library:1.0-SNAPSHOT > [INFO]task-segment: [install] > [INFO] > > Adding a element will eliminate the "Building Unnamed..." message. > (Also check the other archetypes) -- 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: (NMAVEN-135) VS Addin 'Add Maven Artifact' does not respect mirrors in settings.xml
[ http://jira.codehaus.org/browse/NMAVEN-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-135: Fix Version/s: 0.14 (Unreleased) > VS Addin 'Add Maven Artifact' does not respect mirrors in settings.xml > -- > > Key: NMAVEN-135 > URL: http://jira.codehaus.org/browse/NMAVEN-135 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: NMaven 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > The VS Addin's 'Add Maven Artifact' feature does not respect mirrors in > settings.xml. > When you use 'Configure Maven Repository', it adds or updates a repository > with id=nmaven.id in settings.xml. > If there is a mirrof of nmaven.id defined in settings.xml, it is ignored. -- 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: (NMAVEN-88) ProjectFactory createArtifactFrom() method uses hard coded path ${user.home}/.m2/uac/gac_msil
[
http://jira.codehaus.org/browse/NMAVEN-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NMAVEN-88:
---
Fix Version/s: 0.14 (Unreleased)
> ProjectFactory createArtifactFrom() method uses hard coded path
> ${user.home}/.m2/uac/gac_msil
> -
>
> Key: NMAVEN-88
> URL: http://jira.codehaus.org/browse/NMAVEN-88
> Project: NMaven
> Issue Type: Bug
>Affects Versions: 0.14 (Unreleased)
> Environment: Windows XP, Vista
>Reporter: Dan Batten
> Fix For: 0.14 (Unreleased)
>
>
> Firstly let me say that I think this and NMAVEN-87 are somehow associated.
> Currently the createArtifactFrom() method of the class
> org.apache.maven.dotnet.dao.ProjectFactory is hard coded (maybe this is a
> bad use of the term) to use the following path -
> ${user.home}/.m2/uac/gac_msil. This causes a problem when the Maven
> repository is not located in ${user.home}, specifically when compiling
> projects with references as the reference path points to the wrong location.
> It would be nice if this path was somehow linked to the location of the Maven
> repository as it seems some components can handle the repository not existing
> in ${user.home}.
> My current work-around is simply to compile NMaven with the path to my
> repository, so it's not holding me up. I looked into supplying a patch but
> unfortunately I'm not intimate enough with the code (I'm working on changing
> 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] Updated: (NMAVEN-132) VS Addin 'Configure Maven Repository' breaks command line builds
[
http://jira.codehaus.org/browse/NMAVEN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NMAVEN-132:
Fix Version/s: 0.14 (Unreleased)
> VS Addin 'Configure Maven Repository' breaks command line builds
>
>
> Key: NMAVEN-132
> URL: http://jira.codehaus.org/browse/NMAVEN-132
> Project: NMaven
> Issue Type: Bug
>Affects Versions: 0.14 (Unreleased)
>Reporter: Allan G. Ramirez
> Fix For: 0.14 (Unreleased)
>
>
> The VS Addin's 'Configure Maven Repository' option adds a profile to
> settings.xml with the repository url you supply.
> This change breaks command-line builds:
> {code}
> C:\svn\examples\NMaven.Sample>mvn clean
> ...
> java.lang.ClassCastException: Settings.addActiveProfiles(string) parameter
> must be instanceof java.lang.String
> at
> org.apache.maven.settings.Settings.addActiveProfile(Settings.java:91)
> at
> org.apache.maven.settings.DefaultMavenSettingsBuilder.activateDefaultProfiles(DefaultMavenSettingsBuilder.java:197)
> at
> org.apache.maven.settings.DefaultMavenSettingsBuilder.buildSettings(DefaultMavenSettingsBuilder.java:177)
> at
> org.apache.maven.settings.DefaultMavenSettingsBuilder.buildSettings(DefaultMavenSettingsBuilder.java:153)
> at
> org.apache.maven.settings.DefaultMavenSettingsBuilder.buildSettings(DefaultMavenSettingsBuilder.java:141)
> at org.apache.maven.cli.MavenCli.buildSettings(MavenCli.java:315)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:176)
> 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)
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (NMAVEN-128) Document packaging and built-in lifecycle bindings
[ http://jira.codehaus.org/browse/NMAVEN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-128: Fix Version/s: 0.14 (Unreleased) > Document packaging and built-in lifecycle bindings > -- > > Key: NMAVEN-128 > URL: http://jira.codehaus.org/browse/NMAVEN-128 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > We should document the available packaging options and built-in lifecycle > bindings. > Similar to: > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_Bindings > Related thread: > http://www.nabble.com/NMaven-packaging-and-lifecycle-bindings-td17328669.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] Updated: (NMAVEN-85) Install plugin fails when parent project is not in parent directory
[ http://jira.codehaus.org/browse/NMAVEN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-85: --- Fix Version/s: 0.14 (Unreleased) > Install plugin fails when parent project is not in parent directory > > > Key: NMAVEN-85 > URL: http://jira.codehaus.org/browse/NMAVEN-85 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: NMaven head (revision 570776). > Maven 2.0.6 > Windows Vista. > Microsoft Visual Studio 2005 version 8.0.50727.867 >Reporter: Peter Nilsson > Fix For: 0.14 (Unreleased) > > > I have a fairly big project built with Maven and the parent of a Maven > project is not always located in the parent directory. However this seems to > cause problems when installing libraries with NMaven. > To try it out created two small projects, foo and bar, in sibling > directories. > The parent project is foo with the following pom: > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > nmaventest > foo > pom > 1.0.0.0 > > > > org.apache.maven.dotnet.plugins > maven-compile-plugin > true > > > > > I install it into local repo with "mvn install". > The child project, bar, has this pom: > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > > nmaventest > foo > 1.0.0.0 > > bar > library > 1.0.0.0 > > The bar project contains a single C# file in src/main/csharp. > Building project bar with "mvn package" works fine and creates bar.dll. > However, installing the dll with "mvn install" cause the following error: > [INFO] NMAVEN-1001-000: Failed to install artifacts > Embedded error: NMAVEN-001-014: Unable to store model: Message = > C:\temp\nmaventest\bar\..\pom.xml (The system cannot find the file specified) > It seems like the install plugin tries to install the parent pom as well > which of course fails as it is not always available (except in local repo). > The end of "mvn install -X": > [DEBUG] Configuring mojo > 'org.apache.maven.dotnet.plugins:maven-install-plugin:0.14-SNAPSHOT:install' > --> > [DEBUG] (f) isGacInstall = false > [DEBUG] (f) localRepository = C:\Users\peterni\.m2\repository > [DEBUG] (f) pomFile = C:\temp\nmaventest\bar\pom.xml > [DEBUG] (f) profile = GACUTIL > [DEBUG] (f) project = [EMAIL PROTECTED] > [DEBUG] -- end configuration -- > [INFO] [install:install] > 2007-aug-29 19:39:53 org.apache.maven.dotnet.registry.ConnectionsRepository > lazyLoad > INFO: NMAVEN-080-001: Adding data access object: Class Name = > org.apache.maven.dotnet.dao.impl.ProjectDaoImpl > 2007-aug-29 19:39:53 org.apache.maven.dotnet.registry.ConnectionsRepository > lazyLoad > INFO: NMAVEN-080-004: Connection Start Up: Time = 67 > [INFO] NMAVEN-001-007: Installing file into repository: File = > C:\temp\nmaventest\bar\target\bar.dll > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] NMAVEN-1001-000: Failed to install artifacts > Embedded error: NMAVEN-001-014: Unable to store model: Message = > C:\temp\nmaventest\bar\..\pom.xml (The system cannot find the file specified) > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: NMAVEN-1001-000: > Failed to install artifacts > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenC
[jira] Updated: (NMAVEN-136) References added using Visual Studio controls (Add Reference) do not update the pom
[ http://jira.codehaus.org/browse/NMAVEN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-136: Fix Version/s: 0.14 (Unreleased) > References added using Visual Studio controls (Add Reference) do not update > the pom > > > Key: NMAVEN-136 > URL: http://jira.codehaus.org/browse/NMAVEN-136 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: jan ancajas > Fix For: 0.14 (Unreleased) > > > adding of references from the GAC using Visual Studio controls (Add > Reference) should also reflect in the pom -- 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: (NMAVEN-130) NPE when deploying to remote repo
[ http://jira.codehaus.org/browse/NMAVEN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-130: Fix Version/s: 0.14 (Unreleased) > NPE when deploying to remote repo > - > > Key: NMAVEN-130 > URL: http://jira.codehaus.org/browse/NMAVEN-130 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: NMaven 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > Deploying to a remote repo results in a NullPointerException > C:\Temp>mvn org.apache.maven.dotnet.plugins:maven-deploy-plugin:deploy-file > -Dfile=sample.dll -DgroupId=Examples -DartifactId=SampleProject > -DartifactVersion=1.0 -Dpackaging=library -Durl=file:///temp/repo > ... > [INFO] [deploy:deploy-file] > Uploading: file:///temp/repo/Examples/SampleProject/1.0/SampleProject-1.0.dll > 3K uploaded > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:919) > at > org.apache.maven.project.artifact.ProjectArtifactMetadata.storeInLocalRepository(ProjectArtifactMetadata.java:86) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:437) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86) > at > org.apache.maven.dotnet.plugins.DeployFileMojo.execute(DeployFileMojo.java:150) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: 8 seconds > [INFO] Finished at: Tue May 27 16:05:57 MST 2008 > [INFO] Final Memory: 6M/14M > [INFO] > > The file is deployed, but without metadata: > C:\Temp>tree /F repo > Folder PATH listing > Volume serial number is BCCB-CB88 > C:\TEMP\REPO > └───Examples > └───SampleProject > └───1.0 > SampleProject-1.0.dll > SampleProject-1.0.dll.md5 > SampleProject-1.0.dll.sha1 -- 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: (NMAVEN-125) NUnit dependency should be in test scope
[
http://jira.codehaus.org/browse/NMAVEN-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NMAVEN-125:
Fix Version/s: 0.14 (Unreleased)
> NUnit dependency should be in test scope
>
>
> Key: NMAVEN-125
> URL: http://jira.codehaus.org/browse/NMAVEN-125
> Project: NMaven
> Issue Type: Bug
>Affects Versions: 0.14 (Unreleased)
> Environment: NNmaven 0.14 branch + patches
>Reporter: Wendy Smoak
>Priority: Minor
> Fix For: 0.14 (Unreleased)
>
>
> In a project created from maven-archetype-dotnet-simple, the NUnit dependency
> is not in test scope.
> It should be:
> {noformat}
>
> NUnit
> NUnit.Framework
> 2.2.8.0
> library
> test < add this line
>
> {noformat}
--
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: (NMAVEN-138) Code Signature not viewable from within Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-138: Fix Version/s: 0.14 (Unreleased) > Code Signature not viewable from within Visual Studio > - > > Key: NMAVEN-138 > URL: http://jira.codehaus.org/browse/NMAVEN-138 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Fix For: 0.14 (Unreleased) > > Attachments: screenshot-1.jpg > > > When signing the code using the procedures listed, these updates are not > reflected in the IDE. > Example, from solution explorer > Properties > Signing. The display for > signature / keyfile is blank. > Only the pom is updated in the signing by nmaven. It should also update the > csproj / vbproj file such that it will reflect the changes in solution > explorer > Properties > Signing -- 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: (NMAVEN-122) JavaBinding (solution generation) plugin needs a Clean goal
[ http://jira.codehaus.org/browse/NMAVEN-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-122: Fix Version/s: 0.14 (Unreleased) > JavaBinding (solution generation) plugin needs a Clean goal > --- > > Key: NMAVEN-122 > URL: http://jira.codehaus.org/browse/NMAVEN-122 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: Wendy Smoak >Priority: Minor > Fix For: 0.14 (Unreleased) > > > The JavaBinding plugin's Solution goal generates .sln and .csproj (or > .vbproj) files. It would be nice to have a companion Clean goal to delete > them. > (Similar to mvn idea:idea and mvn idea:clean) -- 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: (NMAVEN-115) Using the systemPath element in a dependecy doesn't work
[ http://jira.codehaus.org/browse/NMAVEN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-115: Fix Version/s: 0.14 (Unreleased) > Using the systemPath element in a dependecy doesn't work > > > Key: NMAVEN-115 > URL: http://jira.codehaus.org/browse/NMAVEN-115 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-115-vs-support.patch, NMAVEN-115.patch > > > Using a system scope w/ a systemPath element in a dependency won't work, > NMaven always points to local repo. -- 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: (NMAVEN-116) Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory
[ http://jira.codehaus.org/browse/NMAVEN-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-116: Fix Version/s: 0.14 (Unreleased) > Add feature for Solution.JavaBinding plugin to pickup resource file in the > source directory > --- > > Key: NMAVEN-116 > URL: http://jira.codehaus.org/browse/NMAVEN-116 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) > Environment: Windows XP SP2, VS2005, JDK 1.5, Maven 2.0.7 >Reporter: Napoleon Esmundo C. Ramirez > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-116.patch > > > If *.resx file is found in the source directory of nmaven project, > Solution.JavaBinding will generate the reference entry in *.csproj/.*vbproj > file. -- 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: (NMAVEN-126) Unable to retrieve and use timestamped snapshots of plugins
[ http://jira.codehaus.org/browse/NMAVEN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-126: Fix Version/s: 0.14 (Unreleased) > Unable to retrieve and use timestamped snapshots of plugins > --- > > Key: NMAVEN-126 > URL: http://jira.codehaus.org/browse/NMAVEN-126 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > Attempting to build the C# quickstart project against a remote repo > containing timestamped snapshots does not work. > >mvn archetype:create ... -DarchetypeArtifactId=maven-archetype-dotnet-simple > >... > ... > C:\Temp\NMaven.Sample>mvn install > [INFO] Scanning for projects... > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error building POM (may not be this project's POM). > Project ID: org.apache.maven.dotnet.plugins:maven-compile-plugin > Reason: Error getting POM for > 'org.apache.maven.dotnet.plugins:maven-compile-plugin' from the repository: > Failed to resolve artifact, possibly due to a repository list that is not > appropriately equipped for this artifact's metadata. > > org.apache.maven.dotnet.plugins:maven-compile-plugin:pom:0.14-20080521.120818-19 > from the specified remote repositories: > ... -- 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: (NMAVEN-137) Reference listing in VS remains after removing a NMaven artifact
[ http://jira.codehaus.org/browse/NMAVEN-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-137: Fix Version/s: 0.14 (Unreleased) > Reference listing in VS remains after removing a NMaven artifact > > > Key: NMAVEN-137 > URL: http://jira.codehaus.org/browse/NMAVEN-137 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Fix For: 0.14 (Unreleased) > > > When selecting 'Remove NMaven Artifact from the solution explorer menu; the > reference is removed from the pom, but the listing remains in the solution > explorer reference list. -- 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: (NMAVEN-89) Update documentation for Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-89: --- Fix Version/s: 0.14 (Unreleased) > Update documentation for Visual Studio > -- > > Key: NMAVEN-89 > URL: http://jira.codehaus.org/browse/NMAVEN-89 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) >Reporter: Wendy Smoak >Priority: Minor > Fix For: 0.14 (Unreleased) > > > Some changes need to be made on this page: > http://incubator.apache.org/nmaven/ide/visual-studio.html > The Sample Generated Addin file should be updated to show the new location of > the dll files in the 'gac' directory (they are no longer in the default Maven > local repository.) > Under 'Debugging' it should explain that the c:\tmp directory must exist > before using the suggested 'devenv...' command, or that you should use an > existing directory. I found that if the directory did not exist, no log file > would be created. -- 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: (NMAVEN-124) NMaven crashes when generating solution files
[ http://jira.codehaus.org/browse/NMAVEN-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-124: Fix Version/s: 0.14 (Unreleased) > NMaven crashes when generating solution files > -- > > Key: NMAVEN-124 > URL: http://jira.codehaus.org/browse/NMAVEN-124 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) > Environment: NMaven 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > Attachments: SampleWithAltStructure.zip > > > NMaven crashes when I attempt to generate solution files for the attached > sample project. > The sample project is based on the C# simple archetype, but with an alternate > source and test directory structure. There is code directly in the > sourceDirectory as well as one level below that. > To reproduce: > 1. unzip sample project > 2. mvn install > 3. mvn > NMaven.Plugins:NMaven.Plugin.Solution.JavaBinding:0.14-SNAPSHOT:Solution > Result: "NMaven.Plugin.Loader has encountered a problem and needs to close" > dialog box -- 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: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file
[ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-119: Fix Version/s: 0.14 (Unreleased) > Ability to generate pom.xml file from an existing Visual Studio solution file > - > > Key: NMAVEN-119 > URL: http://jira.codehaus.org/browse/NMAVEN-119 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: jan ancajas > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-assemblies-119-v2.patch, > NMaven-assemblies-119.patch > > > the pom generator utility will accept the parent solution file, parses its > corresponding csproj/vbproj files then generate the pom for every module of > the project -- 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: (NMAVEN-131) Deploy plugin should generate a minimal pom if one is not supplied
[ http://jira.codehaus.org/browse/NMAVEN-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-131: Fix Version/s: 0.14 (Unreleased) > Deploy plugin should generate a minimal pom if one is not supplied > -- > > Key: NMAVEN-131 > URL: http://jira.codehaus.org/browse/NMAVEN-131 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) > Environment: NMaven 0.14 branch + patches >Reporter: Wendy Smoak > Fix For: 0.14 (Unreleased) > > > When deploying libraries to a remote repo, the deploy plugin should generate > a pom by default. > (The Java version of this plugin has a 'generatePom' parameter that defaults > to true.) > Workaround: create a minimal pom and use -DpomFile=/path/to/pom.xml when > deploying libraries to a remote repo. -- 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: (NMAVEN-59) IDE Output Pane Only Displays the Maven Java Output
[ http://jira.codehaus.org/browse/NMAVEN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-59: --- Fix Version/s: 0.14 (Unreleased) > IDE Output Pane Only Displays the Maven Java Output > --- > > Key: NMAVEN-59 > URL: http://jira.codehaus.org/browse/NMAVEN-59 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 (Unreleased) > > > The maven embedder only writes Maven (Java) output to the IDE output pane.. > The .NET generated console output also needs to be written to the IDE. -- 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: (NMAVEN-87) ConnectionsRepository is hard coded to use ${user.home}/.m2/uac/rdfRepository
[
http://jira.codehaus.org/browse/NMAVEN-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NMAVEN-87:
---
Fix Version/s: 0.14 (Unreleased)
> ConnectionsRepository is hard coded to use ${user.home}/.m2/uac/rdfRepository
> -
>
> Key: NMAVEN-87
> URL: http://jira.codehaus.org/browse/NMAVEN-87
> Project: NMaven
> Issue Type: Bug
>Affects Versions: 0.14 (Unreleased)
> Environment: Windows XP, Vista
>Reporter: Dan Batten
> Fix For: 0.14 (Unreleased)
>
>
> Currently the lazyLoad() method of the class
> org.apache.maven.dotnet.registry.ConnectionsRepository is hard coded to use
> the following path - ${user.home}/.m2/uac/rdfRepository. This causes a
> problem when the Maven repository is not located in ${user.home}.
> It would be nice if this path was somehow linked to the location of the Maven
> repository as it seems some components can handle the repository not existing
> in ${user.home}.
--
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: (NMAVEN-113) Remove dependencies using VS NMaven Plugin
[ http://jira.codehaus.org/browse/NMAVEN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-113: Affects Version/s: 0.14 (Unreleased) Fix Version/s: 0.14 (Unreleased) > Remove dependencies using VS NMaven Plugin > -- > > Key: NMAVEN-113 > URL: http://jira.codehaus.org/browse/NMAVEN-113 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: John Michael Luy > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-113.patch > > > Provide functionality to remove dependencies using VS NMaven 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] Updated: (NMAVEN-111) the visual studio installer plugin doesn't work on an empty local repository
[ http://jira.codehaus.org/browse/NMAVEN-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-111: Affects Version/s: 0.14 (Unreleased) Fix Version/s: 0.14 (Unreleased) > the visual studio installer plugin doesn't work on an empty local repository > > > Key: NMAVEN-111 > URL: http://jira.codehaus.org/browse/NMAVEN-111 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Maria Catherine Tan > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-111.patch > > > This applies for > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ > You currently have to run both "mvn install" on an NMaven project and to > generate the solution file to get the following artifacts in your local > repository for the vsinstaller plugin to succeed: > * NMaven.Plugins:NMaven.Plugin.Settings.JavaBinding > * NMaven.Plugins:NMaven.Plugin.Solution > In addition, you have to manually install the dotnet-embedder WAR file using > the following: > mvn install:install-file -DgroupId=org.apache.maven.dotnet > -DartifactId=dotnet-service-embedder -Dversion=0.14-maestro-1.5-M3 > -Dpackaging=war > -Dfile=%REPOSITORY%\org\apache\maven\dotnet\dotnet-service-embedder\0.14-maestro-1.5-M3\dotnet-service-embedder-0.14-maestro-1.5-M3.war > > -DpomFile=%REPOSITORY%\org\apache\maven\dotnet\dotnet-service-embedder\0.14-maestro-1.5-M3\dotnet-service-embedder-0.14-maestro-1.5-M3.pom > (Assumes %REPOSITORY% is the location of the MPS releases repository - > obviously not always available on the client... so maybe a POM is better). -- 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: (NMAVEN-110) Ability to generate .vbproj files
[ http://jira.codehaus.org/browse/NMAVEN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-110: Affects Version/s: 0.14 (Unreleased) Fix Version/s: 0.14 (Unreleased) > Ability to generate .vbproj files > - > > Key: NMAVEN-110 > URL: http://jira.codehaus.org/browse/NMAVEN-110 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: Maria Catherine Tan > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-110-COMPLETE.patch, NMAVEN-110.patch > > > this applies to > https://svn.apache.org/repos/asf/incubator/nmaven/tags/STABLE-2007-12-16/ -- 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: (NMAVEN-38) "NUnit" group ID hardwired into TesterMojo.java(142) - doesn't match site documentation.
[ http://jira.codehaus.org/browse/NMAVEN-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed NMAVEN-38. -- Assignee: Shane Isbell Resolution: Fixed Fix Version/s: 0.14 (Unreleased) AIUI this was fixed > "NUnit" group ID hardwired into TesterMojo.java(142) - doesn't match site > documentation. > > > Key: NMAVEN-38 > URL: http://jira.codehaus.org/browse/NMAVEN-38 > Project: NMaven > Issue Type: Bug > Environment: rev 521824 from trunk >Reporter: Van Curtis >Assignee: Shane Isbell >Priority: Minor > Fix For: 0.14 (Unreleased) > > > http://incubator.apache.org/nmaven/getting-started.html gives examples of > using NUnit and installing existing assemblies into the maven repository > using a groupId of "org.nunit". Trying to use this in a POM results in > "NMAVEN-1100-003: Could not find any nunit libraries." > Looking at line 142 of TesterMojo.java, it tests against "NUnit". Using the > following line to install... > mvn org.apache.maven.plugins:maven-install-plugin:install-file > -DgroupId=NUnit -DartifactId=Nunit.Framework -Dversion=2.2.9.0 > -Dpackaging=dll -Dfile="C:\\Program Files\\NUnit-Net-2.0 > 2.2.9\\bin\\nunit.framework.dll" -DgeneratePom=true > And setting the POM dependency as > > NUnit > Nunit.Framework > 2.2.9.0 > library > cleared it up. Don't know which way *should* be the right way, but it would > be nice if the docs and code match. > thanks, > van. -- 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: (NMAVEN-72) Investigate whether MS-CL is compatible with AL 2.0
[ http://jira.codehaus.org/browse/NMAVEN-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed NMAVEN-72. -- Resolution: Not A Bug AIUI, no intention to use anything licensed under this just yet - cross that bridge at the time > Investigate whether MS-CL is compatible with AL 2.0 > --- > > Key: NMAVEN-72 > URL: http://jira.codehaus.org/browse/NMAVEN-72 > Project: NMaven > Issue Type: Task >Reporter: Shane Isbell >Priority: Minor > > Investigate whether MS-CL is compatible with AL 2.0: > http://www.microsoft.com/resources/sharedsource/licensingbasics/communitylicense.mspx -- 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: (NMAVEN-63) Signing of assemblies not supported for VB and Java on Framework Version 1.1
[ http://jira.codehaus.org/browse/NMAVEN-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-63: --- Affects Version/s: 0.14 (Unreleased) Fix Version/s: 0.14 (Unreleased) > Signing of assemblies not supported for VB and Java on Framework Version 1.1 > > > Key: NMAVEN-63 > URL: http://jira.codehaus.org/browse/NMAVEN-63 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 (Unreleased) > > > Signing of assemblies not supported for VB and Java on framework version 1.1. > Need to add in the keyfile and keyname attributes. -- 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: (NMAVEN-50) Verify Assembly's Public Key Token Before Installing into GAC
[ http://jira.codehaus.org/browse/NMAVEN-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-50: --- Affects Version/s: 0.14 (Unreleased) Fix Version/s: 0.14 (Unreleased) > Verify Assembly's Public Key Token Before Installing into GAC > - > > Key: NMAVEN-50 > URL: http://jira.codehaus.org/browse/NMAVEN-50 > Project: NMaven > Issue Type: Improvement >Affects Versions: 0.14 (Unreleased) >Reporter: Shane Isbell >Priority: Minor > Fix For: 0.14 (Unreleased) > > > Verify assembly's public key token matches PublicKeyToken entry in > net-executables.xml file, prior to installing assembly into the GAC. -- 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: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file
[ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137451#action_137451 ] Brett Porter commented on NMAVEN-119: - does this module work with trunk as well? > Ability to generate pom.xml file from an existing Visual Studio solution file > - > > Key: NMAVEN-119 > URL: http://jira.codehaus.org/browse/NMAVEN-119 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: jan ancajas > Fix For: 0.14 (Unreleased), 0.16 > > Attachments: NMAVEN-assemblies-119-v2.patch, > NMaven-assemblies-119.patch > > > the pom generator utility will accept the parent solution file, parses its > corresponding csproj/vbproj files then generate the pom for every module of > the project -- 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: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file
[ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-119: Fix Version/s: 0.14 (Unreleased) > Ability to generate pom.xml file from an existing Visual Studio solution file > - > > Key: NMAVEN-119 > URL: http://jira.codehaus.org/browse/NMAVEN-119 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: jan ancajas > Fix For: 0.14 (Unreleased), 0.16 > > Attachments: NMAVEN-assemblies-119-v2.patch, > NMaven-assemblies-119.patch > > > the pom generator utility will accept the parent solution file, parses its > corresponding csproj/vbproj files then generate the pom for every module of > the project -- 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: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file
[ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NMAVEN-119: Fix Version/s: (was: 0.14 (Unreleased)) 0.16 > Ability to generate pom.xml file from an existing Visual Studio solution file > - > > Key: NMAVEN-119 > URL: http://jira.codehaus.org/browse/NMAVEN-119 > Project: NMaven > Issue Type: New Feature >Affects Versions: 0.14 (Unreleased) >Reporter: jan ancajas > Fix For: 0.14 (Unreleased), 0.16 > > Attachments: NMAVEN-assemblies-119-v2.patch, > NMaven-assemblies-119.patch > > > the pom generator utility will accept the parent solution file, parses its > corresponding csproj/vbproj files then generate the pom for every module of > the project -- 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] Reopened: (NMAVEN-68) Sandcastle Maven Plugin
[ http://jira.codehaus.org/browse/NMAVEN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak reopened NMAVEN-68: --- Reopening to consider using Sandcastle Help File Builder > Sandcastle Maven Plugin > --- > > Key: NMAVEN-68 > URL: http://jira.codehaus.org/browse/NMAVEN-68 > Project: NMaven > Issue Type: New Feature > Environment: Microsoft, Windows >Reporter: Shane Isbell >Priority: Minor > > A Maven plugin for sandcastle, which is Microsoft's API document generator. -- 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: (NMAVEN-84) Reseach feasability of SHFB plugin
[ http://jira.codehaus.org/browse/NMAVEN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137453#action_137453 ] Wendy Smoak commented on NMAVEN-84: --- I reopened the parent issue. Campbell, are you still interested in working on it? > Reseach feasability of SHFB plugin > -- > > Key: NMAVEN-84 > URL: http://jira.codehaus.org/browse/NMAVEN-84 > Project: NMaven > Issue Type: Sub-task >Reporter: Campbell Boucher-Burnet >Priority: Minor > -- 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-2446) parent Pom properties not resolved for module dependencies
[
http://jira.codehaus.org/browse/MNG-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137460#action_137460
]
Paul Bakker commented on MNG-2446:
--
I agree this is a major issue. We use the exact same mechanism as described by
Hans, and run into the same problem.
> parent Pom properties not resolved for module dependencies
> ---
>
> Key: MNG-2446
> URL: http://jira.codehaus.org/browse/MNG-2446
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.4
> Environment: WindowsXP/Linux - JDK 1.4 last version
>Reporter: Jeremie Poutrin
>Priority: Minor
> Fix For: Reviewed Pending Version Assignment
>
>
> root-project --> root-pom.xml with ${my.version}
> |--->proj1 ${my.version}
> |--->proj2 ${my.version}
> | |
> | |->proj1 dependency
> |--->proj3 ${my.version}
> if I compile from the root-project directory, all compile fine.
> if I compile from the proj2 directory, maven2 resolve proj2-${my.version}
> resolve proj1-${my.version}
> but tries to resolve the parent version root-project-${my.version} but this
> is not resolved.
--
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
