[jira] Created: (MNG-2659) possible to create an infinite loop in processing a POM

[Brett Porter (JIRA)]

possible to create an infinite loop in processing a POM
---

 Key: MNG-2659
 URL: http://jira.codehaus.org/browse/MNG-2659
 Project: Maven 2
  Issue Type: Bug
  Components: Inheritence and Interpolation
Affects Versions: 2.0.4
Reporter: Brett Porter


If you define a property like this:

{code:xml}

  ${http.port}

{code}

The interpolator *correctly* identifies that this will cause a loop and throws 
an Exception.

However, if you define it with some indirection, eg:
{code:xml}

  ${foo}
  ${http.port}

{code}

This causes an infinite loop, where it should be detected and the same 
exception thrown as above.

-- 
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-870) Make plugin discovery reactor aware

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-870?page=all ]

Brett Porter closed MNG-870.


Resolution: Fixed

you can't reopen stuff fixed in the past without upsetting JIRA. If it's a 
regression, please open a new ticket.

> Make plugin discovery reactor aware
> ---
>
> Key: MNG-870
> URL: http://jira.codehaus.org/browse/MNG-870
> Project: Maven 2
>  Issue Type: New Feature
>  Components: Plugins and Lifecycle
>Reporter: Kenney Westerhof
> Assigned To: Brett Porter
> Attachments: MNG-870.diff
>
>   Original Estimate: 1 hour
>  Time Spent: 1 hour
>  Remaining Estimate: 0 minutes
>
> If plugin discovery is reactor aware, plugins that are part of a reactor 
> build and are used to aid the build
> can be used in one go. Else first the plugin should be installed, and then 
> the rest of the project can
> be built.
> But mainly this aids in integration testing for plugins: the maven-it-plugin 
> in sandbox can't add the current plugin
> + artifact to the lifecycle without making some methods public. If the plugin 
> were to be discovered using the reactor,
> those methods can remain private.

-- 
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-2620) Guide to Building Maven 2.0 needs to be updated to reflect the real process

[Wendy Smoak (JIRA)]

[ http://jira.codehaus.org/browse/MNG-2620?page=comments#action_80189 ] 

Wendy Smoak commented on MNG-2620:
--

I updated the 'building 2.0' instructions in r475127.  We still need to explain 
how to build 2.1, and we could link to the page about building plugins.

> Guide to Building Maven 2.0 needs to be updated to reflect the real process
> ---
>
> Key: MNG-2620
> URL: http://jira.codehaus.org/browse/MNG-2620
> Project: Maven 2
>  Issue Type: Improvement
>  Components: Documentation: Guides
>Affects Versions: 2.0.4
>Reporter: Aleksandr Tarutin
>
> Guide to Building Maven 2.0 
> (http://maven.apache.org/guides/development/guide-building-m2.html) does not 
> accurately reflect the process of building Maven 2.0. I was able to get the 
> correct instructions from IRC. There are discrepancies between these 
> instructions and the ones given in the Guide.

-- 
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: (WAGON-60) wagon-webdav fails with commons-logging classloader issues

[Ivan S. Dubrov (JIRA)]

[ http://jira.codehaus.org/browse/WAGON-60?page=comments#action_80188 ] 

Ivan S. Dubrov commented on WAGON-60:
-

Simple workaround for whom still getting this error. You can SLF4J 
implementation of Commons Logging interface. Just put jcl104-over-slf4j.jar and 
slf4j-jdk14.jar (or any other SLF4J backend) from the 
http://www.slf4j.org/dist/slf4j-1.0.2.zip instead of commons-logging.jar into 
your maven lib directory.


> wagon-webdav fails with commons-logging classloader issues
> --
>
> Key: WAGON-60
> URL: http://jira.codehaus.org/browse/WAGON-60
> Project: wagon
>  Issue Type: Bug
>  Components: wagon-webdav
>Affects Versions: 1.0-beta-1
> Environment: maven 2.0.4
>Reporter: Yuri Schimke
> Assigned To: Carlos Sanchez
>Priority: Critical
>
> I tried it with a build extension and also putting jars in $M2_HOME/lib, but 
> both ways I get classloader issues with commons-logging.
> My project uses commons logging and I've seen at least one other report that 
> it can be a problem.
> with things in lib:
> Caused by: org.apache.commons.logging.LogConfigurationException: 
> org.apache.commons.logging.LogConfigurationException: 
> org.apache.commons.logging.LogConfigurationException: Invalid class loader 
> hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by 
> org.apache.commons.logging.LogConfigurationException: Invalid class loader 
> hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed.) (Caused by 
> org.apache.commons.logging.LogConfigurationException: 
> org.apache.commons.logging.LogConfigurationException: Invalid class loader 
> hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by 
> org.apache.commons.logging.LogConfigurationException: Invalid class loader 
> hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed.))
> at 
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
> at 
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
> at 
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
> at 
> org.apache.commons.httpclient.HttpClient.(HttpClient.java:69)
> ... 30 more
> Caused by: org.apache.commons.logging.LogConfigurationException: 
> org.apache.commons.logging.LogConfigurationException: Invalid class loader 
> hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by 
> org.apache.commons.logging.LogConfigurationException: Invalid class loader 
> hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed.)
> at 
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:397)
> at 
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
> ... 34 more
> Caused by: org.apache.commons.logging.LogConfigurationException: Invalid 
> class loader hierarchy.  You have more than one version of 
> 'org.apache.commons.logging.Log' visible, which is not allowed.
> at 
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:385)
> using build extension:
> java.lang.ExceptionInInitializerError
> at 
> org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:145)
> at 
> org.apache.webdav.lib.WebdavSession.getSessionInstance(WebdavSession.java:127)
> at 
> org.apache.webdav.lib.WebdavResource.setClient(WebdavResource.java:1273)
> at 
> org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1298)
> at 
> org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320)
> at 
> org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408)
> at 
> org.apache.webdav.lib.WebdavResource.(WebdavResource.java:290)
> at 
> org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.(CorrectedWebdavResource.java:52)
> at 
> org.apache.maven.wagon.providers.webdav.WebDavWagon.openConnection(WebDavWagon.java:139)
> at 
> org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
> at 
> org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
> at 
> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:132)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> a

[jira] Created: (MCLOVER-62) Compile errors when files are 'ed from intrumentation.

[Nick Pellow (JIRA)]

Compile errors when files are 'ed from intrumentation.
---

 Key: MCLOVER-62
 URL: http://jira.codehaus.org/browse/MCLOVER-62
 Project: Maven 2.x Clover Plugin
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Nick Pellow
 Attachments: beanutils-clover-out.txt

As far as I can tell, by looking at the source code, files that are excluded 
from 
instrumentation, are also excluded from being compiled.

This means, that if I exclude source code that is referenced by the unit tests, 
or indeed
other sources that aren't excluded, the compile will fail.

To observe this behaviour:

1)  Checkout the commons beanutils project from:
http://svn.apache.org/repos/asf/jakarta/commons/proper/beanutils/trunk

2) Add these lines to plugins element in the pom.xml

  org.apache.maven.plugins
  maven-clover-plugin
  

  **/locale/**

  


3) Run: mvn clean clover:instrument clover:clover
 
Attached is the output from maven when running the above recipe with the -X 
option.


-- 
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: (MPECLIPSE-126) Add support for wtp 1.0 and 1.5

[Arnaud Heritier (JIRA)]

Add support for wtp 1.0 and 1.5
---

 Key: MPECLIPSE-126
 URL: http://jira.codehaus.org/browse/MPECLIPSE-126
 Project: maven-eclipse-plugin
  Issue Type: Improvement
Affects Versions: 1.11
Reporter: Arnaud Heritier


Can't we reuse some code from the m2 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] Commented: (MRM-221) Webdav upload is not working

[Greg Luck (JIRA)]

[ http://jira.codehaus.org/browse/MRM-221?page=comments#action_80183 ] 

Greg Luck commented on MRM-221:
---

I created another new repository and retested. This time I could browse to it 
bu the webdav issue remains the same.

> Webdav upload is not working
> 
>
> Key: MRM-221
> URL: http://jira.codehaus.org/browse/MRM-221
> Project: Archiva
>  Issue Type: Bug
>Affects Versions: 1.0-beta-1, 1.0
> Environment: Mac OS X using the default jetty container. Jetty 
> started with mvn jetty:run
>Reporter: Greg Luck
>
> MRM-172 added webdav support. This is not working.
> I have everything working scping to the repository. webdav via Archiva does 
> not work.
> When I use 
> 
> 
> 
> 
>  
>  url="dav://localhost:9091/repository/maven_repository">
>  password="###"/>
> 
> 
> 
> I get 
> upload-to-repository:
> [artifact:install-provider] Installing provider: 
> org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-1
> [artifact:install-provider] Installing provider: 
> org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-1
> [artifact:install] [INFO] Installing 
> /Users/gluck/work/ehcache/trunk/target/dist/ehcache-1.2.4.jar to 
> /m2repository/net/sf/ehcache/ehcache/1.2.4/ehcache-1.2.4.jar
> [artifact:deploy] Deploying to 
> dav://localhost:9091/repository/maven_repository
> [artifact:deploy] WAGON_VERSION: 1.0-beta-1
> BUILD FAILED
> /Users/gluck/work/ehcache/trunk/build.xml:364: 
> java.lang.IllegalArgumentException: id is null
> If I click on the webdav link from archiva I get:
> Error 404 Not Found
> Resource in error: http://localhost:9091/repository/LOCAL/maven_repository
> Exception details:
> it.could.webdav.DAVException: Not found
>   at it.could.webdav.methods.HEAD.process(HEAD.java:52)
>   at it.could.webdav.methods.GET.process(GET.java:58)
>   at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79)
>   at 
> org.apache.maven.archiva.web.servlet.repository.RepositoryAccess.servletRequest(RepositoryAccess.java:223)
>   at 
> org.apache.maven.archiva.web.servlet.PlexusComponentServlet.service(PlexusComponentServlet.java:126)
>   at 
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
>   at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1049)
>   at 
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
>   at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
>   at 
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
>   at 
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
>   at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
>   at 
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
>   at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
>   at 
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:352)
>   at 
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:230)
>   at 
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
>   at 
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
>   at 
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
>   at 
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
>   at org.mortbay.jetty.Server.handle(Server.java:286)
>   at 
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:444)
>   at 
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:701)
>   at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)
>   at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203)
>   at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:340)
>   at 
> org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
>   at 
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)

-- 
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: (MRM-221) Webdav upload is not working

[Greg Luck (JIRA)]

Webdav upload is not working


 Key: MRM-221
 URL: http://jira.codehaus.org/browse/MRM-221
 Project: Archiva
  Issue Type: Bug
Affects Versions: 1.0-beta-1, 1.0
 Environment: Mac OS X using the default jetty container. Jetty started 
with mvn jetty:run
Reporter: Greg Luck


MRM-172 added webdav support. This is not working.

I have everything working scping to the repository. webdav via Archiva does not 
work.

When I use 







 






I get 

upload-to-repository:
[artifact:install-provider] Installing provider: 
org.apache.maven.wagon:wagon-webdav:jar:1.0-beta-1
[artifact:install-provider] Installing provider: 
org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-1
[artifact:install] [INFO] Installing 
/Users/gluck/work/ehcache/trunk/target/dist/ehcache-1.2.4.jar to 
/m2repository/net/sf/ehcache/ehcache/1.2.4/ehcache-1.2.4.jar
[artifact:deploy] Deploying to dav://localhost:9091/repository/maven_repository
[artifact:deploy] WAGON_VERSION: 1.0-beta-1

BUILD FAILED
/Users/gluck/work/ehcache/trunk/build.xml:364: 
java.lang.IllegalArgumentException: id is null

If I click on the webdav link from archiva I get:

Error 404 Not Found

Resource in error: http://localhost:9091/repository/LOCAL/maven_repository

Exception details:

it.could.webdav.DAVException: Not found
at it.could.webdav.methods.HEAD.process(HEAD.java:52)
at it.could.webdav.methods.GET.process(GET.java:58)
at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79)
at 
org.apache.maven.archiva.web.servlet.repository.RepositoryAccess.servletRequest(RepositoryAccess.java:223)
at 
org.apache.maven.archiva.web.servlet.PlexusComponentServlet.service(PlexusComponentServlet.java:126)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:445)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1049)
at 
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
at 
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
at 
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
at 
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1040)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:352)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:230)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:286)
at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:444)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:701)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:340)
at 
org.mortbay.jetty.nio.HttpChannelEndPoint.run(HttpChannelEndPoint.java:270)
at 
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)


-- 
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: (WAGONFTP-7) site:deploy (deploying with FTP) Wagon protocol 'ftp' doesn't support directory copying

[Bose Daggubati (JIRA)]

[ http://jira.codehaus.org/browse/WAGONFTP-7?page=comments#action_80180 ] 

Bose Daggubati commented on WAGONFTP-7:
---

Is some one working on this issue, Looks like its not yet assigned.
I am trying to deplot the Site, looks like it wants to do a directory FTP and 
it throws this error.

[INFO] [site:deploy]
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Wagon protocol 'ftp' doesn't support directory copying

> site:deploy (deploying with FTP)  Wagon protocol 'ftp' doesn't support 
> directory copying
> 
>
> Key: WAGONFTP-7
> URL: http://jira.codehaus.org/browse/WAGONFTP-7
> Project: wagon-ftp
>  Issue Type: Improvement
>Affects Versions: 1.0-alpha-4
> Environment: windows
>Reporter: pinghe
>
> Wagon protocol 'ftp' doesn't support directory copying

-- 
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: (MIDEA-60) Keep attached sources when replacing libraries in module

[Dennis Lundberg (JIRA)]

 [ http://jira.codehaus.org/browse/MIDEA-60?page=all ]

Dennis Lundberg closed MIDEA-60.


Resolution: Cannot Reproduce

> Keep attached sources when replacing libraries in module
> 
>
> Key: MIDEA-60
> URL: http://jira.codehaus.org/browse/MIDEA-60
> Project: Maven 2.x Idea Plugin
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: David Hay
> Attachments: ideatest-after-module-rebuild.jar, ideatest-log.txt, 
> ideatest-with-source.jar
>
>
> Many times, the dependencies downloaded by Maven do not have corresponding 
> source jars.  So I download the source separately and attach it to the 
> dependencies in my module.  However, if I regenerate the module, those source 
> attachments are lost.
> I'd like to see the Idea plugin (perhaps optionally) keep any source or 
> javadoc attachments that have been made.

-- 
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: (MJAR-57) Specification and Implementation details missing from manifest

[Dennis Lundberg (JIRA)]

[ http://jira.codehaus.org/browse/MJAR-57?page=comments#action_80179 ] 

Dennis Lundberg commented on MJAR-57:
-

I have updated the documentation with everything, except for the reasons why 
the change was made.

> Specification and Implementation details missing from manifest
> --
>
> Key: MJAR-57
> URL: http://jira.codehaus.org/browse/MJAR-57
> Project: Maven 2.x Jar Plugin
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Wendy Smoak
>
> The manifest customization page claims that Specification and Implementation 
> details will be included in the jar file manifest by default:
>
> http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html
> This does not happen, the default manifest contains only
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> Created-By: Apache Maven
> Built-By: wsmoak
> Build-Jdk: 1.5.0_05
> On the user list, the following configuration was suggested, but it does not 
> produce any additional entries in the manifest.
>   
> 
>   true
>   true
> 
>   

-- 
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: (MIDEA-72) -DdownloadSources=true only works if sources do not already exist in local repository

[Dennis Lundberg (JIRA)]

 [ http://jira.codehaus.org/browse/MIDEA-72?page=all ]

Dennis Lundberg closed MIDEA-72.


Resolution: Cannot Reproduce

> -DdownloadSources=true only works if sources do not already exist in local 
> repository
> -
>
> Key: MIDEA-72
> URL: http://jira.codehaus.org/browse/MIDEA-72
> Project: Maven 2.x Idea Plugin
>  Issue Type: Bug
> Environment: Clean install of Maven 2.04.
>Reporter: Rob Butler
>
> Running mvn idea:idea -DdownloadSources=true will add source jars to idea 
> project file if the source jars are downloaded (not in local repository).  If 
> the project files are deleted and the command run again the sources will not 
> be added to the project files because they already exist in the local 
> repository and are not downloaded.

-- 
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: (MSITE-192) Docs don't indicate where site.xml should be created

[Dennis Lundberg (JIRA)]

 [ http://jira.codehaus.org/browse/MSITE-192?page=all ]

Dennis Lundberg closed MSITE-192.
-

 Assignee: Dennis Lundberg
   Resolution: Fixed
Fix Version/s: 2.0

Fixed in SVN.

> Docs don't indicate where site.xml should be created
> 
>
> Key: MSITE-192
> URL: http://jira.codehaus.org/browse/MSITE-192
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-5
>Reporter: Graham Leggett
> Assigned To: Dennis Lundberg
>Priority: Minor
> Fix For: 2.0
>
>
> In the docs available at 
> http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html,
>  it says that a site descriptor can be created to modify the site generated.
> Nowhere in the docs does it say where in the project tree the site.xml file 
> must be created, nor does it say whether the location of this file can be 
> modified should the project layout be non standard.

-- 
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: (MJAVADOC-101) Embedded error: Error rendering Maven report

[Vincent Siveton (JIRA)]

[ http://jira.codehaus.org/browse/MJAVADOC-101?page=comments#action_80178 ] 

Vincent Siveton commented on MJAVADOC-101:
--

You used the maven-javadoc-plugin version 2.0. Could you try with 
maven-javadoc-plugin:2.1 ?
The option -U doesnt update plugins in reporting section so you need to call:
mvn -U javadoc:javadoc

Waiting for your comments.

> Embedded error: Error rendering Maven report
> 
>
> Key: MJAVADOC-101
> URL: http://jira.codehaus.org/browse/MJAVADOC-101
> Project: Maven 2.x Javadoc Plugin
>  Issue Type: Bug
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> 

[jira] Closed: (MDEP-49) Can't unpack multiple classifiers from same artifact; "already unpacked"

[Chris Hilton (JIRA)]

 [ http://jira.codehaus.org/browse/MDEP-49?page=all ]

Chris Hilton closed MDEP-49.


   Resolution: Fixed
Fix Version/s: 2.0-alpha-1

Already fixed in the new version.

> Can't unpack multiple classifiers from same artifact; "already unpacked"
> 
>
> Key: MDEP-49
> URL: http://jira.codehaus.org/browse/MDEP-49
> Project: Maven 2.x Dependency Plugin
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Chris Hilton
> Assigned To: Brian Fox
> Fix For: 2.0-alpha-1
>
>
> A plugin configuration like this does not work:
> 
> org.codehaus.mojo
> dependency-maven-plugin
> 
>   
> generate-resources-apphome
> generate-resources
> 
>   
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   someFiles
>   zip
>   target/dir1
> 
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   otherFiles
>   zip
>   target/dir2
> 
>   
> 
> 
>   unpack
> 
>   
> 
>   
> The otherFiles.zip file is never unpacked to dir2 and the conole output 
> states:
> [INFO] MyProject-5.0-SNAPSHOT-otherFiles.zip already unpacked.
> When actually it was the someFiles.zip that was already unpacked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MDEP-49) Can't unpack multiple classifiers from same artifact; "already unpacked"

[Chris Hilton (JIRA)]

[ http://jira.codehaus.org/browse/MDEP-49?page=comments#action_80174 ] 

Chris Hilton commented on MDEP-49:
--

I tried it with the new snapshot version and it did indeed work fine. Don't you 
love those kinds of bugs?

I also tried the overwrite flag and even the markerFile property found in the 
old documentation, but got the "no setters" error for them and, looking at the 
Javadoc, it does indicate that there are no setters for those properties in 
ArtifactItem. So I'll stick with the above workaround for now.

> Can't unpack multiple classifiers from same artifact; "already unpacked"
> 
>
> Key: MDEP-49
> URL: http://jira.codehaus.org/browse/MDEP-49
> Project: Maven 2.x Dependency Plugin
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Chris Hilton
> Assigned To: Brian Fox
>
> A plugin configuration like this does not work:
> 
> org.codehaus.mojo
> dependency-maven-plugin
> 
>   
> generate-resources-apphome
> generate-resources
> 
>   
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   someFiles
>   zip
>   target/dir1
> 
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   otherFiles
>   zip
>   target/dir2
> 
>   
> 
> 
>   unpack
> 
>   
> 
>   
> The otherFiles.zip file is never unpacked to dir2 and the conole output 
> states:
> [INFO] MyProject-5.0-SNAPSHOT-otherFiles.zip already unpacked.
> When actually it was the someFiles.zip that was already unpacked.

-- 
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] Moved: (MJAVADOC-101) Embedded error: Error rendering Maven report

[Dennis Lundberg (JIRA)]

 [ http://jira.codehaus.org/browse/MJAVADOC-101?page=all ]

Dennis Lundberg moved MSITE-193 to MJAVADOC-101:


Affects Version/s: (was: 2.0-beta-4)
  Key: MJAVADOC-101  (was: MSITE-193)
  Project: Maven 2.x Javadoc Plugin  (was: Maven 2.x Site Plugin)

> Embedded error: Error rendering Maven report
> 
>
> Key: MJAVADOC-101
> URL: http://jira.codehaus.org/browse/MJAVADOC-101
> Project: Maven 2.x Javadoc Plugin
>  Issue Type: Bug
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/mai

[jira] Commented: (MSITE-193) Embedded error: Error rendering Maven report

[Dennis Lundberg (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-193?page=comments#action_80173 ] 

Dennis Lundberg commented on MSITE-193:
---

You just need to remove "maven-javadoc-plugin" from the "reports" section of 
your pom.

> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> a

[jira] Commented: (MSITE-193) Embedded error: Error rendering Maven report

[Bose Daggubati (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-193?page=comments#action_80172 ] 

Bose Daggubati commented on MSITE-193:
--

You may please fwd this to javadoc team.

How can i run this site command excluding this javadoc generation

> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/rande

[jira] Commented: (MSITE-193) Embedded error: Error rendering Maven report

[Dennis Lundberg (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-193?page=comments#action_80171 ] 

Dennis Lundberg commented on MSITE-193:
---

I've had a look at your log-file and it seems that your problem occurs when the 
javadocs are generated. See the snippet below.
I suggest that we move this issue to the maven-javadoc-plugin instead. Do you 
agree?

{code}
[DEBUG] Generating 
C:\ExpressContact\StandAlone\RandomizationEngine\target\site\apidocs\index.html
[INFO] Generate "JavaDocs" report.
[DEBUG] Javadoc executable=[C:\j2sdk1.4.2_10\jre\..\bin\javadoc.exe]
[DEBUG] C:\j2sdk1.4.2_10\jre\..\bin\javadoc.exe @options @files
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/App.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/dao/CaseUnitDao.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/dao/jdbc/JdbcBaseTemplateDao.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/dao/jdbc/JdbcCaseUnitDao.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/dao/jdbc/JdbcRandomizerDao.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/dao/RandomizerDao.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Arm.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/CaseType.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/CaseUnit.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/RandomizationMethod.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Study.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/RandomizeEngine.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/service/BaseCaseUnitRandomizer.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/service/CaseUnitRandomizer.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/service/ClientCaseUnitRandomizer.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/service/MemberCaseUnitRandomizer.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/service/RandomizerFactory.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/service/RandomizerFactoryImpl.java...
Loading source file 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/Startup.java...
2 errors
1 warning
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error during page generation

Embedded error: Error rendering Maven report: Exit code: 1 - 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
^
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 not a statement
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
^
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 ';' expected
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
   ^
{code}

> Embedded error: Error rendering Maven report
> 
>
> 

[jira] Updated: (MRELEASE-175) Svn commit fails due to large number of poms on windows

[Dan Tran (JIRA)]

 [ http://jira.codehaus.org/browse/MRELEASE-175?page=all ]

Dan Tran updated MRELEASE-175:
--

Affects Version/s: (was: 2.0-beta-5)
   2.0-beta-4
Fix Version/s: 2.0-beta-5

> Svn commit fails due to large number of poms on windows
> ---
>
> Key: MRELEASE-175
> URL: http://jira.codehaus.org/browse/MRELEASE-175
> Project: Maven 2.x Release Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: windows
>Reporter: Dan Tran
> Fix For: 2.0-beta-5
>
>
> I have so many projects under one source tree that release:prepare fails when 
> trying to commit the 
> changed pom files ( ie svn command is too long)
> Can we just issue "svn commit" ?  This problem hits all scm types on windows 
> platform

-- 
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-175) Svn commit fails due to large number of poms on windows

[Dan Tran (JIRA)]

Svn commit fails due to large number of poms on windows
---

 Key: MRELEASE-175
 URL: http://jira.codehaus.org/browse/MRELEASE-175
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
Affects Versions: 2.0-beta-5
 Environment: windows
Reporter: Dan Tran
 Fix For: 2.0-beta-5


I have so many projects under one source tree that release:prepare fails when 
trying to commit the 
changed pom files ( ie svn command is too long)

Can we just issue "svn commit" ?  This problem hits all scm types on windows 
platform





-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MSITE-193) Embedded error: Error rendering Maven report

[Bose Daggubati (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-193?page=comments#action_80168 ] 

Bose Daggubati commented on MSITE-193:
--

where ever java command is executed behind the scenes by Maven 

Should Maven use the -ae option as mentioned .

To enable assertions, use the switch -enableassertion (or -ea).



> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/Stan

[jira] Commented: (MSITE-193) Embedded error: Error rendering Maven report

[Bose Daggubati (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-193?page=comments#action_80167 ] 

Bose Daggubati commented on MSITE-193:
--

I am using the maven-site-plugin:maven-plugin:2.0-beta-5
Attached is the log and POM's Used.


> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Clie

[jira] Updated: (MSITE-193) Embedded error: Error rendering Maven report

[Bose Daggubati (JIRA)]

 [ http://jira.codehaus.org/browse/MSITE-193?page=all ]

Bose Daggubati updated MSITE-193:
-

Attachment: pom.xml
pom.xml

parent POM , and module POM attached

> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (pla

[jira] Updated: (MSITE-193) Embedded error: Error rendering Maven report

[Bose Daggubati (JIRA)]

 [ http://jira.codehaus.org/browse/MSITE-193?page=all ]

Bose Daggubati updated MSITE-193:
-

Attachment: Maven Site issue.txt

This file has the log 

Command run was compile and site

> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
> Attachments: Maven Site issue.txt, pom.xml, pom.xml
>
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> as

[jira] Created: (MAVENUPLOAD-1234) Please upload EZMorph-0.9

[Andres Almiray (JIRA)]

Please upload EZMorph-0.9
-

 Key: MAVENUPLOAD-1234
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1234
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Andres Almiray


EZMorph is simple java library for transforming an Object to another Object.

Bundle was created by hand according to spec.
The pom includes a PluginRepositories definition for the FindBugs plugin at 
codehaus.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MDEP-49) Can't unpack multiple classifiers from same artifact; "already unpacked"

[Brian Fox (JIRA)]

[ http://jira.codehaus.org/browse/MDEP-49?page=comments#action_80160 ] 

Brian Fox commented on MDEP-49:
---

btw, you should also be able to specify the overWrite flag to force the 
unpacking instead of adding a second execution.

> Can't unpack multiple classifiers from same artifact; "already unpacked"
> 
>
> Key: MDEP-49
> URL: http://jira.codehaus.org/browse/MDEP-49
> Project: Maven 2.x Dependency Plugin
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Chris Hilton
> Assigned To: Brian Fox
>
> A plugin configuration like this does not work:
> 
> org.codehaus.mojo
> dependency-maven-plugin
> 
>   
> generate-resources-apphome
> generate-resources
> 
>   
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   someFiles
>   zip
>   target/dir1
> 
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   otherFiles
>   zip
>   target/dir2
> 
>   
> 
> 
>   unpack
> 
>   
> 
>   
> The otherFiles.zip file is never unpacked to dir2 and the conole output 
> states:
> [INFO] MyProject-5.0-SNAPSHOT-otherFiles.zip already unpacked.
> When actually it was the someFiles.zip that was already unpacked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MSITE-193) Embedded error: Error rendering Maven report

[Dennis Lundberg (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-193?page=comments#action_80158 ] 

Dennis Lundberg commented on MSITE-193:
---

We need more information to be able to track down the cause of this:
- What command did you issue when the error occured?
- What does your pom.xml look like?
- 2.0-beta-5 of the plugin has been out for quite a while. Could you please 
test with that version and see if the error is still there.

> Embedded error: Error rendering Maven report
> 
>
> Key: MSITE-193
> URL: http://jira.codehaus.org/browse/MSITE-193
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
> Environment: XP
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>Reporter: Bose Daggubati
>
> 2 errors
> 1 warning
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  warning: as of release 1.4, assert
> is a keyword, and may not be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  not a statement
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
> ^
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
>  ';' expected
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
>^
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
> generation
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
> rendering Maven report: Exit code: 1 - 
> C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
> lient.java:21: warning: as of release 1.4, assert is a keyword, and may not 
> be used as an identifier
> assert (planTypeId == null) || (bplId == null) : "A Client (from a 
> Randomization Standpoint) should not have both a PLAN

[jira] Commented: (MDEP-49) Can't unpack multiple classifiers from same artifact; "already unpacked"

[Brian Fox (JIRA)]

[ http://jira.codehaus.org/browse/MDEP-49?page=comments#action_80159 ] 

Brian Fox commented on MDEP-49:
---

Can you try this with 
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-1-snapshot? The code 
has been refactored and I believe the marker now uses the classifer too.

> Can't unpack multiple classifiers from same artifact; "already unpacked"
> 
>
> Key: MDEP-49
> URL: http://jira.codehaus.org/browse/MDEP-49
> Project: Maven 2.x Dependency Plugin
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Chris Hilton
> Assigned To: Brian Fox
>
> A plugin configuration like this does not work:
> 
> org.codehaus.mojo
> dependency-maven-plugin
> 
>   
> generate-resources-apphome
> generate-resources
> 
>   
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   someFiles
>   zip
>   target/dir1
> 
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   otherFiles
>   zip
>   target/dir2
> 
>   
> 
> 
>   unpack
> 
>   
> 
>   
> The otherFiles.zip file is never unpacked to dir2 and the conole output 
> states:
> [INFO] MyProject-5.0-SNAPSHOT-otherFiles.zip already unpacked.
> When actually it was the someFiles.zip that was already unpacked.

-- 
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: (MSITE-193) Embedded error: Error rendering Maven report

[Bose Daggubati (JIRA)]

Embedded error: Error rendering Maven report


 Key: MSITE-193
 URL: http://jira.codehaus.org/browse/MSITE-193
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Affects Versions: 2.0-beta-4
 Environment: XP
java version "1.4.2_10"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
Reporter: Bose Daggubati


2 errors
1 warning
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error during page generation

Embedded error: Error rendering Maven report: Exit code: 1 - 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 warning: as of release 1.4, assert
is a keyword, and may not be used as an identifier
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
^
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 not a statement
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
^
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 ';' expected
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
   ^

[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page 
generation
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page 
generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error 
rendering Maven report: Exit code: 1 - 
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/C
lient.java:21: warning: as of release 1.4, assert is a keyword, and may not be 
used as an identifier
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
^
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 not a statement
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
^
C:/ExpressContact/StandAlone/RandomizationEngine/src/main/java/com/express_scripts/imms/randeng/domain/Client.java:21:
 ';' expected
assert (planTypeId == null) || (bplId == null) : "A Client (from a 
Randomization Standpoint) should not have both a PLAN TYPE ID and BPL ID";
 

[jira] Commented: (MDEP-49) Can't unpack multiple classifiers from same artifact; "already unpacked"

[Chris Hilton (JIRA)]

[ http://jira.codehaus.org/browse/MDEP-49?page=comments#action_80157 ] 

Chris Hilton commented on MDEP-49:
--

Priority should be reduced to minor as I've found the following workaround. 
Specify the second artifact in a separate execution element and add the 
 element to the second configuration that points to a 
different directory (i.e. not target\maven-dependency-plugin-markers).


> Can't unpack multiple classifiers from same artifact; "already unpacked"
> 
>
> Key: MDEP-49
> URL: http://jira.codehaus.org/browse/MDEP-49
> Project: Maven 2.x Dependency Plugin
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Chris Hilton
> Assigned To: Brian Fox
>
> A plugin configuration like this does not work:
> 
> org.codehaus.mojo
> dependency-maven-plugin
> 
>   
> generate-resources-apphome
> generate-resources
> 
>   
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   someFiles
>   zip
>   target/dir1
> 
> 
>   com.example
>   MyProject
>   5.0-SNAPSHOT
>   otherFiles
>   zip
>   target/dir2
> 
>   
> 
> 
>   unpack
> 
>   
> 
>   
> The otherFiles.zip file is never unpacked to dir2 and the conole output 
> states:
> [INFO] MyProject-5.0-SNAPSHOT-otherFiles.zip already unpacked.
> When actually it was the someFiles.zip that was already unpacked.

-- 
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-232) Build when a dependency has been changed/updated

[Emmanuel Venisse (JIRA)]

[ http://jira.codehaus.org/browse/CONTINUUM-232?page=comments#action_80155 
] 

Emmanuel Venisse commented on CONTINUUM-232:


Done, but only for dependencies that are Continuum projects.
I'll do jsp modifications tomorrow

> Build when a dependency has been changed/updated
> 
>
> Key: CONTINUUM-232
> URL: http://jira.codehaus.org/browse/CONTINUUM-232
> Project: Continuum
>  Issue Type: New Feature
>  Components: Core system
>Reporter: Trygve Laugstol
> Assigned To: 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] Created: (MDEP-49) Can't unpack multiple classifiers from same artifact; "already unpacked"

[Chris Hilton (JIRA)]

Can't unpack multiple classifiers from same artifact; "already unpacked"


 Key: MDEP-49
 URL: http://jira.codehaus.org/browse/MDEP-49
 Project: Maven 2.x Dependency Plugin
  Issue Type: Bug
Affects Versions: 1.0
Reporter: Chris Hilton
 Assigned To: Brian Fox


A plugin configuration like this does not work:


org.codehaus.mojo
dependency-maven-plugin

  
generate-resources-apphome
generate-resources

  

  com.example
  MyProject
  5.0-SNAPSHOT
  someFiles
  zip
  target/dir1


  com.example
  MyProject
  5.0-SNAPSHOT
  otherFiles
  zip
  target/dir2

  


  unpack

  

  

The otherFiles.zip file is never unpacked to dir2 and the conole output states:

[INFO] MyProject-5.0-SNAPSHOT-otherFiles.zip already unpacked.

When actually it was the someFiles.zip that was already unpacked.

-- 
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: (MEV-459) Velocity should not depend on Velocity-dep

[Henri Yandell (JIRA)]

[ http://jira.codehaus.org/browse/MEV-459?page=comments#action_80147 ] 

Henri Yandell commented on MEV-459:
---

If this was a pom badly generated by the Maven team (or someone other than the 
Velocity committers); shouldn't the existing pom get fixed?

> Velocity should not depend on Velocity-dep
> --
>
> Key: MEV-459
> URL: http://jira.codehaus.org/browse/MEV-459
> Project: Maven Evangelism
>  Issue Type: Bug
>  Components: Dependencies
>Reporter: Vincent Massol
>
> If a project is using ORO in version 2.0.8 then velocity-dep clashes with it 
> as it includes ORO with the original package name (a really really bad 
> practice). 
> For information, the problem arises for example with 
> Perl5Substitution.appendSubstitution(java.lang.StringBuffer stringBuffer, 
> org.apache.oro.text.regex.MatchResult matchResult, int i, java.lang.String 
> string, org.apache.oro.text.regex.PatternMatcher patternMatcher, 
> org.apache.oro.text.regex.Pattern pattern) which is valid in ORO 2.0.8 but 
> not in the version inside velocity-dep.
> This problem should be raised against the Velocity project as it should not 
> be allowed to internally include another external package.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONTINUUM-963) Derby Database initialization error on Webapp restarts on Jetty

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-963?page=all ]

Jesse McConnell updated CONTINUUM-963:
--

Component/s: Database

> Derby Database initialization error on Webapp restarts on Jetty 
> 
>
> Key: CONTINUUM-963
> URL: http://jira.codehaus.org/browse/CONTINUUM-963
> Project: Continuum
>  Issue Type: Bug
>  Components: Database
>Reporter: Rahul Thakur
> Assigned To: Jesse McConnell
> Fix For: 1.1
>
> Attachments: CONTINUUM-963.patch
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONTINUUM-36) Automatic issue creation for cronically failing tests

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-36?page=all ]

Jesse McConnell updated CONTINUUM-36:
-

Component/s: Core system

> Automatic issue creation for cronically failing tests
> -
>
> Key: CONTINUUM-36
> URL: http://jira.codehaus.org/browse/CONTINUUM-36
> Project: Continuum
>  Issue Type: Wish
>  Components: Core system
>Reporter: David Blevins
>Priority: Trivial
>
> If a unit test fails several builds in a row, automatically create an issue 
> in the project's issue tracker.
> Extra: If a person views the build details, there should be a link to the 
> issue so that people can see if it is being worked on or what the status may 
> be.

-- 
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-2657) Generics - Compilation failure - incompatible types - cast to parent type from method taking in subtype.

[Kenny MacDermid (JIRA)]

[ http://jira.codehaus.org/browse/MNG-2657?page=comments#action_80129 ] 

Kenny MacDermid commented on MNG-2657:
--

Actually it appears that this is a difference between eclipse's compiler, and 
sun's. I plan to investigate further, but now believe it it not a bug in maven.

Thank you,

Kenny

> Generics - Compilation failure - incompatible types - cast to parent type 
> from method taking in subtype.
> 
>
> Key: MNG-2657
> URL: http://jira.codehaus.org/browse/MNG-2657
> Project: Maven 2
>  Issue Type: Bug
>Affects Versions: 2.0.4
> Environment: Windows Xp and Ubuntu Linux. Standard x86 hardware.
>Reporter: Kenny MacDermid
>
> Maven will not compile classes in the following situation, although eclipse 
> will compile them fine:
> These are the two classes that are the types maven is getting confused with:
> public abstract class User {...}
> public class Employee extends User {...}
> A factory called EntityManager returns a generic typed Criteria:
> public  Criteria createCriteria(Class c) {
> return new CriteriaImpl(c);
> }
> This is being used in the Tests in the following way:
> Criteria criteria = em.createCriteria(Employee.class);
> As I said, in eclipse this compiles fine, with no warnings. With maven I 
> receive the error message:
> [INFO] Compilation failure
> ...UserTest.java:[59,51] incompatible types
> found   : Criteria
> required: Criteria
> The stack trace is as follows:
> org.apache.maven.BuildFailureException: Compilation failure
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation 
> failure
> at 
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
> at 
> org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:99)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Other possible useful maven information (actualy dir replaced with DIR):
> [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:testCompile' -->
> [DEBUG]   (f) basedir = DIR
> [DEBUG]   (f) buildDirectory = DIR\target
> [DEBUG]   (f) classpathElements = [DIR\target\classes, 
> DIR\target\test-classes, ... (many others)]
> [DEBUG]   (f) compileSourceRoots = [DIR\src\test\java]
> [DEBUG]   (f) compilerId = javac
> [DEBUG]   (f) debug = true
> [DEBUG]   (f) fork = false
> [DEBUG]   (f) optimize = false
> [DEBUG]   (f) outputDirectory = DIR\target\test-classes
> [DEBUG]   (f) outputFileName = IdentityRepository-0.1
> [DEBUG]   (f) showDeprecation = false
> [DEBUG]   (f) showWarnings = false
> [DEBUG]   (f) source = 1.5
> [DEBUG]   (f) staleMillis = 0
> [DEBUG]   (f) target = 1.5
> [DEBUG]   (f) verbose = false
> [DEBUG] -- end configuration --
> Thanks in advance,
> Kenny

-- 
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: ht

[jira] Updated: (CONTINUUM-34) Keep trying till build works, notify via email what is required

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-34?page=all ]

Jesse McConnell updated CONTINUUM-34:
-

Component/s: Core system

> Keep trying till build works, notify via email what is required
> ---
>
> Key: CONTINUUM-34
> URL: http://jira.codehaus.org/browse/CONTINUUM-34
> Project: Continuum
>  Issue Type: Wish
>  Components: Core system
>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-820) Shell script execution rights under Linux

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-820?page=all ]

Jesse McConnell updated CONTINUUM-820:
--

Component/s: Integration - Shell

> Shell script execution rights under Linux
> -
>
> Key: CONTINUUM-820
> URL: http://jira.codehaus.org/browse/CONTINUUM-820
> Project: Continuum
>  Issue Type: Bug
>  Components: Integration - Shell
>Affects Versions: 1.0.3
> Environment: Linux
>Reporter: Nicolas Cazottes
>
> When adding a new shell script project, in continuum, the build does not work 
> because of missing execution rights on the checkouted resources.
> The cause of the problem is that by default, a checkout with svn does not set 
> the execution rights.
> Continuum should change the execution flag of the script to be executed.

-- 
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

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-501?page=all ]

Jesse McConnell updated CONTINUUM-501:
--

Component/s: Project Grouping

> 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
>  Issue Type: Improvement
>  Components: Project Grouping
>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-143) We need to categorize error states and display them useful messages to the user

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-143?page=all ]

Jesse McConnell updated CONTINUUM-143:
--

Component/s: Core system

> We need to categorize error states and display them useful messages to the 
> user
> ---
>
> Key: CONTINUUM-143
> URL: http://jira.codehaus.org/browse/CONTINUUM-143
> Project: Continuum
>  Issue Type: Improvement
>  Components: Core system
>Affects Versions: 1.0-alpha-3
>Reporter: Jason van Zyl
> Fix For: 1.1
>
>
> Right now we're only tracking checkout errors but we need to categorize all 
> error so that we can easily extract them and display useful messages to the 
> user.

-- 
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-447) Remove Project Exception

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-447?page=all ]

Jesse McConnell updated CONTINUUM-447:
--

Component/s: Core system

> Remove Project Exception
> 
>
> Key: CONTINUUM-447
> URL: http://jira.codehaus.org/browse/CONTINUUM-447
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.0.1
> Environment: Windows 2000 sp4 OS, 1GB of RAM, 1.70 GHz CPU
>Reporter: Michael Fiedler
>Priority: Minor
> Fix For: 1.1
>
>
> I created build projects for each subproject.  Once I correctly added the 
> higher level POM (containing all of the sub projects), I wanted to delete 
> each of the sub projects that I had added.  I started to delete them from the 
> build machine (which is running Continuum).  To do it quicker, I also started 
> to delete them from my machine.  While deleting one of them, I received the 
> following stacktrace:
> ognl.MethodFailedException: Method "removeProject" failed for object [EMAIL 
> PROTECTED] [org.apache.maven.continuum.ContinuumException: No such object.]
>   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 \
> org.apache.maven.continuum.ContinuumException: No such object.
>   at 
> org.apache.maven.continuum.DefaultContinuum.logAndCreateException(DefaultContinuum.java:1729)
>   at 
> org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinuum.java:210)
>   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:585)
>   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.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)
>   

[jira] Updated: (CONTINUUM-932) Admin Connection to embedded derby database

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-932?page=all ]

Jesse McConnell updated CONTINUUM-932:
--

Component/s: Database

> Admin Connection to embedded derby database
> ---
>
> Key: CONTINUUM-932
> URL: http://jira.codehaus.org/browse/CONTINUUM-932
> Project: Continuum
>  Issue Type: New Feature
>  Components: Database
>Reporter: Michael Locher
>Priority: Minor
> Attachments: embeddedDerby.xml
>
>
> Please include an ant projectfile which can be invoked to get an ij Session 
> on the embedded Derby database.
> This is usefull if the database is corrupt and the admin needs to issue some 
> sql statements.
> e.g The file could be located in the bin directory and be named as 
> 'embeddedDerby.xml'
> the admin would attach to the database with the following command: 'ant -f 
> embeddedDerby.xml'

-- 
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

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-581?page=all ]

Jesse McConnell updated CONTINUUM-581:
--

Component/s: Core system

> Share continuum build number to underlying build project
> 
>
> Key: CONTINUUM-581
> URL: http://jira.codehaus.org/browse/CONTINUUM-581
> Project: Continuum
>  Issue Type: New Feature
>  Components: Core system
>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-723) strange trouble on solaris

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-723?page=all ]

Jesse McConnell updated CONTINUUM-723:
--

Component/s: Environmental

> strange trouble on solaris 
> ---
>
> Key: CONTINUUM-723
> URL: http://jira.codehaus.org/browse/CONTINUUM-723
> Project: Continuum
>  Issue Type: Bug
>  Components: Environmental
>Affects 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-440) Failed to start continuum on 64bit Linux

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-440?page=all ]

Jesse McConnell updated CONTINUUM-440:
--

Component/s: Environmental

> Failed to start continuum on 64bit Linux
> 
>
> Key: CONTINUUM-440
> URL: http://jira.codehaus.org/browse/CONTINUUM-440
> Project: Continuum
>  Issue Type: Bug
>  Components: Environmental
>Affects 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-145) Allow the creation of template project configurations

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-145?page=all ]

Jesse McConnell updated CONTINUUM-145:
--

Component/s: Core - Profiles

> Allow the creation of template project configurations
> -
>
> Key: CONTINUUM-145
> URL: http://jira.codehaus.org/browse/CONTINUUM-145
> Project: Continuum
>  Issue Type: New Feature
>  Components: Core - Profiles
>Reporter: Jason van Zyl
>
> For a given project type, say m2, allow the user the define template values 
> that will be used when new projects of that type are created.

-- 
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

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-575?page=all ]

Jesse McConnell updated CONTINUUM-575:
--

Component/s: Web - UI

> Version number doesn't update on projects screen
> 
>
> Key: CONTINUUM-575
> URL: http://jira.codehaus.org/browse/CONTINUUM-575
> Project: Continuum
>  Issue Type: Bug
>  Components: Web - UI
>Affects 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-278) associate project developers with continuum users

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-278?page=all ]

Jesse McConnell updated CONTINUUM-278:
--

Component/s: Web - Configuration

> associate project developers with continuum users
> -
>
> Key: CONTINUUM-278
> URL: http://jira.codehaus.org/browse/CONTINUUM-278
> Project: Continuum
>  Issue Type: Sub-task
>  Components: Web - Configuration
>Reporter: Brett Porter
> 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] Updated: (CONTINUUM-971) Symbolic links are traversed on deletion

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-971?page=all ]

Jesse McConnell updated CONTINUUM-971:
--

Fix Version/s: 1.1
  Component/s: Environmental

> Symbolic links are traversed on deletion
> 
>
> Key: CONTINUUM-971
> URL: http://jira.codehaus.org/browse/CONTINUUM-971
> Project: Continuum
>  Issue Type: Bug
>  Components: Environmental
>Affects Versions: 1.0.3
> Environment: Reproduced on Redhat Enterprise 4 but applicable to all 
> forms of UNIX
>Reporter: Uri Moszkowicz
>Priority: Critical
> Fix For: 1.1
>
>
> To reproduce:
> 1. Create a project that checks out files from some SCM
> 2. Create a build script that creates symbolic links outside of the checked 
> out project sandbox. This is often done to bring outside libraries into the 
> project.
> 3. Delete the created project from the Continuum website. Notice how all 
> kinds of files disappear from your file system!
> From looking at the release logs it looks like someone added follow symbolic 
> links as the default and mentioned that at some point in the future an option 
> should be added to disable this behavior. Following symbolic links is very 
> dangerous and if supported it should be disabled by default, not the reverse. 
> A warning should be posted in a visible place for the existing versions until 
> this can be fixed as it can result in significant data loss outside of the 
> Continuum program.

-- 
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-935) Conflict between manageUsers and admin roles

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-935?page=all ]

Jesse McConnell updated CONTINUUM-935:
--

Component/s: Web - Security

while this is indicated on the acegi-branch its something that should to 
checked that it is covered to a large enough degree by the plexus-security 
integration

> Conflict between manageUsers and admin roles
> 
>
> Key: CONTINUUM-935
> URL: http://jira.codehaus.org/browse/CONTINUUM-935
> Project: Continuum
>  Issue Type: Bug
>  Components: Web - Security
>Affects Versions: 1.1
> Environment: acegi branch
>Reporter: Carlos Sanchez
> Assigned To: Lester Ecarma
>Priority: Critical
>
> An user with manageUsers role should not be able to assign the admin role to 
> anybody.
> The problem expands to any role, i think the solution should be implemented 
> in UserManager
> When getting the list of available groups for adding to an user it must not 
> return groups that have roles that the current user does not have. This must 
> be checked in the method that adds an user to a group too.
> When adding roles to an user group, only the roles of the current user can be 
> added, to avoid people adding roles to their groups.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MAVENUPLOAD-1233) Upload hibernate-entitymanager-3.2.0.cr2

[Johann Reyes (JIRA)]

Upload hibernate-entitymanager-3.2.0.cr2


 Key: MAVENUPLOAD-1233
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1233
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Johann Reyes


Pleas upload hibernate-entitymanager-3.2.0.cr2, needed dependency for 
hibernate3-maven-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] Created: (MAVENUPLOAD-1232) Upload backport-util-concurrent-3.0

[Taras Puchko (JIRA)]

Upload backport-util-concurrent-3.0
---

 Key: MAVENUPLOAD-1232
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1232
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Taras Puchko


http://fileanchor.com/78996-d

http://dcl.mathcs.emory.edu/util/backport-util-concurrent/ 

This package is the backport of java.util.concurrent API, introduced in Java 
5.0, to Java 1.4.

-- 
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-476) jdo model improvements

[Jesse McConnell (JIRA)]

[ http://jira.codehaus.org/browse/CONTINUUM-476?page=comments#action_80138 
] 

Jesse McConnell commented on CONTINUUM-476:
---

I would really like to set the store api cleared up in general with this.  Its 
frustrating to try and balance all of the 'do I have build definitions in the 
project instance I just asked for?'

joakim and I ended up working out some really nice conventions for accessing 
objects and dealing with things in the plexus-security store in terms of save* 
and get* operations.  I think we could really go a long ways towards making 
continuum more maintainable if we were able to just bite the bullet and 
refactor the store api and the underlying jdo store.  programming against the 
current api just feels really hit or miss.

> jdo model improvements
> --
>
> Key: CONTINUUM-476
> URL: http://jira.codehaus.org/browse/CONTINUUM-476
> Project: Continuum
>  Issue Type: Improvement
>  Components: Core system, Database
>Reporter: Brett Porter
> Fix For: 1.1
>
>
> some notes I sent to the dev list earlier in the year
> There are  afew areas I'm still not happy with. The fetch groups don't
> seem to fit well with what is required a lot of the time. I'm wondering
> whether we are better off making everything be in the default fetch
> group, and lazy loading the lists instead. It seems since we are only
> doing this as an optimization that'd be a better way to do it.
> We'd still need to avoid long lists, ie build results. I think that
> should not be a field on the project, and instead it should just have
> references to the last successful build, last finished build, current
> build (either in progress or finished).
> I'm not particularly happy with using store methods "mid-way" through a
> block of code. I'm not sure if it does any dirty checking when you do a
> re-attach,but I see potential to read something, have it changed
> externally, then write over the top of it. The fact that we are
> re-retrieving from the db at random points could make this harder to
> track. I think we should be in the practise of getting all we need from
> the db at the start, modifying the detached objects, then updating them
> with dirty check at the end. We need to be able to resolve common cases
> where we can recover, and fail gracefully when it can't. At the end of
> the day, this isn't preventing it working now, so I'll just schedule a
> review of the use of the store later as it may be a source of ongoing
> bugs otherwise.

-- 
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

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-593?page=all ]

Jesse McConnell updated CONTINUUM-593:
--

Component/s: (was: Web interface)
 (was: Core system)
 SCM

> Unable to update starteam url
> -
>
> Key: CONTINUUM-593
> URL: http://jira.codehaus.org/browse/CONTINUUM-593
> Project: Continuum
>  Issue Type: Bug
>  Components: SCM
>Affects 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] Commented: (CONTINUUM-786) Failing to build project in right order or failing to recognize a svn change in the right order

[Jesse McConnell (JIRA)]

[ http://jira.codehaus.org/browse/CONTINUUM-786?page=comments#action_80135 
] 

Jesse McConnell commented on CONTINUUM-786:
---

http://www.nabble.com/build-scheduling-issues-tf2592068.html#a7235065

vincent, any feedback you would like to make on that thread?

> Failing to build project in right order or failing to recognize a svn change 
> in the right order
> ---
>
> Key: CONTINUUM-786
> URL: http://jira.codehaus.org/browse/CONTINUUM-786
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.0.3
>Reporter: Vincent Massol
>Priority: Critical
> Fix For: 1.1
>
> Attachments: Continuum after Cargo commit rev1152.jpg, This is what 
> happened after a build all.jpg
>
>
> Here's what happened. 
> * Today (26th of July) around 15:35GMT+1, I made a big commit in Cargo 
> touching several modules.
> * At 16:04GMT+1 I received 2 emails from C (C = Continuum) showing 
> compilation errors in the following 2 modules (see 
> http://ci.codehaus.org:8001/continuum/servlet/continuum/target/Summary.vm/fid/continuumProject):
> ** "Cargo Core Geronimo Container"
> ** "Cargo Core Jetty Container"
> * Note that the build is working fine locally here
> The 
> [error|http://ci.codehaus.org:8001/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=47541&id=151]
>  is because it's finding a class that's been renamed in the "Cargo Core 
> Container API" module. Note that this module is defined to be built before 
> the two modules in error above.
> What's also strange is that C shows a lot of modules in error (the red 
> crosses) but if you look in the build results these modules are building 
> fine. I'm attaching a screenshot to this issue.
> What can I do more to help debu this? This makes C unusable for me as I 
> consider these 2 emails as false positives. Is there something I don't 
> understand?
> 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-833) Include jspc:compile to verify all continuum-webapp jsps.

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-833?page=all ]

Jesse McConnell updated CONTINUUM-833:
--

   Assignee: Joakim Erdfelt
Component/s: Web interface

your a commiter, you do it, or if its done, close this :)

> Include jspc:compile to verify all continuum-webapp jsps.
> -
>
> Key: CONTINUUM-833
> URL: http://jira.codehaus.org/browse/CONTINUUM-833
> Project: Continuum
>  Issue Type: Improvement
>  Components: Web interface
>Reporter: Joakim Erdfelt
> Assigned To: Joakim Erdfelt
> Attachments: CONTINUUM-jsp-precompile.patch
>
>
> Include the jspc:compile step to verify all of the jsps in the 
> continuum-webapp.

-- 
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-44) multiple profiles

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-44?page=all ]

Jesse McConnell updated CONTINUUM-44:
-

Fix Version/s: (was: 1.2)
   1.1
  Component/s: Core - Profiles

> multiple profiles
> -
>
> Key: CONTINUUM-44
> URL: http://jira.codehaus.org/browse/CONTINUUM-44
> Project: Continuum
>  Issue Type: New Feature
>  Components: Core - Profiles
>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-137) Store dependency information at the ContinuumProject level

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-137?page=all ]

Jesse McConnell updated CONTINUUM-137:
--

   Assignee: (was: Kenney Westerhof)
Component/s: Integration - Maven 2

> Store dependency information at the ContinuumProject level
> --
>
> Key: CONTINUUM-137
> URL: http://jira.codehaus.org/browse/CONTINUUM-137
> Project: Continuum
>  Issue Type: New Feature
>  Components: Integration - Maven 2
>Affects 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-225) Collect all build/execution classes for a particular tool like Maven into a single package

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-225?page=all ]

Jesse McConnell updated CONTINUUM-225:
--

Component/s: Core system

> Collect all build/execution classes for a particular tool like Maven into a 
> single package
> --
>
> Key: CONTINUUM-225
> URL: http://jira.codehaus.org/browse/CONTINUUM-225
> Project: Continuum
>  Issue Type: Improvement
>  Components: Core system
>Reporter: Jason van Zyl
> Fix For: 1.1
>
>
> Right now there are build execution classes for Maven in one place and 
> project builder classes for maven in another. We need to package them up into 
> a single module for clarity.

-- 
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-2657) Generics - Compilation failure - incompatible types - cast to parent type from method taking in subtype.

[Kenny MacDermid (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-2657?page=all ]

Kenny MacDermid closed MNG-2657.


Resolution: Cannot Reproduce

> Generics - Compilation failure - incompatible types - cast to parent type 
> from method taking in subtype.
> 
>
> Key: MNG-2657
> URL: http://jira.codehaus.org/browse/MNG-2657
> Project: Maven 2
>  Issue Type: Bug
>Affects Versions: 2.0.4
> Environment: Windows Xp and Ubuntu Linux. Standard x86 hardware.
>Reporter: Kenny MacDermid
>
> Maven will not compile classes in the following situation, although eclipse 
> will compile them fine:
> These are the two classes that are the types maven is getting confused with:
> public abstract class User {...}
> public class Employee extends User {...}
> A factory called EntityManager returns a generic typed Criteria:
> public  Criteria createCriteria(Class c) {
> return new CriteriaImpl(c);
> }
> This is being used in the Tests in the following way:
> Criteria criteria = em.createCriteria(Employee.class);
> As I said, in eclipse this compiles fine, with no warnings. With maven I 
> receive the error message:
> [INFO] Compilation failure
> ...UserTest.java:[59,51] incompatible types
> found   : Criteria
> required: Criteria
> The stack trace is as follows:
> org.apache.maven.BuildFailureException: Compilation failure
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> 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:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation 
> failure
> at 
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
> at 
> org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:99)
> at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Other possible useful maven information (actualy dir replaced with DIR):
> [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:testCompile' -->
> [DEBUG]   (f) basedir = DIR
> [DEBUG]   (f) buildDirectory = DIR\target
> [DEBUG]   (f) classpathElements = [DIR\target\classes, 
> DIR\target\test-classes, ... (many others)]
> [DEBUG]   (f) compileSourceRoots = [DIR\src\test\java]
> [DEBUG]   (f) compilerId = javac
> [DEBUG]   (f) debug = true
> [DEBUG]   (f) fork = false
> [DEBUG]   (f) optimize = false
> [DEBUG]   (f) outputDirectory = DIR\target\test-classes
> [DEBUG]   (f) outputFileName = IdentityRepository-0.1
> [DEBUG]   (f) showDeprecation = false
> [DEBUG]   (f) showWarnings = false
> [DEBUG]   (f) source = 1.5
> [DEBUG]   (f) staleMillis = 0
> [DEBUG]   (f) target = 1.5
> [DEBUG]   (f) verbose = false
> [DEBUG] -- end configuration --
> Thanks in advance,
> Kenny

-- 
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-918) Sometimes when building the icon shows in queue in project group view page

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-918?page=all ]

Jesse McConnell updated CONTINUUM-918:
--

Component/s: Web - UI

> Sometimes when building the icon shows in queue in project group view page
> --
>
> Key: CONTINUUM-918
> URL: http://jira.codehaus.org/browse/CONTINUUM-918
> Project: Continuum
>  Issue Type: Bug
>  Components: Web - UI
>Affects Versions: 1.1
>Reporter: Carlos Sanchez
>Priority: Trivial
>
> Seems that sometimes happen that the status icon doesn't change
> Table shows
> Building   Continuum Parent Project   1.1-SNAPSHOT(In Queue) icon
> Log says
> 2006-09-15 20:07:47,236 [pool-1-thread-1] INFO  BuildController   
>  - Merging SCM results
> 2006-09-15 20:07:47,236 [pool-1-thread-1] INFO  BuildController   
>  - Changes found, building
> 2006-09-15 20:07:47,237 [pool-1-thread-1] INFO  BuildController   
>  - Performing action update-project-from-working-directory
> 2006-09-15 20:07:47,250 [pool-1-thread-1] INFO  
> Action:update-project-from-working-directory - Updating project 'Continuum 
> Parent Project' from checkout.
> 2006-09-15 20:07:47,836 [pool-1-thread-1] INFO  JDO   
>  - >> JoinMapStore.put key=address [EMAIL PROTECTED]
> 2006-09-15 20:07:48,873 [pool-1-thread-1] WARN  SQL   
>  - Object with id "94" not found !
> 2006-09-15 20:07:48,924 [pool-1-thread-1] INFO  BuildController   
>  - Performing action execute-builder
> 2006-09-15 20:07:49,187 [pool-1-thread-1] WARN  ContinuumBuildExecutor:maven2 
>  - Could not find the executable 'mvn' in this path:
> 2006-09-15 20:07:50,108 [pool-1-thread-1] INFO  ShellCommandHelper
>  - Executing: mvn --batch-mode --non-recursive clean install site
> 2

-- 
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-991) Add meta refresh header to summary pages

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-991?page=all ]

Jesse McConnell updated CONTINUUM-991:
--

Fix Version/s: 1.1
  Component/s: Web - UI

> Add meta refresh header to summary pages
> 
>
> Key: CONTINUUM-991
> URL: http://jira.codehaus.org/browse/CONTINUUM-991
> Project: Continuum
>  Issue Type: New Feature
>  Components: Web - UI
>Reporter: John Didion
>Priority: Minor
> Fix For: 1.1
>
>
> It's nice to refresh summary pages automatically to update build statuses 
> without the user having to continually click the refresh button.
> I didn't include a patch because I'm working against the Maestro codebase, 
> which has migrated all the UI to jsp. Should be the same concept, though. 
> Just add  to the  section.

-- 
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-774) Better support for multiprojects

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-774?page=all ]

Jesse McConnell updated CONTINUUM-774:
--

Component/s: Project Grouping

> Better support for multiprojects
> 
>
> Key: CONTINUUM-774
> URL: http://jira.codehaus.org/browse/CONTINUUM-774
> Project: Continuum
>  Issue Type: Improvement
>  Components: Project Grouping
>Reporter: Tomasz Pik
>Priority: Minor
>
> Currently when multiproject is being added to continuum, then top project is 
> being registered as 'non-recursive' and all submodules are being added as 
> separate projects.
> It will be nice to have the possibility to define (during initiial POM 
> loading) if project should be treat that way or as a multiproject with full 
> recursive build and without adding subprojects.
> I'm doing that manually, by redefining build section for top project and 
> removing subprojects.

-- 
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-995) MavenTwoBuildExecutor.getDeployableArtifacts does not return attached artifacts

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-995?page=all ]

Jesse McConnell updated CONTINUUM-995:
--

Component/s: Integration - Maven 2

> MavenTwoBuildExecutor.getDeployableArtifacts does not return attached 
> artifacts
> ---
>
> Key: CONTINUUM-995
> URL: http://jira.codehaus.org/browse/CONTINUUM-995
> Project: Continuum
>  Issue Type: Bug
>  Components: Integration - Maven 2
>Reporter: John Didion
> Attachments: deploy-attached-artifacts.diff
>
>
> It only returns the main artifact for the project, and not any of the ones 
> that get attached.
> This patch also adds a few more cases for -dist artifacts (assemblies).

-- 
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-989) There are two component definitions for role org.codehaus.plexus.mailsender.MailSender

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-989?page=all ]

Jesse McConnell updated CONTINUUM-989:
--

Fix Version/s: 1.1
  Component/s: Notifier - Mail

> There are two component definitions for role 
> org.codehaus.plexus.mailsender.MailSender
> --
>
> Key: CONTINUUM-989
> URL: http://jira.codehaus.org/browse/CONTINUUM-989
> Project: Continuum
>  Issue Type: Bug
>  Components: Notifier - Mail
>Affects Versions: 1.0.3
>Reporter: John Didion
> Fix For: 1.1
>
>
> In continuum-webapp/src/main/resources/META-INF/plexus.application.xml, there 
> are two component definitions for role 
> org.codehaus.plexus.mailsender.MailSender. When Plexus is configured, the 
> last component definition wins, so unless you configure the last (or both) 
> mail sender components, the MailSender will always try to send via localhost. 
> It appears that the second one is redundant and can be removed.

-- 
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-972) Unable to delete projects

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-972?page=all ]

Jesse McConnell updated CONTINUUM-972:
--

Component/s: Core system

> Unable to delete projects
> -
>
> Key: CONTINUUM-972
> URL: http://jira.codehaus.org/browse/CONTINUUM-972
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.0.3
> Environment: Redhat Enterprise 3
>Reporter: Uri Moszkowicz
>
> I am unable to delete project sometimes. I've tried creating a simple project 
> and immediately deleting it. That seems to work. But when I create a real 
> project, let it run for a few days and then try to delete it I cannot.
> To reproduce:
> 1. Install continuum
> 2. Create a project
> 3. Let it run for at least one build (success or failure doesn't matter)
> 4. Delete the project by clicking on "X" from main project page. A delete 
> confirmation page should then appear.
> 5. Click on the "delete" button to confirm. The web browser then begins 
> loading but it never terminates. The logs show no exceptions. The delete just 
> hangs.
> I've removed all the files from the build-output and working-directory and 
> tried deleting again. This makes no difference. If you interrupt the delete 
> and click on show projects the projects page ends up in an inconsistent state 
> (not as many columns, no buttons, an Apache copyright message).

-- 
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-841) Notifier get duplicated during builds

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-841?page=all ]

Jesse McConnell updated CONTINUUM-841:
--

Fix Version/s: 1.1
  Component/s: Notification Subsystem

> Notifier get duplicated during builds
> -
>
> Key: CONTINUUM-841
> URL: http://jira.codehaus.org/browse/CONTINUUM-841
> Project: Continuum
>  Issue Type: Bug
>  Components: Notification Subsystem
>Affects Versions: 1.0.3
> Environment: maven 1.1-beta3 on Windows 2000 / JDK 5
>Reporter: nicolas de loof
> Fix For: 1.1
>
> Attachments: wrapper.log
>
>
> I receive my failure mail 12 times. Looking at the project configuration in 
> continuum, my notifier eMail is registered 12 times. I delete all and 
> register a fresh new email account. After some (failed) builds, it gets 
> duplicated as notifier.

-- 
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-600) Add INIT INFO to run.sh

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-600?page=all ]

Jesse McConnell updated CONTINUUM-600:
--

Description: 
Add something like this to the start shell-skript, so it is more standards 
compliant:

 ### BEGIN INIT INFO 
 # Provides: continuum
 # Required-Start: $network
 # Required-Stop: $network
 # Default-Start: 3 5
 # Default-Stop: 0 1 2 6
 # Description: Maven Continuum
 ### END INIT INFO

  was:
Add something like this to the start shell-skript, so it is more standards 
compliant:

### BEGIN INIT INFO
# Provides: continuum
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Maven Continuum
### END INIT INFO


> Add INIT INFO to run.sh
> ---
>
> Key: CONTINUUM-600
> URL: http://jira.codehaus.org/browse/CONTINUUM-600
> Project: Continuum
>  Issue Type: Improvement
>  Components: Environmental
> Environment: Linux
>Reporter: Michael Böckling
>
> Add something like this to the start shell-skript, so it is more standards 
> compliant:
>  ### BEGIN INIT INFO 
>  # Provides: continuum
>  # Required-Start: $network
>  # Required-Stop: $network
>  # Default-Start: 3 5
>  # Default-Stop: 0 1 2 6
>  # Description: Maven Continuum
>  ### END INIT 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: (CONTINUUM-156) should validate that an updated pom doesn't change too drastically

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-156?page=all ]

Jesse McConnell updated CONTINUUM-156:
--

Component/s: Core system

> should validate that an updated pom doesn't change too drastically
> --
>
> Key: CONTINUUM-156
> URL: http://jira.codehaus.org/browse/CONTINUUM-156
> Project: Continuum
>  Issue Type: Improvement
>  Components: Core system
>Reporter: Brett Porter
> Fix For: 1.1
>
>
> I added maven-core's POM, which is using a post -alpha-2 technique of 
> inheriting the SCM connection URL and appending the artifact ID.
> This resulted in the new SCM URL being different and so it checked out the 
> root POM and proceeded to checkout all of maven/components/trunk.
> IF the group ID/artifact ID of the POM changes on update, I think this needs 
> to go into an error state that requires user intervention to either accept it 
> has changed, or find out what is wrong.

-- 
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-291) implement per project developer management

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-291?page=all ]

Jesse McConnell updated CONTINUUM-291:
--

Fix Version/s: (was: 1.1)
   1.2
  Component/s: Web - UI

my guess is a little developer dashboard that they can configure with their 
projects of interest and latest activity, etc..

> implement per project developer management
> --
>
> Key: CONTINUUM-291
> URL: http://jira.codehaus.org/browse/CONTINUUM-291
> Project: Continuum
>  Issue Type: New Feature
>  Components: Web - UI
>Reporter: Brett Porter
> Fix For: 1.2
>
>


-- 
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-606) Add Build Time to Project Summary Page

[Ryan Slobojan (JIRA)]

[ http://jira.codehaus.org/browse/CONTINUUM-606?page=comments#action_80121 
] 

Ryan Slobojan commented on CONTINUUM-606:
-

This starts to tend to a larger issue - should there be a large set of columns 
to select from on the project summary page, and should the set of columns be 
configurable?

Obviously that's a different issue, but it may be a good long-term fix to 
issues like this popping up in the future ("I want column X on the project 
summary"). For now, what is the likelihood that a fix for this issue will make 
it into Continuum 1.1?

> Add Build Time to Project Summary Page
> --
>
> Key: CONTINUUM-606
> URL: http://jira.codehaus.org/browse/CONTINUUM-606
> Project: Continuum
>  Issue Type: Improvement
>  Components: Web interface
>Affects Versions: 1.0.2
>Reporter: Richard C. L. Li
> Assigned To: Kenney Westerhof
> Fix For: 1.1
>
>
> It is nice to have the last success build time in the summary.  I always need 
> to make severial clicks to see if the build the newest one.

-- 
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

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-140?page=all ]

Jesse McConnell updated CONTINUUM-140:
--

Fix Version/s: 1.2
  Component/s: Web - UI

> Allow the use of the CC in the web UI
> -
>
> Key: CONTINUUM-140
> URL: http://jira.codehaus.org/browse/CONTINUUM-140
> Project: Continuum
>  Issue Type: New Feature
>  Components: Web - UI
>Affects Versions: 1.0-alpha-4
>Reporter: Jason van Zyl
> Fix For: 1.2
>
>
> 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-670) State of a project

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-670?page=all ]

Jesse McConnell updated CONTINUUM-670:
--

Fix Version/s: 1.2
  Component/s: Core system

> State of a project
> --
>
> Key: CONTINUUM-670
> URL: http://jira.codehaus.org/browse/CONTINUUM-670
> Project: Continuum
>  Issue Type: New Feature
>  Components: Core system
>Reporter: Reinhard Spisser
> Fix For: 1.2
>
>
> I suggest to introduce states of the projects: active, disabled and archived
> - active: continuum will check for modifications and build it
> - disabled: the project remains on the same "project list" as the
> active project (the continuum homepage), but the project links are
> greyed out. Continuum will not check for modifications. Projects can
> be enabled again to become active.
> - archived: the project is not show on the main project list, but on a
> "Archived Projects" tab (or something similar). These projects will
> not be build, but build history will remain.
> With this states, someone could write a program that disables a
> project if no commits were done in the last x weeks and archives a
> project if no commits were done in the last x months. Also, if a
> commit is done in a disabled project then the project is enabled
> 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-127) Try using a series of incorrect data in the integration tests

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-127?page=all ]

Jesse McConnell updated CONTINUUM-127:
--

Fix Version/s: 1.1
  Component/s: Testing

> Try using a series of incorrect data in the integration tests
> -
>
> Key: CONTINUUM-127
> URL: http://jira.codehaus.org/browse/CONTINUUM-127
> Project: Continuum
>  Issue Type: Task
>  Components: Testing
>Affects Versions: 1.0-alpha-3
>Reporter: Jason van Zyl
> Assigned To: Trygve Laugstol
>Priority: Critical
> Fix For: 1.1
>
>
> We need to trap any incorrect data being thrown at continuum coming from any 
> interface. The best place to try this is the integration tests that we run 
> from python. I accidentally used some bad POMs using the xmlrpc interface and 
> in the web interface the projects seems to stay perpetually in the "Checking 
> Out" state.

-- 
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: (MAVENUPLOAD-1228) Request for maven sync with m2.modularity.net.au

[Ben Fortuna (JIRA)]

[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1228?page=comments#action_80103 ] 

Ben Fortuna commented on MAVENUPLOAD-1228:
--

Just to explain a bit further, the goal here is to automatically upload 
releases of multiple open source projects, namely ical4j (ical4j.sf.net) and 
mstor (mstor.sf.net). The documentation on how to achieve this is very minimal, 
but I'm assuming this is the correct way.

The reason I has originally specified the root directory (/) is that I don't 
have a lot in my maven repository right now, just the first release of ical4j 
and the parent pom. Note that the parent pom is under a different group id, 
which is why I have know specified to sync the 'net' directory. If you require 
me to be more specific I will need to provide two scripts: one to sync 
'net.modularity' and one to sync 'net.fortuna' (I read somewhere that parent 
poms must also be uploaded to the repository, which is why I need both group 
ids synced).

Let me know if there are further issues here.

regards,
ben


> Request for maven sync with m2.modularity.net.au
> 
>
> Key: MAVENUPLOAD-1228
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1228
> Project: maven-upload-requests
>  Issue Type: Task
>Reporter: Ben Fortuna
> Attachments: modularity-m2sync.sh, modularity-m2sync.sh
>
>
> I'd like to request the setup of an automatic sync between repository 
> m2.modularity.net.au and ibiblio.
> Please find attached the required rsync script to facilitate this process. 
> Note that as SSH is enabled I have added the maven public key 
> [http://www.ibiblio.org/maven/id_dsa.pub] to the home directory of the 
> mavensync user.
> If I have missed anything, or there are any problems with this request feel 
> free to let me know.
> regards,
> ben

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MSITE-91) "src/site/site.xml" hardcoded in AbstractSiteMojo.java

[Vincent Siveton (JIRA)]

[ http://jira.codehaus.org/browse/MSITE-91?page=comments#action_80102 ] 

Vincent Siveton commented on MSITE-91:
--

Hi Franz,

Dennis already committed stuff [1] in the past. Could you verify it?

BTW, FYI @version tag is more for files, @since is better for methods [2]

Thanks!

http://svn.apache.org/viewvc?view=rev&rev=473599
http://java.sun.com/j2se/javadoc/writingdoccomments

> "src/site/site.xml" hardcoded in AbstractSiteMojo.java
> --
>
> Key: MSITE-91
> URL: http://jira.codehaus.org/browse/MSITE-91
> Project: Maven 2.x Site Plugin
>  Issue Type: Bug
>Affects Versions: 2.0-beta-4
>Reporter: Fabrice BELLINGARD
> Assigned To: Dennis Lundberg
> Fix For: 2.0
>
> Attachments: MSITE-91-maven-site-plugin.patch, MSITE-91.patch
>
>
> There's a todo in the code, so this issue is more a reminder than an unknown 
> bug.
> In AbstractSiteMojo.java, there's:
> protected File getSiteDescriptorFile( File basedir, Locale locale )
> {
> // TODO: get proper siteDirectory from site configuration of the 
> project this relates to
> File siteDescriptor = new File( basedir, "src/site/site_" + 
> locale.getLanguage() + ".xml" );
> if ( !siteDescriptor.exists() )
> {
> siteDescriptor = new File( basedir, "src/site/site.xml" );
> }
> return siteDescriptor;
> }

-- 
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: (MAVENUPLOAD-1228) Request for maven sync with m2.modularity.net.au

[Ben Fortuna (JIRA)]

 [ http://jira.codehaus.org/browse/MAVENUPLOAD-1228?page=all ]

Ben Fortuna updated MAVENUPLOAD-1228:
-

Attachment: modularity-m2sync.sh

Here is a second version of the mavensync script, which narrows the sync to the 
"net" directory

> Request for maven sync with m2.modularity.net.au
> 
>
> Key: MAVENUPLOAD-1228
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1228
> Project: maven-upload-requests
>  Issue Type: Task
>Reporter: Ben Fortuna
> Attachments: modularity-m2sync.sh, modularity-m2sync.sh
>
>
> I'd like to request the setup of an automatic sync between repository 
> m2.modularity.net.au and ibiblio.
> Please find attached the required rsync script to facilitate this process. 
> Note that as SSH is enabled I have added the maven public key 
> [http://www.ibiblio.org/maven/id_dsa.pub] to the home directory of the 
> mavensync user.
> If I have missed anything, or there are any problems with this request feel 
> free to let me know.
> regards,
> ben

-- 
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-2658) [maven-plugin-testing-harness-1.0-beta-2] : expressions are not correctly evaluated

[Emmanuel Hugonnet (JIRA)]

[maven-plugin-testing-harness-1.0-beta-2] : expressions are not correctly 
evaluated
---

 Key: MNG-2658
 URL: http://jira.codehaus.org/browse/MNG-2658
 Project: Maven 2
  Issue Type: Bug
  Components: Plugin Creation Tools
Affects Versions: 2.0.4
Reporter: Emmanuel Hugonnet
 Attachments: expressionEvaluator.patch

When evaluating an expression, the evaluator doesn't use System.properties, ou 
profiles.
I have attached a patch so at least System.properties are checked and null is 
returned if none is found.

-- 
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-1000) NullPointerException in maven 2 builder on build failure

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-1000?page=all ]

Jesse McConnell updated CONTINUUM-1000:
---

Component/s: (was: Core system)
 Integration - Maven 2

> NullPointerException in maven 2 builder on build failure
> 
>
> Key: CONTINUUM-1000
> URL: http://jira.codehaus.org/browse/CONTINUUM-1000
> Project: Continuum
>  Issue Type: Bug
>  Components: Integration - Maven 2
>Affects Versions: 1.1
> Environment: JDK v1.4.2 on RHAS4, with maven 2.0.4.
>Reporter: Graham Leggett
>Priority: Critical
>
> When an attempt is made to build a maven 2 subproject, and that subproject is 
> known to fail to build, the following build error is logged during the 
> continuum build:
> [INFO] Scanning for projects...
> [INFO] 
> 
> [ERROR] FATAL ERROR
> [INFO] 
> 
> [INFO] null
> [INFO] 
> 
> [INFO] Trace
> java.lang.NullPointerException
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1078)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:674)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192)
>   at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
>   at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
>   at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>   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:585)
>   at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] 
> 
> [INFO] Total time: < 1 second
> [INFO] Finished at: Wed Nov 08 14:43:16 SAST 2006
> [INFO] Final Memory: 3M/239M
> [INFO] 
> 
> It's not clear at this point whether this is a maven 2 bug, or a continuum 
> bug.

-- 
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-788) updated white site to reflect proposed ideas for user and project group role management

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-788?page=all ]

Jesse McConnell closed CONTINUUM-788.
-

Resolution: Fixed

covered by integration with p-sec

> updated white site to reflect proposed ideas for user and project group role 
> management
> ---
>
> Key: CONTINUUM-788
> URL: http://jira.codehaus.org/browse/CONTINUUM-788
> Project: Continuum
>  Issue Type: Improvement
>Reporter: Jesse McConnell
> Attachments: group-and-roles-updates.diff
>
>
> based on the discussions on the mailing list regarding the addition of roles 
> and permissions to user and project groups management I mocked the changes 
> into the white site..
> here is a stab at a few screens and some linkages
> changes are noticable on the index page/summary where the distinct project 
> groups are broken out and clickable to the singular project group status 
> page, which in turn can be managed as a project group...the groupManagement 
> page shows teh roles, permissions, and users allocated and allows you to go 
> to the editRoles page from there.
> user pages now show the project group role allocations

-- 
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-724) Make the group name update itself when the build runs.

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-724?page=all ]

Jesse McConnell updated CONTINUUM-724:
--

Component/s: Integration - Maven 2

> Make the group name update itself when the build runs.
> --
>
> Key: CONTINUUM-724
> URL: http://jira.codehaus.org/browse/CONTINUUM-724
> Project: Continuum
>  Issue Type: Sub-task
>  Components: Integration - Maven 2
>Affects Versions: 1.0.3
>Reporter: Adrian
> Fix For: 1.1
>
>
> The group name never updates itself throughout the projects life, even if I 
> change the name in the pom.xml

-- 
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-829) Summary / project group pages should be a tree view with relationship

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-829?page=all ]

Jesse McConnell updated CONTINUUM-829:
--

Component/s: Web - UI

> Summary / project group pages should be a tree view with  relationship
> --
>
> Key: CONTINUUM-829
> URL: http://jira.codehaus.org/browse/CONTINUUM-829
> Project: Continuum
>  Issue Type: Improvement
>  Components: Web - UI
>Reporter: Kenney Westerhof
>


-- 
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-784) Allow viewing files in ${java.io.tmpdir} in the "Working Copy" tab

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-784?page=all ]

Jesse McConnell updated CONTINUUM-784:
--

Component/s: Web - UI

> Allow viewing files in ${java.io.tmpdir} in the "Working Copy" tab
> --
>
> Key: CONTINUUM-784
> URL: http://jira.codehaus.org/browse/CONTINUUM-784
> Project: Continuum
>  Issue Type: Improvement
>  Components: Web - UI
>Affects Versions: 1.0.3
>Reporter: Vincent Massol
>
> Some programs use the java.io.tmpDir directory to put some temporaryf files 
> and in order to debug a problem it's sometimes necessary to check what's in 
> there but the UI doesn't allow 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-785) javax.jdo.JDODataStoreException: Update request failed: UPDATE BUILDRESULT SET ERROR=? WHERE ID=?

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-785?page=all ]

Jesse McConnell updated CONTINUUM-785:
--

Component/s: Database

> javax.jdo.JDODataStoreException: Update request failed: UPDATE BUILDRESULT 
> SET ERROR=? WHERE ID=?
> -
>
> Key: CONTINUUM-785
> URL: http://jira.codehaus.org/browse/CONTINUUM-785
> Project: Continuum
>  Issue Type: Bug
>  Components: Database
>Affects Versions: 1.0.3
> Environment:   Operating system : Linux(unknown)
>   Java version : 1.5.0_06(Sun Microsystems Inc.)
>Reporter: Kevin Wang
>
> When I build my project in Continuum that is upgraded to 1.0.3 from 1.0.2, I 
> always receive such error message with nodifier:
> Build statistics:
>   State: Error
>   Previous State: Error
>   Started at: Mon, 3 Jul 2006 15:30:00 +0800
>   Finished at: Mon, 3 Jul 2006 15:30:04 +0800
>   Total time: 4s
>   Build Trigger: Schedule
>   Exit code: 0
>   Building machine hostname: bjlinux15
>   Operating system : Linux(unknown)
>   Java version : 1.5.0_06(Sun Microsystems Inc.)
> Changes
>   No files changed
>   
> 
> Build Error:
> 
> javax.jdo.JDODataStoreException: Update request failed: UPDATE BUILDRESULT 
> SET ERROR=? 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.AbstractPersistenceManager.markDirty(AbstractPersistenceManager.java:3126)
>   at 
> org.jpox.state.StateManagerImpl.postWriteField(StateManagerImpl.java:4334)
>   at org.jpox.state.StateManagerImpl.makeDirty(StateManagerImpl.java:1050)
>   at 
> org.jpox.state.AttachFieldManager.storeIntField(AttachFieldManager.java:255)
>   at 
> org.jpox.state.StateManagerImpl.providedIntField(StateManagerImpl.java:2571)
>   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:2964)
>   at 
> org.jpox.state.StateManagerImpl.internalAttachCopy(StateManagerImpl.java:4028)
>   at 
> org.jpox.state.StateManagerImpl.attachCopy(StateManagerImpl.java:3963)
>   at 
> org.jpox.AbstractPersistenceManager.attachCopy(AbstractPersistenceManager.java:1336)
>   at 
> org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1109)
>   at 
> org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1201)
>   at 
> org.apache.maven.continuum.store.JdoContinuumStore.updateBuildResult(JdoContinuumStore.java:238)
>   at 
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:324)
>   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)
> NestedThrowablesStackTrace:
> ERROR 22001: A truncation error was encountered trying to shrink VARCHAR 
> 'org.apache.maven.continuum.execution.ContinuumBuildExecutorE&' to length 
> 8192.
>   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.UpdateResultSet.collectAffectedRows(Unknown 
> Source)
>   at org.apache.derby.impl.sql.execute.UpdateResultSet.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.a

[jira] Updated: (CONTINUUM-548) Can't change project name

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-548?page=all ]

Jesse McConnell updated CONTINUUM-548:
--

Fix Version/s: 1.1
  Component/s: Core system

http://www.nabble.com/project-group-shortcuts-tf2542431.html#a7083998

I wrote on this and think we have a solution to this, just need to get it 
implemented

> Can't change project name
> -
>
> Key: CONTINUUM-548
> URL: http://jira.codehaus.org/browse/CONTINUUM-548
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.0.2
>Reporter: Tim McCune
> Fix For: 1.1
>
>
> I have created a new Maven 1.x project in Continuum and after doing so, 
> edited its project name in the web UI.  The edit seems to work fine, but the 
> next time the project gets built, its name gets reverted back to the original 
> name that it picked up from the POM.  This is a real pain in the ass because 
> I want multiple Continuum projects created from the same POM (so they are all 
> getting the same name) to do things like building multiple branches, and 
> running different goals on different schedules.

-- 
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-245) Define what default information Continuum should populate on its first startup

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-245?page=all ]

Jesse McConnell updated CONTINUUM-245:
--

Component/s: Web - Configuration

> Define what default information Continuum should populate on its first startup
> --
>
> Key: CONTINUUM-245
> URL: http://jira.codehaus.org/browse/CONTINUUM-245
> Project: Continuum
>  Issue Type: Task
>  Components: Web - Configuration
>Reporter: Jason van Zyl
> Fix For: 1.1
>
>
> Continuum is becoming more configurable but it would still be nice if 
> Continuum could run out of the box by picking up system information like the:
> o JDK (the one used to run Continuum)
> o Default schedule (hourly is probably fine using update mode)
> o Ant
> o Maven 1.x
> o Maven 2.x

-- 
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-661) ConcurrentModificationException when building maven2 multiproject

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-661?page=all ]

Jesse McConnell updated CONTINUUM-661:
--

Component/s: Integration - Maven 2

> ConcurrentModificationException when building maven2 multiproject
> -
>
> Key: CONTINUUM-661
> URL: http://jira.codehaus.org/browse/CONTINUUM-661
> Project: Continuum
>  Issue Type: Bug
>  Components: Integration - Maven 2
>Affects 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-758) Use plexus-cdc where it is possible for the generation of components.xml

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-758?page=all ]

Jesse McConnell updated CONTINUUM-758:
--

   Assignee: Jesse McConnell
Component/s: Core system

I have continuum-core mostly switched over locally from working on this before, 
I'll just take this issue and try and knock it off

couple of configuration issues in there so we'll have to merge descriptors for 
continuum-core at least, haven't looked at the other modules yet

> Use plexus-cdc where it is possible for the generation of components.xml
> 
>
> Key: CONTINUUM-758
> URL: http://jira.codehaus.org/browse/CONTINUUM-758
> Project: Continuum
>  Issue Type: Task
>  Components: Core system
>Affects Versions: 1.1
>Reporter: Emmanuel Venisse
> Assigned To: Jesse McConnell
>Priority: Trivial
> 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] Updated: (CONTINUUM-968) Tests for continuum-release fail randomly

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-968?page=all ]

Jesse McConnell updated CONTINUUM-968:
--

Component/s: Testing

> Tests for continuum-release fail randomly
> -
>
> Key: CONTINUUM-968
> URL: http://jira.codehaus.org/browse/CONTINUUM-968
> Project: Continuum
>  Issue Type: Test
>  Components: Testing
>Affects Versions: 1.1
> Environment: tests fail for some environments and pass for others. 
> For some they fail at random
>Reporter: Philippe Faes
>Priority: Minor
> Fix For: 1.1
>
> Attachments: continuum-release.diff
>
>
> The test for continuum-release fails randomly. This is because the two test 
> methods are executed in a random order (this is intended JUnit behavior), and 
> the tests alter files. 
> Solution is to restore files between tests (method setUp) and to force the 
> order of the two tests (create one test method that calls the two other 
> methods one by one).
> Patch is attached. Please verify and commit.

-- 
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-579) Rename run.sh to continuum.sh

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-579?page=all ]

Jesse McConnell updated CONTINUUM-579:
--

Fix Version/s: 1.1
  Component/s: Environmental

> Rename run.sh to continuum.sh
> -
>
> Key: CONTINUUM-579
> URL: http://jira.codehaus.org/browse/CONTINUUM-579
> Project: Continuum
>  Issue Type: Improvement
>  Components: Environmental
>Affects Versions: 1.0.2
> Environment: Linux
>Reporter: Henri Yandell
>Priority: Trivial
> Fix For: 1.1
>
>
> It's a bit odd doing:  "sh linux/run.sh stop"
> It'd be nicer to be doing:  "sh linux/continuum.sh stop" or  "sh 
> linux/continuum stop".

-- 
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-840) jdbc2_0-stdext.jar download instructions not in README.txt

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-840?page=all ]

Jesse McConnell updated CONTINUUM-840:
--

 Assignee: Jesse McConnell
Fix Version/s: 1.1
  Component/s: Documentation

> jdbc2_0-stdext.jar download instructions not in README.txt 
> ---
>
> Key: CONTINUUM-840
> URL: http://jira.codehaus.org/browse/CONTINUUM-840
> Project: Continuum
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.0.3
>Reporter: Baerrach bonDierne
> Assigned To: Jesse McConnell
>Priority: Minor
> Fix For: 1.1
>
> Attachments: patch.txt
>
>
> The README file does not include jdbc2_0-stdext.jar instructions.
> It is fairly easy to read the pom from ibiblio and work it out.
> (patch attached)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MASSEMBLY-153) files included with the tag have fileMode 204

[Paul Jungwirth (JIRA)]

[ http://jira.codehaus.org/browse/MASSEMBLY-153?page=comments#action_80128 
] 

Paul Jungwirth commented on MASSEMBLY-153:
--

Note also that whoever wrote the code to assign a default mode also got bit by 
this bug, because when no mode is specified, you still get mode 0204.


> files included with the  tag have fileMode 204
> 
>
> Key: MASSEMBLY-153
> URL: http://jira.codehaus.org/browse/MASSEMBLY-153
> Project: Maven 2.x Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 2.1
> Environment: linux
>Reporter: Paul Jungwirth
>Priority: Minor
>
> I'm trying to include files like this:
> 
>   
> README
> true
>   
>   
> src/blah
>   
> 
> I'm packaging them as both .tar.gz and .zip. In the tarball, the files wind 
> up with mode 0204:
> --wr--
> In the zip file, they wind up with mode 1204:
> --wr-T
> Using a  element of 644 does not fix the problem. This only happens 
> for files specified in , not . It happens whether I use 
> filtering or not.
> These are pretty weird modes. I don't think this is a duplicate of 
> MASSEMBLY-75. It's not just losing the mode I set; it's assigning a very 
> peculiar mode as if with a mind of its own.
> My umask is 0002.
> Paul

-- 
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: (MASSEMBLY-153) files included with the tag have fileMode 204

[Paul Jungwirth (JIRA)]

[ http://jira.codehaus.org/browse/MASSEMBLY-153?page=comments#action_80127 
] 

Paul Jungwirth commented on MASSEMBLY-153:
--

Ah, thank you for the workaround. Interpreting those numbers as decimal is 
surely a bug and should be fixed. I won't even complain when the workaround 
breaks. :-)


> files included with the  tag have fileMode 204
> 
>
> Key: MASSEMBLY-153
> URL: http://jira.codehaus.org/browse/MASSEMBLY-153
> Project: Maven 2.x Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 2.1
> Environment: linux
>Reporter: Paul Jungwirth
>Priority: Minor
>
> I'm trying to include files like this:
> 
>   
> README
> true
>   
>   
> src/blah
>   
> 
> I'm packaging them as both .tar.gz and .zip. In the tarball, the files wind 
> up with mode 0204:
> --wr--
> In the zip file, they wind up with mode 1204:
> --wr-T
> Using a  element of 644 does not fix the problem. This only happens 
> for files specified in , not . It happens whether I use 
> filtering or not.
> These are pretty weird modes. I don't think this is a duplicate of 
> MASSEMBLY-75. It's not just losing the mode I set; it's assigning a very 
> peculiar mode as if with a mind of its own.
> My umask is 0002.
> Paul

-- 
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-467) observe folder for changes which can trigger a build

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-467?page=all ]

Jesse McConnell updated CONTINUUM-467:
--

Component/s: Core system

> observe folder for changes which can trigger a build
> 
>
> Key: CONTINUUM-467
> URL: http://jira.codehaus.org/browse/CONTINUUM-467
> Project: Continuum
>  Issue Type: New Feature
>  Components: Core system
> Environment: all
>Reporter: yo
>Priority: Minor
>
> It would be nice if another way to trigger a build would be to observe a 
> folder for changes. everytime someone commits something back to the repo a 
> file is created in a folder which continuum observes and triggers the build 
> of the project by the name of the file. That was conitnuum does not have to 
> say query a hundreds svnrepos if something changed.
> Greetings
> Yo

-- 
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-977) Create web UI tests for "Add m1 & m2 projects" pages

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-977?page=all ]

Jesse McConnell updated CONTINUUM-977:
--

Component/s: Testing

> Create web UI tests for "Add m1 & m2 projects" pages
> 
>
> Key: CONTINUUM-977
> URL: http://jira.codehaus.org/browse/CONTINUUM-977
> Project: Continuum
>  Issue Type: Task
>  Components: Testing
>Reporter: Maria Odea Ching
> Assigned To: Maria Odea Ching
> Attachments: CONTINUUM-977-continuum-webapp-test.patch
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MDEPLOY-19) Ability to deploy-file as classifier

[Anagnostopoulos Kostis (JIRA)]

[ http://jira.codehaus.org/browse/MDEPLOY-19?page=comments#action_80124 ] 

Anagnostopoulos Kostis commented on MDEPLOY-19:
---

Hello,
I have the same problem as Stefan Hübner said:

The deploy goal does not take into consideration the  parameter.

We should either re-open this issue or file a new one!
What should we do?

Regards,
  Kostis

> Ability to deploy-file as classifier
> 
>
> Key: MDEPLOY-19
> URL: http://jira.codehaus.org/browse/MDEPLOY-19
> Project: Maven 2.x Deploy Plugin
>  Issue Type: New Feature
>Affects Versions: 2.1
> Environment: xp
>Reporter: Dan Tran
> Assigned To: Allan Ramirez
> Fix For: 2.2
>
> Attachments: MDEPLOY19.diff
>
>  Time Spent: 2 hours
>  Remaining Estimate: 0 minutes
>
> deploy-file currently does not support this option

-- 
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

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-660?page=all ]

Jesse McConnell updated CONTINUUM-660:
--

Component/s: Integration - Maven 2

> 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
>  Issue Type: Bug
>  Components: Integration - Maven 2
>Affects 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-860) multiple email addresses delimited with commas causes AddressException

[Jesse McConnell (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-860?page=all ]

Jesse McConnell updated CONTINUUM-860:
--

Fix Version/s: 1.1
  Component/s: Notifier - Mail

> multiple email addresses delimited with commas causes AddressException
> --
>
> Key: CONTINUUM-860
> URL: http://jira.codehaus.org/browse/CONTINUUM-860
> Project: Continuum
>  Issue Type: Bug
>  Components: Notifier - Mail
>Reporter: Adam Hardy
> Fix For: 1.1
>
>
> Email notification fails with a "javax.mail.internet.AddressException: 
> Illegal route-addr in string" exception when a comma-delimited list of email 
> addresses is used. 
> See the linked message for the pom.xml node for an example.
> There is a work-around, see this thread in user list 
> http://mail-archives.apache.org/mod_mbox/maven-continuum-users/200609.mbox/browser

-- 
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