[jira] Reopened: (MWAR-52) WAR plugin does not honor the webXml configuration setting [patch included!]
[ http://jira.codehaus.org/browse/MWAR-52?page=all ]
Andreas Schildbach reopened MWAR-52:
Here is my testcase:
org.apache.maven.plugins
maven-war-plugin
2.0
myWeb.xml
[INFO] Error assembling WAR: Deployment descriptor: C:\[...]\WEB-INF\web.xml
does not exist.
The plugin asks for web.xml, although I have configured myWeb.xml.
> WAR plugin does not honor the webXml configuration setting [patch included!]
>
>
> Key: MWAR-52
> URL: http://jira.codehaus.org/browse/MWAR-52
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Andreas Schildbach
> Assignee: Brett Porter
> Attachments: patch.txt
>
> Original Estimate: 15 minutes
>Time Spent: 30 minutes
> Remaining: 0 minutes
>
> The WAR plugin does not honor the webXml configuration setting. I think this
> comes from web.xml being hardcoded into WarMojo, rather than using the
> default-value mechanism for the MOJO attribute.
> Here is a patch:
> Index:
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> ===
> ---
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> (revision 416739)
> +++
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> (working copy)
> @@ -102,7 +102,7 @@
> /**
> * The path to the web.xml file to use.
> *
> - * @parameter expression="${maven.war.webxml}"
> + * @parameter expression="${maven.war.webxml}"
> default-value="WEB-INF/web.xml"
> */
> private File webXml;
>
> Index:
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> ===
> ---
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> (revision 416739)
> +++
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> (working copy)
> @@ -177,7 +177,7 @@
>
> warArchiver.addDirectory( getWebappDirectory() );
>
> -warArchiver.setWebxml( new File( getWebappDirectory(),
> "WEB-INF/web.xml" ) );
> +warArchiver.setWebxml( getWebXml() );
>
> // create archive
> archiver.createArchive( getProject(), archive );
--
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: (MWAR-41) War plugin doesn't honour system or project properties when filtering resource files.
[ http://jira.codehaus.org/browse/MWAR-41?page=all ]
Brett Porter updated MWAR-41:
-
Assign To: Brett Porter
Remaining Estimate: 30 minutes
Original Estimate: 30 minutes
> War plugin doesn't honour system or project properties when filtering
> resource files.
> -
>
> Key: MWAR-41
> URL: http://jira.codehaus.org/browse/MWAR-41
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0.1
> Environment: osx 10.4.6, java 1.4.2_06
> Reporter: Julian Wood
> Assignee: Brett Porter
> Fix For: 2.0.1
> Attachments: my-webapp.zip
>
> Original Estimate: 30 minutes
> Remaining: 30 minutes
>
> The war plugin only honours properties specified in a properties file,
> identified in a build/filters/filter element.
> To be consistent with regular resource filtering, it should honour properties
> specified on the CL, in a profile, in a plugin, or in the pom (eg.,
> ${project.version} ). None of these currently work.
> To demonstrate:
> mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes
> -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeVersion=1.0-alpha-4
> -DgroupId=ca.ucalgary.tlc -DartifactId=my-webapp
> And then add this to the pom.xml:
>
>
>
> maven-war-plugin
>
>
>
> true
> ${basedir}/src/main/webapp
>
> **/*.xml
>
>
>
>
>
>
>
> And finally change the web.xml produced by the archetype so there is
> something to filter:
>
> ${project.name}
>
> Now 'mvn package' and note that target/my-webapp-1.0-SNAPSHOT/WEB-INF/web.xml
> is *not* filtered.
> If you add:
>
> src/main/filters/build.dev.properties
>
> to the build element, and add the build.dev.properties, and specify the
> project.name property, you do get successful filtering.
--
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: (MWAR-41) War plugin doesn't honour system or project properties when filtering resource files.
[ http://jira.codehaus.org/browse/MWAR-41?page=all ]
Brett Porter closed MWAR-41:
Resolution: Fixed
> War plugin doesn't honour system or project properties when filtering
> resource files.
> -
>
> Key: MWAR-41
> URL: http://jira.codehaus.org/browse/MWAR-41
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0.1
> Environment: osx 10.4.6, java 1.4.2_06
> Reporter: Julian Wood
> Assignee: Brett Porter
> Fix For: 2.0.1
> Attachments: my-webapp.zip
>
> Original Estimate: 30 minutes
>Time Spent: 45 minutes
> Remaining: 0 minutes
>
> The war plugin only honours properties specified in a properties file,
> identified in a build/filters/filter element.
> To be consistent with regular resource filtering, it should honour properties
> specified on the CL, in a profile, in a plugin, or in the pom (eg.,
> ${project.version} ). None of these currently work.
> To demonstrate:
> mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes
> -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeVersion=1.0-alpha-4
> -DgroupId=ca.ucalgary.tlc -DartifactId=my-webapp
> And then add this to the pom.xml:
>
>
>
> maven-war-plugin
>
>
>
> true
> ${basedir}/src/main/webapp
>
> **/*.xml
>
>
>
>
>
>
>
> And finally change the web.xml produced by the archetype so there is
> something to filter:
>
> ${project.name}
>
> Now 'mvn package' and note that target/my-webapp-1.0-SNAPSHOT/WEB-INF/web.xml
> is *not* filtered.
> If you add:
>
> src/main/filters/build.dev.properties
>
> to the build element, and add the build.dev.properties, and specify the
> project.name property, you do get successful filtering.
--
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: (MWAR-43) Web resource filtering does not expand variables
[ http://jira.codehaus.org/browse/MWAR-43?page=all ]
Brett Porter closed MWAR-43:
Assign To: Brett Porter
Resolution: Duplicate
Fix Version: (was: 2.0.1)
> Web resource filtering does not expand variables
>
>
> Key: MWAR-43
> URL: http://jira.codehaus.org/browse/MWAR-43
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Environment: Windows XP, Cygwin
> Reporter: Mark Hobson
> Assignee: Brett Porter
> Attachments: test.zip
>
>
> Variables contained within filter values are not expanded for web resource
> filtering as they are for normal resource filtering.
> mvn package attached project:
> Expected:
> * target/WEB-INF/classes/resource.txt == Test
> * target/web-resource.txt == Test
> Actual:
> * target/WEB-INF/classes/resource.txt == Test
> * target/web-resource.txt == ${project.name}
--
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: (MWAR-52) WAR plugin does not honor the webXml configuration setting [patch included!]
[ http://jira.codehaus.org/browse/MWAR-52?page=all ]
Brett Porter updated MWAR-52:
-
Attachment: my-webapp.zip
> WAR plugin does not honor the webXml configuration setting [patch included!]
>
>
> Key: MWAR-52
> URL: http://jira.codehaus.org/browse/MWAR-52
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Andreas Schildbach
> Assignee: Brett Porter
> Attachments: my-webapp.zip, patch.txt
>
> Original Estimate: 15 minutes
>Time Spent: 30 minutes
> Remaining: 0 minutes
>
> The WAR plugin does not honor the webXml configuration setting. I think this
> comes from web.xml being hardcoded into WarMojo, rather than using the
> default-value mechanism for the MOJO attribute.
> Here is a patch:
> Index:
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> ===
> ---
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> (revision 416739)
> +++
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> (working copy)
> @@ -102,7 +102,7 @@
> /**
> * The path to the web.xml file to use.
> *
> - * @parameter expression="${maven.war.webxml}"
> + * @parameter expression="${maven.war.webxml}"
> default-value="WEB-INF/web.xml"
> */
> private File webXml;
>
> Index:
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> ===
> ---
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> (revision 416739)
> +++
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> (working copy)
> @@ -177,7 +177,7 @@
>
> warArchiver.addDirectory( getWebappDirectory() );
>
> -warArchiver.setWebxml( new File( getWebappDirectory(),
> "WEB-INF/web.xml" ) );
> +warArchiver.setWebxml( getWebXml() );
>
> // create archive
> archiver.createArchive( getProject(), archive );
--
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: (MWAR-48) review plugin documentation
[ http://jira.codehaus.org/browse/MWAR-48?page=comments#action_68310 ] Brett Porter commented on MWAR-48: -- please ensure webResources are documented, too > review plugin documentation > --- > > Key: MWAR-48 > URL: http://jira.codehaus.org/browse/MWAR-48 > Project: Maven 2.x War Plugin > Type: Task > Versions: 2.0 > Reporter: Marvin King > Assignee: Marvin King > > Time Spent: 15 hours >Remaining: 0 minutes > -- 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: (MDEP-25) Option to copy artifact also, along with its deps on (copy/unpack)-dependencies goals
[ http://jira.codehaus.org/browse/MDEP-25?page=all ] Anagnostopoulos Kostis closed MDEP-25: -- Resolution: Won't Fix Thank you Dan, i should have known this right from the start. I'm closing this issue, but it may be a good idea to add a small reference to plugin documentation about this discouraged usage and that they should use the assembly plugin instead. Kostis > Option to copy artifact also, along with its deps on > (copy/unpack)-dependencies goals > - > > Key: MDEP-25 > URL: http://jira.codehaus.org/browse/MDEP-25 > Project: Maven 2.x Dependency Plugin > Type: New Feature > Versions: 1.1 > Reporter: Anagnostopoulos Kostis > Priority: Minor > > > Hi, > This worthy plugin can be extended to provide the ability to copy the > artifact along with its dependencies by default. That way, when it is used > to build a dir with all required jars to run an application, it won't be > necessary to use both goals, copy (for the artifact) and copy-dependencies > (for its libs). > I also want to ask the developers if they would preffer me to contribute a > patch for this new boolean param, named "copyArtifact"? > anKostis a gmail.com -- 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: (MNG-2408) Following "How do I make my first Maven project?" doesn't work
Following "How do I make my first Maven project?" doesn't work -- Key: MNG-2408 URL: http://jira.codehaus.org/browse/MNG-2408 Project: Maven 2 Type: Bug Components: Documentation: Guides Versions: 2.0.4 Reporter: Graham Leggett If you follow the instructions at http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20make%20my%20first%20Maven%20project? to use the archetype plugin to create a new project skeleton, the suggested command line fails as below. It seems there is a typo of some kind in the suggested command line, I am not familiar enough with maven 2 to know for sure. Graham-Leggetts-Computer:~/src/standard/alchemy/maven minfrin$ mvn archetype:create -DgroupId=za.co.standardbank.alchemy -DartifactId=alchemy-trader [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jun 27 09:43:14 SAST 2006 [INFO] Final Memory: 1M/2M [INFO] -- 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: (MNG-2408) Following "How do I make my first Maven project?" doesn't work
[ http://jira.codehaus.org/browse/MNG-2408?page=all ] Brett Porter closed MNG-2408: - Assign To: Brett Porter Resolution: Won't Fix http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-novalidversion It's a configuration error on your end. > Following "How do I make my first Maven project?" doesn't work > -- > > Key: MNG-2408 > URL: http://jira.codehaus.org/browse/MNG-2408 > Project: Maven 2 > Type: Bug > Components: Documentation: Guides > Versions: 2.0.4 > Reporter: Graham Leggett > Assignee: Brett Porter > > > If you follow the instructions at > http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20make%20my%20first%20Maven%20project? > to use the archetype plugin to create a new project skeleton, the suggested > command line fails as below. > It seems there is a typo of some kind in the suggested command line, I am not > familiar enough with maven 2 to know for sure. > Graham-Leggetts-Computer:~/src/standard/alchemy/maven minfrin$ mvn > archetype:create -DgroupId=za.co.standardbank.alchemy > -DartifactId=alchemy-trader > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jun 27 09:43:14 SAST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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-709) Runtime error during recording in datanase
[ http://jira.codehaus.org/browse/CONTINUUM-709?page=comments#action_68316 ] Heikki Rauhala commented on CONTINUUM-709: -- This bug affects continuum-1.0.3 on Linux. The bug appeared when only sources were modified, and Continuum continued to work normally after a restart. Without restart no projects were getting built. > Runtime error during recording in datanase > -- > > Key: CONTINUUM-709 > URL: http://jira.codehaus.org/browse/CONTINUUM-709 > Project: Continuum > Type: Bug > Components: Core system > Environment: solaris 9 > Reporter: Olivier Lamy > > > I have the following strack trace : > ERROR 22001: A truncation error was encountered trying to shrink VARCHAR > '/OTAReceiver/trunk/ota-rec > eiver-parsing/src/main/java/com/ac&' to length 255. > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown > Source) > at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown > Source) > at > org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown > Source) > at > org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown > Source) > at > org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown > Source) > at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown > Source) > at org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > at org.jpox.store.StoreManager.insert(StoreManager.java:739) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) > at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) > at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.jav > a:1146) > at > org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1201) > at > org.codehaus.plexus.jdo.PlexusJdoUtils.makePersistent(PlexusJdoUtils.java:97) > at > org.apache.maven.continuum.store.JdoContinuumStore.makePersistent(JdoContinuumStore.java: > 524) > at > org.apache.maven.continuum.store.JdoContinuumStore.addBuildResult(JdoContinuumStore.java: > 265) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.makeAndStoreBuildResult > (DefaultBuildController.java:443) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildContr > oller.java:298) > The result is strange : > - in the build history the build is marked as succesfull > - in the project summary I have the red icon which says failed but no mail > received > -- > Olivier -- 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] Reopened: (MNG-2408) Following "How do I make my first Maven project?" doesn't work
[ http://jira.codehaus.org/browse/MNG-2408?page=all ] Graham Leggett reopened MNG-2408: - How on earth is this a configuration issue? The maven install is brand new, there is no configuration at all. The new user _does not_ have a priori knowledge that they have to run maven with the -U switch. Why would they? Maven has always updated itself automatically, why should it stop now? Do a Google search for the above error, and you get person after person asking the same question over and over again. All it takes is a single extra line of documentation indicating to the user that the -U switch may be required on new installations. Please take feedback from new users seriously. I know it is difficult from the point of view of a developer to see maven as the new user sees it. When a new user points out something isn't clear, then change it so it is. Maven is supposed to make the developer's life easier, not harder. > Following "How do I make my first Maven project?" doesn't work > -- > > Key: MNG-2408 > URL: http://jira.codehaus.org/browse/MNG-2408 > Project: Maven 2 > Type: Bug > Components: Documentation: Guides > Versions: 2.0.4 > Reporter: Graham Leggett > Assignee: Brett Porter > > > If you follow the instructions at > http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20make%20my%20first%20Maven%20project? > to use the archetype plugin to create a new project skeleton, the suggested > command line fails as below. > It seems there is a typo of some kind in the suggested command line, I am not > familiar enough with maven 2 to know for sure. > Graham-Leggetts-Computer:~/src/standard/alchemy/maven minfrin$ mvn > archetype:create -DgroupId=za.co.standardbank.alchemy > -DartifactId=alchemy-trader > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jun 27 09:43:14 SAST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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-2408) Following "How do I make my first Maven project?" doesn't work
[ http://jira.codehaus.org/browse/MNG-2408?page=comments#action_68318 ] Brett Porter commented on MNG-2408: --- ok, usually it's a configuration error (you have a proxy that isn't configured). Since it's not the case, it must have been an intermittent issue with ibiblio, which caused a metadata error. This is a known issue (probably filed elsewhere). I'll assign this to 2.0.5 for now, but we should try and find the original issue. > Following "How do I make my first Maven project?" doesn't work > -- > > Key: MNG-2408 > URL: http://jira.codehaus.org/browse/MNG-2408 > Project: Maven 2 > Type: Bug > Components: Documentation: Guides > Versions: 2.0.4 > Reporter: Graham Leggett > Assignee: Brett Porter > > > If you follow the instructions at > http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20make%20my%20first%20Maven%20project? > to use the archetype plugin to create a new project skeleton, the suggested > command line fails as below. > It seems there is a typo of some kind in the suggested command line, I am not > familiar enough with maven 2 to know for sure. > Graham-Leggetts-Computer:~/src/standard/alchemy/maven minfrin$ mvn > archetype:create -DgroupId=za.co.standardbank.alchemy > -DartifactId=alchemy-trader > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jun 27 09:43:14 SAST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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-2408) Improve handling of "no plugin version found" error after intermittent errors
[ http://jira.codehaus.org/browse/MNG-2408?page=all ] Brett Porter updated MNG-2408: -- Assign To: (was: Brett Porter) Fix Version: 2.0.5 Component: Artifacts and Repositories Artifacts Summary: Improve handling of "no plugin version found" error after intermittent errors (was: Following "How do I make my first Maven project?" doesn't work) > Improve handling of "no plugin version found" error after intermittent errors > - > > Key: MNG-2408 > URL: http://jira.codehaus.org/browse/MNG-2408 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories, Artifacts, Documentation: Guides > Versions: 2.0.4 > Reporter: Graham Leggett > Fix For: 2.0.5 > > > If you follow the instructions at > http://maven.apache.org/guides/getting-started/index.html#How%20do%20I%20make%20my%20first%20Maven%20project? > to use the archetype plugin to create a new project skeleton, the suggested > command line fails as below. > It seems there is a typo of some kind in the suggested command line, I am not > familiar enough with maven 2 to know for sure. > Graham-Leggetts-Computer:~/src/standard/alchemy/maven minfrin$ mvn > archetype:create -DgroupId=za.co.standardbank.alchemy > -DartifactId=alchemy-trader > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not > exist or no valid version could be found > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Tue Jun 27 09:43:14 SAST 2006 > [INFO] Final Memory: 1M/2M > [INFO] > -- 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: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml
[ http://jira.codehaus.org/browse/MRESOURCES-20?page=comments#action_68320
]
Vincent Cornet commented on MRESOURCES-20:
--
This issue occurs with unresolved variables ending not only in ".file", but
also in ".version", ".url", or any other available property of "$pom".
> Filtering ${foo.file} evaluates to in full path to pom.xml
> --
>
> Key: MRESOURCES-20
> URL: http://jira.codehaus.org/browse/MRESOURCES-20
> Project: Maven 2.x Resources Plugin
> Type: Bug
> Versions: 2.2
> Environment: Windows XP, Maven 2.0.2
> Reporter: Martin Onis
> Priority: Minor
>
>
> If an unresolved variable is encountered, the plugin simply does not replace
> the variable in the target file.
> If this unresolved variable however ends in ".file}" it will evaluate to a
> file object that targets the current pom. This results in the replacement
> being the complete path to that pom (in the 2.1 version of the plugin this
> results in a ClassCastException).
> The workaround is, of course, not to filter the affected files.
> Though this will not work if other variables in the affected files do need to
> be replaced.
--
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: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml
[ http://jira.codehaus.org/browse/MRESOURCES-20?page=comments#action_68322
]
Eric Bottard commented on MRESOURCES-20:
I would suggest raising the priority of this bug as it can have very nasty side
effects, for example when using velocity templates.
It would also be nice to have the possibility to
1- Use other delimiters for properties (ie not only @@ or ${})
2- De-activate the ${} delimiters
> Filtering ${foo.file} evaluates to in full path to pom.xml
> --
>
> Key: MRESOURCES-20
> URL: http://jira.codehaus.org/browse/MRESOURCES-20
> Project: Maven 2.x Resources Plugin
> Type: Bug
> Versions: 2.2
> Environment: Windows XP, Maven 2.0.2
> Reporter: Martin Onis
> Priority: Minor
>
>
> If an unresolved variable is encountered, the plugin simply does not replace
> the variable in the target file.
> If this unresolved variable however ends in ".file}" it will evaluate to a
> file object that targets the current pom. This results in the replacement
> being the complete path to that pom (in the 2.1 version of the plugin this
> results in a ClassCastException).
> The workaround is, of course, not to filter the affected files.
> Though this will not work if other variables in the affected files do need to
> be replaced.
--
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: (MWAR-52) WAR plugin does not honor the webXml configuration setting [patch included!]
[ http://jira.codehaus.org/browse/MWAR-52?page=comments#action_68324 ]
Andreas Schildbach commented on MWAR-52:
Your testcase works in my environment, too.
However, just delete myWeb.xml and watch the plugin cry for the wrong file.
> WAR plugin does not honor the webXml configuration setting [patch included!]
>
>
> Key: MWAR-52
> URL: http://jira.codehaus.org/browse/MWAR-52
> Project: Maven 2.x War Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Andreas Schildbach
> Assignee: Brett Porter
> Attachments: my-webapp.zip, patch.txt
>
> Original Estimate: 15 minutes
>Time Spent: 30 minutes
> Remaining: 0 minutes
>
> The WAR plugin does not honor the webXml configuration setting. I think this
> comes from web.xml being hardcoded into WarMojo, rather than using the
> default-value mechanism for the MOJO attribute.
> Here is a patch:
> Index:
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> ===
> ---
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> (revision 416739)
> +++
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/AbstractWarMojo.java
> (working copy)
> @@ -102,7 +102,7 @@
> /**
> * The path to the web.xml file to use.
> *
> - * @parameter expression="${maven.war.webxml}"
> + * @parameter expression="${maven.war.webxml}"
> default-value="WEB-INF/web.xml"
> */
> private File webXml;
>
> Index:
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> ===
> ---
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> (revision 416739)
> +++
> C:/cc/sd_area51_3/OcToPuS/tools/maven/plugins/maven-war-plugin/src/main/java/org/apache/maven/plugin/war/WarMojo.java
> (working copy)
> @@ -177,7 +177,7 @@
>
> warArchiver.addDirectory( getWebappDirectory() );
>
> -warArchiver.setWebxml( new File( getWebappDirectory(),
> "WEB-INF/web.xml" ) );
> +warArchiver.setWebxml( getWebXml() );
>
> // create archive
> archiver.createArchive( getProject(), archive );
--
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] Erstellt: (CONTINUUM-737) Database log contains continuum user passwords in clear text
Database log contains continuum user passwords in clear text Key: CONTINUUM-737 URL: http://jira.codehaus.org/browse/CONTINUUM-737 Project: Continuum Type: Bug Components: Core system Versions: 1.0.3 Reporter: Bernhard Wellhöfer Priority: Minor Hello, The database log contains the continuum user passwords in clear text. This is kind of a security issue. Regards, Bernd -- 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-542) Reimplement authentication management
[ http://jira.codehaus.org/browse/CONTINUUM-542?page=all ] Emmanuel Venisse updated CONTINUUM-542: --- Summary: Reimplement authentication management (was: Use OS User for authentication management) > Reimplement authentication management > - > > Key: CONTINUUM-542 > URL: http://jira.codehaus.org/browse/CONTINUUM-542 > Project: Continuum > Type: Improvement > Reporter: Emmanuel Venisse > Fix For: 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] Closed: (CONTINUUM-725) CLONE -Cannot reference POM via http link with authentication
[ http://jira.codehaus.org/browse/CONTINUUM-725?page=all ] Emmanuel Venisse closed CONTINUUM-725: -- Resolution: Cannot Reproduce Fix Version: (was: 1.0.3) 1.1 > CLONE -Cannot reference POM via http link with authentication > - > > Key: CONTINUUM-725 > URL: http://jira.codehaus.org/browse/CONTINUUM-725 > Project: Continuum > Type: Bug > Reporter: Scott McLachlan > Assignee: Emmanuel Venisse > Fix For: 1.1 > > > Continuum is not able to download a POM from a URL like http://user:[EMAIL > PROTECTED]/trunk/pom.xml. I've seen a number of bugs posted relating to this > issue, but they've been closed almost 6 months ago. Has this feature been > left out of the 1.0.2 release? -- 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-115) Start designing visual representations of historical build information
[ http://jira.codehaus.org/browse/CONTINUUM-115?page=all ] Emmanuel Venisse updated CONTINUUM-115: --- Fix Version: (was: 1.1) > Start designing visual representations of historical build information > -- > > Key: CONTINUUM-115 > URL: http://jira.codehaus.org/browse/CONTINUUM-115 > Project: Continuum > Type: Task > Versions: 1.0.1 > Reporter: Jason van Zyl > > > Start looking at ways to represent historical build information. Tufte is > always a good resource in this regard. > http://www.tufte.com -- 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-37) Add a professional user interface
[ http://jira.codehaus.org/browse/CONTINUUM-37?page=all ] Emmanuel Venisse updated CONTINUUM-37: -- Fix Version: (was: 1.1) We'll look at ajax features > Add a professional user interface > - > > Key: CONTINUUM-37 > URL: http://jira.codehaus.org/browse/CONTINUUM-37 > Project: Continuum > Type: New Feature > Components: Web interface > Reporter: Emmanuel Venisse > > > I'd like to see a professional interface with some flash components like a > Macromedia Flex interface. > Laszlo provides an open source implementation of this technology (CPL > License). http://www.laszlosystems.com/ > You can see some demo here (http://www.laszlosystems.com/demos/). > The screen creation is very simple, it a very simple xml. > I'll hope you'll be interesting. -- 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-265) Concurrent builds
[ http://jira.codehaus.org/browse/CONTINUUM-265?page=all ] Emmanuel Venisse updated CONTINUUM-265: --- Fix Version: (was: 1.1) > Concurrent builds > - > > Key: CONTINUUM-265 > URL: http://jira.codehaus.org/browse/CONTINUUM-265 > Project: Continuum > Type: New Feature > Components: Core system > Reporter: Torsten Curdt > > > Instead of processing the builds sequentially it would be great to be > able to specify how many projects are being build concurrently. -- 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-140) Allow the use of the CC in the web UI
[ http://jira.codehaus.org/browse/CONTINUUM-140?page=all ] Emmanuel Venisse updated CONTINUUM-140: --- Fix Version: (was: 1.1) > Allow the use of the CC in the web UI > - > > Key: CONTINUUM-140 > URL: http://jira.codehaus.org/browse/CONTINUUM-140 > Project: Continuum > Type: New Feature > Versions: 1.0-alpha-4 > Reporter: Jason van Zyl > > > This will require some changes in the UI to make this work but we can assess > in alpha-3 -- 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-34) Keep trying till build works, notify via email what is required
[ http://jira.codehaus.org/browse/CONTINUUM-34?page=all ] Emmanuel Venisse updated CONTINUUM-34: -- Fix Version: (was: 1.1) > Keep trying till build works, notify via email what is required > --- > > Key: CONTINUUM-34 > URL: http://jira.codehaus.org/browse/CONTINUUM-34 > Project: Continuum > Type: Wish > Reporter: David Blevins > Priority: Minor > > > I don't know if this is relevant to continuum's style of building, but > I have a script that scm updates then builds an m1 project with the default, > i.e. using just 'maven' with no goals supplied. This works the majority of > time, but every once in a while someone refactors something and i need to do > a clean build to really get everything to build. > The idea: > Have the concept of escalating the depth of the build till it works (or until > you've tried everything). If you find one that works send an email that > lists the exact steps (or maven command) required to get your build to work > again. > Example scenario 1: > $ cvs update -dP > $ maven > > BUILD FAILED > > $ maven clean default > > BUILD SUCCESSFUL > (email sent suggesting people do a 'maven clean default' after updating) > Example scenario 2: > $ cvs update -dP > $ maven > > BUILD FAILED > > $ maven clean default > > BUILD FAILED > $ cvs co alanparsons > $ cd alanparsons > $ maven > > BUILD SUCCESSFUL > (email sent suggesting people get a clean checkout of the alanparsons project > before attempting to build) -- 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-511) Continuum should use Server VM
[ http://jira.codehaus.org/browse/CONTINUUM-511?page=all ] Emmanuel Venisse updated CONTINUUM-511: --- Fix Version: (was: 1.1) > Continuum should use Server VM > -- > > Key: CONTINUUM-511 > URL: http://jira.codehaus.org/browse/CONTINUUM-511 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.2 > Reporter: Matthew Beermann > Priority: Minor > Attachments: patch.txt > > > Continuum could (should?) use the Server VM rather than the default Client VM > when running as a service. I'm not fully versed in all the differences > between them, but from what I do know, it seems much more appropriate. > This would involve adding another "wrapper.java.additional" parameter to > bin/win32/wrapper.conf (-server). -- 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-667) need a way to limit the mount of time a unit test runs for
[ http://jira.codehaus.org/browse/CONTINUUM-667?page=all ] Emmanuel Venisse updated CONTINUUM-667: --- Fix Version: 1.1 > need a way to limit the mount of time a unit test runs for > -- > > Key: CONTINUUM-667 > URL: http://jira.codehaus.org/browse/CONTINUUM-667 > Project: Continuum > Type: Bug > Components: Web interface, Core system > Versions: 1.0.3 > Reporter: james strachan > Priority: Blocker > Fix For: 1.1 > > > We get lots of builds hanging in CI due to test cases with timing issues on > different platforms. (You'd be amazed how easy that is to do). We need a way > to put in a maximum amount of time (say 5 minutes) for a single unit test - > or a max time per entire test run (say 1 hour) so that we can be alerted if a > test hangs. > If a test hangs it normally hoses the entire CI server. The worst thing is > this makes the entire CI useless since it does no more builds and we don't > know its failed. > I understand there are complications in killing stuff in Java. (Though > java.lang.Process.destroy() works for most things). One option is to just > have a status XML file we can poll for on a canoncial URL > http;//serverhost/module/status.xml > then we can look to see if any of the builds are blocked and if they are we > can get nagios or something to reboot the box / restart the CI server etc. -- 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-736) "Edit User" page resets password to the empty password - admin user no longer useable
[ http://jira.codehaus.org/browse/CONTINUUM-736?page=all ] Emmanuel Venisse updated CONTINUUM-736: --- Fix Version: 1.1 > "Edit User" page resets password to the empty password - admin user no longer > useable > - > > Key: CONTINUUM-736 > URL: http://jira.codehaus.org/browse/CONTINUUM-736 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.3 > Reporter: Bernhard Wellhöfer > Priority: Blocker > Fix For: 1.1 > > > Hello, > > I changed in the user management section the real name for the continuum > admin user. The form where I added the real name also presented the password > field. Here the password field was empty - nevertheless the admin user had a > password. After entering the new real name for admin and after hitting > "submit" the real named changed - but the password also changed. I did not > enter anything in the password text field ... > It seems that the new password is now blank. This is a serious issue, since > the login page does not allow an empty password. So how do I reset the admin > password to a known value? > Moreover I need a solution how to repair my continuum system. > > Cheers, > > Bernd -- 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-699) Error in displaying of build state icons in main page of gui.
[ http://jira.codehaus.org/browse/CONTINUUM-699?page=all ] Emmanuel Venisse updated CONTINUUM-699: --- Fix Version: 1.1 > Error in displaying of build state icons in main page of gui. > - > > Key: CONTINUUM-699 > URL: http://jira.codehaus.org/browse/CONTINUUM-699 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.3 > Environment: Linux Debian > maven 2.0.4 > Reporter: Wolfgang Klein > Priority: Critical > Fix For: 1.1 > Attachments: icon_problem.png > > > Hello! > First, let me say that i like the 1.0.3 version. > I´ve got a small problem with the state icons > in the web client and have attached a screen > shot showing the problem. > After some time, the "update sources" icons > disappears and it looks like shown in the > screenshot. > I´ve found another icon bug, i hope, this is > a different bug and so no duplicate! > Greetings, > W.K. -- 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-684) Access to Continuum using XML-RPC is not authenticated.
[ http://jira.codehaus.org/browse/CONTINUUM-684?page=all ] Emmanuel Venisse updated CONTINUUM-684: --- Fix Version: 1.1 > Access to Continuum using XML-RPC is not authenticated. > --- > > Key: CONTINUUM-684 > URL: http://jira.codehaus.org/browse/CONTINUUM-684 > Project: Continuum > Type: Bug > Components: XMLRPC Interface > Reporter: Rahul Thakur > Priority: Critical > Fix For: 1.1 > > > Noticed that I could connect to a Continuum instance on my local box and > obtain list of project details without being authenticated. > Can this also be considered as a request to implement a "doLogin( )" service > or similar for Continuum - Thanks. -- 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-691) Build Numbers are obscured by the queuing/building icon
[ http://jira.codehaus.org/browse/CONTINUUM-691?page=all ] Emmanuel Venisse updated CONTINUUM-691: --- Fix Version: 1.1 > Build Numbers are obscured by the queuing/building icon > --- > > Key: CONTINUUM-691 > URL: http://jira.codehaus.org/browse/CONTINUUM-691 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.3 > Reporter: Christian Gruber > Priority: Critical > Fix For: 1.1 > > > In our system, we're building every five minutes or so, and we can't see the > last good build version number when things are queued or building. It would > be very helpful if the last good build could be completely independent of the > build status. -- 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-440) Failed to start continuum on 64bit Linux
[ http://jira.codehaus.org/browse/CONTINUUM-440?page=all ] Emmanuel Venisse updated CONTINUUM-440: --- Fix Version: 1.1 > Failed to start continuum on 64bit Linux > > > Key: CONTINUUM-440 > URL: http://jira.codehaus.org/browse/CONTINUUM-440 > Project: Continuum > Type: Bug > Versions: 1.0 > Environment: OS:Debian Linux x86-64, Proc: amd64-xeon > Reporter: Nic > Priority: Critical > Fix For: 1.1 > > > When starting continuum I get the following error: > # ./run.sh start > Starting continuum... > ./run.sh: line 192: /usr/local/continuum-1.0/bin/linux/wrapper: No such file > or directory > ./run.sh: line 192: /usr/local/continuum-1.0/bin/linux/wrapper: Success > But, there's no such error on a 32bit Linux system. -- 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-723) strange trouble on solaris
[ http://jira.codehaus.org/browse/CONTINUUM-723?page=all ] Emmanuel Venisse updated CONTINUUM-723: --- Fix Version: 1.1 > strange trouble on solaris > --- > > Key: CONTINUUM-723 > URL: http://jira.codehaus.org/browse/CONTINUUM-723 > Project: Continuum > Type: Bug > Versions: 1.0.3 > Environment: solaris > Reporter: Olivier Lamy > Priority: Critical > Fix For: 1.1 > Attachments: CONTINUUM-723.tar.gz > > > Hi, > I have a junit test with contains the following code : > SimpleDateFormat simpleDateFormat = new SimpleDateFormat( "-MM-dd", > Locale.FRANCE ); > // harcoded date due to xmlunit comparaison > Date timeStamp = simpleDateFormat.parse( "2001-05-28" ); > return DateTools.setNoonHour( timeStamp ); > FastDateFormat.getInstance( "-MM-dd'T'HH:mm:ss.SSSZZ" > ).format(date); > On windows+cygwin : 2001-05-28T12:00:00.000+02:00 > On solaris with same user who start continuum exec junit with cli : > 2001-05-28T12:00:00.000+02:00 > The same junit with continuum says : 2001-05-28T12:00:00.000+00:00 > Error says : > Expected attribute value '2001-05-28T12:00:00.000+02:00' but was > '2001-05-28T12:00:00.000+00:00' - comparing at > /OTA_HotelAvailRS[1]/@TimeStamp to at /OTA_HotelAvailRS[1]/@TimeStamp > I start continuum with $CONTINUUM_HOME/bin/plexus.sh > /dev/null & > The .profile contains : > ... > LANG=en_US.ISO8859-15 > export LANG > ##opts maven > MAVEN_OPTS="-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1" > export MAVEN_OPTS > ... > I don't change anything on plexus.sh script. > Any ideas ?? > Thanks, > -- > Olivier -- 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-463) add possibility to retrieve the complete project instance in one chunk
[ http://jira.codehaus.org/browse/CONTINUUM-463?page=all ] Emmanuel Venisse updated CONTINUUM-463: --- Fix Version: 1.1 > add possibility to retrieve the complete project instance in one chunk > -- > > Key: CONTINUUM-463 > URL: http://jira.codehaus.org/browse/CONTINUUM-463 > Project: Continuum > Type: New Feature > Components: XMLRPC Interface > Reporter: Milos Kleint > Fix For: 1.1 > Attachments: CONTINUUM-463.txt, CONTINUUM-463.txt > > > when calling getProjects() one gets only half populated instances Project. > one hs to call getproject(int) on ech of them to get the complete set. > And it seems I never get any data in Project.getBuildResults() 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-137) Store dependency information at the ContinuumProject level
[ http://jira.codehaus.org/browse/CONTINUUM-137?page=all ] Emmanuel Venisse updated CONTINUUM-137: --- Fix Version: 1.1 > Store dependency information at the ContinuumProject level > -- > > Key: CONTINUUM-137 > URL: http://jira.codehaus.org/browse/CONTINUUM-137 > Project: Continuum > Type: New Feature > Versions: 1.0-alpha-3 > Reporter: Jason van Zyl > Fix For: 1.1 > > > In order to be able to build in any deterministic order we need dependency > information on all the projects entered into the system. -- 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-660) One or more module in a project is added twice during adding maven2 projects
[ http://jira.codehaus.org/browse/CONTINUUM-660?page=all ] Emmanuel Venisse updated CONTINUUM-660: --- Fix Version: 1.1 > One or more module in a project is added twice during adding maven2 projects > > > Key: CONTINUUM-660 > URL: http://jira.codehaus.org/browse/CONTINUUM-660 > Project: Continuum > Type: Bug > Versions: 1.0.3 > Environment: Solaris10 on sparc > Reporter: Kaare Nilsen > Fix For: 1.1 > Attachments: stacktrace_when_delete.txt > > > In the latest rc when adding a project with multiple modules one or more of > the modules are added twice (duplicated). When this happens there is no way > of deleting one of them eighter so basicly you are stuck with one module > which always will have the "new" state and are never built. > I will attach some log showing what happens when I get to work in the morning -- 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-583) Show the build queue on the web/xmlrpc interface
[ http://jira.codehaus.org/browse/CONTINUUM-583?page=all ] Emmanuel Venisse updated CONTINUUM-583: --- Fix Version: 1.1 > Show the build queue on the web/xmlrpc interface > > > Key: CONTINUUM-583 > URL: http://jira.codehaus.org/browse/CONTINUUM-583 > Project: Continuum > Type: New Feature > Components: XMLRPC Interface, Web interface > Reporter: Henri Yandell > Fix For: 1.1 > > > It would be very nice to be able to see the build queue on the web interface. > The current interface shows whether things are in progress, or in queue; but > not what the order is. -- 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-666) Added (Jabber) Notifiers didn't persist
[ http://jira.codehaus.org/browse/CONTINUUM-666?page=all ] Emmanuel Venisse updated CONTINUUM-666: --- Fix Version: 1.1 > Added (Jabber) Notifiers didn't persist > --- > > Key: CONTINUUM-666 > URL: http://jira.codehaus.org/browse/CONTINUUM-666 > Project: Continuum > Type: Bug > Components: Jabber Notifier, Core system > Versions: 1.0.3 > Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) > Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca142ifx-20051115 (SR3 + > 94164 + 97403 + 97482) (JIT enabled: jitc)) > Reporter: ariva > Fix For: 1.1 > > > After imported a maven1 project and added a jabber notifier (by web > interface) it seems that when a new build starts, the notifier is vanished. > I have looked into derby db but it seems that there is no data in > project_notifiers table. -- 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-465) Lot's of unexpected input errors
[ http://jira.codehaus.org/browse/CONTINUUM-465?page=all ] Emmanuel Venisse updated CONTINUUM-465: --- Fix Version: 1.1 > Lot's of unexpected input errors > > > Key: CONTINUUM-465 > URL: http://jira.codehaus.org/browse/CONTINUUM-465 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.1 > Environment: Linux Fedora Core 4 > SVN with SSPI authentication > SVN repository has external links > Reporter: Tom Skinner > Fix For: 1.1 > > > Getting a bunch of these errors in my wrapper.log during builds. > INFO | jvm 2| 2005/11/21 14:29:58 | 2005-11-21 14:29:58,841 [Thread-1] > INFO ScmManager - Working directory: > /local/ci/continuum-1.0.1/apps/continuum/working-directory/6 > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,108 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,109 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,109 > [Thread-212] DEBUG ScmManager - Fetching external item > into 'hpsps-inside/src/main/java' > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,110 > [Thread-212] INFO ScmManager - Unknown file status: 'F'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,110 > [Thread-212] DEBUG ScmManager - External at revision 2150. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,279 > [Thread-212] INFO ScmManager - Unknown file status: 'E'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,279 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - Fetching external item > into 'hpsps-inside/src/main/webapp' > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] INFO ScmManager - Unknown file status: 'F'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - External at revision 2150. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] INFO ScmManager - Unknown file status: 'E'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - Fetching external item > into 'hpsps-outside/src/main/java' > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] INFO ScmManager - Unknown file status: 'F'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,280 > [Thread-212] DEBUG ScmManager - External at revision 2150. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] INFO ScmManager - Unknown file status: 'E'. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be at least three characters long. Line: ''. > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] DEBUG ScmManager - > INFO | jvm 2| 2005/11/21 14:30:10 | 2005-11-21 14:30:10,281 > [Thread-212] WARN ScmManager - Unexpected input, the > line must be
[jira] Updated: (CONTINUUM-582) Error in detecting chagnes
[ http://jira.codehaus.org/browse/CONTINUUM-582?page=all ] Emmanuel Venisse updated CONTINUUM-582: --- Fix Version: 1.1 > Error in detecting chagnes > -- > > Key: CONTINUUM-582 > URL: http://jira.codehaus.org/browse/CONTINUUM-582 > Project: Continuum > Type: Bug > Reporter: Adam Altemus > Fix For: 1.1 > > > When Continuum does a new build, the comments for the changes on the build > result page are are inconsistent with the actual cvs changes. The comments > on the latest build (build number 25 for the module) are from cvs version > 1.25 when they should be coming from the latest, which is version 1.34. -- 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-703) Display of last build date on Project Summary page
[ http://jira.codehaus.org/browse/CONTINUUM-703?page=all ] Emmanuel Venisse updated CONTINUUM-703: --- Fix Version: 1.1 > Display of last build date on Project Summary page > -- > > Key: CONTINUUM-703 > URL: http://jira.codehaus.org/browse/CONTINUUM-703 > Project: Continuum > Type: Improvement > Components: Web interface > Reporter: Paul Spencer > Fix For: 1.1 > > > Adding the date of the last build to the Project Summary pages would be very > useful. At the very least the user can tell how log it has been since a > build was attempted for a project without having to view the builds history. -- 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-704) Make columns on the project summary page sortable.
[ http://jira.codehaus.org/browse/CONTINUUM-704?page=all ] Emmanuel Venisse updated CONTINUUM-704: --- Fix Version: 1.1 > Make columns on the project summary page sortable. > -- > > Key: CONTINUUM-704 > URL: http://jira.codehaus.org/browse/CONTINUUM-704 > Project: Continuum > Type: Improvement > Components: Web interface > Reporter: Paul Spencer > Fix For: 1.1 > > > Making the columns on the Project Summary page sortable would be very > useful. As an example you could sort by build status, which is the first > column of icons, to see all of the failed builds group together. I added an > issue requesting the addition of build date column. Sorting by this column > will allow the user to see the order projects where build. -- 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-332) Notification message includes the test-report log file of the failed test case.
[ http://jira.codehaus.org/browse/CONTINUUM-332?page=all ] Emmanuel Venisse updated CONTINUUM-332: --- Fix Version: 1.1 > Notification message includes the test-report log file of the failed test > case. > --- > > Key: CONTINUUM-332 > URL: http://jira.codehaus.org/browse/CONTINUUM-332 > Project: Continuum > Type: New Feature > Versions: 1.0-beta-1 > Reporter: Fritz Oconer > Fix For: 1.1 > > > When a usecase fails and notification is sent, it would be nice if a link to > the test-report log file of the particular failed testcase is included in the > message of the notification. -- 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-464) cannot use a build.xml file in a folder
[ http://jira.codehaus.org/browse/CONTINUUM-464?page=all ]
Emmanuel Venisse updated CONTINUUM-464:
---
Fix Version: 1.1
> cannot use a build.xml file in a folder
> ---
>
> Key: CONTINUUM-464
> URL: http://jira.codehaus.org/browse/CONTINUUM-464
> Project: Continuum
> Type: Bug
> Versions: 1.0.1
> Environment: running on Linux Debian
> Reporter: Adam Kiezun
> Fix For: 1.1
>
>
> In an ANT project, I have a build.xml file in a subfolder ("experiments") of
> the main project folder.
> The webinterface form says I can specify a relative path to that file but
> "experiments/build.xml" does not work.
--
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-459) ANT projects ask for POM and Goals when adding build definition
[ http://jira.codehaus.org/browse/CONTINUUM-459?page=all ] Emmanuel Venisse updated CONTINUUM-459: --- Fix Version: 1.1 > ANT projects ask for POM and Goals when adding build definition > --- > > Key: CONTINUUM-459 > URL: http://jira.codehaus.org/browse/CONTINUUM-459 > Project: Continuum > Type: Bug > Versions: 1.0.1 > Reporter: Tomislav Stojcevich > Fix For: 1.1 > > > After adding and ANT project it asks for POM and Goals when adding a build > definition. > This makes it impossible to setup an ant build file to run (at least I can't > figure out another way to make an ANT project run). -- 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-617) javax.jdo.JDODataStoreException: Insert request failed
[ http://jira.codehaus.org/browse/CONTINUUM-617?page=all ]
Emmanuel Venisse updated CONTINUUM-617:
---
Fix Version: 1.1
> javax.jdo.JDODataStoreException: Insert request failed
> --
>
> Key: CONTINUUM-617
> URL: http://jira.codehaus.org/browse/CONTINUUM-617
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0.2
> Reporter: Brian Fox
> Fix For: 1.1
>
>
> This happened apparently randomly during a scheduled build. On the next
> scheduled build, it was successfull.
>
> Build Error:
>
> javax.jdo.JDODataStoreException: Insert request failed: INSERT INTO
> PROJECTDEPENDENCY (PROJECTDEPENDENCY_ID,ARTIFACT_ID,VERSION,GROUP_ID) VALUES
> (?,?,?,?)
>at
> org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:329)
>at
> org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:1774)
>at org.jpox.store.StoreManager.insert(StoreManager.java:721)
>at
> org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3066)
>at
> org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3039)
>at
> org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3452)
>at
> org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644)
>at org.jpox.sco.List.attachCopy(List.java:326)
>at
> org.jpox.state.AttachFieldManager.storeObjectField(AttachFieldManager.java:107)
>at
> org.jpox.state.StateManagerImpl.providedObjectField(StateManagerImpl.java:2394)
>at
> org.apache.maven.continuum.model.project.Project.jdoProvideField(Project.java)
>at
> org.apache.maven.continuum.model.project.Project.jdoProvideFields(Project.java)
>at
> org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:2732)
>at
> org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:3518)
>at
> org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3446)
>at
> org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1644)
>at
> org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1660)
>at
> org.apache.maven.continuum.store.JdoContinuumStore.updateObject(JdoContinuumStore.java:679)
>at
> org.apache.maven.continuum.store.JdoContinuumStore.updateProject(JdoContinuumStore.java:841)
>at
> org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:94)
>at
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:171)
>at
> org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53)
>at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
>at java.lang.Thread.run(Thread.java:534)
> NestedThrowablesStackTrace:
> ERROR 40001: A lock could not be obtained due to a deadlock, cycle of locks
> and waiters is:
> Lock : ROW, PROJECTDEPENDENCY, (1614,14)
> Waiting XID : {31204919, X} , SA, INSERT INTO PROJECTDEPENDENCY
> (PROJECTDEPENDENCY_ID,ARTIFACT_ID,VERSION,GROUP_ID) VALUES (?,?,?,?)
> Granted XID : {31204120, X}
> Lock : ROW, PROJECT, (1,34)
> Waiting XID : {31204120, S} , SA, UPDATE PROJECTDEPENDENCY SET
> DEPENDENCIES_ID_OWN = ?,DEPENDENCIESINTEGER_IDX = ? WHERE
> PROJECTDEPENDENCY_ID = ?
> Granted XID : {31204919, X}
> . The selected victim is XID : 31204919.
>at
> org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
>at
> org.apache.derby.impl.services.locks.Deadlock.buildException(Unknown Source)
>at
> org.apache.derby.impl.services.locks.LockSet.lockObject(Unknown Source)
>at
> org.apache.derby.impl.services.locks.SinglePool.lockAnObject(Unknown Source)
>at
> org.apache.derby.impl.services.locks.SinglePool.lockObject(Unknown Source)
>at
> org.apache.derby.impl.store.raw.xact.RowLocking3.lockRecordForWrite(Unknown
> Source)
>at
> org.apache.derby.impl.store.access.heap.HeapController.lockRow(Unknown Source)
>at
> org.apache.derby.impl.store.access.heap.HeapController.lockRow(Unknown Source)
>at
> org.apache.derby.impl.store.access.btree.index.B2IRowLocking3.lockRowOnPage(Unknown
> Source)
>
[jira] Updated: (CONTINUUM-712) Download as text link in Build result page does not work from URL send in notification mails
[ http://jira.codehaus.org/browse/CONTINUUM-712?page=all ]
Emmanuel Venisse updated CONTINUUM-712:
---
Fix Version: 1.1
> Download as text link in Build result page does not work from URL send in
> notification mails
> -
>
> Key: CONTINUUM-712
> URL: http://jira.codehaus.org/browse/CONTINUUM-712
> Project: Continuum
> Type: Bug
> Components: Web interface
> Versions: 1.0.3
> Reporter: Shinobu Kawai
> Fix For: 1.1
>
>
> When you go to the Build result page from the link sent by the notification
> mail, the URL is something like this:
> http://localhost:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/21/buildId/704
> Since the id and buildId are not in request parameter form, the "Download as
> text" link becomes something like this:
> http://localhost:8080/continuum/servlet/browse?file=$requestUtil.getParameter('id')/${requestUtil.getParameter('buildId')}.log.txt
> Therefore, failing to download.
--
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: (MRELEASE-133) Language settings affect proper check-in for Subversion
Language settings affect proper check-in for Subversion
---
Key: MRELEASE-133
URL: http://jira.codehaus.org/browse/MRELEASE-133
Project: Maven 2.x Release Plugin
Type: Bug
Versions: 2.0-beta-4
Reporter: Joerg Schaible
Priority: Minor
The plugin seems to parse the returned lines of the svn command when checking
in the tagged version:
{noformat}
...
[INFO] Checking in modified POMs...
[INFO] Executing: svn --non-interactive commit --file
c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-5489.commit
C:/Work/standard/master-pom/pom.xml
[INFO] Working directory: C:\Work\standard\master-pom
[INFO] Unknown line: 'Sende pom.xml'
[INFO] Unknown line: 'bertrage Daten .'
[INFO] Unknown line: 'Revision 1140 ?bertragen.'
[INFO] Tagging release with the label v_4...
[INFO] Executing: svn --non-interactive copy --file
c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-2091412033.commit .
http://websvn/svn/essvn/development/buildsystem/maven-2/master-pom/tags/v_4
[INFO] Working directory: C:\Work\standard\master-pom
[INFO] Transforming 'Elsag Master Project'...
[INFO] Removing release POMs...
[INFO] Checking in modified POMs...
[INFO] Executing: svn --non-interactive commit --file
c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-1116553554.commit
C:/Work/standard/master-pom/pom.xml
[INFO] Working directory: C:\Work\standard\master-pom
[INFO] Unknown line: 'Sende pom.xml'
[INFO] Unknown line: 'bertrage Daten .'
[INFO] Unknown line: 'Revision 1142 ?bertragen.'
[INFO] Release preparation complete.
[INFO]
[INFO] BUILD SUCCESSFUL
...
{noformat}
Starting the plugin with
{noformat}
LANG=C mvn release:prepare
{noformat}
does not produce this _Unknown line_ messages. The plugin should invoke the svn
command with an English locale.
--
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-415) cvs update log shows all updates, not just relevant updates
[ http://jira.codehaus.org/browse/CONTINUUM-415?page=all ] Emmanuel Venisse updated CONTINUUM-415: --- Fix Version: 1.1 > cvs update log shows all updates, not just relevant updates > --- > > Key: CONTINUUM-415 > URL: http://jira.codehaus.org/browse/CONTINUUM-415 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0 > Environment: WinXP > Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2115 > (client/server) > Server: Concurrent Versions System (CVSNT) 2.0.34 (client/server) > Reporter: Brian Ewins > Fix For: 1.1 > > > To reproduce, perform a build on a project which uses CVS. Take a look at the > results for the build What I see is the list of files changed in the most > recent update, followed by the author and comment for /every/ commit on those > files /ever/. What I expected to see was (at best) only changes since the > last build, or (at least) only recent changes, say in the last day or two. > I've traced this one down a bit, the cause is quite convoluted; the code > producing the log is making an incorrect assumption about the ScmResults > created on updates. Here's the call sequence that's messing up as far as I > can tell (from browsing svn and correlating with the log messages I see): > DefaultContinuum.buildProject(various) > -..after a couple of steps..-> DefaultContinuumScm.updateProject(project) > -> [ScmResult] result = convertScmResult( > scmManager.getProviderByRepository( repository ).update( > repository, fileSet, tag ) ) > -> [CvsScmProvider].update(repository, fileSet, tag) > -> [AbstractUpdateCommand].execute( repository.getProviderRepository(), > fileSet, parameters ) > -> (ChangeLogScmResult) [AbstractChangeLogCommand].executeCommand( repository, > > fileSet, > > parameters ); > -> [CvsChangeLogCommand].executeCommand(repository, fileSet, null, null, 0, > branch) > This then calls cvs log with no date limiting parameters, so the ScmResult > for the update contains the full log, although it is trimmed to just the > files that changed. > then later on, when asked to produce the build log: > DefaultContinuum.getChangesSinceLastSuccess(projectId, buildId) > -> changes.addAll( buildResult.getScmResult().getChanges() ); > This adds all the changes recorded in that build result, which the previous > trace shows are actually all changes, ever. This set of changes isn't then > filtered by date. > From the looks of 'getChangesSinceLastSuccess' its supposed to provide a list > of all changes from build 'buildId' up to the current one. The assumption in > that method appears to be that each buildResult contains only appropriate > changes. However, since it contains /all/ changes, I'd expect that the > situation is much worse: multiple changes to a file since the last build will > mean we get multiple copies of /all/ changes to that file dumped into the log. > There's some kind of logical disconnect here. I think what's missing is that > the call to 'scmManager.getProviderByRepository( repository ).update( > repository, fileSet, tag ) ' should actually be passing in the timestamp of > the previous build, so that we can retrieve just changes since that build: > that way the assumption in 'getChangesSinceLastSuccess' is correct. - that > the changes from multiple builds can just be appended together. > If I've diagnosed this wrong, then it means that whatever's meant to filter > down the changes to just those since the last build isn't working. I couldn't > find any code that was actually attempting to do that, though. -- 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-721) JDO Deadlock stack whilst removing a POM
[ http://jira.codehaus.org/browse/CONTINUUM-721?page=all ]
Emmanuel Venisse updated CONTINUUM-721:
---
Fix Version: 1.1
> JDO Deadlock stack whilst removing a POM
>
>
> Key: CONTINUUM-721
> URL: http://jira.codehaus.org/browse/CONTINUUM-721
> Project: Continuum
> Type: Bug
> Versions: 1.0.3
> Environment: linux amd64
> Reporter: Andy Brook
> Fix For: 1.1
>
>
> ognl.MethodFailedException: Method "removeProject" failed for object [EMAIL
> PROTECTED] [javax.jdo.JDODataStoreException: Update request failed: UPDATE
> PROJECT SET CHECKOUT_RESULT_SCMRESULT_ID_OID=? WHERE ID=?
> NestedThrowables:
> SQL Exception: A lock could not be obtained due to a deadlock, cycle of locks
> and waiters is:
> Lock : ROW, PROJECT, (3,17)
> Waiting XID : {64696941, X} , SA, UPDATE PROJECT SET
> CHECKOUT_RESULT_SCMRESULT_ID_OID=? WHERE ID=?
> Granted XID : {64696933, X}
> Lock : ROW, BUILDDEFINITION, (3,28)
> Waiting XID : {64696933, X} , SA, INSERT INTO BUILDDEFINITION
> (SCHEDULE_ID_OID,LATEST_BUILD_ID,MODEL_ENCODING,BUILD_FILE,GOALS,DEFAULT_FOR_PROJECT,PROFILE_ID_OID,ARGUMENTS,ID)
> VALUES (?,?,?,?,?,?,?,?,?)
> Granted XID : {64696941, X}
> . The selected victim is XID : 64696941.]
> at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796)
> at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
> at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
> at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
> at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
> at ognl.SimpleNode.getValue(SimpleNode.java:210)
> at ognl.Ognl.getValue(Ognl.java:333)
> at ognl.Ognl.getValue(Ognl.java:378)
> at ognl.Ognl.getValue(Ognl.java:357)
> at
> org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation(DeleteEntity.java:57)
> at
> org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.java:47)
> at
> org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68)
> at
> org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70)
> at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
> at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:615)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
> at
> org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
> at
> org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
> at org.mortbay.http.HttpServer.service(HttpServer.java:879)
> at org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
> at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
> at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
> at
> org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218)
> at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331)
> at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)
> /-- Encapsulated exception \
> javax.jdo.JDODataStoreException: Update request failed: UPDATE PROJECT SET
> CHECKOUT_RESULT_SCMRESULT_ID_OID=? WHERE ID=?
> at
> org.jpox.store.rdbms.request.UpdateRequest.execute(UpdateRequest.java:267)
> at org.jpox.store.rdbms.table.ClassTable.update(ClassTable.java:2200)
> at org.jpox.store.StoreManager.update(StoreManager.java:786)
> at org.jpox.state.StateManagerImpl.flush(StateManagerImpl.java:4596)
> at
> org.jpox.AbstractPersistenceManager.flush(AbstractPersistenceManager.java:3167)
> at
> org.jpox.NonmanagedTransaction.getConnection(NonmanagedTransaction.java:235)
> at
> org.jpox.NonmanagedTransaction.getConnection(NonmanagedTransaction.java:204)
> at
> org.jpox.AbstractPersistenceManager.getConnection(AbstractPersistenceManager.java:370)
> at
> org.jpox.store.rdbms.scostore.InverseListStore.clear(InverseListStore.java:986)
> at
> org.jpox.store.mapping.CollectionMapping.preDelete(CollectionMapping.java:304)
> at
> org.jpox.store.mapping.CollectionMapping.deleteDependent(CollectionMapping.java:332)
> at
> org.jpox.store.rdbms.table.ClassTable.deleteDependent(ClassTable.java:2280)
> at org.jpox.store.StoreManager.deleteDependent(StoreManager.java:838)
> at
> org.jpox.state.StateManagerImpl.deletePersistent(StateManagerImpl.java:4049)
>
[jira] Updated: (CONTINUUM-536) Show the elapsed time in addition to the start and end times.
[ http://jira.codehaus.org/browse/CONTINUUM-536?page=all ] Emmanuel Venisse updated CONTINUUM-536: --- Fix Version: 1.1 > Show the elapsed time in addition to the start and end times. > - > > Key: CONTINUUM-536 > URL: http://jira.codehaus.org/browse/CONTINUUM-536 > Project: Continuum > Type: Improvement > Versions: 1.0, 1.0.1, 1.0.2 > Reporter: Trygve Laugstol > Fix For: 1.1 > > > Affects at least the "project list" and "project" views. -- 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-261) When building Ant and Shell project, still look for pom.xml
[ http://jira.codehaus.org/browse/CONTINUUM-261?page=all ] Emmanuel Venisse updated CONTINUUM-261: --- Fix Version: 1.1 > When building Ant and Shell project, still look for pom.xml > --- > > Key: CONTINUUM-261 > URL: http://jira.codehaus.org/browse/CONTINUUM-261 > Project: Continuum > Type: New Feature > Components: Core system > Reporter: Trygve Laugstol > Fix For: 1.1 > > > This is useful for those who want to make it easy to configure their > Continuum instance. > At least read notifiers, dependencies and developers. -- 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-456) released artifacts don't include javadoc and sources..
[ http://jira.codehaus.org/browse/CONTINUUM-456?page=all ] Emmanuel Venisse updated CONTINUUM-456: --- Fix Version: 1.1 > released artifacts don't include javadoc and sources.. > -- > > Key: CONTINUUM-456 > URL: http://jira.codehaus.org/browse/CONTINUUM-456 > Project: Continuum > Type: Bug > Versions: 1.0.1 > Reporter: Milos Kleint > Fix For: 1.1 > > > the artifacts in remote repositories (eg ibiblio.org) don't have appropriate > javadoc and source jars along side the main artifacts. maven itself does > have it I think and it's supposed to be part of the release plugin.. -- 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-568) Need to be able to schedule forced builds
[ http://jira.codehaus.org/browse/CONTINUUM-568?page=all ] Emmanuel Venisse updated CONTINUUM-568: --- Fix Version: 1.1 > Need to be able to schedule forced builds > - > > Key: CONTINUUM-568 > URL: http://jira.codehaus.org/browse/CONTINUUM-568 > Project: Continuum > Type: Improvement > Reporter: Adam Altemus > Fix For: 1.1 > > > I would like to be able to schedule forced builds so that one of my modules > is constantly updated. -- 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-456) released artifacts don't include javadoc and sources..
[ http://jira.codehaus.org/browse/CONTINUUM-456?page=all ] Emmanuel Venisse closed CONTINUUM-456: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: (was: 1.1) 1.0.2 > released artifacts don't include javadoc and sources.. > -- > > Key: CONTINUUM-456 > URL: http://jira.codehaus.org/browse/CONTINUUM-456 > Project: Continuum > Type: Bug > Versions: 1.0.1 > Reporter: Milos Kleint > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > the artifacts in remote repositories (eg ibiblio.org) don't have appropriate > javadoc and source jars along side the main artifacts. maven itself does > have it I think and it's supposed to be part of the release plugin.. -- 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-501) It should be possible to add a project with sub modules without adding all the sub modules
[ http://jira.codehaus.org/browse/CONTINUUM-501?page=all ] Emmanuel Venisse updated CONTINUUM-501: --- Fix Version: 1.1 > It should be possible to add a project with sub modules without adding all > the sub modules > -- > > Key: CONTINUUM-501 > URL: http://jira.codehaus.org/browse/CONTINUUM-501 > Project: Continuum > Type: Improvement > Reporter: Kaare Nilsen > Fix For: 1.1 > Attachments: continuum-api.diff, continuum-cc.diff, continuum-core.diff, > continuum-web.diff > > > When adding a url to a maven2 pom there sould be a checkbox to indicate if > you would like to import projects recursivly or just the one pom. > e.g. "add sub modules" true/false > In some cases i would see the benifit of adding the top pom, and removing the > --non-recursive flag for doing a full build. > this is somewhat difficult today, when if e.g you have 20 modules you would > add the top pom,. and then you would have to delete all the children manually. -- 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-662) "Show Projects" page shows a "Build Error" icon, but clicking on the "Build" number link, the State is "Build Success".
[ http://jira.codehaus.org/browse/CONTINUUM-662?page=all ] Emmanuel Venisse updated CONTINUUM-662: --- Fix Version: 1.1 > "Show Projects" page shows a "Build Error" icon, but clicking on the "Build" > number link, the State is "Build Success". > --- > > Key: CONTINUUM-662 > URL: http://jira.codehaus.org/browse/CONTINUUM-662 > Project: Continuum > Type: Bug > Reporter: Edwin Punzalan > Fix For: 1.1 > > > This happened with the MPIR project. > But clicking the "Build Now" icon updated both icons to show "Build Success". -- 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-639) Rebuild not triggered when svn repository change consists of a single file deletion
[ http://jira.codehaus.org/browse/CONTINUUM-639?page=all ] Emmanuel Venisse updated CONTINUUM-639: --- Fix Version: 1.1 > Rebuild not triggered when svn repository change consists of a single file > deletion > --- > > Key: CONTINUUM-639 > URL: http://jira.codehaus.org/browse/CONTINUUM-639 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.2 > Environment: Continuum 1.3-SNAPSHOT (RC 1) > Java 5.0 Update 6 > Windows XP SP2 > Subversion 1.3.0 > Reporter: Mark Reynolds > Fix For: 1.1 > > > Here is a continuum log snippet after I deleted a single file from my > subversion repository. > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,342 > [defaultScheduler_Worker-12] INFO SchedulesActivator - > > Executing build job (DEFAULT_SCHEDULE)... > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,342 > [defaultScheduler_Worker-12] INFO ContinuumStore:jdo - nb result > : 3 > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,514 [Thread-1] > INFO ContinuumScm - Updating project: id: '3', name > 'Apreso Content Manager Web App'. > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,545 [Thread-1] > INFO ScmManager - Executing: svn --non-interactive update > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,545 [Thread-1] > INFO ScmManager - Working directory: > C:\continuum\working-directory\3 > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,749 > [defaultScheduler_Worker-12] INFO Continuum - Enqueuing > 'Apreso Content Manager Web App' (Build definition id=3). > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,827 > [defaultScheduler_Worker-3] INFO SchedulesActivator - > > Executing build job (DEFAULT_SCHEDULE)... > INFO | jvm 1| 2006/03/24 12:02:31 | 2006-03-24 12:02:31,827 > [defaultScheduler_Worker-3] INFO ContinuumStore:jdo - nb result > : 3 > INFO | jvm 1| 2006/03/24 12:02:32 | 2006-03-24 12:02:32,108 > [Thread-51624] DEBUG ScmManager - At revision 3114. > INFO | jvm 1| 2006/03/24 12:02:32 | 2006-03-24 12:02:32,186 [Thread-1] > INFO BuildController- The project was not built because all > changes are unknown. > INFO | jvm 1| 2006/03/24 12:02:32 | 2006-03-24 12:02:32,483 [Thread-1] > INFO ContinuumScm - Updating project: id: '1', name > 'Apreso Content Manager'. > INFO | jvm 1| 2006/03/24 12:02:32 | 2006-03-24 12:02:32,515 [Thread-1] > INFO ScmManager - Executing: svn --non-interactive update > INFO | jvm 1| 2006/03/24 12:02:32 | 2006-03-24 12:02:32,515 [Thread-1] > INFO ScmManager - Working directory: > C:\continuum\working-directory\1 > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,109 > [Thread-51626] DEBUG ScmManager - D > acm-lib\src\test\java\com\anystream\acm\service\TestLocationService.java > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,109 > [Thread-51626] DEBUG ScmManager - Skipping non-file: > acm-lib\src\test\java\com\anystream\acm\service\TestLocationService.java > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,109 > [Thread-51626] DEBUG ScmManager - Updated to revision > 3114. > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,187 [Thread-1] > INFO BuildController- The project was not built because all > changes are unknown. > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,484 [Thread-1] > INFO ContinuumScm - Updating project: id: '2', name > 'Apreso Content Manager Library'. > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,500 [Thread-1] > INFO ScmManager - Executing: svn --non-interactive update > INFO | jvm 1| 2006/03/24 12:02:33 | 2006-03-24 12:02:33,500 [Thread-1] > INFO ScmManager - Working directory: > C:\continuum\working-directory\2 > INFO | jvm 1| 2006/03/24 12:02:34 | 2006-03-24 12:02:34,109 > [Thread-51628] DEBUG ScmManager - D > src\test\java\com\anystream\acm\service\TestLocationService.java > INFO | jvm 1| 2006/03/24 12:02:34 | 2006-03-24 12:02:34,109 > [Thread-51628] DEBUG ScmManager - Skipping non-file: > src\test\java\com\anystream\acm\service\TestLocationService.java > INFO | jvm 1| 2006/03/24 12:02:34 | 2006-03-24 12:02:34,109 > [Thread-51628] DEBUG ScmManager - Updated to revision > 3114. > INFO | jvm 1| 2006/03/24 12:02:34 | 2006-03-
[jira] Updated: (CONTINUUM-661) ConcurrentModificationException when building maven2 multiproject
[ http://jira.codehaus.org/browse/CONTINUUM-661?page=all ] Emmanuel Venisse updated CONTINUUM-661: --- Fix Version: 1.1 > ConcurrentModificationException when building maven2 multiproject > - > > Key: CONTINUUM-661 > URL: http://jira.codehaus.org/browse/CONTINUUM-661 > Project: Continuum > Type: Bug > Versions: 1.0.3 > Environment: Solaris 10 Sparc > Reporter: Kaare Nilsen > Fix For: 1.1 > > > ConcurrentModificationException occurs sometimes. I counted 3 in about 15 > hours, when running a 55 module project. > Stacktrace : > INFO | jvm 1| 2006/04/19 03:00:03 | Apr 19, 2006 3:00:02 AM > org.quartz.core.JobRunShell run > INFO | jvm 1| 2006/04/19 03:00:03 | SEVERE: Job > DEFAULT.DEFAULT_SCHEDULE threw an unhandled Exception: > INFO | jvm 1| 2006/04/19 03:00:03 | > java.util.ConcurrentModificationException > INFO | jvm 1| 2006/04/19 03:00:03 | at > java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:617) > INFO | jvm 1| 2006/04/19 03:00:03 | at > java.util.LinkedList$ListItr.next(LinkedList.java:552) > INFO | jvm 1| 2006/04/19 03:00:03 | at > java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.buildqueue.evaluator.BuildProjectTaskViabilityEvaluator.evaluate(BuildProjectTaskViabilityEvaluator.java:62) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.codehaus.plexus.taskqueue.DefaultTaskQueue.put(DefaultTaskQueue.java:153) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:543) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:436) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:65) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.quartz.core.JobRunShell.run(JobRunShell.java:191) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) > INFO | jvm 1| 2006/04/19 03:00:03 | Apr 19, 2006 3:00:02 AM > org.quartz.core.ErrorLogger schedulerError > INFO | jvm 1| 2006/04/19 03:00:03 | SEVERE: Job > (DEFAULT.DEFAULT_SCHEDULE threw an exception. > INFO | jvm 1| 2006/04/19 03:00:03 | org.quartz.SchedulerException: Job > threw an unhandled exception. [See nested exception: > java.util.ConcurrentModificationException] > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.quartz.core.JobRunShell.run(JobRunShell.java:202) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) > INFO | jvm 1| 2006/04/19 03:00:03 | * Nested Exception (Underlying > Cause) --- > INFO | jvm 1| 2006/04/19 03:00:03 | > java.util.ConcurrentModificationException > INFO | jvm 1| 2006/04/19 03:00:03 | at > java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:617) > INFO | jvm 1| 2006/04/19 03:00:03 | at > java.util.LinkedList$ListItr.next(LinkedList.java:552) > INFO | jvm 1| 2006/04/19 03:00:03 | at > java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.buildqueue.evaluator.BuildProjectTaskViabilityEvaluator.evaluate(BuildProjectTaskViabilityEvaluator.java:62) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.codehaus.plexus.taskqueue.DefaultTaskQueue.put(DefaultTaskQueue.java:153) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:543) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinuum.java:436) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(ContinuumBuildJob.java:65) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.quartz.core.JobRunShell.run(JobRunShell.java:191) > INFO | jvm 1| 2006/04/19 03:00:03 | at > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) -- 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-713) re-enabling xfire?
[ http://jira.codehaus.org/browse/CONTINUUM-713?page=all ] Emmanuel Venisse updated CONTINUUM-713: --- Fix Version: 1.1 > re-enabling xfire? > -- > > Key: CONTINUUM-713 > URL: http://jira.codehaus.org/browse/CONTINUUM-713 > Project: Continuum > Type: Wish > Versions: 1.0.2, 1.0.3 > Reporter: Laszlo Hornyak Kocka > Fix For: 1.1 > > > As far as I remember XFire-based ws interface was disabled by default from > continuum in release 1.0.2, and I did not manange to re-enable it. > XFire 1.1 has motm support, so the build data can be streamed to clients e.g. > for IDE-plugins... -- 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-580) Fails to build on OS X
[ http://jira.codehaus.org/browse/CONTINUUM-580?page=all ] Emmanuel Venisse updated CONTINUUM-580: --- Fix Version: 1.1 > Fails to build on OS X > -- > > Key: CONTINUUM-580 > URL: http://jira.codehaus.org/browse/CONTINUUM-580 > Project: Continuum > Type: Bug > Components: Core system > Environment: OS X > Reporter: Henri Yandell > Fix For: 1.1 > Attachments: org.apache.maven.continuum.it.ShellIntegrationTest.txt > > > The build currently does not complete from the 1.0.x branch of Continuum. > An error occurs in the ShellIntegrationTest (see attachment). -- 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-416) A button I could click on the login page to remember me and automatically log me in next time
[ http://jira.codehaus.org/browse/CONTINUUM-416?page=all ] Emmanuel Venisse closed CONTINUUM-416: -- Assign To: Emmanuel Venisse Resolution: Duplicate Duplicated with CONTINUUM-513 > A button I could click on the login page to remember me and automatically log > me in next time > - > > Key: CONTINUUM-416 > URL: http://jira.codehaus.org/browse/CONTINUUM-416 > Project: Continuum > Type: Wish > Components: Web interface > Versions: 1.0 > Reporter: David Blevins > Assignee: Emmanuel Venisse > > > A button I could click on the login page to remember me and automatically log > me in next time. Something similar to JIRA or Confluence. -- 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-409) Email notifications could still include build stats when includeBuildResult is false
[ http://jira.codehaus.org/browse/CONTINUUM-409?page=all ] Emmanuel Venisse updated CONTINUUM-409: --- Fix Version: 1.1 > Email notifications could still include build stats when includeBuildResult > is false > > > Key: CONTINUUM-409 > URL: http://jira.codehaus.org/browse/CONTINUUM-409 > Project: Continuum > Type: Wish > Versions: 1.0 > Reporter: David Blevins > Fix For: 1.1 > > > I really like the "Build statistics" and "Changes" sections continuum creates > in the emails and definitely want them in every email. It's really just the > section that contains the output generated from the build itself that I don't > want as that will consistently be several megs of text for our project. > Basically, I assumed 'includeBuildResults=false' would just exclude out > everything after these lines > > Output: > > I really don't care what the option is called as long as I can get an email > as described. > Maybe you want to do something like this > true > true > 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
[jira] Updated: (CONTINUUM-573) Allow definition of default goals for a schedule
[ http://jira.codehaus.org/browse/CONTINUUM-573?page=all ] Emmanuel Venisse updated CONTINUUM-573: --- Fix Version: 1.1 > Allow definition of default goals for a schedule > > > Key: CONTINUUM-573 > URL: http://jira.codehaus.org/browse/CONTINUUM-573 > Project: Continuum > Type: New Feature > Components: Core system > Reporter: Michael Böckling > Fix For: 1.1 > > > There should be an option to associate default goals to a schedule. > Reason: a CI build must be fast and lean, while the nightly build can be more > demanding and will thus use different goals (+site, e.g.). Having to > configure the goals for each project again and again by hand is not something > you should have to do. -- 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-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=comments#action_68339 ] Emmanuel Venisse commented on CONTINUUM-44: --- A continuum profile should be an aggregate of multiple profile like this : My continuum profile can include : - a continuum profile that define the jdk 1.4 - a continuum profile that define the schedule - a continuum profile that define the build definition > multiple profiles > - > > Key: CONTINUUM-44 > URL: http://jira.codehaus.org/browse/CONTINUUM-44 > Project: Continuum > Type: New Feature > Reporter: Brett Porter > Fix For: 1.1 > > > would like to be able to define a profile (which can include certain > environmental things such as the version of m2 to use, the JDK version, etc). > Profiles should be able to be used globally, per group or per project. In > this way, you could build certain projects under a variety of different JDKs > for example. -- 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-563) integrate core gbuild distributed builds
[ http://jira.codehaus.org/browse/CONTINUUM-563?page=all ] Emmanuel Venisse updated CONTINUUM-563: --- Fix Version: 1.1 > integrate core gbuild distributed builds > > > Key: CONTINUUM-563 > URL: http://jira.codehaus.org/browse/CONTINUUM-563 > Project: Continuum > Type: Task > Reporter: Brett Porter > Fix For: 1.1 > > > see: http://opensource2.atlassian.com/confluence/oss/display/GBuild/Home -- 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-561) Invalid data-stamp at build-result UI
[ http://jira.codehaus.org/browse/CONTINUUM-561?page=all ]
Emmanuel Venisse closed CONTINUUM-561:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.3
> Invalid data-stamp at build-result UI
> -
>
> Key: CONTINUUM-561
> URL: http://jira.codehaus.org/browse/CONTINUUM-561
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0.2
> Environment: windows xp 32bit.
> jdk 1.4.2_5
> Reporter: Gediminas Siutilas
> Assignee: Emmanuel Venisse
> Fix For: 1.0.3
>
>
> The incorrect date stamp is shown at "Build result" window.
> Build # Start TimeEnd Time
> State
> 1 Jan 17, 2006 9:02:43 PM{color:red} Jan 1, 1970
> 2:00:00 AM{color} BuildingResult
> After page refresh when the build task is completed in the background the
> date stamp becomes valid.
--
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-553) Feature request that would enable user to delete the project's working directory.
[ http://jira.codehaus.org/browse/CONTINUUM-553?page=all ] Emmanuel Venisse updated CONTINUUM-553: --- Fix Version: 1.1 > Feature request that would enable user to delete the project's working > directory. > - > > Key: CONTINUUM-553 > URL: http://jira.codehaus.org/browse/CONTINUUM-553 > Project: Continuum > Type: New Feature > Reporter: Fritz Oconer > Fix For: 1.1 > > > Would like to request for an option where a user can delete the project's > working directory. This enables continuum to build on a fresh copy of the > project's source code. -- 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-738) Add permission for Working Copy view
Add permission for Working Copy view Key: CONTINUUM-738 URL: http://jira.codehaus.org/browse/CONTINUUM-738 Project: Continuum Type: Improvement Components: Web interface Reporter: Eric Bernstein It would be very useful if I could allow certain users to have access to continuum, view projects, see build results, etc... but not actually have access to the checked out source in the Working Copy. -- 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-152) bad ID leads to confusing page
[ http://jira.codehaus.org/browse/CONTINUUM-152?page=all ] Emmanuel Venisse updated CONTINUUM-152: --- Fix Version: 1.1 > bad ID leads to confusing page > -- > > Key: CONTINUUM-152 > URL: http://jira.codehaus.org/browse/CONTINUUM-152 > Project: Continuum > Type: Bug > Components: Web interface > Reporter: Brett Porter > Fix For: 1.1 > > > when hitting back, the project I had earlier deleted was there (I'll be > filing a separate bug for setting an expiry). > Hitting "info" on the now non-existant project brought the project info page > with unpopulated vars $project.name instead of an error page. I presume > others are similar. -- 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-436) prefill the build definition
[ http://jira.codehaus.org/browse/CONTINUUM-436?page=all ] Emmanuel Venisse updated CONTINUUM-436: --- Fix Version: 1.1 > prefill the build definition > > > Key: CONTINUUM-436 > URL: http://jira.codehaus.org/browse/CONTINUUM-436 > Project: Continuum > Type: Improvement > Versions: 1.0 > Reporter: Wim Deblauwe > Fix For: 1.1 > > > when adding a build definition it would be nice if it is pre-filled with the > values of the previous one. Most of the time the values will probably be the > same (wel at least the location of the pom.xml). It might save some typing > (and the possibility for typo's!). Or you can have a clone button or > something. -- 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-520) Finner grained Group Management
[ http://jira.codehaus.org/browse/CONTINUUM-520?page=all ] Emmanuel Venisse updated CONTINUUM-520: --- Fix Version: 1.1 > Finner grained Group Management > --- > > Key: CONTINUUM-520 > URL: http://jira.codehaus.org/browse/CONTINUUM-520 > Project: Continuum > Type: New Feature > Components: Core system > Versions: 1.0.2 > Reporter: Alex Mayorga Adame > Fix For: 1.1 > > > There should be group level access for project or group of projects. Not just > activities as it is now. > Example: Users in group A can build and see only especific projects and not > all of them. -- 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-622) Configure default build description
[ http://jira.codehaus.org/browse/CONTINUUM-622?page=all ] Emmanuel Venisse updated CONTINUUM-622: --- Fix Version: 1.1 > Configure default build description > --- > > Key: CONTINUUM-622 > URL: http://jira.codehaus.org/browse/CONTINUUM-622 > Project: Continuum > Type: Wish > Components: Core system > Versions: 1.0.2 > Reporter: Shinobu Kawai > Fix For: 1.1 > > > It would be great if it was possible to configure the build definition > created when adding a project. > e.g. Currently, the goal for m2 projects are "clean install". If you wanted > to have all your projects do "clean deploy site site:deploy", you need to > edit them one by one. But if you could configure the defaults, you can set > it to the goals you would use most. > I guess this will improve with the upcoming bulk updating feature, but you > still need to edit 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] Updated: (CONTINUUM-99) The Continuum Python CLI has to be configurable
[ http://jira.codehaus.org/browse/CONTINUUM-99?page=all ] Emmanuel Venisse updated CONTINUUM-99: -- Fix Version: 1.1 > The Continuum Python CLI has to be configurable > --- > > Key: CONTINUUM-99 > URL: http://jira.codehaus.org/browse/CONTINUUM-99 > Project: Continuum > Type: Improvement > Reporter: Trygve Laugstol > Fix For: 1.1 > > > In particular the host and port to talk to has to be configured. -- 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: (MNG-2409) @requiresDependencyResolution re-resolves transitive dependencies
@requiresDependencyResolution re-resolves transitive dependencies
-
Key: MNG-2409
URL: http://jira.codehaus.org/browse/MNG-2409
Project: Maven 2
Type: Bug
Components: Dependencies
Versions: 2.0.4
Reporter: Stepan Roh
Attachments: test.rdr.zip
Consider this scenario:
project A
project B, depends on A
project C, to be compiled, depends on B
projects A and B are from artifact repository, project C is being compiled
Let's say that before phase compile of project C my plugin is called which
looks for all dependencies of C (in our case A and B) and change their file
(Artifact.setFile()). All those dependencies are already resolved. Then
compile:compile is run which has @requiresDependencyResolution compile which
leads to A being re-resolved = it loses my file, but B retains it:
original A.getFile() = a.jar
original B.getFile() = b.jar
changed A.getFile() = xa.jar
changed B.getFile() = xb.jar
after compile A.getFile() = a.jar
after compile B.getFile() = xb.jar
Attached archive contains all necessary source code (source of A, B, C and test
Mojo) to recreate the situation. Just do:
unzip test.rdr.zip
cd test.rdr
( cd project-a; mvn install )
( cd project-b; mvn install )
( cd maven-refile-plugin; mvn install )
( cd project-c; mvn install )
The output of last mvn install will be something like (edited for brevity):
[INFO] [refile:set-file {execution: set}]
[INFO] Dependency: test.rdr:project-b:jar:1.0-SNAPSHOT:compile
[INFO] resolved: true
[INFO] file: .../project-b-1.0-SNAPSHOT.jar
[INFO] new file: .../project-b-1.0-SNAPSHOT.jar.new.jar
[INFO] Dependency: test.rdr:project-a:jar:1.0-SNAPSHOT:compile
[INFO] resolved: true
[INFO] file: .../project-a-1.0-SNAPSHOT.jar
[INFO] new file: .../project-a-1.0-SNAPSHOT.jar.new.jar
[INFO] Compile classpath: [target\classes,
.../project-b-1.0-SNAPSHOT.jar.new.jar, .../project-a-1.0-SNAPSHOT.jar.new.jar]
[INFO] [refile:show-file {execution: show-before-compile}]
[INFO] Dependency: test.rdr:project-b:jar:1.0-SNAPSHOT:compile
[INFO] resolved: true
[INFO] file: .../project-b-1.0-SNAPSHOT.jar.new.jar
[INFO] Dependency: test.rdr:project-a:jar:1.0-SNAPSHOT:compile
[INFO] resolved: true
[INFO] file: .../project-a-1.0-SNAPSHOT.jar.new.jar
[INFO] Compile classpath: [target\classes,
.../project-b-1.0-SNAPSHOT.jar.new.jar, .../project-a-1.0-SNAPSHOT.jar.new.jar]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [refile:show-file {execution: show-after-compile}]
[INFO] Dependency: test.rdr:project-b:jar:1.0-SNAPSHOT:compile
[INFO] resolved: true
[INFO] file: .../project-b-1.0-SNAPSHOT.jar.new.jar
[INFO] Dependency: test.rdr:project-a:jar:1.0-SNAPSHOT:compile
[INFO] resolved: true
[INFO] file: .../project-a-1.0-SNAPSHOT.jar
[INFO] Compile classpath: [target\classes,
.../project-b-1.0-SNAPSHOT.jar.new.jar, .../project-a-1.0-SNAPSHOT.jar]
...
As you can see after compile is run, project A's file is back to original
value, but B retained new file. I think this is a strange behaviour and should
be changed to act one way or another, preferably that already resolved
dependencies are not re-resolved.
--
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-529) Modules (child) scm connection URLs are not constructed correctly
[ http://jira.codehaus.org/browse/CONTINUUM-529?page=all ]
Emmanuel Venisse updated CONTINUUM-529:
---
Fix Version: 1.1
> Modules (child) scm connection URLs are not constructed correctly
> -
>
> Key: CONTINUUM-529
> URL: http://jira.codehaus.org/browse/CONTINUUM-529
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0.2
> Reporter: Grégory Joseph
> Fix For: 1.1
>
>
> It *seems* to me that, when adding a parent pom to continuum, which has
> defined, but the scm url only defined in the parent, it gets and
> parses the child poms correctly, but their scm URLs are build as
> ${parentScmUrl}/${childArtifactId} , while I think they should rather be
> ${parentScmUrl}/${modulePath}
> Maybe this is a maven inheritance issue, though ?
--
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-133) Language settings affect proper check-in for Subversion
[ http://jira.codehaus.org/browse/MRELEASE-133?page=comments#action_68340 ]
Grzegorz Slowikowski commented on MRELEASE-133:
---
I had the same problem. My solution was by setting system variable
LC_MESSAGES=en_EN
as described here:
http://svnbook.red-bean.com/en/1.2/svn.advanced.l10n.html
I think this is maven-scm-provider-svnexe issue, not release-plugin.
> Language settings affect proper check-in for Subversion
> ---
>
> Key: MRELEASE-133
> URL: http://jira.codehaus.org/browse/MRELEASE-133
> Project: Maven 2.x Release Plugin
> Type: Bug
> Versions: 2.0-beta-4
> Reporter: Joerg Schaible
> Priority: Minor
>
>
> The plugin seems to parse the returned lines of the svn command when checking
> in the tagged version:
> {noformat}
> ...
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-5489.commit
> C:/Work/standard/master-pom/pom.xml
> [INFO] Working directory: C:\Work\standard\master-pom
> [INFO] Unknown line: 'Sende pom.xml'
> [INFO] Unknown line: 'bertrage Daten .'
> [INFO] Unknown line: 'Revision 1140 ?bertragen.'
> [INFO] Tagging release with the label v_4...
> [INFO] Executing: svn --non-interactive copy --file
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-2091412033.commit .
> http://websvn/svn/essvn/development/buildsystem/maven-2/master-pom/tags/v_4
> [INFO] Working directory: C:\Work\standard\master-pom
> [INFO] Transforming 'Elsag Master Project'...
> [INFO] Removing release POMs...
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-1116553554.commit
> C:/Work/standard/master-pom/pom.xml
> [INFO] Working directory: C:\Work\standard\master-pom
> [INFO] Unknown line: 'Sende pom.xml'
> [INFO] Unknown line: 'bertrage Daten .'
> [INFO] Unknown line: 'Revision 1142 ?bertragen.'
> [INFO] Release preparation complete.
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> ...
> {noformat}
> Starting the plugin with
> {noformat}
> LANG=C mvn release:prepare
> {noformat}
> does not produce this _Unknown line_ messages. The plugin should invoke the
> svn command with an English locale.
--
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-598) Ability to specify which scm connection should be used to build the project (connection or developerConnection)
[ http://jira.codehaus.org/browse/CONTINUUM-598?page=all ] Emmanuel Venisse updated CONTINUUM-598: --- Fix Version: 1.1 > Ability to specify which scm connection should be used to build the project > (connection or developerConnection) > --- > > Key: CONTINUUM-598 > URL: http://jira.codehaus.org/browse/CONTINUUM-598 > Project: Continuum > Type: New Feature > Components: Web interface, Core system > Versions: 1.0, 1.0.1, 1.0.2 > Reporter: Igor Vaynberg > Fix For: 1.1 > > > i am a committer on a sf.net project. the anonymous cvs access is extremely > unstable, but the developer access is rock solid. since i am a developer and > i run a continuum server i am in a position to leverage the developer scm > connection. it would be great if i can just tell continuum to use the > developerConnection scm url rather then the regular connection scm url. > i tried chaning the url in the project info manually, but after the project > is built once the url reverts back to the one in the pom ( as it should i > would imagine ) > i think a simple drop down in project info with > connection/developerConnection choice would be great -- 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-424) Do not add again the same project
[ http://jira.codehaus.org/browse/CONTINUUM-424?page=all ] Emmanuel Venisse updated CONTINUUM-424: --- Fix Version: 1.1 > Do not add again the same project > - > > Key: CONTINUUM-424 > URL: http://jira.codehaus.org/browse/CONTINUUM-424 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0 > Reporter: Vincent Massol > Fix For: 1.1 > > > I added some projects using a POM URL. Then I hit F5 in my browser to refresh > the view and all the projects were added 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] Updated: (CONTINUUM-397) try building a project without setting an build definition show uncatched java exception
[ http://jira.codehaus.org/browse/CONTINUUM-397?page=all ] Emmanuel Venisse updated CONTINUUM-397: --- Fix Version: 1.1 > try building a project without setting an build definition show uncatched > java exception > > > Key: CONTINUUM-397 > URL: http://jira.codehaus.org/browse/CONTINUUM-397 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0 > Environment: Mac os x > Reporter: yo > Fix For: 1.1 > > > try building a project without setting an build definition show uncatched > java exception > ognl.MethodFailedException: Method "buildProject" failed for object [EMAIL > PROTECTED] [org.apache.maven.continuum.ContinuumException: Project requires a > build definition.] > at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) > at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) > at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) > at ognl.ASTMethod.getValueBody(ASTMethod.java:75) > at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) > at ognl.SimpleNode.getValue(SimpleNode.java:210) > at ognl.Ognl.getValue(Ognl.java:333) > at ognl.Ognl.getValue(Ognl.java:378) > at ognl.Ognl.getValue(Ognl.java:357) > at > org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) > at > org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) > at > org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) > at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) > at org.mortbay.http.HttpServer.service(HttpServer.java:879) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) > /-- Encapsulated exception \ > org.apache.maven.continuum.ContinuumException: Project requires a build > definition. > at > org.apache.maven.continuum.DefaultContinuum.getDefaultBuildDefinition(DefaultContinuum.java:804) > at > org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:319) > 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:324) > at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) > at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) > at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) > at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) > at ognl.ASTMethod.getValueBody(ASTMethod.java:75) > at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) > at ognl.SimpleNode.getValue(SimpleNode.java:210) > at ognl.Ognl.getValue(Ognl.java:333) > at ognl.Ognl.getValue(Ognl.java:378) > at ognl.Ognl.getValue(Ognl.java:357) > at > org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) > at > org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) > at > org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) > at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) > at > org.mortbay.jetty.servlet.WebAppli
[jira] Updated: (CONTINUUM-398) changes window shows internal id for project
[ http://jira.codehaus.org/browse/CONTINUUM-398?page=all ] Emmanuel Venisse updated CONTINUUM-398: --- Fix Version: 1.1 > changes window shows internal id for project > > > Key: CONTINUUM-398 > URL: http://jira.codehaus.org/browse/CONTINUUM-398 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0 > Environment: Mac Os X > Reporter: yo > Fix For: 1.1 > > > The build result window shows the internal id for a project in the url > for example > 6/somedir/somefile > this should be > somedir/somefile -- 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-575) Version number doesn't update on projects screen
[ http://jira.codehaus.org/browse/CONTINUUM-575?page=all ] Emmanuel Venisse updated CONTINUUM-575: --- Fix Version: 1.1 > Version number doesn't update on projects screen > > > Key: CONTINUUM-575 > URL: http://jira.codehaus.org/browse/CONTINUUM-575 > Project: Continuum > Type: Bug > Versions: 1.0.2 > Reporter: Brian Fox > Fix For: 1.1 > > > I changed the version number on my poms that continuum is building from scm. > The display still shows the old version number. -- 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-593) Unable to update starteam url
[ http://jira.codehaus.org/browse/CONTINUUM-593?page=all ] Emmanuel Venisse updated CONTINUUM-593: --- Fix Version: 1.1 > Unable to update starteam url > - > > Key: CONTINUUM-593 > URL: http://jira.codehaus.org/browse/CONTINUUM-593 > Project: Continuum > Type: Bug > Components: Web interface, Core system > Versions: 1.0.2 > Environment: Solaris 10 > Reporter: Aviran Mordo > Fix For: 1.1 > > > I have a project setup, now the StarTeam password changed. When I go to the > web interface and change the Scm Url to reflect the new password. Continuum > ignores the new username/password while trying to update the project from > StarTeam. The url (from the continuum.log file) becomes: stcmd co -x -nologo > -stop -p @158.xxx.xxx.xxx:49205/Project... > Note there is no username and password in the command line before the @. > If I create a new project with the updated pom file and the same scm element > the new project works. > One more thing. The web interface shows the Username:Password in the scm > element, it just that when it runs, continuum ignores these settings. -- 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-458) Trigger scripts ?
[ http://jira.codehaus.org/browse/CONTINUUM-458?page=all ] Emmanuel Venisse updated CONTINUUM-458: --- Fix Version: 1.1 > Trigger scripts ? > -- > > Key: CONTINUUM-458 > URL: http://jira.codehaus.org/browse/CONTINUUM-458 > Project: Continuum > Type: New Feature > Versions: 1.0.1 > Reporter: Grégory Joseph > Fix For: 1.1 > > > http://maven.apache.org/continuum/guides/getting-started/index.html mentions > 2 python scripts. > However, these are not present in the 1.0.1 tgz distribution. > I hope these are useable as on-commit scripts, to trigger builds when > commiting. > Could be extra nice to have (or others) downloadable as separate artifact, in > order to use them as on-commit trigger scripts, for instance when your > continuum instance runs remotely from the scm server, you wouldn't > necessarily want your scm admin to have to get the 12mb archive ;) -- 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-358) User Authentication via LDAP
[ http://jira.codehaus.org/browse/CONTINUUM-358?page=all ] Emmanuel Venisse updated CONTINUUM-358: --- Fix Version: 1.1 > User Authentication via LDAP > > > Key: CONTINUUM-358 > URL: http://jira.codehaus.org/browse/CONTINUUM-358 > Project: Continuum > Type: New Feature > Components: Web interface > Reporter: Frank Zhao > Fix For: 1.1 > > > Please add LDAP support for the user authentication in Continuum user > management function. -- 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-417) Don't list the entire revision history for a changed file, just the most recent changes
[ http://jira.codehaus.org/browse/CONTINUUM-417?page=all ] Emmanuel Venisse updated CONTINUUM-417: --- Fix Version: 1.1 > Don't list the entire revision history for a changed file, just the most > recent changes > --- > > Key: CONTINUUM-417 > URL: http://jira.codehaus.org/browse/CONTINUUM-417 > Project: Continuum > Type: Improvement > Components: Web interface > Versions: 1.0 > Reporter: David Blevins > Fix For: 1.1 > > > Instead, think of allowing ViewCVS or FishEye to be configured and create > links. > It is *extremely* annoying the way it is now. On OpenEJB, when a project.xml > file is changed, we get this: > modules/core/project.xml > djencks GERONIMO-1123 add dependencies on plugin where it is used > djencks GERONIMO-1123 Use dependency plugin to generate > geronimo-service.xml files > djencks GERONIMO-880 Remove bouncy-castle in favor of some copied > classes > ammulder branches: 1.58.2; Sync with Geronimo changes - ServerInfo now > an interface - Moved management API interfaces to a new module > djencks GERONIMO-784 and refactor xmlbeans2 plugin for move to xmlbeans > djencks GERONIMO-782 step 1 remove xfire. Also clean up dependencies a > bit > dain Removed openorb/tmporb Removed tools jar hack Removed all stub/tie > compiler code since is used openorb > djencks GERONIMO-738 move to xmlbeans v2 > dain Added KernelFactory for pluggable kernel Kernel is now an interface > Moved Kernel implementation to basic kernel Converted JMX registry and config > manager to plain old gbeans (they do not require special access to the > kernel) Magic attributes such as state and enabled are now accessed via > kernel methods Use of getAttribute and invoke for magic attributes and state > transition is now deprecated Cleaned up cruft in GBean infos such as > declaration of non existent attributes Upgraded to newest CGLIB, asm, and > commons-collections > djencks update dependency versions > maguroRemoved reliance on tmporb-ssl > djencks Add NamedUsernamePasswordCredential and supporting > infrastructure to allow configuring security info for ws client calls > maguroChange dependency to geronimo-spec-corba. > maguroUpdated to use the default Sun ORB. > dain Convert remaining tmporb references to openorb > dain Switch to tmporb > chirino Implemented WSDL port address replacment. > dblevins First run of axis integration. more to sew up yet. > maguroIntermediate CORBA checkin. > djencks simple MEJB implementation, some changes to help MEJB > deployment > dblevins Revising the WSContainer to better support rpc/encoded strictly > against a lightweight WSDL->Java mapping. Added validation for lightweigth > mappings. Added ability to download the WSDL via > http://foobar.com/someservice?wsdl > maguroNeeded for CSIv2 > djencks Partial implementation of GERONIMO-450. GBean names are > (mostly) constructed like jsr-77 names and xml config usually only needs to > specify namePart and optionally type > chirino The geronimo security package now depends on activeio and no > longer on geronimo remoting. > dblevins Basic soap rpc/encoded deployment and container support along > with a general revamping of the networkservice stacks. > dblevins The asm and bouncycastle dependencies had hardcoded versions > dblevins Reformatted > dain Replaced xml parsed entities for dependency version numbers with > project.properties > djencks GERONIMO-402, 464. Split openejb and security deployment code > into separate modules > djencks GERONIMO-403/405/418 Split builders out of j2ee, naming, and > jetty > maguroIntermediate CORBA checkin > dblevins Updated castor version to 0.9.5.3 > maguroCORBA jars > djencks don't make duplicate xmlbeans-generated classes. Work around > problem with xmlbeans imported group refs > dblevins Added AppClient support for JNDI > dain Consolidated all version numbers into etc/version-info.ent > djencks Add timer support to session and mdbs. (entities still todo). > Adapt to TransactionContextManager. Adapt to deploying with external plan. > > djencks Upgrade conncurrent to 1.3.4 > djencks Implement message driven bean deployment and some of > message-destination refs. Update to howl 0.1.3 > dain Updated the spec jar version numbers to rc2 > djencks Eliminate two threadlocals. Move more thread specific context > information (unshareableResources and applicationManagedSecurityRes
[jira] Updated: (CONTINUUM-472) wrong UI for ant based projects
[ http://jira.codehaus.org/browse/CONTINUUM-472?page=all ] Emmanuel Venisse updated CONTINUUM-472: --- Fix Version: 1.1 > wrong UI for ant based projects > --- > > Key: CONTINUUM-472 > URL: http://jira.codehaus.org/browse/CONTINUUM-472 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.1 > Reporter: Milos Kleint > Fix For: 1.1 > > > in order to run ant based project in continuum one needs to add a build > definition. > but that one has completely wrong UI, it talks about POM file and Goals. But > ant has build.xml files and targets. > and since it's not possible to run the build without this info, it should be > present at the creation page of the ant project. -- 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-668) Build history not showing after 1.0.2 to 1.0.3 migration
[ http://jira.codehaus.org/browse/CONTINUUM-668?page=all ] Emmanuel Venisse updated CONTINUUM-668: --- Fix Version: 1.1 > Build history not showing after 1.0.2 to 1.0.3 migration > > > Key: CONTINUUM-668 > URL: http://jira.codehaus.org/browse/CONTINUUM-668 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.3 > Environment: hpux, winxp > Reporter: Shinobu Kawai > Fix For: 1.1 > > > After following the instructions at > http://maven.apache.org/continuum/upgrade.html and upgrading to 1.0.3, the > build history screen shows nothing. Builds after the upgrade are showing. > However, if I directly put the URL for a specific build, I can view the > results. > Like this: > http://localhost:8080/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=534&id=14 -- 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-581) Share continuum build number to underlying build project
[ http://jira.codehaus.org/browse/CONTINUUM-581?page=all ]
Emmanuel Venisse updated CONTINUUM-581:
---
Fix Version: 1.1
> Share continuum build number to underlying build project
>
>
> Key: CONTINUUM-581
> URL: http://jira.codehaus.org/browse/CONTINUUM-581
> Project: Continuum
> Type: New Feature
> Reporter: Alex Boisvert
> Fix For: 1.1
>
>
> It would be nice if Continuum shared its build number with the underlying
> build projects (e.g. Ant/Maven{1,2})
> What I'm trying to do is generate artifacts with the following naming
> convention:
> myproject-1.0-123.zip
> where 1.0 is the version number defined in Maven (e.g. pom.xml), and 123
> is the Continuum build number. Artifacts could be .zip, .jar, .war, etc.
> I guess one way to do this is to pass the build number via an environment
> variable
--
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-672) test-jar artifacts are not copied to the configured deployment directory
[ http://jira.codehaus.org/browse/CONTINUUM-672?page=all ] Emmanuel Venisse updated CONTINUUM-672: --- Fix Version: 1.1 > test-jar artifacts are not copied to the configured deployment directory > > > Key: CONTINUUM-672 > URL: http://jira.codehaus.org/browse/CONTINUUM-672 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.3 > Environment: cocoon.zones > Reporter: Jorg Heymans > Fix For: 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] Closed: (CONTINUUM-673) html is not escaped properly in build output
[ http://jira.codehaus.org/browse/CONTINUUM-673?page=all ] Emmanuel Venisse closed CONTINUUM-673: -- Assign To: Emmanuel Venisse Resolution: Duplicate > html is not escaped properly in build output > > > Key: CONTINUUM-673 > URL: http://jira.codehaus.org/browse/CONTINUUM-673 > Project: Continuum > Type: Bug > Components: Core system > Environment: cocoon.zones > Reporter: Jorg Heymans > Assignee: Emmanuel Venisse > > > see > http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=178&id=162 > for an example -- 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-562) "groupId is null" when uploading maven 1 pom but it isn't
[ http://jira.codehaus.org/browse/CONTINUUM-562?page=all ] Emmanuel Venisse updated CONTINUUM-562: --- Fix Version: 1.1 > "groupId is null" when uploading maven 1 pom but it isn't > - > > Key: CONTINUUM-562 > URL: http://jira.codehaus.org/browse/CONTINUUM-562 > Project: Continuum > Type: Bug > Components: Web interface > Versions: 1.0.2 > Environment: Windows 2000, jdk 1.4.2_09, PIV 1Gb > Reporter: David Martínez > Fix For: 1.1 > Attachments: project.xml > > > Hi, > I'm trying to upload enclosed maven 1 pom and get a message: > " * Error while reading maven POM. > Check the logs for more details. > * groupId is null. > Check the logs for more details." > But, as you can see in the enclosed pom, groupId is not null. > The pom works properly when unsing it maven 1. > Thank you in advance. -- 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-738) Add permission for Working Copy view
[ http://jira.codehaus.org/browse/CONTINUUM-738?page=all ] Emmanuel Venisse updated CONTINUUM-738: --- Fix Version: 1.1 > Add permission for Working Copy view > > > Key: CONTINUUM-738 > URL: http://jira.codehaus.org/browse/CONTINUUM-738 > Project: Continuum > Type: Improvement > Components: Web interface > Reporter: Eric Bernstein > Fix For: 1.1 > > > It would be very useful if I could allow certain users to have access to > continuum, view projects, see build results, etc... but not actually have > access to the checked out source in the Working Copy. -- 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: (MNG-2410) adding a method in AbstractMavenReport to obtain newSink()
adding a method in AbstractMavenReport to obtain newSink() -- Key: MNG-2410 URL: http://jira.codehaus.org/browse/MNG-2410 Project: Maven 2 Type: New Feature Components: Sites & Reporting Versions: 2.0.4 Environment: all Reporter: Olivier Lamy Actually when extending AbstractMavenReport, I can get a Sink for write only one page. For report, I need to create some pages. I like to have a new method called newSink(FileWriter) to write some other pages. Or could we have a SinkFactory object injected in AbstractMavenReport ? Note, I need a Sink with the current site skin. Thanks, -- Olivier -- 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-664) Continuum main project page displays error crosses against projects that have successfully built.
[ http://jira.codehaus.org/browse/CONTINUUM-664?page=all ] Emmanuel Venisse updated CONTINUUM-664: --- Fix Version: 1.1 > Continuum main project page displays error crosses against projects that have > successfully built. > -- > > Key: CONTINUUM-664 > URL: http://jira.codehaus.org/browse/CONTINUUM-664 > Project: Continuum > Type: Bug > Versions: 1.0.3 > Environment: Linux. Maven 2.0.3 > Reporter: Adrian > Fix For: 1.1 > Attachments: schedules.jpg, wrapper.log.zip > > > Continuum main project page displays error crosses against projects that have > successfully built. When you look at the build log for one of these projects > it shows that it built correctly. > This is an intermittent bug and I cannot spot a pattern as to why it is > happening. -- 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-2410) adding a method in AbstractMavenReport to obtain newSink()
[ http://jira.codehaus.org/browse/MNG-2410?page=comments#action_68345 ] Kenney Westerhof commented on MNG-2410: --- Just so this doesn't get lost: I've prepared some patches a few months ago, and updated them. They still need to be discussed as they're API changes. Patches: http://gods.nl/~forge/sink/ A sample multi-page report using the new api svn://svn.neonics.com/m2-plugins/trunk/schemadoc-maven-plugin/ (or http://svn.neonics.com/svn/m2-plugins/trunk/schemadoc-maven-plugin, user/pass=anonymous/anonymous). > adding a method in AbstractMavenReport to obtain newSink() > -- > > Key: MNG-2410 > URL: http://jira.codehaus.org/browse/MNG-2410 > Project: Maven 2 > Type: New Feature > Components: Sites & Reporting > Versions: 2.0.4 > Environment: all > Reporter: Olivier Lamy > > > Actually when extending AbstractMavenReport, I can get a Sink for write only > one page. > For report, I need to create some pages. > I like to have a new method called newSink(FileWriter) to write some other > pages. > Or could we have a SinkFactory object injected in AbstractMavenReport ? > Note, I need a Sink with the current site skin. > Thanks, > -- > Olivier -- 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-701) Continuum obscures the output of CVS exceptions
[ http://jira.codehaus.org/browse/CONTINUUM-701?page=all ]
Emmanuel Venisse updated CONTINUUM-701:
---
Assign To: (was: John Casey)
Fix Version: 1.1
> Continuum obscures the output of CVS exceptions
> ---
>
> Key: CONTINUUM-701
> URL: http://jira.codehaus.org/browse/CONTINUUM-701
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0.3
> Reporter: Alex Mayorga Adame
> Fix For: 1.1
>
>
> The error in Continuum on initial checkout of a Maven 2 project under
> Continuum 1.0.3 when using following syntax of SCM:
> {code:none}
> scm:cvs:pserver:[EMAIL PROTECTED]:port:repository:module
> {code}
> Error in Continuum is as follows and doesn't represent real issue on mvn
> scm:checkout goal:
> {code:none}
> Provider message: The cvs command failed.
> Command output:
> --
> port/repository: no such repository
> cvs checkout: authorization failed: server host rejected access to
> port/repository for user user
> cvs checkout: used empty password; try "cvs login" with a real password
> ---
> {code}
> The Continuum logs for this error:
> {code:none}
> INFO | jvm 1 | 2006/05/11 01:00:08 | 2006-05-11 01:00:08,921 [Thread-2] WARN
> SQL - Object with id "0" not found !
> INFO | jvm 1 | 2006/05/11 01:00:08 | 2006-05-11 01:00:08,950 [Thread-2] INFO
> ContinuumScm - Checking out project: 'Maven Webapp Archetype', id: '12' to
> '/usr/bin/continuum/continuum-1.0.3/bin/solaris/../../apps/continuum/working-directory/12'.
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,026 [Thread-2] DEBUG
> ScmManager - cvsRoot: :pserver:[EMAIL PROTECTED]:port/repository
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,027 [Thread-2] DEBUG
> ScmManager - passFile: /opt/continuum-user/.cvspass
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,029 [Thread-2] DEBUG
> ScmManager - cvsroot :pserver:[EMAIL PROTECTED]:port/repository already exist
> in /opt/continuum-user/.cvspass. SKIPPED.
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,033 [Thread-2] INFO
> ScmManager - Executing: cvs -z3 -f -d :pserver:[EMAIL
> PROTECTED]:port/repository -q checkout -d 12 path/to/module
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,033 [Thread-2] INFO
> ScmManager - Working directory:
> /usr/bin/continuum/continuum-1.0.3/apps/continuum/working-directory
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,653 [Thread-2] WARN
> ContinuumScm - Error while checking out the code for project: 'Maven Webapp
> Archetype', id: '12' to
> '/usr/bin/continuum/continuum-1.0.3/bin/solaris/../../apps/continuum/working-directory/12'.
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,655 [Thread-2] WARN
> ContinuumScm - Command output: port/repository: no such repository
> INFO | jvm 1 | 2006/05/11 01:00:09 | cvs checkout: authorization failed:
> server host rejected access to port/repository for user user
> INFO | jvm 1 | 2006/05/11 01:00:09 | cvs checkout: used empty password; try
> "cvs login" with a real password
> INFO | jvm 1 | 2006/05/11 01:00:09 |
> INFO | jvm 1 | 2006/05/11 01:00:09 | 2006-05-11 01:00:09,655 [Thread-2] WARN
> ContinuumScm - Provider message: The cvs command failed.
> {code}
> The _real_ error behind this:
> {code:none}
> bash-2.03$ mvn scm:checkout -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'scm'.
> [INFO]
>
> [INFO] Building Maven Webapp Archetype
> [INFO]task-segment: [scm:checkout] (aggregator-style)
> [INFO]
>
> [INFO] [scm:checkout]
> [INFO] Removing /export1/eae/am74839/pvr/target/checkout
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Cannot run checkout command :
>
> Embedded error: Exception while executing SCM command.
> cvs: not found
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Cannot run checkout
> command :
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalA
[jira] Closed: (CONTINUUM-682) Builds that are only On Demand, not scheduled
[ http://jira.codehaus.org/browse/CONTINUUM-682?page=all ] Emmanuel Venisse closed CONTINUUM-682: -- Assign To: Emmanuel Venisse Resolution: Won't Fix We won't add this feature because you can do it with schedule defined in the future. Personally, I don't understand why you put in a ci tool, something that must be run manually like you do it from the command line. > Builds that are only On Demand, not scheduled > - > > Key: CONTINUUM-682 > URL: http://jira.codehaus.org/browse/CONTINUUM-682 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.3 > Reporter: David Eric Pugh > Assignee: Emmanuel Venisse > > > I would like to be able to have a build that is purely on demand, without > editing build targets. For example, I want to run a build that deploys my > applciation to test, but I dont' want it scheduled. Or runs our Selenium > tests, but again, only on demand. Currently you must pick a schedule. I > tried setting a schedule for 1970, so it would never run automatically, but > Continuum prevented me by saying it would never run. While that was nice, i > would rather have a warning then be prevented! -- 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-694) Add proxy configuration support for notifiers
[ http://jira.codehaus.org/browse/CONTINUUM-694?page=comments#action_68349
]
Emmanuel Venisse commented on CONTINUUM-694:
do you have tested java properties for proxies? http.proxyHost,
http.proxyPort...
(http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html)
> Add proxy configuration support for notifiers
> -
>
> Key: CONTINUUM-694
> URL: http://jira.codehaus.org/browse/CONTINUUM-694
> Project: Continuum
> Type: Improvement
> Components: MSN Notifier, Mail Notifier, Jabber Notifier, IRC Notifier, AOL
> Notifier
> Versions: 1.0.3
> Reporter: Anatol Pomozov
>
>
> I would like to use Continuum for project, but I have problem - all ports are
> proxied. Not only HTTP but also mail and all others.
> That is why I cant use mailnotifier. It breaks with error listed below. As I
> said timeout occures due to port is closed by proxy. I check it only for mail
> notifier but I beleive that it is related to all other notifiers.
> {{
> 72414 [Thread-2] ERROR
> org.apache.maven.continuum.notification.ContinuumNotificationDispatcher -
> Error while trying to use the mailnotifier.
> org.codehaus.plexus.notification.NotificationException: Exception while
> sending message.
> at
> org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:403)
> at
> org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:307)
> at
> org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendNotification(MailContinuumNotifier.java:202)
> at
> org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:173)
> at
> org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96)
> at
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:378)
> at
> org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47)
> at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.codehaus.plexus.mailsender.MailSenderException: Error while
> sending mail.
> at
> org.codehaus.plexus.mailsender.javamail.JavamailMailSender.send(JavamailMailSender.java:217)
> at
> org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:399)
> ... 8 more
> Caused by: javax.mail.MessagingException: Could not connect to SMTP host:
> smtp.gmail.com, port: 465;
> nested exception is:
> java.net.ConnectException: Connection timed out: connect
> at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1213)
> at
> com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:311)
> at javax.mail.Service.connect(Service.java:255)
> at javax.mail.Service.connect(Service.java:134)
> at javax.mail.Service.connect(Service.java:86)
> at com.sun.mail.smtp.SMTPTransport.connect(SMTPTransport.java:144)
> at javax.mail.Transport.send0(Transport.java:150)
> at javax.mail.Transport.send(Transport.java:80)
> at
> org.codehaus.plexus.mailsender.javamail.JavamailMailSender.send(JavamailMailSender.java:213)
> ... 9 more
> }}
--
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-689) User settings permission
[ http://jira.codehaus.org/browse/CONTINUUM-689?page=all ] Emmanuel Venisse updated CONTINUUM-689: --- Fix Version: 1.1 > User settings permission > > > Key: CONTINUUM-689 > URL: http://jira.codehaus.org/browse/CONTINUUM-689 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.3 > Reporter: Felipe Leme > Fix For: 1.1 > > > There should be a permission that allows the user to change his information > (like email and password) - right now either the user has no permission to do > it or it has full access to user/group management. -- 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-530) HTML encode the build output
[ http://jira.codehaus.org/browse/CONTINUUM-530?page=all ] Emmanuel Venisse updated CONTINUUM-530: --- Fix Version: 1.1 > HTML encode the build output > > > Key: CONTINUUM-530 > URL: http://jira.codehaus.org/browse/CONTINUUM-530 > Project: Continuum > Type: Bug > Reporter: Trygve Laugstol > Fix For: 1.1 > Attachments: continuum-snapshot.png, htmlEscape.patch > > > Currently the output is included verbatim, which means that the browser will > try to parse any XML that's in the build output. See the attached snapshot > versus the actual output: > -- SNIP -- > > identifier="swrefVrecordVdatasetZaddressVcollectionZne_adresseVkeysZ158428" > typeName="View of GAB Adresse"> > Norge > 158428 > 219 > Bærum > KYRRES VEI > 19 > C > > 1369 > STABEKK > > ID="swrefVgeometryVdatasetZaddressVcollectionZne_adresseVfieldZposisjonVlocalZTrueVkeysZ536885020X662636086X690767" > swldy:world="swrefVworldVdatasetZaddressVuniverseZ2VworldZ0"> > -409769860,-357023026 > > > > ID="swrefVgeometryVdatasetZaddressVcollectionZne_adresseVfieldZannotationVlocalZTrueVkeysZ536885020X662636069X690770" > swldy:world="swrefVworldVdatasetZaddressVuniverseZ2VworldZ0"> > -409769860,-357022026 > 19C > 0.00 > 22 > > 1.00 > > > > > > > > -- SNIP -- -- 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
