I always prefix my artifactId(s) with a common prefix - for that reason; e.g.
"myproject-core", "myproject-commons", "myproject-webapp",
"myproject-webapp-jsf", "myproject-webapp-struts", and so on. It lengthens
the names, but makes everything clear (and I don't need to use the
'finalName' property too...)
On 5/15/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
> Hi there,
>
> I've notice that when using maven-idea-plugin, the module name that is
> generated is based solely on artifact id.
>
> Is there a particular reason for this? Why wouldn't it use project name
> instead?
>
> The reason I'm asking this is that we have three maven projects with
> following structure,
>
> project/
> +- common/webapp/
> +- customer/webapp/
>
> Where artifact names are simply the name of the directory (e.g.,
webapp),
> and I use final-name as ${groupId}.${artifactId}-${version} to control
the
> uniqueness of the actual artifacts file name that get generated.
>
> Unfortunatly, with current maven-idea-plugin this results in a module
> naming conflicting within IntelliJ. I think at the very least there
should
> be a way to specify generated IntelliJ module's name, using pom's
project
> name seems like a good idea to me.
>
> Does anyone have any thought on this?
The artifact id is normally unique enough, but your idea is still useful
so please file an issue in JIRA[1].
[1]: http://jira.codehaus.org/browse/MIDEA
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
