[jira] Commented: (MPJDIFF-6) Support SVN, not just CVS for retrieving base API definition

The following comment has been added to this issue: Author: John Fallows Created: Wed, 20 Oct 2004 1:05 AM Body: This was a feature request. Looking at the plugin.jelly source for version 1.4 of the plugin, it seems like sections such as the following needs to become

RE: can't create an issue on jira

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 > -Message d'origine- > De : Julien Kirch [mailto:[EMAIL PROTECTED] > Envoyé : mardi 19 octobre 2004 23:50 > À : [EMAIL PROTEC

cvs commit: maven-plugins/ear/src/plugin-test/test01/src/resources resource.txt

felipeal2004/10/19 19:29:56 Modified:ear/src/plugin-test maven.xml project.xml Added: ear/src/plugin-test/test01 LICENSE.txt maven.xml project.properties project.xml ear/src/plugin-test/test01/src/application/META-INF

cvs commit: maven-plugins/ear/src/plugin-test/test01/src/resources - New directory

felipeal2004/10/19 19:27:20 maven-plugins/ear/src/plugin-test/test01/src/resources - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/ear/src/plugin-test/test01/src/application/META-INF - New directory

felipeal2004/10/19 19:27:20 maven-plugins/ear/src/plugin-test/test01/src/application/META-INF - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/ear/src/plugin-test/test01/src/application - New directory

felipeal2004/10/19 19:27:20 maven-plugins/ear/src/plugin-test/test01/src/application - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/ear/src/plugin-test/test01/src - New directory

felipeal2004/10/19 19:27:20 maven-plugins/ear/src/plugin-test/test01/src - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/ear/src/plugin-test/test01 - New directory

felipeal2004/10/19 19:26:38 maven-plugins/ear/src/plugin-test/test01 - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [jira] Updated: (MPARTIFACT-18) Need a property to specify what value should be used for a snapshot deploy.

Felipe, Just changed the fix for because it needs to be addressed in the next release - whether it takes on wagon or not. The resolution may well be won't fix. To be honest, I don't have the bandwidth to discuss these things at the moment. I'm flat out. - Brett Quoting Felipe Leme <[EMAIL PROTE

Re: [jira] Updated: (MPARTIFACT-18) Need a property to specify what value should be used for a snapshot deploy.

Hi Brett, You changed the 'Fix Version' for this bug, but it's being pretty much dormant since I proposed the fix: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=877620 So, what's up? Should we continue the thread above and then finalize the bug (fixing it or marking it as

[jira] Updated: (MPEAR-22) The ear plugin needs to have a settable manifest Class-Path like the WAR plugin

The following issue has been updated: Updater: Wiley Fuller (mailto:[EMAIL PROTECTED]) Date: Tue, 19 Oct 2004 8:11 PM Comment: This patch enables the use of the 'ear.manifest.classpath' property for dependencies. The implementation is virtually identical to the implementation in t

can't create an issue on jira

Dear maveners 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 ? PS : I have a patch for the issue :-) Regards Julien - To unsubscribe, e-mail: [EMAIL PR

[jira] Created: (MPPDF-20) add author names to generated pdf

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPPDF-20 Here is an overview of the issue: - Key: M

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

I also think that having a single directory for both "standard" and "test" resources is pretty unusual and should be discouraged... a common project layout is usually something like: src/ main resources test test-resources said that, I would like to see the include resource property ON by

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

Personnally, I think that duplicate resource declaration is a bad conception of directory structure. It isn't readable, and it's necessary to check the pom for know which file go to which directory. I'm -0 for rework the plugin for accept this bad conception. Emmanuel - Original Message

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

There is no way the test resources should be in src/conf. It should be discouraged (although not broken :) That said, I think the current fix is correct. - Brett Eric Pugh wrote: Hi all, A while ago some patches where made that allowed the elements to be added to the Eclipse .classpath. This lo

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

Hi all, A while ago some patches where made that allowed the elements to be added to the Eclipse .classpath. This looked good, and I committed it. However, as I have gone on with more testing, I think this needs to be reworked. What happens is right now the resources for the regular java files

[jira] Commented: (MPCLOVER-26) Update to clover-ant-1.3_02.jar

The following comment has been added to this issue: Author: Gary Gregory Created: Tue, 19 Oct 2004 3:23 PM Body: Well, it looks like there is a version 1.3.1 now; see http://www.cenqua.com/forums/thread.jspa?threadID=985&tstart=0. --

[jira] Created: (MPCLOVER-26) Update to clover-ant-1.3_02.jar

Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPCLOVER-26 Here is an overview of the issue: - Key

[jira] Commented: (MPCHECKSTYLE-20) Unable to get class information for custom exceptions

The following comment has been added to this issue: Author: Pål Brattberg Created: Tue, 19 Oct 2004 2:17 PM Body: I may have the time to look at this at a later time, but for now, here is a work around which may or may not help you out. http://www.palbrattberg.com/index.php?p=46

[jira] Updated: (MPPMD-14) PMD should run on unit tests

The following issue has been updated: Updater: Sebastian Esponda (mailto:[EMAIL PROTECTED]) Date: Tue, 19 Oct 2004 12:58 PM Comment: We needed PMD to analyze our tests sources, so we did some changes: Plugin.jelly: If ${pom.build.unitTestSourceDirectory} points to a valid director

[jira] Closed: (MPCRUISECONTROL-14) More flexible configuration

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Tue, 19 Oct 2004 12:12 PM Take a looksee. At somepoint this cruisecontrol.jsl file is going to be just TOO configurable. May want to add some sort of simple-cruisecontrol.jsl with minimal settings..

cvs commit: maven-plugins/cruisecontrol plugin.properties

epugh 2004/10/19 09:10:44 Modified:cruisecontrol/xdocs changes.xml cruisecontrol/src/plugin-resources cruisecontrol.jsl cruisecontrol plugin.properties Log: MPCRUISECONTROL-14 More flexible configuration Revision ChangesPath 1.18 +1

[jira] Closed: (MPCRUISECONTROL-13) plugin:test complains about scm method

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Tue, 19 Oct 2004 12:04 PM I changed the patch to maven:get and also fixed some other unit test errors that had been introduced. Can you verify everything builds for you as well? -

cvs commit: maven-plugins/cruisecontrol/src/plugin-test/cvs-scm maven.xml project.properties

epugh 2004/10/19 09:02:22 Modified:cruisecontrol/src/plugin-test/svn-scm project.properties maven.xml cruisecontrol/src/plugin-test/cvs-scm maven.xml project.properties Log: Fix tests that had broken in earlier commit o

Upgrade Maven

Hi, is there any documentation explaining how to upgrade from 1.0beta7 to release 1.0? Alexis

[jira] Commented: (MAVEN-156) classpath or jelly:xml issue with XSLT transformations

The following comment has been added to this issue: Author: Sergey Tereschenko Created: Tue, 19 Oct 2004 11:08 AM Body: Solution from FAQ 4.9. "How do I get the XSLT tasks to work?" really don`t work under JDK 5.0. I hack this bug in maven xml with string: ${systemScope.setProper

RE: cvs commit: maven-plugins/eclipse/xdocs changes.xml

See my other email (which was queued up in my outbox, ARGH!) > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 19, 2004 3:19 PM > To: Maven Developers List > Subject: Re: cvs commit: maven-plugins/eclipse/xdocs changes.xml > > > Why you do thi

Re: A question about Jelly

Hi Brett Thank's it help me a lot. I also want to embedded jelly in our project. And these explanations are very usefull for me. Maven use jelly in a nice way. But may be is it a way to embedded maven to benefits of pluggins facilities ? Best regards Andre Brett Porter wrote: I'll answer the spec

Re: cvs commit: maven-plugins/eclipse/xdocs changes.xml

Why you do this? Emmanuel - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 19, 2004 4:13 PM Subject: cvs commit: maven-plugins/eclipse/xdocs changes.xml > epugh 2004/10/19 07:13:04 > > Modified:eclipse plugin.properties plugin.j

cvs commit: maven-plugins/eclipse/xdocs changes.xml

epugh 2004/10/19 07:13:04 Modified:eclipse plugin.properties plugin.jelly eclipse/src/plugin-resources/templates classpath.jelly eclipse/src/plugin-test maven.xml eclipse/xdocs changes.xml Log: Turn off the inclusion of pom build resour

Re: [Fwd: Re: Is maven.final.name deprecated?]

It was sending both the list reply-to and one for me. I've changed a config - let's see if this helps... Jason van Zyl wrote: Message meant for the list, Brett your reply-to points to you :-) Subject: Re: Is maven.final.

[Fwd: Re: Is maven.final.name deprecated?]

Message meant for the list, Brett your reply-to points to you :-) -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on you

[jira] Commented: (MPECLIPSE-8) Support shared Eclipse launch configurations

The following comment has been added to this issue: Author: Charlie Dobbie Created: Tue, 19 Oct 2004 9:15 AM Body: Sorry, the project I really needed that function for ended some time ago. After 11 months without any activity I rather gave up on anything being done. Basically it

Re: A question about Jelly

I'll answer the specific questions inline, but to give you some focus - you don't need to know how Maven uses Jelly to be able to use Jelly. You are probably only interested in how Jelly is built with Maven. A Leg wrote: Hi I am looking to work on patches for JellySwt to be able to use it. T do

Re: Is maven.final.name deprecated?

I'll start by rounding up thoughts, with specific answer below to the last email. Let me sum up where I think we're at here: - artifact separation. We've talked about this on the maven and m2-dev lists a lot in the last 6 months and thinking through all the issues concluded that one project = o

[jira] Closed: (MPECLIPSE-45) maven.eclipse.classpath.include.output

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Tue, 19 Oct 2004 8:01 AM As far as I can tell, everything works fine for webapp development. - View the issue: http://jira.codehaus.org

[jira] Closed: (MPECLIPSE-26) Add a property to dependencies to link to source

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Tue, 19 Oct 2004 7:59 AM See MPECLIPSE-48 handling source attachments (patch), this has been added in a limited fashion. - View the iss

[jira] Closed: (MPECLIPSE-8) Support shared Eclipse launch configurations

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Tue, 19 Oct 2004 8:00 AM Over a year old, time to close it! - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-8 Here is an o

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

The following comment has been added to this issue: Author: David Eric Pugh Created: Tue, 19 Oct 2004 7:58 AM Body: I have applied and committed the patch. However, i think this introduced a bug.. the src/java directory is being added multiple times now... --

[jira] Closed: (MPECLIPSE-50) Support for Eclipse-Plugin maven projects (or kind="con" classpath)

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Tue, 19 Oct 2004 7:56 AM Please check out the unit test that I added.. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-50

cvs commit: maven-plugins/eclipse/xdocs changes.xml properties.xml

epugh 2004/10/19 04:55:28 Modified:eclipse/src/plugin-resources/templates classpath.jelly eclipse/src/plugin-test maven.xml eclipse/xdocs changes.xml properties.xml Log: MPECLIPSE-50 Support for Eclipse-Plugin maven projects (or kind="con" classpath)