On Tue, 19 Oct 2004 22:32:35 +1000, Brett Porter [EMAIL PROTECTED] wrote:
[snip]
This is right - you need to know what the single build artifact is, and
that should be {maven.final.name}.jar
Did you really mean this? Having a jar as the only artifact is very restrictive.
--
On Wed, 2004-10-20 at 07:04, Dion Gillard wrote:
Did you really mean this? Having a jar as the only artifact is very restrictive.
Exactly. I guess that's the reason the maven.war.final.name was created
at first instance.
-
To
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-123
Here is an overview of the issue:
-
Yes, I meant it in terms of there being one main output. There may be
others, but they are offshoots of the original. You can read back
through this thread, the previous discussions, and the discussions on
m2-dev (I think eyebrowse is still the only one archiving this
unfortunately) for more
Well.. I think everybodies points are well said! I learn something new
about doing project layout. In retrospect, my setup is kinda boneheaded,
thats why I didn't see it when committing patches.. Only when I started
using it. And instead of taking the simple approach of rationalizing my
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-238
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Wed, 20 Oct 2004 2:21 PM
Discussion on mailing list resolved my last concern.
-
View the issue:
epugh 2004/10/20 11:23:11
Modified:eclipse plugin.properties
eclipse/src/plugin-resources/templates classpath.jelly
eclipse/src/plugin-test maven.xml
Log:
Remove temporary property. Issue with add resources resolved by discussion on
mailing list.
Arnaud HERITIER wrote:
Hi Julien
It seems to work for me.
http://jira.codehaus.org/secure/CreateIssue!default.jspa
There was certainly a problem. It happens from time to time.
Arnaud
I still haven't the link on the projects (tried regulary all day long),
and when directly trying your link
On Wed, Oct 20, 2004 at 09:57:46PM +0200, Julien Kirch wrote:
Arnaud HERITIER wrote:
Hi Julien
It seems to work for me.
http://jira.codehaus.org/secure/CreateIssue!default.jspa
There was certainly a problem. It happens from time to time.
Arnaud
I still haven't the link on
Trygve Laugstøl wrote:
You have to be logged in to make a new issue.
sigh
the question was :
I'm logged in jira and the issue creation option is disabled (in the
project maven and all the plugin I tried), is it normal ?
but nice try
and thanks
Julien
Actually I have an error :-(
If I can access to it, I'll check your rights.
Arnaud
System Error
A system error has occurred.
If this problem persists - please notify your JIRA administrator of this problem.
If you are an administrator, please try submitting this problem via the Support
Your permissions seems ok :-(
You are in jira-users group and jira-users can create issues on maven !
Arnaud
-Message d'origine-
De : Julien Kirch [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 20 octobre 2004 22:06
À : Maven Developers List
Objet : Re: can't create an issue on jira
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1474
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-239
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 20 Oct 2004 7:38 PM
Body:
This is probably because Maven is endorsing other xml libraries, but those are not in
the compilation classpath so you miss out on both fronts.
Does setting
16 matches
Mail list logo
