[ http://jira.codehaus.org/browse/MECLIPSE-46?page=all ]
Jason van Zyl moved MNG-907 to MECLIPSE-46:
-------------------------------------------
Version: (was: 2.0-beta-1)
Fix Version: (was: 2.0-beta-2)
type: Bug (was: Improvement)
Component: (was: maven-eclipse-plugin)
Workflow: jira (was: Maven)
Key: MECLIPSE-46 (was: MNG-907)
Project: Maven 2.x Eclipse Plugin (was: Maven 2)
> The eclipse output directory should configurable. I would be nice to pick
> something other than target/classes.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-46
> URL: http://jira.codehaus.org/browse/MECLIPSE-46
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Reporter: Hiram Chirino
> Assignee: John Casey
> Attachments: patch
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining: 0 minutes
>
> The output directory eclipse:eclipse uses, should be configurable. I chatted
> with jdcasey on irc about it:
> [5:14pm] hchirino: it really should not spit it's output to target/classes
> [5:14pm] jdcasey: maybe kenney and trygvis...not too sure
> [5:14pm] jason: trygvis made the first version, but it's had a lot of work on
> it
> [5:16pm] hchirino: The problem is you could save a file with a compiler error
> in eclipse, do a m2 build and the m2 build succeeds since eclipse writes a
> .class file even though it had an error.
> [5:16pm] jdcasey: yikes
> [5:16pm] jdcasey: yeah, eclipse uses /bin by default iirc
> [5:17pm] jdcasey: and I've had to separate the maven-generated classes from
> the eclipse ones in the past, too...
> [5:17pm] hchirino: yep me too.
> [5:17pm] hchirino: I've had do "maven clean default" many times after editing
> in eclipse as it adds extra stuff sometimes.
> [5:19pm] hchirino: The big debate in my mind is if we do use a different
> folder for eclipse, should it be under target? in other words, should clean
> wipe out the eclipse .class files? Every time that happens I have to do a
> big eclipse refresh that takes forever.
> [5:19pm] hchirino: And if I wanted to do that, eclipse provides a 'clean'
> feature too.
> [5:21pm] hchirino: where do the eclipse plugin live?
> [5:21pm] hchirino: perhaps I can hack it up a bit.
> [5:24pm] jdcasey: hchirino: the eclipse plugin is in mojo.codehaus.org
> [5:24pm] jdcasey: I'd put the classfiles in the default eclipse /bin dir, and
> keep them separate from the maven target dir, personally
> [5:25pm] hchirino: yeah. that's what i'm leaning towards too
> [5:25pm] jdcasey: they shouldn't be touched by m2 clean:clean IMO...it just
> makes another filter for svn commits, though
> [5:25pm] jdcasey: no point in deviating from the default if it doesn't get
> you anything, right?
> [5:25pm] hchirino: I guess I could put it in .bin ;-)
> I'm attaching a patch that makes it configurable.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
