I can't select "Maven Project Administration" in Jira "create bug" page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would I create a Jira Issue about Jira config ;-)
Nico.
Brett Porter a écrit :
In a multi-module project you might be right that grouping by scope is not the
easiest way to group. However, we might consider creating groups for each
module and for each scope, i.e. in a project with three modules data, logic,
mvc. We might create the following list of project libraries:
- da
Please put it in JIRA under the project MPA (Maven Project
Administration) - thanks.
Nicolas De Loof wrote:
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
gro
I don't agree with grouping by scope (that likely wouldn't work if I
understand correctly, as the project libraries would be different for
every module), but by groupId might as an optional configuration option.
Please put it in the JIRA.
- Brett
Roald Bankras wrote:
Hi all
Are there yet a
Hi,
Responding to Trygve and Kenney from here (beaver suffered an outtage).
Just looking at the PEPs (http://www.python.org/dev/peps/) and looks like a
good idea. They have templates and my argument for the same format is the
historical success of couching problems a la The Pattern Language as i
On 5/15/06, Jesse McConnell <[EMAIL PROTECTED]> wrote:
I think this is a great idea, it would be a good exercise to go
through the existing ideas that are slated and clean them up in a
clear well reasoned way. the limited amount in the queue at any one
point in time is probably a good idea as w
I think this is a great idea, it would be a good exercise to go
through the existing ideas that are slated and clean them up in a
clear well reasoned way. the limited amount in the queue at any one
point in time is probably a good idea as well...force the asking of
the tough questions and whatnot
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
group/artifact/artifact-xyz-java-sources.jar
So I can see three options :
1. Add a new Rule for "java-sources"
> First thought: Why "modules"? Everyone talks about
> "multi-projects" and "artifacts"
I try to avoid calling it multiproject for this reason.
So how do you call it then? ;)
> When I tried to build the (main) project I got told off that packaging
> was meant to be "pom" not "jar" ...ok - but
Hello guys,
From a previous post I know Maven1 repo is a redirect to maven2
repository content, with path transcripted to match maven2 hierarchy.
commons-collection (as an example) has sources jar in maven2 repo
(http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commo
Hi everyone,
Just to let you know that JavaBlackBelt (http://www.javablackbelt.com/) has
started a Maven2 certification. I have helped them define the test
objectives and I'm marked as the certification lead. There are currently 3
certifications defined (listed at the bottom of
http://www.javablac
Hi all
Are there yet any plans to group the dependencies inside intellij?
I'd like to see some project libraries instead of module libraries. My
suggestion is to group them by scope, but another way might be to group them by
module (esspecially for multi module projects).
What are your idea's?
I am new to maven and I am currently creating a plugin for building a
particular type of project using Maven 2.x. To acheive this I develop a
plugin based in an Ant mojo.
I would like to have access, in my Ant mojo script, to a XSL file
(transform.xsl) stored into the plugin (at the root reposit
Hi,
User comment : what about http://jira.codehaus.org/browse/MWAR-33 ?
I think if WEB-INF/lib from war dependencies is not by default excluded
can cause some surprises when the war is deployed on a app server.
Because the WEB-INF/lib cab be different from the classpath in the test
cases.
But the
On 5/15/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Heh, this was 13/4 not 14/5 as I thought.
Time flies, right?
Are these still needing to be looked at?
Yes
So here's a little update :)
patch management
- review MJAR-27 - let me know if you really want a test case or apply.
- review
+0
s/
On 5/14/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Maven 2.0 had a fairly decent regression:
http://jira.codehaus.org/browse/MWAR-38
which appears to have been caused by:
http://jira.codehaus.org/browse/MWAR-7 (though the fix should support both)
I'm surprised nobody noticed this during
Jason van Zyl wrote:
Hi,
I was just looking at the wiki for the 2.1 design stuff and was
wondering if we could use a common format for each issue? I was
thinking that we may borrow from a Pattern Language and for each issue
have a Context, Problem, Solution, and maybe Implementation Detai
+1
Emmanuel
Brett Porter a écrit :
Maven 2.0 had a fairly decent regression:
http://jira.codehaus.org/browse/MWAR-38
which appears to have been caused by:
http://jira.codehaus.org/browse/MWAR-7 (though the fix should support both)
I'm surprised nobody noticed this during the testing period. I
18 matches
Mail list logo
