> Thanks for all the help. I commend the work you do Brett;
> not just in developing the plug-ins but also in how you
> acquit yourself to addressing countless questions on this
> list everyday -- politely and patiently. Keep up the good work.
It's a pleasure to do so for polite and patient
Right you are! Things work just fine with the official rc-2 release.
Sorry for having taken up the bandwidth.
Thanks for all the help. I commend the work you do Brett; not just in developing the
plug-ins but also in how you acquit yourself to addressing countless questions on this
list every
Thanks Brett.
I'll upgrade to RC2.
--- Brett Porter <[EMAIL PROTECTED]> wrote:
> This property was added after RC1, so you'll need to
> use RC2 to get it, or
> manually download and install this version.
>
> While it may work, this is not supported under Maven
> beta10. Please upgrade
> if pos
Ok, now it makes more sense. This bug existed on HEAD for some time - the
fix was only merged in Tuesday.
You might like to refer to the wiki or my earlier email today that details
the current CVS status.
Cheers,
Bret
> -Original Message-
> From: Sri Sankaran [mailto:[EMAIL PROTECTED]
>
I've been using rc2 for a while now (built Maven from CVS HEAD) and so haven't tried
it on rc1.
I will
a) try it on the official rc2 release
b) if (a) is not successful create a small project and try and recreate
the problem.
Sri
-Original Message-
From: Brett Porter [mailto:[EMAI
Thanks. This is odd.
Did this work on rc1 or is it a new installation?
Do you have a small sample project that shows the problem? If so, post it to
JIRA.
Thanks,
Brett
> -Original Message-
> From: Sri Sankaran [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 25 March 2004 12:15 PM
> To: Mav
Answer 1: java:compile works fine on its own. test:test works fine on its own
Answer 2: I have tried with just *.cache removed. Then I tried with the entire
plugins directory wiped out. Same failure in both cases.
Sri
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Se
Hi Peter,
Inheritence handling in 1.0 is not the best, but is something we'll work on
in future versions of maven.
What actually happens is that maven.xml goals are inherited, but properties
are not. So what is probably happening is that the goal is being inherited
when you run a subproject and r
stupid me...i removed .maven/repository not ./maven/plugins
works fine if you remove right one ;-)
thanks
vlad
>>> [EMAIL PROTECTED] 03/24/04 03:38PM >>>
Seems to be the same problem as another thread on the list. Can you answer
these questions to help diagnose the problem:
1) If you run just "
I'm working at automatically correcting this in further releases.
> -Original Message-
> From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 25 March 2004 9:49 AM
> To: [EMAIL PROTECTED]
> Subject: RE: webapp goal not working in RC2
>
>
> stupid me...i removed .maven/repos
This property was added after RC1, so you'll need to use RC2 to get it, or
manually download and install this version.
While it may work, this is not supported under Maven beta10. Please upgrade
if possible.
Cheers,
Brett
> -Original Message-
> From: Konrad [mailto:[EMAIL PROTECTED]
> S
Some of the plugin documentation has not been published yet. I will aim to
do this today.
- Brett
> -Original Message-
> From: VLADIMIR TERZIC [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 25 March 2004 9:05 AM
> To: [EMAIL PROTECTED]
> Subject: Maven Jira Report plugin in RC2?
>
>
> New
Seems to be the same problem as another thread on the list. Can you answer
these questions to help diagnose the problem:
1) If you run just "java:compile" on its own does it work?
2) When you say that you deleted the plugin cache, did you remove the entire
~/.maven/plugins directory or just the .c
Just recapping my Q's to see what is happening here:
1) If you run just "java:compile" on its own does it work?
2) When you say that you deleted the plugin cache, did you remove the entire
~/.maven/plugins directory or just the .cache files?
- Brett
> -Original Message-
> From: Sri Sanka
When I run war:webapp goal in maven RC2 I get an error saying that java:compile goal
does not exist.
I also tried removing and rebuilding maven repo from scratch but I still get same
behaviour.
thanks
vlad
-
To unsubscribe, e-
New maven release candidate refers to jira plugin but i don't see any references to it
anywhere else on maven site.
Is there such a plugin and where could I find some documentation about it?
thanks
vlad
-
To unsubscribe, e-mail
Thanks for the feedback. Are you using WAS5.0 or 5.1?
Richard
- Original Message -
From: "Al Robertson" <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 25, 2004 3:46 AM
Subject: Re: Anyone working on WebSp
Hello.
Just wondering if the "maven.javadoc.locale" property
of the Javadoc plugin worked as of Maven1.0-beta10?
I tried setting the following property in my
project.properties file:
maven.javadoc.locale=en_US
but it did not work. I have the Japanese IME
installed on WindowsXP, so it's out
Maven will always try to download dependencies from the project.xml in the directory
from where
you run Maven before it attempts to execute any goals. You should only specify the
dependencies
for the subprojects that need them. The top level project.xml should only contain
dependencies
that al
Perhaps something such as
The operating system is Windows
The operating system is Unix
-Original Message-
From: Erik Husby [mailto:[EMAIL PROTECTED]
Sent: 24 March 2004 16:37
To: [EMAIL PROTECTED]
Michele,
See http://maven-plugins.sourceforge.net/maven-was5-plugin/index.html
It appears to be a new plugin by Richard Lewis-Shell. Thanks for the work
Richard. Works a treat. I'm sure the sourceforge maven-plugins main page
will be updated to include it soon.
Al
Digital Union UK
[EMAIL PROTECT
I am trying to convert an Ant script that I have that needs to know
which OS it is currently running on. I took the statements
condition property="isUnix">
and put them in my maven.xml as
Jå$òñ Må¢þhè®$õñ wrote:
I’ve setup a remote repository using https
~/build.properties
maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave
n
Using this setup causes maven to search for dependencies using only one
slash.
Maven output:
Error retrieving artifact from [https:/myS
Jå$òñ Må¢þhè®$õñ wrote:
I’ve setup a remote repository using https
~/build.properties
maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave
n
Using this setup causes maven to search for dependencies using only one
slash.
Maven output:
Error retrieving artifact from [https:/myS
Hi Wim,
> 1) XMLMerger.xml
> -a) tag : in my original Dep. Descripter there's an
> entity bean with no resource refs (refs to Datasources e.g.). Is it
> possible to put the tags somewhere in de XMLMerger.xml so
> that they get merged with the earlier -info. Here's an example:
Well the way it wor
Ive setup a remote repository using https
~/build.properties
maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave
n
Using this setup causes maven to search for dependencies using only one
slash.
Maven output:
Error retrieving artifact from [https:/myServer.edu/maven
Thanks for help, I've posted a ticket on cactus bugzilla for this.
Nico.
[EMAIL PROTECTED] a écrit :
It is probably a problem in the maven cactus plugin.
To solve it you can add the next dependance to the
~/.maven/plugins/cactus-maven-1.6dev-20040226/project.xml
commons-jelly
co
I've take a look on cactus plugin.jelly for 1.6dev-20040226 version
It uses xmlns:x="jelly:xml" tags, but doesn't declare dependency on it
in project.xml.
It seems to be a cactus-maven-plugin bug ! I've posted a ticket on
cactus-maven-integration for this.
Nico.
Barbier Gabriel a écrit :
I
Hi Wil,
thanks for the hint you got in the XDoclet mailing list (I didn't take a
closer look at it right now, but I definitely will...).
As mentioned before do we not use arch4j but XSLT.
Our plugin contains the following two goals for merging DDs. Here's the
Jelly script part for merging ejb-jar.
It is probably a problem in the maven cactus plugin.
To solve it you can add the next dependance to the
~/.maven/plugins/cactus-maven-1.6dev-20040226/project.xml
commons-jelly
commons-jelly-tags-xml
20030211.142705
Is it true ?
Nicolas,
nicolas De Loof <[EMAIL
It seems this dependency is only needed when using latest versions of
cactus plugin.
Using 1.6dev-20040115, eclipse plugin works fine.
Nico.
Barbier Gabriel a écrit :
I verified in maven rc2, and I didn't find this jar in default distribution (ie in lib folder).
-Message d'origine-
De
That did the trick
cheers
On Wed, 2004-03-24 at 11:28, Joachim Bader wrote:
> On Wednesday 24 March 2004 12:08, Joe Taylor wrote:
> > RC2 doesn't seem to have the torque plugin. From earlier posts it looks
> > like this has been migrated into the torque project but I cant find a
> > download for
I verified in maven rc2, and I didn't find this jar in default distribution (ie in lib
folder).
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:55
À : Maven Users List
Objet : Re: having troubles with maven RC2
OK about that, but did
I tryied the 3 cactus-maven-plugin versions that I found on ibiblio.
Using 1.6dev-20040115, eclipse plugin works fine. with the 2 newers one,
I got this ClassNotFoundException.
Is this a known bug ? Iis it any "api change" in cactus plugin that
causes this exception ? Do I need to open a new bu
OK about that, but didn't maven dependency ensure this when runing the
eclipse plugin ?
I re-installed maven RC2 and deleted my local repo for test.
without the cactus plugin, eclipse:generate-classpath goal works fine
with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException
Do I ne
this jar must be place in your folder
${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is
installed.
-Message d'origine-
De : nicolas De Loof [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 24 mars 2004 14:46
À : Maven Users List
Objet : having troubles with m
Hello,
I'm trying to use maven RC2 on some of our projects that are using RC1.
Everything looks good (build, test, cactus with new cactus-maven
plugin...), but I get some troubles with maven-eclipse plugin :
maven eclipse:generate-classpath fails with this error :
__ __
| \/ |__ _Apache__ _
I am sorry... I meant to say .
So, to recap:
Project structure
Root
|
+-- sub-project-1
|
+-- sub-project-2
Root's maven.xml:
<-- Causes the error
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 9:35 PM
To: 'Maven Users Li
Hello dion,
Following your advice I wanted to give a look at the stutus of the current
plugin for WAS50, but the link is pointing to the maven-plugins page where
only the maven plugin for was4.0 is present.
Or am I missing something ? In case can someone from the audience point me
to the rigth loc
On Wednesday 24 March 2004 12:08, Joe Taylor wrote:
> RC2 doesn't seem to have the torque plugin. From earlier posts it looks
> like this has been migrated into the torque project but I cant find a
> download for it. Do i need to build this from CVS? or have i missed
> something else along the way?
Hello
I have a multiproject project set up something like this:
/root-project
maven.xml
project.xml
project.properties
/sub-projects
/sub-project-one
maven.xml
project.xml
proje
> RC2 doesn't seem to have the torque plugin. From earlier posts it looks
> like this has been migrated into the torque project but I cant find a
> download for it. Do i need to build this from CVS? or have i missed
> something else along the way??
Yes, you need to build it.
You can ask to torque
Hi Jörn,
Thanks for your fast reply.
The ['raw'-jars with seperate DD] (configurable via XSLT) approach
could be a satisfying solution. We could split de DD in changeable and
un-changeble pieces. De end-deployers can access de changeable pieces of
the DD OR even better, provide there own over
RC2 doesn't seem to have the torque plugin. From earlier posts it looks
like this has been migrated into the torque project but I cant find a
download for it. Do i need to build this from CVS? or have i missed
something else along the way??
cheers
Joe
___
Hi Wim,
we have a very similar issue. We have many modules containing EJBs, each in
a separate Maven project. We are combining these modules to a product and
merge the deployment descriptors using XSLT. To achieve this, each module is
a normal jar (i.e. has no META-INF directory) that contains a s
Hi there,
Newbie question: I've read the introduction to maven as described in
http://maven.apache.org/reference/user-guide.html#Multi_Project_Builds_and_t
he_Reactor. Then I copied from another source a new goal into my maven.xml.
Build fails with the following messages:
_
Hi there,
This is actually a 'configuration' issue.
i have the following situation:
I want to assemble an J2EE application (ear) which consist of 2
EJB-JARS.
One of de EJB-JARS contains 'common' stuff (let's say, like
user-management, authentication, authorisation) and is an artifact
created vi
Hi,
I have a maven.xml file in all my projects and subprojects that defines the
default goal for the project, i.e. a maven.xml might look like this:
Is there a way to call the multiproject plugin or the reactor with the clean
and 'default' goals, i.e. does the default goal defined in maven.
Response inline
>The way that I went about something similar was to create a custom xdoclet module.
>It's fairly
>trivial to create a task that simply uses your xdt files. You can then package this
>module and
>deploy it to your ANT_HOME/lib (like your other xdoclet modules). Then you simply
>d
Your situation is the inverse, you need to have 3 projects :
- an EJB-JAR
- a WAR for presentation
-an EAR who have the ejb-jar and the war as dependencies (take a look at
the ear plugin docs)
Yoou can use multiproject to generate all these artifacts
(3 kind of artifact => 3 project :
http://wik
Sébastien BRUNOT wrote:
Hello,
It seems to me that the javadoc plugin does not copy the doc-files
directories. Is it a known bug or a misconfiguration from myself ?
I also had this problem lately, but did not have time to investigate.
I'm under impression that the files should be copied by th
51 matches
Mail list logo
