Thanks Brett!
It turns out that the jalopy plug-in does support multi-module projects ...
http://mojo.codehaus.org/jalopy-maven-plugin/examples/multimodule.html
Sorry for not looking at the docs a bit closer before firing off
questions on the mailing
list. But thanks anyway for drawing my
Hi Dennis,
I tried commenting out not only the Clover plugin but all the reporting
plugins and I get a fundamentally different behavior than in your setup ...
I still get at least the doxia versions alpha 7 and 10 pulled on top of 11.
Did you use the build script? Or otherwise what exact command
Thanks for your help Brett.
Hm, yes the metadata looks outdated. I am wondering why though. Is there any
setting that could prevent this metadata from being updated? What is weird
to me is that it is apparently possible that a new version of the plugin is
being installed without its metadata
Hi,
I am successfully using the Assembly Plugin to create an archive containing
extra content for a release.
However, now I would like to create another archive containing this archive,
plus the generated war file, plus a readme file for the client.
Any idea how that can be done?
Thanks in
run multiple assembly executions, use maven-dependency-plugin to
prepare staging area as needed.
-D
On Thu, Aug 28, 2008 at 3:58 AM, Peter Horlock
[EMAIL PROTECTED] wrote:
Hi,
I am successfully using the Assembly Plugin to create an archive containing
extra content for a release.
However,
Hi Dan, thanks for your fast reply.
However - could you please a bit more specific of how this can be done?
E.g.
a) Where can I add the multiple assembly executions - in the pom or in the
assembly descriptor?
b) what''s a staging area?
Thanks,
Peter
you can create multiple assembly descriptors.
The first one puts the output under a staging area like 'target/staging'.
you can copy more files into that staging area using antrun, dependency plugins
Your second assembly descriptor then work off the staging area.
You will need to run
ChrisGWarp wrote:
Haikal Saadh-2 wrote:
Yup, it's simple. It's one of those things that took me a while to
figure out as well.
servers
server
idsvn.warpspeed.com.au/id
usernameusername/username
Has anyone worked on it.
Where can I get a sample build file for the same and start.
Regards
DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the
property of Persistent Systems Ltd. It is intended only for the use of the
individual or entity
Unfortunately, 2.5 doesn't work for me.
Eventhough I can find it when I manually browse the Central Repo,
my Maven 2 version can't find it. I assume that someone forgot to update
those additional xml files telling with versions are hosted by the server. I
manually downloaded the javadoc 2.5 jar,
2008/8/28 Asif [EMAIL PROTECTED]
Has anyone worked on it.
Where can I get a sample build file for the same and start.
http://maven.apache.org/plugins/maven-war-plugin/usage.html
Regards
DISCLAIMER
==
This e-mail may contain privileged and confidential information which is
the
Hi Peter,
Verify that you defined the correct javadoc plugin version in your poms.
http://maven.apache.org/plugins/maven-javadoc-plugin/plugin-info.html
You could also run
mvn help:effective-pom
HTH
Cheers,
Vincent
2008/8/28 Peter Horlock [EMAIL PROTECTED]:
Unfortunately, 2.5 doesn't work
Hello Asif, you will have to start with the PDF tutorials. Use the Archetypes
to create a project that creates a (dot).jar. Then, you will have to add in
something like the following in your pom.xml:
packagingwar/packaging
Asif wrote ..
Has anyone worked on it.
Where can I get a sample
Hi All.
I have this error with release:perform. release:prepare, release:rollback
and release:clean all work fine.
This is the error (it cann't find what it wants - but why?)
D:\Hudson\jobs\FireDragon\workspace\trunk\FireDragonmvn release:perform
[INFO] Scanning for projects...
[INFO] Reactor
Chris Graham wrote:
Hi All.
I have this error with release:perform. release:prepare, release:rollback
and release:clean all work fine.
This is the error (it cann't find what it wants - but why?)
D:\Hudson\jobs\FireDragon\workspace\trunk\FireDragonmvn release:perform
[INFO] Scanning
Hi
2008/8/27 Giovanni Azua [EMAIL PROTECTED]:
Hi Dennis,
I swept my local repo first and then ran the build as you recommended using
the -X option.
These are all the doxia versions that end up being downloaded into my local
repo:
1.0-alpha-7
maven-reporting-api-2.0.5 uses doxia-api
Hi Chris,
Specifying the SCM section only in the parent pom should be sufficient. I've
been using this setup with the release plugin and it works like a charm.
-Guillaume
From: ChrisGWarp [mailto:[EMAIL PROTECTED]
Sent: Wed 27/08/2008 11:51 PM
To:
On Aug 27, 2008, at 8:34 PM, Brett Porter wrote:
Can you file this in JIRA under MNG if it isn't already?
http://jira.codehaus.org/browse/MNG-3733
Trevor
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Hi everybody,
Problem: how to inherit dependecies version from a parent
Scenario:
superpom.xml (the parent one)
--
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdit.trend/groupId
artifactIdsuperpom/artifactId
version1.0/version
Hi
in the frwpom.xml (the son)
just delete the line where u have dependencyManagement
and also /dependencyManagement
normaly that will be work
2008/8/28 Jo Support [EMAIL PROTECTED]
Hi everybody,
Problem: how to inherit dependecies version from a parent
Scenario:
superpom.xml
Are you running this build in hudson, or in some sort of modified maven
environment?
Ravi Luthra wrote:
I don't know what this means:
[WARNING]
WARNING
This Maven runtime contains a LifecycleExecutor component with an
incomplete configuration.
LifecycleExecutor
it worked, great! thanks a lot!
On Thu, Aug 28, 2008 at 4:10 PM, MedElb [EMAIL PROTECTED] wrote:
Hi
in the frwpom.xml (the son)
just delete the line where u have dependencyManagement
and also /dependencyManagement
normaly that will be work
2008/8/28 Jo Support [EMAIL PROTECTED]
-DperformRelease=true ... is it still around?
Marcelo Morales
On Wed, Aug 27, 2008 at 2:30 PM, raja72 [EMAIL PROTECTED] wrote:
Is there an option in Maven (mvn install or other commands) to include the
source files with the compiled classes in the target folder?
Thanks in advance,
Raja.
On Thu, Aug 28, 2008 at 3:43 AM, Asif [EMAIL PROTECTED] wrote:
Has anyone worked on it.
Where can I get a sample build file for the same and start.
mvn archetype:generate -DarchetypeArtifactId=maven-archetype-webapp
... and answer the prompts about group and artifact ids. It will
create a
Yes it was inside Hudson. I just tested in Netbeans using external Maven,
and the warnings are not there.
On Thu, Aug 28, 2008 at 7:37 AM, John Casey [EMAIL PROTECTED] wrote:
Are you running this build in hudson, or in some sort of modified maven
environment?
Ravi Luthra wrote:
I don't
Hi folks,
I'm interested in using gunit
(http://antlr.org/wiki/display/ANTLR3/gUnit+-+Grammar+Unit+Testing)
using the Surefire plugin, I already sent the same request to the
ANTLR mailing list but it seems nobody knows the solution...
Can anyone suggests me something? Thanks in advance!
Best
-DperformRelease=true option creating source and javadoc as seperate jar
files in the target directory.
I'm trying to compile an utility jar file with source code and add it the
local repository using maven.
Thanks,
raja.
Marcelo Morales-2 wrote:
-DperformRelease=true ... is it still
On Thu, Aug 28, 2008 at 9:47 AM, raja72 [EMAIL PROTECTED] wrote:
I'm trying to compile an utility jar file with source code and add it the
local repository using maven.
Try specifying your 'src' directory in resources so that it will get
copied into your jar.
If you have anything in
you should be able to use the exec-maven-plugin attached to the
generate-test-sources phase in order to generate the junit tests from
your grammar. then use build-helper to attach the generated test
sources so they will be compiled in the test-compile phase and then
surefire will pick them
add src/main/java/ as a resource folder with an includes of **.java
Sent from my iPod
On 28 Aug 2008, at 17:47, raja72 [EMAIL PROTECTED] wrote:
-DperformRelease=true option creating source and javadoc as seperate
jar
files in the target directory.
I'm trying to compile an utility jar
After adding src directory under resources, I'm able to see the source files
in the output jar.
Thanks for your help,
Raja.
Wendy Smoak-3 wrote:
On Thu, Aug 28, 2008 at 9:47 AM, raja72 [EMAIL PROTECTED] wrote:
I'm trying to compile an utility jar file with source code and add it the
Hi Stephen,
thank you very much for your hints!
Best regards,
Simone
2008/8/28 Stephen Connolly [EMAIL PROTECTED]:
you should be able to use the exec-maven-plugin attached to the
generate-test-sources phase in order to generate the junit tests from your
grammar. then use build-helper to attach
We have a number of projects that are built from a single POM file that
contains a much of modules. To build the project I just enter mvn goal
and whatever goal is specified is applied to each project.
However, the scm plugin does not seem to work this way. When I enter mvn
scm:update, only
On Mon, Aug 25, 2008 at 4:15 PM, John Casey [EMAIL PROTECTED] wrote:
Hi again,
One bug was identified in 2.0.10-RC10 last Friday night. This release
candidate addresses that issue. You can find it here:
Hello
We're using maven to create OSGi Bundles (using the felix plugins). We
also have a distribution project which has dependencies to an OSGi
container and to the various bundles that are part of the distribution
(without transitive dependencies).
One problem is, that the OSGi-container
Hudson is actually the use case for which I wrote that warning. The
problem is, the DefaultLifecycleExecutor component was modified in the
latest round of development, and now has a couple new component
dependencies, or requirements. Since Hudson extends this component
implementation directly
there is an update-subprojects goal that does what you want
Sent from my iPod
On 28 Aug 2008, at 19:20, W. Dave Rathnow [EMAIL PROTECTED]
wrote:
We have a number of projects that are built from a single POM file
that
contains a much of modules. To build the project I just enter
mvn
Guys,
I am facing this issue with the usage of maven release plugin and would
really appreciate some suggestions/feedback...
So i have this product/project heirarchy as below which i am trying to
release using the maven-release plugin but am getting this exception
BuildFailureException: The
Hello,
I am trying to convert an ant script into a maven build and I am having
trouble building my webapps folder.
My directory structure:
src
--main
--java
--resources
--webapp
target
--classes
--jars
webapps
--default
WEB-INF
lib
The ant script used to perform the
The metadata is probably not being updated because the project already
specifies the version and so there is no reason to consult the remote
repository for updated metadata. This is to be expected from Maven 2.0.9
onwards.
As for help:describe - sounds like a bug that should be filed as it is
The reason antrun is not running is you had phase = build, which is not a
valid phase.
Most of what you are doing here is not in line with the definition of the
elements. For example:
- resources are not for webapp resources, they are for classpath entries
- builds are intended to produce a single
Repositories elements seem to play different roles - either you are
retrieving from the repository, using the defined respository element in
settings.xml or you are deploying to a repository using the repository
element inside of distributionmanagement within the pom.xml. The way in
which this is
Check out the sample chapters attached to the book called
Maven-definitive-guide.
Check this link for all downloads and other references.
http://maven.apache.org/articles.html
-Original Message-
From: Asif [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2008 4:13 PM
To:
43 matches
Mail list logo