Use XML entities.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Joël Wijngaarde [Us Media] [EMAIL PROTECTED] wrote on 04/10/2003
07:47:45 PM:
Hi,
I would like to insert the contents of some files in the xdoc
documentation. the files I mean are in
On Sun, 2003-10-05 at 21:22, Jean-Noel Filippi wrote:
Hi there,
After instanciating a maven Project object, how can I attain a goal (like
java:compile)?
I tried to add a goal with a MavenSession object and run 'attaingoal'
but it does not work. Here is my code:
Project p =
On Sun, 2003-10-05 at 21:44, Stou Sandalski wrote:
Hi,
Hi,
I have been trying to get maven to run the unit tests on my project, maven
test:test tries to launch the unit test by its class name as opposed to its
full package.class name, however the 'maven test:single' command runs the
test
Hi,
Thanks Jason, I'll look into that. I also wanted to commend Maven for
stepping into a hole no product including Ant has (to my knowledge) filled -
defining the processes (via plugins and goals) used through project
developments. Defining a goal for every standard process (war:war for
creating
I added some verbose information and realized that the way dotuml looks
for packages in the sourcetree is the problem. It all works fine, when I
execute the dotuml goal on a single project. If this project
participates in a multiproject it can't deal with constructed pathnames
(contains /../).
If
I would support this request, which, if I understand well, hasn't been
answered yet.
It is clear that many extra things will be caught (e.g. servlet's
doGet) by such a report but this is not really a problem and such a
tool should support being configured to avoid declaring it as unused.
It
Hello,
Maven has a mechanism for project-inheritance via the extend tag. This is
a good practice enabling even further standardization and unity between
various project aspects, especially for organizations/corporations
generating more than a small number of projects.
However, I've seen in
Siegfried Goeschl wrote:
Oops,
considering dynamic class loading and reflection it is actually impossible ...
Cheers,
Siegfried Goeschl
I can second that--but I can go one further.
Due to the type of design and true separation of implementation/interface with
Avalon style components, each
On Mon, 2003-10-06 at 08:37, Arik Kfir wrote:
Hello,
In summary we realize the failings of the current mechanism but put this
text in JIRA so it can be referenced. The mechanism will not change
until post 1.0.
Maven has a mechanism for project-inheritance via the extend tag. This is
a good
There is already Jira issue.
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-699
You can vote on it.
Arik Kfir wrote:
Hello,
Maven has a mechanism for project-inheritance via the extend tag. This is
a good practice enabling even further standardization and unity between
various project
Nooo... I think users of such a tool would accept to write by hand the
methods that should be considered as entry-points to the package!
Paul
On Lundi, octo 6, 2003, at 14:48 Europe/Paris, Berin Loritsch wrote:
Siegfried Goeschl wrote:
Oops,
considering dynamic class loading and reflection it
Paul Libbrecht wrote:
Nooo... I think users of such a tool would accept to write by hand the
methods that should be considered as entry-points to the package!
I am not advocating that this project build such an animal. All I am
saying is that when you have every piece as truly isolated as
We use Clover (and there is a plugin for it last time I checked) which gives
you a bunch of statistics (method completion, statement completion, and
conditional completion) on code coverage in your source directory. These
statistics are bsed on your unit test coverage.
-Original
Clover actually reports on all method/statement/conditional level usage in
your code. You first have to instrument your code and all that means is
running your source through the Clover filter which adds clover java lines
after every statement in your class. Then when you run your units against
Berin Loritsch wrote:
Paul Libbrecht wrote:
Nooo... I think users of such a tool would accept to write by hand the
methods that should be considered as entry-points to the package!
I am not advocating that this project build such an animal. All I am
saying is that when you have every piece as
Tim,
I would recommend Maven to everyone. I come from a Config Management
background and its hard pushing the principles on to other who don't
care or shouldn't care. Maven provides a framework for all to work
within and thus includes everybody in that framework.
So as long as everybody is
I have a problem generating my navigation. All links in the navigation
bar are empty.
?xml version=1.0 encoding=ISO-8859-1 ?
project name=MyProject
properties
author email=[EMAIL PROTECTED]Marek Lange/author
titleMyProject/title
/properties
body
links
A Maven regional repository has been set up. It is at
http://hoover.unx.sas.com/maven. All files from http://d7779/maven have been copied
over. Brian Helsel wants to know if the setup is working alright. Please update your
properties to point to this location and report any problems/errors.
On Monday 06 Oct 2003 21:01, Sri Sankaran wrote:
A Maven regional repository has been set up. It is at
http://hoover.unx.sas.com/maven. All files from http://d7779/maven have
been copied over. Brian Helsel wants to know if the setup is working
alright. Please update your properties to
I'm using multiproject plugin in a situation with one paren project
aggregating documentation for several sub projects.
It appears that the #foreach ($reactorProject) loop in navigation.xml
does not list my sub projects if they do not have an id tag in
their projct.xml (although they do have a
On Monday 06 Oct 2003 21:08, Dolf Starreveld wrote:
I'm using multiproject plugin in a situation with one paren project
aggregating documentation for several sub projects.
It appears that the #foreach ($reactorProject) loop in navigation.xml
does not list my sub projects if they do not have an
Maven genapp has been updated. It is now interactive. Please download
maven-1.0rc1-MIS-2003-10-06.zip from the regional repository
http://hoover.unx.sas.com/maven .
Summary of changes
* Interaction
* Project is created in a sub-directory of the current location
* All spaces
At 21:16 +0100 10/6/03, Andy Jefferson spoke thusly:
I suppose I was confused then. Am I correct and understanding that
there is no relationship between id and the other two
groupId/artifactId?
On Monday 06 Oct 2003 21:08, Dolf Starreveld wrote:
I'm using multiproject plugin in a situation
On Monday 06 Oct 2003 21:20, Dolf Starreveld wrote:
I suppose I was confused then. Am I correct and understanding that
there is no relationship between id and the other two
groupId/artifactId?
Well from how I understand it ...
* A project currently uses groupId and id. It doesn't use
On Mon, 2003-10-06 at 16:01, Sri Sankaran wrote:
A Maven regional repository has been set up. It is at
http://hoover.unx.sas.com/maven. All files from http://d7779/maven have been copied
over. Brian Helsel wants to know if the setup is working alright. Please update
your properties to
I am attempting to override a plugin goal and am not able to. Maven
continues to execute the original goal, not my override.
This is in beta 10. My recollection is that all you had to do was declare a
goal of the same name in your maven.xml file. Is this incorrect?
Thanks,
Wordman
On Mon, 2003-10-06 at 16:46, Lester Ward wrote:
I am attempting to override a plugin goal and am not able to. Maven
continues to execute the original goal, not my override.
This is in beta 10. My recollection is that all you had to do was declare a
goal of the same name in your maven.xml
Oops. Sri meant to send this to our -internal- Maven-users list, not the Maven
community at large. Sorry!
Jason
considers renaming internal list to anything besides maven-users
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 12:43 PM
What version of Maven? As of RC1, ${pom.build.sourceDirectory} is an
absolute path already.
Can you confirm that calling ant / changes ${basedir} itself? If so, file
a bug in JIRA - my guess is if this is happening, that they both use a
system property and ant scrogs maven's value.
- Brett
Brett,
Thank you for your answer.
I use beta-10.
Can you confirm that calling ant / changes ${basedir} itself? If so, file
a bug in JIRA - my guess is if this is happening, that they both use a
system property and ant scrogs maven's value.
that's the point, ${basedir} is not changed, but the
Brett,
Thank you for your answer.
I use beta-10.
Can you try RC1, and remove the use of FileUtil? Pom.build.sourceDirectory
should be absolute already, and you can use the maven:makeAbsolutePath tag
to do this otherwise.
Can you confirm that calling ant / changes ${basedir}
itself? If
I will try RC1
Can you try RC1, and remove the use of FileUtil? Pom.build.sourceDirectory
should be absolute already, and you can use the maven:makeAbsolutePath tag
to do this otherwise.
I don't actually use it directly. Both checkstyle and PMD plugins use
FileUtil to parse the dir structure
Ok, now I've got it. If this is still a problem in RC1, let me know. I
believe I removed this behaviour when I fixed the ${basedir} problems, but
am not entirely sure.
Thanks,
Brett
-Original Message-
From: Alexey Krasnoriadtsev
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, 7 October
33 matches
Mail list logo
