Dain and I had talked about this on Friday. I think the direction needs to be to NOT have user
artifacts in the Geronimo repo its just the way it is right now. I think the idea of making a
groupId of user-apps is fine. Perhaps something like installedJ2EEApps would catch someone's eye
faster.
Dave Colasurdo wrote:
Keeping with the theme of talking to myself..
I guess it is simpler to just change the groupid in the sample
deployment plans to user-apps. Of course users are free to specify any
groupid they want .. but the default in the sample plans that we provide
(including our documentation) will result in the user applications being
separated from the geronimo plumbing by naming convention without any
code impact..
-Dave-
Dave Colasurdo wrote:
This reminds me of a topic from a few weeks ago.. Is there a JIRA
open to address separating the end user applications from the geronimo
internal plumbing?
Specifically, /Geronimo-1.1/repository/geronimo/ seems like a strange
spot for end user applications. Searching for deployed applications
seems a bit like looking for a needle in the haystack.
/Geronimo-1.1/repository/ has nearly 40 directories
/Geronimo-1.1/repository/geronimo has nearly 70 directories.
How about a simple /Geronimo-1.1/user-apps/ that contains only
deployed user applications?
Thanks
-Dave-
David Jencks (JIRA) wrote:
remove config-store directories from assemblies, now that they aren't
used any more
-----------------------------------------------------------------------------------
Key: GERONIMO-1932
URL: http://issues.apache.org/jira/browse/GERONIMO-1932
Project: Geronimo
Type: Bug
Security: public (Regular issues) Components: buildsystem
Versions: 1.1 Reporter: David Jencks
Assigned to: David Jencks Fix For: 1.1
modify the assembly plugin to not create the bogus empty unused
obsolete config-store directory
