[jira] Commented: (MPARTIFACT-14) *-pom-version created but not deleted

The following comment has been added to this issue: Author: Matthias Kerkhoff Created: Thu, 24 Jun 2004 2:18 AM Body: Both the xxx.md5 file and the xxx-snapshot-version file are temporary files. The md5 file _is_ deleted after it has been deployed (line 124, 182) so there is no ne

[jira] Commented: (MPARTIFACT-14) *-pom-version created but not deleted

The following comment has been added to this issue: Author: Brett Porter Created: Thu, 24 Jun 2004 1:56 AM Body: there also seems to be a project.xml.md5 - View this comment: http://jira.codehaus.org/browse/MPART

[jira] Reopened: (MPARTIFACT-14) *-pom-version created but not deleted

Message: The following issue has been reopened. Reopener: Brett Porter Date: Thu, 24 Jun 2004 1:56 AM ah, there is a pom-snapshot-version... I found it. Sorry for the confusion - View the issue: http://jira.codeha

[jira] Commented: (MPEJB-11) change the name of the ejb client jar in order to be referenced in pom dependencies

The following comment has been added to this issue: Author: dion gillard Created: Thu, 24 Jun 2004 1:19 AM Body: I believe the second format for the client name makes more sense than the first. - View this comment:

Maven2 (was Re: maven-plugin-plugin generate docs improvement)

>These are all good ideas, however it is probably not worth the effort at this >point. m2's plugins are self documenting in the fashion you are talking about, >and there is a clear direction to start pushing them in to use in maven 1 in the >near future. > Sounds cool. This leads to the following

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

This may all be moot if we decide to postpone any changes until m2 as suggested by Brett, but I'll update the proposal with Dion's comments (and my responses) just in case people want to go ahead with it: > > 1) Ensure backward-compatibility. One solution is to create a property setting > >

[jira] Commented: (MPANNOUNCEMENT-7) [patch] Remove an unnecessary cast to type String

The following comment has been added to this issue: Author: Gary Gregory Created: Wed, 23 Jun 2004 7:56 PM Body: This is not "Major" obviously. but I cannot change the Priority after creating the ticket. - View th

[jira] Updated: (MPANNOUNCEMENT-7) [patch] Remove an unnecessary cast to type String

The following issue has been updated: Updater: Gary Gregory (mailto:[EMAIL PROTECTED]) Date: Wed, 23 Jun 2004 7:55 PM Comment: cvs diff patch. Changes: Attachment changed to patch.txt - For a fu

[jira] Created: (MPANNOUNCEMENT-7) [patch] Remove an unnecessary cast to type String

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

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

On Wed, 23 Jun 2004 11:02:05 -0700, M. Sean Gilligan <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > Thanks for the positive feedback and brainstorming. I made some specific > suggestions on JIRA, I'll repeat them here and incorporate/respond-to some > suggestions made on the list. > > 1) E

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

All, These are all good ideas, however it is probably not worth the effort at this point. m2's plugins are self documenting in the fashion you are talking about, and there is a clear direction to start pushing them in to use in maven 1 in the near future. Hope this helps! Cheers, Brett Quoting

[jira] Commented: (MPARTIFACT-14) *-pom-version created but not deleted

The following comment has been added to this issue: Author: Brett Porter Created: Wed, 23 Jun 2004 7:22 PM Body: Don't you mean *-snapshot-version? This is only ever deployed to the removte repository, so has nothing to do with .cvsignore, etc and shouldn't be deleted. Unless I'm

m2 and Ant taks (was Re: Hibernate plugin use Ant task instead of custom integration)

>On 18:15 Wed 23 Jun , Eric Pugh wrote: >> Argh... You were right about classloader hell.. I was able quite quickly >> to swap it to use the Hibernate SchemaExportTask with a .properties file. >> However, attempting to get the right mix of classpath's etc to get >> SchemaExportTask to work

Re: Hibernate plugin use Ant task instead of custom integration

On 18:15 Wed 23 Jun , Eric Pugh wrote: > Argh... You were right about classloader hell.. I was able quite quickly > to swap it to use the Hibernate SchemaExportTask with a .properties file. > However, attempting to get the right mix of classpath's etc to get > SchemaExportTask to work with

cvs commit: maven-plugins/jnlp/src/main/org/apache/maven/jnlp UpdateManifest.java

evenisse2004/06/23 15:22:00 Modified:jnlp/src/main/org/apache/maven/jnlp UpdateManifest.java Log: remove jdk1.5 keyword. Revision ChangesPath 1.4 +4 -4 maven-plugins/jnlp/src/main/org/apache/maven/jnlp/UpdateManifest.java Index: UpdateManifest.java

cvs commit: maven/src/test/java/org/apache/maven/project OrganizationTest.java

evenisse2004/06/23 14:38:11 Modified:src/test/java/org/apache/maven/project Tag: MAVEN-1_0-BRANCH OrganizationTest.java Log: Trims url and logo. Revision ChangesPath No revision No revision 1.1.10.2 +8 -0

[jira] Created: (MAVEN-1337) Maven plugins docs need updating

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

[jira] Commented: (MPARTIFACT-14) *-pom-version created but not deleted

The following comment has been added to this issue: Author: Matthias Kerkhoff Created: Wed, 23 Jun 2004 2:32 PM Body: The file i mentioned is created from the class DefaultArtifactDeployer. Please have a look at line #145 (today's cvs version), where it is created. Check the res

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

I'd really like to contribute to this task, but I'm not aware of the protocol (for non commiters) to follow since submiting patches to the plugin post 1.0 is not an options, as I guess, and there's no 1.1 brach, or is it? M. Sean Gilligan wrote: Hi Everyone, Thanks for the positive feedback and

RE: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Hi Everyone, Thanks for the positive feedback and brainstorming. I made some specific suggestions on JIRA, I'll repeat them here and incorporate/respond-to some suggestions made on the list. 1) Ensure backward-compatibility. One solution is to create a property setting to cause properties.

[jira] Closed: (MPCRUISECONTROL-1) cruisecontrol:run goal implementation

Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPCRUISECONTROL-1 Here is an overview of the issue: -

Please IGNORE, This post is to the wrong list (was Re: saveErrors...)

Mark R. Diggory wrote: I was looking at the code for Action.saveErrors(...) and was think this is a little inflexible when it comes to error and message management: protected void saveErrors(HttpServletRequest request, ActionMessages errors) { // Remove any error messages attribute

[jira] Closed: (MAVEN-1320) maven --info must sort all installed plugins

Message: The following issue has been closed. Resolver: Emmanuel Venisse Date: Wed, 23 Jun 2004 1:13 PM Applied. Thanks. - View the issue: http://jira.codehaus.org/browse/MAVEN-1320 Here is an overview of the iss

cvs commit: maven/xdocs changes.xml

evenisse2004/06/23 10:12:54 Modified:xdocsTag: MAVEN-1_0-BRANCH changes.xml Log: [MAVEN-1320]. Sort all installed plugins. Revision ChangesPath No revision No revision 1.14.4.23 +3 -0 maven/xdocs/changes.xml Index: cha

cvs commit: maven/src/java/org/apache/maven/plugin PluginManager.java

evenisse2004/06/23 10:11:28 Modified:src/java/org/apache/maven/plugin Tag: MAVEN-1_0-BRANCH PluginManager.java Log: [MAVEN-1320]. Sort all installed plugin. Revision ChangesPath No revision No revision 1.70.4

saveErrors...

I was looking at the code for Action.saveErrors(...) and was think this is a little inflexible when it comes to error and message management: protected void saveErrors(HttpServletRequest request, ActionMessages errors) { // Remove any error messages attribute if none are required

[jira] Commented: (MPCRUISECONTROL-1) cruisecontrol:run goal implementation

The following comment has been added to this issue: Author: Winston Rast Created: Wed, 23 Jun 2004 1:03 PM Body: I'm all good with it. Even if the current run implementation doesn't satisfy, I customized a separate plugin for my own purposes. In fact, I've actually moved away fro

RE: Hibernate plugin use Ant task instead of custom integration

Argh... You were right about classloader hell.. I was able quite quickly to swap it to use the Hibernate SchemaExportTask with a .properties file. However, attempting to get the right mix of classpath's etc to get SchemaExportTask to work with .cfg.xml configuration file has been a very frustra

Re: RE : RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Heritier Arnaud wrote: The problem is that in some plugins, the documentation of goals is very more detailled in the doc than in the plugin.jelly. In the goal's description you can't use HTML tags. For example : http://maven.apache.org/reference/plugins/dist/goals.html HTML in goal documentation

[jira] Commented: (MPECLIPSE-9) Eclipse plugin includes non-classpath dependencies in generated files

The following comment has been added to this issue: Author: Joerg Schaible Created: Wed, 23 Jun 2004 11:52 AM Body: jar and zip please (hello Oracle) - View this comment: http://jira.codehaus.org/browse/MPECLIPSE

RE : RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

> the properties.xml could be generated with a more advanced > parsing and > maybe assuming all properties begin with the plugin name > followed by a '.' The problem will be to standardize the properties documentation and to parse the file. # MY DOC xxx..= > > Should synchro

Re: RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Heritier Arnaud wrote: goals.xml and properties.xml are already generated but the problem is that there's no synchronization. It's only usefull for the first generation. A dynamic goals.xml (and properties.xml if possible) should be a good idea. the properties.xml could be generated with a more

RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

goals.xml and properties.xml are already generated but the problem is that there's no synchronization. It's only usefull for the first generation. A dynamic goals.xml (and properties.xml if possible) should be a good idea. Arnaud > -Message d'origine- > De : Miguel Griffa [mailto:[EMAI

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Hi, I totally agree with this. Generating the goals.xml shuold be quite easy (a simple matter of xsl), the properties.xml may be another story... Having goals.xml generated would contribute to a more uniform documentation M. Sean Gilligan wrote: Hello Dion, et. al., I thought I'd move some

maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Hello Dion, et. al., I thought I'd move some of this (http://jira.codehaus.org/browse/MPPLUGIN-17) discussion off of JIRA and on to the dev list. (I'm not sure what the correct protocol is, so please forgive me if I'm breaking it. I also apologize if a JIRA priority of "major" seems high, I n

[jira] Commented: (MPECLIPSE-9) Eclipse plugin includes non-classpath dependencies in generated files

The following comment has been added to this issue: Author: Miguel Griffa Created: Wed, 23 Jun 2004 10:57 AM Body: I think that a better approach with be include dependencies only when their type is jar. Other type of dependencies shuold be _somehow_ included but certainly (I thin

[jira] Commented: (MPPLUGIN-17) generate-goals and generate-properties should make more than skeletons

The following comment has been added to this issue: Author: M. Sean Gilligan Created: Wed, 23 Jun 2004 10:51 AM Body: The current generate-goals and generate-properties produce xdocs that require additional hand editing. Also, if you update plugin.jelly or plugin.properties, the

[jira] Updated: (MPPLUGIN-18) plugin:repository-deploy not documented on plugins page

The following issue has been updated: Updater: Miguel Griffa (mailto:[EMAIL PROTECTED]) Date: Wed, 23 Jun 2004 10:49 AM Comment: Added description to plugin.jelly and added the goal to the goals.xml doc Changes: Attachment changed to MPPLUGIN-18.patch --

RE: Synced servers on ibiblio

On Wed, 2004-06-23 at 09:23, Jörg Schaible wrote: > Does anybody know where the origin of the OpenSymphony repo is kept and who is > responsible for its contents? There is no hint for such a repo on their site and > there are newer versions of webwork and xwork. For the OS repository, the OS fo

[jira] Commented: (MAVEN-1320) maven --info must sort all installed plugins

The following comment has been added to this issue: Author: Miguel Griffa Created: Wed, 23 Jun 2004 10:17 AM Body: previous patch should fix the issue - View this comment: http://jira.codehaus.org/browse/MAVEN-13

[jira] Closed: (MPTASKLIST-8) The title seems to be Articles instead ot Todos

Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPTASKLIST-8 Here is an overview of the issue: - Ke

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

brett 2004/06/23 07:17:35 Modified:tasklist project.xml tasklist/src/plugin-resources/templates tasklist.vm tasklist/xdocs changes.xml Log: PR: MPTASKLIST-8 fix typo in xdoc title Revision ChangesPath 1.24 +1 -1 maven-plugins/ta

Another 1.0 issue patched

This was a really simple one (I hope it's ok) http://jira.codehaus.org/browse/MAVEN-1320 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (MAVEN-1320) maven --info must sort all installed plugins

The following issue has been updated: Updater: Miguel Griffa (mailto:[EMAIL PROTECTED]) Date: Wed, 23 Jun 2004 10:13 AM Comment: I think this solves the issue in a pretty clean way Changes: Attachment changed to patch-1320.txt ---

[jira] Closed: (MPARTIFACT-4) improve handling of EJB-client and other types, according to ArtifactType class

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 10:10 AM handled differently - need to map the whole path, not just the extension. - View the issue: http://jira.codehaus

[jira] Closed: (MPARTIFACT-14) *-pom-version created but not deleted

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 10:09 AM I can't see how you are producing this file. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-14 He

[jira] Closed: (MPARTIFACT-5) Problem with SCP deployement

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 10:06 AM putty can covert to a valid SSH key I believe. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-5 H

[jira] Closed: (MPARTIFACT-10) artifact:install doesn't resolve references in pom files

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 10:04 AM already implemented in m2 - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-10 Here is an overview o

[jira] Closed: (MPARTIFACT-7) Deploy an special artifact (like maven plugins)

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 9:59 AM this is now fixed - you can provide a custom handler to map to a different path. See the dist plugin for an example. -

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

The following comment has been added to this issue: Author: Brett Porter Created: Wed, 23 Jun 2004 9:54 AM Body: that's somewhat hardwird in at the moment - it will take a while to make this a possibility. - View

Reminder

issue http://jira.codehaus.org/browse/MAVEN-1208 is scheduled to be fixed before 1.0 and has a patch pending closing this shuold be easy any commiter with couple of minutes??? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additio

[jira] Closed: (MPARTIFACT-15) artifact:deploy deploys as plugin extension not as jar

Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-15 Here is an overview of the issue: - K

[jira] Commented: (MAVEN-1332) proxy firewall by NTLM authentication is not supported

The following comment has been added to this issue: Author: george wang Created: Wed, 23 Jun 2004 9:35 AM Body: instead of these two new parameters: #new parameters for this issue maven.proxy.loginHost =myMachineHost maven.proxy.loginDomain =myMachineDomain cvsgrab2.1 only need

[jira] Closed: (MPARTIFACT-2) Add tag attribute to relax the restriction on artifact type and file extension association

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 9:36 AM dist plugin now uses artifact - View the issue: http://jira.codehaus.org/browse/MPARTIFACT-2 Here is an overview

cvs commit: maven-plugins/dist plugin.jelly

brett 2004/06/23 06:29:35 Modified:dist plugin.jelly Log: fix artifact tags project references Revision ChangesPath 1.16 +4 -4 maven-plugins/dist/plugin.jelly Index: plugin.jelly ===

[jira] Closed: (MPEJB-11) change the name of the ejb client jar in order to be referenced in pom dependencies

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 9:27 AM I don't think we should break compatibility "just because". If it is so you can append -client to , try appending it to instead. ---

RE: Synced servers on ibiblio

Jörg Schaible wrote on Monday, June 21, 2004 11:25 PM: > Hi Jason, [snip] > Do you know, where from the OpenSymphony project is synced > from? Looking at > their website, they are obviously using java.net infrastructure now > (https://opensymphony.dev.java.net/) and I cannot detect any location >

RE: Hibernate plugin use Ant task instead of custom integration

> -Original Message- > From: Eric Pugh [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 23, 2004 2:42 PM > To: Maven-Dev > Subject: Hibernate plugin use Ant task instead of custom integration > > > Hi all, > > I noticed a patch a while ago to the list from Konstantin > Shaposhnikov wh

[jira] Closed: (MPXDOC-110) tags can't contain trailing or leading spaces

Message: The following issue has been closed. Resolver: Brett Porter Date: Wed, 23 Jun 2004 9:14 AM trimmed in o.a.m.project.Organization class. Consistent with Project class. - View the issue: http://jira.codehau

cvs commit: maven/src/java/org/apache/maven/project Organization.java

brett 2004/06/23 06:13:27 Modified:src/java/org/apache/maven/project Tag: MAVEN-1_0-BRANCH Organization.java Log: PR: MPXDOC-110 trim logo (and url while I'm at it). Consistent with Project. Revision ChangesPath No revision

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

brett 2004/06/23 06:13:01 Modified:dist plugin.jelly project.properties project.xml dist/xdocs changes.xml Log: switch to the artifact plugin for deployments Revision ChangesPath 1.15 +60 -56maven-plugins/dist/plugin.jelly Index: plugin.

cvs commit: maven-plugins/dist/src/test - New directory

brett 2004/06/23 06:08:51 maven-plugins/dist/src/test - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/test/org - New directory

brett 2004/06/23 06:08:51 maven-plugins/dist/src/test/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/test/org/apache - New directory

brett 2004/06/23 06:08:51 maven-plugins/dist/src/test/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/test/org/apache/maven/dist - New directory

brett 2004/06/23 06:08:51 maven-plugins/dist/src/test/org/apache/maven/dist - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/test/org/apache/maven - New directory

brett 2004/06/23 06:08:51 maven-plugins/dist/src/test/org/apache/maven - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Well known Directory for generated source?

No standard at the moment. Each plugin should define its own in Maven 1.x so that you don't add the source files to the build list more than once. ${maven.build.dir}/generated-src-xdoclet would work Cheers, Brett Quoting Eric Pugh <[EMAIL PROTECTED]>: > Hi all, > > I am looking at MPECLIPSE-5,

cvs commit: maven-plugins/dist/src/main/org/apache/maven - New directory

brett 2004/06/23 06:06:40 maven-plugins/dist/src/main/org/apache/maven - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/main/org/apache/maven/dist - New directory

brett 2004/06/23 06:06:40 maven-plugins/dist/src/main/org/apache/maven/dist - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/main/org - New directory

brett 2004/06/23 06:05:38 maven-plugins/dist/src/main/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/main/org/apache - New directory

brett 2004/06/23 06:05:38 maven-plugins/dist/src/main/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: maven-plugins/dist/src/main - New directory

brett 2004/06/23 06:05:03 maven-plugins/dist/src/main - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

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

brett 2004/06/23 06:04:29 Modified:artifact plugin.jelly project.xml artifact/src/main/org/apache/maven/artifact/deployer ArtifactDeployer.java DefaultArtifactDeployer.java DeployBean.java artifact/xdocs chan

cvs commit: maven/src/java/org/apache/maven/repository ArtifactTypeHandler.java DefaultArtifactTypeHandler.java

brett 2004/06/23 06:00:38 Added: src/java/org/apache/maven/repository Tag: MAVEN-1_0-BRANCH ArtifactTypeHandler.java DefaultArtifactTypeHandler.java Log: temporary type handler for the artifact plugin Revision ChangesPath

cvs commit: maven/xdocs/start anakia.xml

brett 2004/06/23 05:56:19 Modified:xdocsTag: MAVEN-1_0-BRANCH musings.xml status.xml xdocs/misc Tag: MAVEN-1_0-BRANCH tasks.xml xdocs/reference Tag: MAVEN-1_0-BRANCH user-guide.xml xdocs/start Tag: MAVEN-1_0-BRANCH anakia.xml Log: fi

Hibernate plugin use Ant task instead of custom integration

Hi all, I noticed a patch a while ago to the list from Konstantin Shaposhnikov which converted the Hibernate plugin to use the SchemaExportTask that is now available from the main Hibernate jar. I am going to update to using the Ant task as the existing interface to SchemaExport hasn't kept up wi

cvs commit: maven-plugins/idea/src/plugin-resources/templates/v4 module.jelly

brett 2004/06/23 05:28:49 Modified:idea/src/plugin-resources/templates/v4 module.jelly Log: PR: MPIDEA-6 use maven.war.src for webroots Revision ChangesPath 1.7 +3 -1 maven-plugins/idea/src/plugin-resources/templates/v4/module.jelly Index: module.jell

[jira] Closed: (MPIDEA-6) the web module handling should add a web root

Message: The following issue has been closed. - View the issue: http://jira.codehaus.org/browse/MPIDEA-6 Here is an overview of the issue: - Key: M

[jira] Commented: (MPECLIPSE-5) Generated source support

The following comment has been added to this issue: Author: David Eric Pugh Created: Wed, 23 Jun 2004 8:03 AM Body: I think that you are wrong about maven.build.src.. maven.build.src points to the /src directory.. Any generated source should probably be in the /target directory.

Well known Directory for generated source?

Hi all, I am looking at MPECLIPSE-5, and while in the bug the reporter refers to maven.build.src as where generated source goes, and I think that is wrong, is there a well known location for generated source? Something like maven.build.src.generated? I am using xdoclet to build some "source" fil

[jira] Closed: (MPECLIPSE-17) maven.eclipse.classpath.include does not appear to work

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Wed, 23 Jun 2004 7:43 AM This issue was fixed as part of MPECLIPSE-29. - View the issue: http://jira.codehaus.org/browse/MPECLIPSE-17

[jira] Commented: (MAVENUPLOAD-145) Spring 1.0.2

The following comment has been added to this issue: Author: Alef Arendsen Created: Wed, 23 Jun 2004 7:35 AM Body: Guys, I didn't notice you require a project.xml now. I'll update the file to include it... Alef -

[jira] Created: (MAVEN-1335) Docs: User guide should reference POM spec

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

[jira] Created: (MAVEN-1336) Docs: Please clarify plugin plugin

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

[jira] Reopened: (MPXDOC-91) bundled css files contain no filter tokens for ui property values

Message: The following issue has been reopened. Reopener: Brett Porter Date: Wed, 23 Jun 2004 6:56 AM reopening to address previous comment - View the issue: http://jira.codehaus.org/browse/MPXDOC-91 Here is an

cvs commit: maven-plugins/cruisecontrol project.xml

epugh 2004/06/23 03:31:52 Modified:cruisecontrol project.xml Log: Fix issue tracking url reported by Carlos Sanchez. MPCRUISECONTROL-4 Revision ChangesPath 1.24 +1 -0 maven-plugins/cruisecontrol/project.xml Index: project.xml ==

[jira] Closed: (MPCRUISECONTROL-4) Incorrect issueTrackingUrl

Message: The following issue has been closed. Resolver: David Eric Pugh Date: Wed, 23 Jun 2004 6:33 AM Patch applied. As far as I'm concerned, fixes of this nature can be applied by anyone. - View the issue: h

[jira] Commented: (MPCRUISECONTROL-1) cruisecontrol:run goal implementation

The following comment has been added to this issue: Author: David Eric Pugh Created: Wed, 23 Jun 2004 6:36 AM Body: Winston.. I think that either your patch was applied, or someone else added a cruisecontrol:run goal.. I looked, and how things stand now seems more or less simil

[jira] Created: (MPLINKCHECK-14) Stack trace when Connection refused

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

[jira] Created: (MPCRUISECONTROL-4) Incorrect issueTrackingUrl

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

[jira] Updated: (MPCRUISECONTROL-4) Incorrect issueTrackingUrl

The following issue has been updated: Updater: Carlos Sanchez (mailto:[EMAIL PROTECTED]) Date: Wed, 23 Jun 2004 4:49 AM Comment: Just tell me if you want me to commit this small changes next time. Changes: Attachment changed to patch.txt

[jira] Created: (MPFAQ-13) CDATA sections are transformed

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