I think we should continue to use ARCHETYPE and start planning
towards a 1.0 with the new code base. The current JIRA will need a
clean up to see what issues are still relevant in the new code base,
of course.
- Brett
On 09/04/2007, at 5:02 AM, Franz Allan Valencia See wrote:
Curious,..
Where is the jira issue(s) for this? ..Can't seem to find them :-)
Thanks,
Franz
On 4/1/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 1 Apr 07, at 6:49 AM 1 Apr 07, Milos Kleint wrote:
>
> >>
> >
> > exactly this is a showstopper for me in the current archetype
when I
> > attempted to create an archetype for netbeans module
development. I
> > need to place Bundle.properties and layer.xml file in
resources into
> > the proper package.
> >
>
> That's fine all we need is the right examples to work against.
But in
> your case do you just need the final distributable to have
resources
> in the same package as the classes or do you actually need to
> archetype to mix resources with the sources?
having the resources in the right place at runtime is fine. I know
about targetPath element in resource definition, however I'd rather
stay away from that.
Often people will need to use both the META-INF/services path and the
package named path like: org/codehaus/mevenide/netbeans/xxx.xxx
and it
becomes non-obvious where to put the services when you define the
targetPath.
On top of that localization bundles come here as well, these are
to be
placed in package named path as well, so there's one
Bundle.properties
for for eac package in the module + some gifs etc. And the form
editor
in the IDE is not capable of handling the shortened paths. Also the
module development file templates can have problems with it.
Milos
>
> Jason.
>
> > Milos
> >
> >
---------------------------------------------------------------------
> > 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]
