You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Basile Chandesris (JIRA)" <ji...@apache.org> on 2010/02/19 13:27:27 UTC
[jira] Created: (TAP5-1023) tapestry-hibernate-5.2.0 jar generated
with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas alo
tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas alo
----------------------------------------------------------------------------------------------------------------------------------------------
Key: TAP5-1023
URL: https://issues.apache.org/jira/browse/TAP5-1023
Project: Tapestry 5
Issue Type: Improvement
Reporter: Basile Chandesris
causing duplicate of tapestry-hibernate-XXX.jar at the deployment.
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
tapestry-ioc-5.2.0-SNAPSHOT.jar
tapestry5-annotations-5.2.0-SNAPSHOT.jar
tapestry-core-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Basile Chandesris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Basile Chandesris updated TAP5-1023:
------------------------------------
Fix Version/s: 5.2.0
Description:
Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
Example:
tapestry-core-5.2.0-SNAPSHOT.jar
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
tapestry-ioc-5.2.0-SNAPSHOT.jar
tapestry5-annotations-5.2.0-SNAPSHOT.jar
was:
causing duplicate of tapestry-hibernate-XXX.jar at the deployment.
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
tapestry-ioc-5.2.0-SNAPSHOT.jar
tapestry5-annotations-5.2.0-SNAPSHOT.jar
tapestry-core-5.2.0-SNAPSHOT.jar
Environment: osx snow leopard, linux redhat
Summary: (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT (was: tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas alo)
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1023.
----------------------------------------
Assignee: Howard M. Lewis Ship
Resolution: Cannot Reproduce
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Basile Chandesris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Basile Chandesris updated TAP5-1023:
------------------------------------
Fix Version/s: 5.2.0
Description:
Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
Example:
tapestry-core-5.2.0-SNAPSHOT.jar
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
tapestry-ioc-5.2.0-SNAPSHOT.jar
tapestry5-annotations-5.2.0-SNAPSHOT.jar
was:
causing duplicate of tapestry-hibernate-XXX.jar at the deployment.
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
tapestry-ioc-5.2.0-SNAPSHOT.jar
tapestry5-annotations-5.2.0-SNAPSHOT.jar
tapestry-core-5.2.0-SNAPSHOT.jar
Environment: osx snow leopard, linux redhat
Summary: (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT (was: tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas alo)
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1023.
----------------------------------------
Assignee: Howard M. Lewis Ship
Resolution: Cannot Reproduce
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Ulrich Stärk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835732#action_12835732 ]
Ulrich Stärk commented on TAP5-1023:
------------------------------------
Could you please rephrase that? I don't get what your problem is...
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Basile Chandesris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835815#action_12835815 ]
Basile Chandesris commented on TAP5-1023:
-----------------------------------------
When I use in my pom.xml:
Extract:
...
<dependencies>
<dependency>
<groupId>javassist</groupId>
<artifactId>javassist</artifactId>
<version>3.10.0.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<version>3.3.2.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-c3p0</artifactId>
<version>3.3.2.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-annotations</artifactId>
<version>3.4.0.GA</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate-core</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-core</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-ioc</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry5-annotations</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
...
with
<properties>
<tapestry-release-version>5.2.0-SNAPSHOT</tapestry-release-version>
<!-- <tapestry-release-version>5.1.0.7</tapestry-release-version> -->
</properties>
Launching each day 'mvn install',
add a new tapestry-hibernate- .jar
without removing the old one.
The names here are always different.
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
But this process is working for all jar named with 5.2.0-SNAPSHOT,
all the other jar of Tapestry 5.2.0-SNAPSHOT.
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Ulrich Stärk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835732#action_12835732 ]
Ulrich Stärk commented on TAP5-1023:
------------------------------------
Could you please rephrase that? I don't get what your problem is...
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1023) (5.2.0-SPNAPSHOT Maven dependencies)
tapestry-hibernate-5.2.0 jar generated with
tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar >
tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using
-5.2.0-SNAPSHOT
Posted by "Basile Chandesris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835815#action_12835815 ]
Basile Chandesris commented on TAP5-1023:
-----------------------------------------
When I use in my pom.xml:
Extract:
...
<dependencies>
<dependency>
<groupId>javassist</groupId>
<artifactId>javassist</artifactId>
<version>3.10.0.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<version>3.3.2.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-c3p0</artifactId>
<version>3.3.2.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-annotations</artifactId>
<version>3.4.0.GA</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate-core</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-core</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-ioc</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry5-annotations</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
...
with
<properties>
<tapestry-release-version>5.2.0-SNAPSHOT</tapestry-release-version>
<!-- <tapestry-release-version>5.1.0.7</tapestry-release-version> -->
</properties>
Launching each day 'mvn install',
add a new tapestry-hibernate- .jar
without removing the old one.
The names here are always different.
tapestry-hibernate-5.2.0-20100217.091747-192.jar
tapestry-hibernate-5.2.0-20100219.090323-194.jar
But this process is working for all jar named with 5.2.0-SNAPSHOT,
all the other jar of Tapestry 5.2.0-SNAPSHOT.
> (5.2.0-SPNAPSHOT Maven dependencies) tapestry-hibernate-5.2.0 jar generated with tapestry-hibernate-5.2.0-yyyyMMdd.hhmmss-?.jar > tapestry-hibernate-5.2.0-SNAPSHOT.jar whereas all other jar are using -5.2.0-SNAPSHOT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1023
> URL: https://issues.apache.org/jira/browse/TAP5-1023
> Project: Tapestry 5
> Issue Type: Improvement
> Environment: osx snow leopard, linux redhat
> Reporter: Basile Chandesris
> Fix For: 5.2.0
>
>
> Cause duplicate of tapestry-hibernate-XXX.jar at the deployment.
> Example:
> tapestry-core-5.2.0-SNAPSHOT.jar
> tapestry-hibernate-5.2.0-20100217.091747-192.jar
> tapestry-hibernate-5.2.0-20100219.090323-194.jar
> tapestry-hibernate-core-5.2.0-SNAPSHOT.jar
> tapestry-ioc-5.2.0-SNAPSHOT.jar
> tapestry5-annotations-5.2.0-SNAPSHOT.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.