Hi,
I have the following usecase:
Run a mojo to collect generated reports from all other modules and combine
these into one big report.
This involves collecting a number of XML files which will be combined into
one file, but that's not the problem. Just a matter of retrieving output
My guess would be:
Submit a report at http://jira.codehaus.org/browse/MNG
Or even better, report and submit a patch at the same location.
Info about patches:
http://maven.apache.org/guides/development/guide-m2-development.html
-Jeroen
On 05/06/07, Thorsten Heit [EMAIL PROTECTED] wrote:
Could it be that you are using uniqueVersion in the configuration of your
repositories?
Perhaps such a configuration without cleaning before compiling results in
multiple similar depenencies...
-Jeroen
On 19/04/07, Raghurajan Gurunathan [EMAIL PROTECTED] wrote:
Hi All,
some of our team has
missing artifacts. Isn't that correct? If that is correct, then
maven won't download the new required artifacts to the internal repository
Thanks,
David
Jeroen Leenarts [EMAIL PROTECTED]
04/20/2007 07:55 AM
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users
, Jeroen Leenarts [EMAIL PROTECTED] wrote:
That is correct. Overriding central prevents loading from the Ibiblio
repository.
I was a bit fast with my responce, since you would like to be able to
update your internal repository as well.
Th suggestion by Jim is a very interesting one. By having
Define your internal repository as central. That overrides the Maven Ibiblio
repository setting.
Jeroen
On 20/04/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Hi Everyone,
I'm pretty new to maven and have a repository question. I have set up a
internal repository that will hold the
Sounds reasonable.
In the dependency tag you have to define the type by using the type tag.
Else Maven defaults to jar.
Wodzuu can check this by having a look in his local repository. He wil
probably find a file without an ejb classifier. (Which is nothing more than
blabla-ejb-1.0.0.jar, notice
Hello,
At the project I'm at right now we have a plugin which runs the ejbdeploy
tool for any EJB's we might have. (EJB Deploy generates WebSphere specific
stub and interop code for an EJB.) The mojo pickes up the standard EJB jar,
runs it through EJB Deploy and publishes the result using a
This will wett your appetite:
/**
* @parameter expression=${project.packaging}
* @readonly
*/
private String packaging;
/**
* @see org.apache.maven.plugin.Mojo#execute()
*/
public void execute() throws MojoExecutionException,
MojoFailureException {
using an inheritance tree for your poms.
+ toplevel pom
--jar pom
FooBar pom
--ejb pom
FooBarEjb pom
You would then define the checkstyle stuff in the jar of ejb poms.
But it will probably not fit somewhere.
jeroen
On 19/04/07, Jeroen Leenarts [EMAIL PROTECTED] wrote:
This will wett your
tree organized after artifact type does not map to responsible
developer/team very well.
Perhaps it would be possible to use profiles for controlling the use of
plugins and let the packaging activate the profile?
Thanks.
Peter
-Original Message-
From: Jeroen Leenarts [mailto:[EMAIL
I've looked it up in the docs:
http://maven.apache.org/pom.html#Properties
It might actually be project.packaging.
Jeroen
On 19/04/07, Jeroen Leenarts [EMAIL PROTECTED] wrote:
You might be on to something there
The page:
http://maven.apache.org/guides/introduction/introduction
Perhaps this links helps a bit:
http://maven.apache.org/examples/injecting-properties-via-settings.html
On 19/04/07, Wayne Fay [EMAIL PROTECTED] wrote:
http://maven.apache.org/pom.html#Properties
There is no Maven equivalent to build.properties. All properties for a
project should be
Look into the distributionmanagement section of the Maven pom:
http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_distributionManagement
Note the uniqueVersion element.
Jeroen
On 18/04/07, Chen Li [EMAIL PROTECTED] wrote:
Hi,
It might be a very basic question.
I want to add
This'll help a bit too I think:
http://docs.codehaus.org/display/MAVENUSER/Creating+the+repositories
(search for uniqueVersion with your browser on the page.)
On 19/04/07, Jeroen Leenarts [EMAIL PROTECTED] wrote:
Look into the distributionmanagement section of the Maven pom:
http
, as you described, and surprisingly it
works.
Everything works fine with Maven 2.0.5.
Cheers,
Henrique
Jeroen Leenarts wrote:
I'm not sure how to debug this, but this is what happened after having
upgraded to Maven 2.0.6. I have checked my dependency management
sections as
described
Could try binding to the phase post-site. It's an imperfect solution to a
imperfect plugin.
As I see it plugin execution within a phase is undetermined.
Jeroen
On 05/04/07, Gianfranco Oldani [EMAIL PROTECTED] wrote:
Hi,
I have developed a plugin which I want to setup in the reporting
*
Jeroen
On 05/04/07, Jeroen Leenarts [EMAIL PROTECTED] wrote:
I'm in the process of checking whether or not a clean build with 2.0.5fails. It
is running as we speak.
Just a note with 2.0.6:
mvn clean install fails
mvn clean compile succeeds
mvn clean compile and then mvn install succeeds
I'm not sure how to debug this, but this is what happened after having
upgraded to Maven 2.0.6. I have checked my dependency management sections as
described in the release notes. No conflicts there.
1. Get a fresh code base.
2. When I run mvn install the build fails during the compile phase of
David Liles wrote:
I just downloaded Maven and followed the install instructions. I created a very
basic project.xml file and when I attempt to run maven site:generate from the
same location as the project.xml file I get an error.
I have environment variables defining JAVA_HOME, ANT_HOME and
David Liles wrote:
Not sure if this is what you're asking for...
BUILD FAILED
Compile failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:844)
...
File.. C:\Documents and Settings\david.liles\.maven\cache\maven-java-plugin-
Try comparing your .classpath (also generated by XDE) file with the
dependancies stated in your project.xml. They should match up...
Btw, you can a properly configured Maven project generate eclipse 2.1
(current XDE) and eclipse 3.0 .project and .classpath files. Simple
matter of adding an
STRAYER, JON (SBCSI) wrote:
I have about 15 projects and a master POM for all of them. I
use maven to build the individual projects as well as the
integrated web site. When Maven does this multiproject build,
it uses the current development branch for the project that
it is building, but the
23 matches
Mail list logo
