Another thing is that the convention plugin is using
java.util.logging.*. I think we should stick to what we have in core
and everywhere else.
musachy
On Mon, May 12, 2008 at 6:26 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> Ok, I will let Brian clean that up then.
>
> musachy
>
>
>
> On Mo
+1
On Tue, May 13, 2008 at 9:14 AM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> Another thing is that the convention plugin is using
> java.util.logging.*. I think we should stick to what we have in core
> and everywhere else.
>
> musachy
>
Agreed.
Musachy Barroso wrote:
Another thing is that the convention plugin is using
java.util.logging.*. I think we should stick to what we have in core
and everywhere else.
musachy
On Mon, May 12, 2008 at 6:26 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
Ok, I will let Brian clean that
It was a port of SmartURLs and I didn't get everything totally cleaned
up before getting so busy I could barely check my email ;). I'll remove
them.
-bp
Don Brown wrote:
You can remove the author tags, but only the author can remove
copyright headers, unfortunately.
BTW, how did code get che
Done
On Tue, May 13, 2008 at 10:58 AM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> Agreed.
>
>
>
>
> Musachy Barroso wrote:
>
> > Another thing is that the convention plugin is using
> > java.util.logging.*. I think we should stick to what we have in core
> > and everywhere else.
> >
> > musach
I have deployed 2.1.1 and I get the same result. I would like to mention that
the error occurs only if Security [either Basic or form based] is enabled [
users are authenticated agains LDAP server by WAS container]. That is say, if I
enter https://localhost:9445/ccol/index.html , I get prompted
I committed all of the copyright changes and author tags changes. It
seems that all of the copyrights were correct, however, the IntelliJ
copyright plugin decided to add in the old copyright in addition to the
new ASF copyright. So, everything was still all ASL v2, but some files
had dual assig
I have been playing with the plugin since yesterday, and everything
that is documented here:
http://cwiki.apache.org/S2PLUGINS/convention-plugin.html
seems to be working fine. Is there anything you are aware of that
would prevent us from moving it out of the sandbox?
musachy
On Tue, May 13, 200
With the addition of @IntereceptorRefs to the Convention plugin, it is
now possible to do most of the action mapping using annotations. Also
having 2 plugins to do the same thing is really confusing for users,
so we should deprecate Zero Config (good thing is that it was always
"experimental").
If
+1
On Tue, May 13, 2008 at 9:39 PM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> With the addition of @IntereceptorRefs to the Convention plugin, it is
> now possible to do most of the action mapping using annotations. Also
> having 2 plugins to do the same thing is really confusing for users,
>
-1. Move the features of Convention into Zero Config.
On Tue, May 13, 2008 at 10:56 PM, Matt Raible <[EMAIL PROTECTED]> wrote:
> +1
>
> On Tue, May 13, 2008 at 9:39 PM, Musachy Barroso <[EMAIL PROTECTED]>
> wrote:
> > With the addition of @IntereceptorRefs to the Convention plugin, it is
> > now
+1
2008/5/14 Musachy Barroso <[EMAIL PROTECTED]>:
> With the addition of @IntereceptorRefs to the Convention plugin, it is
> now possible to do most of the action mapping using annotations. Also
> having 2 plugins to do the same thing is really confusing for users,
> so we should deprecate Zero C
Has any work been done to support existing zero config applications
with this new plugin? If not, I'd kinda consider that a blocker (-1)
because a sufficiently flexible configuration system should be able to
support multiple conventions. Also, someone will have to sign up to
convert the REST plug
13 matches
Mail list logo
