On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst
<[email protected]> wrote:
> In my opinion MECLIPSE-443 is a very bad idea. Should every plugin be
> configured so that the resources available in src/main/java are
> treated as classpath entries?
It was my understanding that if you had resources in src/main/java
that Maven would not package these.
They must be in src/main/resources.
What is wrong with configuring your ide to behave how Maven behaves?
This will stop you having moments where it works in Eclipse but Maven fails.
> According to me the eclipse plugin
> should take the <resources> part of the pom into account, rather than
> invent yet another way of specifying where resources live.
The plugin takes it diirectly from the in memory copy of the pom via
project.getBuild().getResources() as can be seen in the code below.
It does not invent another way of specifying where resources live.
>From EclipsePlugin.buildDirectoryList():
extractResourceDirs( mainDirectories,
project.getBuild().getResources(), basedir, projectBaseDir, false,
mainOutput );
> This "fix" break so many existing builds and archetypes it is not fun
> anymore. I for one don't like being the helpdesk for maven on the
> Wicket user list.
Can you be specific about what breaks?
Which files, why they are in src/main/java and not somewhere else, etc.
We are aware that this has caused pain, especially for AJDT, which is
why 2.7 automatically includes *.aj on the source directories. See
http://jira.codehaus.org/browse/MECLIPSE-538
For other edge cases 2.7 added
http://jira.codehaus.org/browse/MECLIPSE-104, which allows you to
configure what files can be included/excluded from source directories.
Without specifics it is impossible to fix your complaint.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
