This happens whenever the maven-checkstyle-plugin does not find the
specified configuration file.
Adrian.
Ziv Ben-Eliahu wrote:
Short description of the problem
*
When running mvn release:perform, Checkstyle report plugin fails on:
[WARNING] Unable to load
I'm trying once again...
I'm not sure whether I'm not using dependencies correctly or this is a
bug, but the situation is as follows:
I have a junit 4.1 dependency in my project (and also xmlbeans).
Now xmlbeans happens to have a dependency on junit 3.8.
The problem is that my project
It isn't possible for now.
Emmanuel
Justin Deoliveira a écrit :
Hi all,
I am wondering if anyone knows of a good way to setup the subject line
of the mailer so that the build number is included. Or perhaps some
other way to set up the subject line so that build notification messages
don't
Continuum build all projects in the correct order like maven do it, but in
1.0.3, if a project doesn't have src changes, continuum doesn't build it even
if a dependency is modified.
In Continuum 1.1, Continuum build a project on dependency change too.
Dependency=a project that is in continuum
If your checkstyle file isn't in your source tree, you can set your checkstyle
config like that :
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
Emmanuel
Adrian Herscu a écrit :
This happens whenever the maven-checkstyle-plugin does not find the
Hi,
I have some questions with the dependencies resolution and custon jar
generation.
I have noticed that maven only find dependencies if they were generated by
Maven. Why ?
(So he only find the packages that were generated by the default lifeCycle
Mapping jar, ejb, war, ...)
For example :
I
Hi all,
I'm interested in solutions, how you would solve following situation?
I want to build a Maven 2.0 project but have three different pom.xml's for
that.
These files are:
1.) full build, including build and integration testing
2.) full build without integration testing
3.) start
hello,
you don't want 3 poms, you want 3 profiles.
Milos
On 3/27/07, Martin M [EMAIL PROTECTED] wrote:
Hi all,
I'm interested in solutions, how you would solve following situation?
I want to build a Maven 2.0 project but have three different pom.xml's for
that.
These files are:
1.) full
Hello Milos,
using three profiles is also possible, but then I see only one project in
Continuum with three different build-defintions.
But I would like to see three different projects with different names and
therefore I've to add three poms.
I will post this question on the Continuum forum, as
Hi all,
I'm interested in solutions, how you would solve following situation?
I want to build a Maven 2.0 project but have three different pom.xml's for
that.
These files are:
1.) full build, including build and integration testing
2.) full build without integration testing
3.) start
It isn't a good idea to add 3 pom for the same project.
The best way is to create 3 profiles and choose one of them in each build
definitions.
Emmanuel
Martin M a écrit :
Hi all,
I'm interested in solutions, how you would solve following situation?
I want to build a Maven 2.0 project but
If you want 3 project in continuum, you must use a different version in each.
continuum users list is better for continuum discussion.
Emmanuel
Martin M a écrit :
Hello Milos,
using three profiles is also possible, but then I see only one project in
Continuum with three different
Hi all,
When running the maven-dependency-plugin in a multi-project, it works
only for the first child project. The following messages appear on the
console:
[INFO] [dependency:unpack-dependencies {execution: default}]
[INFO] Expanding: C:\some.war into C:\target\somefiles
It does not work
Can you paste your config?
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: Tuesday, March 27, 2007 8:14 AM
To: users@maven.apache.org
Subject: [m2][maven-dependency-plugin] unpack-dependencies issue
Hi all,
When running the
Hi Emmanuel,
if I use three different build-definitions, I won't see, which
build-definition had which result at the first glance, when I log-in to
Continuum.
I only see one project with a result, but I don't see, that a certain kind
of build failed. As I'm interested to know, which build failed
We need to improve the UI to see build definitions results in the project list.
As I wrote on maven users list, if you add 3 project, you must use a different version for each. Without it, continuum won't know the build order because each project will have the same id
use an exclusion on the xmlbeans dependency to stop junit from
being used?
in 2.0.6 dependencyManagement should sort this.
Andy
On 27 Mar 2007, at 08:07, Ecker Severin wrote:
I'm trying once again...
I'm not sure whether I'm not using dependencies correctly or this is a
bug, but the
maybe
http://mojo.codehaus.org/sql-maven-plugin/
can be of help.
mit freundlichen Grüßen/best regards
Wolfgang Schrecker
Hat man Glück, findet man mehr, as man gesucht hat - aber man muss an der
richtigen Stelle suchen.
-- Lisa Randall in: Verborgene Universen p. 86
Please put it into Jira as an enhancement request.
On 3/27/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
It isn't possible for now.
Emmanuel
Justin Deoliveira a écrit :
Hi all,
I am wondering if anyone knows of a good way to setup the subject line
of the mailer so that the build number
Hi,
I built archiva from trunk rev. 521889.
If I assign the role Repository Observer to Guest I can access the
repository but I a newly created user.
The user I created does not have the Validated flag set in the User
Management page. Is that the reason?
Then how can I validate the user? Is an
One of the biggest reasons we passed on Continuum was the lack of
distributed building (in the sense that on machine controls what gets
built on other machines in a cluster, NOT on build is spread across
multiple machines). We have anywhere between 5 and 10 active branches
at any given time and
Here's what I came up with using the maven-antrun-plugin. How would I do
this with the assembly plugin?
profile
idzipContent/id
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
I'm currently migrating an ASP-based site to Maven and Subversion. The
previous site didn't use any source control, so the images directory is
quite large (1 GB). I can exclude/include this directory easily enough with
the maven-war-plugin and profiles, but I'm wondering what's the best way to
You need to create an assemlby file and configure it to zip up your
directory. There is plenty examples at assembly-plugin's site.
-D
On 3/27/07, mraible [EMAIL PROTECTED] wrote:
Here's what I came up with using the maven-antrun-plugin. How would I do
this with the assembly plugin?
Is there any way to either generate warning messages when a particular
dependency is used, or to even force someone to stop using it?
The problem we're found is this: we discover a reasonably serious bug in
version 1.5 of a Jar, fix the bug and change the version number to 1.5.1.
Another
Based on the fact that the [dependency:unpack-dependencies {execution:
default}]
Is showing up, the plugin is executing, it's possible that it isn't
finding anything to copy. Try removing the includes and excludes and let
it run with default behavior, you should see it copying all dependencies
of
zip and deploy? if so, use assembly:attached
On 3/27/07, mraible [EMAIL PROTECTED] wrote:
I'm currently migrating an ASP-based site to Maven and Subversion. The
previous site didn't use any source control, so the images directory is
quite large (1 GB). I can exclude/include this directory
Hi Brian,
Here are the relevant POM sections (if you need the entire POMs, please
let me know):
The parent
modules
modulesamples/module
modulelang/module
/modules
1nd child -- samples
build
plugin
groupIdorg.apache.maven.plugins/groupId
Assuming you're all developers in the same company, I would proceed as follows:
1. Use dependencyManagement in all your apps to centralize version numbers.
2. Use [1.5, ) or even [1.5, 1.6) to constrain versions, but not
[1.5]. For more info, see
Hi,
Using Maven generates all the artifacts (jars/wars/ears)
with a unique filename artifactid-version).type. How do we remove
the version number from the filenames? I need a generic way to do this,
because we have many sub-modules and would like to have a common
solution that can be
OK, I got it working by adding the following profile:
profile
idstatic-content/id
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
Hi,
I am a little unsure on this matter...there are a set of wars in which
I want to change the src/main/webapp default to something
else...should this be set in the war plugin config via
warSourceDirectory..and if I set this, do I need to add baseDir in
front of it...somehow this does not seem
I am having problems accessing CVS from the Maven release plugin.
Here's the SCM section of my pom.xml:
scm
connectionscm:cvs:atcvs.doit.wisc.edu:/var/opt/projects/CVS/east:easttest/connection
On 3/26/07, Baz [EMAIL PROTECTED] wrote:
All,
How is Cruisecontrol compare to Continuum? I am working on Maven 2
project and it seems to be pretty much integrated with Maven 2.
Considerations:
1. Integration with M2.
2. Control:
a. Does the interface allow both release engineers and
Hello all,
I have found multiple references to this problem and am wondering
whether this is a problem that can be solved or a deficiency in Maven's
architecture.
I have multi-module project with internal dependencies between modules.
mvn package and mvn eclipse:eclipse work fine.
mvn
[WARNING] Component returned which is not the same manager. Ignored.
[EMAIL PROTECTED]
--
Sean Qiu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm trying to use the assembly plugin to package up WARs from a bunch of
sub-projects. My goal is to get a target/release.zip after running mvn
package from the top-level directory.
I have this working when I run mvn package assembly:assembly, but I'd like
to make it work for mvn package of my
hi,
i was wondering if anybody of you already used raven
(http://raven.rubyforge.org/) instead of maven, and the your
experiences with it?
it builds on rake and ruby gems which is successfully used e.g. for
ruby on rails. what ibiblio is for maven, http://gems.rubyraven.org/
is for raven.
it
Hi,
I need to build and deploy Junit Integration tests to weblogic and run the
integration tests.I think cargo plug-in helps one achieve that.
A sample pom file to achieve this would be of great help.Server could be
anything.
Once deployed as a war i need to invoke the tests using the webapp
it was just a problem of classpath's length.
i made a shared directory with my repository as root disk and it's ok.
thanks
Joakim Erdfelt-2 wrote:
Wow. that's ugly!
The lack of STDOUT or STDERR output on this error is troubling.
Can you delete your
Wow. that's ugly!
The lack of STDOUT or STDERR output on this error is troubling.
Can you delete your $HOME/.m2/repository/jpox/jpox-enhancer/* files and
try again?
If it still fails, I'd like for you to run mvn --debug clean install
and see if there is anymore STDOUT or STDERR output.
- Joakim
Hi Joakim,
thanks for your answer.
If there were users with less permission than guest, that would be
alright for me.
What I meant is, that even if I make the new user Repository Observer
he is still not able to browse the WebDAV repository. I revoked
Repository Observer from Guest becuase I do
Hi,
I just installed the latest build from the trunk
continuum-20070327.03.tar.gz, but Continuum 1.1-SNAPSHOT fails to
checkout projects from CVS, with the exception in the GUI:
Exception:
org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutConsumer
I manually run the command
43 matches
Mail list logo
