Thanks, that did the trick! -K
On Jul 4, 2008, at 3:08 PM, Lukas Theussl wrote:
You define the site plugin inside , I guess you want it
inside .
I can confirm that MSITE-274 is fixed for me with beta-7.
HTH,
-Lukas
Kathryn Huxtable wrote:
Okay, I renamed my entire repository and started f
On Fri, Jul 4, 2008 at 6:35 PM, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]> wrote:
> However, when I bound this plugin to a phase in the pom.xml (e.g.
> deploy) and ran the following:
>
> mvn deploy
>
> Then the plugin executed correctly. Why doesnt the plugin work from the
> comma
I have tried running a Maven plugin from a directory which has my
standard java maven structure and pom.xml. From this directory, I run
the following command:
mvn test-group:test-plugin:TEST:work
Here, I got wrong results.
However, when I bound this plugin to a phase in the pom.xml (e.g.
Michael McCallum wrote:
> On Fri, 04 Jul 2008 02:43:03 Jörg Schaible wrote:
>> Sorry, but our priority is to ensure that all artifacts are built with
>> the same plugins and use the same artifact versions. In your model I have
>> to duplicate all the versions for your individual service parents. T
You define the site plugin inside , I guess you want it
inside .
I can confirm that MSITE-274 is fixed for me with beta-7.
HTH,
-Lukas
Kathryn Huxtable wrote:
Okay, I renamed my entire repository and started from scratch. After
several attempts with strange results, I removed the maven-site
Michael McCallum wrote:
> On Fri, 04 Jul 2008 03:59:29 Peter Horlock wrote:
>> Sorry, but what's the purpose of the release plugin anyway? It's site
>> doesn't really tell it:
>> http://maven.apache.org/plugins/maven-release-plugin/
> Very good question and simple to answer...
>
> release-prepar
Okay, I renamed my entire repository and started from scratch. After
several attempts with strange results, I removed the maven-site-plugin
directory from my local repository and ran the command at the head of
the attached file. I'm also attaching my pom.
Note that it downloads both the bet
Okay, I deleted the older site plugins from my local repo and rebuild
the site. It downloaded version 2.0-beta-6, despite my having, so far
as I know, no references to it, and a specific reference to 2.0-beta-7
in my pom.xml file.
I'm bewildered. Surely there are no transitive reporting dep
If you want to try it out, the code is available at
$ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvs/i2mi login
$ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvs/i2mi co
ldappc-mvn
The tests are broken at the moment, but not relevant for the site, so
adding -Dmaven.test.skip=true will be neces
I can say, having looked at the HTML produced, that all the anchor
tags have newlines following them. This is generating the extra space.
For instance, the APT text
After reading this document, if you desire more detailed design
information, go to
{{{design.html}Design}}.
Depending on
So I intended also to ask if I should maybe be looking at anything
else. Consider it asked. -K
On Jul 4, 2008, at 9:53 AM, Kathryn Huxtable wrote:
Yes, I did. It got downloaded, along with the newer doxia. I assume
it's getting used.
I think it's good practice to specify the version on you
Yes, I did. It got downloaded, along with the newer doxia. I assume
it's getting used.
I think it's good practice to specify the version on your build and
reporting plugins to ensure repeatability of builds.
-K
On Jul 3, 2008, at 3:30 PM, Dennis Lundberg wrote:
Kathryn Huxtable wrote:
I
Btw, how do you perform nightly builds, continuous integration, automated
regression tests, etc if your build only works with eclipse (To be more
specific: with a dedicated eclipse installation/configuration)?
You will get all those out of the box for free if you use maven the 'maven-way'
:)
h
If you take the user libraries and write all the dependencies to the pom, your
colleagues will not notice much a difference after a mvn eclipse:eclipse
The Javadoc is usually already in the maven repo. So if you take an artifact
from a public repo you will almost always find an attached sources.
> 11) don't mix inheritance and aggregation. that means a parent pom NEVER
ever
> has modules, if you think about the concept for a minute - or longer -
there
> will be a moment of enlightenment
>
>
> structure of the generated archetype.
>
> So, I'm curious as to why you would say not to do this.
struberg wrote:
>
> Hi Vickey!
>
> I'm not aware, but it seems very unlikely.
>
> A maven build should always be possible regardless if the developer use
> idea, eclipse, netbeans, vi or whatever.
>
> So the support for those IDEs is only a one-way from maven to this IDE,
> but I don't kno
Hi,
You can use the maven-jar-plugin [1] with the test-jar goal.
Or you can use the maven-assembly-plugin [2] .
If what you want to do is only to package the tests classes in a jar file,
run mvn jar:test-jar. If you want it to be done automatically in your build,
configure the plugin in your pom
I run mvn package only package the java code into a jar file. How can I
package the test code?
--
View this message in context:
http://www.nabble.com/How-to-package-test-souce-code--tp18274870p18274870.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
Hi Vickey!
I'm not aware, but it seems very unlikely.
A maven build should always be possible regardless if the developer use idea,
eclipse, netbeans, vi or whatever.
So the support for those IDEs is only a one-way from maven to this IDE, but I
don't know one single point where the data flow
Hi,
I am trying to refer to a multi-module project in my own project. For example,
selenium-rc is a top level pom project containing a number of modules and
I'd like to use all such modules. So, in my pom.xml I have:
org.openqa.selenium
selenium-rc
0.9.2
test
It does
20 matches
Mail list logo
