[jira] Commented: (MWAR-100) War overlay with merged web.xml
[ http://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109149 ] Richard C. L. Li commented on MWAR-100: --- I am in need of this feature, any progress? I can help to implement this feature if you permitted, this should be easy though. > War overlay with merged web.xml > --- > > Key: MWAR-100 > URL: http://jira.codehaus.org/browse/MWAR-100 > Project: Maven 2.x War Plugin > Issue Type: Wish >Affects Versions: 2.0 >Reporter: Anders Romin > > I'm looking for a way to use the war overlay feature and have the web.xml > merged with the content of both the parent war and the child war. > For example, we have two wars A and B, and B is depending on A using the > overlay feature. Now, I'd like all filters, servlets etc that are configured > in A to be available in the resulting war, as well as all filters, servlets > etc from B. If the id attributes clash, then the objects from B should be > used. > Any ideas how this could be accomplished? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2921) ejb-client dependency no longer working
[ http://jira.codehaus.org/browse/MNG-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92696 ] Richard C. L. Li commented on MNG-2921: --- I have encounter this same problem as well. > ejb-client dependency no longer working > --- > > Key: MNG-2921 > URL: http://jira.codehaus.org/browse/MNG-2921 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.6 > Environment: Fedora Core 6 >Reporter: Frank Cornelis >Priority: Blocker > Attachments: test.zip > > > When running 'mvn clean install' on the test project (see attachment) under > Maven 2.0.5 every builds as expected. On Maven 2.0.6 it no longer compiles. > On Maven 2.0.5 I get in the log: > [DEBUG] be.frankcornelis.maven:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] be.frankcornelis.maven:model:ejb-client:client:1.0-SNAPSHOT:compile > (selected for compile) > Under Maven 2.0.6 I get: > [DEBUG] be.frankcornelis.maven:client:jar:1.0-SNAPSHOT (selected for null) > [DEBUG] be.frankcornelis.maven:model:ejb-client:client:1.0-SNAPSHOT > (selected for null) > and an error message saying it cannot find the required interfaces defined in > Model. > When I remove type:ejb-client in the Client pom.xml it compiles again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
New indexes created during continuum startup when using postgresql -- Key: CONTINUUM-994 URL: http://jira.codehaus.org/browse/CONTINUUM-994 Project: Continuum Issue Type: Bug Components: Database Affects Versions: 1.0.3 Reporter: Richard C. L. Li I used postgresql 8.1.4 with continuum and everytime when continuum startup, it creates a set of indexes. I configured to restart continuum once a day and after 2 months it generated tens of indexes in every table. I guessed this maybe the problem of the the UPPER CASE of the table and column names, this may make the detection of indexes fails and the JDO recreate everytime it startup. Workaround: after starting continuum for the first time and set the property org.jpox.autoCreateSchema to false so that indexes will not recreated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=comments#action_82840 ] Richard C. L. Li commented on CONTINUUM-994: Will new release upgrade the dependencies to 1.1.5? > New indexes created during continuum startup when using postgresql > -- > > Key: CONTINUUM-994 > URL: http://jira.codehaus.org/browse/CONTINUUM-994 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Richard C. L. Li > > I used postgresql 8.1.4 with continuum and everytime when continuum startup, > it creates a set of indexes. I configured to restart continuum once a day > and after 2 months it generated tens of indexes in every table. > I guessed this maybe the problem of the the UPPER CASE of the table and > column names, this may make the detection of indexes fails and the JDO > recreate everytime it startup. > Workaround: after starting continuum for the first time and set the property > org.jpox.autoCreateSchema to false so that indexes will not recreated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=comments#action_82844 ] Richard C. L. Li commented on CONTINUUM-994: I just tried to build the continuum ffrom trunk and replace the jpox from 1.1.1 to 1.1.5, this problem still persists. Any idea? > New indexes created during continuum startup when using postgresql > -- > > Key: CONTINUUM-994 > URL: http://jira.codehaus.org/browse/CONTINUUM-994 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Richard C. L. Li > > I used postgresql 8.1.4 with continuum and everytime when continuum startup, > it creates a set of indexes. I configured to restart continuum once a day > and after 2 months it generated tens of indexes in every table. > I guessed this maybe the problem of the the UPPER CASE of the table and > column names, this may make the detection of indexes fails and the JDO > recreate everytime it startup. > Workaround: after starting continuum for the first time and set the property > org.jpox.autoCreateSchema to false so that indexes will not recreated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=comments#action_85299
]
Richard C. L. Li commented on CONTINUUM-994:
After some investigation, I figure out that the problem is in jpox. When using
Upper Case for identifiers, postgresql jdbc driver will response all identifier
with quotes, but quoting identifiers will trigger a bug in jpox that it cannot
identify existing indexes and recreating them. To work around, simply set the
use of identifiers to use Lower Case and problem solved.
Edit the file /apps/continuum/webapp/WEB-INF/classes/META-INF/plexus/application.xml and
add the property org.jpox.identifier.case in the jpox component definition.
{code:xml}
org.codehaus.plexus.jdo.JdoFactory
users
org.codehaus.plexus.jdo.DataSourceConfigurableJdoFactory
java:comp/env/jdbc/users
java:comp/env/jdbc/usersShutdown
org.jpox.PersistenceManagerFactoryImpl
org.jpox.autoCreateSchema
true
org.jpox.validateTables
false
org.jpox.validateConstraints
false
org.jpox.validateColumns
false
org.jpox.autoStartMechanism
None
org.jpox.transactionIsolation
READ_UNCOMMITTED
org.jpox.poid.transactionIsolation
READ_UNCOMMITTED
org.jpox.rdbms.dateTimezone
JDK_DEFAULT_TIMEZONE
org.jpox.identifier.case
LowerCase
org.codehaus.plexus.jdo.JdoFactory
org.codehaus.plexus.jdo.DataSourceConfigurableJdoFactory
continuum
java:comp/env/jdbc/continuum
java:comp/env/jdbc/continuum_shutdown
org.jpox.PersistenceManagerFactoryImpl
org.jpox.autoCreateSchema
true
org.jpox.validateTables
false
org.jpox.validateColumns
false
org.jpox.validateConstraints
false
org.jpox.autoStartMechanism
None
org.jpox.transactionIsolation
READ_UNCOMMITTED
org.jpox.identifier.case
LowerCase
{code}
> New indexes created during continuum startup when using postgresql
> --
>
> Key: CONTINUUM-994
> URL: http://jira.codehaus.org/browse/CONTINUUM-994
> Project: Continuum
> Issue Type: Bug
> Components: Database
>Affects Versions: 1.0.3
>Reporter: Richard C. L. Li
> Fix For: 1.1
>
>
> I used postgresql 8.1.4 with continuum and everytime when continuum startup,
> it creates a set of indexes. I configured to restart continuum once a day
> and after 2 months it generated tens of indexes in every table.
> I guessed this maybe the problem of the the UPPER CASE of the table and
> column names, this may make the detection of indexes fails and the JDO
> recreate everytime it startup.
> Workaround: after starting continuum for the first time and set the property
> org.jpox.autoCreateSchema to false so that indexes will not recreated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=all ] Richard C. L. Li closed CONTINUUM-994. -- Resolution: Won't Fix Fix Version/s: 1.1 > New indexes created during continuum startup when using postgresql > -- > > Key: CONTINUUM-994 > URL: http://jira.codehaus.org/browse/CONTINUUM-994 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Richard C. L. Li > Fix For: 1.1 > > > I used postgresql 8.1.4 with continuum and everytime when continuum startup, > it creates a set of indexes. I configured to restart continuum once a day > and after 2 months it generated tens of indexes in every table. > I guessed this maybe the problem of the the UPPER CASE of the table and > column names, this may make the detection of indexes fails and the JDO > recreate everytime it startup. > Workaround: after starting continuum for the first time and set the property > org.jpox.autoCreateSchema to false so that indexes will not recreated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1140) Build failed ReleasePrepareActionTest produce error
Build failed ReleasePrepareActionTest produce error --- Key: CONTINUUM-1140 URL: http://jira.codehaus.org/browse/CONTINUUM-1140 Project: Continuum Issue Type: Bug Affects Versions: 1.1 Reporter: Richard C. L. Li Attachments: continuum.patch org/apache/maven/continuum/web/action/ReleasePrepareActionTest.java produces errors upon running. I have attached a patch to fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1140) Build failed ReleasePrepareActionTest produce error
[ http://jira.codehaus.org/browse/CONTINUUM-1140?page=comments#action_85423 ] Richard C. L. Li commented on CONTINUUM-1140: - I have attached the surefire report of error testcases. The null appeared in the path is due to the null in working directory. > Build failed ReleasePrepareActionTest produce error > --- > > Key: CONTINUUM-1140 > URL: http://jira.codehaus.org/browse/CONTINUUM-1140 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Richard C. L. Li > Attachments: continuum.patch, > org.apache.maven.continuum.web.action.ReleasePrepareActionTest.txt > > > org/apache/maven/continuum/web/action/ReleasePrepareActionTest.java produces > errors upon running. I have attached a patch to fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1140) Build failed ReleasePrepareActionTest produce error
[ http://jira.codehaus.org/browse/CONTINUUM-1140?page=comments#action_85427 ] Richard C. L. Li commented on CONTINUUM-1140: - jdk 1.5.0 update 10. The problem happens in both the 32-bit Windows version and 64-bit Linux version. > Build failed ReleasePrepareActionTest produce error > --- > > Key: CONTINUUM-1140 > URL: http://jira.codehaus.org/browse/CONTINUUM-1140 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Richard C. L. Li > Attachments: continuum.patch, > org.apache.maven.continuum.web.action.ReleasePrepareActionTest.txt > > > org/apache/maven/continuum/web/action/ReleasePrepareActionTest.java produces > errors upon running. I have attached a patch to fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[
http://jira.codehaus.org/browse/CONTINUUM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85955
]
Richard C. L. Li commented on CONTINUUM-994:
Continuum will generate an exception when using with postgresql and JPOX 1.1.6
upon browsing the web page at the first time, the problem is resides in plexus:
{panel}
http://jira.codehaus.org/browse/PLX-322
{panel}
> New indexes created during continuum startup when using postgresql
> --
>
> Key: CONTINUUM-994
> URL: http://jira.codehaus.org/browse/CONTINUUM-994
> Project: Continuum
> Issue Type: Bug
> Components: Database
>Affects Versions: 1.0.3
>Reporter: Richard C. L. Li
> Fix For: 1.1
>
>
> I used postgresql 8.1.4 with continuum and everytime when continuum startup,
> it creates a set of indexes. I configured to restart continuum once a day
> and after 2 months it generated tens of indexes in every table.
> I guessed this maybe the problem of the the UPPER CASE of the table and
> column names, this may make the detection of indexes fails and the JDO
> recreate everytime it startup.
> Workaround: after starting continuum for the first time and set the property
> org.jpox.autoCreateSchema to false so that indexes will not recreated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
