write your own assembly descriptor.
you can do exactly what you are after (i.e. copy all the war artifacts to
ABC, copy all the jar artifacts to XYZ and wrap the whole thing up in a
tar.gz file
-Stephen
On 6 July 2010 21:01, Ron Wheeler rwhee...@artifact-software.com wrote:
On 06/07/2010 2:24
The rule for Maven is that the order of plugin execution within a phase is
undefined.
-Stephen
On 6 July 2010 21:47, asookazian asookaz...@gmail.com wrote:
Does the plugin goal below get executed before or after the completion of
the
install phase when I exec 'mvn clean install' command?
AFAIK it's the order they are defined in in the pom. This would depend on
the version of Maven though, as it has not always been like that.
/Anders
On Wed, Jul 7, 2010 at 08:08, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
The rule for Maven is that the order of plugin execution
You could move to something like this:
1. Have Hudson execute build when cvs is updated
2. Replace your ant build with maven.
3. If all tests pass, have Hudson invoke 'mvn deploy' to deploy your build
artefacts to a central nexus repository.
4. Setup a Hudson job to invoke maven builds
Am Mittwoch, 7. Juli 2010 01:19:16 schrieb asookazian:
[...]
This is one area where Ant is much more flexible than Maven (or at least
it's easier to customize invocations of targets in Ant than it is with
goals in Maven's lifecycle phases)...
Why don't you stick with Ant then?
From your
AFAIK, the order only applies for plugins in the main build section, not
plugins introduced via a profile, and the ordering is just a side effect.
The recommendation is not to rely on the order within a phase, if something
should run prior to something else, bind it to an earlier phase
-Stephen
Regarding plugins bound in a profile I believe you're right. I had the main
build section in mind.
/Anders
On Wed, Jul 7, 2010 at 09:40, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
AFAIK, the order only applies for plugins in the main build section, not
plugins introduced via a
I have a problem while performing a mvn release:prepare task when the project
is downloaded from CVS, because the files are read only (so pom.xml can't be
updated with new version).
Error writing POM: C:\Documents and
Settings\a.dionisi\Desktop\PLX\Source\AuditingWebService\pom.xml (Access is
Hi All,
I represent Packt Publishing, the publishers of computer related books.
We are planning to extend our range of Open Source books based on Java
technology and are currently inviting authors interested in writing them. This
doesn't require any past writing experience. All that we
Would anyone be interested in teaming up on something like this? Have thought
about pitching a maven book before but don't have the cycles to go it alone
Sent from my iPhone
On 7 Jul 2010, at 09:54, Kshipra Singh kship...@packtpub.com wrote:
Hi All,
I represent Packt Publishing, the
Hey,
I'm already working on a Cookbook for Maven 3 with Packt and am eager to
collaborate with the community to create a better book. If anybody is
interested, please get in touch with me.
Thanks,
Sri
On Wed, Jul 7, 2010 at 2:49 PM, Benjamin Wootton
benjaminwoot...@loyaltyspace.com wrote:
Hi Srirangan
I would be very interested in this - have been considering a maven 3 title and
the cookbook style works well. I'm currently converting a huge maven 2 project
to version 3 focusing on tests, intrgration tests, meter, static analysis.
Where are you up to with your book and any areas
On 07/07/2010 2:07 AM, Stephen Connolly wrote:
write your own assembly descriptor.
you can do exactly what you are after (i.e. copy all the war artifacts to
ABC, copy all the jar artifacts to XYZ and wrap the whole thing up in a
tar.gz file
How do I specify that those files are in Nexus?
On 07/07/2010 2:52 AM, Martin Höller wrote:
Am Mittwoch, 7. Juli 2010 01:19:16 schrieb asookazian:
[...]
This is one area where Ant is much more flexible than Maven (or at least
it's easier to customize invocations of targets in Ant than it is with
goals in Maven's lifecycle phases)...
On 07/07/2010 5:19 AM, Benjamin Wootton wrote:
Would anyone be interested in teaming up on something like this? Have thought
about pitching a maven book before but don't have the cycles to go it alone
There is a desperate need for a Best Practice book.
You see all kinds of strange
Hello All
I have project which i want build with 2 different pom.xml . one after the
other
I have tried the mvn command line option like *mvn -f ./pom1.xml
install -e*which works fine.
Actually i have multi level projects which have build using continuum.
Is there any way i specify in my parent
Hey Ben,
I have yet to start with the book. I've only just finalized the outline and
schedule with the publisher and signed the contract. I will begin working on
it full-time couple of weeks from now as I find a way to ease myself out of
my current project.
Your experience of migrating to Maven
Hi Ron!
Am Mittwoch, 7. Juli 2010 14:00:22 schrieb Ron Wheeler:
On 07/07/2010 5:19 AM, Benjamin Wootton wrote:
Would anyone be interested in teaming up on something like this? Have
thought about pitching a maven book before but don't have the cycles to
go it alone
There is a
Hello.
It's not clear why do you want to use two different poms,
but I can suggest, you have two different build cycle.
For example one for build on local machine, second for you continuum.
But in this case, the better solution is to use maven profiles. And you
will have possibility to choose
On 7/7/10 8:30 AM, govind ashrit wrote:
Hello All
I have project which i want build with 2 different pom.xml . one after the
other
Don't do this. Figure out how to use profiles or split the project.
-
To unsubscribe,
On Wed, Jul 7, 2010 at 7:00 AM, Ron Wheeler
rwhee...@artifact-software.com wrote:
On 07/07/2010 5:19 AM, Benjamin Wootton wrote:
Would anyone be interested in teaming up on something like this? Have
thought about pitching a maven book before but don't have the cycles to go
it alone
I would like to unsubscribe from the Maven Book Writer's List without leaving
the Maven Users List.
Is this possible?
!-- Frank Gorham-Engard →
Be kinder than necessary.
Everyone you work here with is fighting some kind of battle.
-Original Message-
From: Andrew Close
On Wed, Jul 7, 2010 at 7:12 PM, Gorham-Engard, Frank
frank_gorham-eng...@cable.comcast.com wrote:
I would like to unsubscribe from the Maven Book Writer's List without
leaving the Maven Users List.
Is this possible?
LOL.. Sorry for my share of spam.. :-P
On 07/07/2010 8:55 AM, Martin Höller wrote:
Hi Ron!
Am Mittwoch, 7. Juli 2010 14:00:22 schrieb Ron Wheeler:
On 07/07/2010 5:19 AM, Benjamin Wootton wrote:
Would anyone be interested in teaming up on something like this? Have
thought about pitching a maven book before but don't have
On 07/07/2010 9:42 AM, Gorham-Engard, Frank wrote:
I would like to unsubscribe from the Maven Book Writer's List without leaving the
Maven Users List.
Is this possible?
No but you could add a filter to remove posts that include book in the
subject and that would remove some of the topics
Martin Höller wrote:
Am Mittwoch, 7. Juli 2010 01:19:16 schrieb asookazian:
[...]
This is one area where Ant is much more flexible than Maven (or at least
it's easier to customize invocations of targets in Ant than it is with
goals in Maven's lifecycle phases)...
Why don't you stick
When you don't specify the version of a plugin, Maven should download the
latest version. However, very often the version is defined through a
pluginManagement section. This could be either in your pom hierarchy or in
Maven's super-POM. In your case, the version of the antrun-plugin is defined
1) I *must* use Maven for work project. And currently we're stuck with
2.0.8 (we have no in-house Maven experts to help us upgrade to 2.2.x or
Since you're the one posting here, are you not the in-house expert?
If not, why aren't you asking these questions of your experts and
then they can ask
I don't know. If i recall correctly, the help:describe mojo by default works
on the latest version of the plugin being described, when I use it with
Maven-3.0-beta1. I could be wrong, but that's how I recall tings. So, I
always specify the version [1] when I use help:describe. That way I have
Hello,
Am Mittwoch, den 07.07.2010, 14:00 +0200 schrieb Ron Wheeler
A book on the subject will also have to touch on IDE integration, source
management, maven repositories, continuous integration and other
development areas.
I would like to see a book targeted at the 80% of developers
I'm used to using a jboss-log4j.xml with the JBoss AS app to control logging
to console and file appenders. Any answers? thx.
--
View this message in context:
http://maven.40175.n5.nabble.com/logging-level-in-Mojo-only-INFO-tp510999p1044783.html
Sent from the Maven - Users mailing list
Hi All,
I am doing maven release using maven release plugin and trying to get the
automated generated tag pom version using auto generated release.properties.
The file contains a key
project.rel.com.selfservice\:self-service=1.0.1
I use below variables to manipulate inside maven-antrun-plugin'
Anders Hammar wrote:
I don't know. If i recall correctly, the help:describe mojo by default
works
on the latest version of the plugin being described, when I use it with
Maven-3.0-beta1. I could be wrong, but that's how I recall tings. So, I
always specify the version [1] when I use
I wrote a review on the Packt Maven book:
http://books.dzone.com/reviews/apache-maven-2-effective
I am not a big fan of Packt books. I like O'Reilly and Manning mostly.
Anyways, it would be nice if this new best practices book also covered how
to create a custom lifecycle (and when, why,
So I just ran 'mvn archetype:generate' and it's not finding that goal. So I
download version 2.0-alpha5 from here:
http://mvnrepository.com/artifact/org.apache.maven.plugins/maven-archetype-plugin/2.0-alpha-5
by simply adding the following POM snippet in a pom.xml and running 'mvn
clean
I am actually trying to create a custom lifecycle right now... Not sure if I
need to use the forking that is covered here or not:
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-custom-lifecycle.html
--
View this message in context:
well, I answered one of my questions:
mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-5:generate
which worked.
So I'm using mvn 2.0.8, but I believe the algorithm it uses to select the
plugin version (when not explicitly specified) may be the same with 3.0...
--
View this
Ok so here is my initial attempt at overriding (or creating) a lifecycle. My
goal is to override the package phase (specifically the war:war with
war:explode). I followed the example here:
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-override-default-lifecycle.html
I already explained this. If the version is not defined/locked through
pluginManagement, Maven selects the latest version (by looking in the
maven-metadata.xml file in the repos, so if the metadat is incorrect, it
might not get the actual latest version). The pluginManagement section could
either
Ok, looks like it's working now.
components.xml:
component-set
components
component
roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role
role-hintexploded/role-hint
implementation
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping
If you want something that's app-server generic, take a look at the cargo
project.
http://cargo.codehaus.org/
/Anders
On Wed, Jul 7, 2010 at 00:37, asookazian asookaz...@gmail.com wrote:
what about weblogic, websphere, glassfish, etc.? i don't agree...
--
View this message in context:
Getting closer. Now using war:exploded (see below). So in order to wrap
this up (for an exploded EAR), there are a few steps required. The mojo for
the maven-ear-plugin (which doesn't have an exploded goal!) needs to be
modified to add the exploded goal. Then the exploded WAR needs to be
Anders Hammar wrote:
I already explained this. If the version is not defined/locked through
pluginManagement, Maven selects the latest version (by looking in the
maven-metadata.xml file in the repos, so if the metadat is incorrect, it
might not get the actual latest version). The
1) the super-POM still applies.
2) Right. There is one for each repo. Maven will merge these, but also check
the remote repos. Don't bother with this, I just mentioned it as there could
be cases where Maven isn't pulling the latest due to incorrect meta data.
/Anders
On Wed, Jul 7, 2010 at
Well after some extensive experimentation with creating a custom lifecycle,
it appears as though using war:explode in components.xml with
packagingwar/packaging in the POM may not be possible.
When I use packagingexploded/packaging, it works ok. But I don't think
this is feasible to use for a
1) It's possible to exec 'mvn archetype:generate' in a directory that does
not have a pom.xml in it (I just did this). In this case, the
If you care about what version of a plugin is being used, you MUST
specify it explicitly. Otherwise you must be willing to accept
non-deterministic results.
Well after some extensive experimentation with creating a custom lifecycle,
it appears as though using war:explode in components.xml with
packagingwar/packaging in the POM may not be possible.
As I understand it, this is correct because Maven already has a
pre-defined lifecycle for projects of
I have a multi--module configuration. the directory structure is:
aggregate
ejb
war
The war file includes the ejb as a dependency. When I do a
release:prepare -DdryRun maven generates the pom.xml.tag correctly but
it doesn't update the sub module dependencies in the pom.xml.next. How
do I get
I've only just started experimenting with the book generation capabilities of
the doxia maven plugin.
I am trying to figure out how to modify the look of the generated PDF.
I haven't found that one nugget of information to help me.
I've tried creating a site/resource/site.css file (per some
Hi guys,
I'm using maven-deploy-plugin:deploy-file to upload an artifact to my Nexus
repository.
The upload process works fine but the metadata is not regenerated.
So when I download the artifact I get a Checksum Failed error.
Regenerating metadata via Nexus fix the problem. (of course I don't
The Mojo team is pleased to announce the release of the JBoss Maven
Plugin version 1.4.1.
http://mojo.codehaus.org/jboss-maven-plugin/
This release includes bug fixes and minor enhancements, specifically
related to the way the plugin starts and stops a JBoss server.
To get this update, simply
This is a known issue with Maven 2.2.0.
Upgrading to 2.2.1 will fix this.
Rich
On Jul 7, 2010, at 12:21 PM, Victor Calvello wrote:
Hi guys,
I'm using maven-deploy-plugin:deploy-file to upload an artifact to my Nexus
repository.
The upload process works fine but the metadata is not
Quick question: I noticed that webResources section to include something in
a war via parent pom fails to execute. The webResources section is omitted
during execution. Copying the same section to a the actual pom war works
just fine. Is it by design or a bug?
More often than not I have to
53 matches
Mail list logo
