Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: Not version specific
-
Component/s: Development
-
Labels:None
Description
I think I started this convention with the original plugin layout using META-INF/workflow.xml (regretfully so). That directory has special meaning within Java and so I think we should stop using it for configuration files and go back and fix the places where we do use it.
We could allow it to be used still for plugins moving forward to support backward compatibility if desired but I think it should at the very least be deprecated there.
Attachments
Activity
That works for me.
Maven assumes that resources are under <module-name>/src/main/resources so I think we want to keep that but I don't think it prescribes any meaning to the META-INF directory.
Maybe maven just assume the resources directory, not resources/META-INF... I can't remember right off hand. Were you also thinking of removing the resources directory, or just META-INF where there are no specs?
Maven wants all non-java resources in META-INF by default? I wasn't aware of that. I was thinking more along the lines of all of the configuration files we have that we put in that directory.
Are you just saying for the workflow.xml file? I think this is the default for all non-java resources according to maven.
no longer an issue.