Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Mon, 9 Aug 2004 10:43 AM
Can you supply a patch file and then reopen this bug? Not being a Eclipse plugin
developer (although sometime soon I'll start!) I want to make sure I have an exact
example. Also, please apply a unit test, look in src/plugin-test for examples.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-34
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-34
Summary: Support for creating maven plugins by adding maven.eclipse.con.include
Type: Improvement
Status: Closed
Priority: Major
Resolution: INCOMPLETE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Fix Fors:
1.8
Versions:
1.8
Assignee:
Reporter: Archimedes Trajano
Created: Fri, 25 Jun 2004 11:11 PM
Updated: Mon, 9 Aug 2004 10:43 AM
Description:
In classpath.jelly we can add
<u:tokenize var="maven.eclipse.con.include.split"
delim=",">${maven.eclipse.con.include}</u:tokenize>
<j:forEach var="res" items="${maven.eclipse.classpath.include.split}">
<classpathentry kind="con" path="${res}"/>
</j:forEach>
So we can add
maven.eclipse.con.include=org.eclipse.pde.core.requiredPlugins
to the project.properties file to make it support Eclipse 3.0 plugin creation.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]