Not by hand from the command line afaik. The eclipse plugin will try to
download both if available when you run eclipse:eclipse.
mike
Patrick Moore [EMAIL PROTECTED] wrote on 08/21/2006 12:46:56 PM:
Hi there -
It looks like there is no way with maven2 to get the generated javadoc
jar or
Reboot?
The only time I see rogue maven processes is when our unit tests fork and I
kill the main maven process. The child unit test maven instance continues
to run until the unit tests are complete.
mike
Jeff Mutonho [EMAIL PROTECTED] wrote on 08/17/2006 12:24:30 PM:
kill -9 PID is not
Could you tell us what you want this plugin to do?
javed mandary [EMAIL PROTECTED] wrote on 08/16/2006 07:14:53 AM:
Am going to be working with Websphere 6 Seems there are no plugins for
it.
Anyone had experience working with M2 and Websphere 6?
cheers and thanks,
Javed
On
authorized_keys is the only way I know to do this easily. Look into the
webdav wagon. That might allow you to use your LDAP auth for HTTP PUTs and
GETs to/from the repo so you don't have to go through any Unix security
hurdles.
[EMAIL PROTECTED] wrote on 08/16/2006 12:36:45 PM:
I'm not a
Runtime - contains things that you don't need at compile but you do need
for your app to actually run. You might compile against JMS but require
ActiveMQ at runtime (i.e. a JMS engine).
Test - contains test specific classes. Junit, mocks, a lightweight
database like HSQLDB, etc.
[EMAIL
Prashanth, the Perforce checkout does not use the -f (force) sync flag. If
you delete files by hand, it will not pull them down again. You have three
choices:
1) Don't do this. You shouldn't be mucking about directly on your build
server. It's a bad idea in general.
2) Force a sync by
I like it and I think that's a reasonable request. Throw it in JIRA and
maybe Santa will deliver it in 2.1. :-)
mike
[EMAIL PROTECTED] wrote on 08/09/2006 11:37:39 PM:
It could define the version conflict resolution rules such that
dependencyManagement version declarations in *my* POMs
[EMAIL PROTECTED] wrote on 08/10/2006 12:28:36 AM:
If I understand your recommendation correctly, you would like me to
declare
my dependency on version [1.7.0,) instead (meaning version 1.7.0 or
any
later version). From a QE perspective, that is an untestable assertion
--
there is no
Well, I added my vote and +1 to the issue. That's about all I can do since
I shy away from touching the maven core.
mike
Jörg Schaible [EMAIL PROTECTED] wrote on 08/10/2006
08:42:40 AM:
This *is* what MNG-1577 is about and it has been postponed since 2.0.1.
:-/
We have come up with a pattern that we feel works pretty well to work
around this. We split our modules into standard jars and j2ee type
archives. The standard jars declare their own deps as normal. The j2ee
jars all share a parent which overrides all dependency versions so all the
Not exactly. We have a single parent POM per ear and don't share war/ejbs
between ears, yes. But you can still do what you want with a
dependencyManagement section in the parent to centralize the version
numbers and just have each ear POM pull in its required ejbs. Or am I
missing
Again, this is because dependency B is not using version ranges but rather
forcing a specific version on its downstream dependents.
If A requires a different version, it has to declare that dependency in
order to override the transitive dependency version from B. There's
nothing Maven can do
You might be running into MASSEBLY-99. Try version 2.0.1 and see if the
depSet works then.
mike
mike7 [EMAIL PROTECTED] wrote on 08/08/2006 03:24:22 PM:
I tried with the dependencySet as follows:
Well, it doesn't produce anything in the jar. If I use moduleSets then it
works but it
No, JARs are the standard way to share code. You can't share code in a
WAR or EAR. Move the common code into a JAR module.
-Original Message-
From: Martin Goldhahn [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 10:43 AM
To: users@maven.apache.org
Subject: WAR dependency in a WAR
mvn --help?
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of jan_bar
Sent: Monday, July 31, 2006 2:10 PM
To: users@maven.apache.org
Subject: Maven2 command line reference
Hi,
I searched maven site and even used Google, but I cannot find any
documentation about maven
Maven has no standard goals. _Everything_ is a plugin.
-Original Message-
From: Alex Turner [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 30, 2006 5:54 PM
To: Maven Users List
Subject: Re: Including dependencies in final JAR
Not to ask a stupid question, but why should I have to use a
in final JAR
ok - but there are standard plugins (I assume defined in the super pom),
and
plugins that have to be detailed in the project's pom.xml. This is
functionality that really should be in a standard plugin
Alex
On 7/30/06, Mike Perham [EMAIL PROTECTED] wrote:
Maven has no standard
Use the -X to enable Maven debugging. The p4 commands are emitted
before they are executed.
-Original Message-
From: Prashanth Krishnamurthy [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 12:22 PM
To: continuum-users@maven.apache.org
Subject: Perforce-continuum related issues
No.
-Original Message-
From: German de la Cruz [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 6:09 PM
To: Maven Users List
Subject: Packaging EE applications (Real problem)
Is there a better solution???
-
Why? Removing version info is very dangerous. You then have no idea
which version was actually selected by Maven by looking in the artifact
after the fact.
-Original Message-
From: LaCasse, John [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 25, 2006 12:57 PM
To: Maven Users List
Maven must use it's own naming scheme within the repo, that's why it
only affects packaging. Note you can change the names of jars/wars
within an ear so that the module URI in the application.xml does not
need to change with every version increment.
As Chris mentioned, the best way is to add a
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 25, 2006 4:40 PM
To: Maven Users List
Subject: RE: deploying jars without version information
Isn't that what MANIFEST.MF files are for?
| -Original Message-
| From: Mike Perham [mailto:[EMAIL PROTECTED]
| Sent: Tuesday, July 25, 2006 2:23 PM
We are using this exact version of jboss with ears with about 50-60 jars
and don't have to do this. The jars are in a lib/ directory inside the
ear and we have 2-3 wars in the root of the EAR. The wars all have
manifest.mfs with Class-Path entries that reference the jars like this.
Class-Path:
Do you have a pre-existing MANIFEST.MF in your webapp source? The first
example doesn't look like it was generated by Maven 2; you should see a
Plexus Archiver entry. If you remove the custom manifest entry, does
the Class-Path entry appear?
-Original Message-
From: David J. M. Karlsen
The book was probably written against pmd-plugin 2.0 or earlier. We've
upgraded the PMD version several times since then and they add new rules
to our default rulesets all the time. In other words, you might not
have done anything wrong and still see errors due to new rules being
triggered.
Is it JavaSource or JavaSources? You use both below.
-Original Message-
From: Jeff Mutonho [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 7:18 AM
To: Maven Users List
Subject: basedir JavaSource does not exist
m2 is spitting out the error message basedir JavaSource does not
Certainly looks that way. It looks like a Maven SCM bug. What SCM
system are you using?
-Original Message-
From: Ciprian Duma [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 5:21 AM
To: Maven Users List
Subject: prepare:release failure for flat layout project structure
Hi,
I
Try using warSourceExcludes in the war config.
-Original Message-
From: Jeff Mutonho [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 11:45 AM
To: Maven Users List
Subject: Excluding java files in war
My war file is being created with the source files (i.e java files)
in it.I
Report aggregation is hit and miss currently. Javadoc, javancss and
clover for instance have home-grown aggregation support but there is no
standard way to do it. For most reporting plugins, the answer is no.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent:
release:perform just uses the scm:checkout command. There's no
scm:export command.
-Original Message-
From: Mark Hewett [mailto:[EMAIL PROTECTED]
Sent: Monday, July 17, 2006 2:10 PM
To: Maven Users
Subject: [m2] release:perform checkout vs. export (with Subversion)
When doing a
The maven version has nothing to do with it.
It's broken in maven-war-plugin 2.0 and fixed in 2.0.1.
-Original Message-
From: Lukasz Szelag [mailto:[EMAIL PROTECTED]
Sent: Friday, July 14, 2006 9:44 AM
To: users@maven.apache.org
Subject: Re: WEB-INF/lib excludes once more
WAR plugin
The plugin does not come with Maven. Maven downloads the latest
version when you first need it. If you were to install 2.0.4 today, it
would download 2.0.1.
No. It would be a nice feature in the EAR plugin, IMO.
-Original Message-
From: Lukasz Szelag [mailto:[EMAIL PROTECTED]
Sent:
This is not possible with the latest install plugin release. It has been fixed
in SVN but not released yet.
-Original Message-
From: Ingo Düppe [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 13, 2006 10:04 AM
To: Maven Users List
Subject: Re: installing source jar with install plugin
We use wget to mirror specific versions of dependencies from central.
It's a terrible solution and doesn't work with dependency version ranges
(because the maven-metadata.xml files are wrong) but it works ok when
your versions are locked down.
wget -nd -r -l 1 dir
If someone has a better
'mvn compile' is what you want. 'mvn clean install' is what I use 90% of the
time.
-Original Message-
From: ThE-cLoN NoLc-EhT [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 6:24 AM
To: users@maven.apache.org
Subject: Problems con maven-plugin-java
i need help, i newbie in
Change the plugin so that it does nothing when the current project uses
pom and/or maven-plugin packaging? You have a circular dependency here
- there's no solution other than breaking the cycle. You need to have a
master POM which is not tracked via this plugin.
-Original Message-
This release upgrades the plugin to use PMD 3.7 and adds a few minor new
features. Users should also find that PMD can no longer crash the Maven
site generation due to PMD bugs.
You can get more details with the Change Log report in JIRA:
settings.xml can only exist in two places AFAIK. ~/.m2/settings.xml and
MAVEN_HOME/conf/settings.xml. The latter can be used to configure all
users on the machine and is thoroughly commented.
-Original Message-
From: Tung Nguyen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 11, 2006
They coorespond to svn commands. See any svn book or manual.
-Original Message-
From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 3:09 AM
To: Maven Users List
Subject: RE: maven-scm-plugin goals question
Emmanuel,
It would be helpful, if it is possible to
The clover and cobertura plugins add a dependency programmatically to a
project. Check out their source.
-Original Message-
From: Wendell Beckwith [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 6:23 PM
To: users@maven.apache.org
Subject: Is it possible for a mojo to dynamically
You are using excludes incorrectly.
plugin
artifactIdmaven-war-plugin/artifactId
configuration
warSourceExcludesWEB-INF/lib/*.jar/warSourceExcludes
archive
manifest
addClasspathtrue/addClasspath
Not true.
-Original Message-
From: Pete Marvin King [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 09, 2006 11:52 AM
To: Maven Users List
Subject: Re: WEB-INF/lib excludes once more
if you want to exclude certain dependencies from the war, just specify
the scope as compile. only
It gives you an empty report if you have no code which triggers the
default PMD rules.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 2:00 AM
To: users@maven.apache.org
Cc: [EMAIL PROTECTED]
Subject: RE: maven-pmd-plugin can't
Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: donderdag 6 juli 2006 17:31
To: Maven Users List
Subject: RE: [M2] maven-war-plugin 2.0.1
You mean WEB-INF/lib has no jars in it? Please post the
relevant parts
of your POM.
-Original Message-
From: [EMAIL
It sounds like you are trying to use a ruleset from an older version and
the PMD code is no longer there to support the old rule(s). Try
removing the rulesets and I bet it will work fine.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 05,
Your question makes no sense. Could you be more specific?
-Original Message-
From: David McGee [mailto:[EMAIL PROTECTED]
Sent: Monday, July 03, 2006 11:22 AM
To: users@maven.apache.org
Subject: Maven Plugin for RAD6
Is there a version of the Maven Plugin that works running RAD
.
Basically just put your label in there and it should work fine.
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, June 30, 2006 10:09 AM
To: continuum-users@maven.apache.org
Cc: Mike Perham
Subject: Re: How to have project pull specific label from SCM
Graham, you would just list the updated logger 1.0.1 dependency in your
own POM. Maven will prefer that because it is closer and override 1.0
in Sally's POM.
-Original Message-
From: Graham Lea [mailto:[EMAIL PROTECTED]
Sent: Friday, June 30, 2006 6:27 PM
To: users@maven.apache.org
the associated bugs
and looking at some source code (though I don't know where in
the source
tree the archiver has moved to), but I didn't figure out the
switch to
turn on automatic entries or how to specify my own values.
-- Mark R
Mike Perham wrote:
Mark, there is a flag which you can
Mark, are you familiar with the buildpluginManagement section? If
you are just trying to configure your plugin but will execute it by hand
via command-line, you want to use pluginManagement, not plugins.
-Original Message-
From: Russell, Mark [mailto:[EMAIL PROTECTED]
Sent:
Mark, there is a flag which you can specify to enable the old manifest
default values. I'm not positive on the exact syntax so you'll need to
do some legwork to find this. I think the plan was to document all this
in the jar plugin but I guess the war plugin snuck out first without
full
Akbarr, you might want to watch this issue.
http://jira.codehaus.org/browse/MRELEASE-134
-Original Message-
From: Akbarr [mailto:[EMAIL PROTECTED]
Sent: Thu 6/22/2006 12:22 PM
To: Maven Users List
Subject: M2: Using version ranges in dependencies
Hi all,
I have a doubt with
If you are generating them, why are you considering them source in the
first place? Why not just generate them straight into
target/artifactId-version? That's where everything is copied to so
it can be jarred into a war.
-Original Message-
From: Alexandre Poitras [mailto:[EMAIL
Mark, I can't confirm an exact date but I just went through JIRA last
night and closed/resolved 10-15 of the existing issues. The one thing
that has not been done yet is an overhaul of the documentation to
conform with the new doc standards. Once this has been done, the
release should be
Geoffrey, read this:
http://mojo.codehaus.org/javancss-maven-plugin/howto.html
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey De Smet
Sent: Friday, June 23, 2006 8:32 AM
To: users@maven.apache.org
Subject: Re: [ANN] Maven2 javancss plugin 2.0-beta-1
Andrew, FWIW, we've given up using Clover in an automated fashion for
now. It conflicts with too many other plugins in unexpected ways. We
just run 'mvn clover:instrument clover:clover' during development to
determine coverage needs.
-Original Message-
From: [EMAIL PROTECTED]
Thanks John. I just added site documentation based on this example.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, June 23, 2006 11:51 AM
To: Maven Users List
Subject: Re: Deleting additional directories during clean
This is not to short circuit the
Yep, I just ran into this also. I have a module which has [1.1.0,) and
1.1.0 and 1.1.1-SNAPSHOT in my local repo. I can't release the module.
It basically makes dependency ranges unusable for us. I'm unclear who's
at fault here (the release plugin, maven's dependency resolution
alogrithm, etc)
I'm trying to use version ranges in my POMs as described in chapter 3.6
of BBWM.
No versions are present in the repository for the artifact with a range
[3.1.3,3.2)
org.hibernate:hibernate:jar:null
I built my repository by hand and it does not contain many of the
maven-metadata.xml files which
Does Maven support dependency version ranging? I don't want to use the
traditional closest version declaration wins but want to use version
requirement ranges so I can say this:
A:
dependency
artifactIdfoo/artifactId
version[2.3.1,)/version
/dependency
B:
dependency
artifactIdfoo/artifactId
We just output to target/classes:
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
execution
phasetest-compile/phase
goals
We use Websphere Rapid Deploy. Just copy the generated EAR to the
Websphere Rapid Deploy directory. Works on both development machines
and automated test machines.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 4:05 AM
To:
@maven.apache.org
Subject: RE: IBM WAS 6 M2 plugin
Thanks Mike. How do you get around bindingfile generation ? Do you
generate at deploy time automatically (wsi files, etc) ?
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: 16 June 2006 14:48
To: Maven
See the maven-antrun-plugin docs.
-Original Message-
From: cristal [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 12:35 PM
To: users@maven.apache.org
Subject: calling ant build.xml directly
Hi guys, this might be a stupid question, but...
Can I simply call an existing
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 7:44 AM
To: users@maven.apache.org
Subject: common jars between modules in EAR
I declared in ear's pom:
* the webModule simple_war and
* the javaModule common_jar
They are also
correct. But the jar library
is included
into the war file...
I tried also: dependentWarExcludes*.jar/dependentWarExcludes
What is wrong ?
Andre
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto
The perforce provider does not handle passwords; it is assumed that you
are already logged in. We have a special build user who is only allowed
to log in from the build server and whose login never expires.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent:
the users password from an environment variable?
Mike, did you try that before you left this person logged in?
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 12:12 PM
To: Maven Users List
Subject: RE: integration builds and version
that before you left this person logged in?
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 12:12 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
The perforce provider does not handle passwords
?
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 4:31 PM
To: Maven Users List
Subject: RE: integration builds and version numbers
You need something like this in your POM.
scm
connectionscm:perforce://depot/modules/fabric
-Original Message-
In this case, we have something like this:
//depot/up-svcs-test/rel/R1.0/pom.xml --- parent
//depot/up-svcs-test/rel/R1.0/A/pom.xml
//depot/up-svcs-test/rel/R1.0/B/pom.xml --- children
//depot/up-svcs-test/rel/R1.0/C/pom.xml
Without putting
Have you tried looking for open or recently closed bugs in JIRA?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lee Meador
Sent: Wednesday, June 14, 2006 5:27 PM
To: Maven Users List
Subject: Re: antrun classpaths
Does anyone have any ideas on
It's been voted on but I was waiting for Jean-Laurent to get committer
privileges so he could do the release. I'll let him comment on his expected
timeframe for the release.
-Original Message-
From: Stefan Hübner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 10:31 AM
To:
Any jar can be uploaded to ibiblio, you just need to create an upload
bundle for it and enter a MAVENUPLOAD issue.
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
http://jira.codehaus.org/browse/MAVENUPLOAD
-Original Message-
From: Steve Lewis [mailto:[EMAIL PROTECTED]
Users List'
Subject: RE : multi-module build overriding dependency versions
Hi,
Mike, it's certainly the main reason why (IMHO)
http://jira.codehaus.org/browse/MRELEASE-91 can be considered as a bug
;-)
WDYT ?
--
Olivier
-Message d'origine-
De : Mike Perham [mailto:[EMAIL PROTECTED
FYI the issue is MNG-1245 and I have developed a patch for it if anyone else if
having this problem.
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Friday, June 09, 2006 8:42 AM
To: Maven Users List
Subject: RE: RE : multi-module build overriding dependency
I have a set of modules:
root/
a/
b/
Both modules are at version 1.1.2-SNAPSHOT and B depends on version
1.1.1 of A.
When I run the root build, it builds A and B and version 1.1.2-SNAPSHOT
of A is forced upon B. This is a massive problem for us as it means we
can't do independent
beneath to build.
-Original Message-
From: Henry S. Isidro [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 08, 2006 7:18 PM
To: Maven Users List
Subject: Re: multi-module build overriding dependency versions
On Friday, June 9, 2006 07:36, Mike Perham wrote:
I have a set of modules:
root
We use an exclude rule for WEB-INF/lib/*.jar and a custom version of the
war plugin with MWAR-39 fixed.
-Original Message-
From: Arthur Crawford [mailto:art[EMAIL PROTECTED]
Sent: Wednesday, June 07, 2006 3:02 AM
To: users@maven.apache.org
Subject: [m2] war plugin - need dependencies
Containers usually have their own logging configuration. WebSphere has
a config page in their admin console. Jboss has a log4j.xml
configuration file. Check the docs.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
ben short
Sent: Wednesday, June 07,
release.
Regards,
Arthur.
Mike Perham wrote:
We use an exclude rule for WEB-INF/lib/*.jar and a custom version of
the war plugin with MWAR-39 fixed.
-Original Message-
From: Arthur Crawford [mailto:art[EMAIL PROTECTED]
Sent: Wednesday, June 07, 2006 3:02 AM
To: users@maven.apache.org
I don't use Continuum so I can't answer this.
-Original Message-
From: Bob Arnott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 06, 2006 4:10 AM
To: continuum-users@maven.apache.org
Subject: Re: Perforce and Client Specs
Mike Perham wrote:
-Dmaven.scm.perforce.clientspec.name=yourspec
What about it? It should be the exact same command.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 06, 2006 8:16 AM
To: Maven Users List
Subject: RE: Maven2 SCM plugin
How about perforce?
-Original Message-
From: dan tran [mailto:[EMAIL
This has been a point of debate. On one hand, it makes releasing a set
of modules together easier. On the other hand, it forces a new version
on your module even though you have no reason to require the new version
yet.
-Original Message-
From: LECAN Damien [mailto:[EMAIL PROTECTED]
-Dmaven.scm.perforce.clientspec.name=yourspec
This property will override the Perforce SCM driver's generated
clientspec name.
-Original Message-
From: Bob Arnott [mailto:[EMAIL PROTECTED]
Sent: Monday, June 05, 2006 12:07 PM
To: continuum-users@maven.apache.org
Subject: Perforce and
You would use 'mvn package' and bind the assembly:assembly mojo to the
'package' build lifecycle phase in your pom. I could swear I've seen an
example on the list before but I don't have an convienent example.
-Original Message-
From: hamdard [mailto:[EMAIL PROTECTED]
Sent: Monday, June
-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Monday, June 05, 2006 3:45 PM
To: Maven Users List
Subject: RE: [M2] can we use 'mvn assembly' instead assembly:assembly
You would use 'mvn package' and bind the assembly:assembly mojo to the
'package' build lifecycle phase in your pom. I
war:manifest will generate a standalone MANIFEST.MF in
warSourceDirectory/META-INF. Despite the war association it does not
require a war project; you can use it anywhere (for ejb/mdb projects for
instance). Example:
plugin
This is a PMD bug and has nothing to do with Maven. You can turn off
the UselessOverridingMethod rule (see PMD docs) or turn off the entire
PMD report for your particular module like this:
reporting
plugins
plugin
We are using JAVA_HOME to point to the VM to use to invoke Maven. This
is fully supported by mvn and mvn.bat. But surefire appears to fork the
VM that is in your PATH. So we are seeing instances where one type of
VM is used to start Maven but another is used to run the tests.
Shouldn't the
. Maybe you could open a
jira issue for it.
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 1:28 PM
To: Maven Users List
to
use, I had to use it work around the problem. Maybe you could open a
jira issue for it.
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Original Message-
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent
You're on the right track here.
1. http://jira.codehaus.org/browse/MWAR-39 Fixed but not released yet.
You can use the older version of the WAR plugin but that version does
not contain the war:manifest goal which will autogenerate
WebContent/META-INF/MANIFEST.MF for you.
2. I don't know of an
descriptor but just inherits it from the root?
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 12:08 PM
To: Maven Users List
Subject: Re: site child module listing
On Wed, 31 May 2006, Mike Perham wrote:
you're not running 'mvn -N site' by any
Nope. Feel free to enter a JIRA issue. I hit that bug myself
yesterday. In the meantime, 'p4 label -d foo' will workaround the
problem.
-Original Message-
From: Smythe, Steve [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 31, 2006 1:31 PM
To: 'continuum-users@maven.apache.org'
Cc:
[WARNING] repository metadata for: 'org.apache.maven.plugins' could not
be retrieved from repository: central due to an error: Error
transferring file
Sounds like a transient network problem. Try again.
-Original Message-
From: Vikramm [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May
I have a SNAPSHOT of the war plugin that I built and deployed to fix a
blocker for us that has not been released. In my POM, I refer to it
like this:
build
plugins
plugin
artifactIdmaven-war-plugin/artifactId
version2.0.1-20060525.222101-1/version
I did
I built our shared repo based on my local repo. You just need to rename
the maven-metadata-central.xml files to maven-metadata.xml I think. The
command 'wget -nd -r -l 1 URL' is also very handy to scrape a
directory from central.
We will probably use maven-proxy next time.
-Original
Are the hbm.xmls being copied to target/classes or target/test-classes?
We generate our hbm.xmls to ${project.build.outputDirectory} and it
works fine.
hibernatedoclet destdir=${project.build.outputDirectory}
excludedtags=@version,@author,@todo,@see,@desc verbose=true
fileset
We put the explicit version for each plugin in our top-level POM and
update them by hand as we need new features. A deterministic build
process should never use -U.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lee Meador
Sent: Wednesday, May 24, 2006
1 - 100 of 246 matches
Mail list logo
