date:20071001

[jira] Created: (DOXIA-157) Doxia Book doesn't work with xdoc source files

2007-10-01 Thread Lukas Theussl (JIRA)

Doxia Book doesn't work with xdoc source files
--

 Key: DOXIA-157
 URL: http://jira.codehaus.org/browse/DOXIA-157
 Project: Maven Doxia
  Issue Type: Bug
  Components: Book
Affects Versions: 1.0-alpha-9
Reporter: Lukas Theussl
 Fix For: 1.0-beta-1


Files with xml extension are parsed by the docbook parser. Doxia book doesn't 
recognize the standard Maven site structure to determine the site module.

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

[jira] Created: (CONTINUUM-1506) pages that are displayed while preparing and performing release should show more information

2007-10-01 Thread Tomislav Stojcevich (JIRA)

pages that are displayed while preparing and performing release should show 
more information


 Key: CONTINUUM-1506
 URL: http://jira.codehaus.org/browse/CONTINUUM-1506
 Project: Continuum
  Issue Type: Improvement
  Components: Release, Web - UI
Affects Versions: 1.1-beta-3
Reporter: Tomislav Stojcevich


Things like which group/project, what version it is releasing the development 
version is, what scm tag is being used to tag would be useful on that page and 
the page that is displayed when it's done.

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

[jira] Created: (CONTINUUM-1505) release perform page does not use defaults specified in pom for release plugin for goals and useReleaseProfile

2007-10-01 Thread Tomislav Stojcevich (JIRA)

release perform page does not use defaults specified in pom for release plugin 
for goals and useReleaseProfile
--

 Key: CONTINUUM-1505
 URL: http://jira.codehaus.org/browse/CONTINUUM-1505
 Project: Continuum
  Issue Type: Bug
  Components: Release
Affects Versions: 1.1-beta-3
Reporter: Tomislav Stojcevich


I would expect the defaults on the release prepare to be set to those defined 
in the pom for the release plugin, but they are not, they seem to be clean 
deploy with use Build Profile checked.

I turned off useBuilidProfile in the pom and have a different set of goals.

-- 
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-1492) error when trying to run data management tool when behind a proxied firewall

2007-10-01 Thread Tomislav Stojcevich (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108786
 ] 

Tomislav Stojcevich commented on CONTINUUM-1492:


not sure what kind of proxy i am using, i do know that i have to specify 
proxyHost, proxyPort, username and password.  This username and password is 
different from my windows username and password.

> error when trying to run data management tool when behind a proxied firewall
> 
>
> Key: CONTINUUM-1492
> URL: http://jira.codehaus.org/browse/CONTINUUM-1492
> Project: Continuum
>  Issue Type: Bug
>  Components: Data Management
>Affects Versions: 1.1-beta-3
>Reporter: Tomislav Stojcevich
>
> Using -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 
> -Dproxy.User=myuserid -Dhttp.proxyPassword=mypassword doesn't work
> Setting -Djava.net.useSystemProxies=true doesn't work
> Setting -Dhttp.auth.ntlm.domain=mydomain doesn't work
> Nor does it pick up the proxy settings in my settings.xml file.
> 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  - 
> Processing Continuum database...
> Exception in thread "main" 
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: 
> Missing:
> --
> 1) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.apache.maven.continuum 
> -DartifactId=data-management-jdo \
>   -Dversion=1.1-beta-3 -Dpackaging=jar -Dfile=/path/to/file
>   Path to dependency:
> 1) dummy:dummy:pom:1.0
> 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3
> --
> 1 required artifact is missing.
> for artifact:
>   dummy:dummy:pom:1.0
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243)
> at 
> org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:292)
> at 
> org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:173)
> at 
> org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:146)

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

[jira] Created: (CONTINUUM-1504) when autoVersionSubmodules=true is defined in the pom for the release plugin, the release prepare screen should not show or allow changing of child project versions

2007-10-01 Thread Tomislav Stojcevich (JIRA)

when autoVersionSubmodules=true is defined in the pom for the release plugin, 
the release prepare screen should not show or allow changing of child project 
versions


 Key: CONTINUUM-1504
 URL: http://jira.codehaus.org/browse/CONTINUUM-1504
 Project: Continuum
  Issue Type: Bug
  Components: Release
Affects Versions: 1.1-beta-3
Reporter: Tomislav Stojcevich


90% of the time the defaults for the versions are correct, however when I need 
to use a different value i have to make the change in too many places on the 
screen.  when using the release plugin, it only asks me for the parent versions 
and propgates them down automatically.  i would assume the release prepare 
screen would do the same and not have inputs available to put in child pom 
versions.

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

[jira] Created: (CONTINUUM-1503) scm release tag default should match what the release plugin uses

2007-10-01 Thread Tomislav Stojcevich (JIRA)

scm release tag default should match what the release plugin uses
-

 Key: CONTINUUM-1503
 URL: http://jira.codehaus.org/browse/CONTINUUM-1503
 Project: Continuum
  Issue Type: Bug
  Components: Release
Affects Versions: 1.1-beta-3
Reporter: Tomislav Stojcevich


The release plugin gives a default scm tag to used when doing a 
release:prepare, continuum's release prepare does not use the same value.

I happen to be on a branch so in continuum my project's scm tag is the branch 
name. (using cvs).

When i went to release prepare, the tag default was the existing value in the 
pom for the scm tag.  I didn't change it and when the project finished the 
prepare, there was nothing tagged (because the tag it tried to use was the same 
name as the branch I was on).

The release plugin uses a different default and doesn't create this problem.

-- 
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-448) validation for reports form

2007-10-01 Thread Joakim Erdfelt (JIRA)


[ 
http://jira.codehaus.org/browse/MRM-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108784
 ] 

Joakim Erdfelt commented on MRM-448:


Started some of the validation.
Can't get the validation messages to stay through a "redirect-action".

> validation for reports form
> ---
>
> Key: MRM-448
> URL: http://jira.codehaus.org/browse/MRM-448
> Project: Archiva
>  Issue Type: Bug
>  Components: web application
>Affects Versions: 1.0-beta-1
>Reporter: Brett Porter
> Fix For: 1.0-beta-3
>
>
> validation is missing - see MRM-329

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

[jira] Created: (CONTINUUM-1502) After changing the name of a project group, the project dissapears and is not accessible, not even by the admin user.

2007-10-01 Thread Iker Almandoz (JIRA)

After changing the name of a project group, the project dissapears and is not 
accessible, not even by the admin user.
-

 Key: CONTINUUM-1502
 URL: http://jira.codehaus.org/browse/CONTINUUM-1502
 Project: Continuum
  Issue Type: Bug
Affects Versions: 1.1-beta-3
 Environment: Linux CentOS4, Maven2.0.7, Java-5
Reporter: Iker Almandoz
Priority: Minor


In the project view for a given project, if i change the name of the project 
(project group name), then the project disappears and is not accessible from 
continuum.
Not even the admin can see it... 

I have changed the project name from "name" to "name " in my test.

I was able to recover the projects by directly connecting to the derby database 
and updating the projectgroup table doing
>update projectgroup set name='name' where name='name ';



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

[jira] Commented: (MSITE-253) NoClassDefFoundError for org/codehaus/plexus/util/xml/XmlStreamReader

2007-10-01 Thread Pablo Gutierrez (JIRA)


[ 
http://jira.codehaus.org/browse/MSITE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108782
 ] 

Pablo Gutierrez commented on MSITE-253:
---

I have tried snapshot with date #Sat Sep 08 19:35:16 CEST 2007
And I got a similar message

-
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Internal error in the plugin manager executing goal 
'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site': Unabl
e to find the mojo 
'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site' in the 
plugin 'org.apache.maven.plugins:maven-
site-plugin'
org/apache/maven/doxia/site/decoration/LinkItem
[INFO] 
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the 
plugin manager executing goal 'org.apache.maven.plugins:m
aven-site-plugin:2.0-beta-6-SNAPSHOT:site': Unable to find the mojo 
'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:sit
e' in the plugin 'org.apache.maven.plugins:maven-site-plugin'
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:543)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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.PluginManagerException: Unable to find the 
mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-beta
-6-SNAPSHOT:site' in the plugin 'org.apache.maven.plugins:maven-site-plugin'
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
Unable to lookup component 'org.apache.maven.pl
ugin.Mojoorg.apache.maven.plugins:maven-site-plugin:2.0-beta-6-SNAPSHOT:site', 
it could not be created
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at 
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562)
... 18 more
Caused by: 
org.codehaus.plexus.component.factory.ComponentInstantiationException: Could 
not instanciate component: role: 'null', implem
entation: 'org.apache.maven.plugins.site.SiteMojo'
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
at 
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
at 
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
at 
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
at 
org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
... 20 more
Caused by: java.lang.NoClassDefFoundError: 
org/apache/maven/doxia/site/decoration/LinkItem
at java.lang.Class.getDeclaredCons

[jira] Closed: (MRM-428) managed and remote repositories with same name causes problems

2007-10-01 Thread Joakim Erdfelt (JIRA)


 [ 
http://jira.codehaus.org/browse/MRM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joakim Erdfelt closed MRM-428.
--

  Assignee: Joakim Erdfelt
Resolution: Fixed

Closing jira, as recent changes to the repository admin/config screens now 
prevents this from occuring.

> managed and remote repositories with same name causes problems
> --
>
> Key: MRM-428
> URL: http://jira.codehaus.org/browse/MRM-428
> Project: Archiva
>  Issue Type: Bug
>Affects Versions: 1.0-alpha-2
>Reporter: Eli Miller
>Assignee: Joakim Erdfelt
>Priority: Critical
> Fix For: 1.0-beta-3
>
>
> I created both a managed and remote repository entry with the name central -- 
> the intent was for one to proxy the other.  The administrative interfaces did 
> not gripe about using duplicate names but the proxy did not seem to work.  In 
> the logs I found the following information (which looked suspect):
> 328579 [SocketListener0-1] DEBUG 
> org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default  - 
> Attempting connector: ProxyConnector[
>   source:ArchivaRepository[central,file:/u01/home/proj/.repos/central/]
>   target:ArchivaRepository[central,file:/u01/home/proj/.repos/central/]
>   proxyId:mpare
>   policy[releases]:once
>   policy[checksum]:fix
>   policy[snapshots]:disabled
>   policy[cache-failures]:ignored
> ]
> When I requested that the remote central repository be deleted, the managed 
> repository entry was deleted instead.  After I removed all central 
> repositories I created a managed repository named central and a remote 
> repository named centralExt and the proxying seemed to work as expected.

-- 
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-1466) Project name accepts blank spaces when edited in Project Summary > Members Tab > Edit Project

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1466:


 Assignee: Olivier Lamy
Affects Version/s: (was: Future)
   1.1-beta-1
   1.1-beta-2
   1.1-beta-3
Fix Version/s: 1.1-beta-4

> Project name accepts blank spaces when edited in Project Summary > Members 
> Tab > Edit Project
> -
>
> Key: CONTINUUM-1466
> URL: http://jira.codehaus.org/browse/CONTINUUM-1466
> Project: Continuum
>  Issue Type: Bug
>  Components: Web - UI
>Affects Versions: 1.1-beta-1, 1.1-beta-2, 1.1-beta-3
> Environment: firefox 2, ubuntu 
>Reporter: jan ancajas
>Assignee: Olivier Lamy
>Priority: Trivial
> Fix For: 1.1-beta-4
>
>
> Steps:
> 1. Login as admin
> 2. Add a Maven Two Project with project group defined by pom
> 3. In the group summary page, click the project group of the project you've 
> just added
> 4. When the project group summary page is loaded, click on the Members tab
> 5. In the Project Group Members page, click the Edit Project icon of the 
> project that you've just added
> 6. Once in the Edit Project page, replace the project name with empty spaces 
> and click the Save button
> 7. You will be redirected to the Project Information page, and you will see 
> that the project name is now blank.

-- 
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-1492) error when trying to run data management tool when behind a proxied firewall

2007-10-01 Thread Olivier Lamy (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108776
 ] 

Olivier Lamy commented on CONTINUUM-1492:
-

I need more information on your proxy : what kind of proxy are you using ?
Because I have done this on a solaris machine using a windows proxy with auth 
(only -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80) and was working fine.

> error when trying to run data management tool when behind a proxied firewall
> 
>
> Key: CONTINUUM-1492
> URL: http://jira.codehaus.org/browse/CONTINUUM-1492
> Project: Continuum
>  Issue Type: Bug
>  Components: Data Management
>Affects Versions: 1.1-beta-3
>Reporter: Tomislav Stojcevich
>
> Using -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 
> -Dproxy.User=myuserid -Dhttp.proxyPassword=mypassword doesn't work
> Setting -Djava.net.useSystemProxies=true doesn't work
> Setting -Dhttp.auth.ntlm.domain=mydomain doesn't work
> Nor does it pick up the proxy settings in my settings.xml file.
> 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  - 
> Processing Continuum database...
> Exception in thread "main" 
> org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: 
> Missing:
> --
> 1) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=org.apache.maven.continuum 
> -DartifactId=data-management-jdo \
>   -Dversion=1.1-beta-3 -Dpackaging=jar -Dfile=/path/to/file
>   Path to dependency:
> 1) dummy:dummy:pom:1.0
> 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3
> --
> 1 required artifact is missing.
> for artifact:
>   dummy:dummy:pom:1.0
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243)
> at 
> org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:292)
> at 
> org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:173)
> at 
> org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:146)

-- 
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-1494) Maximum length for name column exceeded in makeAndStoreBuildResult

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1494:


Fix Version/s: 1.1-beta-4

> Maximum length for name column exceeded in makeAndStoreBuildResult
> --
>
> Key: CONTINUUM-1494
> URL: http://jira.codehaus.org/browse/CONTINUUM-1494
> Project: Continuum
>  Issue Type: Bug
>  Components: Database
>Affects Versions: 1.1-beta-2
>Reporter: André Næss
> Fix For: 1.1-beta-4
>
> Attachments: maxlength.patch
>
>
> This bug is similar to a bunch of other bugs like this, it seems the data 
> model has been consistently designed with too few characters in the name 
> field. This particular bugs occurs when Continuum tries to store the test 
> results (SuiteResult in the model). Using -Dmaven.test.skip=true made the 
> problem disappear.
> I've attached a very simple fix for the problem, however, I note that 
> TestCaseFailure has no stash.maxSize set, and as soon as my Test breaks it 
> will probably crash with the same problem.
> Here's the stack trace:
> 863290102 [Thread-6] ERROR 
> org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project  - 
> Error executing task
> edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: 
> javax.jdo.JDOFatalUserException: Attempt to store value 
> "/new-web/newweb-erp-integration/trunk/src/main/ja
> va/com/pointcarbon/erp/agresso/domain/agressostatus/AcuhistrStatus.java (from 
> /new-web/newweb-erp-integration/trunk/src/main/java/com/pointcarbon/erp/agresso/domain/agressos
> tatus/AcuhistrStatusEnum.java:4297)" in column ""NAME"" that has maximum 
> length of 255. Please correct your data!
> at 
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
> at 
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
> at 
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:159)
> at 
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:127)
> Caused by: javax.jdo.JDOFatalUserException: Attempt to store value 
> "/new-web/newweb-erp-integration/trunk/src/main/java/com/pointcarbon/erp/agresso/domain/agressostatus/Acuh
> istrStatus.java (from 
> /new-web/newweb-erp-integration/trunk/src/main/java/com/pointcarbon/erp/agresso/domain/agressostatus/AcuhistrStatusEnum.java:4297)"
>  in column ""NAME""
> that has maximum length of 255. Please correct your data!
> at 
> org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214)
> at 
> org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203)
> at 
> org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122)
> at 
> org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757)
> at 
> org.apache.maven.continuum.model.scm.ChangeFile.jdoProvideField(ChangeFile.java)
> at 
> org.apache.maven.continuum.model.scm.ChangeFile.jdoProvideFields(ChangeFile.java)
> at 
> org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115)
> at 
> org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252)
> at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519)
> at org.jpox.store.StoreManager.insert(StoreManager.java:920)
> at 
> org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667)
> at 
> org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646)
> at 
> org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198)
> at 
> org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243)
> at 
> org.jpox.store.rdbms.scostore.FKListStore.validateElementForWriting(FKListStore.java:1231)
> at 
> org.jpox.store.rdbms.scostore.FKListStore.internalAdd(FKListStore.java:772)
> at 
> org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:386)
> at 
> org.jpox.store.mapping.CollectionMapping.postInsert(CollectionMapping.java:209)
> at 
> org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:464)
> at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519)
> at org.jpox.store.StoreManager.insert(StoreManager.java:920)
> at 
> org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667)
> at 
> org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646)
> at 
> org.jpox.AbstractPersis

[jira] Updated: (CONTINUUM-1487) should not be allowed to delete a build result that is still executing

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1487:


Fix Version/s: 1.1-beta-4

Sure we have to add a confirmation page for Delete Build Result(s)

> should not be allowed to delete a build result that is still executing
> --
>
> Key: CONTINUUM-1487
> URL: http://jira.codehaus.org/browse/CONTINUUM-1487
> Project: Continuum
>  Issue Type: Bug
>Affects Versions: 1.1-beta-3
>Reporter: Brett Porter
> Fix For: 1.1-beta-4
>
>
> note that deleting the build result from on the build result page also seems 
> to skip confirmation. All I did was hit the space bar...

-- 
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-1482) XmlRpc API - add method buildAll(...) to ProjectGroupSummary

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1482:


Fix Version/s: 1.1-beta-4

> XmlRpc API - add method buildAll(...)  to ProjectGroupSummary
> -
>
> Key: CONTINUUM-1482
> URL: http://jira.codehaus.org/browse/CONTINUUM-1482
> Project: Continuum
>  Issue Type: New Feature
>Affects Versions: 1.1-beta-2
>Reporter: Amine ZAROUK
> Fix For: 1.1-beta-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] Updated: (CONTINUUM-1474) At the time of an addition of new BuildDefinition with XmlRPC client, the automatically generated buildDefinitionID cannot be recovered

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1474:


Fix Version/s: 1.1-beta-4

> At the time of an addition of new BuildDefinition with XmlRPC client, the 
> automatically generated buildDefinitionID cannot be recovered
> ---
>
> Key: CONTINUUM-1474
> URL: http://jira.codehaus.org/browse/CONTINUUM-1474
> Project: Continuum
>  Issue Type: Bug
>Affects Versions: 1.1-beta-2
> Environment: widows with maven 2.0.4
>Reporter: Amine ZAROUK
> Fix For: 1.1-beta-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] Updated: (CONTINUUM-1461) add surefire results to mail notifications on failure

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1461:


Fix Version/s: 1.1-beta-4

IMHO only failing test(s) is enough.

> add surefire results to mail notifications on failure
> -
>
> Key: CONTINUUM-1461
> URL: http://jira.codehaus.org/browse/CONTINUUM-1461
> Project: Continuum
>  Issue Type: New Feature
>  Components: Notifier - Mail
>Reporter: Teodoro Cue Jr.
> Fix For: 1.1-beta-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] Updated: (CONTINUUM-1457) add failures from surefire report directly to the build output page, using the link only for the full report

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1457:


Fix Version/s: 1.1-beta-4

> add failures from surefire report directly to the build output page, using 
> the link only for the full report
> 
>
> Key: CONTINUUM-1457
> URL: http://jira.codehaus.org/browse/CONTINUUM-1457
> Project: Continuum
>  Issue Type: New Feature
>  Components: Web - UI
>Reporter: Teodoro Cue Jr.
> Fix For: 1.1-beta-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] Updated: (CONTINUUM-1403) Error on edit project group page

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy updated CONTINUUM-1403:


 Assignee: Emmanuel Venisse
Fix Version/s: 1.1-beta-4

Emmanuel : can you confirm it was a bad db entry after migration ?

> Error on edit project group page
> 
>
> Key: CONTINUUM-1403
> URL: http://jira.codehaus.org/browse/CONTINUUM-1403
> Project: Continuum
>  Issue Type: Bug
>  Components: Web interface
> Environment: 
> http://vmbuild1.apache.org/continuum/editProjectGroup.action
>Reporter: Henri Yandell
>Assignee: Emmanuel Venisse
> Fix For: 1.1-beta-4
>
> Attachments: CONTINUUM-1403.trace
>
>
> When clicking Edit on the Group page

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

[jira] Closed: (CONTINUUM-1452) Show a summary total of the Projects and Build Status columns on the Project Groups page

2007-10-01 Thread Olivier Lamy (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy closed CONTINUUM-1452.
---

Resolution: Fixed

Patch commited in rev 581085 with moving inline css to extremecomponents.css.
Thanks.

> Show a summary total of the Projects and Build Status columns on the Project 
> Groups page
> 
>
> Key: CONTINUUM-1452
> URL: http://jira.codehaus.org/browse/CONTINUUM-1452
> Project: Continuum
>  Issue Type: Wish
>  Components: Web - UI
>Affects Versions: 1.1-beta-2
>Reporter: Tomislav Stojcevich
>Assignee: Olivier Lamy
>Priority: Minor
> Fix For: 1.1-beta-4
>
> Attachments: CONTINUUM-1452, CONTINUUM-1452-continuum-webapp.patch, 
> Project Group with totals.jpg, screenshot-1.jpg
>
>
> It would be nice to see a summary total of all of the projects and the status 
> displayed at the bottom of the the Projects and Build Status columns on the 
> Project Groups page.

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

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

2007-10-01 Thread Dennis Lundberg (JIRA)


[ 
http://jira.codehaus.org/browse/MSITE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108761
 ] 

Dennis Lundberg commented on MSITE-91:
--

Yes, 2.0-beta-6-SNAPSHOT

> "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
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-6
>
> 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] Issue Comment Edited: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108758
 ] 

Tionan Lim edited comment on MECLIPSE-264 at 10/1/07 2:34 PM:
--

MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin
  
true 
2.0




 was:
MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin

 
true 
2.0



> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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] Issue Comment Edited: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108758
 ] 

Tionan Lim edited comment on MECLIPSE-264 at 10/1/07 2:34 PM:
--

MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin

 
true 
2.0




 was:
MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin
 
true 
2.0



> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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] Issue Comment Edited: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108758
 ] 

Tionan Lim edited comment on MECLIPSE-264 at 10/1/07 2:33 PM:
--

MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin
 
true 
2.0




 was:
MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin
 
true 
2.0



> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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] Issue Comment Edited: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108758
 ] 

Tionan Lim edited comment on MECLIPSE-264 at 10/1/07 2:32 PM:
--

MECLIPSE-264-NEW patch is based on the maven-264 patch.

Sample configuration:


org.apache.maven.plugins
maven-eclipse-plugin
 
true 
2.0




 was:
MECLIPSE-264-NEW patch is based on the maven-264 patch.

> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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] Issue Comment Edited: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108758
 ] 

Tionan Lim edited comment on MECLIPSE-264 at 10/1/07 2:31 PM:
--

MECLIPSE-264-NEW patch is based on the maven-264 patch.


 was:
Based on the maven-264 patch.

> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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] Issue Comment Edited: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


[ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108758
 ] 

Tionan Lim edited comment on MECLIPSE-264 at 10/1/07 2:27 PM:
--

Based on the maven-264 patch.


 was:
Based on the MECLIPSE-264 patch.

> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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: (MECLIPSE-264) Support for WTP2.0

2007-10-01 Thread Tionan Lim (JIRA)


 [ 
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tionan Lim updated MECLIPSE-264:


Attachment: MECLIPSE-264-NEW.patch

Based on the MECLIPSE-264 patch.

> Support for WTP2.0
> --
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
>  Issue Type: Improvement
>  Components: WTP support
>Affects Versions: 2.4
>Reporter: Geir Pettersen
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: maven-264.patch, MECLIPSE-264-NEW.patch
>
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while 
> WTP 2.0 is already released in milestone 6

-- 
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: (MANTLR-23) Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code

2007-10-01 Thread Kenny MacDermid (JIRA)


 [ 
http://jira.codehaus.org/browse/MANTLR-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kenny MacDermid closed MANTLR-23.
-

Resolution: Incomplete

Sorry, this patch was/is for antlr3-maven-plugin.  Posted to the wrong list.

Thanks

> Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to 
> generate test code
> 
>
> Key: MANTLR-23
> URL: http://jira.codehaus.org/browse/MANTLR-23
> Project: Maven 2.x Antlr Plugin
>  Issue Type: Improvement
>Reporter: Kenny MacDermid
>Priority: Minor
> Attachments: refactor.patch
>
>
> Currently Antlr3PluginMojo generates source to generated-source/antlr.  This 
> is fine for regular code, but doesn't work so well with antlr test code.
> Instead refactor to a base class and have AntlrMojo generate the source for 
> main code to generated-source/antlr/main, so that later a goal can be created 
> to generate-test-source to generated-source/antlr/test.

-- 
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: (SUREFIRE-349) redirectTestOutputToFile truncates summary information

2007-10-01 Thread Jason T. Greene (JIRA)


[ 
http://jira.codehaus.org/browse/SUREFIRE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108745
 ] 

Jason T. Greene commented on SUREFIRE-349:
--

Strike that. The 2.3.X does not work on all platforms. I am seeing failures in 
Windows.

> redirectTestOutputToFile truncates summary information
> --
>
> Key: SUREFIRE-349
> URL: http://jira.codehaus.org/browse/SUREFIRE-349
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Jason T. Greene
> Fix For: 2.3.1
>
>
> In the current 2.4-SNAPSHOT, Instead of the normally expected
> ---
>  T E S T S
> ---
> Running org.jboss.cache.FqnTest
> Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.439 sec
> Results :
> Tests run: 26, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> You get:
> ---
>  T E S T S
> ---
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [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] Created: (MINSTALL-42) classifier seems to be ignored

2007-10-01 Thread Brill Pappin (JIRA)

classifier seems to be ignored
--

 Key: MINSTALL-42
 URL: http://jira.codehaus.org/browse/MINSTALL-42
 Project: Maven 2.x Install Plugin
  Issue Type: Bug
Affects Versions: 2.1
 Environment: Maven  2.0.7. I'm unsure of the specific plugin version.
Reporter: Brill Pappin
Priority: Blocker


install-file is failing to take into account the classifier option... this used 
to work (as of last week) but is being ignored when I do the same thing again.
The repo structure its using is incorrect.

That or possible maven has changed the way that classifier is used.



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

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

2007-10-01 Thread Pablo Gutierrez (JIRA)


[ 
http://jira.codehaus.org/browse/MSITE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108742
 ] 

Pablo Gutierrez commented on MSITE-91:
--

Is there a snapshot version that includes this fix?

Thanks,
Pablo

> "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
>Assignee: Dennis Lundberg
> Fix For: 2.0-beta-6
>
> 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] Created: (MSITE-258) Deployment on network drive for multi-modules fails for modules sites

2007-10-01 Thread Romain Linsolas (JIRA)

Deployment on network drive for multi-modules fails for modules sites
-

 Key: MSITE-258
 URL: http://jira.codehaus.org/browse/MSITE-258
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
  Components: inheritance, multi module, site:deploy
Affects Versions: 2.0-beta-5
 Environment: Windows, Maven 2.0.5, site plugin version 2.0-beta-5
Reporter: Romain Linsolas
Priority: Minor


I work on a project with several modules, for example :
myproject
  + commons
  + business
  + ...

(myproject is also the parent project for all modules)

In the parent pom.xml, I define the distribution management in order to deploy 
my whole site on a network drive (which is not mapped):



website
file://yyy/sites/my-site



When I deploy the whole site (command mvn site-deploy run on the parent 
directory), the "core" site is correctly deployed on my network drive, but all 
modules are deployed on my C: drive (in the directory 
C:\\y\sites\my-site\...).

As the core site is correctly deployed, I think the problem is that the 
deployment URL is not correctly given to all project children. Maybe it is a 
Maven bug, not a Site Plugin problem?

The only way to make the deployment works correctly is to redefine, for each 
modules, the distributionManagement!

Note that this problem does not occur if the network drive is mapped (for 
example if the distribution URL is something like "F:/sites/my-site/").


-- 
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-1742) please upload rhino javascript engine modified by the Dojo team

2007-10-01 Thread nicolas de loof (JIRA)

please upload rhino javascript engine modified by the Dojo team
---

 Key: MAVENUPLOAD-1742
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1742
 Project: maven-upload-requests
  Issue Type: Improvement
Reporter: nicolas de loof


dojotoolkit use a customized rhino engine for javascript compression


-- 
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-22) Error deploying artifact: Unable to create directory

2007-10-01 Thread Barış Efe (JIRA)


[ 
http://jira.codehaus.org/browse/WAGONFTP-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108738
 ] 

Barış Efe commented on WAGONFTP-22:
-

Hi,
I was suffering with the same issue and I find the solution after some ftp 
server debug.
I am using proftpd and there was no 

DefaultRoot ~
 
line on my 
/etc/proftpd/proftpd.conf

So when you try to run 
#mvn deploy

you can see "CWD /" command on the server side and if you do not have 
DefaultRoot ~
it really goes to file system root and you get
[INFO] Error deploying artifact: Unable to create directory org
error that you do not get on normal ftp(Because you do not run #dir / command.).

Hope this help to you and others.

> Error deploying artifact: Unable to create directory
> 
>
> Key: WAGONFTP-22
> URL: http://jira.codehaus.org/browse/WAGONFTP-22
> Project: wagon-ftp
>  Issue Type: Bug
>Affects Versions: 1.0-alpha-6
> Environment: maven-2.0.6
> Windows XP SP2
>Reporter: troy ronning
>
> I'm trying to deploy a project and receiving error below.
> .
> [INFO] [deploy:deploy]
> altDeploymentRepository = test.ftp::default::ftp://
> [INFO] Using alternate deployment repository test.ftp::default::ftp://
> [INFO] Retrieving previous build number from test.ftp
> [DEBUG] repository metadata for: 'snapshot org.test:foo:1.0-SNAPSHOT' could 
> not be found on repository: test.ftp
> Uploading: ftp:///org/test/foo/1.0-SNAPSHOT/foo-1.0-SNAPSHOT.jar
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Error deploying artifact: Unable to create directory org
> [INFO] 
> 
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying 
> artifact: Unable to create directory org
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying 
> artifact: Unable to create directory org
>   at 
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>   ... 16 more
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: 
> Error deploying artifact: Unable to create directory org
>   at 
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>   at 
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
>   ... 18 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Unable to create 
> directory org
>   at 
> org.apache.maven.wagon.providers.ftp.FtpWagon.fillOutputData(FtpWagon.java:264)
>   at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133)
>   at 
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:237)
>   at 
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:153)
>   at 
> org.apache.maven

[jira] Closed: (CONTINUUM-1495) Calling getAllProjectGroups() fails

2007-10-01 Thread Emmanuel Venisse (JIRA)


 [ 
http://jira.codehaus.org/browse/CONTINUUM-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Emmanuel Venisse closed CONTINUUM-1495.
---

  Assignee: Emmanuel Venisse
Resolution: Fixed

> Calling getAllProjectGroups() fails
> ---
>
> Key: CONTINUUM-1495
> URL: http://jira.codehaus.org/browse/CONTINUUM-1495
> Project: Continuum
>  Issue Type: Bug
>  Components: XMLRPC Interface
>Affects Versions: 1.1-beta-3
> Environment: Server (with continuum): Windows Server 2003,Java 
> 1.5.0_11-b03
> Client: Maven2 java project (sourcelevel 1.5) dependent upon 
> org.apache.maven.continuum:continuum-xmlrpc-client:1.1-beta-3
>Reporter: Steven Cummings
>Assignee: Emmanuel Venisse
> Fix For: 1.1-beta-4
>
>
> Trying this:
> final ContinuumXmlRpcClient client = new 
> ContinuumXmlRpcClient(new URL("http://myserver:8080/continuum/xmlrpc";), "me", 
> "my passwd");
> for (final Iterator projectGroupIterator = 
> client.getAllProjectGroups().iterator(); projectGroupIterator.hasNext();)
> {
> final ProjectGroupSummary projectGroup = 
> (ProjectGroupSummary) projectGroupIterator.next();
> System.out.println(projectGroup.getName());
> }
> I get this:
> java.lang.RuntimeException: org.apache.maven.continuum.ContinuumException: 
> The remote method failed.
>   at 
> com.cerner.msvc.orders.continuum.InstallProjectsTest.testGetAllProjectGroups(InstallProjectsTest.java:66)
>   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 junit.framework.TestCase.runTest(TestCase.java:154)
>   at junit.framework.TestCase.runBare(TestCase.java:127)
>   at junit.framework.TestResult$1.protect(TestResult.java:106)
>   at junit.framework.TestResult.runProtected(TestResult.java:124)
>   at junit.framework.TestResult.run(TestResult.java:109)
>   at junit.framework.TestCase.run(TestCase.java:118)
>   at 
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
>   at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: org.apache.maven.continuum.ContinuumException: The remote method 
> failed.
>   at 
> org.apache.maven.continuum.xmlrpc.client.ContinuumXmlRpcClient.getAllProjectGroups(ContinuumXmlRpcClient.java:211)
>   at 
> com.cerner.msvc.orders.continuum.InstallProjectsTest.testGetAllProjectGroups(InstallProjectsTest.java:58)
>   ... 16 more
> Caused by: org.apache.xmlrpc.XmlRpcException: Failed to invoke method 
> getAllProjectGroups in class 
> org.apache.maven.continuum.xmlrpc.server.ContinuumServiceImpl: You have just 
> attempted to access field "projects" yet this field was not detached when you 
> detached the object. Either dont access this field, or detach the field when 
> detaching the object.
>   at 
> org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(XmlRpcStreamTransport.java:184)
>   at 
> org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:145)
>   at 
> org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:94)
>   at 
> org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:39)
>   at 
> org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:53)
>   at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166)
>   at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136)
>   at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125)
>   at 
> org.apache.xmlrpc.client.util.ClientFactory$1.invoke(ClientFactory.java:104)
>   at $Proxy0.getAllProjectGroups(Unknown Source)
>   at 
> org.apache.maven.continuum.xmlrpc.client.ContinuumXmlRpcClient.getAllProjectGroups(ContinuumXmlRpcClient.java:207)
>   ... 17 more

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

[jira] Commented: (MAVENUPLOAD-1739) New version of XINS for Maven2 repository

2007-10-01 Thread Anthony Goubard (JIRA)


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108726
 ] 

Anthony Goubard commented on MAVENUPLOAD-1739:
--

Yes I've read the information of how to supply jars.

The pom and the jars are included in the jar file.
e.g. xins-server-2.1.jar includes
xins-server-2.1-javadoc.jar, xins-server-2.1-sources.jar, xins-server-2.1.jar 
and pom.xml

Is there something wrong in my packages? (it used to work for the previous 
releases)

Best regards,
Anthony

> New version of XINS for Maven2 repository
> -
>
> Key: MAVENUPLOAD-1739
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1739
> Project: maven-upload-requests
>  Issue Type: Task
>Reporter: Anthony Goubard
>
> Hi,
> Here are new JAR file that I'd like to have uploaded in Maven:
> http://xins.sourceforge.net/maven/xins-server-2.1.jar
> http://xins.sourceforge.net/maven/xins-common-2.1.jar
> http://xins.sourceforge.net/maven/xins-client-2.1.jar
> http://xins.sourceforge.net/maven/logdoc-2.1.jar
> Kind regards,
> Anthony

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

37 matches

Mail list logo