[
http://jira.codehaus.org/browse/MECLIPSE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl moved MNG-1054 to MECLIPSE-277:
---------------------------------------------
Fix Version/s: (was: 2.1.x)
Complexity: (was: Intermediate)
Key: MECLIPSE-277 (was: MNG-1054)
Project: Maven 2.x Eclipse Plugin (was: Maven 2)
> EclipsePluginTask to support eclipsePlugin from Antlib
> ------------------------------------------------------
>
> Key: MECLIPSE-277
> URL: http://jira.codehaus.org/browse/MECLIPSE-277
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Reporter: darren hartford
> Attachments: EclipsePluginTask.java
>
>
> An attempt to call an existing Maven2 Eclipse plugin through an Ant task
> using maven-antlib (maven-artifact-ant). Intent is although the primary
> (automated) build system may be Maven/Maven2, the primary development
> environments may -only- be Eclipse or other IDE and not have a system-install
> of Maven available.
> Gave it a shot, but I think I may be running into classloader issues between
> the antlib stuff, the eclipsepluginTask, and the eclipseplugin itself.
> I was hesistant to add to JIRA as I feel like this should be EclipsePlugin
> specific task, but if there truly are classloader issues it may be beyond the
> scope of the plugin writers and may need to go with the Antlib group
> initially.
> My initial test involved maven-eclipse-plugin-2.0-alpha-3,
> maven-plugin-api-2.0-beta-2, and maven-artifact-ant-2.0-beta-1-dep. Attached
> is the attempt that looks pretty simple and clean, but that may be because
> this is more complicated than originally thought ;-)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
