[jira] Created: (SUREFIRE-290) [PATCH] Forking to java 1.3 not working when using relative paths in modules.
[PATCH] Forking to java 1.3 not working when using relative paths in modules.
-
Key: SUREFIRE-290
URL: http://jira.codehaus.org/browse/SUREFIRE-290
Project: Maven Surefire
Issue Type: Bug
Environment: WinXp + Java 1.3
Reporter: Mark Holster
Attachments: no-relative-classpath-urls.patch
For a java 1.3 multi-module project we use a construction like
{code:xml}
..\mymodule1
..\..\mymodule2
{code}
The testcases work fine if maven is started in the modules, but when running
from the aggegator pom a ClassNotFoundException on any testcase will occur.
The attached patch add canonnical paths to the classpath if a given path is
absolute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-1181) Continuum aborts when running Postgres under JBoss
[
http://jira.codehaus.org/browse/CONTINUUM-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88323
]
Emmanuel Venisse commented on CONTINUUM-1181:
-
You can try to uncomment the following code in your application.xml (Note: it
is in two places in application.xml)
{code:xml}
org.jpox.identifier.case
PreserveCase
{code}
And remove your database before to restart continuum
> Continuum aborts when running Postgres under JBoss
> --
>
> Key: CONTINUUM-1181
> URL: http://jira.codehaus.org/browse/CONTINUUM-1181
> Project: Continuum
> Issue Type: Bug
> Components: Database
>Affects Versions: 1.1
> Environment: MS Windows XP Pro SP2
> postgres 8.1.4-1 with JDBC Driver postgresql-8.1-408.jdbc3
> JBoss 4.0.5.GA
>Reporter: thierry lach
>
> I'm trying to get Continuum to store its data in a postgres database while
> running under JBoss and I'm getting an exception. It seems that someone is
> trying to change the transaction isolation during a transaction.
> Excerpt from JBoss logs follows...
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> - Starting Continuum.
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> - < Continuum 1.1-SNAPSHOT started! >
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> - ---
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> -\ ^__^
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> - \ (oo)\___
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> -(__)\ )\/\
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> -||w |
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum
> -|| ||
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -
> 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum -
> 2007-02-21 12:56:02,613 [ScannerThread] INFO ContinuumInitializer:default
> - Continuum initializer running ...
> 2007-02-21 12:56:02,644 [ScannerThread] WARN LocalManagedConnectionFactory
> - Error resetting transaction isolation
> org.postgresql.util.PSQLException: Cannot change transaction isolation level
> in the middle of a transaction.
> at
> org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection.java:733)
> at
> org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.cleanup(BaseWrapperManagedConnection.java:189)
> at
> org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java
> :320)
> at
> org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.returnConnection(JBossManagedConnectionPool.java:620)
> at
> org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection
> (BaseConnectionManager2.java:363)
> at
> org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:623)
> at
> org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle
> (BaseWrapperManagedConnection.java:266)
> at
> org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> at
> org.jpox.store.rdbms.adapter.DatabaseAdapter.getConnection(DatabaseAdapter.java
> :928)
> at
> org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTransaction.java:324)
> at
> org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:356)
> at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached
> (PlexusJdoUtils.java:346)
> at
> org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302)
> at
> org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(
> JdoContinuumStore.java:1287)
> at
> org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1282)
> at
> org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached
> (JdoContinuumStore.java:1277)
> at
> org.apache.maven.continuum.store.JdoContinuumStore.getSystemConfiguration(JdoContinuumStore.java:1375)
> at
> org.apache.maven.continuum.initialization.DefaultContinuumInitializer.initialize
> (DefaultContinuumInitializer.java:90)
> at
> org.apache.maven.continuum.Defaul
[jira] Created: (CONTINUUM-1182) Pass configured scm username and password to execution of maven goals
Pass configured scm username and password to execution of maven goals
-
Key: CONTINUUM-1182
URL: http://jira.codehaus.org/browse/CONTINUUM-1182
Project: Continuum
Issue Type: Improvement
Components: Core system
Reporter: Jan Edelbroek
It's possible to configure a scm username and password. Continuum uses this to
update the sourcecode from the scm before the actual build takes place.
Because of this feature, i don't have to configure this in my project pom for
maven2.
It would be nice if i could use these username and password also for executing
maven goals.
For example, if i use the scm:tag goal in my build definition, it would be nice
to have something like this in my maven2 build definition:
clean install scm:tag -Dusername=${scm.username} -Dpassword=${scm.password}
In this case, continuum should substitute the configured scm username and
password before executing the 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] Closed: (CONTINUUM-1182) Pass configured scm username and password to execution of maven goals
[
http://jira.codehaus.org/browse/CONTINUUM-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed CONTINUUM-1182.
---
Resolution: Won't Fix
The best way is to use properties defined in settings.xml
> Pass configured scm username and password to execution of maven goals
> -
>
> Key: CONTINUUM-1182
> URL: http://jira.codehaus.org/browse/CONTINUUM-1182
> Project: Continuum
> Issue Type: Improvement
> Components: Core system
>Reporter: Jan Edelbroek
>
> It's possible to configure a scm username and password. Continuum uses this
> to update the sourcecode from the scm before the actual build takes place.
> Because of this feature, i don't have to configure this in my project pom for
> maven2.
> It would be nice if i could use these username and password also for
> executing maven goals.
> For example, if i use the scm:tag goal in my build definition, it would be
> nice to have something like this in my maven2 build definition:
> clean install scm:tag -Dusername=${scm.username} -Dpassword=${scm.password}
> In this case, continuum should substitute the configured scm username and
> password before executing the 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] Commented: (CONTINUUM-1182) Pass configured scm username and password to execution of maven goals
[
http://jira.codehaus.org/browse/CONTINUUM-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88325
]
Emmanuel Venisse commented on CONTINUUM-1182:
-
and configure the plugin with them
> Pass configured scm username and password to execution of maven goals
> -
>
> Key: CONTINUUM-1182
> URL: http://jira.codehaus.org/browse/CONTINUUM-1182
> Project: Continuum
> Issue Type: Improvement
> Components: Core system
>Reporter: Jan Edelbroek
>
> It's possible to configure a scm username and password. Continuum uses this
> to update the sourcecode from the scm before the actual build takes place.
> Because of this feature, i don't have to configure this in my project pom for
> maven2.
> It would be nice if i could use these username and password also for
> executing maven goals.
> For example, if i use the scm:tag goal in my build definition, it would be
> nice to have something like this in my maven2 build definition:
> clean install scm:tag -Dusername=${scm.username} -Dpassword=${scm.password}
> In this case, continuum should substitute the configured scm username and
> password before executing the 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] Created: (MRM-288) Error on startup of current revision (r510897)
Error on startup of current revision (r510897) -- Key: MRM-288 URL: http://jira.codehaus.org/browse/MRM-288 Project: Archiva Issue Type: Bug Reporter: Lester Ecarma 2007-02-23 18:11:34.480::WARN: Failed startup of context [EMAIL PROTECTED]/,/home/lecarma/workspace/mergere/OSS/apache/archiva/trunk/archiva-webapp/src/main/webapp} java.lang.NullPointerException: configuration can not be null at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.(CommonsConfigurationRegistry.java:89) at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.getSection(CommonsConfigurationRegistry.java:422) at org.apache.maven.archiva.configuration.DefaultArchivaConfiguration.addChangeListener(DefaultArchivaConfiguration.java:86) at org.apache.maven.archiva.scheduler.DefaultRepositoryTaskScheduler.start(DefaultRepositoryTaskScheduler.java:91) at org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:130) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:143) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:133) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:87) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:101) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:313) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291) at org.codehaus.plexus.container.initialization.StartLoadOnStartComponentsPhase.execute(StartLoadOnStartComponentsPhase.java:54) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:928) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:876) at org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:853) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:222) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:236) at org.codehaus.plexus.xwork.PlexusLifecycleListener.contextInitialized(PlexusLifecycleListener.java:76) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:511) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372) at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) This causes a 404 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-288) Error on startup of current revision (r510897)
[ http://jira.codehaus.org/browse/MRM-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88335 ] Lester Ecarma commented on MRM-288: --- Fix attached to http://jira.codehaus.org/browse/PLXCOMP-60, please review. Thanks. > Error on startup of current revision (r510897) > -- > > Key: MRM-288 > URL: http://jira.codehaus.org/browse/MRM-288 > Project: Archiva > Issue Type: Bug >Reporter: Lester Ecarma > > 2007-02-23 18:11:34.480::WARN: Failed startup of context [EMAIL > PROTECTED]/,/home/lecarma/workspace/mergere/OSS/apache/archiva/trunk/archiva-webapp/src/main/webapp} > java.lang.NullPointerException: configuration can not be null > at > org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.(CommonsConfigurationRegistry.java:89) > at > org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.getSection(CommonsConfigurationRegistry.java:422) > at > org.apache.maven.archiva.configuration.DefaultArchivaConfiguration.addChangeListener(DefaultArchivaConfiguration.java:86) > at > org.apache.maven.archiva.scheduler.DefaultRepositoryTaskScheduler.start(DefaultRepositoryTaskScheduler.java:91) > at > org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java:33) > at > org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:130) > at > org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:143) > at > org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:133) > at > org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:87) > at > org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:101) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:313) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291) > at > org.codehaus.plexus.container.initialization.StartLoadOnStartComponentsPhase.execute(StartLoadOnStartComponentsPhase.java:54) > at > org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:928) > at > org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:876) > at > org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:853) > at > org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:222) > at > org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:236) > at > org.codehaus.plexus.xwork.PlexusLifecycleListener.contextInitialized(PlexusLifecycleListener.java:76) > at > org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:511) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) > at > org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1191) > at > org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:481) > at > org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:434) > at > org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) > at > org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:147) > at > org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:372) > at org.mortbay.jetty.plugin.util.Scanner.run(Scanner.java:159) > This causes a 404 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MASSEMBLY-186) Download files from HTTP or FTP
Download files from HTTP or FTP --- Key: MASSEMBLY-186 URL: http://jira.codehaus.org/browse/MASSEMBLY-186 Project: Maven 2.x Assembly Plugin Issue Type: New Feature Environment: All Reporter: Marcel Schoen Priority: Minor It would be nice if the assembly plugin could also gather files to be packed from external sources over HTTP or FTP. The configuration could look like this: http://files.acme.com/data **/*.jar / ftp://files.acme.com/data **/*.jar / It could support basically every available URL protocoll suitable for file retrieval, like "scp:", "smb:" etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHANGES-70) NPE if the version attribute is not set properly in the changes.xml file
NPE if the version attribute is not set properly in the changes.xml file
Key: MCHANGES-70
URL: http://jira.codehaus.org/browse/MCHANGES-70
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-3
Reporter: Stephane Nicoll
Priority: Minor
Fix For: 2.0-beta-3
If the version is not set in the release xml element, a NPE is thrown:
{noformat}
java.lang.NullPointerException
at
org.apache.maven.plugin.announcement.AnnouncementMojo.getLatestRelease(AnnouncementMojo.java:372)
at
org.apache.maven.plugin.announcement.AnnouncementMojo.doGenerate(AnnouncementMojo.java:277)
at
org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:235)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:898)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:734)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:505)
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)
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-212) Catalan Language
Catalan Language Key: MSITE-212 URL: http://jira.codehaus.org/browse/MSITE-212 Project: Maven 2.x Site Plugin Issue Type: New Feature Reporter: Javier de Ros Attachments: site-plugin_ca.properties That's the Catalan language properties for the maven site 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: (CONTINUUM-1181) Continuum aborts when running Postgres under JBoss
[ http://jira.codehaus.org/browse/CONTINUUM-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88361 ] thierry lach commented on CONTINUUM-1181: - That did not fix the problem. It did, however, change the filenames to be upper and lower case instead of all upper case. > Continuum aborts when running Postgres under JBoss > -- > > Key: CONTINUUM-1181 > URL: http://jira.codehaus.org/browse/CONTINUUM-1181 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1 > Environment: MS Windows XP Pro SP2 > postgres 8.1.4-1 with JDBC Driver postgresql-8.1-408.jdbc3 > JBoss 4.0.5.GA >Reporter: thierry lach > > I'm trying to get Continuum to store its data in a postgres database while > running under JBoss and I'm getting an exception. It seems that someone is > trying to change the transaction isolation during a transaction. > Excerpt from JBoss logs follows... > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - Starting Continuum. > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - < Continuum 1.1-SNAPSHOT started! > > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - --- > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -\ ^__^ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - \ (oo)\___ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -(__)\ )\/\ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -||w | > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -|| || > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO ContinuumInitializer:default > - Continuum initializer running ... > 2007-02-21 12:56:02,644 [ScannerThread] WARN LocalManagedConnectionFactory > - Error resetting transaction isolation > org.postgresql.util.PSQLException: Cannot change transaction isolation level > in the middle of a transaction. > at > org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection.java:733) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.cleanup(BaseWrapperManagedConnection.java:189) > at > org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java > :320) > at > org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.returnConnection(JBossManagedConnectionPool.java:620) > at > org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection > (BaseConnectionManager2.java:363) > at > org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:623) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle > (BaseWrapperManagedConnection.java:266) > at > org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129) > at > org.jpox.store.rdbms.adapter.DatabaseAdapter.getConnection(DatabaseAdapter.java > :928) > at > org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTransaction.java:324) > at > org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:356) > at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached > (PlexusJdoUtils.java:346) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached( > JdoContinuumStore.java:1287) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1282) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached > (JdoContinuumStore.java:1277) > at > org.apache.maven.continuum.store.JdoContinuumStore.getSystemConfiguration(JdoContinuumStore.java:1375) > at > org.apache.maven.continuum.initialization.DefaultContinuumInitializer.initialize > (DefaultContinuumInitializer.java:90) > at > org.apache.maven.continuum.DefaultContinuum.start(DefaultContinuum.java:2281) > at > org.codehaus.plexus.personality.plexus.lifecycle.phase.StartPhase.execute(StartPhase.java > :33) >
[jira] Created: (CONTINUUM-1183) Perforce problem: incorrect client spec is used
Perforce problem: incorrect client spec is used --- Key: CONTINUUM-1183 URL: http://jira.codehaus.org/browse/CONTINUUM-1183 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Reporter: Anton Katernoga Attachments: patch.p4.txt I have 2 projects set up which use the same perforce scm url. One is run each 5 mins, the other is a nightly tests build. I've noticed that the latter never gets run-the message is that the dir is up-to date. It appeared that after the first project is run, its client spec is set to system variable in PerforceCheckOutCommand (maven-scm perforce provider) class and afterwards the value of the var is used instead of a correct client spec. I didn't remove the property set, as it is a fix to SCM-165, but rather the place where prop is used. Now works fine. Patch is 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] Created: (MASSEMBLY-187) Incorrect FileSet causes infinite loop
Incorrect FileSet causes infinite loop -- Key: MASSEMBLY-187 URL: http://jira.codehaus.org/browse/MASSEMBLY-187 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Linux JDK 1.5 Maven 2.0.4 Reporter: Jimisola Laursen Priority: Minor Using an incorrect FileSet (see example below) causes an infinite loop after "[INFO] Building jar: ..." have been outputed. http://maven.apache.org/ASSEMBLY/1.1.0-SNAPSHOT"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/1.1.0-SNAPSHOT http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd";> package jar false *:jar:* *:sources target -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-285) Build fails on Windows when the folder being executed has spaces in it.
[ http://jira.codehaus.org/browse/SUREFIRE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated SUREFIRE-285: Attachment: SUREFIRE-285.patch Improved patch with some doc, ready to be committed > Build fails on Windows when the folder being executed has spaces in it. > --- > > Key: SUREFIRE-285 > URL: http://jira.codehaus.org/browse/SUREFIRE-285 > Project: Maven Surefire > Issue Type: Bug > Components: plugin >Affects Versions: 2.3 > Environment: Windows XP, Maven 2.0.4 >Reporter: Petar Tahchiev > Fix For: 2.4 > > Attachments: MavenSurefire.patch, SUREFIRE-285.patch > > > Hi guys, > I am a fan of the Fedora Core linux system, and I don't have any problem when > trying to build the surefire plugin on that box, but today I sat on a Windows > PC and I checkout the project in "My Documents" folder. I tried to build the > plugin and one of the tests - UrlUtilTest failed. After examining the results > it turned out that it was looking for url of the type: > "file:/C:\My Documents\workspace\surefire" but found > "file:/C:\My%20Documents\workspace\surefire", which I guess is because you > have forgotten to escape the intervals. > Anyway I escaped the spaces and it works as a charm. > Please review accept my 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] Closed: (MNG-2797) Instance variables are null when extending a mojo
[
http://jira.codehaus.org/browse/MNG-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MNG-2797.
---
Assignee: Carlos Sanchez
Resolution: Won't Fix
This is a question for the maven mailing list, not an issue, please ask there.
I guess it's a configuration problem, maven injects values in current mojo, but
you are extending a mojo in other jar
> Instance variables are null when extending a mojo
> -
>
> Key: MNG-2797
> URL: http://jira.codehaus.org/browse/MNG-2797
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 2.0.4
> Environment: Tested on Fedora Core 6.
>Reporter: Petar Tahchiev
> Assigned To: Carlos Sanchez
>
> Hi gyus,
> first of all I want to be execused if this is not the right place to post
> this. Now on the problem: I am trying to make my own mojo and for the purpose
> I extend an exisitng mojo (for example SurefirePlugin). So my mojo is
> something like this:
> public class MyTestMojo extends AbstractMojo
> {
> /**
> * This is the mojo's "main" method.
> *
> * @throws MojoExecutionException in case of error
> * @throws MojoFailureException in case of error
> */
> public void execute() throws MojoExecutionException, MojoFailureException
> {
> super.execute();
> }
> }
> After building my mojo as maven plugin and trying to run it, I get the
> following stack-trace.
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:355)
> at
> org.apache.cactus.integration.m2.CactusTestMojo.execute(CactusTestMojo.java:53)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.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)
> And I see on the line 355 of the maven-surefire-plugin (ver.2.2) it stays:
> else if ( !testClassesDirectory.exists() )
> and after debugging it, I see that testClassesDirectory is always null !!!
> It is really surpising to me, as testClassesDirectory is initialized with the
> following lines:
> /**
> * The directory containing generated test classes of the project being
> tested.
> *
> * @parameter expression="${project.build.testOutputDirectory}"
> * @required
> */
> private File testClassesDirectory;
> OK, I want to hear what do you think?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-1184) using plexus-contextualizer to setup port in jetty
using plexus-contextualizer to setup port in jetty -- Key: CONTINUUM-1184 URL: http://jira.codehaus.org/browse/CONTINUUM-1184 Project: Continuum Issue Type: Improvement Environment: all Reporter: Olivier Lamy Actually when using continuum-plexus-runtime, in order to change the http port : the application must be started (in order to be extracted), stopped. Then configuration file can be changed. With this patch the jetty port can be set before the first start. I have deployed all needed artifacts in codehaus snapshot repo. -- 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-1184) using plexus-contextualizer to setup port in jetty
[ http://jira.codehaus.org/browse/CONTINUUM-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1184: Attachment: CONTINUUM-1184 patch attached. > using plexus-contextualizer to setup port in jetty > -- > > Key: CONTINUUM-1184 > URL: http://jira.codehaus.org/browse/CONTINUUM-1184 > Project: Continuum > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy > Attachments: CONTINUUM-1184 > > > Actually when using continuum-plexus-runtime, in order to change the http > port : the application must be started (in order to be extracted), stopped. > Then configuration file can be changed. > With this patch the jetty port can be set before the first start. > I have deployed all needed artifacts in codehaus snapshot repo. > -- > 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] Created: (MEV-501) Velocity poms should have license sections added.
Velocity poms should have license sections added. - Key: MEV-501 URL: http://jira.codehaus.org/browse/MEV-501 Project: Maven Evangelism Issue Type: Improvement Components: Incomplete POM Reporter: Daniel Kulp The Velocity poms (also the ones for the older versions) should this added: The Apache Software License, Version 2.0 http://www.apache.org/licenses/LICENSE-2.0.txt repo A bug has been logged with the velocity team and they are correcting it for future releases: https://issues.apache.org/jira/browse/VELOCITY-518 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEV-502) woodstox poms should have licenses/organization elements
woodstox poms should have licenses/organization elements Key: MEV-502 URL: http://jira.codehaus.org/browse/MEV-502 Project: Maven Evangelism Issue Type: Improvement Components: Incomplete POM Reporter: Daniel Kulp The pom should have: The Apache Software License, Version 2.0 http://www.apache.org/licenses/LICENSE-2.0.txt repo Codehaus http://www.codehaus.org/ Bug with the woodstox team logged at: http://jira.codehaus.org/browse/WSTX-108 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEV-502) woodstox poms should have licenses/organization elements
[ http://jira.codehaus.org/browse/MEV-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-502. -- Assignee: Carlos Sanchez Resolution: Fixed > woodstox poms should have licenses/organization elements > > > Key: MEV-502 > URL: http://jira.codehaus.org/browse/MEV-502 > Project: Maven Evangelism > Issue Type: Improvement > Components: Incomplete POM >Reporter: Daniel Kulp > Assigned To: Carlos Sanchez > > The pom should have: > > > The Apache Software License, Version 2.0 > http://www.apache.org/licenses/LICENSE-2.0.txt > repo > > > > Codehaus > http://www.codehaus.org/ > > Bug with the woodstox team logged at: > http://jira.codehaus.org/browse/WSTX-108 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-291) Create comprehensive tests
Create comprehensive tests -- Key: SUREFIRE-291 URL: http://jira.codehaus.org/browse/SUREFIRE-291 Project: Maven Surefire Issue Type: Task Affects Versions: 2.3 Reporter: Brett Porter 'nuff said. Aiming for high coverage on the APIs, providers. Integration tests will be needed also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-292) Documentation for surefire API and providers
Documentation for surefire API and providers Key: SUREFIRE-292 URL: http://jira.codehaus.org/browse/SUREFIRE-292 Project: Maven Surefire Issue Type: Task Affects Versions: 2.3 Reporter: Brett Porter While the docs for the plugins are reasonable, the surefire mini-site is barebones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-292) Documentation for surefire API and providers
[ http://jira.codehaus.org/browse/SUREFIRE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-292: -- Priority: Blocker (was: Major) Complexity: Novice (was: Intermediate) > Documentation for surefire API and providers > > > Key: SUREFIRE-292 > URL: http://jira.codehaus.org/browse/SUREFIRE-292 > Project: Maven Surefire > Issue Type: Task >Affects Versions: 2.3 >Reporter: Brett Porter >Priority: Blocker > Fix For: 2.4 > > > While the docs for the plugins are reasonable, the surefire mini-site is > barebones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-292) Documentation for surefire API and providers
[ http://jira.codehaus.org/browse/SUREFIRE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-292: -- Fix Version/s: 2.4 > Documentation for surefire API and providers > > > Key: SUREFIRE-292 > URL: http://jira.codehaus.org/browse/SUREFIRE-292 > Project: Maven Surefire > Issue Type: Task >Affects Versions: 2.3 >Reporter: Brett Porter > Fix For: 2.4 > > > While the docs for the plugins are reasonable, the surefire mini-site is > barebones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-291) Create comprehensive tests
[ http://jira.codehaus.org/browse/SUREFIRE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-291: -- Priority: Blocker (was: Major) Fix Version/s: 2.4 > Create comprehensive tests > -- > > Key: SUREFIRE-291 > URL: http://jira.codehaus.org/browse/SUREFIRE-291 > Project: Maven Surefire > Issue Type: Task >Affects Versions: 2.3 >Reporter: Brett Porter >Priority: Blocker > Fix For: 2.4 > > > 'nuff said. Aiming for high coverage on the APIs, providers. Integration > tests will be needed also. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEV-501) Velocity poms should have license sections added.
[ http://jira.codehaus.org/browse/MEV-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MEV-501. -- Assignee: Carlos Sanchez Resolution: Fixed > Velocity poms should have license sections added. > - > > Key: MEV-501 > URL: http://jira.codehaus.org/browse/MEV-501 > Project: Maven Evangelism > Issue Type: Improvement > Components: Incomplete POM >Reporter: Daniel Kulp > Assigned To: Carlos Sanchez > > The Velocity poms (also the ones for the older versions) should this added: > > > The Apache Software License, Version 2.0 > http://www.apache.org/licenses/LICENSE-2.0.txt > repo > > > A bug has been logged with the velocity team and they are correcting it for > future releases: > https://issues.apache.org/jira/browse/VELOCITY-518 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MAVENUPLOAD-1390) JasperReports 1.3.1 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1390. --- Assignee: Carlos Sanchez Resolution: Fixed > JasperReports 1.3.1 upload > -- > > Key: MAVENUPLOAD-1390 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1390 > Project: maven-upload-requests > Issue Type: Task >Reporter: Teodor Danciu > Assigned To: Carlos Sanchez > > http://rs.jaspersoft.com/maven2/jasperreports-1.3.1-bundle.jar > http://sourceforge.net/projects/jasperreports > http://sourceforge.net/project/memberlist.php?group_id=36382 > Open Source Reporting Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1391) New version of TableLayout
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88381 ] Carlos Sanchez commented on MAVENUPLOAD-1391: - It's missing license element Why did you build the jar? it's available for download from their download page no dependencies? > New version of TableLayout > -- > > Key: MAVENUPLOAD-1391 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1391 > Project: maven-upload-requests > Issue Type: Task >Reporter: John David N. Dionisio > > http://www.cs.lmu.edu/~dondi/maven/TableLayout-20050920-bundle.jar > https://tablelayout.dev.java.net > This is the latest version of the TableLayout project; the current version on > ibiblio is for 20020517 only. I am not an official developer on the project > (yet --- my request is pending but I have gotten no response). However, the > bundle is built directly from the CVS trunk of the above project on > tablelayout.dev.java.net. I simply wrote a POM and built via > repository:bundle-create. If you wish, just use my POM and rebuild the > bundle, so that you are sure that the JAR is indeed derived from the project. > 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] Commented: (MJAVADOC-111) Can't release when I use javadoc aggregate/groups
[ http://jira.codehaus.org/browse/MJAVADOC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88382 ] Andy Signer commented on MJAVADOC-111: -- I encountered the same problem. Release:perform or site-deploy failed with the same error as stated in FailedToReleaseDueToJavadoc.txt when I set aggregate=true. When aggregate=false everything went smooth. > Can't release when I use javadoc aggregate/groups > - > > Key: MJAVADOC-111 > URL: http://jira.codehaus.org/browse/MJAVADOC-111 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: XP Pro >Reporter: David Hoffer > Attachments: FailedToReleaseDueToJavadoc.txt > > > I added the following section to my parent POM and can't release anymore, I > will attach the error log. > > true > > > Public Packages > > com.xrite.xdsiii:com.xrite.xdsiii.driver:com.xrite.xdsiii.driver.* > > > Internal Packages - API Subject To > Change > > com.xrite.awt:com.xrite.swing:com.xrite.util:com.xrite.xdsiii.instrument:com.xrite.xdsiii.instrument.* > > > > It looks like it needs the jars that have not jet been released yet (that's > what the release goal is for). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEV-503) AOP alliance needs a URL
AOP alliance needs a URL Key: MEV-503 URL: http://jira.codehaus.org/browse/MEV-503 Project: Maven Evangelism Issue Type: Improvement Components: Incomplete POM Reporter: Daniel Kulp Pom should have: http://aopalliance.sourceforge.net/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEV-504) Jetty 5.1.10 and 5.1.11 missing poms
Jetty 5.1.10 and 5.1.11 missing poms Key: MEV-504 URL: http://jira.codehaus.org/browse/MEV-504 Project: Maven Evangelism Issue Type: Improvement Components: Missing POM Reporter: Daniel Kulp The NEW versions of Jetty (6.x) have correct poms that include all the information. However, the 5.1.11 and 5.1.12 are missing poms. I've used information from the 6.1 version and 5.1.10 versions to create: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 jetty org.mortbay.jetty 5.1.11 http://jetty.mortbay.org Jetty Server Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0 Mort Bay Consulting http://www.mortbay.com jira http://jira.codehaus.org/browse/Jetty Jetty Discuss List http://lists.sourceforge.net/lists/listinfo/jetty-discuss http://www.nabble.com/Jetty-Discuss-f60.html Jetty Support List http://lists.sourceforge.net/lists/listinfo/jetty-support http://www.nabble.com/Jetty-Support-f61.html Jetty Announce List http://lists.sourceforge.net/lists/listinfo/jetty-announce http://www.nabble.com/Jetty---Announce-f2649.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1391) New version of TableLayout
[
http://jira.codehaus.org/browse/MAVENUPLOAD-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88383
]
John David N. Dionisio commented on MAVENUPLOAD-1391:
-
I have other code that needs this JAR (at this particular version due to API
changes), and I was hoping to use it as a Maven dependency from the central
repository. I was hoping not to need a private repository because one of the
dependent projects is open source host on SourceForge (and they don't like
using the Web space they provide for non-Web page downloads).
Yes, unfortunately the site does not explicitly give any license text, although
all indications show some kind of open source distribution. So far the owner
("clearthought") has been incommunicado.
In any case, that is my situation, and requesting an upload to the central
repository (since an earlier version was already there, albeit in Maven 1 form)
seemed to be the way to go. If this won't be appropriate, then I'm open to any
suggestions that you might have. Thanks!
> New version of TableLayout
> --
>
> Key: MAVENUPLOAD-1391
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1391
> Project: maven-upload-requests
> Issue Type: Task
>Reporter: John David N. Dionisio
>
> http://www.cs.lmu.edu/~dondi/maven/TableLayout-20050920-bundle.jar
> https://tablelayout.dev.java.net
> This is the latest version of the TableLayout project; the current version on
> ibiblio is for 20020517 only. I am not an official developer on the project
> (yet --- my request is pending but I have gotten no response). However, the
> bundle is built directly from the CVS trunk of the above project on
> tablelayout.dev.java.net. I simply wrote a POM and built via
> repository:bundle-create. If you wish, just use my POM and rebuild the
> bundle, so that you are sure that the JAR is indeed derived from the project.
> 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] Commented: (SUREFIRE-169) No tests detected when both TestNG and JUnit in classpath
[ http://jira.codehaus.org/browse/SUREFIRE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88393 ] Bill Wallace commented on SUREFIRE-169: --- An initial change to just allow the type of test suites to run would be very helpful - eg JUnit 4 POJO JUnit 3 TestNG as a plugin configuration. Then, later on it would be nice if all tests just run - whether JUnit or TestNG, without duplications. It doesn't much matter which system they run in, as long as the tests get run. > No tests detected when both TestNG and JUnit in classpath > - > > Key: SUREFIRE-169 > URL: http://jira.codehaus.org/browse/SUREFIRE-169 > Project: Maven Surefire > Issue Type: Bug > Components: classloading, JUnit 3.x support, TestNG support >Affects Versions: 2.0 (2.2 plugin) > Environment: Linux, JDK1.5 >Reporter: Jim Crossley > Fix For: 2.4 > > > I have a multi-module project where testng is declared as a dep in the parent > and a subproject declares junit as a dep. When I invoke 'mvn test' in the > subproject, surefire doesn't detect any tests to run. If I simply remove the > testng dep from the parent, the tests run fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1391) New version of TableLayout
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88409 ] John David N. Dionisio commented on MAVENUPLOAD-1391: - The bundle at the given URL has been updated so that its POM file includes a license element. Correct, this project has no dependencies. > New version of TableLayout > -- > > Key: MAVENUPLOAD-1391 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1391 > Project: maven-upload-requests > Issue Type: Task >Reporter: John David N. Dionisio > > http://www.cs.lmu.edu/~dondi/maven/TableLayout-20050920-bundle.jar > https://tablelayout.dev.java.net > This is the latest version of the TableLayout project; the current version on > ibiblio is for 20020517 only. I am not an official developer on the project > (yet --- my request is pending but I have gotten no response). However, the > bundle is built directly from the CVS trunk of the above project on > tablelayout.dev.java.net. I simply wrote a POM and built via > repository:bundle-create. If you wish, just use my POM and rebuild the > bundle, so that you are sure that the JAR is indeed derived from the project. > 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: (SUREFIRE-61) Incorrect classpath ordering
[ http://jira.codehaus.org/browse/SUREFIRE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-61: - Fix Version/s: 2.4 > Incorrect classpath ordering > > > Key: SUREFIRE-61 > URL: http://jira.codehaus.org/browse/SUREFIRE-61 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 3.x support >Affects Versions: 2.0 (2.2 plugin) > Environment: maven2.0.4, sun-jdk-1.5.0.09, maven-surefire-plugin 2.2, > surefire 2.0, gentoo linux x86 >Reporter: Martin Vysny >Priority: Critical > Fix For: 2.4 > > Attachments: my-app.zip, > SUREFIRE61_barrettas_surefire_surefire-booter_for_rev_489098.patch > > > Surefire incorrectly interprets classpath ordering. > Steps to reproduce: > 1. unzip my-app.zip - it's a simple mvn project created with >mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app >and lightly patched > 2. mvn test >in my case, it prints out > jar:file:/home/vyzivus/.m2/repository/jxta/jxta/2.0/jxta-2.0.jar!/log4j.properties > jar:file:/home/vyzivus/.m2/repository/jxta/jxta/2.0/jxta-2.0.jar!/log4j.properties >which is incorrect. log4j.properties is located both in jxta.jar and > src/test/resources, but I think that src/test/resources takes precedence over > jxta. This ordering is set correctly in surefire36745tmp file I think, but > surefire seems to ignore the ordering. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SUREFIRE-289) Surefire classlaoder loads wrong class when classes are of same package/class name
[ http://jira.codehaus.org/browse/SUREFIRE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated SUREFIRE-289: -- Fix Version/s: 2.4 > Surefire classlaoder loads wrong class when classes are of same package/class > name > -- > > Key: SUREFIRE-289 > URL: http://jira.codehaus.org/browse/SUREFIRE-289 > Project: Maven Surefire > Issue Type: Bug > Components: classloading >Affects Versions: 2.0 (2.2 plugin) > Environment: Windows, Cygwin >Reporter: Zachary Jones > Fix For: 2.4 > > Attachments: cheese.zip, cheesetest.zip > > > This is a repeat of the comment in SUREFIRE-286 > I am having a problem with surefire classloading. > I had to hack the ServiceMix class: > org.apache.servicemix.http.processors.ConsumerProcessor. > I saved the hacked version as the same class name and the same package. This > class does compile to target/classes. The ServiceMix jar that contains this > class is included in my classpath after the target/classes directory (seen > with -X) > When running mvn test, I get a test failure for the Test class that tries to > create a ConsumerProcessor. We are expecting it to create "our" version of > ConsumerProcessor, but it instead creates the ServiceMix version. > I have tried all the available usage options from the surefire plugin > documentation to no avail. Through debug in Eclipse, I see through a watch > expression (getClass().getClassLoader()) is always the IsolatedClassLoader, > no matter what options we set. > This test passes in Eclipse, so I am pretty sure it is a classloading issue > with the surefire plugin. > Thanks for your help in advance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-290) [PATCH] Forking to java 1.3 not working when using relative paths in modules.
[
http://jira.codehaus.org/browse/SUREFIRE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated SUREFIRE-290:
--
Fix Version/s: 2.4
> [PATCH] Forking to java 1.3 not working when using relative paths in modules.
> -
>
> Key: SUREFIRE-290
> URL: http://jira.codehaus.org/browse/SUREFIRE-290
> Project: Maven Surefire
> Issue Type: Bug
> Environment: WinXp + Java 1.3
>Reporter: Mark Holster
> Fix For: 2.4
>
> Attachments: no-relative-classpath-urls.patch
>
>
> For a java 1.3 multi-module project we use a construction like
> {code:xml}
>
> ..\mymodule1
> ..\..\mymodule2
>
> {code}
> The testcases work fine if maven is started in the modules, but when running
> from the aggegator pom a ClassNotFoundException on any testcase will occur.
> The attached patch add canonnical paths to the classpath if a given path is
> absolute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-256) Incoherent data between 'Package List ' and 'Test Cases' items in report
[ http://jira.codehaus.org/browse/SUREFIRE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88410 ] Brett Porter commented on SUREFIRE-256: --- it appears this was already fixed in 2.3, but we should incorporate the tests in this patch > Incoherent data between 'Package List ' and 'Test Cases' items in report > > > Key: SUREFIRE-256 > URL: http://jira.codehaus.org/browse/SUREFIRE-256 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin >Affects Versions: 2.0 Report Plugin >Reporter: Damien Lecan > Fix For: 2.4 > > Attachments: MSUREFIREREP-26-maven-surefire-plugin.patch, > MSUREFIREREP-26-maven-surefire-plugin.patch, surefire-report.html > > > As it can be seen of the attached file, the ConfigTest has incoherent data > between items 'Package List ' and 'Test Cases' . > In 'Package List ' : > Class Tests Errors FailuresSuccess RateTime > ConfigTest3 0 0100% > 0.585 > ConfigTest has just 3 tests. > But, in 'Test Cases', there are much more than 3 tests (they are duplicated > from the other tested class ManagerTest !) > ConfigTest > testCBEM1 0.039 > testCBEM2 0.001 > testCBEM3 0.001 > testCBEM4 0.001 > testCBEM5 0 > testCBEM6 0 > testCBEM7 0 > testCBEM8 0 > testCBEM9 0 > testCBEM10 0.001 > testCBEM11 0 > testCBEM12 0.001 > testGetBooleanProperty 0.528 > testGetFloatProperty0.029 > testGetIntProperty 0.012 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
