You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by si...@insession.com on 2005/07/12 03:44:58 UTC
Removal of SNAPSHOTs from builds
I was thinking a good way to get a start on removal of SNAPSHOTs is to
raise a JIRA issue for each SNAPSHOT we depend upon so each can be
individually tracked/discussed and worked on. The etc/project.properties
file could then be updated with a comment for each SNAPSHOT containing the
JIRA issue number.
Does this sound like a reasonable approach?
I would then ask that anyone with knowledge of each SNAPSHOT or patched
version to assign it to themselves and comment in the JIRA issue on why we
are using it and whether we can move to a formal release or an estimate of
when that may be possible if known.
This should allow us to track the work required and the state of it.
The "Release specs as a separate distro from M4" mail thread seemed to
indicate the specs JARS are going to be moved to formal versions. Has a
decision been reached? Would it make sense to have a single JIRA issue
for all the spec jars?
Have people been using a tool in the past to see the dependency tree? If
so what tool?
Here is the current list of SNAPSHOTS taken from etc/project.properties:
# hack to work with activemq
geronimo_kernel_version=1.0-SNAPSHOT
geronimo_system_version=1.0-SNAPSHOT
# actual dependencies
activemq_version=3.1-SNAPSHOT
geronimo_version=1.0-SNAPSHOT
openejb_version=2.0-SNAPSHOT
tmporb_version=1.0-SNAPSHOT
tranql_version=1.0-SNAPSHOT
tranql_connector_version=1.0-SNAPSHOT
geronimo_spec_activation_version=1.0.2-SNAPSHOT
geronimo_spec_javamail_version=1.3.1-SNAPSHOT
activecluster_version=1.0-SNAPSHOT
axis_version=1.3-SNAPSHOT
commons_discovery_version=SNAPSHOT
ews_version=SNAPSHOT
jaxb_ri_version=SNAPSHOT
juddi_version=SNAPSHOT
scout_version=1.0-SNAPSHOT
servicemix_version=1.0-SNAPSHOT
The following are look like they aren't formal versions, shall I also
create JIRA issues for these (see note about spec JARs above). Even if
there isn't a formal version available it would be good to document where
the dependency is used and have the issue to review later in time to see
if the situation has changed?
geronimo_spec_corba_version=2.3-rc4
geronimo_spec_ejb_version=2.1-rc4
geronimo_spec_j2ee_version=1.4-rc4
geronimo_spec_j2ee_connector_version=1.5-rc4
geronimo_spec_j2ee_deployment_version=1.1-rc4
geronimo_spec_j2ee_jacc_version=1.0-rc4
geronimo_spec_j2ee_management_version=1.0-rc4
geronimo_spec_jaxr_version=1.0-rc4
geronimo_spec_jaxrpc_version=1.1-rc4
geronimo_spec_jms_version=1.1-rc4
geronimo_spec_jsp_version=2.0-rc4
geronimo_spec_jta_version=1.0.1B-rc4
geronimo_spec_saaj_version=1.1-rc4
geronimo_spec_servlet_version=2.4-rc4
geronimo_spec_qname_version=1.1-rc4
axion_version=1.0-M3-dev
cglib_version=HEAD-06-06-05
commons_jelly_version=1.0-beta-4
drools_version=2.0-beta-13
emberio_version=0.3-alpha
jetty_version=5.1.4rc0
jdbm_version=0.20-dev
openorb_version=1.4.0-GERONIMO
servicemix_spring_version=1.2.2-dev-2
stax_version=1.1.1-dev
wsdl4j_version=PATCH-1193602
xfire_version=20050202
xml_apis_version=1.0.b2
xmlbeans_version=1.0-DEV
xmlpull_version=1.1.3.4d_b4_min
Thanks,
John
This e-mail message and any attachments may contain confidential,
proprietary or non-public information. This information is intended
solely for the designated recipient(s). If an addressing or transmission
error has misdirected this e-mail, please notify the sender immediately
and destroy this e-mail. Any review, dissemination, use or reliance upon
this information by unintended recipients is prohibited. Any opinions
expressed in this e-mail are those of the author personally.
Re: Removal of SNAPSHOTs from builds
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Jul 12, 2005, at 2:27 PM, David Jencks wrote:
> It strikes me that a lot of the dependencies here shouldn't even be
> there. At least, I have no idea which component pulls them in. It
> would be great to see which ones can be removed entirely, although
> I don't have an efficient reproducible procedure in mind.
>
> If a dependency is needed only in a module that is not needed in
> the "j2ee core" I wonder if it could be in a different section of
> the file?
>
> Can anyone think of a way of cross-referencing which modules use
> which depenency?
I did this a while ago for some due diligence work, trying to figure
out what needed what. I'll see if I can find my scripts. I was just
scanning the maven files...
geir
>
> I've marked the dependencies I don't personally know the use of
> with a ? on the line before the dependency and added a couple
> comments.
>
> thanks
> david jencks
>
> On Jul 11, 2005, at 8:15 PM, Donald Woods wrote:
>
>
>> Here is an updated project.properties from Rev 209846
>> that I'm trying out (note that the same changes need
>> to be made to the openejb/etc/project.properties file)
>> with the old values commented out with "##". Please
>> note, that the below compiles and both the Server and
>> DebugConsole will start, but none of the tests have
>> been executed to verify these levels should be used
>> yet....
>>
>> #####################################################
>> # Dependency Version
>> #####################################################
>> # hack to work with activemq
>>
> ?
>
>> geronimo_kernel_version=1.0-SNAPSHOT
>>
> ?
>
>> geronimo_system_version=1.0-SNAPSHOT
>> # actual dependencies
>> activeio_version=1.0
>> ##activemq_version=3.1-SNAPSHOT
>> activemq_version=3.1-M3
>> geronimo_version=1.0-SNAPSHOT
>> openejb_version=2.0-SNAPSHOT
>>
> ?
>
>> tmporb_version=1.0-SNAPSHOT
>> tranql_version=1.0-SNAPSHOT
>> tranql_connector_version=1.0-SNAPSHOT
>>
>> geronimo_spec_activation_version=1.0.2-SNAPSHOT
>> geronimo_spec_corba_version=2.3-rc4
>> geronimo_spec_ejb_version=2.1-rc4
>> geronimo_spec_j2ee_version=1.4-rc4
>> geronimo_spec_j2ee_connector_version=1.5-rc4
>> geronimo_spec_j2ee_deployment_version=1.1-rc4
>> geronimo_spec_j2ee_jacc_version=1.0-rc4
>> geronimo_spec_j2ee_management_version=1.0-rc4
>> geronimo_spec_javamail_version=1.3.1-SNAPSHOT
>> geronimo_spec_jaxr_version=1.0-rc4
>> geronimo_spec_jaxrpc_version=1.1-rc4
>> geronimo_spec_jms_version=1.1-rc4
>> geronimo_spec_jsp_version=2.0-rc4
>> geronimo_spec_jta_version=1.0.1B-rc4
>> geronimo_spec_saaj_version=1.1-rc4
>> geronimo_spec_servlet_version=2.4-rc4
>> geronimo_spec_qname_version=1.1-rc4
>>
>> ##activecluster_version=1.0-SNAPSHOT
>>
> ?
>
>> activecluster_version=1.1-SNAPSHOT
>>
> ? If this is needed, can it be the same as geronimo's jetty version?
>
>> activemq_jetty_version=4.2.20RC0
>> ##ant_version=1.5
>>
> ?
>
>> ant_version=1.6.5
>> ##antlr_version=2.7.2
>> antlr_version=2.7.5
>> ##asm_version=1.4.3
>> asm_version=1.5.3
>>
> ? axion is handy but dead. I'm afraid I think we should stop using it
>
>> axion_version=1.0-M3-dev
>> axis_version=1.3-SNAPSHOT
>> ##avalon_framework_version=4.1.4
>>
> ? dain, I think you should take this stuff out of m4. Can you
> explain the risks you see?
>
>> avalon_framework_version=4.1.5
>> ##avalon_logkit_version=1.2.2
>>
> ? ditto
>
>> avalon_logkit_version=2.0.0
>> ##bouncycastle_version=jdk14-124
>> bouncycastle_version=jdk14-129
>> ##cglib_version=HEAD-06-06-05
>> cglib_version=2.1_2
>> ##castor_version=0.9.5.3
>>
> ?
>
>> castor_version=0.9.7
>> ##commons_beanutils_version=1.6.1
>>
> ? to all the commons packages...
>
>> commons_beanutils_version=1.7.0
>> commons_cli_version=1.0
>> commons_collections_version=3.1
>>
> ???
>
>> commons_dbcp_version=1.2
>> ##commons_digester_version=1.6
>> commons_digester_version=1.7
>> ##commons_discovery_version=SNAPSHOT
>> commons_discovery_version=0.2
>> commons_el_version=1.0
>> commons_io_version=1.0
>> commons_fileupload_version=1.0
>> commons_httpclient_version=2.0.1
>> ##commons_jelly_version=1.0-beta-4
>> commons_jelly_version=1.0
>> commons_jxpath_version=1.1
>> commons_logging_version=1.0.4
>> commons_modeler_version=1.1
>> commons_primitives_version=1.0
>> commons_pool_version=1.2
>> concurrent_version=1.3.4
>> derby_version=10.0.2.1
>> ##dom4j_version=1.4
>>
> ?
>
>> dom4j_version=1.6.1
>>
> ?
>
>> drools_version=2.0-beta-13
>> eclipse_compiler_version=3.0.1
>>
> ?
>
>> emberio_version=0.3-alpha
>>
> ??
>
>> ews_version=SNAPSHOT
>> howl_version=0.1.8
>>
> ?
>
>> hsqldb_version=1.7.2.2
>> jasper_version=5.5.9
>> javacc_version=2.1
>>
> ?
>
>> jaxb_ri_version=SNAPSHOT
>>
> ?
>
>> jdbm_version=0.20-dev
>> jelly_velocity_tags_version=1.0
>> ##jetty_version=5.1.4rc0
>> jetty_version=5.1.4
>>
> ?
>
>> jmock_version=1.0.1
>>
> ?
>
>> jrms_version=1.1
>> ##juddi_version=SNAPSHOT
>> juddi_version=0.9rc4
>> junit_version=3.8.1
>>
> ?
>
>> jxta_version=2.0
>> log4j_version=1.2.8
>> maven_itest_plugin_version=1.0
>> maven_version=1.0
>>
> should probably be maven_version=1.0.2, version 1.0 doesn't work
> any more for us
> ?
>
>> mockobjects_version=0.09
>> mx4j_version=3.0.1
>>
> ?
>
>> openorb_version=1.4.0-GERONIMO
>>
> ?
>
>> oro_version=2.0.8
>>
> ?
>
>> p2psockets_version=1.1.2
>> regexp_version=1.3
>> scout_version=1.0-SNAPSHOT
>> ##spring_version=1.1.3
>> spring_version=1.2.2
>> stax_version=1.1.1-dev
>> stax_api_version=1.0
>> tomcat_jk2_version=5.0.18
>> tomcat_version=5.5.9
>> velocity_version=1.4
>> ##wsdl4j_version=PATCH-1193602
>> wsdl4j_version=1.5.1
>> xerces_version=2.6.2
>> ##xfire_version=20050202
>> ##xfire_version=1.0-SNAPSHOT - compile errors occurred
>> xfire_version=20050202
>> xml_apis_version=1.0.b2
>> xml_resolver_version=1.1
>> xml_parser_apis_version=2.2.1
>> xmlbeans_version=1.0-DEV
>>
> this xmlbeans version is actually a snapshot. We should try 1.0.4,
> or just move to 2.0 (see other email)
>
>> xmlpull_version=1.1.3.4d_b4_min
>> ##xpp3_version=1.1.3.3
>> xpp3_version=1.1.3.4.M
>> ##xstream_version=1.0.2
>> xstream_version=1.1.2
>> servicemix_version=1.0-SNAPSHOT
>> ##servicemix_spring_version=1.2.2-dev-2
>> servicemix_spring_version=1.2.2
>>
>>
>> -Donald
>>
>>
>> --- Aaron Mulder <am...@alumni.princeton.edu>
>> wrote:
>>
>>
>>> Sounds reasonable to me. I hate to see that many
>>> JIRA issues
>>> added all in one shot, but we do need to keep track
>>> of them somehow. :)
>>>
>>> Aaron
>>>
>>> On Tue, 12 Jul 2005 sissonj@insession.com wrote:
>>>
>>>> I was thinking a good way to get a start on
>>>>
>>> removal of SNAPSHOTs is to
>>>
>>>> raise a JIRA issue for each SNAPSHOT we depend
>>>>
>>> upon so each can be
>>>
>>>> individually tracked/discussed and worked on. The
>>>>
>>> etc/project.properties
>>>
>>>> file could then be updated with a comment for each
>>>>
>>> SNAPSHOT containing the
>>>
>>>> JIRA issue number.
>>>>
>>>> Does this sound like a reasonable approach?
>>>>
>>>> I would then ask that anyone with knowledge of
>>>>
>>> each SNAPSHOT or patched
>>>
>>>> version to assign it to themselves and comment in
>>>>
>>> the JIRA issue on why we
>>>
>>>> are using it and whether we can move to a formal
>>>>
>>> release or an estimate of
>>>
>>>> when that may be possible if known.
>>>>
>>>> This should allow us to track the work required
>>>>
>>> and the state of it.
>>>
>>>>
>>>> The "Release specs as a separate distro from M4"
>>>>
>>> mail thread seemed to
>>>
>>>> indicate the specs JARS are going to be moved to
>>>>
>>> formal versions. Has a
>>>
>>>> decision been reached? Would it make sense to
>>>>
>>> have a single JIRA issue
>>>
>>>> for all the spec jars?
>>>>
>>>> Have people been using a tool in the past to see
>>>>
>>> the dependency tree? If
>>>
>>>> so what tool?
>>>>
>>>> Here is the current list of SNAPSHOTS taken from
>>>>
>>> etc/project.properties:
>>>
>>>>
>>>> # hack to work with activemq
>>>> geronimo_kernel_version=1.0-SNAPSHOT
>>>> geronimo_system_version=1.0-SNAPSHOT
>>>>
>>>> # actual dependencies
>>>> activemq_version=3.1-SNAPSHOT
>>>> geronimo_version=1.0-SNAPSHOT
>>>> openejb_version=2.0-SNAPSHOT
>>>> tmporb_version=1.0-SNAPSHOT
>>>> tranql_version=1.0-SNAPSHOT
>>>> tranql_connector_version=1.0-SNAPSHOT
>>>>
>>>>
>>> geronimo_spec_activation_version=1.0.2-SNAPSHOT
>>>
>>>> geronimo_spec_javamail_version=1.3.1-SNAPSHOT
>>>> activecluster_version=1.0-SNAPSHOT
>>>> axis_version=1.3-SNAPSHOT
>>>> commons_discovery_version=SNAPSHOT
>>>> ews_version=SNAPSHOT
>>>> jaxb_ri_version=SNAPSHOT
>>>> juddi_version=SNAPSHOT
>>>> scout_version=1.0-SNAPSHOT
>>>> servicemix_version=1.0-SNAPSHOT
>>>>
>>>> The following are look like they aren't formal
>>>>
>>> versions, shall I also
>>>
>>>> create JIRA issues for these (see note about spec
>>>>
>>> JARs above). Even if
>>>
>>>> there isn't a formal version available it would be
>>>>
>>> good to document where
>>>
>>>> the dependency is used and have the issue to
>>>>
>>> review later in time to see
>>>
>>>> if the situation has changed?
>>>>
>>>> geronimo_spec_corba_version=2.3-rc4
>>>> geronimo_spec_ejb_version=2.1-rc4
>>>> geronimo_spec_j2ee_version=1.4-rc4
>>>> geronimo_spec_j2ee_connector_version=1.5-rc4
>>>> geronimo_spec_j2ee_deployment_version=1.1-rc4
>>>> geronimo_spec_j2ee_jacc_version=1.0-rc4
>>>> geronimo_spec_j2ee_management_version=1.0-rc4
>>>> geronimo_spec_jaxr_version=1.0-rc4
>>>> geronimo_spec_jaxrpc_version=1.1-rc4
>>>> geronimo_spec_jms_version=1.1-rc4
>>>> geronimo_spec_jsp_version=2.0-rc4
>>>> geronimo_spec_jta_version=1.0.1B-rc4
>>>> geronimo_spec_saaj_version=1.1-rc4
>>>> geronimo_spec_servlet_version=2.4-rc4
>>>> geronimo_spec_qname_version=1.1-rc4
>>>> axion_version=1.0-M3-dev
>>>> cglib_version=HEAD-06-06-05
>>>> commons_jelly_version=1.0-beta-4
>>>> drools_version=2.0-beta-13
>>>> emberio_version=0.3-alpha
>>>> jetty_version=5.1.4rc0
>>>> jdbm_version=0.20-dev
>>>> openorb_version=1.4.0-GERONIMO
>>>> servicemix_spring_version=1.2.2-dev-2
>>>> stax_version=1.1.1-dev
>>>> wsdl4j_version=PATCH-1193602
>>>> xfire_version=20050202
>>>> xml_apis_version=1.0.b2
>>>> xmlbeans_version=1.0-DEV
>>>> xmlpull_version=1.1.3.4d_b4_min
>>>>
>>>> Thanks,
>>>>
>>>> John
>>>>
>>>> This e-mail message and any attachments may
>>>>
>>> contain confidential,
>>>
>>>> proprietary or non-public information. This
>>>>
>>> information is intended
>>>
>>>> solely for the designated recipient(s). If an
>>>>
>>> addressing or transmission
>>>
>>>> error has misdirected this e-mail, please notify
>>>>
>>> the sender immediately
>>>
>>>> and destroy this e-mail. Any review,
>>>>
>>> dissemination, use or reliance upon
>>>
>>>> this information by unintended recipients is
>>>>
>>> prohibited. Any opinions
>>>
>>>> expressed in this e-mail are those of the author
>>>>
>>> personally.
>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>> __________________________________
>> Discover Yahoo!
>> Have fun online with music videos, cool games, IM and more. Check
>> it out!
>> http://discover.yahoo.com/online.html
>>
>>
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Removal of SNAPSHOTs from builds
Posted by David Jencks <da...@yahoo.com>.
It strikes me that a lot of the dependencies here shouldn't even be
there. At least, I have no idea which component pulls them in. It
would be great to see which ones can be removed entirely, although I
don't have an efficient reproducible procedure in mind.
If a dependency is needed only in a module that is not needed in the
"j2ee core" I wonder if it could be in a different section of the file?
Can anyone think of a way of cross-referencing which modules use which
depenency?
I've marked the dependencies I don't personally know the use of with a
? on the line before the dependency and added a couple comments.
thanks
david jencks
On Jul 11, 2005, at 8:15 PM, Donald Woods wrote:
> Here is an updated project.properties from Rev 209846
> that I'm trying out (note that the same changes need
> to be made to the openejb/etc/project.properties file)
> with the old values commented out with "##". Please
> note, that the below compiles and both the Server and
> DebugConsole will start, but none of the tests have
> been executed to verify these levels should be used
> yet....
>
> #####################################################
> # Dependency Version
> #####################################################
> # hack to work with activemq
?
> geronimo_kernel_version=1.0-SNAPSHOT
?
> geronimo_system_version=1.0-SNAPSHOT
> # actual dependencies
> activeio_version=1.0
> ##activemq_version=3.1-SNAPSHOT
> activemq_version=3.1-M3
> geronimo_version=1.0-SNAPSHOT
> openejb_version=2.0-SNAPSHOT
?
> tmporb_version=1.0-SNAPSHOT
> tranql_version=1.0-SNAPSHOT
> tranql_connector_version=1.0-SNAPSHOT
>
> geronimo_spec_activation_version=1.0.2-SNAPSHOT
> geronimo_spec_corba_version=2.3-rc4
> geronimo_spec_ejb_version=2.1-rc4
> geronimo_spec_j2ee_version=1.4-rc4
> geronimo_spec_j2ee_connector_version=1.5-rc4
> geronimo_spec_j2ee_deployment_version=1.1-rc4
> geronimo_spec_j2ee_jacc_version=1.0-rc4
> geronimo_spec_j2ee_management_version=1.0-rc4
> geronimo_spec_javamail_version=1.3.1-SNAPSHOT
> geronimo_spec_jaxr_version=1.0-rc4
> geronimo_spec_jaxrpc_version=1.1-rc4
> geronimo_spec_jms_version=1.1-rc4
> geronimo_spec_jsp_version=2.0-rc4
> geronimo_spec_jta_version=1.0.1B-rc4
> geronimo_spec_saaj_version=1.1-rc4
> geronimo_spec_servlet_version=2.4-rc4
> geronimo_spec_qname_version=1.1-rc4
>
> ##activecluster_version=1.0-SNAPSHOT
?
> activecluster_version=1.1-SNAPSHOT
? If this is needed, can it be the same as geronimo's jetty version?
> activemq_jetty_version=4.2.20RC0
> ##ant_version=1.5
?
> ant_version=1.6.5
> ##antlr_version=2.7.2
> antlr_version=2.7.5
> ##asm_version=1.4.3
> asm_version=1.5.3
? axion is handy but dead. I'm afraid I think we should stop using it
> axion_version=1.0-M3-dev
> axis_version=1.3-SNAPSHOT
> ##avalon_framework_version=4.1.4
? dain, I think you should take this stuff out of m4. Can you explain
the risks you see?
> avalon_framework_version=4.1.5
> ##avalon_logkit_version=1.2.2
? ditto
> avalon_logkit_version=2.0.0
> ##bouncycastle_version=jdk14-124
> bouncycastle_version=jdk14-129
> ##cglib_version=HEAD-06-06-05
> cglib_version=2.1_2
> ##castor_version=0.9.5.3
?
> castor_version=0.9.7
> ##commons_beanutils_version=1.6.1
? to all the commons packages...
> commons_beanutils_version=1.7.0
> commons_cli_version=1.0
> commons_collections_version=3.1
???
> commons_dbcp_version=1.2
> ##commons_digester_version=1.6
> commons_digester_version=1.7
> ##commons_discovery_version=SNAPSHOT
> commons_discovery_version=0.2
> commons_el_version=1.0
> commons_io_version=1.0
> commons_fileupload_version=1.0
> commons_httpclient_version=2.0.1
> ##commons_jelly_version=1.0-beta-4
> commons_jelly_version=1.0
> commons_jxpath_version=1.1
> commons_logging_version=1.0.4
> commons_modeler_version=1.1
> commons_primitives_version=1.0
> commons_pool_version=1.2
> concurrent_version=1.3.4
> derby_version=10.0.2.1
> ##dom4j_version=1.4
?
> dom4j_version=1.6.1
?
> drools_version=2.0-beta-13
> eclipse_compiler_version=3.0.1
?
> emberio_version=0.3-alpha
??
> ews_version=SNAPSHOT
> howl_version=0.1.8
?
> hsqldb_version=1.7.2.2
> jasper_version=5.5.9
> javacc_version=2.1
?
> jaxb_ri_version=SNAPSHOT
?
> jdbm_version=0.20-dev
> jelly_velocity_tags_version=1.0
> ##jetty_version=5.1.4rc0
> jetty_version=5.1.4
?
> jmock_version=1.0.1
?
> jrms_version=1.1
> ##juddi_version=SNAPSHOT
> juddi_version=0.9rc4
> junit_version=3.8.1
?
> jxta_version=2.0
> log4j_version=1.2.8
> maven_itest_plugin_version=1.0
> maven_version=1.0
should probably be maven_version=1.0.2, version 1.0 doesn't work any
more for us
?
> mockobjects_version=0.09
> mx4j_version=3.0.1
?
> openorb_version=1.4.0-GERONIMO
?
> oro_version=2.0.8
?
> p2psockets_version=1.1.2
> regexp_version=1.3
> scout_version=1.0-SNAPSHOT
> ##spring_version=1.1.3
> spring_version=1.2.2
> stax_version=1.1.1-dev
> stax_api_version=1.0
> tomcat_jk2_version=5.0.18
> tomcat_version=5.5.9
> velocity_version=1.4
> ##wsdl4j_version=PATCH-1193602
> wsdl4j_version=1.5.1
> xerces_version=2.6.2
> ##xfire_version=20050202
> ##xfire_version=1.0-SNAPSHOT - compile errors occurred
> xfire_version=20050202
> xml_apis_version=1.0.b2
> xml_resolver_version=1.1
> xml_parser_apis_version=2.2.1
> xmlbeans_version=1.0-DEV
this xmlbeans version is actually a snapshot. We should try 1.0.4, or
just move to 2.0 (see other email)
> xmlpull_version=1.1.3.4d_b4_min
> ##xpp3_version=1.1.3.3
> xpp3_version=1.1.3.4.M
> ##xstream_version=1.0.2
> xstream_version=1.1.2
> servicemix_version=1.0-SNAPSHOT
> ##servicemix_spring_version=1.2.2-dev-2
> servicemix_spring_version=1.2.2
>
>
> -Donald
>
>
> --- Aaron Mulder <am...@alumni.princeton.edu>
> wrote:
>
>> Sounds reasonable to me. I hate to see that many
>> JIRA issues
>> added all in one shot, but we do need to keep track
>> of them somehow. :)
>>
>> Aaron
>>
>> On Tue, 12 Jul 2005 sissonj@insession.com wrote:
>>> I was thinking a good way to get a start on
>> removal of SNAPSHOTs is to
>>> raise a JIRA issue for each SNAPSHOT we depend
>> upon so each can be
>>> individually tracked/discussed and worked on. The
>> etc/project.properties
>>> file could then be updated with a comment for each
>> SNAPSHOT containing the
>>> JIRA issue number.
>>>
>>> Does this sound like a reasonable approach?
>>>
>>> I would then ask that anyone with knowledge of
>> each SNAPSHOT or patched
>>> version to assign it to themselves and comment in
>> the JIRA issue on why we
>>> are using it and whether we can move to a formal
>> release or an estimate of
>>> when that may be possible if known.
>>>
>>> This should allow us to track the work required
>> and the state of it.
>>>
>>> The "Release specs as a separate distro from M4"
>> mail thread seemed to
>>> indicate the specs JARS are going to be moved to
>> formal versions. Has a
>>> decision been reached? Would it make sense to
>> have a single JIRA issue
>>> for all the spec jars?
>>>
>>> Have people been using a tool in the past to see
>> the dependency tree? If
>>> so what tool?
>>>
>>> Here is the current list of SNAPSHOTS taken from
>> etc/project.properties:
>>>
>>> # hack to work with activemq
>>> geronimo_kernel_version=1.0-SNAPSHOT
>>> geronimo_system_version=1.0-SNAPSHOT
>>>
>>> # actual dependencies
>>> activemq_version=3.1-SNAPSHOT
>>> geronimo_version=1.0-SNAPSHOT
>>> openejb_version=2.0-SNAPSHOT
>>> tmporb_version=1.0-SNAPSHOT
>>> tranql_version=1.0-SNAPSHOT
>>> tranql_connector_version=1.0-SNAPSHOT
>>>
>> geronimo_spec_activation_version=1.0.2-SNAPSHOT
>>> geronimo_spec_javamail_version=1.3.1-SNAPSHOT
>>> activecluster_version=1.0-SNAPSHOT
>>> axis_version=1.3-SNAPSHOT
>>> commons_discovery_version=SNAPSHOT
>>> ews_version=SNAPSHOT
>>> jaxb_ri_version=SNAPSHOT
>>> juddi_version=SNAPSHOT
>>> scout_version=1.0-SNAPSHOT
>>> servicemix_version=1.0-SNAPSHOT
>>>
>>> The following are look like they aren't formal
>> versions, shall I also
>>> create JIRA issues for these (see note about spec
>> JARs above). Even if
>>> there isn't a formal version available it would be
>> good to document where
>>> the dependency is used and have the issue to
>> review later in time to see
>>> if the situation has changed?
>>>
>>> geronimo_spec_corba_version=2.3-rc4
>>> geronimo_spec_ejb_version=2.1-rc4
>>> geronimo_spec_j2ee_version=1.4-rc4
>>> geronimo_spec_j2ee_connector_version=1.5-rc4
>>> geronimo_spec_j2ee_deployment_version=1.1-rc4
>>> geronimo_spec_j2ee_jacc_version=1.0-rc4
>>> geronimo_spec_j2ee_management_version=1.0-rc4
>>> geronimo_spec_jaxr_version=1.0-rc4
>>> geronimo_spec_jaxrpc_version=1.1-rc4
>>> geronimo_spec_jms_version=1.1-rc4
>>> geronimo_spec_jsp_version=2.0-rc4
>>> geronimo_spec_jta_version=1.0.1B-rc4
>>> geronimo_spec_saaj_version=1.1-rc4
>>> geronimo_spec_servlet_version=2.4-rc4
>>> geronimo_spec_qname_version=1.1-rc4
>>> axion_version=1.0-M3-dev
>>> cglib_version=HEAD-06-06-05
>>> commons_jelly_version=1.0-beta-4
>>> drools_version=2.0-beta-13
>>> emberio_version=0.3-alpha
>>> jetty_version=5.1.4rc0
>>> jdbm_version=0.20-dev
>>> openorb_version=1.4.0-GERONIMO
>>> servicemix_spring_version=1.2.2-dev-2
>>> stax_version=1.1.1-dev
>>> wsdl4j_version=PATCH-1193602
>>> xfire_version=20050202
>>> xml_apis_version=1.0.b2
>>> xmlbeans_version=1.0-DEV
>>> xmlpull_version=1.1.3.4d_b4_min
>>>
>>> Thanks,
>>>
>>> John
>>>
>>> This e-mail message and any attachments may
>> contain confidential,
>>> proprietary or non-public information. This
>> information is intended
>>> solely for the designated recipient(s). If an
>> addressing or transmission
>>> error has misdirected this e-mail, please notify
>> the sender immediately
>>> and destroy this e-mail. Any review,
>> dissemination, use or reliance upon
>>> this information by unintended recipients is
>> prohibited. Any opinions
>>> expressed in this e-mail are those of the author
>> personally.
>>>
>>
>
>
>
>
> __________________________________
> Discover Yahoo!
> Have fun online with music videos, cool games, IM and more. Check it
> out!
> http://discover.yahoo.com/online.html
>
Re: Removal of SNAPSHOTs from builds
Posted by Donald Woods <dr...@yahoo.com>.
Here is an updated project.properties from Rev 209846
that I'm trying out (note that the same changes need
to be made to the openejb/etc/project.properties file)
with the old values commented out with "##". Please
note, that the below compiles and both the Server and
DebugConsole will start, but none of the tests have
been executed to verify these levels should be used
yet....
#####################################################
# Dependency Version
#####################################################
# hack to work with activemq
geronimo_kernel_version=1.0-SNAPSHOT
geronimo_system_version=1.0-SNAPSHOT
# actual dependencies
activeio_version=1.0
##activemq_version=3.1-SNAPSHOT
activemq_version=3.1-M3
geronimo_version=1.0-SNAPSHOT
openejb_version=2.0-SNAPSHOT
tmporb_version=1.0-SNAPSHOT
tranql_version=1.0-SNAPSHOT
tranql_connector_version=1.0-SNAPSHOT
geronimo_spec_activation_version=1.0.2-SNAPSHOT
geronimo_spec_corba_version=2.3-rc4
geronimo_spec_ejb_version=2.1-rc4
geronimo_spec_j2ee_version=1.4-rc4
geronimo_spec_j2ee_connector_version=1.5-rc4
geronimo_spec_j2ee_deployment_version=1.1-rc4
geronimo_spec_j2ee_jacc_version=1.0-rc4
geronimo_spec_j2ee_management_version=1.0-rc4
geronimo_spec_javamail_version=1.3.1-SNAPSHOT
geronimo_spec_jaxr_version=1.0-rc4
geronimo_spec_jaxrpc_version=1.1-rc4
geronimo_spec_jms_version=1.1-rc4
geronimo_spec_jsp_version=2.0-rc4
geronimo_spec_jta_version=1.0.1B-rc4
geronimo_spec_saaj_version=1.1-rc4
geronimo_spec_servlet_version=2.4-rc4
geronimo_spec_qname_version=1.1-rc4
##activecluster_version=1.0-SNAPSHOT
activecluster_version=1.1-SNAPSHOT
activemq_jetty_version=4.2.20RC0
##ant_version=1.5
ant_version=1.6.5
##antlr_version=2.7.2
antlr_version=2.7.5
##asm_version=1.4.3
asm_version=1.5.3
axion_version=1.0-M3-dev
axis_version=1.3-SNAPSHOT
##avalon_framework_version=4.1.4
avalon_framework_version=4.1.5
##avalon_logkit_version=1.2.2
avalon_logkit_version=2.0.0
##bouncycastle_version=jdk14-124
bouncycastle_version=jdk14-129
##cglib_version=HEAD-06-06-05
cglib_version=2.1_2
##castor_version=0.9.5.3
castor_version=0.9.7
##commons_beanutils_version=1.6.1
commons_beanutils_version=1.7.0
commons_cli_version=1.0
commons_collections_version=3.1
commons_dbcp_version=1.2
##commons_digester_version=1.6
commons_digester_version=1.7
##commons_discovery_version=SNAPSHOT
commons_discovery_version=0.2
commons_el_version=1.0
commons_io_version=1.0
commons_fileupload_version=1.0
commons_httpclient_version=2.0.1
##commons_jelly_version=1.0-beta-4
commons_jelly_version=1.0
commons_jxpath_version=1.1
commons_logging_version=1.0.4
commons_modeler_version=1.1
commons_primitives_version=1.0
commons_pool_version=1.2
concurrent_version=1.3.4
derby_version=10.0.2.1
##dom4j_version=1.4
dom4j_version=1.6.1
drools_version=2.0-beta-13
eclipse_compiler_version=3.0.1
emberio_version=0.3-alpha
ews_version=SNAPSHOT
howl_version=0.1.8
hsqldb_version=1.7.2.2
jasper_version=5.5.9
javacc_version=2.1
jaxb_ri_version=SNAPSHOT
jdbm_version=0.20-dev
jelly_velocity_tags_version=1.0
##jetty_version=5.1.4rc0
jetty_version=5.1.4
jmock_version=1.0.1
jrms_version=1.1
##juddi_version=SNAPSHOT
juddi_version=0.9rc4
junit_version=3.8.1
jxta_version=2.0
log4j_version=1.2.8
maven_itest_plugin_version=1.0
maven_version=1.0
mockobjects_version=0.09
mx4j_version=3.0.1
openorb_version=1.4.0-GERONIMO
oro_version=2.0.8
p2psockets_version=1.1.2
regexp_version=1.3
scout_version=1.0-SNAPSHOT
##spring_version=1.1.3
spring_version=1.2.2
stax_version=1.1.1-dev
stax_api_version=1.0
tomcat_jk2_version=5.0.18
tomcat_version=5.5.9
velocity_version=1.4
##wsdl4j_version=PATCH-1193602
wsdl4j_version=1.5.1
xerces_version=2.6.2
##xfire_version=20050202
##xfire_version=1.0-SNAPSHOT - compile errors occurred
xfire_version=20050202
xml_apis_version=1.0.b2
xml_resolver_version=1.1
xml_parser_apis_version=2.2.1
xmlbeans_version=1.0-DEV
xmlpull_version=1.1.3.4d_b4_min
##xpp3_version=1.1.3.3
xpp3_version=1.1.3.4.M
##xstream_version=1.0.2
xstream_version=1.1.2
servicemix_version=1.0-SNAPSHOT
##servicemix_spring_version=1.2.2-dev-2
servicemix_spring_version=1.2.2
-Donald
--- Aaron Mulder <am...@alumni.princeton.edu>
wrote:
> Sounds reasonable to me. I hate to see that many
> JIRA issues
> added all in one shot, but we do need to keep track
> of them somehow. :)
>
> Aaron
>
> On Tue, 12 Jul 2005 sissonj@insession.com wrote:
> > I was thinking a good way to get a start on
> removal of SNAPSHOTs is to
> > raise a JIRA issue for each SNAPSHOT we depend
> upon so each can be
> > individually tracked/discussed and worked on. The
> etc/project.properties
> > file could then be updated with a comment for each
> SNAPSHOT containing the
> > JIRA issue number.
> >
> > Does this sound like a reasonable approach?
> >
> > I would then ask that anyone with knowledge of
> each SNAPSHOT or patched
> > version to assign it to themselves and comment in
> the JIRA issue on why we
> > are using it and whether we can move to a formal
> release or an estimate of
> > when that may be possible if known.
> >
> > This should allow us to track the work required
> and the state of it.
> >
> > The "Release specs as a separate distro from M4"
> mail thread seemed to
> > indicate the specs JARS are going to be moved to
> formal versions. Has a
> > decision been reached? Would it make sense to
> have a single JIRA issue
> > for all the spec jars?
> >
> > Have people been using a tool in the past to see
> the dependency tree? If
> > so what tool?
> >
> > Here is the current list of SNAPSHOTS taken from
> etc/project.properties:
> >
> > # hack to work with activemq
> > geronimo_kernel_version=1.0-SNAPSHOT
> > geronimo_system_version=1.0-SNAPSHOT
> >
> > # actual dependencies
> > activemq_version=3.1-SNAPSHOT
> > geronimo_version=1.0-SNAPSHOT
> > openejb_version=2.0-SNAPSHOT
> > tmporb_version=1.0-SNAPSHOT
> > tranql_version=1.0-SNAPSHOT
> > tranql_connector_version=1.0-SNAPSHOT
> >
> geronimo_spec_activation_version=1.0.2-SNAPSHOT
> > geronimo_spec_javamail_version=1.3.1-SNAPSHOT
> > activecluster_version=1.0-SNAPSHOT
> > axis_version=1.3-SNAPSHOT
> > commons_discovery_version=SNAPSHOT
> > ews_version=SNAPSHOT
> > jaxb_ri_version=SNAPSHOT
> > juddi_version=SNAPSHOT
> > scout_version=1.0-SNAPSHOT
> > servicemix_version=1.0-SNAPSHOT
> >
> > The following are look like they aren't formal
> versions, shall I also
> > create JIRA issues for these (see note about spec
> JARs above). Even if
> > there isn't a formal version available it would be
> good to document where
> > the dependency is used and have the issue to
> review later in time to see
> > if the situation has changed?
> >
> > geronimo_spec_corba_version=2.3-rc4
> > geronimo_spec_ejb_version=2.1-rc4
> > geronimo_spec_j2ee_version=1.4-rc4
> > geronimo_spec_j2ee_connector_version=1.5-rc4
> > geronimo_spec_j2ee_deployment_version=1.1-rc4
> > geronimo_spec_j2ee_jacc_version=1.0-rc4
> > geronimo_spec_j2ee_management_version=1.0-rc4
> > geronimo_spec_jaxr_version=1.0-rc4
> > geronimo_spec_jaxrpc_version=1.1-rc4
> > geronimo_spec_jms_version=1.1-rc4
> > geronimo_spec_jsp_version=2.0-rc4
> > geronimo_spec_jta_version=1.0.1B-rc4
> > geronimo_spec_saaj_version=1.1-rc4
> > geronimo_spec_servlet_version=2.4-rc4
> > geronimo_spec_qname_version=1.1-rc4
> > axion_version=1.0-M3-dev
> > cglib_version=HEAD-06-06-05
> > commons_jelly_version=1.0-beta-4
> > drools_version=2.0-beta-13
> > emberio_version=0.3-alpha
> > jetty_version=5.1.4rc0
> > jdbm_version=0.20-dev
> > openorb_version=1.4.0-GERONIMO
> > servicemix_spring_version=1.2.2-dev-2
> > stax_version=1.1.1-dev
> > wsdl4j_version=PATCH-1193602
> > xfire_version=20050202
> > xml_apis_version=1.0.b2
> > xmlbeans_version=1.0-DEV
> > xmlpull_version=1.1.3.4d_b4_min
> >
> > Thanks,
> >
> > John
> >
> > This e-mail message and any attachments may
> contain confidential,
> > proprietary or non-public information. This
> information is intended
> > solely for the designated recipient(s). If an
> addressing or transmission
> > error has misdirected this e-mail, please notify
> the sender immediately
> > and destroy this e-mail. Any review,
> dissemination, use or reliance upon
> > this information by unintended recipients is
> prohibited. Any opinions
> > expressed in this e-mail are those of the author
> personally.
> >
>
__________________________________
Discover Yahoo!
Have fun online with music videos, cool games, IM and more. Check it out!
http://discover.yahoo.com/online.html
Re: Removal of SNAPSHOTs from builds
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Sounds reasonable to me. I hate to see that many JIRA issues
added all in one shot, but we do need to keep track of them somehow. :)
Aaron
On Tue, 12 Jul 2005 sissonj@insession.com wrote:
> I was thinking a good way to get a start on removal of SNAPSHOTs is to
> raise a JIRA issue for each SNAPSHOT we depend upon so each can be
> individually tracked/discussed and worked on. The etc/project.properties
> file could then be updated with a comment for each SNAPSHOT containing the
> JIRA issue number.
>
> Does this sound like a reasonable approach?
>
> I would then ask that anyone with knowledge of each SNAPSHOT or patched
> version to assign it to themselves and comment in the JIRA issue on why we
> are using it and whether we can move to a formal release or an estimate of
> when that may be possible if known.
>
> This should allow us to track the work required and the state of it.
>
> The "Release specs as a separate distro from M4" mail thread seemed to
> indicate the specs JARS are going to be moved to formal versions. Has a
> decision been reached? Would it make sense to have a single JIRA issue
> for all the spec jars?
>
> Have people been using a tool in the past to see the dependency tree? If
> so what tool?
>
> Here is the current list of SNAPSHOTS taken from etc/project.properties:
>
> # hack to work with activemq
> geronimo_kernel_version=1.0-SNAPSHOT
> geronimo_system_version=1.0-SNAPSHOT
>
> # actual dependencies
> activemq_version=3.1-SNAPSHOT
> geronimo_version=1.0-SNAPSHOT
> openejb_version=2.0-SNAPSHOT
> tmporb_version=1.0-SNAPSHOT
> tranql_version=1.0-SNAPSHOT
> tranql_connector_version=1.0-SNAPSHOT
> geronimo_spec_activation_version=1.0.2-SNAPSHOT
> geronimo_spec_javamail_version=1.3.1-SNAPSHOT
> activecluster_version=1.0-SNAPSHOT
> axis_version=1.3-SNAPSHOT
> commons_discovery_version=SNAPSHOT
> ews_version=SNAPSHOT
> jaxb_ri_version=SNAPSHOT
> juddi_version=SNAPSHOT
> scout_version=1.0-SNAPSHOT
> servicemix_version=1.0-SNAPSHOT
>
> The following are look like they aren't formal versions, shall I also
> create JIRA issues for these (see note about spec JARs above). Even if
> there isn't a formal version available it would be good to document where
> the dependency is used and have the issue to review later in time to see
> if the situation has changed?
>
> geronimo_spec_corba_version=2.3-rc4
> geronimo_spec_ejb_version=2.1-rc4
> geronimo_spec_j2ee_version=1.4-rc4
> geronimo_spec_j2ee_connector_version=1.5-rc4
> geronimo_spec_j2ee_deployment_version=1.1-rc4
> geronimo_spec_j2ee_jacc_version=1.0-rc4
> geronimo_spec_j2ee_management_version=1.0-rc4
> geronimo_spec_jaxr_version=1.0-rc4
> geronimo_spec_jaxrpc_version=1.1-rc4
> geronimo_spec_jms_version=1.1-rc4
> geronimo_spec_jsp_version=2.0-rc4
> geronimo_spec_jta_version=1.0.1B-rc4
> geronimo_spec_saaj_version=1.1-rc4
> geronimo_spec_servlet_version=2.4-rc4
> geronimo_spec_qname_version=1.1-rc4
> axion_version=1.0-M3-dev
> cglib_version=HEAD-06-06-05
> commons_jelly_version=1.0-beta-4
> drools_version=2.0-beta-13
> emberio_version=0.3-alpha
> jetty_version=5.1.4rc0
> jdbm_version=0.20-dev
> openorb_version=1.4.0-GERONIMO
> servicemix_spring_version=1.2.2-dev-2
> stax_version=1.1.1-dev
> wsdl4j_version=PATCH-1193602
> xfire_version=20050202
> xml_apis_version=1.0.b2
> xmlbeans_version=1.0-DEV
> xmlpull_version=1.1.3.4d_b4_min
>
> Thanks,
>
> John
>
> This e-mail message and any attachments may contain confidential,
> proprietary or non-public information. This information is intended
> solely for the designated recipient(s). If an addressing or transmission
> error has misdirected this e-mail, please notify the sender immediately
> and destroy this e-mail. Any review, dissemination, use or reliance upon
> this information by unintended recipients is prohibited. Any opinions
> expressed in this e-mail are those of the author personally.
>