cheers Dion & Brett,
think I might learn a bit more about xml before I try using it :)
[EMAIL PROTECTED] wrote:
Doctype is only for DTDs.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast <[EMAIL PROTECTED]> wrote on 04/09/2003 07:21:07 PM:
Hi
Why not preGoal on the distribution goal and set the extra things up.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nelson Arapé <[EMAIL PROTECTED]> wrote on 05/09/2003 08:45:35 AM:
> Hello to all
>
> I want to know if I could a goal defined in maven.xm
Doctype is only for DTDs.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Nathan Coast <[EMAIL PROTECTED]> wrote on 04/09/2003 07:21:07 PM:
> Hi,
>
> POM validation, is there any reason why project.xml is validated using
> pom:validate rather than adding
Hello to all
I want to know if I could a goal defined in maven.xml overwrite a plugin's
goal?.
I have a multiproject configuration and I want to make a customized
distribution (subprojects jar, plus parent project docs, plus subprojects
javadocs, etc).
I guess that I could just define a new
POM validate does so more on Maven's requirements than just the xsd I
believe.
Your doctype has the wrong root element (web-app), the publicId is
artificial so you might as well use SYSTEM instead of PUBLIC
"maven-project", and lastly I'm not sure DOCTYPE works with xsd at all :) I
think it is onl
> 2. Apply custom filters. say for e.g if I say @[EMAIL PROTECTED]
> it will filtered as href="www.viewcvs.com/index.html">index.html.
That depends where you want to filter. You can already do this on resources,
but not docs.
> When I refer the project documentation, I came to know that,
> the
Hi,
POM validation, is there any reason why project.xml is validated using
pom:validate rather than adding a DOCTYPE element to the project.xml?
So allowing my xml editor to worry about the validity of my project.xml.
I tried adding this
with maven-project.xsd in the same dir as the project.x
The attached patch to the plugin.jelly script for the maven-jar-plugin will
allow you to add arbitrary values to the manifest--complete with sections
which will make the sealing of classes/packages possible. The new values
are added like this:
maven.jar.manifest.attributes.list = GUIApp-Conf,GUIAp
Erik Husby wrote:
I had a need to do this as well.
In maven.xml, I added:
And then in project.properties, one adds
maven.jar.manifest=MANIFEST.MF
SO it does merge...
I just spent some time changing the plugin to add to the manifest using properties.
Example snippet below:
I had a need to do this as well.
In maven.xml, I added:
And then in project.properties, one adds
maven.jar.manifest=MANIFEST.MF
The result is Maven will merge the MANIFEST.MF that you generate with
the one it does.
Make sure that you have the latest version of the JAR plug
Berin Loritsch wrote:
Is this a bug or what?
I want to post-process the compiled tests to generate meta info,
however under some circumstances "maven.test.dest" is not set.
As a result any files referenced to that variable are off.
For example:
No test sources -> variable not set (maven.test.des
Is there currently any way to simply add new manifest entries to all
the ones that Maven generates for you? I have a special packaging
requirement that needs to add up to four attributes--but I don't want
to have to choose between Maven generated and personally generated
manifests. I would like t
On Thursday 04 Sep 2003 17:53, [EMAIL PROTECTED] wrote:
> I suppose so, but there are essentially two places:
> a) maven core properties (as per the user guide), or
> b) the plugin that provides that functionality.
>
>
> Would a page like this
> http://maven.apache.org/reference/plugins/index.html
Is this a bug or what?
I want to post-process the compiled tests to generate meta info,
however under some circumstances "maven.test.dest" is not set.
As a result any files referenced to that variable are off.
For example:
No test sources -> variable not set (maven.test.dest = '')
No concrete tes
[EMAIL PROTECTED] wrote:
I suppose so, but there are essentially two places:
a) maven core properties (as per the user guide), or
b) the plugin that provides that functionality.
Would a page like this
http://maven.apache.org/reference/plugins/index.html
help if there were more detail, or are you
I suppose so, but there are essentially two places:
a) maven core properties (as per the user guide), or
b) the plugin that provides that functionality.
Would a page like this
http://maven.apache.org/reference/plugins/index.html
help if there were more detail, or are you after fundamentally diff
On Thursday 04 September 2003 05:02, Emmanuel Venisse wrote:
> Yes, you should create a Jira issue.
> maven.latex.docs represents files list used for the generation.
Done, MAVEN-780
Now if someone provime instructions I think that I can fix it
Nelson Arapé
>
> - Original Message -
> From
How about including the version number in the file name, along with
RELEASE? For example, myproject-1.0-RELEASE, myproject-2.0-RELEASE,
myproject-2.1-SNAPSHOT, etc.
On Thu, 4 Sep 2003, at 14:19:44 [GMT +0700] Jason Dillon wrote:
> Works, though which release? A project may have a stable 2.0 and
[EMAIL PROTECTED] wrote:
Documentation:
1) maven.compile.src.set - documented as part of the java plugin @
http://maven.apache.org/reference/plugins/java/properties.html
2) core property documented in the users guide
3) maven.test.compile.src.set - is NOT documented as part of the test
plugin @
Documentation:
1) maven.compile.src.set - documented as part of the java plugin @
http://maven.apache.org/reference/plugins/java/properties.html
2) core property documented in the users guide
3) maven.test.compile.src.set - is NOT documented as part of the test
plugin @ http://maven.apache.org/r
So who wants to change the repository plugin to enforce the pom being
present.
It's really low on my list of priorities for a 1.0 release...
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Michal Maczka" <[EMAIL PROTECTED]> wrote on 04/09/2003 09
post us a sample
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Paul Libbrecht <[EMAIL PROTECTED]> wrote on 04/09/2003 06:53:00 PM:
>
> Hi,
>
> I am currently making a bunch of JNLP output within a maven.xml and...
> maven complains that the jar el
There are a couple properties that I found useful to use in my own plugin.
I have a plugin that I want to generate meta information for all classes
compiled. I conveniently added postGoal entries for "test:compile" and
"java:compile". The properties I needed to leverage were:
maven.compile.src.se
Is there a directory layout defined for maven j2ee projects anywhere
like the j2se one defined here -
http://maven.apache.org/reference/dirlayout.html All I can find is the
following two documents, each specifying different structures.
ftp://www6.software.ibm.com/software/developer/library/j-m
> No.
>
> A reactored jar:install, or multiproject:install will build from the
> bottom up.
I agree that it .should. be doing so. My problem is that it is not.
According to the "Our processing order:" list, bar.jar is correctly getting
built first, but before anything is built I get the error sa
On Thu, 4 Sep 2003, Jason Dillon wrote:
> Works, though which release? A project may have a stable 2.0 and a
> legacy 1.0, both are releases IMO. Just a naming confusion problem.
>
> I like the stable/unstable tags which debian uses.
Unstable is the nightly build :) And thus should be SNAPSHO
I fixed it in cvs head.
The correct line is
- Original Message -
From: "Christian Goos" <[EMAIL PROTECTED]>
To: "'Maven Users List'" <[EMAIL PROTECTED]>
Sent: Thursday, September 04, 2003 2:04 PM
Subject: RE: Problem with Jar-Plugin Extension List
> Thanks, I will do. But I don't know
Thanks, I will do. But I don't know how yet.
Are there some guidelines to follow (project, issue type, etc.),
when raising an issue.
Raise this into jira and I'll fix it asap.
Christian Goos wrote:
> Hi,
>
> Although I set the variable "maven.jar.manifest.extensions.add==true" the
> extension
- Original Message -
From: "S. Radhakrishnan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 04, 2003 12:15 PM
Subject: FW: Regarding Maven Enhancements.
> Hi,
>
> I am using Maven beta 10. In that I had the following requirements.
>
> 1. Sending email if build fa
You can create a project.xml that contains all dependencies without os
specifics, and os specifics project.xml that extends to first project.
- base-project.xml
- project-solaris.xml extends base-project.xml and contains
swt-solaris-motif
- project-win32.xml extends base-project.xml and contains s
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 4:16 AM
> To: Maven Users List
> Subject: Re: Distinguishing between runtime and compile time
dependencies
>
>
>
> On Thu, 4 Sep 2003 [EMAIL PROTECTED] wrote:
>
> > Henri Yandell
Hi,
I am using Maven beta 10. In that I had the following requirements.
1. Sending email if build fails.
2. Apply custom filters. say for e.g if I say @[EMAIL PROTECTED] it will
filtered as index.html.
When I refer the project documentation, I came to know that, the
nagEmailAddress in project.xm
Yes, you should create a Jira issue.
maven.latex.docs represents files list used for the generation.
- Original Message -
From: "Nelson Arapé" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 03, 2003 11:03 PM
Subject: Docs for latex plugin miss a needed property
H
Could you please clarify how I could in a single project.xml file define
OS specific dependencies?
I wish to download swt for windows when maven is run on a win32 box and
swt for solaris on a solaris box.
swt
2.1.0
swt-win32-2.1.0.jar
or
swt
2.1.0
swt-
Hi,
I am currently making a bunch of JNLP output within a maven.xml and...
maven complains that the jar element needs a jar-file to be specified...
Well... I tried putting everything in the no-namespace world, but that
doesn't help either...
My current solution is to use but it's definitely
That looks nice...
Is there any policy about plugin-distributions and download ?
Is there a separate chain of repositories for plugins ?
Thanks.
Paul
On Mercredi, sept 3, 2003, at 23:28 Europe/Paris, Trygve Laugstøl wrote:
On Wed, 3 Sep 2003, Berin Loritsch wrote:
The old how to write a plugin
I know that...
But if jnlp, for example, is part of the "standard" distribution of
plugins (does this exist?) then its tags should be fed as well.
An alternate route could be to have, at registration time, the plugins
add elements to the schema... and have a "validate:generate-xsd" task.
Paul
Works, though which release? A project may have a stable 2.0 and a
legacy 1.0, both are releases IMO. Just a naming confusion problem.
I like the stable/unstable tags which debian uses.
But I don't care too much, just that there is some link that always
points to the latest release as to re
38 matches
Mail list logo
