Re: dna-dev Digest, Vol 5, Issue 4
by Serge Pagop
For my point of view, this change will bring a better organization in
the DNA 0.2 project.
Take care and have a good weekend.
dna-dev-request(a)lists.jboss.org wrote:
> Send dna-dev mailing list submissions to
> dna-dev(a)lists.jboss.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.jboss.org/mailman/listinfo/dna-dev
> or, via email, send a message with subject or body 'help' to
> dna-dev-request(a)lists.jboss.org
>
> You can reach the person managing the list at
> dna-dev-owner(a)lists.jboss.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dna-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Response requested: When can we move some Maven projects
> around? (Randall Hauch)
> 2. Re: dna-dev Digest, Vol 5, Issue 3 (sp(a)innoq.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 7 Aug 2008 17:06:30 -0500
> From: Randall Hauch <rhauch(a)redhat.com>
> Subject: Re: [dna-dev] Response requested: When can we move some Maven
> projects around?
> To: Randall Hauch <rhauch(a)redhat.com>
> Cc: JBoss DNA <dna-dev(a)lists.jboss.org>
> Message-ID: <C6ECA00C-7732-4513-9C06-6E2ED66D9BCF(a)redhat.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Any responses to this? I've heard nothing yet.
>
> On Aug 6, 2008, at 11:30 AM, Randall Hauch wrote:
>
>
>> DNA 0.1 introduced the concept of a sequencer, and we created a
>> "sequencers" folder (under trunk) where we've been putting the
>> projects that provide sequencer implementations. With DNA 0.2,
>> we've also introduced the concept of a connector and - not
>> surprisingly - placed all of the connector implementations in
>> projects under a "connectors" folder (under trunk). Recently we
>> introduced a third kind of extension point: the MIME type detector.
>> We currently have only one implementation, but there certainly is
>> the possibility that we'll have more. And really, the "dna-maven-
>> classloader" is another type of extension.
>>
>> But three different types of "extensions" doth make a pattern, and I
>> wouldn't be surprised if we have more. Rather than have different
>> folders under trunk for these different types of extensions, I'd
>> like to make a single "extensions" folder (under trunk) and move all
>> sequencer, connector, MIME type detector, and Maven class loader
>> projects into that one folder. The project naming convention helps
>> keep things clearly identified, all of these extensions really are
>> optional (easier to describe in the documentation), we'll simplify
>> the directory organization, and it will make it easier if any
>> extension project wants to provide more than one type of extension
>> (say, a detector AND a sequencer).
>>
>> I'd like to schedule this to have a minimal impact on our
>> development environments, so please let me know whether tomorrow is
>> a good time to do this. If not, please let me know a time that
>> might work better for you. Feel free to reply to this email or
>> comment directly on https://jira.jboss.org/jira/browse/DNA-191.
>>
>> Best regards,
>>
>> Randall
>> _______________________________________________
>> dna-dev mailing list
>> dna-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/dna-dev
>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 8 Aug 2008 13:18:07 +0200 (CEST)
> From: sp(a)innoq.com
> Subject: [dna-dev] Re: dna-dev Digest, Vol 5, Issue 3
> To: dna-dev(a)lists.jboss.org
> Message-ID: <1612.91.12.23.160.1218194287.squirrel(a)www.innoq.com>
> Content-Type: text/plain;charset=iso-8859-1
>
> Hi randall,
>
> for my site is not a problem, if you close this issue today.
>
> Best regard.
> /Serge
>
>> Send dna-dev mailing list submissions to
>> dna-dev(a)lists.jboss.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.jboss.org/mailman/listinfo/dna-dev
>> or, via email, send a message with subject or body 'help' to
>> dna-dev-request(a)lists.jboss.org
>>
>> You can reach the person managing the list at
>> dna-dev-owner(a)lists.jboss.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of dna-dev digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Response requested: When can we move some Maven projects
>> around? (Randall Hauch)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 6 Aug 2008 11:30:36 -0500
>> From: Randall Hauch <rhauch(a)redhat.com>
>> Subject: [dna-dev] Response requested: When can we move some Maven
>> projects around?
>> To: JBoss DNA <dna-dev(a)lists.jboss.org>
>> Message-ID: <97A0BF7D-5A20-4637-BEB3-A8A9CF52574F(a)redhat.com>
>> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>>
>> DNA 0.1 introduced the concept of a sequencer, and we created a
>> "sequencers" folder (under trunk) where we've been putting the
>> projects that provide sequencer implementations. With DNA 0.2, we've
>> also introduced the concept of a connector and - not surprisingly -
>> placed all of the connector implementations in projects under a
>> "connectors" folder (under trunk). Recently we introduced a third
>> kind of extension point: the MIME type detector. We currently have
>> only one implementation, but there certainly is the possibility that
>> we'll have more. And really, the "dna-maven-classloader" is another
>> type of extension.
>>
>> But three different types of "extensions" doth make a pattern, and I
>> wouldn't be surprised if we have more. Rather than have different
>> folders under trunk for these different types of extensions, I'd like
>> to make a single "extensions" folder (under trunk) and move all
>> sequencer, connector, MIME type detector, and Maven class loader
>> projects into that one folder. The project naming convention helps
>> keep things clearly identified, all of these extensions really are
>> optional (easier to describe in the documentation), we'll simplify the
>> directory organization, and it will make it easier if any extension
>> project wants to provide more than one type of extension (say, a
>> detector AND a sequencer).
>>
>> I'd like to schedule this to have a minimal impact on our development
>> environments, so please let me know whether tomorrow is a good time to
>> do this. If not, please let me know a time that might work better for
>> you. Feel free to reply to this email or comment directly on
>> https://jira.jboss.org/jira/browse/DNA-191
>> .
>>
>> Best regards,
>>
>> Randall
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> dna-dev mailing list
>> dna-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/dna-dev
>>
>>
>> End of dna-dev Digest, Vol 5, Issue 3
>> *************************************
>>
>>
>>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> dna-dev mailing list
> dna-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/dna-dev
>
>
> End of dna-dev Digest, Vol 5, Issue 4
> *************************************
>
>
--
------------------
|||| Serge Pagop
|||| Senior Consultant
||||
|||| JBug Munich Founder
||||
|||| innoQ Deutschland GmbH, Halskestr. 17, D-40880 Ratingen, Germany
|||| P: +49 2102 77162-100, M: +49 178 4049592, F: +49 210 277160-1
|||| Mail: serge.pagop(a)innoq.com, Web: http://www.innoq.com
|||| Weblog: http://www.innoq.com/blog/sp
|||| JBug Munich: http://www.jbug-munich.org
17 years, 8 months
Re: dna-dev Digest, Vol 5, Issue 3
by sp＠innoq.com
Hi randall,
for my site is not a problem, if you close this issue today.
Best regard.
/Serge
> Send dna-dev mailing list submissions to
> dna-dev(a)lists.jboss.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.jboss.org/mailman/listinfo/dna-dev
> or, via email, send a message with subject or body 'help' to
> dna-dev-request(a)lists.jboss.org
>
> You can reach the person managing the list at
> dna-dev-owner(a)lists.jboss.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dna-dev digest..."
>
>
> Today's Topics:
>
> 1. Response requested: When can we move some Maven projects
> around? (Randall Hauch)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 6 Aug 2008 11:30:36 -0500
> From: Randall Hauch <rhauch(a)redhat.com>
> Subject: [dna-dev] Response requested: When can we move some Maven
> projects around?
> To: JBoss DNA <dna-dev(a)lists.jboss.org>
> Message-ID: <97A0BF7D-5A20-4637-BEB3-A8A9CF52574F(a)redhat.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> DNA 0.1 introduced the concept of a sequencer, and we created a
> "sequencers" folder (under trunk) where we've been putting the
> projects that provide sequencer implementations. With DNA 0.2, we've
> also introduced the concept of a connector and - not surprisingly -
> placed all of the connector implementations in projects under a
> "connectors" folder (under trunk). Recently we introduced a third
> kind of extension point: the MIME type detector. We currently have
> only one implementation, but there certainly is the possibility that
> we'll have more. And really, the "dna-maven-classloader" is another
> type of extension.
>
> But three different types of "extensions" doth make a pattern, and I
> wouldn't be surprised if we have more. Rather than have different
> folders under trunk for these different types of extensions, I'd like
> to make a single "extensions" folder (under trunk) and move all
> sequencer, connector, MIME type detector, and Maven class loader
> projects into that one folder. The project naming convention helps
> keep things clearly identified, all of these extensions really are
> optional (easier to describe in the documentation), we'll simplify the
> directory organization, and it will make it easier if any extension
> project wants to provide more than one type of extension (say, a
> detector AND a sequencer).
>
> I'd like to schedule this to have a minimal impact on our development
> environments, so please let me know whether tomorrow is a good time to
> do this. If not, please let me know a time that might work better for
> you. Feel free to reply to this email or comment directly on
> https://jira.jboss.org/jira/browse/DNA-191
> .
>
> Best regards,
>
> Randall
>
>
> ------------------------------
>
> _______________________________________________
> dna-dev mailing list
> dna-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/dna-dev
>
>
> End of dna-dev Digest, Vol 5, Issue 3
> *************************************
>
>
17 years, 8 months
Response requested: When can we move some Maven projects around?
by Randall Hauch
DNA 0.1 introduced the concept of a sequencer, and we created a
"sequencers" folder (under trunk) where we've been putting the
projects that provide sequencer implementations. With DNA 0.2, we've
also introduced the concept of a connector and - not surprisingly -
placed all of the connector implementations in projects under a
"connectors" folder (under trunk). Recently we introduced a third
kind of extension point: the MIME type detector. We currently have
only one implementation, but there certainly is the possibility that
we'll have more. And really, the "dna-maven-classloader" is another
type of extension.
But three different types of "extensions" doth make a pattern, and I
wouldn't be surprised if we have more. Rather than have different
folders under trunk for these different types of extensions, I'd like
to make a single "extensions" folder (under trunk) and move all
sequencer, connector, MIME type detector, and Maven class loader
projects into that one folder. The project naming convention helps
keep things clearly identified, all of these extensions really are
optional (easier to describe in the documentation), we'll simplify the
directory organization, and it will make it easier if any extension
project wants to provide more than one type of extension (say, a
detector AND a sequencer).
I'd like to schedule this to have a minimal impact on our development
environments, so please let me know whether tomorrow is a good time to
do this. If not, please let me know a time that might work better for
you. Feel free to reply to this email or comment directly on https://jira.jboss.org/jira/browse/DNA-191
.
Best regards,
Randall
17 years, 8 months
Please review JIRA issues targeted for 0.2
by Randall Hauch
We've made a lot of progress in the last few months. We have a lot of
great functionality - some great sequencers, federation, the start of
a JCR implementation, and lots of improvements.
So while we're getting close to the point where I'd like to release
0.2, there are a number of outstanding issues. Several of them are
pretty major (e.g., JCR and federation) and still under heavy
development, and they'll no doubt drive the release date. There are a
few outstanding issues that don't fall into this category. Please
take a look at the unresolved 0.2 issues (see https://jira.jboss.org/jira/secure/IssueNavigator.jspa?sorter/field=resol...)
.
Specifically, I have questions about:
https://jira.jboss.org/jira/browse/DNA-152 (John, please look at,
since it's should be an easy change to use the new MIME type stuff)
https://jira.jboss.org/jira/browse/DNA-153 (Michael)
https://jira.jboss.org/jira/browse/DNA-172 (Serge)
https://jira.jboss.org/jira/browse/DNA-102 (John, please look at)
https://jira.jboss.org/jira/browse/DNA-114 will be completed when 152
and 153 are completed.
Thanks in advance!
Randall
17 years, 8 months
