That was it! Thanks, Lester.
On Fri, 12 Dec 2003, at 10:11:45 [GMT -0500] Lester Ward wrote:
>> I'm having a hard time figuring out how to specify a navigation.xml
>> file for my subprojects. When I do a multiproject:site, I find that my
>> subproject's xdocs/navigation.xml file is ignored, and t
Do you have any dependencies to build your EAR in your main
project.xml? If so, that could be the problem since your
ear/project.xml will inherit the dependencies.
Jeff
On Fri, 12 Dec 2003, at 13:02:49 [GMT -0500] Tim Chen wrote:
> I followed the link on someone else post and trimmed by projec
Perhaps there should be a plugin or test of some sort to validate
plugins and make sure that they
adhere to some basic standards like using ${maven.build.dir} rather
than hardcoding to 'target/'.
Anyone can write a plugin anyway they want, but this could be a
checkstyle type thing to help peop
>> My point was only that I've seen projects disintegrate when
>> they began to insist that the rest of the world conform to
>> them _unnecessarily_.
> I think the opposite has happened with Maven though. Compared
> to Ant you are greatly more restricted in what you can do.
True, but the restr
> Unfortunately the use of ${maven.build.dir} was not adopted
> by all parties else this discussion would have been moot.
> The source of our discomfort are the odors eminating from the
> use of hard-coded directory names like "src" and "target"
> in some templates and jelly scripts.
Hmm. Odd. I
So lets start a drive to get rid of them in all the plugins.
Fire up the first bug report!
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"W. Sean Hennessy" <[EMAIL PROTECTED]> wrote on 13/12/2003
10:30:27 AM:
> Yes.
> Unfortunately the use of ${maven
The is inside a element, right?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Chad Woolley <[EMAIL PROTECTED]> wrote on 13/12/2003 10:49:40 AM:
> Hi,
>
> I am starting a new simple java project. I used the "Simple Java"
example from
> the examples
Dependency
Needs to be wrapped in a tag.
Ex:
bcel
5.1
Tim Chen
[EMAIL PROTECTED]
-Original Message-
From: Chad Woolley [mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003 6:50 PM
To: [EMAIL PROTECTED]
Subject: How do I get java:compile to automatic
Chad Woolley wrote:
bcel
5.1
you should try the following :
bcel
bcel
5.1
-- gd
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I am starting a new simple java project. I used the "Simple Java" example from
the examples plugin. I only have two class files so far (test classes not added
yet).
The problem is that when I run java:compile, it does not add my dependent jar to
the classpath, even though I have it in th
Yes.
Unfortunately the use of ${maven.build.dir} was not adopted by all parties else this
discussion would have been moot.
The source of our discomfort are the odors eminating from the use of hard-coded
directory names like "src" and "target"
in some templates and jelly scripts.
-Original M
Brian Burridge wrote:
Is there a way to include one xdoc file (../../xdoc/test.xml) from
another (subtest.xml)?
not sure if this is exactly what you want to achieve but you could use
external entitities in your pom that would point to the other xdocs. i
do that and havent experimented any troubl
Guillaume Barré wrote:
Error retrieving artifact from [http://www.ibiblio.org/maven/dom4j/jars/dom4j-1.
3.jar]: java.net.ConnectException: Connection timed out: connect
Arent you behind a firewall ? if yes you can try to use ntlm proxy. ive
used it successfully with maven some months ago to by
[EMAIL PROTECTED] wrote:
When defining propert "a.b" in plugin aPlugin, then using the bPlugin,
is it possible to access default properties defined in aPlugin (e.g.
${a.b})?
I tried, and i faild. Is there a workaround?
workaround for what ? what did you try ?
something like this should work :
On Fri, 2003-12-12 at 17:00, W. Sean Hennessy wrote:
> A point of order..
> "currently flexible property with a rigid standard"
> is not entirely accurate.
> "target/" is not a property, it is hard coded.
> The discussion is about changing this hard coded directory name to a property like
> ${targ
A point of order..
"currently flexible property with a rigid standard"
is not entirely accurate.
"target/" is not a property, it is hard coded.
The discussion is about changing this hard coded directory name to a property like
${target-dir-nm}.
-Original Message-
From: Lester Ward [mailto
Hi all,
I'm realy new to maven and i'm trying to install it on Windows 2000 Professional.
My %MAVEN_HOME% is C:\Program Files\Apache Software Foundation\Maven 1.0-rc1
Ma %PATH% contains C:\Program Files\Apache Software Foundation\Maven 1.0-rc1\bin
I have run the "%MAVEN_HOME%\bin\install_repo.
On Fri, 2003-12-12 at 15:38, Lester Ward wrote:
> > Your analysis is simply erroneous. We don't make changes
> > arbitrarily for the sake of making changes or to cause users
> > long-term grief. So far I think I've done all right in OSS
> > using similiar practices that I employ for Maven.
>
>
> Your analysis is simply erroneous. We don't make changes
> arbitrarily for the sake of making changes or to cause users
> long-term grief. So far I think I've done all right in OSS
> using similiar practices that I employ for Maven.
I agree. Maven is a wonderful piece of technology.
> Veloci
Hi Celso,
you can build ANY type of application (and even for any type of language).
If you are already familiar with Ant, you know that you simply declare
tasks (which can be any type: compile, jar, copy, anything) and order Ant
to execute them. Look at Ant user manual to have an idea the typ
Is there a way to include one xdoc file (../../xdoc/test.xml) from
another (subtest.xml)?
Brian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello Folks,
I am trying to use maven in a desktop project and I am having some
difficults to write the project.xml
and maven.xml. I've been looking for examples but I found just examples to
web applications. Does
anybody has an example (project.xml and maven.xml) or a tutorial wich
teaches to us
On Fri, 2003-12-12 at 11:30, Kyle Adams wrote:
> Granted, I also think it's a best practice to version JAR files; however, I'm not
> convinced that putting the version in the file name is a good idea, let alone a best
> practice.
>
> Filenames don't seem to be a good place for storing data like
On Fri, 2003-12-12 at 10:51, Stéphane Philippart wrote:
> Hi,
>
> I am in a case where I don't want version number on my deliverable files
> but i want to be able to use the install targets to install my app in
> the repository to refence the file with the dependency tag.
>
> When I don't put a
On Fri, 2003-12-12 at 10:22, Lester Ward wrote:
> Jason van Zyl wrote:
> > Fair enough, development ease is certainly a valid use case but I
> > honestly see this as a limitation of the tools being used that aren't
> > flexible enough themselves to deal with different locations
>
> This is the big
I followed the link on someone else post and trimmed by project.xml and
project.properties.
I found that I get the error regardless of whether the type is a jar or
an ear.
Any ideas what might cause a plugin to lose it's goal definitions?
+
| Executing mul
Hi,
I've got "strange" error with multiproject:site. I have a set of project [X, Y,
Z], if I use goal [multiproject:site], it fail on project X.
Error is : Goal [xdoc:register-reports] has no action definition
But if I run goal [site] inside project X, it works fine and the site is generated.
Try this article: http://www.theserverside.com/resources/article.jsp?l=MavenMagic
It helped me a lot when I switched from ant to maven. Also check out the maven wiki. There are a couple of great docs covering J2EE projects.
Ralf
Lester Ward wrote:
What is the best way to build a J2EE project?
Maven 1.0 rc1
I'm not sure what I did wrong.
My multiproject works fine until I try to drop in an ear module.
The structure is as so:
C:\projects\MITFactoryGui\modules\ear>
I get this when running: maven multiproject:install
+
| Executing multiproject:install
It's a known issue. See :
http://jira.codehaus.org/ViewIssue.jspa?key=MAVEN-109
Nicolas,
"Javier Ramos" <[EMAIL PROTECTED]>
12/12/2003 17:46
Veuillez répondre à "Maven Users List"
Pour : "Maven Users List" <[EMAIL PROTECTED]>
cc :
Objet : Completion status of mav
Hi all,
Here is my problem, let's see if anyone has an answer:
As part of the installation of a development environment based in eclipse and
maven, I am creating a script in dos shell to configure several files, database
tables, and so on.
I am launching maven to carry out some goa
Granted, I also think it's a best practice to version JAR files; however, I'm not
convinced that putting the version in the file name is a good idea, let alone a best
practice.
Filenames don't seem to be a good place for storing data like this, especially when
you have Sun's versioning specs
Hullo all...
I was searching for the Maven User List, but no results...
I'm trying to generate checkstyle statistics, but with no sucess...
I also get no errors in maven.log...
Could someone point me to the right direction, please??
Thanks in advance...
__
Demerson Zounar
Analista
I define in my ear module the next dependencies :
protoCoopgen
coopgen
SNAPSHOT
war
true
protoCoopgen
protoCoopgen-ejb
coopgen
SNAPSHOT
ejb
true
I launch ear:install. The lo
Agreed that it is probably best practice but if you want to you can
always over-ride the property (if provided) of the plugin you are using.
Read http://maven.apache.org/reference/plugins/index.html for more
information
Since you are creating a jar then you should look at the properties of
the j
Hi Charlie,
For some reason that isn't clear to me, the war plugin seems to look in a
different place to the jar plugin when determining where to deploy the
artifact.
You need to add something like the following to your project.properties
file:
#deployment - settings for artifact / war.
# see
http
All jars MUST have a version. It's a best practices.
Emmanuel
- Original Message -
From: "Stéphane Philippart" <[EMAIL PROTECTED]>
To: "Maven Users List (E-mail)" <[EMAIL PROTECTED]>
Sent: Friday, December 12, 2003 4:51 PM
Subject: Name of generated files
Hi,
I am in a case where I do
Nevermind...it's a different issue. The JBoss plugin's deploy-warfile
task calls war:war after I've already called it (via cactus:cactifywar),
and it was overwriting my web.xml or something...
-- Sean T.
> -Original Message-
> From: Sean Timm
> Sent: Friday, December 12, 2003 8:42 AM
>
Hi,
I am in a case where I don't want version number on my deliverable files
but i want to be able to use the install targets to install my app in
the repository to refence the file with the dependency tag.
When I don't put a tag in my project.xml (or put the
tag ) the generated file are all w
The cactifywar ant task (used by the Cactus plugin's cactifywar task)
automatically merges the redirectors into the web.xml file. I created a
custom goal in a maven.xml file, and I set prereqs="cactus:cactifywar".
However, the resultant cactified war file does not contain the
redirectors. However
> What is the best way to build a J2EE project?
There is a fairly decent sample on doing this, though it was written before
the multiproject plugin existed:
http://www.pivolis.com/pdf/J2EE_projects_Maven_V1.1.pdf
http://blogs.codehaus.org/people/vmassol/archives/everest.zip
Wordman
Jason van Zyl wrote:
> Fair enough, development ease is certainly a valid use case but I
> honestly see this as a limitation of the tools being used that aren't
> flexible enough themselves to deal with different locations
This is the biggest trap of open source development. A lot of projects are
> I'm having a hard time figuring out how to specify a navigation.xml
> file for my subprojects. When I do a multiproject:site, I find that my
> subproject's xdocs/navigation.xml file is ignored, and the main
> project's xdocs/navigation.xml file is used instead.
The trick is defining this propert
On Thu, 2003-12-11 at 16:21, Lester Ward wrote:
> > Ok, in your opinion what would be the advantage of making these things
> > above configurable? Do you really care that much if all classes are
> > output to target/ ?
>
> It is sometimes useful to have classes be output outside the project
> dire
When defining propert "a.b" in plugin aPlugin, then using the bPlugin,
is it possible to access default properties defined in aPlugin (e.g.
${a.b})?
I tried, and i faild. Is there a workaround?
Cheers,
simon
-
To unsubscribe,
Thank you to all, "The forest didn't let me see the trees". I have gone
through the user guide many times, but I didn't remember to have seen this
feature (jar overrides).
The choices that I have in order to make use of dependencies that comes
from CVS are:
a) maven.repo.remote=
${ba
to all plugin-developers:
I would like to know what the best practice is in documenting the properties
of a plugin (on sitedoc)?
plugin:generate-docs produces a skeleton for the sitedoc, but what is the
best way to fill it with content?
As I understood, there are two ways with different conseque
Hi,
check this first : http://www.mail-archive.com/[EMAIL PROTECTED]/msg03187.html
> -Message d'origine-
> De : Kristinn Danielsson [mailto:[EMAIL PROTECTED]
> Envoyé : Friday, December 12, 2003 11:06 AM
> À : [EMAIL PROTECTED]
> Objet : Out of memory
>
>
> Hi,
> I'm using the Maven 1
Hi,
I'm using the Maven 1.0 RC1 on windows. I have multi-project set-up. But when I try to
execute multiproject:site goal I get java.lang.OutOfMemoryError. Has anyone
encountered this? and is there some solution to this problem.
--
I would not have any problem with the version numbers if the
application.xml is generated from Maven. However, currently I am using the
application.xml file generated from my WSAD. Inside WSAD, the jar and war
files do not have a version tagged to it.
If I were to generate the application.xml u
50 matches
Mail list logo
