I am goinging to make a official alpha 1 release (soon) for native-maven-plugin since the windows build is very stable in my environment.
linux and solaris are comming.
-D
On 1/13/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Final Tally:1a. Should we create a mojo-sandbox parent and have sandbox plugins derive from here? This way we can set the scm urls and anything else that comes along here. Only the parent section would need to change when a plugin graduates from the sandbox.+1 Kris, Carlos,Dan,Brett1b. Keep deriving from mojo parent, but add instructions to site to tell devs how to override the scm connection when added to sandbox and add instructions to guidelines for release to have devs remember to remove the override when graduating.-1 Kris,2. Should we correct the plugin names?+1 Kris,Carlos,Dan,Brett3. Should all sandbox plugins be added to the mojo sandbox site?+1 Kris, Carlos,Dan,BrettAdditionally:Brett suggested demoting plugins to the sandbox that haven't been released. This would be -Jboss and Jspc that are trying to do releases shortly.So I will begin working this over the weekend. First by renaming the plugins, then adding the sandbox parent, then updating the sites and releasing snapshots. I'll hold on the demotion until the vote on moving some mojos to apache is finalized to avoid redundant work.I'll need to deploy the sandbox parent before I can deploy the snapshots, I might need help with permissions on that part.
From: Brian E. Fox [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 10, 2006 9:07 PM
To: [email protected]
Subject: [mojo-dev] [vote] Sandbox cleanup
I've been looking at some plugins in the sandbox and I see some issues:1. If sandbox plugins deploy sites, (as they probably should so they get some visability), the scm connections are wrong because they inherit from the mojo parent.2. Some plugins have the name maven-xxx-plugin instead of xxx-maven-plugin3. Many plugins aren't even posted on the mojo site.I'd like to have a vote on these issues:1a. Should we create a mojo-sandbox parent and have sandbox plugins derive from here? This way we can set the scm urls and anything else that comes along here. Only the parent section would need to change when a plugin graduates from the sandbox.- OR-1b. Keep deriving from mojo parent, but add instructions to site to tell devs how to override the scm connection when added to sandbox and add instructions to guidelines for release to have devs remember to remove the override when graduating.2. Should we correct the plugin names?3. Should all sandbox plugins be added to the mojo sandbox site?Thx.
