@author tags in our codebase
by Randall Hauch
I've recently read a suggestions for open source communities that the
author names are removed from the content. In the case of DNA's
codebase, that would mean removing the @author tags. I'm not sure
there was a lot of thought put into using author tags vs. not using
them, but I'd like to reconsider our policy.
What does everyone think about the @author tags? Please reply to all,
stating your opinion (or lack of one).
I'll start. I see a couple of advantages to getting rid of all
@author tags:
When there are no @author tags, then there is a far smaller notion of
ownership by the author(s). On one side of this, the author(s) may
not appreciate changes to "their" code, and on the other side, non-
authors may feel intimidated about working on code for which they are
not an author. IMO, we want to _discourage_ ownership and _encourage_
everyone to work in any area of the code they want.
When there are no @author tags, we don't need a policy that says when
you can add your name to a class/method as an author. I'm not even
sure what our policy is, but I think we're not being consistent (other
than when we create a new class/interface)
@author tags can be inaccurate. SVN has the true history of who
contributed exactly what code.
The only benefit I can think of is that the @author tag does help to
give some notion of who is the "expert" of the class, in case they
need to be consulted. However, I don't believe this is really much of
a reason, since it's far better to consult the SVN history and see who
actually modified the different parts of the code. In fact, the
annotated views in Fisheye even show on many of the lines the name of
the last person to change it. For example, see http://fisheye.jboss.org/browse/DNA/trunk/dna-common/src/main/java/org/jb...
What does everyone think about the @author tags? This isn't an
official vote (we've never had one), but I would like to hear
everyone's thoughts, so please reply to all and let us know what you
think.
Best regards,
Randall
16 years, 11 months
Re: dna-dev Digest, Vol 9, Issue 7 - Hibernate's metadata framework
by Sergey Litsenko
Yes, I've considered using Hibernate's metadata framework, and I've reviewed the Hibernate's code back in 2004 (when I did first release of database metadator), and I did it again hours ago for v.3.3.0.SP1.
The JDBC connector needs to be more dynamic than Hibernate can allow. Hibernate is tuned for ORM stuff only, and it was done for the reason. Hibernate's view of database metadata relying on the concept of org.hibernate.dialect.Dialect classes that needs to be supplied in a configuration (JPA or hibernate.cfg.xml) and/or in POJO annotations. Hibernate will know about relationships between objects only if it will be supplied as part of the mapping.
It is sort of static approach (alhough it is possible to programmatically create configuration) and it mostly limited to tables to classes mapping (again, for a reason) - in other words, Hibernate is trying to see a database metadata through your eyes (mapping, a top-down approach).
Loading table's data is important but it is equally important to get other database metadata. In contrast with Hibernate, the database metadator relying on JDBC metadata provided from connection to dynamically get all neccessary info - and it is more comprehensive - everything that java.sql.DatabaseMetaData provides can be extracted using database metadator - tables, views, indexes, stored procedures, database capabilities (a bottom-up approach).
The JDBC connector needs only database connection URL/user info or Datasource name from JNDI to get all metadata, and it can drive from there.
I was thinking about similar way (I'm talking about concept, not the UI view) like Aqua Data Studio does it - http://www.aquafold.com.
The dna-common-jdbc already has most of the logic needed - we just need a glue for a request processor implementation. BTW, the dna-common-jdbc extracts table's metadata in the same way like org.hibernate.tool.hbm2ddl.
IMO, it is possible to use both in the same project - for example to get metadata - use dna-common-jdbc, to issue datbase update statements use Hibernate. But again, it's not difficult to execute "select" statement based on table name without Hibernate.
Again, don't get me wrong - Hibernate is extremely useful when it comes to objects mapping to tables and persistent operations against defined POJO model (in fact, I'm using the Hibernate 3 for my current projects, and very happy with it). But when it comes to something very dynamic like federated access to databases where we're discovering models by traversing graphs - we need something more than that, and database metadator classes can provide that level of flexibility.
Best regards,
Sergiy
________________________________
From: "dna-dev-request(a)lists.jboss.org" <dna-dev-request(a)lists.jboss.org>
To: dna-dev(a)lists.jboss.org
Sent: Tuesday, 9 December, 2008 3:20:50 AM
Subject: dna-dev Digest, Vol 9, Issue 7
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. FYI: Apache Jackrabbit v. 1.5.0 has been released
(Sergey Litsenko)
2. JDBC metadata connector (Randall Hauch)
3. Build failed in Hudson: DNA continuous on JDK1.5 ? JBoss DNA
JDBC Common model #393 (jboss-qa-internal(a)redhat.com)
4. Build failed in Hudson: DNA continuous on JDK1.5 ? JBoss DNA
JDBC Common model #394 (jboss-qa-internal(a)redhat.com)
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Dec 2008 15:24:23 -0800 (PST)
From: Sergey Litsenko <litsenko_sergey(a)yahoo.com>
Subject: [dna-dev] FYI: Apache Jackrabbit v. 1.5.0 has been released
To: dna-dev(a)lists.jboss.org
Message-ID: <357562.58665.qm(a)web50510.mail.re2.yahoo.com>
Content-Type: text/plain; charset="utf-8"
IMO, The most notable changes are:
1) development preview: JSR 283 features (org.apache.jackrabbit.api.jsr283)
2) jackrabbit-jcr-benchmark component (depends on javax.jcr and on jackrabbit-jcr-tests - JCR API test cases designed for
testing the compliance of an implementation.)
Speaking of reusability the jackrabbit-webdav module can be reused for https://jira.jboss.org/jira/browse/DNA-190 Support accessing repository through WebDAV. It depends on small part of jackrabbit-jcr-commons only - org.apache.jackrabbit.commons.xml.SerializingContentHandler to generate XML output.
Regards,
Sergiy
________________________________
From: "dna-dev-request(a)lists.jboss.org" <dna-dev-request(a)lists.jboss.org>
To: dna-dev(a)lists.jboss.org
Sent: Saturday, 6 December, 2008 5:56:37 AM
Subject: dna-dev Digest, Vol 9, Issue 6
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. Build failed in Hudson: DNA continuous on JDK1.5 ? JBoss DNA
Connector to SVN #388 (jboss-qa-internal(a)redhat.com)
2. Hudson build is back to normal: DNA continuous on JDK1.5 ?
JBoss DNA Connector to SVN #389 (jboss-qa-internal(a)redhat.com)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Dec 2008 10:36:01 -0500 (EST)
From: jboss-qa-internal(a)redhat.com
Subject: [dna-dev] Build failed in Hudson: DNA continuous on JDK1.5 ?
JBoss DNA Connector to SVN #388
To: dna-dev(a)lists.jboss.org, rhauch(a)gmail.com
Message-ID:
<516078381.13271228491361684.JavaMail.hudson(a)hudson1.qa.atl2.redhat.com>
Content-Type: text/plain; charset=us-ascii
See http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss DNA Connector to SVN
[INFO] task-segment: [clean, package]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
[HUDSON] Archiving http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... to /home/hudson/hudson_workspace/jobs/DNA continuous on JDK1.5/modules/org.jboss.dna$dna-connector-svn/builds/2008-12-05_10-32-13/archive/org.jboss.dna/dna-connector-svn/0.4-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[223,86] cannot find symbol
symbol : variable MIME
location: class org.jboss.dna.graph.JcrLexicon
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[223,86] cannot find symbol
symbol : variable MIME
location: class org.jboss.dna.graph.JcrLexicon
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 43 seconds
[INFO] Finished at: Fri Dec 05 10:36:00 EST 2008
[INFO] Final Memory: 62M/353M
[INFO] ------------------------------------------------------------------------
------------------------------
Message: 2
Date: Fri, 5 Dec 2008 11:07:09 -0500 (EST)
From: jboss-qa-internal(a)redhat.com
Subject: [dna-dev] Hudson build is back to normal: DNA continuous on
JDK1.5 ? JBoss DNA Connector to SVN #389
To: dna-dev(a)lists.jboss.org, rhauch(a)gmail.com
Message-ID:
<2103588601.13301228493229923.JavaMail.hudson(a)hudson1.qa.atl2.redhat.com>
Content-Type: text/plain; charset=us-ascii
See http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
------------------------------
_______________________________________________
dna-dev mailing list
dna-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/dna-dev
End of dna-dev Digest, Vol 9, Issue 6
*************************************
Start your day with Yahoo!7 and win a Sony Bravia TV. Enter now http://au.docs.yahoo.com/homepageset/?p1=other&p2=au&p3=tagline
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/dna-dev/attachments/20081207/9e8fe034/at...
------------------------------
Message: 2
Date: Mon, 8 Dec 2008 08:35:29 -0600
From: Randall Hauch <rhauch(a)redhat.com>
Subject: [dna-dev] JDBC metadata connector
To: JBoss DNA <dna-dev(a)lists.jboss.org>
Message-ID: <C06A61F8-ABCA-46CE-8FA2-91CE6BAED768(a)redhat.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Sergiy,
Have you considered using Hibernate's metadata framework? Considering
that Hibernate has verified and tested support for 25 database
management systems, it may very well be worth our while to simply
reuse what they have for extracting metadata. I would think this
approach might offer the broadest coverage with a very small amount of
simple code. Basically, we'd just need to get the list of tables
through JDBC metadata, and then we'd be able to call Hibernate's
framework to load each table (which already handles all the foreign
key functionality).
Thoughts?
Best regards,
Randall
------------------------------
Message: 3
Date: Mon, 8 Dec 2008 11:01:10 -0500 (EST)
From: jboss-qa-internal(a)redhat.com
Subject: [dna-dev] Build failed in Hudson: DNA continuous on JDK1.5 ?
JBoss DNA JDBC Common model #393
To: dna-dev(a)lists.jboss.org, rhauch(a)gmail.com
Message-ID:
<1486165683.31228752070403.JavaMail.hudson(a)hudson1.qa.atl2.redhat.com>
Content-Type: text/plain; charset=us-ascii
See http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss DNA JDBC Common model
[INFO] task-segment: [clean, package]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading: http://repository.jboss.org/maven2/commons-beanutils/commons-beanutils/1....
Downloading: http://apiviz.googlecode.com/svn/site/repo/mvn/release/commons-beanutils/...
Downloading: http://repository.jboss.com/maven2/commons-beanutils/commons-beanutils/1....
Downloading: http://snapshots.jboss.org/maven2/commons-beanutils/commons-beanutils/1.8...
Downloading: http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils/1.8.0/c...
10K downloaded
Downloading: http://repository.jboss.org/maven2/org/apache/commons/commons-parent/11/c...
Downloading: http://apiviz.googlecode.com/svn/site/repo/mvn/release/org/apache/commons...
Downloading: http://repository.jboss.com/maven2/org/apache/commons/commons-parent/11/c...
Downloading: http://snapshots.jboss.org/maven2/org/apache/commons/commons-parent/11/co...
Downloading: http://repo1.maven.org/maven2/org/apache/commons/commons-parent/11/common...
24K downloaded
Downloading: http://repository.jboss.org/maven2/commons-logging/commons-logging/1.1.1/...
17K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '2491c90667a751a5b7a9ba115385bca54bd29d3d'; remote = '76672afb562b9e903674ad3a544cdf2092f1faa3' - RETRYING
Downloading: http://repository.jboss.org/maven2/commons-logging/commons-logging/1.1.1/...
17K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '2491c90667a751a5b7a9ba115385bca54bd29d3d'; remote = '76672afb562b9e903674ad3a544cdf2092f1faa3' - IGNORING
Downloading: http://repository.jboss.org/maven2/org/apache/commons/commons-parent/5/co...
15K downloaded
Downloading: http://repository.jboss.org/maven2/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.pom
Downloading: http://apiviz.googlecode.com/svn/site/repo/mvn/release/hsqldb/hsqldb/1.8....
Downloading: http://repository.jboss.com/maven2/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.pom
Downloading: http://snapshots.jboss.org/maven2/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.pom
Downloading: http://repo1.maven.org/maven2/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.pom
621b downloaded
Downloading: http://repository.jboss.org/maven2/commons-beanutils/commons-beanutils/1....
Downloading: http://apiviz.googlecode.com/svn/site/repo/mvn/release/commons-beanutils/...
Downloading: http://repository.jboss.com/maven2/commons-beanutils/commons-beanutils/1....
Downloading: http://snapshots.jboss.org/maven2/commons-beanutils/commons-beanutils/1.8...
Downloading: http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils/1.8.0/c...
225K downloaded
Downloading: http://repository.jboss.org/maven2/commons-logging/commons-logging/1.1.1/...
59K downloaded
[INFO] [compiler:compile]
[INFO] Compiling 81 source files to http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
[HUDSON] Archiving http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... to /home/hudson/hudson_workspace/jobs/DNA continuous on JDK1.5/modules/org.jboss.dna$dna-common-jdbc/builds/2008-12-08_10-51-52/archive/org.jboss.dna/dna-common-jdbc/0.4-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[103,19] illegal character: \65533
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[1658,15] illegal character: \65533
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[1667,13] illegal character: \65533
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[1667,8] not a statement
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9 minutes 14 seconds
[INFO] Finished at: Mon Dec 08 11:01:09 EST 2008
[INFO] Final Memory: 41M/408M
[INFO] ------------------------------------------------------------------------
------------------------------
Message: 4
Date: Mon, 8 Dec 2008 11:20:35 -0500 (EST)
From: jboss-qa-internal(a)redhat.com
Subject: [dna-dev] Build failed in Hudson: DNA continuous on JDK1.5 ?
JBoss DNA JDBC Common model #394
To: dna-dev(a)lists.jboss.org, rhauch(a)gmail.com
Message-ID:
<2120698925.81228753235529.JavaMail.hudson(a)hudson1.qa.atl2.redhat.com>
Content-Type: text/plain; charset=us-ascii
See http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss DNA JDBC Common model
[INFO] task-segment: [clean, package]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 81 source files to http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
[HUDSON] Archiving http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... to /home/hudson/hudson_workspace/jobs/DNA continuous on JDK1.5/modules/org.jboss.dna$dna-common-jdbc/builds/2008-12-08_11-17-16/archive/org.jboss.dna/dna-common-jdbc/0.4-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[103,19] illegal character: \65533
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[1658,15] illegal character: \65533
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[1667,13] illegal character: \65533
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[1667,8] not a statement
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 15 seconds
[INFO] Finished at: Mon Dec 08 11:20:34 EST 2008
[INFO] Final Memory: 48M/474M
[INFO] ------------------------------------------------------------------------
------------------------------
_______________________________________________
dna-dev mailing list
dna-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/dna-dev
End of dna-dev Digest, Vol 9, Issue 7
*************************************
Start your day with Yahoo!7 and win a Sony Bravia TV. Enter now http://au.docs.yahoo.com/homepageset/?p1=other&p2=au&p3=tagline
17 years
JDBC metadata connector
by Randall Hauch
Sergiy,
Have you considered using Hibernate's metadata framework? Considering
that Hibernate has verified and tested support for 25 database
management systems, it may very well be worth our while to simply
reuse what they have for extracting metadata. I would think this
approach might offer the broadest coverage with a very small amount of
simple code. Basically, we'd just need to get the list of tables
through JDBC metadata, and then we'd be able to call Hibernate's
framework to load each table (which already handles all the foreign
key functionality).
Thoughts?
Best regards,
Randall
17 years
FYI: Apache Jackrabbit v. 1.5.0 has been released
by Sergey Litsenko
IMO, The most notable changes are:
1) development preview: JSR 283 features (org.apache.jackrabbit.api.jsr283)
2) jackrabbit-jcr-benchmark component (depends on javax.jcr and on jackrabbit-jcr-tests - JCR API test cases designed for
testing the compliance of an implementation.)
Speaking of reusability the jackrabbit-webdav module can be reused for https://jira.jboss.org/jira/browse/DNA-190 Support accessing repository through WebDAV. It depends on small part of jackrabbit-jcr-commons only - org.apache.jackrabbit.commons.xml.SerializingContentHandler to generate XML output.
Regards,
Sergiy
________________________________
From: "dna-dev-request(a)lists.jboss.org" <dna-dev-request(a)lists.jboss.org>
To: dna-dev(a)lists.jboss.org
Sent: Saturday, 6 December, 2008 5:56:37 AM
Subject: dna-dev Digest, Vol 9, Issue 6
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. Build failed in Hudson: DNA continuous on JDK1.5 ? JBoss DNA
Connector to SVN #388 (jboss-qa-internal(a)redhat.com)
2. Hudson build is back to normal: DNA continuous on JDK1.5 ?
JBoss DNA Connector to SVN #389 (jboss-qa-internal(a)redhat.com)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Dec 2008 10:36:01 -0500 (EST)
From: jboss-qa-internal(a)redhat.com
Subject: [dna-dev] Build failed in Hudson: DNA continuous on JDK1.5 ?
JBoss DNA Connector to SVN #388
To: dna-dev(a)lists.jboss.org, rhauch(a)gmail.com
Message-ID:
<516078381.13271228491361684.JavaMail.hudson(a)hudson1.qa.atl2.redhat.com>
Content-Type: text/plain; charset=us-ascii
See http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss DNA Connector to SVN
[INFO] task-segment: [clean, package]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 6 source files to http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
[HUDSON] Archiving http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... to /home/hudson/hudson_workspace/jobs/DNA continuous on JDK1.5/modules/org.jboss.dna$dna-connector-svn/builds/2008-12-05_10-32-13/archive/org.jboss.dna/dna-connector-svn/0.4-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[223,86] cannot find symbol
symbol : variable MIME
location: class org.jboss.dna.graph.JcrLexicon
http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org.... :[223,86] cannot find symbol
symbol : variable MIME
location: class org.jboss.dna.graph.JcrLexicon
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 43 seconds
[INFO] Finished at: Fri Dec 05 10:36:00 EST 2008
[INFO] Final Memory: 62M/353M
[INFO] ------------------------------------------------------------------------
------------------------------
Message: 2
Date: Fri, 5 Dec 2008 11:07:09 -0500 (EST)
From: jboss-qa-internal(a)redhat.com
Subject: [dna-dev] Hudson build is back to normal: DNA continuous on
JDK1.5 ? JBoss DNA Connector to SVN #389
To: dna-dev(a)lists.jboss.org, rhauch(a)gmail.com
Message-ID:
<2103588601.13301228493229923.JavaMail.hudson(a)hudson1.qa.atl2.redhat.com>
Content-Type: text/plain; charset=us-ascii
See http://hudson.qa.jboss.com/hudson/job/DNA%20continuous%20on%20JDK1.5/org....
------------------------------
_______________________________________________
dna-dev mailing list
dna-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/dna-dev
End of dna-dev Digest, Vol 9, Issue 6
*************************************
Start your day with Yahoo!7 and win a Sony Bravia TV. Enter now http://au.docs.yahoo.com/homepageset/?p1=other&p2=au&p3=tagline
17 years
Re: [dna-dev] Re: Proposal: new sandbox area for DNA
by John Verhaeg
I'm not sure that answers my question. Why couldn't/shouldn't a project be allowed to exist in more than one branch while development is going on? It seems like this will be important the bigger a project gets.
John Verhaeg
Red Hat, Inc.
(314) 336-2950
----- "Randall Hauch" <rhauch(a)redhat.com> wrote:
| A project either exists in the main area or in the sandbox, but not both. And since the "sandbox" is under "trunk" (at least for now), most of what we're doing stays the same (including the build process, our IDE workspaces, etc.). The only thing that changes that some of the projects would move to a different directory.
|
The main point is to segregate what's "ready" as part of the release vs. stuff that still isn't "ready" when a release is made.
|
|
On Dec 2, 2008, at 11:02 AM, John Verhaeg wrote:
| Wouldn't we potentially have multiple branches other than sandbox where ongoing work is contributed, including when contributors have overlapping changes in the same project?
|
| John Verhaeg
| Red Hat, Inc.
| (314) 336-2950
|
| ----- "Randall Hauch" < rhauch(a)redhat.com > wrote:
| | Any other comments? If not, I'll go ahead and create an issue to make
| | this change at the end of the release.
| |
| | On Nov 25, 2008, at 4:35 PM, Serge Emmanuel Pagop wrote:
| |
| | > Hi all,
| | >
| | > I agree with that proposal with the sandbox area, then dna should be
| | > release with the most stable subprojects and definition of stable
| | > can only be define by the project leader depend on with features the
| | > subproject has to at the least provide.
| | > For me because of the youthfulness of DNA project, we can also
| | > release all subproject, that provide a minimun upon functionalities,
| | > so that we can win some contributors in the community. Of Course "a
| | > minimun upon functionalities" has also to be defined.
| | >
| | > Best regards,
| | > 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. Proposal: new sandbox area for DNA (Randall Hauch)
| | >>
| | >>
| | >> ----------------------------------------------------------------------
| | >>
| | >> Message: 1
| | >> Date: Sun, 23 Nov 2008 11:47:08 -0600
| | >> From: Randall Hauch < rhauch(a)redhat.com >
| | >> Subject: [dna-dev] Proposal: new sandbox area for DNA
| | >> To: JBoss DNA < dna-dev(a)lists.jboss.org >
| | >> Message-ID: < 00474E51-4FBF-4957-937B-B6B8AE4194CD(a)redhat.com >
| | >> Content-Type: text/plain; charset="us-ascii"
| | >>
| | >> I've been wondering recently how to distinguish the (Maven)
| | >> subprojects under trunk that are ready for use vs. those that are
| | >> still under development. In fact, it's not even only the source
| | >> organization, as our release binaries have included all projects
| | >> (regardless of their state). I've tried to note the status in the
| | >> documentation, but I think that is insufficient and we need something
| | >> that is more formal, obvious, and intuitive for users.
| | >>
| | >> The 0.3 release included several projects that were not really "ready
| | >> for use":
| | >> dna-sequencer-cnd
| | >> dna-sequencer-esbMessage
| | >> dna-sequencer-jbpm-jpdl
| | >> dna-connector-svn
| | >>
| | >> And since the 0.3 release we have started (or will so be starting)
| | >> several new subprojects:
| | >> dna-connector-store-jpa
| | >> dna-connector-jdbc-metadata (soon to be created)
| | >>
| | >> So, here's my proposal: we'd create in SVN a new "sandbox" directory
| | >> under the "trunk" directory, and in this area is generally where
| | >> subprojects would live until they are "mature enough" to move outside
| | >> of the "sandbox". In some cases, "mature enough" means that they are
| | >> indeed complete, while in other cases they may be far enough along
| | >> and
| | >> there's commitment to finish them before the next release. I'd
| | >> anticipate that we'd be flexible on what "mature enough" means and
| | >> decide on a case-by-case basis as a community when a sandbox project
| | >> is "mature enough" on a case-by-case basis (although ultimately the
| | >> project lead would have the final say). However, sandbox projects
| | >> would be excluded from the binary release assembly (but maybe
| | >> included
| | >> in the source assembly?) and would not be mentioned in the Getting
| | >> Started document, and all mentions in the Reference Guide would be
| | >> moved to a new chapter covering the sandbox.
| | >>
| | >> Also, with this proposal, I'd think we would still keep all of the
| | >> sandbox projects in our development environments (unless other wise
| | >> requested by a project's developers). And these sandbox projects
| | >> would still included in the Maven builds and Hudson CI jobs.
| | >>
| | >> Here's a strawman list of existing extensions that could be moved
| | >> into
| | >> the "sandbox", based purely upon my understanding of where these
| | >> projects are and the plans to complete them by 0.4:
| | >> dna-classloader-maven (complete, but to be of any use it really needs
| | >> additional components, like perhaps a Maven or SVN connector)
| | >> dna-sequencer-cnd
| | >> dna-sequencer-esbMessage
| | >> dna-sequencer-jbpm-jpdl
| | >> dna-connector-jdbc-metadata (soon to be created)
| | >> dna-sequencer-jdbc-metadata (actually, this is to be removed)
| | >>
| | >> These projects would stay in "trunk", since they are planned to be
| | >> completed for 0.4:
| | >> dna-connector-svn
| | >> dna-connector-store-jpa
| | >>
| | >> Forgive me if my understanding of the state of these projects is
| | >> wrong. If that's the case, please speak up and correct me.
| | >>
| | >> So, what do you think of this proposal? Please weigh in with your
| | >> thoughts and opinions about the proposal and the suggested list of
| | >> "sandbox" subprojects.
| | >>
| | >>
| | >> Best regards,
| | >>
| | >> Randall
| | >> -------------- next part --------------
| | >> An HTML attachment was scrubbed...
| | >> URL: http://lists.jboss.org/pipermail/dna-dev/attachments/20081123/20577752/at...
| | >>
| | >> ------------------------------
| | >>
| | >> _______________________________________________
| | >> dna-dev mailing list
| | >> dna-dev(a)lists.jboss.org
| | >> https://lists.jboss.org/mailman/listinfo/dna-dev
| | >>
| | >>
| | >> End of dna-dev Digest, Vol 8, Issue 17
| | >> **************************************
| | >>
| | >
| | > _______________________________________________
| | > dna-dev mailing list
| | > dna-dev(a)lists.jboss.org
| | > https://lists.jboss.org/mailman/listinfo/dna-dev
| |
| | _______________________________________________
| | dna-dev mailing list
| | dna-dev(a)lists.jboss.org
| | https://lists.jboss.org/mailman/listinfo/dna-dev
| |
|
| _______________________________________________ dna-dev mailing list dna-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/dna-dev
17 years
