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
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
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
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 reporting
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.
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 lineending to be CRLF
while for the tar.* formats we'd like it to be LF.
Does anybody have ideas on how we can achieve
I have to use the repository 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
.
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 repository element in the maven-assembly-plugin's
assembly descriptor. Using this makes
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 repository
element
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..
field
namemyObj/name
version1.0.0/version
association
typeMyClass/type
/association
MyClass myObj = new
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
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
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
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 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
excludeDefaults in reporting 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 excludeDefaultstrue
[ http://jira.codehaus.org/browse/MPIR-32?page=all ]
Prasad Kashyap updated MPIR-32:
---
Attachment: test-parent.zip
excludeDefaults in reporting doesn't work.
---
Key: MPIR-32
URL: http
-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 dist..Mgmtsiteurl element is used, if the value does not have a
leading slash, then the first char of every
[ 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
[ 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
reporting has a excludeDefaults 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
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
Inheritance of plugin overrides that of execution
-
Key: MNG-2103
URL: http://jira.codehaus.org/browse/MNG-2103
Project: Maven 2
Type: Bug
Reporter: Prasad Kashyap
Attachments: test-inheritance.zip
[ 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 plugininherited is set to
false.
Now flip the inheritance boolean at the plugin level
I have a very simple pom with the reporting section set to
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-project-info-reports-plugin/artifactId
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
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
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
I have a multi-module build here under a top level pom whose
packaging 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
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
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
[ 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
[ 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
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
[ 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
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
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
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
[ 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
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
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: '
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
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
41 matches
Mail list logo