[jira] Commented: (MASSEMBLY-241) Multiple includes in dependencySet
[ http://jira.codehaus.org/browse/MASSEMBLY-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107706 ] Wouter Hermeling commented on MASSEMBLY-241: In addition, the following does not work for inclusions: the pom dependencies: aaa.bbb xxx 1.0 aaa.bbb xxx 1.0 javadoc The assembly: aaa.bbb:xxx:jar aaa.bbb:xxx:jar:javadoc This assembly above will produce an assembly containing only javadoc jar. This javadoc jar is being packaged as xxx-1.0.jar i/o xxx-1.0-javadoc.jar. Hope this helps > Multiple includes in dependencySet > -- > > Key: MASSEMBLY-241 > URL: http://jira.codehaus.org/browse/MASSEMBLY-241 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Maven version: 2.0.7 > Java version: 1.6.0_02 > OS name: "linux" version: "2.6.18-gentoo-r4" arch: "i386" >Reporter: Paul Austin > > When you specify multiple include elements inside an includes for a > dependencySet it only uses the first include statement > This works > > /lib/ext > false > runtime > > com.revolsys.jump:* > > > > /lib/ext > false > runtime > > com.revolsys.gis:* > > > This does not > > /lib/ext > false > runtime > > com.revolsys.jump:* > com.revolsys.gis:* > > > There are dependencies from the jump package to the gis package -- 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: (MCLOVER-77) Artifact has 2 candidates, please provide a classifier
[ http://jira.codehaus.org/browse/MCLOVER-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107708 ] Tom Davies commented on MCLOVER-77: --- I haven't been able to reproduce this -- can you provide a simple pair of projects which fail? > Artifact has 2 candidates, please provide a classifier > -- > > Key: MCLOVER-77 > URL: http://jira.codehaus.org/browse/MCLOVER-77 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: maya nayak > > INFO - > INFO - [INFO] [clover:instrumentInternal] > INFO - [WARNING] No Clover instrumentation done as no matching sources files > found > INFO - [INFO] [ear:generate-application-xml] > INFO - [INFO] > > INFO - [ERROR] BUILD FAILURE > INFO - [INFO] > > INFO - [INFO] Artifact[jar:com.tsysprepaid.psa:psa-common] has 2 candidates, > please provide a classifier. > INFO - [INFO] > > psa-common is a separate project and i ran clover:instrument successfully on > that. it created psa-common--clover.jar in the local > repository and after that my other project which lists psa-common as a > dependency started to fail on clover:instrument with the above error. > It appears that since psa-common now has psa-common-.jar and > psa-common--clover.jar in the repository, clover > is unable to resolve it and fails it with message artificat has 2 candidates, > please provide a classifier. > How do I provide a classifier? > Is there any way to prevent clover from installing clover artifacts into m2 > repository? -- 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-1470) "Cancel" button is just going back to the previous page
"Cancel" button is just going back to the previous page --- Key: CONTINUUM-1470 URL: http://jira.codehaus.org/browse/CONTINUUM-1470 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1-beta-2 Reporter: Maria Catherine Tan Priority: Minor Edit a project group or anything that has a cancel button. Try to save in three times with invalid values. Then hit Cancel. Notice that it only goes back to the previous page and not to the list. -- 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] Updated: (CONTINUUM-697) sizes incompatible with mssql (Patch Attached)
[ http://jira.codehaus.org/browse/CONTINUUM-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-697: -- Attachment: CONTINUUM-697.patch Here's one solution using ORMs(http://www.jpox.org/docs/1_1/metadata.html#File_Types) in JPOX. The solution would affect all the databases but Brian though can maybe patch a copy of Continuum, build it and use that with MSSQL. :) If we're looking at ORMs as a long term solution, we need to add the property Mapping when using MSSQL databases. So far, I can only see this happening in the code. Test the driver and if it's an MSSQL one, include the property Mapping when creating the PersistenceManager. Any ideas as to how we can add a dynamic entry on application.xml? Such that when a user deploys Continuum with MSSQL, he/she can add the Mapping property. > sizes incompatible with mssql (Patch Attached) > -- > > Key: CONTINUUM-697 > URL: http://jira.codehaus.org/browse/CONTINUUM-697 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 > Environment: windows/mssql2000 >Reporter: Brian Fox > Fix For: To Sort > > Attachments: CONTINUUM-697.patch, continuum-697.patch > > > This is my configuration: > > javax.jdo.option.ConnectionDriverName > net.sourceforge.jtds.jdbc.Driver > > > javax.jdo.option.ConnectionURL > > jdbc:jtds:sqlserver://cordella.mht.stchome.com:1433/continuum > > > javax.jdo.option.ConnectionUserName > continuum > > > javax.jdo.option.ConnectionPassword > continuum > > I get this exception: > 3984 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - An exception was > thrown while adding/validating class(es) : The size (8192) given to the > column 'COMMENT' exceeds the maximum allowed for any data type (8000). > java.sql.SQLException: The size (8192) given to the column 'COMMENT' exceeds > the maximum allowed for any data type (8000). > 4000 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - java.sql.SQLException: > The size (8192) given to the column 'COMMENT' exceeds the maximum allowed for > any data type (8000). -- 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-1471) Error when performing Release on a Project Group with no project
Error when performing Release on a Project Group with no project Key: CONTINUUM-1471 URL: http://jira.codehaus.org/browse/CONTINUUM-1471 Project: Continuum Issue Type: Bug Affects Versions: 1.1-beta-2 Reporter: Maria Catherine Tan To reproduce: 1. Click a project group with no project 2. In the project group summary page, click the release button -- 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-1472) No navigation on Project Release Summary page
No navigation on Project Release Summary page - Key: CONTINUUM-1472 URL: http://jira.codehaus.org/browse/CONTINUUM-1472 Project: Continuum Issue Type: Improvement Affects Versions: 1.1-beta-2 Reporter: Maria Catherine Tan Priority: Minor If you click 'View Output' after Prepare for Release finishes, the only way to get back from the Project Release Summary page is to use the browser back button. -- 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: (MSITE-233) NoSuchMethodError with Java 6
[ http://jira.codehaus.org/browse/MSITE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107713 ] Antonio Petrelli commented on MSITE-233: It seems that upgrading to 2.0-beta-5 resolves the bug. > NoSuchMethodError with Java 6 > - > > Key: MSITE-233 > URL: http://jira.codehaus.org/browse/MSITE-233 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Environment: Maven 2.0.6, Java 1.6.0_01-b06, maven-site-plugin > 2.0-beta-4 >Reporter: Paul Benedict > > [INFO] [site:site] > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] > org.codehaus.plexus.util.FileUtils.getDefaultExcludes()[Ljava/lang/String; > [INFO] > > [INFO] Trace > java.lang.NoSuchMethodError: > org.codehaus.plexus.util.FileUtils.getDefaultExcludes()[Ljava/lang/String; > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:275) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) -- 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: (MDEP-100) Merge dependency:tree branch for new features
[ http://jira.codehaus.org/browse/MDEP-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107717 ] Mark Hobson commented on MDEP-100: -- Renamed and updated branch with latest trunk changes: http://svn.apache.org/repos/asf/maven/plugins/branches/maven-dependency-plugin-MDEP-100/ > Merge dependency:tree branch for new features > - > > Key: MDEP-100 > URL: http://jira.codehaus.org/browse/MDEP-100 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement > Components: tree >Affects Versions: 2.0-alpha-4 >Reporter: Mark Hobson >Assignee: Mark Hobson > Fix For: 2.0-alpha-6 > > > Reminder to merge the maven-dependency-tree 1.1 branch into trunk after > 2.0-alpha-5 is released: > https://svn.apache.org/repos/asf/maven/plugins/branches/maven-dependency-plugin-tree-1.1/ -- 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: (MSITE-169) links to modules where not working if a modules dir is used
[ http://jira.codehaus.org/browse/MSITE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107719 ] geoff simpson commented on MSITE-169: - I disagree, having to specify the url in each dependent module is a maintenance nightmare. Surely it should be possible to work out the correct structure via the parent dependencies. > links to modules where not working if a modules dir is used > --- > > Key: MSITE-169 > URL: http://jira.codehaus.org/browse/MSITE-169 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0-beta-4, 2.0-beta-5, 2.0-beta-6 >Reporter: Mathias Brökelmann > Attachments: MNG-MSITE-169-maven-site-plugin.patch > > > I've to place the modules into a separate directory: > root/ > ..pom.xml > ..modules/ > module1 > module2 > this is supported by maven through > > modules/module1 > modules/module2 > > in pom. > but the site generation seems to be broken: > if mvn site-deploy is used the links to the modules contain > modules/module1/index.html which is ok but unfortunately the generated site > structure will be generated as follows: > root/ > ..module1 > ..module2 > The result is that the links do not work. > If I run mvn site-stage everything looks ok. The links doesn't contain > modules dir anymore and eveything is working. -- 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] Updated: (CONTINUUM-697) sizes incompatible with mssql (Patch Attached)
[ http://jira.codehaus.org/browse/CONTINUUM-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-697: -- Attachment: CONTINUUM-697.patch Wasn't able to include the other fields. Sorry... :) > sizes incompatible with mssql (Patch Attached) > -- > > Key: CONTINUUM-697 > URL: http://jira.codehaus.org/browse/CONTINUUM-697 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 > Environment: windows/mssql2000 >Reporter: Brian Fox > Fix For: To Sort > > Attachments: CONTINUUM-697.patch, CONTINUUM-697.patch, > continuum-697.patch > > > This is my configuration: > > javax.jdo.option.ConnectionDriverName > net.sourceforge.jtds.jdbc.Driver > > > javax.jdo.option.ConnectionURL > > jdbc:jtds:sqlserver://cordella.mht.stchome.com:1433/continuum > > > javax.jdo.option.ConnectionUserName > continuum > > > javax.jdo.option.ConnectionPassword > continuum > > I get this exception: > 3984 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - An exception was > thrown while adding/validating class(es) : The size (8192) given to the > column 'COMMENT' exceeds the maximum allowed for any data type (8000). > java.sql.SQLException: The size (8192) given to the column 'COMMENT' exceeds > the maximum allowed for any data type (8000). > 4000 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - java.sql.SQLException: > The size (8192) given to the column 'COMMENT' exceeds the maximum allowed for > any data type (8000). -- 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-1353) after a few weeks, continuum runs into outofmemory error
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107731 ] Emmanuel Venisse commented on CONTINUUM-1353: - Do you use the build fresh option? Before 1.1-beta-3, we have an memory issue with it that is fixed. > after a few weeks, continuum runs into outofmemory error > > > Key: CONTINUUM-1353 > URL: http://jira.codehaus.org/browse/CONTINUUM-1353 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-2 >Reporter: tony nys >Priority: Blocker > > when clicking on the build history, memory of the jvm increases from 100MB > until 470MB > after that it crashes with outofmemory error (JDO exception) > Increasing the plexus jvm memory does have no affect: > %PLEXUS_JAVA_EXE% %PLEXUS_OPTS% -Xmx900M -XX:MaxPermSize=128m -classpath > "%PLEXUS_HOME%\core\boot\plexus-classworlds-1.2-alpha-7.jar" > -Dclassworlds.conf="%PLEXUS_HOME%\conf\classworlds.conf" > -Dplexus.core=%PLEXUS_CORE% -Dplexus.system.path="%PATH%" > -Djava.io.tmpdir=%PLEXUS_TMPDIR% -Dplexus.home="%PLEXUS_HOME%" > -Dappserver.base="%PLEXUS_BASE%" -Dtools.jar="%TOOLS_JAR%" > org.codehaus.plexus.classworlds.launcher.Launcher %PLEXUS_CMD_LINE_ARGS% > So probably bug in fetch from db where all objects are retrieved ? > For us this is a showstopper. Would MySQL DB be a workaround ? I guess the > query is the same, so will the memory usage be ? > Where can I find the complete DDL script for mysql ? On the wiki there is > only 1 table ... ? > javax.jdo.JDODataStoreException: Iteration request failed : > SELECT > THIS.CHANGEFILE_ID,THIS.MODEL_ENCODING,THIS."NAME",THIS.REVISION,THIS.STATUS,THIS.FILES_INTEGER_IDX > AS JPOXORDER0 FROM > CHANGEFILE THIS WHERE ? = THIS.FILES_CHANGESET_ID_OID AND > THIS.FILES_INTEGER_IDX >= ? ORDER BY JPOXORDER0 NestedThrowables: SQL > Exception: Java exception: > 'Java heap space: java.lang.OutOfMemoryError'. -- 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-697) sizes incompatible with mssql (Patch Attached)
[ http://jira.codehaus.org/browse/CONTINUUM-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-697. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: To Sort) 1.1-beta-3 Thanks Teodoro, I applied your patch. The mapping property in application.xml must be uncommented to use Continuum with mssql > sizes incompatible with mssql (Patch Attached) > -- > > Key: CONTINUUM-697 > URL: http://jira.codehaus.org/browse/CONTINUUM-697 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 > Environment: windows/mssql2000 >Reporter: Brian Fox >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-3 > > Attachments: CONTINUUM-697.patch, CONTINUUM-697.patch, > continuum-697.patch > > > This is my configuration: > > javax.jdo.option.ConnectionDriverName > net.sourceforge.jtds.jdbc.Driver > > > javax.jdo.option.ConnectionURL > > jdbc:jtds:sqlserver://cordella.mht.stchome.com:1433/continuum > > > javax.jdo.option.ConnectionUserName > continuum > > > javax.jdo.option.ConnectionPassword > continuum > > I get this exception: > 3984 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - An exception was > thrown while adding/validating class(es) : The size (8192) given to the > column 'COMMENT' exceeds the maximum allowed for any data type (8000). > java.sql.SQLException: The size (8192) given to the column 'COMMENT' exceeds > the maximum allowed for any data type (8000). > 4000 [WrapperSimpleAppMain] ERROR JPOX.RDBMS.SCHEMA - java.sql.SQLException: > The size (8192) given to the column 'COMMENT' exceeds the maximum allowed for > any data type (8000). -- 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-1353) after a few weeks, continuum runs into outofmemory error
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107733 ] tony nys commented on CONTINUUM-1353: - using refresh option & continuum-1.1-alpha-2 what does the refresh option actually do ? a complete fresh cvs checkout ? > after a few weeks, continuum runs into outofmemory error > > > Key: CONTINUUM-1353 > URL: http://jira.codehaus.org/browse/CONTINUUM-1353 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-2 >Reporter: tony nys >Priority: Blocker > > when clicking on the build history, memory of the jvm increases from 100MB > until 470MB > after that it crashes with outofmemory error (JDO exception) > Increasing the plexus jvm memory does have no affect: > %PLEXUS_JAVA_EXE% %PLEXUS_OPTS% -Xmx900M -XX:MaxPermSize=128m -classpath > "%PLEXUS_HOME%\core\boot\plexus-classworlds-1.2-alpha-7.jar" > -Dclassworlds.conf="%PLEXUS_HOME%\conf\classworlds.conf" > -Dplexus.core=%PLEXUS_CORE% -Dplexus.system.path="%PATH%" > -Djava.io.tmpdir=%PLEXUS_TMPDIR% -Dplexus.home="%PLEXUS_HOME%" > -Dappserver.base="%PLEXUS_BASE%" -Dtools.jar="%TOOLS_JAR%" > org.codehaus.plexus.classworlds.launcher.Launcher %PLEXUS_CMD_LINE_ARGS% > So probably bug in fetch from db where all objects are retrieved ? > For us this is a showstopper. Would MySQL DB be a workaround ? I guess the > query is the same, so will the memory usage be ? > Where can I find the complete DDL script for mysql ? On the wiki there is > only 1 table ... ? > javax.jdo.JDODataStoreException: Iteration request failed : > SELECT > THIS.CHANGEFILE_ID,THIS.MODEL_ENCODING,THIS."NAME",THIS.REVISION,THIS.STATUS,THIS.FILES_INTEGER_IDX > AS JPOXORDER0 FROM > CHANGEFILE THIS WHERE ? = THIS.FILES_CHANGESET_ID_OID AND > THIS.FILES_INTEGER_IDX >= ? ORDER BY JPOXORDER0 NestedThrowables: SQL > Exception: Java exception: > 'Java heap space: java.lang.OutOfMemoryError'. -- 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: (MECLIPSE-324) Version 0.0.11.20070916-2300 is not working
Version 0.0.11.20070916-2300 is not working --- Key: MECLIPSE-324 URL: http://jira.codehaus.org/browse/MECLIPSE-324 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.0 Environment: Windows XP SP2, Java 1.6 Eclipse 3.3 Reporter: Marcin Dabrowski Priority: Blocker Attachments: .log, eclipse.txt I've installed new version via Eclipse update manager. After starting Eclipse I've got an error. Also error occures when I select Maven on Eclipse preferences page. In file .log I've attached log from eclipse, and in eclipse.txt my Eclipse configuration details. -- 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: (MECLIPSE-324) Version 0.0.11.20070916-2300 is not working
[ http://jira.codehaus.org/browse/MECLIPSE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107739 ] Marcin Dabrowski commented on MECLIPSE-324: --- When I tried to run Eclipse on Java 1.5 this bug is still present. > Version 0.0.11.20070916-2300 is not working > --- > > Key: MECLIPSE-324 > URL: http://jira.codehaus.org/browse/MECLIPSE-324 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Windows XP SP2, > Java 1.6 > Eclipse 3.3 >Reporter: Marcin Dabrowski >Priority: Blocker > Attachments: .log, eclipse.txt > > > I've installed new version via Eclipse update manager. > After starting Eclipse I've got an error. > Also error occures when I select Maven on Eclipse preferences page. > In file .log I've attached log from eclipse, and in eclipse.txt my Eclipse > configuration details. -- 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-1353) after a few weeks, continuum runs into outofmemory error
[ http://jira.codehaus.org/browse/CONTINUUM-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107740 ] Emmanuel Venisse commented on CONTINUUM-1353: - The "build fresh" option do a clean checkout for each build. In 1.1-beta-3, we fixed it and add a new option to run always a build definition even with no modification with an update. When you'll test beta-3, let us know if you have always this OOME, so we'll can close this issue > after a few weeks, continuum runs into outofmemory error > > > Key: CONTINUUM-1353 > URL: http://jira.codehaus.org/browse/CONTINUUM-1353 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-2 >Reporter: tony nys >Priority: Blocker > > when clicking on the build history, memory of the jvm increases from 100MB > until 470MB > after that it crashes with outofmemory error (JDO exception) > Increasing the plexus jvm memory does have no affect: > %PLEXUS_JAVA_EXE% %PLEXUS_OPTS% -Xmx900M -XX:MaxPermSize=128m -classpath > "%PLEXUS_HOME%\core\boot\plexus-classworlds-1.2-alpha-7.jar" > -Dclassworlds.conf="%PLEXUS_HOME%\conf\classworlds.conf" > -Dplexus.core=%PLEXUS_CORE% -Dplexus.system.path="%PATH%" > -Djava.io.tmpdir=%PLEXUS_TMPDIR% -Dplexus.home="%PLEXUS_HOME%" > -Dappserver.base="%PLEXUS_BASE%" -Dtools.jar="%TOOLS_JAR%" > org.codehaus.plexus.classworlds.launcher.Launcher %PLEXUS_CMD_LINE_ARGS% > So probably bug in fetch from db where all objects are retrieved ? > For us this is a showstopper. Would MySQL DB be a workaround ? I guess the > query is the same, so will the memory usage be ? > Where can I find the complete DDL script for mysql ? On the wiki there is > only 1 table ... ? > javax.jdo.JDODataStoreException: Iteration request failed : > SELECT > THIS.CHANGEFILE_ID,THIS.MODEL_ENCODING,THIS."NAME",THIS.REVISION,THIS.STATUS,THIS.FILES_INTEGER_IDX > AS JPOXORDER0 FROM > CHANGEFILE THIS WHERE ? = THIS.FILES_CHANGESET_ID_OID AND > THIS.FILES_INTEGER_IDX >= ? ORDER BY JPOXORDER0 NestedThrowables: SQL > Exception: Java exception: > 'Java heap space: java.lang.OutOfMemoryError'. -- 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: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
Container dependency jar file get copied during the deployment or during hte installation1 -- Key: MDEP-112 URL: http://jira.codehaus.org/browse/MDEP-112 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: copy-dependencies Affects Versions: 2.0 Environment: WindowXP(CYGWIN) JDK 1.5.0_07 Reporter: Alan Mehio Assignee: Brian Fox Priority: Trivial The dependency get copied even it is provided by the container This happens in the following scenario : module A has dependecies as below axis axis-schema 1.3 axis axis-wsdl4j 1.3 xml-apis xml-apis 1.0.b2 javax.xml jaxrpc-api 1.1 commons-discovery commons-discovery 0.2 axis axis-saaj 1.2 you have module B which has the below dependencies mygroup common 1.0.0 mygroup service 1.0.0 mygroup model 1.0.0 tomcat servlet-api 5.0.18 provided The one which get copied is servlet-api-2.3.jar On the otherhand, the other project is using the same dependency ( servlet-api ) but the only difference is the axis artifact and its dependencies are not included Regards, Alan Mehio London, UK -- 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-2234) activeProfile in ~/.m2/settings.xml is ignored when profiles section is missing or empty
[ http://jira.codehaus.org/browse/MNG-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107746 ] Krystian Nowak commented on MNG-2234: - It seems to be a duplicate of http://jira.codehaus.org/browse/MNG-3051 > activeProfile in ~/.m2/settings.xml is ignored when profiles section is > missing or empty > > > Key: MNG-2234 > URL: http://jira.codehaus.org/browse/MNG-2234 > Project: Maven 2 > Issue Type: Bug > Components: Profiles, Settings >Affects Versions: 2.0.4 >Reporter: Manfred Geiler >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > > When i have this settings.xml file in my user home dir, the activeProfile > setting is simply ignored by Maven: > > > env-test > > > Adding an empty profiles section does not help: > > > > > env-test > > > Well, adding a dummy profile makes it work: > > > > dummy > > > > env-test > > > Funny, isn't it? > Regards, > Manfred -- 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-3051) settings.xml doesn't handle profile from pom.xml
[
http://jira.codehaus.org/browse/MNG-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107745
]
Krystian Nowak commented on MNG-3051:
-
It seems to be a duplicate of http://jira.codehaus.org/browse/MNG-2234
I've got the same issue. Quick fix is to add an empty dummy in your
settings.xml file for to be read.
> settings.xml doesn't handle profile from pom.xml
>
>
> Key: MNG-3051
> URL: http://jira.codehaus.org/browse/MNG-3051
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Affects Versions: 2.0.6
>Reporter: Den Orlov
> Fix For: Reviewed Pending Version Assignment
>
> Attachments: nonworking-settings.xml, pom.xml, working-settings.xml
>
>
> I have profile specified in pom.xml (attached). And I try to specify it in
> settings.xml's (attache as nonworking-settings.xml) Accordng
> to help:active-profiles I get:
> {noformat}
> mvn help:active-profiles
> Active Profiles for Project 'test:test:jar:1.0-SNAPSHOT':
> There are no active profiles.
> {noformat}
> When I specify the same profile name in settings.xml (attached as
> working-settings.xml) maven see both profiles (from pom.xml and from
> settings.xml):
> {noformat}
> mvn help:active-profiles
> Active Profiles for Project 'test:test:jar:1.0-SNAPSHOT':
> The following profiles are active:
> - env-test (source: pom)
> - env-test (source: settings.xml)
> {noformat}
--
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-1436) Add build definition template
[ http://jira.codehaus.org/browse/CONTINUUM-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107747 ] Olivier Lamy commented on CONTINUUM-1436: - database model change has been committed in rev 577184. Full implementation will be done in 1.1-beta-4. > Add build definition template > - > > Key: CONTINUUM-1436 > URL: http://jira.codehaus.org/browse/CONTINUUM-1436 > Project: Continuum > Issue Type: Improvement > Components: Core system, Web - UI >Reporter: Emmanuel Venisse >Assignee: Olivier Lamy > Fix For: 1.1-beta-3 > > > A build definition template is a set of build definitions that can be add to > a group. > A user will can choose to attach a template (by default no template will be > selected and we'll use the actual mechanism) to a group. > The templates list will be accessible from the admin menu. > h1. Process: > - when the user add a new project, if no project group is selected, he can > choose a template to add to the group > - when the user create a new group, he can choose a template > - from the group build def page, the user can choose a template to add > h1. storage: > Templates will be stored in a new table. Entries in this table will be linked > to some build definitions stored in the build definitions table > These build definitions won't be use directly by groups but only by templates > so when the user want to use a template, continuum will *copy* all build > definitions from the template to the group so templated build definitions > will can be modified without affected build def already used by groups. -- 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] Updated: (CONTINUUM-1436) Add build definition template
[ http://jira.codehaus.org/browse/CONTINUUM-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1436: Fix Version/s: (was: 1.1-beta-3) 1.1-beta-4 > Add build definition template > - > > Key: CONTINUUM-1436 > URL: http://jira.codehaus.org/browse/CONTINUUM-1436 > Project: Continuum > Issue Type: Improvement > Components: Core system, Web - UI >Reporter: Emmanuel Venisse >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > A build definition template is a set of build definitions that can be add to > a group. > A user will can choose to attach a template (by default no template will be > selected and we'll use the actual mechanism) to a group. > The templates list will be accessible from the admin menu. > h1. Process: > - when the user add a new project, if no project group is selected, he can > choose a template to add to the group > - when the user create a new group, he can choose a template > - from the group build def page, the user can choose a template to add > h1. storage: > Templates will be stored in a new table. Entries in this table will be linked > to some build definitions stored in the build definitions table > These build definitions won't be use directly by groups but only by templates > so when the user want to use a template, continuum will *copy* all build > definitions from the template to the group so templated build definitions > will can be modified without affected build def already used by groups. -- 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: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[ http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107749 ] Brian Fox commented on MDEP-112: Not sure I completely understand. You're saying it is copying a dependency marked as provided? This is normal since I'm getting the list of all dependencies from Maven. If you don't what provided dependencies, then use excludeScope=provided > Container dependency jar file get copied during the deployment or during hte > installation1 > -- > > Key: MDEP-112 > URL: http://jira.codehaus.org/browse/MDEP-112 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 > Environment: WindowXP(CYGWIN) JDK 1.5.0_07 >Reporter: Alan Mehio >Assignee: Brian Fox >Priority: Trivial > > The dependency get copied even it is provided by the container > This happens in the following scenario : > module A has dependecies as below > > > axis > axis-schema > 1.3 > > > axis > axis-wsdl4j > 1.3 > > > xml-apis > xml-apis > 1.0.b2 > > > javax.xml > jaxrpc-api > 1.1 > > > commons-discovery > commons-discovery > 0.2 > > > axis > axis-saaj > 1.2 > > > you have module B which has the below dependencies > > > mygroup > common > 1.0.0 > > > mygroup > service > 1.0.0 > > > mygroup > model > 1.0.0 > > > tomcat > servlet-api > 5.0.18 > provided > > > The one which get copied is servlet-api-2.3.jar > On the otherhand, the other project is using the same dependency ( > servlet-api ) but the only difference is the axis artifact and its > dependencies are not included > Regards, > Alan Mehio > London, UK -- 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] Updated: (CONTINUUM-1421) Add an admin task to stop properly Continuum
[ http://jira.codehaus.org/browse/CONTINUUM-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1421: Fix Version/s: (was: To Sort) 1.1-beta-4 > Add an admin task to stop properly Continuum > > > Key: CONTINUUM-1421 > URL: http://jira.codehaus.org/browse/CONTINUUM-1421 > Project: Continuum > Issue Type: Improvement > Components: Core system >Reporter: Emmanuel Venisse >Assignee: Olivier Lamy > Fix For: 1.1-beta-4 > > > When a project is building and an admin stop continuum, the actual build > result is never marked as stopped. > A possible solution would be to planned a shutdown in the web interface via a > form. With this action, all sheduler will be stopped and a message will be > sent to the admin (page after the submit in the shutdown form). With this > message, the admin will know that he can shutdown Continuum properly without > non ended build process. -- 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-1473) Server Id in wagon notifier edit pages is required but doesn't have validation
Server Id in wagon notifier edit pages is required but doesn't have validation -- Key: CONTINUUM-1473 URL: http://jira.codehaus.org/browse/CONTINUUM-1473 Project: Continuum Issue Type: Bug Components: Notification Subsystem Reporter: Teodoro Cue Jr. Priority: Minor -- 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] Updated: (CONTINUUM-1473) Server Id in wagon notifier edit pages is required but doesn't have validation
[ http://jira.codehaus.org/browse/CONTINUUM-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-1473: --- Attachment: CONTINUUM-1473-continuum-webapp.patch Patch attached. Added webwork client side validation. Also added the localization in the appropriate properties file. > Server Id in wagon notifier edit pages is required but doesn't have validation > -- > > Key: CONTINUUM-1473 > URL: http://jira.codehaus.org/browse/CONTINUUM-1473 > Project: Continuum > Issue Type: Bug > Components: Notification Subsystem >Reporter: Teodoro Cue Jr. >Priority: Minor > Attachments: CONTINUUM-1473-continuum-webapp.patch > > -- 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] Updated: (CONTINUUM-1473) Server Id in wagon notifier edit pages is required but doesn't have validation
[ http://jira.codehaus.org/browse/CONTINUUM-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1473: Affects Version/s: 1.1-beta-3 Fix Version/s: 1.1-beta-4 Patch Submitted: [Yes] > Server Id in wagon notifier edit pages is required but doesn't have validation > -- > > Key: CONTINUUM-1473 > URL: http://jira.codehaus.org/browse/CONTINUUM-1473 > Project: Continuum > Issue Type: Bug > Components: Notification Subsystem >Affects Versions: 1.1-beta-3 >Reporter: Teodoro Cue Jr. >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: CONTINUUM-1473-continuum-webapp.patch > > -- 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: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107761 ] Andris Rauda commented on WAGONSSH-53: -- I have the same problem. after known_hosts were created, I'm no more prompted for "yes", but still non-interactive build fails like this: [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Authentication failed: Cannot connect. Reason: Auth fail whereas in interactive mode I'm prompted for password and everything works allright. I believe, I've specified the same password in settings.xml correctly (checked twise) > Error deploying artifact: Authentication failed: Cannot connect. Reason: > - > > Key: WAGONSSH-53 > URL: http://jira.codehaus.org/browse/WAGONSSH-53 > Project: wagon-ssh > Issue Type: Bug > Environment: My operating system is unix > sun4-cross: uname -a > SunOS swdc-sf06e 5.8 Generic_117350-24 sun4u sparc SUNW,Sun-Fire-15000 >Reporter: sharda sheshabhattar > > Hi, > I am having problems using Maven deploy feature in the non interactive mode. > However the same command ,when used in the interactive mode works fine. It > prompts me for > The authenticity of host 'dsddb2d-swdc' can't be established. > DSA key fingerprint is 09:a4:e9:e9:44:2e:59:d0:91:40:09:47:32:91:39:be. > Are you sure you want to continue connecting? (yes/no): > It proceeds when I type yes.It prompts me about 4-5 times for each deploy. > I need to urgently develop something and make this work in the > non-interactive mode. Please help > Regards, > Sharda > Here is the trace output when I run in the non-interactive mode: > > /xenv/Maven/X/2.0.4/bin/mvn -s settings.xml deploy:deploy-file > -DpomFile=commons-digester-1.5.pom -Dr > epositoryId=nyhub1 -Durl=scp://nyhub1/xenv/scripts/Hermesmvnrep > -Dfile=/xenv/commons-digester/X/1.5/l > ib/commons-digester.jar > + Error stacktraces are turned on. > Maven version: 2.0.4 > [DEBUG] Building Maven user-level plugin registry from: > '/home/sunle/.m2/plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > '/xenv/Maven/X/2.0.4/conf/plugin-registry.x > ml' > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'deploy'. > [DEBUG] maven-deploy-plugin: resolved to version 2.2.1 from repository central > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for > project: null:maven-depl > oy-plugin:maven-plugin:2.2.1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: > org.apache.maven.plugins > :maven-plugins:pom:1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: > org.apache.maven:maven-parent:pom:1 > from the repository. > [INFO] > > [INFO] Building Maven Default Project > [INFO]task-segment: [deploy:deploy-file] (aggregator-style) > [INFO] > > [DEBUG] > org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2.1:runtime > (selected for runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-artifa > ct-manager:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for > runtime) > [DEBUG] > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime > (selected for runtim > e) > [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for > runtime) > [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-artifa > ct:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-reposi > tory-metadata:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime > (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime > (selected for runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-project:jar:2.0 fr > om the repository. > [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for > runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-model: > jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-model:
[jira] Updated: (MNG-2045) Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
[ http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MNG-2045: --- Attachment: MNG-2045-maven-project-r577340.patch1 I'm having the same issue where we have one module whose main classes depend on test classes from another module. I'm attaching a simple fix for this where the artifact type is checked (test-jar) when adding the path. > Maven can't compile against sibling test-jar dependency in multiproject (Test > Attached) > --- > > Key: MNG-2045 > URL: http://jira.codehaus.org/browse/MNG-2045 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: WinXP >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.6 > > Attachments: it1021.tar.gz, mng-2045-ittest.zip, > MNG-2045-maven-project-r577340.patch1, sample.zip > > > I have 2 projects under a parent like so: > --Parent > --- sample-jar > --- sample-jar-user > sample-jar builds and installs a test-jar along with the normal jar. > sample-jar-user depends on the test-jar at compile time. When I build from > the parent folder, the build fails because it can't find the class. When I go > to sample-jar-user and build, it works fine. > In the attached test case, to reproduce: > from the root folder, run mvn clean install - See it fail. > cd sample-jar-user; mvn clean install - see it succeed. > I remember reading somewhere that in multiprojects, maven attempts to locate > the sibling classes in the source tree instead of using the jars from the > repository. I'm guessing the problem is here that it's not looking in > ../sample-jar/target/test-classes for this code, but really one should expect > this to come from the repository. -- 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] Updated: (MNG-2045) Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
[ http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MNG-2045: --- Attachment: MNG-2045-maven-project-r577340.patch2 This patch has a slight enhancement over the first one I submitted. The problem with the first, is that if "clean compile" is run in a multi-module project, then the test-classes directory does not exist. So this patch checks for the existence of the test output directory. And if it does not exist, it falls back to the repository. > Maven can't compile against sibling test-jar dependency in multiproject (Test > Attached) > --- > > Key: MNG-2045 > URL: http://jira.codehaus.org/browse/MNG-2045 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: WinXP >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.6 > > Attachments: it1021.tar.gz, mng-2045-ittest.zip, > MNG-2045-maven-project-r577340.patch1, MNG-2045-maven-project-r577340.patch2, > sample.zip > > > I have 2 projects under a parent like so: > --Parent > --- sample-jar > --- sample-jar-user > sample-jar builds and installs a test-jar along with the normal jar. > sample-jar-user depends on the test-jar at compile time. When I build from > the parent folder, the build fails because it can't find the class. When I go > to sample-jar-user and build, it works fine. > In the attached test case, to reproduce: > from the root folder, run mvn clean install - See it fail. > cd sample-jar-user; mvn clean install - see it succeed. > I remember reading somewhere that in multiprojects, maven attempts to locate > the sibling classes in the source tree instead of using the jars from the > repository. I'm guessing the problem is here that it's not looking in > ../sample-jar/target/test-classes for this code, but really one should expect > this to come from the repository. -- 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: (NMAVEN-66) Support for Satellite Assemblies
[ http://jira.codehaus.org/browse/NMAVEN-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107769 ] Shane Isbell commented on NMAVEN-66: Currently, NMaven supports one type of attached artifact: exe.config. This needs to be extended for general artifact types, including satellitte assemblies. If you do a search for exe.config in the java class files, you will have a good idea of the classes that need to be modified to add support for satellite assemblies. Components Impacted: 1) ArtifactContextImpl (trivial) 2) ArtifactInstallerImpl: Add artifact to pom.xml 3) ProjectDaoImpl (trivial excludes) 4) RepositoryConverterImpl Plugins impacted: 1) Deploy plugin (as you need to deploy the satellites along with the main artifact). I think the impact to any particular class is not high but to get it all working together and tested will require a modest amount of effort. > Support for Satellite Assemblies > > > Key: NMAVEN-66 > URL: http://jira.codehaus.org/browse/NMAVEN-66 > Project: NMaven > Issue Type: New Feature >Reporter: Shane Isbell >Priority: Minor > > Add support for satellite assemblies so that applications can use locale > specific resources. This feature includes: 1) resolving and downloading > satellite assemblies; 2) installing into the correct resource directory of > the main assembly's maven repo directory. -- 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: (MCLOVER-82) Selection of unclovered ear based upon timestamp is too restrictive
Selection of unclovered ear based upon timestamp is too restrictive --- Key: MCLOVER-82 URL: http://jira.codehaus.org/browse/MCLOVER-82 Project: Maven 2.x Clover Plugin Issue Type: Bug Affects Versions: 2.4 Environment: windows/jdk1.5/maven 2. 0.7 Reporter: Martin Franklin Fix For: 2.5 Attachments: cloverlag.diff When clover plugin is run on a jar artifact using the install lifecycle step, the unclovered jar file is also created and installed. In certain circumstances (which appear to be timing related) the unclovered artifact is installed _after_ the clovered artifact. The clover plugin, when creating an ear will then use the unclovered artifact in preference to the unclovered artifact. The patch provided widens the window and so long as the clovered artifact is no more than 100ms older than the unclovered artifact, the clovered artifact will be used. -- 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] Updated: (CONTINUUM-1233) Reduce number of clicks to add a project
[ http://jira.codehaus.org/browse/CONTINUUM-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1233: Fix Version/s: (was: 1.1-beta-3) 1.1-beta-4 > Reduce number of clicks to add a project > > > Key: CONTINUUM-1233 > URL: http://jira.codehaus.org/browse/CONTINUUM-1233 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1-alpha-1 >Reporter: Wendy Smoak >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-4 > > > With the addition of the project group roles, adding a Maven 2 project > changed from one click (Add M2 Project button) to three clicks-- focus on > the Add New Project drop-down, select a type, click the Add button. > If we made the default for the select list configurable somewhere, or even > made it "remember" the last choice used during that session, then adding > multiple projects would be much more pleasant. > In addition, adding a project returns you to the Project Groups page, so that > you have to click to get back to the group summary page to add the next > project. (Similar to CONTINUUM-1115) -- 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] Updated: (CONTINUUM-1388) the NOTICE file is overzealous in declaring dependencies
[ http://jira.codehaus.org/browse/CONTINUUM-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1388: Fix Version/s: (was: 1.1-beta-3) 1.1-beta-4 > the NOTICE file is overzealous in declaring dependencies > > > Key: CONTINUUM-1388 > URL: http://jira.codehaus.org/browse/CONTINUUM-1388 > Project: Continuum > Issue Type: Improvement >Affects Versions: 1.1-beta-2 >Reporter: Brett Porter > Fix For: 1.1-beta-4 > > > we only need to say, for example, software developed by the ASF once, and all > the unnamed ones don't need to be there. > This might require fixes in the remote reosurces plugin and an update. -- 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] Updated: (CONTINUUM-1166) Integration test failures: AccountSecurityTest
[ http://jira.codehaus.org/browse/CONTINUUM-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1166: Fix Version/s: (was: 1.1-beta-3) 1.1-beta-4 > Integration test failures: AccountSecurityTest > -- > > Key: CONTINUUM-1166 > URL: http://jira.codehaus.org/browse/CONTINUUM-1166 > Project: Continuum > Issue Type: Task > Components: Testing >Affects Versions: 1.1-alpha-1 > Environment: WinXP Continuum 1.1-SNAPSHOT r507397 >Reporter: Wendy Smoak > Fix For: 1.1-beta-4 > > Attachments: AccountSecurityTest-r507420.txt, > org.apache.continuum.web.test.AccountSecurityTest.txt > > > --- > Test set: org.apache.continuum.web.test.AccountSecurityTest > --- > Tests run: 5, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 107.797 sec > <<< FAILURE! > When editing a user, effective roles are displayed on the first page, but it > is necessary to click the 'Edit Roles' in order to add or delete roles. > Full Surefire report attached. -- 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-3156) NullPointerException with mvn dependency:sources
[
http://jira.codehaus.org/browse/MNG-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107775
]
John Kew commented on MNG-3156:
---
I've encountered this error too. I fixed this by applying a patch similar to:
---
maven/artifact/trunk/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java
2007/08/17 06:07:31 566931
+++
maven/artifact/trunk/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java
2007/08/20 14:44:01 567719
@@ -89,6 +89,12 @@
{
File systemFile = artifact.getFile();
+if ( systemFile == null )
+{
+throw new ArtifactNotFoundException(
+"System artifact: " + artifact + " has no file
attached", artifact );
+}
+
if ( !systemFile.exists() )
{
throw new ArtifactNotFoundException(
This fix is available in the 2.0.x branch but it was recently removed from
trunk in r511859 on Sept. 1st. I won't post a patch since carlos has already
committed a similar patch. Here's the revision history for trunk, however:
http://svn.apache.org/viewvc/maven/artifact/trunk/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java?view=log
> NullPointerException with mvn dependency:sources
>
>
> Key: MNG-3156
> URL: http://jira.codehaus.org/browse/MNG-3156
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.7
>Reporter: Sam Imari
> Attachments: pom.xml
>
>
> I got a NPE when I use mvn dependency:sources to download all the sources for
> my appfuse M5 project:
> $ mvn -e -U dependency:sources
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO] org.apache.maven.plugins: checking for updates from appfuse
> [INFO] org.apache.maven.plugins: checking for updates from central
> [INFO] org.codehaus.mojo: checking for updates from appfuse
> [INFO] org.codehaus.mojo: checking for updates from central
> [INFO] artifact org.apache.maven.plugins:maven-dependency-plugin: checking
> for updates from appfuse
> [INFO] artifact org.apache.maven.plugins:maven-dependency-plugin: checking
> for updates from central
> [INFO]
>
> [INFO] Building AppFuse Struts 2 Application
> [INFO]task-segment: [dependency:sources]
> [INFO]
>
> Downloading:
> http://repo1.maven.org/maven2/org/codehaus/xfire/bcprov-jdk15/133/bcprov-jdk15-133.pom
> Downloading:
> http://static.appfuse.org/repository/org/codehaus/xfire/bcprov-jdk15/133/bcprov-jdk15-133.pom
> Downloading:
> http://repo1.maven.org/maven2/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom
> Downloading:
> http://static.appfuse.org/repository/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom
> Downloading: http://repo1.maven.org/maven2/wss4j/wss4j/1.5.1/wss4j-1.5.1.pom
> Downloading:
> http://static.appfuse.org/repository/wss4j/wss4j/1.5.1/wss4j-1.5.1.pom
> Downloading:
> http://repo1.maven.org/maven2/xfire/saaj-impl/1.3/saaj-impl-1.3.pom
> Downloading:
> http://static.appfuse.org/repository/xfire/saaj-impl/1.3/saaj-impl-1.3.pom
> [INFO] [dependency:sources]
> Downloading: http://repo1.maven.org/maven2/ant/ant/1.5/ant-1.5-sources.jar
> Downloading:
> http://static.appfuse.org/repository/ant/ant/1.5/ant-1.5-sources.jar
> Downloading: http://repo1.maven.org/maven2/asm/asm/1.5.3/asm-1.5.3-sources.jar
> Downloading:
> http://static.appfuse.org/repository/asm/asm/1.5.3/asm-1.5.3-sources.jar
> Downloading:
> http://repo1.maven.org/maven2/asm/asm-attrs/1.5.3/asm-attrs-1.5.3-sources.jar
> Downloading:
> http://static.appfuse.org/repository/asm/asm-attrs/1.5.3/asm-attrs-1.5.3-sources.jar
> Downloading:
> http://repo1.maven.org/maven2/aspectj/aspectjweaver/1.5.3/aspectjweaver-1.5.3-sources.jar
> Downloading:
> http://static.appfuse.org/repository/aspectj/aspectjweaver/1.5.3/aspectjweaver-1.5.3-sources.jar
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73)
> at
> org.apache.maven.plugin.dependency.utils.resolvers.DefaultArtifactsResolver.re
[jira] Commented: (MNG-3156) NullPointerException with mvn dependency:sources
[ http://jira.codehaus.org/browse/MNG-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107776 ] John Kew commented on MNG-3156: --- My suggestion for Sam is to try out the 2.0.x branch from subversion. > NullPointerException with mvn dependency:sources > > > Key: MNG-3156 > URL: http://jira.codehaus.org/browse/MNG-3156 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.7 >Reporter: Sam Imari > Attachments: pom.xml > > > I got a NPE when I use mvn dependency:sources to download all the sources for > my appfuse M5 project: > $ mvn -e -U dependency:sources > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'dependency'. > [INFO] org.apache.maven.plugins: checking for updates from appfuse > [INFO] org.apache.maven.plugins: checking for updates from central > [INFO] org.codehaus.mojo: checking for updates from appfuse > [INFO] org.codehaus.mojo: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-dependency-plugin: checking > for updates from appfuse > [INFO] artifact org.apache.maven.plugins:maven-dependency-plugin: checking > for updates from central > [INFO] > > [INFO] Building AppFuse Struts 2 Application > [INFO]task-segment: [dependency:sources] > [INFO] > > Downloading: > http://repo1.maven.org/maven2/org/codehaus/xfire/bcprov-jdk15/133/bcprov-jdk15-133.pom > Downloading: > http://static.appfuse.org/repository/org/codehaus/xfire/bcprov-jdk15/133/bcprov-jdk15-133.pom > Downloading: > http://repo1.maven.org/maven2/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom > Downloading: > http://static.appfuse.org/repository/xml-security/xmlsec/1.3.0/xmlsec-1.3.0.pom > Downloading: http://repo1.maven.org/maven2/wss4j/wss4j/1.5.1/wss4j-1.5.1.pom > Downloading: > http://static.appfuse.org/repository/wss4j/wss4j/1.5.1/wss4j-1.5.1.pom > Downloading: > http://repo1.maven.org/maven2/xfire/saaj-impl/1.3/saaj-impl-1.3.pom > Downloading: > http://static.appfuse.org/repository/xfire/saaj-impl/1.3/saaj-impl-1.3.pom > [INFO] [dependency:sources] > Downloading: http://repo1.maven.org/maven2/ant/ant/1.5/ant-1.5-sources.jar > Downloading: > http://static.appfuse.org/repository/ant/ant/1.5/ant-1.5-sources.jar > Downloading: http://repo1.maven.org/maven2/asm/asm/1.5.3/asm-1.5.3-sources.jar > Downloading: > http://static.appfuse.org/repository/asm/asm/1.5.3/asm-1.5.3-sources.jar > Downloading: > http://repo1.maven.org/maven2/asm/asm-attrs/1.5.3/asm-attrs-1.5.3-sources.jar > Downloading: > http://static.appfuse.org/repository/asm/asm-attrs/1.5.3/asm-attrs-1.5.3-sources.jar > Downloading: > http://repo1.maven.org/maven2/aspectj/aspectjweaver/1.5.3/aspectjweaver-1.5.3-sources.jar > Downloading: > http://static.appfuse.org/repository/aspectj/aspectjweaver/1.5.3/aspectjweaver-1.5.3-sources.jar > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) > at > org.apache.maven.plugin.dependency.utils.resolvers.DefaultArtifactsResolver.resolve(DefaultArtifactsResolver.java:81) > at > org.apache.maven.plugin.dependency.AbstractDependencyFilterMojo.getClassifierTranslatedDependencies(AbstractDependencyFilterMojo.java:308) > at > org.apache.maven.plugin.dependency.AbstractDependencyFilterMojo.getDependencySets(AbstractDependencyFilterMojo.java:265) > at > org.apache.maven.plugin.dependency.resolvers.ResolveDependencySourcesMojo.execute(ResolveDependencySourcesMojo.java:69) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.De
[jira] Updated: (CONTINUUM-1452) Show a summary total of the Projects and Build Status columns on the Project Groups page
[ http://jira.codehaus.org/browse/CONTINUUM-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1452: Fix Version/s: (was: To Sort) 1.1-beta-4 > Show a summary total of the Projects and Build Status columns on the Project > Groups page > > > Key: CONTINUUM-1452 > URL: http://jira.codehaus.org/browse/CONTINUUM-1452 > Project: Continuum > Issue Type: Wish > Components: Web - UI >Affects Versions: 1.1-beta-2 >Reporter: Tomislav Stojcevich >Assignee: Olivier Lamy >Priority: Minor > Fix For: 1.1-beta-4 > > Attachments: Project Group with totals.jpg > > > It would be nice to see a summary total of all of the projects and the status > displayed at the bottom of the the Projects and Build Status columns on the > Project Groups page. -- 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-1409) A build does not say which build definition it came from
[ http://jira.codehaus.org/browse/CONTINUUM-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1409. --- Assignee: Olivier Lamy Resolution: Duplicate Fix Version/s: 1.1-beta-3 > A build does not say which build definition it came from > > > Key: CONTINUUM-1409 > URL: http://jira.codehaus.org/browse/CONTINUUM-1409 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Henri Yandell >Assignee: Olivier Lamy > Fix For: 1.1-beta-3 > > > Looking at > http://vmbuild1.apache.org/continuum/buildResult.action?buildId=2126&projectId=186 > - I can't tell which of the two build definitions built it. -- 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: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[
http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107783
]
Alan Mehio commented on MDEP-112:
-
Brian,
Many thanks for your reply. Sorry for my brief description. the servlet-api get
copied into the ${TOMCAT_HOME}/webapps/myweb/WEB-INF/lib
even it is stated that the dependency is provided by the container (Tomcat web
container).
I am wondering why should the servlet-api get copied into the above mentioned
directory even it is supplied by the container. I have checked my other pom and
there is no mention for servlet-api dependency except in the above mentioned
module.
As I understand from the provided, it will not be copied since
the artifact will be provided by the container.
Many thanks
Regards,
Alan Mehio
London, UK
> Container dependency jar file get copied during the deployment or during hte
> installation1
> --
>
> Key: MDEP-112
> URL: http://jira.codehaus.org/browse/MDEP-112
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: copy-dependencies
>Affects Versions: 2.0
> Environment: WindowXP(CYGWIN) JDK 1.5.0_07
>Reporter: Alan Mehio
>Assignee: Brian Fox
>Priority: Trivial
>
> The dependency get copied even it is provided by the container
> This happens in the following scenario :
> module A has dependecies as below
>
>
> axis
> axis-schema
> 1.3
>
>
> axis
> axis-wsdl4j
> 1.3
>
>
> xml-apis
> xml-apis
> 1.0.b2
>
>
> javax.xml
> jaxrpc-api
> 1.1
>
>
> commons-discovery
> commons-discovery
> 0.2
>
>
> axis
> axis-saaj
> 1.2
>
>
> you have module B which has the below dependencies
>
>
> mygroup
> common
> 1.0.0
>
>
> mygroup
> service
> 1.0.0
>
>
> mygroup
> model
> 1.0.0
>
>
> tomcat
> servlet-api
> 5.0.18
> provided
>
>
> The one which get copied is servlet-api-2.3.jar
> On the otherhand, the other project is using the same dependency (
> servlet-api ) but the only difference is the axis artifact and its
> dependencies are not included
> Regards,
> Alan Mehio
> London, UK
--
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] Updated: (CONTINUUM-1355) No admin user found after Tomcat shutdown
[ http://jira.codehaus.org/browse/CONTINUUM-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1355: Assignee: Olivier Lamy Fix Version/s: 1.1-beta-4 > No admin user found after Tomcat shutdown > - > > Key: CONTINUUM-1355 > URL: http://jira.codehaus.org/browse/CONTINUUM-1355 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-1 > Environment: Linux, Tomcat 5.5.17 >Reporter: Pavel Halas >Assignee: Olivier Lamy >Priority: Critical > Fix For: 1.1-beta-4 > > Attachments: continuum.xml > > > Hi, > using the latest snapshot (from yesterday) running on Tomcat 5.5.17. After > the Tomcat kill and running again, Continuum starts with "Create Admin User" > page saying "No admin user found" in the log. > This has been experienced even with the older versions (1.1 snapshots). -- 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-1355) No admin user found after Tomcat shutdown
[ http://jira.codehaus.org/browse/CONTINUUM-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107781 ] Olivier Lamy commented on CONTINUUM-1355: - Which tomcat version do you use ? IMHO The shutdown doesn't work properly with tomcat due to the ehcache shutdowHook which failed witn an NPE. Looks related to http://issues.apache.org/bugzilla/show_bug.cgi?id=40212. A solution is to upgrade ehcache to version 1.3 which has a shutdowhook off by default. (testing with tomcat 6.0.14 and works fine) Can you try with manual replace of ehcache jar in continuum webapp ? Thanks > No admin user found after Tomcat shutdown > - > > Key: CONTINUUM-1355 > URL: http://jira.codehaus.org/browse/CONTINUUM-1355 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-beta-1 > Environment: Linux, Tomcat 5.5.17 >Reporter: Pavel Halas >Priority: Critical > Fix For: 1.1-beta-4 > > Attachments: continuum.xml > > > Hi, > using the latest snapshot (from yesterday) running on Tomcat 5.5.17. After > the Tomcat kill and running again, Continuum starts with "Create Admin User" > page saying "No admin user found" in the log. > This has been experienced even with the older versions (1.1 snapshots). -- 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: (MDEP-112) Container dependency jar file get copied during the deployment or during hte installation1
[ http://jira.codehaus.org/browse/MDEP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107784 ] Brian Fox commented on MDEP-112: I'm getting more confused now. Are you referring to the war plugin or the dependency plugin? Can you paste your pom, or better attach a sample project? > Container dependency jar file get copied during the deployment or during hte > installation1 > -- > > Key: MDEP-112 > URL: http://jira.codehaus.org/browse/MDEP-112 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 > Environment: WindowXP(CYGWIN) JDK 1.5.0_07 >Reporter: Alan Mehio >Assignee: Brian Fox >Priority: Trivial > > The dependency get copied even it is provided by the container > This happens in the following scenario : > module A has dependecies as below > > > axis > axis-schema > 1.3 > > > axis > axis-wsdl4j > 1.3 > > > xml-apis > xml-apis > 1.0.b2 > > > javax.xml > jaxrpc-api > 1.1 > > > commons-discovery > commons-discovery > 0.2 > > > axis > axis-saaj > 1.2 > > > you have module B which has the below dependencies > > > mygroup > common > 1.0.0 > > > mygroup > service > 1.0.0 > > > mygroup > model > 1.0.0 > > > tomcat > servlet-api > 5.0.18 > provided > > > The one which get copied is servlet-api-2.3.jar > On the otherhand, the other project is using the same dependency ( > servlet-api ) but the only difference is the axis artifact and its > dependencies are not included > Regards, > Alan Mehio > London, UK -- 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-1054) IllegalStateException stack adding pom
[ http://jira.codehaus.org/browse/CONTINUUM-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107796 ] Ellecer Valencia commented on CONTINUUM-1054: - As I said, I am getting results different from what the others have been getting. I am not just complaining about a stracktrace coming out in the logs. I am complaining that I cannot add a maven 2 project into Continuum *at all*. How can anyone say "it's not really an exception"? If you can't do what the app is supposed to let you do - what do you call that? The error message displayed in the interface is this: "The specified resource isn't a file or the protocol used isn't allowed." The stacktrace that comes out is identical to the one in this bug. Now is it possible that the same stacktrace is being thrown for entirely different reasons? A friend mentioned it might be a URL issue, but the URL has been parsed fine by Hudson and Bamboo, which are both Java webapps, so I don't think that's the case. Is there a config setting to increase the log levels as it might show a bit more info on what's going on? Should I add this as a different bug, since the situation described in the originating bug is a bit different from what I'm getting? (ie, they can add a project, while i can't) > IllegalStateException stack adding pom > -- > > Key: CONTINUUM-1054 > URL: http://jira.codehaus.org/browse/CONTINUUM-1054 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1-alpha-1 >Reporter: Carlos Sanchez >Priority: Minor > Fix For: Future > > > Adding a m2 pom from a web location causes this stack trace, although seems > to work fine > 2006-12-13 10:46:07,109 [SocketListener0-1] INFO DispatcherUtils >- Unable to find 'webwork.multipart.saveDir' property setting. Defaulting > to javax.servlet.context.tempdir > 2006-12-13 10:46:07,156 [SocketListener0-1] WARN MultiPartRequest >- Item is a file upload of 0 size, ignoring > 2006-12-13 10:46:07,156 [SocketListener0-1] ERROR DispatcherUtils >- Error setting character encoding to 'UTF-8' - ignoring. > java.lang.IllegalStateException: getReader() or getInputStream() called > at > org.mortbay.jetty.servlet.ServletHttpRequest.setCharacterEncoding(ServletHttpRequest.java:602) > at > javax.servlet.ServletRequestWrapper.setCharacterEncoding(ServletRequestWrapper.java:112) > at > com.opensymphony.webwork.dispatcher.DispatcherUtils.prepare(DispatcherUtils.java:392) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:160) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) > at org.mortbay.http.HttpServer.service(HttpServer.java:909) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) -- 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] Updated: (MNG-2045) Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
[ http://jira.codehaus.org/browse/MNG-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2045: -- Fix Version/s: (was: 2.0.6) 2.0.8 > Maven can't compile against sibling test-jar dependency in multiproject (Test > Attached) > --- > > Key: MNG-2045 > URL: http://jira.codehaus.org/browse/MNG-2045 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: WinXP >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.8 > > Attachments: it1021.tar.gz, mng-2045-ittest.zip, > MNG-2045-maven-project-r577340.patch1, MNG-2045-maven-project-r577340.patch2, > sample.zip > > > I have 2 projects under a parent like so: > --Parent > --- sample-jar > --- sample-jar-user > sample-jar builds and installs a test-jar along with the normal jar. > sample-jar-user depends on the test-jar at compile time. When I build from > the parent folder, the build fails because it can't find the class. When I go > to sample-jar-user and build, it works fine. > In the attached test case, to reproduce: > from the root folder, run mvn clean install - See it fail. > cd sample-jar-user; mvn clean install - see it succeed. > I remember reading somewhere that in multiprojects, maven attempts to locate > the sibling classes in the source tree instead of using the jars from the > repository. I'm guessing the problem is here that it's not looking in > ../sample-jar/target/test-classes for this code, but really one should expect > this to come from the repository. -- 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: (MRELEASE-211) set version in batch mode
[
http://jira.codehaus.org/browse/MRELEASE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107800
]
William Ferguson commented on MRELEASE-211:
---
Um, correct me if I'm wrong, but isn't this what the *useReleaseProfile*
parameter on release:perform it there for?
Ie
{code}
maven-release-plugin
false
{code}
will give you exactly what you want.
> set version in batch mode
> -
>
> Key: MRELEASE-211
> URL: http://jira.codehaus.org/browse/MRELEASE-211
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
>Affects Versions: 2.0-beta-5
> Environment: win XP pro SP2, maven 2.0.5, maven release plugin
> 2.0-beta-5
>Reporter: Andrew Chikvaidze
>
> I think a lot of developer teams often don't need generate javadoc for their
> project every time when running release:perform.
> I think it's very useful to add an option to disable javadoc creation.
> When I tried to pass to maven "-DperformRelease=false" this haven't effect.
> Later I saw in function
> private void perform( ReleaseDescriptor releaseDescriptor, Settings
> settings, List reactorProjects,
> File checkoutDirectory, String goals, boolean
> useReleaseProfile,
> ReleaseManagerListener listener, ReleaseResult
> result )
> the code:
> if ( useReleaseProfile )
> {
> if ( !StringUtils.isEmpty( additionalArguments ) )
> {
> /*
> evil hack (we don't need javadoc)
> additionalArguments = additionalArguments + "
> -DperformRelease=true";
> */
> additionalArguments = additionalArguments + "
> -DperformRelease=false";
> }
> else
> {
> /*
> evil hack (we don't need javadoc)
> additionalArguments = "-DperformRelease=true";
> */
> additionalArguments = "-DperformRelease=false";
> }
> }
> so, unfortunately now I cannot set -DperformRelease=false..
--
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
