from:"pjungwir"

Why not limit your plugin to generating the sources, and use the existing
plugins for compiling and packaging? This is likely to be more flexible,
plus it's a lot less work.

If you want different artifactIds for each bundle, you should use a separate
module for each. But you could also put them all into one module if you
wanted to use classifiers. Then you'd get names like this:

- generated-1.0-j2me.jar
- generated-1.0-j2se.jar
- generated-1.0-ansi-c.zip

Paul

Tomas Carlsson wrote:

Hi,

We have a tool that given one input file generates code for different
purposes (currently j2me, j2se, ansi-c). I'm planning to write an m2
plugin
for this tool but I'm not really sure how to do it.

What I'm trying to achieve is to only have one copy of the original input
file and whenever it is changed there should be a simple build/release
step
generating the result deliverables where the different types of
deliverables
preferably has the same version number (ie. generated-j2me-1.0.jar,
generated-j2se-1.0.jar, generated-ansi-c-1.0.zip)

My initial thought is to create a plugin that first generates sources for
the different purposes, then compiles them and lastly packages one archive
for each type.

I.e:
1 input file = 3 generated source trees = 3 compiled classes tress
=
3 packed archetypes

I'm seeing some trouble with this though:

1. It violates the maven philosophy of only having one archetype
2. The plugin seems to get quite complicated which I think should be
possible to avoid

Anyone having experience with this kind of setup? Any best practices out
there?

best regards
Tomas

--
View this message in context:
http://www.nabble.com/Best-practice-for-source-generating-multiple-archetype-plugin-tf2622203s177.html#a7361402
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven plugin interaction


I think you have the right approach, but there are two missing bits:

  - make sure the assembly plugin doesn't attach its result.
  - make sure the last step does attach its result.

An attached file is one that maven considers an artifact and will upload
when you run install/deploy/etc. By default, the assembly plugin tells maven
that its outputs are attached. Probably if you read the assembly
documentation you can turn this off.

The last step of your build should attach the final artifact. I guess
preverification doesn't actually produce a new jar, so the final artifact
would be the result of obfuscating?

There is no way in the pom to attach an artifact; it requires plugin code.
An obfuscator plugin should know how to do this, unless you're just running
some command line tool or an ant task.

I've been meaning to write a plugin that just attaches things, but I haven't
even started yet. Maybe you'd like to do it? :-) It would be very simple,
and I think a lot of people would find it useful. If maven supports it,
maybe it should also have an unattach feature.

Paul



Mikko wrote:
 
 Hi,
 
 First the environment: 
 
 1. Multimodule midp2.0 application - must have (OK)
 2. Assembly is required - must have (OK)
 3. Assembled code jar obfuscation - optinal (NOK)
 3. Assembled code jar preverification - must have (NOK)
 
 What I'm trying to do is to write a plugin(s) for our MIDP project so that
 above steps are accomplished. My problem is that after the assembly is
 complete some jar is constructed and once either the obfuscation or the
 preverification needs to take place the plugin does not know the name of
 the jar that was produced by the maven-assembly-plugin.
 
 It might be that I'm approaching this the wrong way, but could someone
 point me to the right direction, either by suggesting another approach or
 whatever... ;) Basically once the assembly is complete I need to do the
 obfuscation and preverification with the result.
 
 thanks in advance,
 Mikko
 
 

-- 
View this message in context: 
http://www.nabble.com/Maven-plugin-interaction-tf2628577s177.html#a7364650
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven plugin interaction


Hi Mikko,

The assembly plugin by default puts its result in target/ and names it
${finalName}-${version}-${classifier}.${type}, e.g. encc-1.0-bin.zip. I
would write your plugin so it accepts the input jar's filename as a
parameter, which defaults to the same naming scheme (or whatever is
convenient for you). Normally assembly's output is a finished product, so to
speak, but in your case it is an intermediate product; the build isn't
finished with it yet. Right? It is intermediate just like class files before
instrumentation. You control the build, so you can say where assembly puts
the jar and where the other plugins find it. If you were doing this in ant,
your jar and obfuscate tasks would need to cooperate; it's no different
here.

If you prefer to put the unobfuscated jar somewhere else, I believe you can
set that with the assembly descriptor or perhaps the assembly plugin's
configuration section.

Paul


Mikko wrote:
 
 Thanks, but still its not clicking in my brain ;) I fail to see how my
 plugin will be able to do the preverification and obfuscation if the
 assembly plugin does not attach its result. Basically as far as I can see
 my biggest issue is that my plugin does not know what the assembly plugin
 produced.
 
 I guess I'm missing something, can you explain perhaps with more detail.
 
 thanks,
 Mikko
 
 
 pjungwir wrote:
 
 I think you have the right approach, but there are two missing bits:
 
   - make sure the assembly plugin doesn't attach its result.
   - make sure the last step does attach its result.
 
 An attached file is one that maven considers an artifact and will upload
 when you run install/deploy/etc. By default, the assembly plugin tells
 maven that its outputs are attached. Probably if you read the assembly
 documentation you can turn this off.
 
 The last step of your build should attach the final artifact. I guess
 preverification doesn't actually produce a new jar, so the final artifact
 would be the result of obfuscating?
 
 There is no way in the pom to attach an artifact; it requires plugin
 code. An obfuscator plugin should know how to do this, unless you're just
 running some command line tool or an ant task.
 
 I've been meaning to write a plugin that just attaches things, but I
 haven't even started yet. Maybe you'd like to do it? :-) It would be very
 simple, and I think a lot of people would find it useful. If maven
 supports it, maybe it should also have an unattach feature.
 
 Paul
 
 
 
 Mikko wrote:
 
 Hi,
 
 First the environment: 
 
 1. Multimodule midp2.0 application - must have (OK)
 2. Assembly is required - must have (OK)
 3. Assembled code jar obfuscation - optinal (NOK)
 3. Assembled code jar preverification - must have (NOK)
 
 What I'm trying to do is to write a plugin(s) for our MIDP project so
 that above steps are accomplished. My problem is that after the assembly
 is complete some jar is constructed and once either the obfuscation or
 the preverification needs to take place the plugin does not know the
 name of the jar that was produced by the maven-assembly-plugin.
 
 It might be that I'm approaching this the wrong way, but could someone
 point me to the right direction, either by suggesting another approach
 or whatever... ;) Basically once the assembly is complete I need to do
 the obfuscation and preverification with the result.
 
 thanks in advance,
 Mikko
 
 
 
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Maven-plugin-interaction-tf2628577s177.html#a7367049
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [M2] Referencing Project Modules in plugin


Why do you have an asterisk after @parameter? Shouldn't you have a quote mark
after =?

Paul


M Campbell wrote:
 
 I need my plugin to make an arraylist out of the modules in the parent
 pom.
 
 I'm creating a List out of them. I'm trying
 
 [EMAIL PROTECTED] expression=${project.modules}
 
 But i get an error saying I didnt specify
 
 configuration
   ...
 childrenVALUE/children
 /configuration.
 
 
 Is there a way to directly reference my modules listed in
 project
 modules
 modulemodule1/module
 modulemodule2/module
 /modules
 /project
 
 

-- 
View this message in context: 
http://www.nabble.com/-M2--Referencing-Project-Modules-in-plugin-tf2636261s177.html#a7368230
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: error to package jar project


Please post the jar plugin section from your pom.


Barbier-Accary Aurélien wrote:
 
 Hello,
 
  
 
 I obtain an internal error when I try « mvn package » or « mvn install »
 for a « jar » project. The trace is:
 
  
 
 [INFO] Internal error in the plugin manager executing goal
 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the
 mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin
 'org.apache.maven.plugins:maven-jar-plugin'
 
  
 
 Can you help me to find the reason of this error??
 
  
 
 Regards,
 
  
 
 Bastien Jacoud
 
  
 
 
 

-- 
View this message in context: 
http://www.nabble.com/error-to-package-jar-project-tf2636731s177.html#a7368259
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Intalled pom version is not expanded resulting in a bogus pom version in the repository.

2006-11-14 Thread pjungwir


If you're installing the artifact every build, you might want to use a
-SNAPSHOT version.

Paul


Arne Saeten wrote:
 
 
 Hi,
 
 I have the same problem. Any solutions out there?
 
 Thanks,
 Arne
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Intalled-pom-version-is-not-expanded-resulting-in-a-bogus-pom-version-in-the-repository.-tf1558832s177.html#a7340673
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to get path to artifact for a dependency in a plugin


Hi Joachim,

Some methods on MavenProject are deliberately limited to what you see in the
pom, and others contain computed values. getDependencies() and
getDependencyArtifacts() are the former type. Probably you want
getArtifacts(). That will give you a Set of Artifact objects which should
have the information you want.

Regards,
Paul



Joachim Van der Auwera wrote:
 
 I am writing a plugin where I need access to the jar file for a
 dependency.
 
 I have tried looping the dependencies to find this (from 
 MavenProject.getDependencies()), but the dependencies always seem to 
 have null as their getSystemPath() value.
 
 I have also tried checking the artifacts, but similarly, getFile() on 
 the artifacts is also always null...
 
 So, what is the proper way to find the path where the artifact can be
 found?
 
 Thanks for the help,
 Joachim
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/How-to-get-path-to-artifact-for-a-dependency-in-a-plugin-tf2579609s177.html#a7326788
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: problem with provided scope


I believe that dependencyManagement does not actually add dependencies. It
just specifies which version should be used if a child adds that dependency.
So instead of using dependencyManagement, perhaps you should try
dependencies.

Paul




Joachim Van der Auwera wrote:
 
 Thanks for the help.
 
 I had at least two libraries with this problem, and one of them did not 
 have any transitive dependencies, the other one has. So unfortunely, it 
 cannot be just that.
 
 Any other ideas?
 
 Thanks for the help,
 Joachim
 
 Edwin Punzalan wrote:

 hmm... I'm pretty sure the provided scoped artifacts appear in the 
 compile phase... maybe what your project is missing are the transitive 
 dependencies of the provided artifact?

 Joachim Van der Auwera wrote:
 I am using maven 2.0.4

 In my project, I have some artifacts which are defined as provided 
 scope as these artifacts should not be included in the war file. So 
 far so good.

 However, once I change the scope, my project does not *compile* any 
 more as the artifacts seem to have disappeared from the compile 
 classpath as well.

 I have defined the scope in my global pom (in dependecyManagement 
 section) and the classes which reference these are in a module, where 
 the dependency is mentioned without scope (or version).

 What am I doing wrong?

 Thanks for the help,
 Joachim

 -
 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]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/problem-with-%22provided%22-scope-tf2579617s177.html#a7327408
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Assembly plugin - packaging chaning the extension


Hi Ste,

I'm not sure how to get a s4j extension. You could rename the file, but then
it wouldn't be an attached artifact, so things like deploy would break.

To get rid of the top-level directory, put this in your assembly descriptor:

  includeBaseDirectoryfalse/includeBaseDirectory

Paul



Stefano Nichele-2 wrote:
 
 Hi All,
 I have a problem with the assembly plug-in.
 My project builds a war application but the output should be a zip file 
 with the following structure:
 
 /webapp/ 
 myapp.war
 /config
 configFile1.xml
 configFile2.xml
 configFile3.xml
 
 I'm using the following assembly descriptor:
 
 assembly
   idbin/id
   formats
 formatzip/format
   /formats
  
   fileSets
 fileSet
   directorysrc/main/resources/bean/directory
   outputDirectoryconfig/outputDirectory
   includes
 include**/*.*/include
   /includes
 /fileSet
 
 fileSet
   directorytarget/directory
   outputDirectorywebapp/outputDirectory
   includes
 include*.war/include
   /includes
 /fileSet
   /fileSets
 /assembly
 
 Using that descriptor, the output file is a zip file but i need a 
 different extension. I mean, I need a zip file (as format) with 
 extension s4j.
 
 How can i do to  obtain that ?
 
 Moreover, using the above descriptor I obtain a zip file that contains:
 
 /myartifactid
 /webapp
  myapp.war
/config
 *.xml
 
 How can I remove the first level myartifactid ?
 
 Thanks in advance.
 Ste
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Assembly-plugin---packaging-chaning-the-extension-tf2584876s177.html#a7328439
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Continue Build and Site Generation on Junit failure

Suppose you say this:

mvn test mvn site

That gives you a failure but not a site. And if you say this:

mvn test; mvn site

you get a site but not a failure.

So what if you wrote a quick plugin that checks for errors in the surefire
reports? Then you could say:

mvn test; mvn site; mvn my-group:check-for-failures

Paul

jp4 wrote:

I am interested in what you did. We use CC as well. Any info you can
provide would be greatly appreciated. This is very important as we have a
huge codebase and would like to identify all errors every night (NOT JUST
THE FIRST ONE!)

Thanks,

jp4

Jon SlinnHawkins wrote:

TestFailureIgnore will then result in a build success. When infact the
tests failed, so the build needs to be failed.

I had exeactly the same issue.

We are using CruiseControl for our Continuous Integration system.
Unfortunately I had to modify the CC code. It was only a minor change
but
it has enable us to

execute maven 3 times as part of the same build, if any of the 3 runs
fail
the build will continue until all 3 are finshed and THEN report a build
failure.

FYI -
1 - Checkout source and cleanup folders
2 - Maven deploy (inculding unit and functional testing)
3 - Build the site.

If you are using CC i will try and find the peice of code i changed. It
was
a very simple change.

Cheers

Jon

Alexandre Russel [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
View this message in context:
http://www.nabble.com/Continue-Build-and-Site-Generation-on-Junit-failure-tf2553508s177.html#a7329947
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add Directory to Jar Manifest Classpath

2006-10-27 Thread pjungwir


Oh, I'm sorry, I thought you were saying that the Class-Path entry in the
manifest couldn't refer to non-jar items. It's very easy to set the
Class-Path entry using either the jar plugin or the assembly plugin. In the
configuration section, specify an archive element. The jar plugin has
pretty good docs for this. If you want maven to include your dependencies,
say this:

archive
  manifest
mainClasscom.example.App/mainClass
addClasspathtrue/addClasspath
  /manifest
/archive

To give your own classpath (or prepend to what maven writes), do this:

archive
  ...
  manifestEntries
Class-Pathconfig/ classes//Class-Path
  /manifestEntries
/archive

But note that currently the assembly plugin has a bug and ignores
manifestEntries. The jar plugin does not have this bug.

Paul



berndq wrote:
 
 Hi,
 
 Are you sure that documentation wasn't talking about applets? I've run
 executable jars with Class-Path manifest entries referencing the
 filesystem
 many times.
 
 I looked it up again:
 
 http://java.sun.com/j2se/1.3/docs/tooldocs/win32/java.html
 goto -jar option, there it says
 When you use this option [Main-Class:classname], the JAR file is the 
 source of all user classes, and other user class path settings are
 ignored.
 
 I was trying to extend the classpath from outside the jar (-cp xxx)
 and this is what does not work according to the specs.
 
 I did not try to extend the classpath in the manifest inside the jar.
 Is this possible at all when using the assembly plugin the create the
 classpath entry in the manifest?
 
 thanks for you info!
 
 Bernd
 
 Paul
 
 
 berndq wrote:
 SingleShot wrote:
 I am building an executable JAR that depends on a handful of other JARs
 and a
 few config files being on the classpath. I want the config files to be
 editable by the end user, so did not add them as internal JAR
 resources.
 I've configured the maven-jar-plugin to generate a manifest and add the
 dependencies to its classpath (and create a mainclass entry), but
 cannot
 figure out how to configure it to add my config directory (containing
 the
 config files) to the classpath.

 Is it possible to add a directory to the classpath of a Maven-generated
 Manifest?
 Hi,

 I had exactly the same problem. This is not a maven but a (sun?) Java 
 problem:

 Executable jars use a classloader that can only load resources/classes 
 from other jars and not from the file system. I found this documented 
 somewhere under java.sun.com.


 So I had to stop using executable jars :-(

 best regards
 Bernd

 -
 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]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7031994
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to get the groupId and other values from a Maven pom file using


Are you writing a plugin? In that case, declare a parameter of type
org.apache.maven.project.MavenProject and give it these javadoc annotations:

  @parameter default-value=${project}
  @required
  @readonly

You can call methods as shown here:

http://maven.apache.org/ref/current/maven-project/apidocs/index.html

Paul


Sheshabhattar, Sharda [CIB-IT] wrote:
 
 Hi,
 I have a java code which should extract the groupId ,artifactId and
 other details from a pom file.
 What apis should I use to achieve this?
 Please help.
 Thanks,
 Sharda
  
 
 

-- 
View this message in context: 
http://www.nabble.com/How-to-get-the-groupId-and-other-values-from-a-Maven-pom-file-using-java-code-tf2513557.html#a7013602
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add Directory to Jar Manifest Classpath


I don't understand. 2.2 is the plugin version, not the maven version, right?
That appears to be released. For me, it's what maven just uses; I didn't do
anything special.

Paul


Syvalta wrote:
 
 
 pjungwir wrote:
 
 
 Syvalta wrote:
 
 But that doesn't work for me, see:
 http://jira.codehaus.org/browse/MJAR-60.
 
 I didn't get any error with a trailing slash inside Class-Path. JIRA
 says this is fixed against 2.2. I'm not sure why the bug is still open in
 that case. . . .
 
 
 There isn't snapshot of 2.2 yet, so I didn't test with that, so I can't
 confirm. However, as I understand it, fix for means that is should be
 fixed before that release, not that it's fixed.
 

-- 
View this message in context: 
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7014719
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ftp-wagon Unrecognised tag: 'extensions'


I'm not positive, but I think that extensions block will just make
wagon-ftp available as it is needed. I think it's the maven-deploy-plugin
that does the work of picking what to send. But maybe someone with more
knowledge of multi-module builds can help?

Paul


Jeff Mutonho wrote:
 
 On 10/25/06, pjungwir [EMAIL PROTECTED] wrote:

 Hi Jeff,

 What is the benefit of loading wagon-ftp in a profile? That extensions
 block doesn't per se do anything; it just makes wagon-ftp available. I
 guess
 you're loading it for the sake of the sftp:// repository in the top-level
 POM? Then why not just put extensions up there, too (with no profile)?

 Paul

 --
 
 If I put it in the top-level POM , how will it know which ear file to
 ftp to the sftp:// repository ?
 My build results in two different ear files, one with a web
 application and another with some ejb application.The reason for
 having two different ears is that the two ears are deployed
 differently and they serve different purposes.
 Basically all I want to do is ftp two ear files at the end of my build
 to  my sftp:// repository.That's all I wanna do.
 
 -- 
 
 
 Jeff  Mutonho
 
 GoogleTalk : ejbengine
 Skype: ejbengine
 Registered Linux user number 366042
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/ftp-wagon-Unrecognised-tag%3A-%27extensions%27-tf2496953.html#a7014831
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven plugin execution phase: post-site?


Hello,

@execute means that when the mojo is run, it should spawn a separate
lifecycle and run everything up to the given phase before running itself.
It's useful for running a mojo from the command line like mvn plugin:mojo,
but it's problematic when you want to bind the mojo to a phase.

In your pom, you're binding your plugin to the site phase. So when maven
gets there, it processes your mojo. It sees the mojo's @execute tag, so it
spawns a separate lifecycle, runs everything from the beginning up to
post-site, then runs your mojo.

So first remove the @execute tag. Then either change the pom so you're
binding the mojo to the post-site phase, or use the @phase tag to set a
default phase of post-site, and don't give any phase in your pom.

Paul



kovalen pechaycaren wrote:
 
 Hi,
 I am writing a maven plugin to be run on other projects.  It needed to be
 executed after the site phase.  For a multi-project (one parent and
 several
 modules), how to I configure the plugin to be run after reports have been
 generated for all modules?
 
 The problem is that the plugin is being run DURING the site phase (which
 results in a number of invocation when only one for a project was
 expected) when i include the following in the parent pom:
 
 plugin
 groupIdcom.accenture.collab.maven.plugin/groupId
 artifactIdcollab-quality/artifactId
 version0.1-SNAPSHOT/version
 executions
  execution
   phasesite/phase
   goals
goalquality/goal
   /goals
  /execution
 /executions
 /plugin
 I have also included the following in my plugin's mojo, but no success:
 * @execute phase=post-site
 
 Anyone can help?
 
 Thanks
 -- 
 Kovalen
 
 

-- 
View this message in context: 
http://www.nabble.com/maven-plugin-execution-phase%3A-post-site--tf2513362.html#a7014966
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Using Cactus with Maven 2


Hi Mohan,

There is an integration-test phase that comes after package. But if you
really want to test inside a container, you probably want to use a
continuous-build system, unless you tell maven to deploy to the app server
during package.

Paul


Mohan Gopal wrote:
 
 Hi,
 I have been trying to run cactus test cases with Maven
 2 using all possible approaches and to no avail. Would
 be grateful if someone can answer the following
 
 1. Is there any cactus plugin for Maven 2. There is
 absolutely no documentation on this plugin. Anything,
 a sample code would help very much.
 
 2. Testing life cycle stage comes before packaging
 life cycle stage. An in-container test, as we do with
 cactus, cannot be done unless you deploy your
 application. 
 
 So there is this contradiction - you cannot test
 unless you deploy and you cannot deploy unless you
 test. 
 
 Did someone think about itand can share what did
 they finally decide on :)
 
 Thanks,
 Mohan
 
 __
 Do You Yahoo!?
 Tired of spam?  Yahoo! Mail has the best spam protection around 
 http://mail.yahoo.com 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Using-Cactus-with-Maven-2-tf2513964.html#a7015077
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add Directory to Jar Manifest Classpath


That's a very handy command! You're right, it says 2.1. Yesterday I tried
running with -X, and I thought it said it was getting 2.2, but now -X also
says 2.1, so I must have made a mistake. My apologies!

But the trailing slash still works on my system. :-) But I'm running linux,
and the bug is filed against windows

Paul


Syvalta wrote:
 
 
 pjungwir wrote:
 
 I don't understand. 2.2 is the plugin version, not the maven version,
 right? That appears to be released. For me, it's what maven just uses; I
 didn't do anything special.
 
 
 Yes, the version of jar-plugin. To my knowledge 2.1 is the latest version
 (see
 http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-jar-plugin/).
 Jira lists both 2.1 and 2.2 unreleased ( which is wrong for the latter).
 Are you sure you have checked the version of the correct plugin? Yuo can
 check the version with command mvn -Dplugin=jar help:describe.
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7016303
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add Directory to Jar Manifest Classpath