It'd be dangerous is it didn't remove the jar mojo from the forked
lifecycle, as the jar mojo is the mojo that forked the lifecycle in
the first place... and if it didn't remove the plugin from the forked
lifecycle, the forked lifecycle would fork again... and again and
again
2009/2/18
Did you report or resolve this problem eventually?
On 21/01/2009, at 9:27 PM, PeterNilsson wrote:
Our build on Linux (redhat) has more than doubled in time since we
upgraded
the assembly plugin from 2.2-beta-1 to 2.2-beta-3.
I did some testing with a tiny project for different versions of
You have to do:
right click on project - Maven - Enable nested modules
HTH,
Stefan
On Wed, 18 Feb 2009 00:45:11 +
sebb seb...@gmail.com wrote:
I tried enabling Maven Dependency Management on a project with modules
(Surefire 2.4.3) and the dependencies from the top-level project were
You should look at the exclusions tag for dependencies[1]. Using this, you
can exclude commons-collections from the ZK framework dependency.
Stefan
[1] http://maven.apache.org/pom.html#Exclusions
On Wed, 18 Feb 2009 14:55:21 +0900
Ashika Umanga Umangiliya umanga@gmail.com wrote:
Greetings
It is included in Sonar 1.7 that is planned for mid-march. Development has
started already [1].
Full detail are available in the ticket SONAR-205 [2]
Olivier
[1] http://skitch.com/t/pc8
[2] http://jira.codehaus.org/browse/SONAR-205
PabloS wrote:
Great, any idea on when you are going to be
Hi all,
I'm relatively new to Maven and I'm working on a web app project. It's
packaged as a war archive, but what I want is to generate an alternative
package that contains also test classes and resources. The ideal situation
is an executable jar from which test classes can be launched. I tried
Thanks, that's fixed it.
Unfortunately it does not seem to deal with multiple Java versions
well - I would expect it to set the Java version to the highest
version it finds - or at least warn the user that there are multiple
requirements.
On 18/02/2009, Stefan Seidel ssei...@vub.de wrote:
You
I am wondering if Brian, or any other Maven expert our there, could
explain how this warning could be avoided entirely. I have looked into
this at length when adding, for example, source jars to my distribution.
However, the warning always occurs.
I have a pretty good understanding of why the
Hello,
This is actually a repost of this message:
http://markmail.org/message/2xzsgvxmln5krgdl
However, no answers came and I didn't find a solution yet. I check out
a project based on a floating tag in CVS. The tag indicates the code
that can go in a release. Before the release plugin can
The Maven team is pleased to announce the release of the Maven 2.0.10
This is a stable bug fix release and you can see the full list of
issues fixed at
http://maven.apache.org/release-notes.html
Enjoy,
-The Maven team
-
To
It is always better to import Maven projects as Maven projects, not
normal projects and then enabling dependency management. We should
probably just remove that option as it seems to confuse many people
and can also corrupt your eclipse projects.
The version of Java used is determined by
maybe I did not understand what you really like to do, but did you look at
release:rollback? This will revert the pom back to the original status.
One for sure: the scm providers won't help you much when it comes to
manipulating the pom.xml. They are strictly for scm handling only.
LieGrue,
Mark,
2009/2/18 Mark Struberg strub...@yahoo.de:
maybe I did not understand what you really like to do, but did you look at
release:rollback? This will revert the pom back to the original status.
One for sure: the scm providers won't help you much when it comes to
manipulating the pom.xml.
what do you mean with:
tag one of your projects with code_to_include_in_release
?
you surely mean the tag which will automatically be created via
realease:prepare, don't you?
mvn release:perform should work on such a tag without writing things back to
the repo (at least this was the status the
2009/2/18 Mark Struberg strub...@yahoo.de:
what do you mean with:
tag one of your projects with code_to_include_in_release
?
you surely mean the tag which will automatically be created via
realease:prepare, don't you?
No. Read my first mail: developers tag the code that they want to go
into
humm, for such things, you usually have to create a branch and not a tag.
Because that's what you like to do: do some work on that branch! (even if it's
only a release)
And take care that you have to set the branch info in the scm section in your
pom properly for making the release plugin
Hi
I'm confused about how profiles.xml files work.
Here's my case:
I want to filter a JEE datasource file depending on the target platform
(development, integration etc.). For this I've defined all those target
platforms as Maven profiles with their specific properties in my Master
POM:
Hello,
I have an m2eclipse project which references a maven jar dependency. In an
eclipse run configuration (for launching jetty, to be specific) I need to
reference the path to that jar dependency in the VM args, because it is a
javaagent. If the jar in question were in my build path, I could
Hi folks,
I'm attempting to attach an assembly to a sub-module's artifacts, but it
fails to work when I do a release:perform. I have the Assembly plugin
bound to the package phase, but it lives in a pom type submodule.
The assembly plugin is activated through a profile that exists in the
how to include a persistence.xml file inside the META-INF of an EAR ?
the file is inside an ejb-module that is also included in the EAR . ..
--
Please help to test this application:
http://fgaucho.dyndns.org:8080/cejug-classifieds-richfaces
Many projects that provide artifacts via maven often include only the
binary and source artifacts. If a user is just starting with maven, it
can be frustrating not being able to get the JavaDoc artifact in the
same manner as the other variants.
This is particularly important in GUIs
how to include a persistence.xml file inside the META-INF of an EAR ?
Put the file in the ear root/src/main/application directory.
the file is inside an ejb-module that is also included in the EAR . ..
Copy it to the EAR module, or use a plugin to unpack the file there
(or /target) during
eh, vou revisar aqui.. vou separar o modulo de persistencia (mais um
:).. vai ficar um monte de modulos mas esta é a convenção maven ..
Para os que estão acompanhando a saga da migração, vale um
agradecimento: eu tenho entre 1 a 1,5 horas por dia para mexer no
sistema.. e nem todos os dias... no
We're running into an issue that causes our automated builds to fail
quite frequently now and wonder what it is about our use of maven that
is causing this. The builds are failing because the order in which
maven (2.0.9) is choosing to build the components of a large,
multi-component project is
Hello,
I am experiencing weird problem when I am using maven.
When I am using Windows and building jar file and using that jar in other
project all other resources specified in pom getting to my .m2 automatically
and in other project I don't need to include them second time.
When the same jar I
Any idea what am I doing wrong in UNIX?
Unix cares more about upper/lower-casing of file names than Windows
does. Is this perhaps related to your problems?
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
Wayne Fay wrote:
Any idea what am I doing wrong in UNIX?
Unix cares more about upper/lower-casing of file names than Windows
does. Is this perhaps related to your problems?
Wayne
-
To unsubscribe, e-mail:
Hi folks,
I've been working on this all day, and I'm no closer to getting it to
work than I was this morning. I hope someone has that little tid-bit of
information that I'm clearly missing.
I have a multi-module project that is distributed in the form of a ZIP
file. The assembly is built
When building the directed graph of how to order the modules at build
time, Maven doesn't consider (that I'm aware of) the existence of a
dependency in the local repo. Are you using versions to describe the
dependency between these modules? That's about the only thing that comes
to mind? (even
I have project A
which has dependencies on C jar and D jar
and I have project E which is using A.
If I am building the jar in Windows I will get C D in my repo and my maven
automatically but if the same jar was build on UNIX I will not get them at
all. To be able use jar A I will need to
We found the problem today. It turns out that the command we were using to
build was:
mvn install site
(we also tried:
mvn clean install site)
It turns out that it is the site that is causing the problem. There is a
JIRA ticket on this issue (I'm not on my work machine right now and
On Wed, Feb 11, 2009 at 10:46 AM, Barrie Treloar baerr...@gmail.com wrote:
On Tue, Feb 10, 2009 at 11:53 PM, Martin Jäger
martin.jae...@netcetera.ch wrote:
Hi together
The last release of maven-eclipse-plugin is from April 2008 and as I see in
Jira version 2.6 is complete (taskfree).
Who
Hi,
I use the maven ant task ; I have the dependency list (artifact:dependencies
filesetId=dependency.fileset useScope=runtime pomRefId=projet/)
but I don't understand how to get the project jar (a thing like
$repository/$groupId/$artifactid-$version.jar)
Thanks in advance for your help.
33 matches
Mail list logo
