[jira] Updated: (MECLIPSE-235) Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.

2007-11-29 Thread Arnaud Heritier (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-235: - Component/s: Dependencies resolution and build path Eclipse Maven plugin has its own

[jira] Updated: (MECLIPSE-235) Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.

2007-11-01 Thread Arnaud Heritier (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-235: - Fix Version/s: (was: 2.5) Eclipse Maven plugin has its own Classpath Container that

[jira] Updated: (MECLIPSE-235) Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.

2007-10-02 Thread Hasan Ceylan (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hasan Ceylan updated MECLIPSE-235: -- Attachment: q4t_patch.txt Hello, I am back Firstly, I really liked your solution. Secondly, the

[jira] Updated: (MECLIPSE-235) Eclipse Maven plugin has its own Classpath Container that conflicts with generated class paths when enabled.

2007-06-28 Thread Brian Fox (JIRA)
[ http://jira.codehaus.org/browse/MECLIPSE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MECLIPSE-235: --- Fix Version/s: (was: 2.4) 2.5 Eclipse Maven plugin has its own Classpath