There's no such thing as dumb, just not informed. ;-)
In the "basic" archetypes, the App class looks as follows:
package $package;
public class App {
public static String getHello() {
return "Hello";
}
}
We use svn:externals (which act like symlinks) to pull the basic
archetypes' code into the modular archetypes, so this is the same in
the modular's "web" archetype. However, in the "core" module of
modular archetypes, there's a "core" class that has the following:
// There is no package since the Maven Archetype plugin doesn't
support package expansion
// for multi-module archetypes: http://jira.codehaus.org/browse/
ARCHETYPE-23.
public class Core {
public static String getHello() {
return "Hello";
}
}
It sounds like $package might be in your class - or does it get erased?
Matt
On Feb 14, 2008, at 3:22 PM, Nikolay Karasev wrote:
Matt thanks.
I might be dumb, but could you please elaborate a little? What do you
mean by "it doesn't do package expansion." ?
Is this something AppFuse related or is it in general?
As far as I am concerned, if maven builds App and AppTest just fine,
what is the problem having the classes in their corresponding package
paths?
Thanks,
Nikolay
On Thu, Feb 14, 2008 at 2:14 PM, Matt Raible
<[EMAIL PROTECTED]> wrote:
It's basically a bug in Maven's archetype system - it doesn't do
package expansion. We expect you to delete App and AppTest in your
project.
Matt
On Feb 14, 2008, at 2:00 PM, Nikolay Karasev wrote:
Hi all.
I was using appfuse 1.x a while ago and am now trying to get my
dirty
hands on 2.x
First thing I noticed is: Maven
I did create a project for Spring/Modular (my area of interest) and
noticed this: source files in <root>/core/src/main/java have this
comment:
--------------------------------------------------------------------
--
----------------------------------------------------------
There is no package since the Maven Archetype plugin doesn't support
package expansion
--------------------------------------------------------------------
--
----------------------------------------------------------
Ok, I went then to create a simple Maven project (outside of
appfuse)
and using command
mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app
I got following results:
- set my package to be as: com.nik.app
- have java source file <root>/src/main/java/com/nik/app/App.java
- the App.java declares that it is in fact in package com.nik.app
Now I have a question: why does appfuse not use packages?
Or am I missing something here?
Thanks,
Nikolay
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
