[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

The following comment has been added to this issue: Author: Dan Tran Created: Tue, 4 Jan 2005 1:35 AM Body: I thought we want to use maven's POM to generate elipse's project file. This way we do not have maintain 2 different files. But I can see the impact on existing application

svn commit: r124072 - /maven/maven-1/jelly-tags/trunk/project.xml

Author: brett Date: Mon Jan 3 22:00:27 2005 New Revision: 124072 URL: http://svn.apache.org/viewcvs?view=rev&rev=124072 Log: better JIRA URL Modified: maven/maven-1/jelly-tags/trunk/project.xml Modified: maven/maven-1/jelly-tags/trunk/project.xml Url: http://svn.apache.org/viewcvs/maven/mave

[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

The following comment has been added to this issue: Author: dion gillard Created: Mon, 3 Jan 2005 11:08 PM Body: If the .project exists already, and it's a non-java project, I don't see the point in running the eclipse plugin. Can you clear me up on that? -

[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

The following comment has been added to this issue: Author: Dan Tran Created: Mon, 3 Jan 2005 10:22 PM Body: Our developers create eclipse plugins, I just mavenize them. For my case, they create a eclipse plugin with no java source for documentation purpose. I use maven-eclipse-pl

[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

The following comment has been added to this issue: Author: dion gillard Created: Mon, 3 Jan 2005 10:07 PM Body: So why are you running the eclipse plugin against a documentation project? Eclipse will create the .project file for you automatically.

[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

The following comment has been added to this issue: Author: Dan Tran Created: Mon, 3 Jan 2005 10:04 PM Body: My company has a eclipse documention project plugin which has nojava source. but maven.ecplise.plugin generates java builder, in .project and eclipse fails to load the pro

[jira] Commented: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

The following comment has been added to this issue: Author: dion gillard Created: Mon, 3 Jan 2005 8:48 PM Body: Do you have a use case for this? The usual reason for using this plugin is to put the java dependencies onto the eclipse Build Path for a java project. If you are usin

[jira] Created: (MPECLIPSE-63) dont want the hardcoded org.eclipse.jdt.core.javabuilder

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

[jira] Commented: (MPECLIPSE-62) maven.eclipse.conclasspath is ignored when junit test src is not present

The following comment has been added to this issue: Author: Dan Tran Created: Mon, 3 Jan 2005 7:18 PM Body: the work around to create a empty test source directory - View this comment: http://jira.codehaus.org/br

[jira] Closed: (MPGENAPP-18) Put @NAME@ in display-name for web.xml

Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Mon, 3 Jan 2005 6:06 PM Applied. Thanks. - View the issue: http://jira.codehaus.org/browse/MPGENAPP-18 Here is an overview of the issu

svn commit: r124031 - in maven/maven-1/plugins/trunk/genapp: . src/plugin-resources/complex/template-resources src/plugin-resources/default/template-resources src/plugin-resources/ejb/template-resources src/plugin-resources/struts src/plugin-resources/struts-jstl src/plugin-resources/struts-jstl/template-resources src/plugin-resources/struts/template-resources src/plugin-resources/web src/plugin-resources/web-jstl src/plugin-resources/web-jstl/template-resources src/plugin-resources/web-velocity/template-resources src/plugin-resources/web/template-resources xdocs

Author: aheritier Date: Mon Jan 3 14:53:10 2005 New Revision: 124031 URL: http://svn.apache.org/viewcvs?view=rev&rev=124031 Log: MPGENAPP-18 : Use the project's name as display-name in web.xml. + Switch to subversion Modified: maven/maven-1/plugins/trunk/genapp/project.xml maven/maven-1/p

[jira] Closed: (MAVENUPLOAD-283) display tag library 1.0 upload request

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

[jira] Commented: (MPANT-22) ant:mail error

The following comment has been added to this issue: Author: Arnaud HERITIER Created: Mon, 3 Jan 2005 1:17 PM Body: Where do you use this code ? In your maven.xml ? This error is certainly a problem in the ant task but not in the ant plugin !! The ant plugin goal is to generate an a

svn commit: r124020 - in maven/maven-1/plugins/trunk: antlr appserver clover gump j2ee jalopy java javadoc jdepend site tasklist webserver

Author: aheritier Date: Mon Jan 3 10:00:29 2005 New Revision: 124020 URL: http://svn.apache.org/viewcvs?view=rev&rev=124020 Log: Fix MPXDOC-94 : Files re-saved with a correct UTF-8 encoding. Modified: maven/maven-1/plugins/trunk/antlr/project.xml maven/maven-1/plugins/trunk/appserver/projec

[jira] Closed: (MPXDOC-94) maven-jdepend-plugin: incorrectly encoded project.xml

Message: The following issue has been closed. Resolver: Arnaud HERITIER Date: Mon, 3 Jan 2005 1:09 PM My XML editor complains that the entity declaration (as given in the patch) isn't correct (it seems that a DTD must be specified). I fixed characters with accents and saved files i

[jira] Updated: (MPXDOC-129) Add comment in dependencies

The following issue has been updated: Updater: Arnaud HERITIER (mailto:[EMAIL PROTECTED]) Date: Mon, 3 Jan 2005 12:25 PM Changes: type changed from Bug to New Feature priority changed from Major to Minor -

[jira] Created: (MAVENUPLOAD-283) display tag library 1.0 upload request

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