Re: deploy surefire snapshot
Thanx Kenney. Problem solved. Cheers Prasad On 1/10/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote: Prasad Kashyap wrote: > I suspect this to be the cause of my woes :-) > > [INFO] [INFO] Surefire report directory: > C:\Apache\geronimo\trunk\testsuite\deployment-testsuite\deployment-tests\target\surefire-reports > > [INFO] java.lang.NoClassDefFoundError: > org/apache/maven/surefire/booter/SurefireBooter > [INFO] Exception in thread "main" > [INFO] [ERROR] There are test failures. Hi, I just solved this by deploying the surefire plugin itself. The version should be *-9.jar now. -- kenney > > My tests used to work fine just until recently. > > I use the 2.3-SNAPSHOT of maven-surefire-plugin. The latest jar in the > repo is > maven-surefire-plugin-2.3-20070110.125545-8.jar > > The surefire-booter that it depends on is a 2.1-SNAPSHOT and the > latest timestamped jar in the repo is > surefire-booter-2.1-20070108.094711-10.jar > > Cheers > Prasad > > > > On 1/8/07, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: >> done >> >> On 1/8/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote: >> > Hi, >> > >> > Could somebody deploy a surefire snapshot (including the >> > surefire-junit4 provider) ? >> > >> > thanks, >> > >> > Tom >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploy surefire snapshot
I suspect this to be the cause of my woes :-) [INFO] [INFO] Surefire report directory: C:\Apache\geronimo\trunk\testsuite\deployment-testsuite\deployment-tests\target\surefire-reports [INFO] java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/SurefireBooter [INFO] Exception in thread "main" [INFO] [ERROR] There are test failures. My tests used to work fine just until recently. I use the 2.3-SNAPSHOT of maven-surefire-plugin. The latest jar in the repo is maven-surefire-plugin-2.3-20070110.125545-8.jar The surefire-booter that it depends on is a 2.1-SNAPSHOT and the latest timestamped jar in the repo is surefire-booter-2.1-20070108.094711-10.jar Cheers Prasad On 1/8/07, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: done On 1/8/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote: > Hi, > > Could somebody deploy a surefire snapshot (including the > surefire-junit4 provider) ? > > thanks, > > Tom > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
archetype:create strips out comments
I am creating an archetype plugin. The template pom.xml has license headers and other comments. But after the archetype:create is executed, all the comments are stripped out in the newly generated pom.xml. Is there a config option or a workaround to this ? Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to include custom reports from "pom" packaging
I have a custom reporting plugin. It generates a surefire-report for projects whose packaging is set to "pom". (sort of a custom aggregator). I want it's reports to be generated and included along with the other "Project Reports" when I run 'mvn site'. I tried putting the plugin in section but in vain. I used the @execute phase="site" in the Mojo that extends AbstractMavenReport. It goes into a endless loop [INFO] Preparing geronimo:generate-surefire-report [INFO] Preparing geronimo:generate-surefire-report ... Can someone please advise me as to how I can achieve this ? Thanx Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HELP: Running site goal on a cutom packaging
I need some help with running the site goal on a custom packaging. This is how the packaging is defined.. http://rifers.org/paste/show/2093 On running 'mvn site' on a pom with this packaging, I get [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: site. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingintegration-test. org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingintegration-test. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) In the above components.xml, I tried merging both the elements under the same for the same . The default execution of the pom failed. I had to separate the into separate elements. Can someone please guide me into the correct path here ? Thanx Prasad. org.apache.maven.lifecycle.mapping.LifecycleMapping integration-test org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping default org.apache.maven.plugins:maven-resources-plugin:testResources org.apache.maven.plugins:maven-compiler-plugin:testCompile org.apache.maven.plugins:maven-jar-plugin:jar org.apache.maven.plugins:maven-surefire-plugin:test org.apache.maven.plugins:maven-install-plugin:install org.apache.maven.plugins:maven-deploy-plugin:deploy org.apache.maven.lifecycle.mapping.LifecycleMapping integration-test org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping site pre-site site post-site site-deploy org.apache.maven.plugins:maven-site-plugin:site org.apache.maven.plugins:maven-site-plugin:deploy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Lineendings in assembly plugin
While assembling the Geronimo project with the assembly plugin, we have to set different line endings for different formats that we assembly. For the zip format, we'd like the to be CRLF while for the tar.* formats we'd like it to be LF. Does anybody have ideas on how we can achieve this easily without duplicating the descriptor ? Thanx in advance Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple executions of the assembly plugin
I tied the assembly goal to a phase. Problem resolved. Thanx for looking.
Cheers
Prasad
On 6/26/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Dan,
I cannot use the dependency-plugin because with it I cannot duplicate
the maven local repo structure in my assembly. The
element of the assembly's descriptor allows me to do that. However,
only the maven metadata info under META-INF/maven/* in the repo is
extraneous to me.
Cheers
Prasad
On 6/26/06, dan tran <[EMAIL PROTECTED]> wrote:
> maven-dependency-plugin can prepare the "staging area" for you.
>
>
>
> -D
>
>
> On 6/26/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> >
> > I have to use the element in the maven-assembly-plugin's
> > assembly descriptor. Using this makes the assembly contains maven
> > metadata files under META-INF. (maven/.../*.pom and pom.propperties).
> >
> > One solution Jesse and I talked about was to execute the assembly
> > plugin twice. The first execution would copy the repository to the
> > ${tempRoot}. The second execution would use to copy
> > the dirs over but exclude META-INF/maven.
> >
> > Here are the problems with this approach.
> >
> > 1) If I use assembly plugin in a execution, I get a "descriptor not
> > found error". How can the assembly plugin be used in multiple
> > executions ?
> >
> > 2) The first execution of the assembly copies the repo into
> > ${tempRoot}. But the next execution of the assembly cleans this dir
> > before starting. So the repo dirs are lost. Any ideas on how to get
> > around this ?
> >
> > Thanx in advance
> > Prasad
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple executions of the assembly plugin
Dan,
I cannot use the dependency-plugin because with it I cannot duplicate
the maven local repo structure in my assembly. The
element of the assembly's descriptor allows me to do that. However,
only the maven metadata info under META-INF/maven/* in the repo is
extraneous to me.
Cheers
Prasad
On 6/26/06, dan tran <[EMAIL PROTECTED]> wrote:
maven-dependency-plugin can prepare the "staging area" for you.
-D
On 6/26/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
>
> I have to use the element in the maven-assembly-plugin's
> assembly descriptor. Using this makes the assembly contains maven
> metadata files under META-INF. (maven/.../*.pom and pom.propperties).
>
> One solution Jesse and I talked about was to execute the assembly
> plugin twice. The first execution would copy the repository to the
> ${tempRoot}. The second execution would use to copy
> the dirs over but exclude META-INF/maven.
>
> Here are the problems with this approach.
>
> 1) If I use assembly plugin in a execution, I get a "descriptor not
> found error". How can the assembly plugin be used in multiple
> executions ?
>
> 2) The first execution of the assembly copies the repo into
> ${tempRoot}. But the next execution of the assembly cleans this dir
> before starting. So the repo dirs are lost. Any ideas on how to get
> around this ?
>
> Thanx in advance
> Prasad
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Multiple executions of the assembly plugin
I have to use the element in the maven-assembly-plugin's
assembly descriptor. Using this makes the assembly contains maven
metadata files under META-INF. (maven/.../*.pom and pom.propperties).
One solution Jesse and I talked about was to execute the assembly
plugin twice. The first execution would copy the repository to the
${tempRoot}. The second execution would use to copy
the dirs over but exclude META-INF/maven.
Here are the problems with this approach.
1) If I use assembly plugin in a execution, I get a "descriptor not
found error". How can the assembly plugin be used in multiple
executions ?
2) The first execution of the assembly copies the repo into
${tempRoot}. But the next execution of the assembly cleans this dir
before starting. So the repo dirs are lost. Any ideas on how to get
around this ?
Thanx in advance
Prasad
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Instantiating a class in a modello DataModel
Hi, How I can instantiate a class while declaring it as a field member in a modello DataModel ? field/association/type is another class that needs to be instantiated.. myObj 1.0.0 MyClass MyClass myObj = new MyClass(); <<<-- is what I need MyClass myObj; (= null)<<< is what happens now. Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Top level execution of jspc plugin.
I have a samples gallery with numerous applications under it already and more in the pipeline. There are all sorts of apps including webapps, ejbs, clients etc. I would like to use the jspc plugin on all war modules. The current usage of the plugin requires the configuration of the plugin in the parent and execution in every single individual war module's pom. For such large scale use in a diverse environment, it would be nice to specify the plugin execution just at the parent level. The plugin should simply skip those poms to which it is irrelevant. I have attached a patch to the following JIRA. http://jira.codehaus.org/browse/MJSPC-3 I'd sincerely appreciate your feedback. Thanx Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using jspc-maven-plugin
Can someone please help me trying to figure out the following error message while using the jspc-maven-plugin. Caused by: org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:114) at org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316) at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:423) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1552) at org.apache.jasper.compiler.Parser.parse(Parser.java:126) at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:100) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:155) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:295) at org.apache.jasper.JspC.processFile(JspC.java:986) at org.apache.jasper.JspC.execute(JspC.java:1135) at org.codehaus.mojo.jspc.AbstractJspcMojo.execute(AbstractJspcMojo.java:180) ... 18 more Thanx in advance Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Jesse McConnell as a Maven Plugins committer
For what its worth, I'd like to vote a +1 for this proposal. To add to the list of things that Brett mentioned, Jesse also helps out people on the #maven channel. He not only answers questions but creates patches for test/debug purposes when things don't work like they should. [ X ] +1 Cheers Prasad. On 3/27/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > I think we all agree we need more keen people helping out with plugins! > > Jesse has been contributing on the users list and mojo project for some > time, and has recently contributed several patches to the Apache Maven > plugins, tests for the clean, compiler and jar plugins, and contributed > a plugin testing harness. > > I'd like to propose we give him commit access. > > [ ] +1 > [ ] +0 > [ ] -1 > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help using assembly-plugin
I am evaluating the usage the maven-assembly-plugin for building
Geronimo's distribution jars and have some questions regarding it's
usage. I'd appreciate help from maven developers and users familiar
with this plugin.
assembly:assembly goal
1) Can I use variables like ${project.build.directory} in the descriptor xml ?
2) When copying files in a is it possible to copy them
flattened ? Into one single directory without the path ? This would be
really useful.
3) When I unpack jars using is it possible to exclude
certain files or extract only certain files (like the patternset in
ant) ? The current workaround is to unpack them in a temp junk
directory and then use to selectively include/exclude files
to the correct dir. This kinda works but it also zips up the temp junk
dir too. It would be nice if the had a flag.
Setting this boolean would copy/unpack the jars to some temp dir of
the plugin's choosing. The plugin would never include this temp dir
into the final zip.
It would also be nice if the also supported the feature.
Thanx in advance
Prasad
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2133) plugin goal skipped if not bound to any phase and no default phase exists in the mojo.
plugin goal skipped if not bound to any phase and no default phase exists in the mojo. -- Key: MNG-2133 URL: http://jira.codehaus.org/browse/MNG-2133 Project: Maven 2 Type: Bug Components: Plugins and Lifecycle Reporter: Prasad Kashyap In a pom, if no phase is specified for a plugin, then it is bound to the default phase defined by the mojo. However, if the mojo doesn't have a default phase, then it currently seems to be skipped, which is a probably incorrect. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Timestamp plugin
This seems like a very useful plugin to have. I think we should have one.
Cheers
Prasad
On 2/28/06, Anders Hessellund Jensen <[EMAIL PROTECTED]> wrote:
> I would like to be able to substitute timestamps with the build time
> into a resource file. As I understand it, there is currently no plugin
> to to this, so I consider writing one.
>
> The plugin should leverage the existing resource filtering mechanism of
> M2. The plugin would take a configuration like this:
>
>
>
>
> build.date
> .MM.dd
>
>
>
>
> Running the plugin with this configuration would define the M2 property
> build.date, and any filtered resource file would get ${build.date}
> substituted with 2006.02.28 or whatever the date at build time is.
>
> WDYT?
>
> Best regards,
> Anders
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSITE-95) Lack of leading / in the value strips off the first char in the submodules' name after being staged.
Lack of leading / in the value strips off the first char in the submodules' name after being staged. Key: MSITE-95 URL: http://jira.codehaus.org/browse/MSITE-95 Project: Maven 2.x Site Plugin Type: Bug Reporter: Prasad Kashyap Priority: Critical Attachments: test-parent.zip site:stage goal. Multi-module project. When the element is used, if the value does not have a leading slash, then the first char of every submodule under the final staging dir is stripped off. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPIR-32) in doesn't work.
[ http://jira.codehaus.org/browse/MPIR-32?page=all ] Prasad Kashyap updated MPIR-32: --- Attachment: test-parent.zip > in doesn't work. > --- > > Key: MPIR-32 > URL: http://jira.codehaus.org/browse/MPIR-32 > Project: Maven 2.x Project Info Reports Plugin > Type: Bug > Reporter: Prasad Kashyap > Attachments: test-parent.zip > > > The true does not work. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPIR-32) in doesn't work.
in doesn't work. --- Key: MPIR-32 URL: http://jira.codehaus.org/browse/MPIR-32 Project: Maven 2.x Project Info Reports Plugin Type: Bug Reporter: Prasad Kashyap The true does not work. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What are the defaults in report generation ?
has a element under it. What exactly are the defaults ? I thought they are the issue-tracking, license, team etc that's generated by default. I don't want my submodules in a multi-project build to generate this set of html files over and over again. How can I prevent them from doing so ? I have the following section in every one of my submodule. true But it doesn't seem to make a difference. In fact, having this in the top level pom also doesn't seem to make a difference. Those htmls are always created. So either my understanding of defaults is wrong or this doesn't work. If these are indeed the default reports, then it would also be nice if the elemnt had a under it. Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MASSEMBLY-69) "dependencies" configuration element in assembly:unpack plugin read-only
[ http://jira.codehaus.org/browse/MASSEMBLY-69?page=all ] Prasad Kashyap closed MASSEMBLY-69: --- Resolution: Duplicate The functionality is available in dependency-maven-plugin. This issue may be closed. > "dependencies" configuration element in assembly:unpack plugin read-only > - > > Key: MASSEMBLY-69 > URL: http://jira.codehaus.org/browse/MASSEMBLY-69 > Project: Maven 2.x Assembly Plugin > Type: Bug > Reporter: Prasad Kashyap > Attachments: MASSEMBLY-69.patch > > > The "dependencies" configuration element in the maven-assembly-plugin is set > to read-only but the documentation on it say it's optional. > The assembly:unpack goal currently unpacks all dependencies specified in the > project. If this optional element was not read-only, it would be useful to > specify just those dependencies that needed to be unpacked. > http://maven.apache.org/plugins/maven-assembly-plugin/unpack-mojo.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1958) we need a var that always points to the root direcotry in multi module builds
[ http://jira.codehaus.org/browse/MNG-1958?page=comments#action_59330 ]
Prasad Kashyap commented on MNG-1958:
-
Oh, I'm waiting for something like this too. This seems like an absolute
necessity.
> we need a var that always points to the root direcotry in multi module builds
> -
>
> Key: MNG-1958
> URL: http://jira.codehaus.org/browse/MNG-1958
> Project: Maven 2
> Type: Improvement
> Reporter: Mark Proctor
> Fix For: 2.1
>
>
> ${basedir} always points to the local module. There are cases, when having a
> local relative repository, when it would be usefull to have a var that always
> pointed to the root project, ${rootdir}.
> In such a case you may want to think of having the names ${rootdir}
> ${moduledir}
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error generating site for plugin
I had tried that. It throws a NPE. [INFO] Generate "Plugin documentation" report. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.tools.plugin.generator.PluginXdocGenerator.writeGoalParameterTable(PluginXdocGenerator.java:326) at org.apache.maven.tools.plugin.generator.PluginXdocGenerator.writeBody(PluginXdocGenerator.java:277) at org.apache.maven.tools.plugin.generator.PluginXdocGenerator.processMojoDescriptor(PluginXdocGenerator.java:59) at org.apache.maven.tools.plugin.generator.PluginXdocGenerator.execute(PluginXdocGenerator.java:47) Cheers Prasad On 2/22/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Remove one of these txo index file > > Emmanuel > > Prasad Kashyap a écrit : > > I have a very simple pom with the reporting section set to > > > > > > > > > > org.apache.maven.plugins > > maven-project-info-reports-plugin > > > > > > org.apache.maven.plugins > > maven-plugin-plugin > > > > > > > > > > I also generated the site using the site-archetype. > > > > mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app > > -DarchetypeGroupId=org.apache.maven.archetypes > > -DarchetypeArtifactId=maven-archetype-site > > > > Now when I run the mvn site goal, I get this error > > > > [INFO] - > > [INFO] Some files are duplicates in the site directory or in the > > generated-site directory. > > Review the following files for the "English" version: > > index > > apt\index.apt > > xdoc\index.xml > > [INFO] > > - > > > > > > Can some please tell me how this should be fixed ? > > > > Cheers > > Prasad > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error generating site for plugin
I have a very simple pom with the reporting section set to org.apache.maven.plugins maven-project-info-reports-plugin org.apache.maven.plugins maven-plugin-plugin I also generated the site using the site-archetype. mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-site Now when I run the mvn site goal, I get this error [INFO] - [INFO] Some files are duplicates in the site directory or in the generated-site directory. Review the following files for the "English" version: index apt\index.apt xdoc\index.xml [INFO] - Can some please tell me how this should be fixed ? Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-2103) Inheritance of overrides that of
[ http://jira.codehaus.org/browse/MNG-2103?page=comments#action_59250 ] Prasad Kashyap commented on MNG-2103: - I see what you mean. That makes sense only if the is set to false. Now flip the inheritance boolean at the level to true. Going by the same logic, all executions now would be inherited even if they were individually set to false. Now since the value of is true by default, all executions are always inherited and there's no way of overriding them. I think this is what we should do. set to true by default. overrides plugin's setting. if changed to false, all executions inside it are also not inherited, no matter what their individual settings are. > Inheritance of overrides that of > - > > Key: MNG-2103 > URL: http://jira.codehaus.org/browse/MNG-2103 > Project: Maven 2 > Type: Bug > Reporter: Prasad Kashyap > Attachments: test-inheritance.zip > > > The settings of overrides that of it's > By convention, all top level configuration settings are usually overridden by > the settings in the lower levels. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2103) Inheritance of overrides that of
Inheritance of overrides that of - Key: MNG-2103 URL: http://jira.codehaus.org/browse/MNG-2103 Project: Maven 2 Type: Bug Reporter: Prasad Kashyap Attachments: test-inheritance.zip The settings of overrides that of it's By convention, all top level configuration settings are usually overridden by the settings in the lower levels. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with the site plugin
For now how do I specify in my pom to pick up the 2.0-SNAPSHOT ? I have explicitly specified the 2.0-SNAPSHOT as the version in the and in maven-site-plugin 2.0-SNAPSHOT .. ... org.apache.maven.plugins maven-site-plugin 2.0-SNAPSHOT I also used mvn -npr and -npu options on the command line. It still downloads the 2.0-beta-4 version. What else am I missing ? Thanx in advance Prasad On 2/22/06, Vincent Siveton <[EMAIL PROTECTED]> wrote: > I think that the next release should be in March (according plugin statuses). > > Cheers, > > Vincent > > 2006/2/21, Prasad Kashyap <[EMAIL PROTECTED]>: > > Sorry Brett. Will keep that in mind in the future. > > > > Issue 2 is not actually a issue. It was a user-error. > > > > Vincent, as for the site:stage goal, do you know approx when it may > > be available in a release ? > > > > Cheers > > Prasad > > > > On 2/21/06, Vincent Siveton <[EMAIL PROTECTED]> wrote: > > > The site:stage goal only exists in the trunk > > > http://jira.codehaus.org/browse/MSITE-92 > > > > > > Cheers > > > > > > Vincent > > > > > > 2006/2/21, Prasad Kashyap <[EMAIL PROTECTED]>: > > > > Can someone please let me know if the following issues are as designed > > > > or bugs that need a JIRA ? > > > > > > > > 1. The site:stage goal of the maven-site-plugin has disappeared in the > > > > 2.0-beta-4 version. > > > > > > > > 2. The post-site phase doesn't work. I have a simple antrun that > > > > echoes a msg.. It executes in the site phase but doesn't in the > > > > post-site phase. > > > > http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#site > > > > > > > > Cheers > > > > Prasad > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with the site plugin
Sorry Brett. Will keep that in mind in the future. Issue 2 is not actually a issue. It was a user-error. Vincent, as for the site:stage goal, do you know approx when it may be available in a release ? Cheers Prasad On 2/21/06, Vincent Siveton <[EMAIL PROTECTED]> wrote: > The site:stage goal only exists in the trunk > http://jira.codehaus.org/browse/MSITE-92 > > Cheers > > Vincent > > 2006/2/21, Prasad Kashyap <[EMAIL PROTECTED]>: > > Can someone please let me know if the following issues are as designed > > or bugs that need a JIRA ? > > > > 1. The site:stage goal of the maven-site-plugin has disappeared in the > > 2.0-beta-4 version. > > > > 2. The post-site phase doesn't work. I have a simple antrun that > > echoes a msg.. It executes in the site phase but doesn't in the > > post-site phase. > > http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#site > > > > Cheers > > Prasad > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MSITE-93) post-site phase doesn't seem to work
[ http://jira.codehaus.org/browse/MSITE-93?page=all ] Prasad Kashyap closed MSITE-93: --- Resolution: Fixed user-error ! > post-site phase doesn't seem to work > > > Key: MSITE-93 > URL: http://jira.codehaus.org/browse/MSITE-93 > Project: Maven 2.x Site Plugin > Type: Bug > Reporter: Prasad Kashyap > > > The post-site phase doesn't work. I have a simple antrun that echoes a msg.. > It executes in the site phase but doesn't do anything in the post-site phase. > http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#site -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSITE-93) post-site phase doesn't seem to work
post-site phase doesn't seem to work Key: MSITE-93 URL: http://jira.codehaus.org/browse/MSITE-93 Project: Maven 2.x Site Plugin Type: Bug Reporter: Prasad Kashyap The post-site phase doesn't work. I have a simple antrun that echoes a msg.. It executes in the site phase but doesn't do anything in the post-site phase. http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#site -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MASSEMBLY-69) "dependencies" configuration element in assembly:unpack plugin read-only
[ http://jira.codehaus.org/browse/MASSEMBLY-69?page=comments#action_59177 ] Prasad Kashyap commented on MASSEMBLY-69: - Have attached a patch. Please review and apply. > "dependencies" configuration element in assembly:unpack plugin read-only > - > > Key: MASSEMBLY-69 > URL: http://jira.codehaus.org/browse/MASSEMBLY-69 > Project: Maven 2.x Assembly Plugin > Type: Bug > Reporter: Prasad Kashyap > Attachments: MASSEMBLY-69.patch > > > The "dependencies" configuration element in the maven-assembly-plugin is set > to read-only but the documentation on it say it's optional. > The assembly:unpack goal currently unpacks all dependencies specified in the > project. If this optional element was not read-only, it would be useful to > specify just those dependencies that needed to be unpacked. > http://maven.apache.org/plugins/maven-assembly-plugin/unpack-mojo.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MASSEMBLY-69) "dependencies" configuration element in assembly:unpack plugin read-only
[ http://jira.codehaus.org/browse/MASSEMBLY-69?page=all ] Prasad Kashyap updated MASSEMBLY-69: Attachment: MASSEMBLY-69.patch > "dependencies" configuration element in assembly:unpack plugin read-only > - > > Key: MASSEMBLY-69 > URL: http://jira.codehaus.org/browse/MASSEMBLY-69 > Project: Maven 2.x Assembly Plugin > Type: Bug > Reporter: Prasad Kashyap > Attachments: MASSEMBLY-69.patch > > > The "dependencies" configuration element in the maven-assembly-plugin is set > to read-only but the documentation on it say it's optional. > The assembly:unpack goal currently unpacks all dependencies specified in the > project. If this optional element was not read-only, it would be useful to > specify just those dependencies that needed to be unpacked. > http://maven.apache.org/plugins/maven-assembly-plugin/unpack-mojo.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MINSTALL-14) Unable to invoke install-file goal from inside a pom
Unable to invoke install-file goal from inside a pom Key: MINSTALL-14 URL: http://jira.codehaus.org/browse/MINSTALL-14 Project: Maven 2.x Install Plugin Type: Bug Reporter: Prasad Kashyap prasad hi brett.. why is that I can't use the install:install-file from inside a pom but I can use it from command line ? prasad from inside the pom i get an error that artifactid is read-only brett prasad: I think that's a bug -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with the site plugin
Can someone please let me know if the following issues are as designed or bugs that need a JIRA ? 1. The site:stage goal of the maven-site-plugin has disappeared in the 2.0-beta-4 version. 2. The post-site phase doesn't work. I have a simple antrun that echoes a msg.. It executes in the site phase but doesn't in the post-site phase. http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#site Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Lifecycle phases during a multi-module build [M2]
I have a multi-module build here under a top level pom whose is set to "pom". In the same m2 build lifecycle, I would like to execute some goals only at the parent, then execute all the children poms and then come back up to the parent to finish off the build. This currently doesn't seem to be possible. Even in a multi-module build, for most parts, even the parent is treated as yet another independent project. The parent goes thro' all of its lifecycle phases and only then each of the children poms are executed. 1) Is there a way for me to make my build come back up to the parent and execute some finish off goals ? 2) If there isn't, wouldn't it be nice if atleast the parent pom had 2 special phases that would be executed before and after all the children poms are executed ? Cheers Prasad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2075) "dependencies" configuration element in assembly:unpack plugin read-only
"dependencies" configuration element in assembly:unpack plugin read-only - Key: MNG-2075 URL: http://jira.codehaus.org/browse/MNG-2075 Project: Maven 2 Type: Bug Components: Plugin Requests Reporter: Prasad Kashyap The "dependencies" configuration element in the maven-assembly-plugin is set to read-only but the documentation on it say it's optional. The assembly:unpack goal currently unpacks all dependencies specified in the project. If this optional element was not read-only, it would be useful to specify just those dependencies that needed to be unpacked. http://maven.apache.org/plugins/maven-assembly-plugin/unpack-mojo.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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-2055) Error in Introduction to the Build Lifecycle
[ http://jira.codehaus.org/browse/MNG-2055?page=comments#action_58201 ] Prasad Kashyap commented on MNG-2055: - I believe this has been fixed already here. maven-site\src\site\apt\guides\introduction\introduction-to-the-lifecycle.apt Maybe it has not yet been published to the site. But I'll let someone more knowledgeable to close this one out. Cheers Prasad > Error in Introduction to the Build Lifecycle > > > Key: MNG-2055 > URL: http://jira.codehaus.org/browse/MNG-2055 > Project: Maven 2 > Type: Bug > Components: Documentation: Introductions > Reporter: Prasad Kashyap > Priority: Minor > > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > There is no phase called "before-integration-test". It should be replaced > with "pre-integration-test" -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2055) Error in Introduction to the Build Lifecycle
Error in Introduction to the Build Lifecycle Key: MNG-2055 URL: http://jira.codehaus.org/browse/MNG-2055 Project: Maven 2 Type: Bug Components: Documentation: Introductions Reporter: Prasad Kashyap Priority: Minor http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html There is no phase called "before-integration-test". It should be replaced with "pre-integration-test" -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2044) Error in ANT plugin development guide
Error in ANT plugin development guide - Key: MNG-2044 URL: http://jira.codehaus.org/browse/MNG-2044 Project: Maven 2 Type: Bug Components: Documentation: Guides Reporter: Prasad Kashyap Priority: Minor Think there's an error in the following guide http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html In the pom.xml code snippet of the POM section. the should be replaced by -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Invalid POM
Deleted the org/codehaus/plexus directory in my local repository and tried again. It worked fine this time. Thanx Carlos. Cheers Prasad. On 11/17/05, Prasad Kashyap <[EMAIL PROTECTED]> wrote: > > I ran a "mvn -U install" on a pom.xml for Geronimo. I saw the following > errors. > > [WARNING] POM for: 'org.codehaus.plexus:plexus-utils:pom:1.0.4' does not > appear to be valid. Its will be ignored for artifact resolution. > Reason: Parse error reading POM > > > [WARNING] POM for: ' > org.codehaus.plexus:plexus-container-default:pom:1.0-alpha-8' does not > appear to be valid. Its will be ignored for artifact resolution. > Reason: Parse error reading POM > > Cheers > Prasad >
Invalid POM
I ran a "mvn -U install" on a pom.xml for Geronimo. I saw the following errors. [WARNING] POM for: 'org.codehaus.plexus:plexus-utils:pom:1.0.4' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Parse error reading POM [WARNING] POM for: ' org.codehaus.plexus:plexus-container-default:pom:1.0-alpha-8' does not appear to be valid. Its will be ignored for artifact resolution. Reason: Parse error reading POM Cheers Prasad
Missing jars (velocity & jdbm)
When building the Geronimo project from a clean local repo, maven (*v1.0.2*) cannot find the following 2 jars to download. velocity-1.4-dev.jar jdbm-0.20-dev.jar These jars seem to have been recently removed from the remote repo. Any ideas on what happened to them ? Can someone please tell me where I can find them ? Cheers Prasad
