Wendy Smoak wrote:
That (the ability to 'package' non-Java resources) was a problem in
the old archetype plugin, I think it's fixed in the new (v2) one.
Is that done via the archetype-metadata file, or is it "automagic" now?
I thought I had the most current archetype plugin, but I'm still not
Hi,
As I understood, you want to copy *.properties and *.xml files base on
groupId (package name). If so take a look on that [1], on attached
patch. You can specify how to copy files with archetype-metadata.xml
file.
[1] https://issues.apache.org/struts/browse/WW-2911
Regards
--
Lukasz
http://
On Fri, Dec 26, 2008 at 8:18 AM, Dave Newton wrote:
> The resources, at least; for example I'm working on struts2-blank-archetype.
> The Java code is moved, the resources aren't, so the tests fail because the
> package.properties isn't in the correct location.
That (the ability to 'package' no
> Can you be more specific about what's not going into the right place?
The resources, at least; for example I'm working on struts2-blank-archetype.
The Java code is moved, the resources aren't, so the tests fail because the
package.properties isn't in the correct location.
In the Java code the
On Fri, Dec 26, 2008 at 6:17 AM, Dave Newton wrote:
> I think this is a documented archetype issue, but it makes archetypes a
> little less useful: if I'm creating a project from an archetype and give it a
> groupId (package) how come it only puts *some* of the stuff in the
> appropriate classp
I think this is a documented archetype issue, but it makes archetypes a little
less useful: if I'm creating a project from an archetype and give it a groupId
(package) how come it only puts *some* of the stuff in the appropriate
classpath?
And do I really not have access to the groupId etc. in
