[jira] Commented: (MAVEN-1474) exceptions writing classes that use DOM

2004-10-20 Thread jira
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 maven.comp

[jira] Created: (MAVENUPLOAD-239) Ashkay Upload Request

2004-10-20 Thread jira
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: -

[jira] Closed: (MAVENUPLOAD-238) Please upload Dumbster

2004-10-20 Thread jira
Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Wed, 20 Oct 2004 5:19 PM Done. We can purpose to jason kitchen to create a synchronisable directory with ibiblio. - View the issue: h

[jira] Created: (MAVEN-1474) exceptions writing classes that use DOM

2004-10-20 Thread 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: - Key:

RE: can't create an issue on jira

2004-10-20 Thread Arnaud HERITIER
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 jir

RE: can't create an issue on jira

2004-10-20 Thread Arnaud HERITIER
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 Req

Re: can't create an issue on jira

2004-10-20 Thread Julien Kirch
Trygve Laugstøl wrote: You have to be logged in to make a new issue. 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

Re: can't create an issue on jira

2004-10-20 Thread Trygve Laugstøl
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 st

Re: can't create an issue on jira

2004-10-20 Thread Julien Kirch
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 "*St

cvs commit: maven-plugins/eclipse/src/plugin-test maven.xml

2004-10-20 Thread epugh
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.

[jira] Closed: (MPECLIPSE-48) handling source attachments (patch)

2004-10-20 Thread jira
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: http://jira.codehaus.org/browse/MPECLIP

[jira] Created: (MAVENUPLOAD-238) Please upload Dumbster

2004-10-20 Thread jira
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: -

RE: [eclipse] Need to rethink using pom.build.resources in .classpath for Eclipse Plugin

2004-10-20 Thread Eric Pugh
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 layout

Re: Is maven.final.name deprecated?

2004-10-20 Thread Brett Porter
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 in

[jira] Created: (MPXDOC-123) a way to copy xml files instead of transforming

2004-10-20 Thread jira
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: - Key:

Re: Is maven.final.name deprecated?

2004-10-20 Thread Felipe Leme
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

Re: Is maven.final.name deprecated?

2004-10-20 Thread Dion Gillard
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. -- http://www.mult