The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 23 Nov 2004 1:03 AM
Body:
why does your project create an ear and another artifact?
-
View this comment:
http://jira.codehaus
I love the new menu, I think it will be great for first time users as
it requires less interpretation. I am happy to help out with the docs
(although I am by no means a Maven expert yet), just let me know what
you would like done and if I can I will help out.
-Corey
-
While we are on the subject of adding tags to has a scope
tag been considered? This would allow users to generate dep reports
and so on that lead to a better understanding of where and why the
dependancy exists.
Examples:
Runtime (default) runtime
Test Only test
Build Only build
Dependancy of a
On Sunday 21 November 2004 02:14, Vincent Massol wrote:
> Hi Maven devs,
>
> I think there's a need to allow specifying when some artifacts
> are only to be looked for in the local repository. For example,
> in a multiproject the local repository is used to share private
> artifacts between the sub
Looks good, just check you still get prompted for the values when running from a
directory with no project.xml.
A better Jelly expression would be:
${!empty(context.getVariable('...'))} I think. That should test both null and
not 0 length.
- Brett
Quoting Carlos Sanchez <[EMAIL PROTECTED]>:
> H
The following comment has been added to this issue:
Author: Torsten Curdt
Created: Mon, 22 Nov 2004 6:04 PM
Body:
I *did* read that. BUT the current one does not have this information either.
Do you want me to create a textual version of the CPL as LICENSE.txt? ...and to
be hones
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Mon, 22 Nov 2004 5:56 PM
Body:
Please read http://maven.apache.org/repository-upload.html
-
View this comment:
http://jira.codeh
Hi,
When I run
maven scm:checkout-project
-Dmaven.scm.method=cvs
-Dmaven.scm.cvs.module=.
-Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/cvsroot/oness
-Dmaven.scm.checkout.dir=oness
>From a dir with a project.xml, the cvs connection from it overrides the
>command line parameters. I have made
The following comment has been added to this issue:
Author: Torsten Curdt
Created: Mon, 22 Nov 2004 5:52 PM
Body:
The cpl license is inside the jar. Anything else needed?
There is no project.xml for the current version. What should go there?
---
Thanks.
I was thinking something along those lines too, though I've also found it hard
to find what I'm looking for by needing to navigate subtrees. I'll give it
another try.
I'd actually like the navigation to be for return visitors to get straight to
what they want (scrolling is less of an inco
Howdy,
Awesome! The content can definitely be fleshed out as you progress and
hopefully people contribute.
The only comment I have is that there is far too much in the left
navigation. For example I might take the "Getting Started" item and
make that a top-level menu item and then deal with the a
Hi,
I'd like to sign the generated jar and after taking a look to jnlp plugin seems
that its purpose is other than just signing, should
I use it or it'd be better adding a jar:sign goal?
Thanks in advance.
Carlos Sanchez
A Coruña, Spain
http://www.jroller.com/page/carlossg
--
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Mon, 22 Nov 2004 5:23 PM
Cannot deploy without the project.xml file nor LICENSE.txt
-
View the issue:
http://jira.codehaus.org/browse/MA
The following issue has been updated:
Updater: Thiago Leão Moreira (mailto:[EMAIL PROTECTED])
Date: Mon, 22 Nov 2004 11:56 AM
Changes:
Attachment changed to plugin.jelly
-
For a full history of the
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPEAR-28
Here is an overview of the issue:
-
Key: M
Hi folks,
Rather than backing up with tarballs I've started to commit my work on
the Maven site. I had intended to do this on a branch, but I managed to
only branch the modified fields, and all the deletions/additions ended
up on HEAD which was pointless. Rather than fudge around with it, I've
brett 2004/11/22 04:18:05
Modified:xdocsnavigation.xml
Log:
I apologise for using the nav as a comment workspace
Revision ChangesPath
1.50 +1 -1 maven/xdocs/navigation.xml
Index: navigation.xml
===
brett 2004/11/22 04:14:08
Modified:.maven.xml
Log:
messed up the branching of the new site, so it is now on HEAD.
I have disabled site generation on HEAD until the new doco is finished and
voted in - in the mean time, any site releases should continue from
MAVEN-1_0-B
brett 2004/11/22 03:53:00
Modified:xdocsTag: DOCO_REWRITE faq.fml index.xml
navigation-pdf.xml navigation.xml
xdocs/reference Tag: DOCO_REWRITE project-descriptor.xml
xdocs/start Tag: DOCO_REWRITE download.xml install.xml
Adde
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Mon, 22 Nov 2004 5:20 AM
Comment:
major is fairer.
We tend to drive priority by "fix for" version.
Changes:
priority changed from Minor to Major
---
The following comment has been added to this issue:
Author: Boris Boehlen
Created: Mon, 22 Nov 2004 3:57 AM
Body:
Bug's priority should be set to critical as it is in the duplicated bug #1513.
-
View this comment:
Hi folks,
Vincent Massol wrote on Sunday, November 21, 2004 11:15 AM:
[snip]
> One possible solution (backward compatible) would be to add a
> true|false (defaults to false) element to the
> element.
>
> Would this be acceptable for CVS HEAD of m1? Is there
> something planned along these lines
If we can do it without extra tag it's all the best.
Thinking about it, if jar:install is used in multiproject, and no
download is attempted, this should still work as is.
I don't understand why this is linked with the reactor. Let's imagine I wish
to build one of the subprojects without rebu
23 matches
Mail list logo
