[jira] Commented: (CONTINUUM-1255) FATAL EnvironmentCheck Failure on Continuum Startup
[ http://jira.codehaus.org/browse/CONTINUUM-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94301 ] Wendy Smoak commented on CONTINUUM-1255: Is the app working? That shows up in the logs from time to time, but doesn't seem to hurt anything when it's run under the plexus runtime. > FATAL EnvironmentCheck Failure on Continuum Startup > --- > > Key: CONTINUUM-1255 > URL: http://jira.codehaus.org/browse/CONTINUUM-1255 > Project: Continuum > Issue Type: Sub-task >Affects Versions: 1.1-alpha-1 > Environment: JBoss 4.0.5.GA, JDK 1.4.2_12 >Reporter: Gabriel Misura > > 42734 [http-0.0.0.0-8080-1] INFO > org.codehaus.plexus.security.system.check.EnvironmentCheck:required-roles - > Checking the existance of required roles. > 43501 [http-0.0.0.0-8080-1] FATAL > com.opensymphony.xwork.interceptor.Interceptor:pssEnvironmentCheckInterceptor > - EnvironmentCheck Failure. > == > ENVIRONMENT FAILURE !! > Missing "/security" package namespace in xwork.xml > Missing [1] xwork.xml configuration elements. > == > 43651 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssSecureActionInterceptor - > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor > initialized! > 43876 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssSecureActionInterceptor - > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor > initialized! > 43886 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssSecureActionInterceptor - > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor > initialized! > 45228 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssForceAdminUserInterceptor > - Admin user found. No need to configure admin user. > 49640 [http-0.0.0.0-8080-2] INFO > com.opensymphony.webwork.views.freemarker.FreemarkerManager - Instantiating > Freemarker ConfigManager!, > com.opensymphony.webwork.views.freemarker.FreemarkerManager -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MGPG-8) Build error when plugin tries to sign nonexistent jar file in a war module
[
http://jira.codehaus.org/browse/MGPG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94300
]
Wendy Smoak commented on MGPG-8:
I haven't had time to re-test this to make sure it's really happening with the
latest snapshot. I remember building the plugin, but I might not have updated
the plugin version number in the pom. Jesse seems to have gotten it to work
for the Continuum release.
> Build error when plugin tries to sign nonexistent jar file in a war module
> --
>
> Key: MGPG-8
> URL: http://jira.codehaus.org/browse/MGPG-8
> Project: Maven 2.x GPG Plugin
> Issue Type: Bug
>Affects Versions: 1.0-alpha-3
>Reporter: Wendy Smoak
>Assignee: Daniel Kulp
>
> During release:perform for Archiva 0.9-alpha-1, the gpg plugin is complaining
> that a jar is not found, when the module has packaging=war
> [INFO] [gpg:sign {execution: default}]
> gpg: can't open
> `e:\svn\maven\archiva\target\checkout\archiva-webapp\target\archiva-webapp-0.9-alpha-1.jar':
> No such file or directory
> gpg: signing failed: file open error
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Exit code: 2
> [INFO]
> -
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1497) Upload Unitils 1.0 rc 2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1497. --- Assignee: Carlos Sanchez Resolution: Fixed optional means that the projects depending on yours have to explicitly add them but for questions you can use the mailing list > Upload Unitils 1.0 rc 2 > --- > > Key: MAVENUPLOAD-1497 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1497 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tim Ducheyne >Assignee: Carlos Sanchez > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1476) Upload org.bouncycastle:bcprov:jar:1.36 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1476. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload org.bouncycastle:bcprov:jar:1.36 to ibiblio > -- > > Key: MAVENUPLOAD-1476 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1476 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock >Assignee: Carlos Sanchez > > http://www.mattwhitlock.com/bcprov-1.36-bundle.jar > http://www.bouncycastle.org/java.html > The Bouncy Castle Crypto package is a Java implementation of cryptographic > algorithms. The package is organised so that it contains a light-weight API > suitable for use in any environment (including the newly released J2ME) with > the additional infrastructure to conform the algorithms to the JCE framework. > -- > The JDK14 version of bcprov 1.36 is already on ibiblio at > /maven2/bouncycastle/bcprov-jdk14/136, but its POM file is woefully > incomplete, its groupId is not in reverse domain order, and it lacks sources > and javadoc attachments. > I am submitting this bundle that contains the JDK14, JDK15, and JDK16 > versions of bcprov 1.36 along with sources and javadoc attachments for each. > The POM file in my bundle includes name, description, URL, and license > information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work stopped: (MRM-236) Unable to 'proxy through' more than one managed repo
[ http://jira.codehaus.org/browse/MRM-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-236 stopped by Maria Odea Ching. > Unable to 'proxy through' more than one managed repo > > > Key: MRM-236 > URL: http://jira.codehaus.org/browse/MRM-236 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0 > Environment: Affects r478814 1.0-SNAPSHOT >Reporter: Wendy Smoak >Assignee: Maria Odea Ching > Fix For: 1.0 > > > On Proxied Repositories -> Add or Edit, only the 'first' managed repository > added to the system is listed in the 'Proxied through' select list. > It should allow you to choose any of the managed repositories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-205) Files mapped anywhere under META-INF ignored
Files mapped anywhere under META-INF ignored
Key: MASSEMBLY-205
URL: http://jira.codehaus.org/browse/MASSEMBLY-205
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Reporter: Eric Redmond
In an assembly descriptor moving a components.xml file under META-INF is ignored
${basedir}/src/main/components/xstream-components.xml
components.xml
/META-INF/plexus
true
However, moving anywhere else, such as /meta-inf/plexus (lowercase) works file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (WAGONFTP-18) Should have option for retry on connection errors during ftp deploy of site
Should have option for retry on connection errors during ftp deploy of site --- Key: WAGONFTP-18 URL: http://jira.codehaus.org/browse/WAGONFTP-18 Project: wagon-ftp Issue Type: Improvement Environment: OS capable of running Java Reporter: Mauritz Lovgren When deploying a grand site with hundreds of files, even the slightest connection failure causes the build to break, leaving a failed site deploy. What about a configurable retry mechanism that reconnects to the ftp server and continues the file transfer? E.g. or similar that would really help out in these situations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-211) Can't deploy site using site:deploy due to a ProxyHTTP error
[ http://jira.codehaus.org/browse/MSITE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94291 ] Bryan Loofbourrow commented on MSITE-211: - Same problem here with 2.0-beta-5; 2.0-beta-4 works fine. > Can't deploy site using site:deploy due to a ProxyHTTP error > > > Key: MSITE-211 > URL: http://jira.codehaus.org/browse/MSITE-211 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: linux ubuntu dapper drake >Reporter: Elid OR >Priority: Blocker > > When I execute the site deployment (with version that comes with maven 2.0.5) > "mvn site:deploy " I got an error see log en debug mode below. This used to > work correctly with maven version 2.04 (so maybe site plugin version > 2.0-beta-4 : > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error uploading site > Embedded error: Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy > error: Forbidden > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > 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:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading > site > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:184) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 16 more > Caused by: org.apache.maven.wagon.authentication.AuthenticationException: > Cannot connect. Reason: ProxyHTTP: java.io.IOException: proxy error: > Forbidden > at > org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:186) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:149) > ... 18 more > Caused by: com.jcraft.jsch.JSchException: ProxyHTTP: java.io.IOException: > proxy error: Forbidden > at com.jcraft.jsch.ProxyHTTP.connect(Unknown Source) > at com.jcraft.jsch.Session.connect(Unknown Source) > at com.jcraft.jsch.Session.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnection(AbstractJschWagon.java:158) > ... 20 more > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Wed Feb 21 12:00:41 CET 2007 > [INFO] Final Memory: 3M/7M > [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] Reopened: (MRM-227) Archiva doesn't suppost UTF-8 databases in Mysql
[
http://jira.codehaus.org/browse/MRM-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez reopened MRM-227:
Assignee: (was: Carlos Sanchez)
> Archiva doesn't suppost UTF-8 databases in Mysql
>
>
> Key: MRM-227
> URL: http://jira.codehaus.org/browse/MRM-227
> Project: Archiva
> Issue Type: Bug
> Components: Users/Security
>Affects Versions: 1.0
> Environment: Linux jtbox01 2.4.21-37.0.1.ELsmp #1 SMP Wed Jan 11
> 18:35:45 EST 2006 i686 athlon i386 GNU/Linux
> jdk1.5.0_07 + apache-tomcat-5.5.17 + mysql-5.0.22
>Reporter: Arnaud Heritier
>
> If the mysql database is created with Collation utf8_unicode_ci I receive
> this error when tables are created :
> {code}
> 2006-11-17 14:29:13,782 [http-8080-Processor25] ERROR RDBMS
>- Error thrown executing CREATE TABLE `OPERATIONS`
> (
> `NAME` VARCHAR(256) BINARY NOT NULL,
> `DESCRIPTION` VARCHAR(256) BINARY NULL,
> `PERMANENT` BIT NOT NULL,
> `RESOURCE_REQUIRED` BIT NOT NULL,
> PRIMARY KEY (`NAME`)
> ) ENGINE=INNODB : Specified key was too long; max key length is 765 bytes
> java.sql.SQLException: Specified key was too long; max key length is 765 bytes
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2975)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1600)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1695)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:2998)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:2927)
> at com.mysql.jdbc.Statement.execute(Statement.java:535)
> at
> org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:261)
> at
> org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:561)
> at
> org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:516)
> at
> org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:244)
> at
> org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:287)
> at
> org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3006)
> at
> org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2540)
> at
> org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2397)
> at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:603)
> at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:617)
> at org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1016)
> at org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1134)
> at
> org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager.java:2216)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getAllObjects(JdoTool.java:199)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getAllObjects(JdoTool.java:182)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.triggerInit(JdoTool.java:131)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getPersistenceManager(JdoTool.java:118)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getObjectById(JdoTool.java:236)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.objectExistsById(JdoTool.java:283)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacManager.roleExists(JdoRbacManager.java:124)
> at
> org.codehaus.plexus.rbac.profile.AbstractRoleProfile.getRole(AbstractRoleProfile.java:236)
> at
> org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.getRole(DefaultRoleProfileManager.java:72)
> at
> org.codehaus.plexus.security.ui.web.checks.security.RequiredRolesEnvironmentCheck.validateEnvironment(RequiredRolesEnvironmentCheck.java:64)
> at
> org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInterceptor.init(EnvironmentCheckInterceptor.java:78)
> at
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:101)
> at
> com.opensymphony.xwork.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:48)
> at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:702)
> at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:569)
> at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStacks(XmlConfigurationProvider.java:582)
> at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvi
[jira] Reopened: (CONTINUUM-1113) Continuum doesn't work with MySQL
[ http://jira.codehaus.org/browse/CONTINUUM-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez reopened CONTINUUM-1113: --- Assignee: (was: Carlos Sanchez) > Continuum doesn't work with MySQL > - > > Key: CONTINUUM-1113 > URL: http://jira.codehaus.org/browse/CONTINUUM-1113 > Project: Continuum > Issue Type: Improvement > Components: Database >Affects Versions: 1.1-alpha-1 >Reporter: Carlos Sanchez > Attachments: mysql-CONTINUUM-1113.patch > > > 2006-10-20 19:23:14,288 [WrapperSimpleAppMain] ERROR RDBMS - Error thrown > executing CREATE TABLE `PROJECTNOTIFIER_CONFIGURATION` > [SNIP] > 2006/10/20 19:23:14 | java.sql.SQLException: BLOB/TEXT column 'STRING_KEY' > used in key specification without a key length -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-227) Archiva doesn't suppost UTF-8 databases in Mysql
[
http://jira.codehaus.org/browse/MRM-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94288
]
Carlos Sanchez commented on MRM-227:
Seems that MySQL decided it's not a bug in their side, although it's really
inconsistent
http://bugs.mysql.com/bug.php?id=25480
> Archiva doesn't suppost UTF-8 databases in Mysql
>
>
> Key: MRM-227
> URL: http://jira.codehaus.org/browse/MRM-227
> Project: Archiva
> Issue Type: Bug
> Components: Users/Security
>Affects Versions: 1.0
> Environment: Linux jtbox01 2.4.21-37.0.1.ELsmp #1 SMP Wed Jan 11
> 18:35:45 EST 2006 i686 athlon i386 GNU/Linux
> jdk1.5.0_07 + apache-tomcat-5.5.17 + mysql-5.0.22
>Reporter: Arnaud Heritier
>Assignee: Carlos Sanchez
>
> If the mysql database is created with Collation utf8_unicode_ci I receive
> this error when tables are created :
> {code}
> 2006-11-17 14:29:13,782 [http-8080-Processor25] ERROR RDBMS
>- Error thrown executing CREATE TABLE `OPERATIONS`
> (
> `NAME` VARCHAR(256) BINARY NOT NULL,
> `DESCRIPTION` VARCHAR(256) BINARY NULL,
> `PERMANENT` BIT NOT NULL,
> `RESOURCE_REQUIRED` BIT NOT NULL,
> PRIMARY KEY (`NAME`)
> ) ENGINE=INNODB : Specified key was too long; max key length is 765 bytes
> java.sql.SQLException: Specified key was too long; max key length is 765 bytes
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2975)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1600)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1695)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:2998)
> at com.mysql.jdbc.Connection.execSQL(Connection.java:2927)
> at com.mysql.jdbc.Statement.execute(Statement.java:535)
> at
> org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:261)
> at
> org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:561)
> at
> org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:516)
> at
> org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:244)
> at
> org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:287)
> at
> org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3006)
> at
> org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2540)
> at
> org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2397)
> at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:603)
> at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:617)
> at org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1016)
> at org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1134)
> at
> org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager.java:2216)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getAllObjects(JdoTool.java:199)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getAllObjects(JdoTool.java:182)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.triggerInit(JdoTool.java:131)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getPersistenceManager(JdoTool.java:118)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.getObjectById(JdoTool.java:236)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.objectExistsById(JdoTool.java:283)
> at
> org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacManager.roleExists(JdoRbacManager.java:124)
> at
> org.codehaus.plexus.rbac.profile.AbstractRoleProfile.getRole(AbstractRoleProfile.java:236)
> at
> org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.getRole(DefaultRoleProfileManager.java:72)
> at
> org.codehaus.plexus.security.ui.web.checks.security.RequiredRolesEnvironmentCheck.validateEnvironment(RequiredRolesEnvironmentCheck.java:64)
> at
> org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInterceptor.init(EnvironmentCheckInterceptor.java:78)
> at
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:101)
> at
> com.opensymphony.xwork.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:48)
> at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:702)
> at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:569)
> at
> com.opensymphony.xwork.config.providers.XmlConf
[jira] Commented: (CONTINUUM-1113) Continuum doesn't work with MySQL
[ http://jira.codehaus.org/browse/CONTINUUM-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94287 ] Carlos Sanchez commented on CONTINUUM-1113: --- Seems that MySQL decided it's not a bug in their side, althought it's really inconsistent http://bugs.mysql.com/bug.php?id=25480 > Continuum doesn't work with MySQL > - > > Key: CONTINUUM-1113 > URL: http://jira.codehaus.org/browse/CONTINUUM-1113 > Project: Continuum > Issue Type: Improvement > Components: Database >Affects Versions: 1.1-alpha-1 >Reporter: Carlos Sanchez >Assignee: Carlos Sanchez > Attachments: mysql-CONTINUUM-1113.patch > > > 2006-10-20 19:23:14,288 [WrapperSimpleAppMain] ERROR RDBMS - Error thrown > executing CREATE TABLE `PROJECTNOTIFIER_CONFIGURATION` > [SNIP] > 2006/10/20 19:23:14 | java.sql.SQLException: BLOB/TEXT column 'STRING_KEY' > used in key specification without a key length -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SCM-305) release:perform fails on linux
release:perform fails on linux -- Key: SCM-305 URL: http://jira.codehaus.org/browse/SCM-305 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Affects Versions: 1.0-beta-3 Environment: Maven 2.0.6 Linux (Fedora Core release 4) IBM JDK 1.4.2 SR7 Reporter: Patrick Schneider Priority: Critical Attachments: maven-scm-provider-perforce-release-perform-error.txt When attempting a 'release:perform' from Linux, if using Perforce, the command fails. -X output attached. The provider is attempting to create/save a clientspec using forward slashes, which Perforce does not allow. See generateDefaultClientspecName in PerforceScmProvider.java. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MIDEA-88) version control setting lost on update
[ http://jira.codehaus.org/browse/MIDEA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MIDEA-88. Assignee: Dennis Lundberg Resolution: Duplicate Fix Version/s: 2.1 > version control setting lost on update > -- > > Key: MIDEA-88 > URL: http://jira.codehaus.org/browse/MIDEA-88 > Project: Maven 2.x Idea Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: idea 6.0.5 windows xp >Reporter: Larry Hamel >Assignee: Dennis Lundberg > Fix For: 2.1 > > > have project with version control set to cvs. > change pom for a new dependency. > close project. in idea > mvn idea:idea > open project in idea > see that version control setting is lost -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1156) Continuum will not successfully delete build directories containing symbolic links
[ http://jira.codehaus.org/browse/CONTINUUM-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94278 ] John McNair commented on CONTINUUM-1156: I created a patch w/ unit tests and attached it to the referenced plxutils ticket: http://jira.codehaus.org/browse/PLXUTILS-28 I don't know when they'll get around to fixing it, but it bites me too. > Continuum will not successfully delete build directories containing symbolic > links > -- > > Key: CONTINUUM-1156 > URL: http://jira.codehaus.org/browse/CONTINUUM-1156 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 > Environment: Linux Fedora Core 5 >Reporter: Steve Pietrowicz > Fix For: 1.1-alpha-# > > Attachments: ContinuumFileUtils.java > > > FileUtils.cleanDirectory() will not remove symbolic links if they are located > in the directory that it is trying to clean. > This occurs for me when you set up a Shell project with the "Build Fresh" > option checked. > The project I'm building is invoked with a shell script. I download the > shell script through continuum and it kicks off the first build successfully. > On the next scheduled build, the following message occurs: > --- > org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error > executing action 'clean-working-directory' > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:432) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.cleanWorkingDirectory(DefaultBuildController.java:361) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:103) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) > at > edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) > at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528) > at java.lang.Thread.run(Thread.java:595) > Caused by: java.io.IOException: Directory > /scratch/home/srp/tomcat/apache-tomcat-5.5.17/webapps/continuum/WEB-INF/working-directory/1/dir/Linux/external/TclTk/8.5a4/bin > unable to be deleted. > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1332) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.codehaus.plexus.util.FileUtils.deleteDirectory(FileUtils.java:1328) > at org.codehaus.plexus.util.FileUtils.forceDelete(FileUtils.java:1158) > at > org.codehaus.plexus.util.FileUtils.cleanDirectory(FileUtils.java:1371) > at > org.apache.maven.continuum.core.action.CleanWorkingDirectoryAction.execute(CleanWorkingDirectoryAction.java:60) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:406) > ... 9 more > -- > A search in the directory mentioned above show a symbolic link that hasn't > been deleted. > The problem occurs because the Plexus class FileUtils.cleanDirectory() > doesn't work as advertised. I reported that bug on the Plexu Utils Jira, > which you can see here: > http://jira.codehaus.org/b
[jira] Created: (MRELEASE-226) Provide an option to create a branch for maintenance releases
Provide an option to create a branch for maintenance releases - Key: MRELEASE-226 URL: http://jira.codehaus.org/browse/MRELEASE-226 Project: Maven 2.x Release Plugin Issue Type: Improvement Environment: All Reporter: Jim Crossley This email thread prompted this issue: http://www.mail-archive.com/[EMAIL PROTECTED]/msg65485.html As I [Heinrich Nirschl] see it there are two solutions: 1) starting the maintenance branch before the release and doing the release on the branch, in this case you have to manually adjust the version on the trunk. 2) doing the release on the trunk and starting the maintenance branch from the tagged version, in this case the version has to be manually updated on the branch. Both approaches work, but there is some manual version editing in both. Once the branching is done, the release plugin works fine on the branch (for releasing further maintenance releases) and on the trunk (for releasing the next major release). The manual update is only necessary once per branch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1497) Upload Unitils 1.0 rc 2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94263 ] Tim Ducheyne commented on MAVENUPLOAD-1497: --- Let me explain what I'm trying to do. Our library has need for different configurations depending on the project envrionment that is going to use it. For example, there are 3 different unit testing frameworks supported: JUnit3, JUnit4 and TestNG. The project that is going to use Unitils needs to decide which one it wants to use. If it uses JUnit3 as test library, it does not want to retrieve the JUnit4 and TestNG libraries. That's why I set all such dependencies to provided and optional: Provided, so that the projects need to include the dependencies themselves. In the example, the project will need to explicitly add JUnit 3 as dependency. Optional, to indicate that the libraries are not strictly required for Unitils to function. For example, if JUnit3 is used, JUnit4 and TestNG are not required. As you requested, I moved all provided libs to the compile scope and made them optional again. The downside is that projects will now explicitly have to exclude all libraries that are not in their environment (a large exclude list). Any suggestions on how to avoid this (without using the provided scope)? I've uploaded it in a new bundle jar, the url remains the same. Thanks for installing the new bundle. Tim > Upload Unitils 1.0 rc 2 > --- > > Key: MAVENUPLOAD-1497 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1497 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tim Ducheyne > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-223) Generated pom.xml has invalid chars (does not correctly handle xml entities)
[
http://jira.codehaus.org/browse/MRELEASE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94261
]
Stefano Bagnara commented on MRELEASE-223:
--
Well, I used the xml entities so to not have to use the charset.
But when it build the output pom.xml it should take care to correctly escape
data.
The problem is not my editor, but the mvn site plugin.
The website created after the release plugin "mungled" my pom.xml does no more
contain the correct char.
So this is all about maven: I don't use third party editors or anything else.
Just mvn release and mvn site.
I don't know how to test the 2.0-beta5-SNAPSHOT plugin instead of the 2.0-beta4
automatically used by mvn.
> Generated pom.xml has invalid chars (does not correctly handle xml entities)
>
>
> Key: MRELEASE-223
> URL: http://jira.codehaus.org/browse/MRELEASE-223
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-4
>Reporter: Stefano Bagnara
>
> In our main pom we have this entry:
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
> in the resulting pom.xml the entity is converted to the real value, and the
> next time I try to use the pom it results in invalid output.
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-225) release should support multi-module project with sibling subprojects
release should support multi-module project with sibling subprojects Key: MRELEASE-225 URL: http://jira.codehaus.org/browse/MRELEASE-225 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-5 Reporter: Alain Coetmeur When I try to prepare a release for my project it refuses (after project rebuild) with such a message : An error is occurred in the checkin process: C:\Developpement\MavenWork\SIBLING-SUBMODULE-XX\pom.xml was not contained in C:\Developpement\MavenWork\MAIN-MODULE indeed, my project is quite complex with some modules which are sibling to the main module... this architecture is related to the legacy, and also to the fact that Eclipse does not appreciate project inside projects. anyway I have carefully configured the in each POM... a way to do that could be to gather the SCM URLS that are used by each POM, then remove those that are included inside others, and then apply the commit/update... for every remainding. Since many people have the same constraint (Eclipse, legacy...) this improvement would be very valuable note that there is a similar demand for SCM update http://jira.codehaus.org/browse/SCM-116 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 minute 23 seconds [INFO] Finished at: Thu Apr 26 19:16:06 CEST 2007 [INFO] Final Memory: 19M/61M [INFO] [INFO] Checking in modified POMs... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the checkin process: C:\Developpement\MavenWork\FWK DEI Module Trace Manager\pom.xml was not contai ned in C:\Developpement\MavenWork\FWK DEI Maven All -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-71) Cannot resolve license file
[ http://jira.codehaus.org/browse/MCLOVER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94259 ] Jonathon Blumenthal commented on MCLOVER-71: I too am having this problem. Using a relative path seems to work fine. > Cannot resolve license file > --- > > Key: MCLOVER-71 > URL: http://jira.codehaus.org/browse/MCLOVER-71 > Project: Maven 2.x Clover Plugin > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Bryan Madsen > > The license file cannot be found when the license location is a URL. This > works with version 2.3. > [INFO] [clover:instrumentInternal] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to load license file > [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] > Embedded error: Could not find resource > 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to load > license file > [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] > 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.forkProjectLifecycle(DefaultLifecycleExecutor.java:896) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > 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: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.MojoExecutionException: Failed to load > license file > [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:164) > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:134) > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.execute(AbstractCloverMojo.java:119) > at > org.apache.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:132) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > ... 20 more > Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException: > Could not find resource > 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. > at > org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsInputStream(DefaultResourceManager.java:91) > at > org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:117) > at > org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:100) > at > org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:159) > ... 25 more -- T
[jira] Commented: (MRELEASE-221) XML header missing in modified POM after release:prepare
[ http://jira.codehaus.org/browse/MRELEASE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94255 ] Alain Coetmeur commented on MRELEASE-221: - Hum... I've checked (latest snapshot) , I can repeat the problem pom.xml starts with: 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 maybe is it related to another problems, my release:prepare is interupted after the compilation of the project ( completedPhase=run-preparation-goals ) with a message before the checkin :An error is occurred in the checkin process: C:\Developpement\MavenWork\FWK DEI Module Trace Manager\pom.xml was not contained in C:\Developpement\MavenWork\FWK DEI Maven All this is because I use sibling module instead of sub directories... (another problem)... anyway it seems to happens at a moment the plugin wand to commit all. I use JDK1.6.0-b2, and maybe is it an XML problem... message at the end of the prepare ... [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 minute 23 seconds [INFO] Finished at: Thu Apr 26 19:16:06 CEST 2007 [INFO] Final Memory: 19M/61M [INFO] [INFO] Checking in modified POMs... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the checkin process: C:\Developpement\MavenWork\FWK DEI Module Trace Manager\pom.xml was not contained in C:\Developpement\MavenWork\FWK DEI Maven All > XML header missing in modified POM after release:prepare > > > Key: MRELEASE-221 > URL: http://jira.codehaus.org/browse/MRELEASE-221 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: Windows XP, CVSNT, Eclipse >Reporter: Alain Coetmeur > Fix For: 2.0-beta-5 > > > When release plugin modifies the POM to prepare a new release, > the new file does not containt the XML header > > it cause problems with XML editors who ignore the encoding and breaks all > unusual characters. > some XML tools also don't accept XML files without headers... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-223) Generated pom.xml has invalid chars (does not correctly handle xml entities)
[
http://jira.codehaus.org/browse/MRELEASE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94251
]
Alain Coetmeur commented on MRELEASE-223:
-
I have similar problem
because on my maven, release does not add
to the pom.xml.tag ...
do you have this header or not... if not it could explain why your editor does
not understand the stange character
(interpreted as UTF8)
however it seems they cannot reproduce the problem,
http://jira.codehaus.org/browse/MRELEASE-221
I'm checking...
> Generated pom.xml has invalid chars (does not correctly handle xml entities)
>
>
> Key: MRELEASE-223
> URL: http://jira.codehaus.org/browse/MRELEASE-223
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-4
>Reporter: Stefano Bagnara
>
> In our main pom we have this entry:
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
> in the resulting pom.xml the entity is converted to the real value, and the
> next time I try to use the pom it results in invalid output.
> {code:xml}
>
> hilmer
> Søren Hilmer
> sh at widetrail.dk
>
>
> Developer
>
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-224) When asking confirmation for SNASHOT plugin, no project name, many repetiton
When asking confirmation for SNASHOT plugin, no project name, many repetiton Key: MRELEASE-224 URL: http://jira.codehaus.org/browse/MRELEASE-224 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-5 Reporter: Alain Coetmeur Priority: Trivial I use the snapshot version of release plugin in all my POMs, thus the plugin ask me This project relies on a SNAPSHOT of the release plugin. This may be necessary during testing.: Do you want to continue with the release? (yes/no) no: : yes but it does that for each POM that use the parent POM in which Ive configured this snapshot, and also it does not gives the name of the project in cause... another improvement could be to ask only one time for each plugin and not for each plugin and POM. not very serious anyway... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SCM-304) CVS java implementation should work on Windows. should create .cvspass
CVS java implementation should work on Windows. should create .cvspass -- Key: SCM-304 URL: http://jira.codehaus.org/browse/SCM-304 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-cvs Affects Versions: 1.0-rc1 Environment: Windows Reporter: Alain Coetmeur Priority: Minor maven-scm-provider-cvs currently work only with the cvs_native implementation which ask for installation of CVSNT... it is not trivial and in some organisation (locked computer) it is not possible to install third-party software. So it would be very practical if the java implemenation was working on Windows. currently it fails because of ".cvspass" missing. -There should exist a tool, a mojo, to create this .cvspass, -or it should be created from uservame et password automatically if needed. here is the error message for example: [ERROR] Didn't find password for CVSROOT ':pserver:@serv:12021/serv/cvsdata/proj'. org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. at org.netbeans.lib.cvsclient.connection.PServerConnection.openConnection(PServerConnection.java:231) at org.netbeans.lib.cvsclient.connection.PServerConnection.open(PServerConnection.java:326) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.connect(CvsConnection.java:164) at org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand(CvsConnection.java:460) at org.apache.maven.scm.provider.cvslib.cvsjava.command.status.CvsJavaStatusCommand.executeCvsCommand(CvsJavaStatusCommand .java:50) at org.apache.maven.scm.provider.cvslib.command.status.AbstractCvsStatusCommand.executeStatusCommand(AbstractCvsStatusComm and.java:52) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1476) Upload org.bouncycastle:bcprov:jar:1.36 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94249 ] Matt Whitlock commented on MAVENUPLOAD-1476: I have created three new bundles: http://www.mattwhitlock.com/bcprov-jdk14-136-bundle.jar http://www.mattwhitlock.com/bcprov-jdk15-136-bundle.jar http://www.mattwhitlock.com/bcprov-jdk16-136-bundle.jar They have different artifactIds, and they use "bouncycastle" as the groupId and "136" as the version, to match the bouncycastle:bcprov-jd14:jar:136 artifact that is already in ibiblio. > Upload org.bouncycastle:bcprov:jar:1.36 to ibiblio > -- > > Key: MAVENUPLOAD-1476 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1476 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > > http://www.mattwhitlock.com/bcprov-1.36-bundle.jar > http://www.bouncycastle.org/java.html > The Bouncy Castle Crypto package is a Java implementation of cryptographic > algorithms. The package is organised so that it contains a light-weight API > suitable for use in any environment (including the newly released J2ME) with > the additional infrastructure to conform the algorithms to the JCE framework. > -- > The JDK14 version of bcprov 1.36 is already on ibiblio at > /maven2/bouncycastle/bcprov-jdk14/136, but its POM file is woefully > incomplete, its groupId is not in reverse domain order, and it lacks sources > and javadoc attachments. > I am submitting this bundle that contains the JDK14, JDK15, and JDK16 > versions of bcprov 1.36 along with sources and javadoc attachments for each. > The POM file in my bundle includes name, description, URL, and license > information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1149) Upload jboss-seam-ui-1.0.1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94245 ] Carlos Sanchez commented on MAVENUPLOAD-1149: - Please read http://maven.apache.org/guides/mini/guide-central-repository-upload.html for instructions creating a bundle version should be the same they publish, eg 1.0.1.GA > Upload jboss-seam-ui-1.0.1.jar > -- > > Key: MAVENUPLOAD-1149 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1149 > Project: maven-upload-requests > Issue Type: Task >Reporter: Phillip Singer > Attachments: jboss-seam-ui-1.0.1.jar, pom.xml > > > Note: I am not one of the developers. I would like to have this jar uploaded, > however, because the developers of the project refuse to do so (please see > http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached > has simply been renamed from the one in the seam download at > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 > to conform to your naming standards. The pom.xml file I have attached is one > which I have created using the most accurate information I could find. > I will be publishing an archetype to create a JBoss Seam application soon and > would appreciate having the dependencies readily availble to anyone who uses > the archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1147) Upload jboss-seam-1.0.1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1147. --- Assignee: Carlos Sanchez Resolution: Incomplete Please read http://maven.apache.org/guides/mini/guide-central-repository-upload.html for instructions creating a bundle version should be the same they publish, eg 1.0.1.GA > Upload jboss-seam-1.0.1.jar > --- > > Key: MAVENUPLOAD-1147 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1147 > Project: maven-upload-requests > Issue Type: Task >Reporter: Phillip Singer >Assignee: Carlos Sanchez > Attachments: jboss-seam-1.0.1.jar, pom.xml > > > Note: I am not one of the developers. I would like to have this jar uploaded, > however, because the developers of the project refuse to do so (please see > http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached > has simply been renamed from the one in the seam download at > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 > to conform to your naming standards. The pom.xml file I have attached is one > which I have created using the most accurate information I could find. > I will be publishing an archetype to create a JBoss Seam application soon and > would appreciate having the dependencies readily availble to anyone who uses > the archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1405) Eclipse SWT version 3.2.1 linux
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94248 ] Carlos Sanchez commented on MAVENUPLOAD-1405: - we'll upload this as part of the OSGi work being done, we just need more time to figure out some things > Eclipse SWT version 3.2.1 linux > > > Key: MAVENUPLOAD-1405 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1405 > Project: maven-upload-requests > Issue Type: Task >Reporter: Demchenko Vitaliy Victorovich > > SWT Eclipse version 3.2.1 for linux -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1148) Upload jboss-seam-debug-1.0.1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1148. --- Assignee: Carlos Sanchez Resolution: Incomplete Please read http://maven.apache.org/guides/mini/guide-central-repository-upload.html for instructions creating a bundle version should be the same they publish, eg 1.0.1.GA > Upload jboss-seam-debug-1.0.1.jar > - > > Key: MAVENUPLOAD-1148 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1148 > Project: maven-upload-requests > Issue Type: Task >Reporter: Phillip Singer >Assignee: Carlos Sanchez > Attachments: jboss-seam-debug-1.0.1.jar, pom.xml > > > Note: I am not one of the developers. I would like to have this jar uploaded, > however, because the developers of the project refuse to do so (please see > http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached > has simply been renamed from the one in the seam download at > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 > to conform to your naming standards. The pom.xml file I have attached is one > which I have created using the most accurate information I could find. > I will be publishing an archetype to create a JBoss Seam application soon and > would appreciate having the dependencies readily availble to anyone who uses > the archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1149) Upload jboss-seam-ui-1.0.1.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1149. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload jboss-seam-ui-1.0.1.jar > -- > > Key: MAVENUPLOAD-1149 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1149 > Project: maven-upload-requests > Issue Type: Task >Reporter: Phillip Singer >Assignee: Carlos Sanchez > Attachments: jboss-seam-ui-1.0.1.jar, pom.xml > > > Note: I am not one of the developers. I would like to have this jar uploaded, > however, because the developers of the project refuse to do so (please see > http://jira.jboss.org/jira/browse/JBSEAM-225). The jar that I have attached > has simply been renamed from the one in the seam download at > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=163777&release_id=425718 > to conform to your naming standards. The pom.xml file I have attached is one > which I have created using the most accurate information I could find. > I will be publishing an archetype to create a JBoss Seam application soon and > would appreciate having the dependencies readily availble to anyone who uses > the archetype. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-976) Please upload SUN Java 1.2 rutime
[ http://jira.codehaus.org/browse/MAVENUPLOAD-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-976. -- Assignee: Carlos Sanchez Resolution: Won't Fix I'd rather not put this there yet. It'd also need more info, like license, ... > Please upload SUN Java 1.2 rutime > -- > > Key: MAVENUPLOAD-976 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-976 > Project: maven-upload-requests > Issue Type: Task >Reporter: nicolas de loof >Assignee: Carlos Sanchez > > POM for the sun JRE 1.2 rt.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1305) XML Bind Runtime
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1305. --- Assignee: Carlos Sanchez Resolution: Incomplete missing parent pom > XML Bind Runtime > > > Key: MAVENUPLOAD-1305 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1305 > Project: maven-upload-requests > Issue Type: Task >Reporter: Seva Safris >Assignee: Carlos Sanchez > > The XML Bind solution is an alternative approach at XML binding for Java. The > Generator solution is capable of generating source code from an XSD, allowing > the Runtime to marshal and unmarshal those objects into XML. The builders are > responsible for defining task and plugin classes for use of this solution > with Ant and Maven. Builder-ant is for Ant, and Builder-maven is for Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1307) XML Bind Builder [Ant]
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1307. --- Assignee: Carlos Sanchez Resolution: Incomplete missing parent pom > XML Bind Builder [Ant] > -- > > Key: MAVENUPLOAD-1307 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1307 > Project: maven-upload-requests > Issue Type: Task >Reporter: Seva Safris >Assignee: Carlos Sanchez > > The XML Bind solution is an alternative approach at XML binding for Java. The > Generator solution is capable of generating source code from an XSD, allowing > the Runtime to marshal and unmarshal those objects into XML. The builders are > responsible for defining task and plugin classes for use of this solution > with Ant and Maven. Builder-ant is for Ant, and Builder-maven is for Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1306) XML Bind Generator
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1306. --- Assignee: Carlos Sanchez Resolution: Incomplete missing parent pom > XML Bind Generator > -- > > Key: MAVENUPLOAD-1306 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1306 > Project: maven-upload-requests > Issue Type: Task >Reporter: Seva Safris >Assignee: Carlos Sanchez > > The XML Bind solution is an alternative approach at XML binding for Java. The > Generator solution is capable of generating source code from an XSD, allowing > the Runtime to marshal and unmarshal those objects into XML. The builders are > responsible for defining task and plugin classes for use of this solution > with Ant and Maven. Builder-ant is for Ant, and Builder-maven is for Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1308) XML Bind Builder [Maven]
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1308. --- Assignee: Carlos Sanchez Resolution: Incomplete missing parent pom > XML Bind Builder [Maven] > > > Key: MAVENUPLOAD-1308 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1308 > Project: maven-upload-requests > Issue Type: Task >Reporter: Seva Safris >Assignee: Carlos Sanchez > > The XML Bind solution is an alternative approach at XML binding for Java. The > Generator solution is capable of generating source code from an XSD, allowing > the Runtime to marshal and unmarshal those objects into XML. The builders are > responsible for defining task and plugin classes for use of this solution > with Ant and Maven. Builder-ant is for Ant, and Builder-maven is for Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SCM-303) Unable to change maven.scm.provider.cvs.implementation from Maven POM/Settings
[
http://jira.codehaus.org/browse/SCM-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated SCM-303:
-
Fix Version/s: 1.0
> Unable to change maven.scm.provider.cvs.implementation from Maven POM/Settings
> --
>
> Key: SCM-303
> URL: http://jira.codehaus.org/browse/SCM-303
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-plugin
>Affects Versions: 1.0-rc1
> Environment: Windows, CVSNT, maven 1.0.6
>Reporter: Alain Coetmeur
>Priority: Minor
> Fix For: 1.0
>
>
> I did not find any way to set the system variable used by SCM internally like
> maven.scm.provider.cvs.implementation
> the only way is to add this to the command line
> -Dmaven.scm.provider.cvs.implementation=cvs_native which is error prone and
> awkward
> it should be possible to configure it in the POM and even through activated
> profiles...
> many other system properties may be usefull too.
> note that by the way setting maven.scm.provider.cvs.implementation to empty
> content
> should be accepted as "default behavior". it is needed if the property is
> always configured in a systemProperties element in configuration in plugin
> element, but with a value which is either empty or not depending on the OS.
> Ive tested, without success, simply adding POM or profile properties, or
> using "systemProperties" element in "configuration" for plugin
> like that :
>
> org.apache.maven.plugins
> maven-scm-plugin
>
> install
>
>
>
>
> maven.scm.provider.cvs.implementation
>
> ${maven.scm.provider.cvs.implementation}
>
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
>
> 2.0-beta-5-SNAPSHOT
>
>
> true
>
>
>
>
> maven.scm.provider.cvs.implementation
>
>
> ${maven.scm.provider.cvs.implementation}
>
>
>
>
>
>
>
>
>
> Windows
>
>
>
>
>
> cvs_native
>
>
>
>
> thanks 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] Closed: (MAVENUPLOAD-1362) Upload tapestry-flash to central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1362. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload tapestry-flash to central repo > - > > Key: MAVENUPLOAD-1362 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1362 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mark Reynolds >Assignee: Carlos Sanchez > > I asked the developer to upload to central repository and he suggested I do > it myself, so here it is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1361) Upload tapestry-prop 1.0.0 to Central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1361. --- Assignee: Carlos Sanchez Resolution: Incomplete parent is snapshot > Upload tapestry-prop 1.0.0 to Central repo > -- > > Key: MAVENUPLOAD-1361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1361 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mark Reynolds >Assignee: Carlos Sanchez > > I asked the developer to upload to central repository and he suggested that I > do it myself, so here it is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1393) xulfaces 0.9 Release for maven 2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1393. --- Assignee: Carlos Sanchez Resolution: Incomplete > xulfaces 0.9 Release for maven 2 > > > Key: MAVENUPLOAD-1393 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1393 > Project: maven-upload-requests > Issue Type: Task >Reporter: Olivier SCHMITT >Assignee: Carlos Sanchez > Attachments: xulfaces-renderkit-0.9-bundle.jar, > xulfaces-renderkit-0.9-javadoc.jar > > > xulfaces is a JSF RenderKit for XUL. It is an open source project under LGPL > license. > xulfaces integrates JSF with XUL > My name is olivier SCHMITT, alias [EMAIL PROTECTED], i'am the xulfaces admin. > It satisfies the following goals: > * Light deployment. > Mozilla and Firefox have an integrated XUL engine, so you can use your > favorite web browser to run an XUL application. > * Keep the business layer on the server side. > JSF and Ajax are used to build a bridge between the client and the server. > * rich UI features. > XUL offers a rich UI for business applications. XUL is a simple XML language. > There are trees, tabbed panes, list boxes, wizards and so on. You have the > ability to refresh the entire screen or a part of it. > Add power to xulfaces via this Tapestry-like framework based on JSF. > xulfaces is a JSF custom RenderKit and generates pure XUL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1267) Upload of novell jldap
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1267. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload of novell jldap > -- > > Key: MAVENUPLOAD-1267 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1267 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Boorshtein >Assignee: Carlos Sanchez > > I am a commiter for the openldap project (which hosts the source for JLDAP). > I can not find a commiter's list, but a search of openldap.org has several > pages of results with my 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] Closed: (MAVENUPLOAD-1346) New IzPack jar's
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1346. --- Assignee: Carlos Sanchez Resolution: Incomplete > New IzPack jar's > > > Key: MAVENUPLOAD-1346 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1346 > Project: maven-upload-requests > Issue Type: Task >Reporter: Ivan S. Dubrov >Assignee: Carlos Sanchez > > This is 3.9.0 version for IzPack standalone compiler and installer jar's. The > jar's were taken from installed IzPack 3.9.0 (the installer is available > here: http://prdownload.berlios.de/izpack/IzPack-install-3.9.0.jar) > IzPack is an installers generator for the Java platform. It produces > lightweight installers that can be run on any operating system where a Java > virtual machine is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1399) Upload xjavadoc 1.5 version to support JDK 1.5 annotations in xdoclet-maven-plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1399. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload xjavadoc 1.5 version to support JDK 1.5 annotations in > xdoclet-maven-plugin > -- > > Key: MAVENUPLOAD-1399 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1399 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Corridor Software Developer >Assignee: Carlos Sanchez > Attachments: xjavadoc-1.5-050611.jar > > > this bundle will upgrade the xjavadoc project in support of jdk 1.5 > annotations for the xdoclet-maven-plugin. Previous repo versions have a > parser to old to traverse annotation marks in newer code. > This is to support issue MOJO-665 an improvement to the xdoclet-maven-plugin > to support the newer code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1443) Dozer Maven Upload Request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1443. --- Assignee: Carlos Sanchez Resolution: Incomplete > Dozer Maven Upload Request > -- > > Key: MAVENUPLOAD-1443 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1443 > Project: maven-upload-requests > Issue Type: Task >Reporter: Franz Garsombke >Assignee: Carlos Sanchez > > http://dozer.sourceforge.net/dozer-3.1-bundle.jar > http://dozer.sourceforge.net > http://dozer.sourceforge.net/team-list.html > Dozer is a powerful, yet simple Java Bean to Java Bean mapper that > recursively copies data from one object to another. Typically, these Java > Beans will be of different complex types. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1355) Upload Core JSF Validator (commons validator integration)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1355. --- Assignee: Carlos Sanchez Resolution: Incomplete > Upload Core JSF Validator (commons validator integration) > - > > Key: MAVENUPLOAD-1355 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1355 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Raible >Assignee: Carlos Sanchez > > Downloaded source code from > http://www.horstmann.com/corejsf/corejsf-examples.zip -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1128) Rhino js-1.5R3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1128. --- Assignee: Carlos Sanchez Resolution: Fixed uploaded to rhino group > Rhino js-1.5R3 > -- > > Key: MAVENUPLOAD-1128 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1128 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Tomasz Pik >Assignee: Carlos Sanchez > > Rhino Java Script interpreter, with org.mozilla.javascript as groupId -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (SCM-303) Unable to change maven.scm.provider.cvs.implementation from Maven POM/Settings
Unable to change maven.scm.provider.cvs.implementation from Maven POM/Settings
--
Key: SCM-303
URL: http://jira.codehaus.org/browse/SCM-303
Project: Maven SCM
Issue Type: Improvement
Components: maven-plugin
Affects Versions: 1.0-rc1
Environment: Windows, CVSNT, maven 1.0.6
Reporter: Alain Coetmeur
Priority: Minor
I did not find any way to set the system variable used by SCM internally like
maven.scm.provider.cvs.implementation
the only way is to add this to the command line
-Dmaven.scm.provider.cvs.implementation=cvs_native which is error prone and
awkward
it should be possible to configure it in the POM and even through activated
profiles...
many other system properties may be usefull too.
note that by the way setting maven.scm.provider.cvs.implementation to empty
content
should be accepted as "default behavior". it is needed if the property is
always configured in a systemProperties element in configuration in plugin
element, but with a value which is either empty or not depending on the OS.
Ive tested, without success, simply adding POM or profile properties, or using
"systemProperties" element in "configuration" for plugin
like that :
org.apache.maven.plugins
maven-scm-plugin
install
maven.scm.provider.cvs.implementation
${maven.scm.provider.cvs.implementation}
org.apache.maven.plugins
maven-release-plugin
2.0-beta-5-SNAPSHOT
true
maven.scm.provider.cvs.implementation
${maven.scm.provider.cvs.implementation}
Windows
cvs_native
thanks 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] Closed: (MAVENUPLOAD-1130) Rhino js-1.5R4.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1130. --- Assignee: Carlos Sanchez Resolution: Won't Fix > Rhino js-1.5R4.1 > > > Key: MAVENUPLOAD-1130 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1130 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Tomasz Pik >Assignee: Carlos Sanchez > > Rhino Java Script interpreter. > Those are the same jars as in http://www.ibiblio.org/maven2/rhino/js/1.5R4.1/ > (and http://www.ibiblio.org/maven2/rhino/rhino/1.5R4.1/) but with > org.mozilla.javascript as groupId and improved pom file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1129) Rhino js-1.5R4-RC3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1129. --- Assignee: Carlos Sanchez Resolution: Won't Fix Already in rhino group, won't upload again, improved pom > Rhino js-1.5R4-RC3 > -- > > Key: MAVENUPLOAD-1129 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1129 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Tomasz Pik >Assignee: Carlos Sanchez > > Rhino Java Script interpreter. > This is the same jar as in http://www.ibiblio.org/maven2/rhino/js/1.5R4-RC3/ > but with org.mozilla.javascript as groupId and improved pom file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1476) Upload org.bouncycastle:bcprov:jar:1.36 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94234 ] Carlos Sanchez commented on MAVENUPLOAD-1476: - if they use different sources, which afaik is the case, they need to be different artifactIds, and thus different bundles > Upload org.bouncycastle:bcprov:jar:1.36 to ibiblio > -- > > Key: MAVENUPLOAD-1476 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1476 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > > http://www.mattwhitlock.com/bcprov-1.36-bundle.jar > http://www.bouncycastle.org/java.html > The Bouncy Castle Crypto package is a Java implementation of cryptographic > algorithms. The package is organised so that it contains a light-weight API > suitable for use in any environment (including the newly released J2ME) with > the additional infrastructure to conform the algorithms to the JCE framework. > -- > The JDK14 version of bcprov 1.36 is already on ibiblio at > /maven2/bouncycastle/bcprov-jdk14/136, but its POM file is woefully > incomplete, its groupId is not in reverse domain order, and it lacks sources > and javadoc attachments. > I am submitting this bundle that contains the JDK14, JDK15, and JDK16 > versions of bcprov 1.36 along with sources and javadoc attachments for each. > The POM file in my bundle includes name, description, URL, and license > information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1499) JEuclid 2.9.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94233 ] Carlos Sanchez commented on MAVENUPLOAD-1499: - You should remove the snapshot pluginRepositories > JEuclid 2.9.6 > - > > Key: MAVENUPLOAD-1499 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1499 > Project: maven-upload-requests > Issue Type: Task >Reporter: Max Berger > > Juclid is a complete MathML rendering solution, consisting of: a MathViewer > application, command line converters from MathML to other formats, an ant > task for autmated conversion, display components for AWT and Swing and a > component for Apache Cocoon. > This is the newest release. Thank you (also for uploading the older releases) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1501) Upload UrlRewriteFilter 3.0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94232 ] Carlos Sanchez commented on MAVENUPLOAD-1501: - and this is already in two different artifactIds, and now you are using a new groupid ?? > Upload UrlRewriteFilter 3.0.4 > - > > Key: MAVENUPLOAD-1501 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1501 > Project: maven-upload-requests > Issue Type: Task >Reporter: Paul Tuckey > > UrlRewriteFilter > Based on the popular and very useful mod_rewrite for apache, UrlRewriteFilter > is a Java Web Filter for any J2EE > compliant web application server (such as Resin, Orion or Tomcat), which > allows you to rewrite URLs before they get to > your code. It is a very powerful tool just like Apache's mod_rewrite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1500) Upload jMock 2.0.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1500. --- Resolution: Won't Fix > Upload jMock 2.0.0 > -- > > Key: MAVENUPLOAD-1500 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1500 > Project: maven-upload-requests > Issue Type: Task >Reporter: analogue >Assignee: Carlos Sanchez > > http://haroon.sis.utoronto.ca/jmock-1.2.0/jmock-1.2.0-bundle.jar > http://haroon.sis.utoronto.ca/jmock-1.2.0/jmock-cglib-1.2.0-bundle.jar > jMock is a library that supports test-driven development of Java code with > mock objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1501) Upload UrlRewriteFilter 3.0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94231 ] Carlos Sanchez commented on MAVENUPLOAD-1501: - cannot stat `urlrewrite-3.0.4.jar': No such file or directory artifactId doesn't match jar name > Upload UrlRewriteFilter 3.0.4 > - > > Key: MAVENUPLOAD-1501 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1501 > Project: maven-upload-requests > Issue Type: Task >Reporter: Paul Tuckey > > UrlRewriteFilter > Based on the popular and very useful mod_rewrite for apache, UrlRewriteFilter > is a Java Web Filter for any J2EE > compliant web application server (such as Resin, Orion or Tomcat), which > allows you to rewrite URLs before they get to > your code. It is a very powerful tool just like Apache's mod_rewrite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1488) rxtx. upload : java serial and parallel I/O API
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1488. --- Assignee: Carlos Sanchez Resolution: Fixed > rxtx. upload : java serial and parallel I/O API > --- > > Key: MAVENUPLOAD-1488 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1488 > Project: maven-upload-requests > Issue Type: Task >Reporter: Julien Vermillard >Assignee: Carlos Sanchez > > RXTX is a native lib providing serial and parallel communication for the Java > Development Toolkit (JDK). All deliverables are under the gnu LGPL license. > I upload it because I need it for apache MINA (for more info : [EMAIL > PROTECTED]), I'm not an RXTX developer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1502) JPF - Java Plugin Framework
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1502. --- Assignee: Carlos Sanchez Resolution: Fixed > JPF - Java Plugin Framework > --- > > Key: MAVENUPLOAD-1502 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1502 > Project: maven-upload-requests > Issue Type: Task >Reporter: Stefan >Assignee: Carlos Sanchez > > Two bundles: > http://files.sradonia.net/jpf/jpf-1.5-bundle.jar > http://files.sradonia.net/jpf/jpf-boot-1.5-bundle.jar > Project description: > JPF (Java Plugin Framework) is a general-purpose plug-in framework intended > to help building scalable, extendable Java applications with low cost of > maintenance. The framework is specially designed to be easily included into > Java project of any kind. > Please upload these two bundles to the central repository! Thank you very > much! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1496) Blogger API Client is an implementation of Blogger API for Java. Please upload!
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1496. --- Assignee: Carlos Sanchez Resolution: Fixed > Blogger API Client is an implementation of Blogger API for Java. Please > upload! > --- > > Key: MAVENUPLOAD-1496 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1496 > Project: maven-upload-requests > Issue Type: Task >Reporter: zhoushuqun >Assignee: Carlos Sanchez > > http://redv.com/blogger-api-client/downloads/blogger-api-client-1.1-bundle.jar > http://code.google.com/p/blogger-api-client/ > http://redv.com/blogger-api-client/team-list.html > Blogger API Client is an implementation of Blogger API for Java. Please > upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1497) Upload Unitils 1.0 rc 2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94230 ] Carlos Sanchez commented on MAVENUPLOAD-1497: - you got it wrong, provided scope is only used in very few cases like servlet-api, you want optional and not provided scope > Upload Unitils 1.0 rc 2 > --- > > Key: MAVENUPLOAD-1497 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1497 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tim Ducheyne > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1254) Clarification of Configuring Continuum as a Service in "Getting Started" Guide
[ http://jira.codehaus.org/browse/CONTINUUM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94229 ] Doug Tanner commented on CONTINUUM-1254: What problems arise from running the service as Local System? Should this not work properly running as Local System? > Clarification of Configuring Continuum as a Service in "Getting Started" Guide > -- > > Key: CONTINUUM-1254 > URL: http://jira.codehaus.org/browse/CONTINUUM-1254 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Reporter: James Williamson >Priority: Minor > > I was running the service using the Local System account Log On credentials. > I changed the Log On credentials to specify my NT Login and password and now > it works fine. > Looking back at the Continuum "Getting Started" Guide, it explicitly states: > "By default, the service logs on as the Local System account. Be sure to > change this to an account where you want the service to start upon login." > However, I had supposed this meant change it if you want the service to run > in some location other than your local machine. In fact, I discovered that > you will need to change it if you want your service to work correctly. > This document could be improved by stating: "Be sure to change this to an > account where you want the service to start upon login. If you are hosting > the service on your local machine you still need to specify your login > credentials in order for your service to function properly." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1493) Uploading pyx4me 2.0.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1493. --- Resolution: Fixed Yes, a release per top level groupId > Uploading pyx4me 2.0.1 to The Central Repository > > > Key: MAVENUPLOAD-1493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy >Assignee: Carlos Sanchez > Attachments: m2-sync-com.pyx4me.sh > > > The collection of maven-plugins and Archetype used develop applications for > the Java Micro Edition Platform > Upload has 3 parent poms to be loaded first. > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-518) Google Juice POM has wrong "" - should be "jar" and not "pom"
[ http://jira.codehaus.org/browse/MEV-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94227 ] Carlos Sanchez commented on MEV-518: See MAVENUPLOAD-1433 there are more problems than just the packaging > Google Juice POM has wrong "" - should be "jar" and not "pom" > > > Key: MEV-518 > URL: http://jira.codehaus.org/browse/MEV-518 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Arik Kfir > > The pom for guice-1.0 states a packaging of "pom", but it really represents a > jar (sits alongside the guice-1.0.jar file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1433) Include guice in the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1433. --- Assignee: Carlos Sanchez Resolution: Fixed Seems that it wasn't correctly removed, so now it's sitting there with wrong pom > Include guice in the central repository > --- > > Key: MAVENUPLOAD-1433 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1433 > Project: maven-upload-requests > Issue Type: Task >Reporter: Hani Suleiman >Assignee: Carlos Sanchez > Attachments: guice.jar, guice.jar, guice.jar > > > Would also appreciate it if someone could take a peek at the pom.xml to make > sure it's sane, as it's user contributed with some tweaks. jar file contains > the guice jar + pom.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-64) resource processing does not occur correct hierarchical modules.
[
http://jira.codehaus.org/browse/MWAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94225
]
Patrick Schneider commented on MWAR-64:
---
Adding ${basdir} to the element seems to work for me as well.
> resource processing does not occur correct hierarchical modules.
>
>
> Key: MWAR-64
> URL: http://jira.codehaus.org/browse/MWAR-64
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.0.1
> Environment: Windows XP
>Reporter: Brian Keyser
>
> I have a project that is similar to
> + - ProjectA
>|
>- pom.xml
>|
>+ ProjectB
> |
> - pom.xml
> Within the pom.xml for ProjectB there is an entry describing additional
> resources to include in the war
> ...
>
> org.apache.maven.plugins
> maven-war-plugin
>
>
>
> src/main/resources
> true
>
>
>
>
> ...
> When running 'mvn install' from the project A directory, I get the following
> error
> ...
> [INFO] Copy webapp webResources to
> C:\thinktank\thinktank-d1.1.0\server\server-webapp\target\server-webapp-1.1.0-SNAPSHOT
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] basedir src\main\resources does not exist
> [INFO]
>
> [DEBUG] Trace
> java.lang.IllegalStateException: basedir src\main\resources does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:542)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles(AbstractWarMojo.java:810)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:437)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:355)
> at
> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:161)
> at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:127)
> 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.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)
> However, if I change the to
> ...
> projectb/src/main/resources
> ...
> The install goal works fine.
> If I run 'mvn install' from projectb with the first configuration it does
> perform an install, ie, when the directory is configured as
> 'src/main/resources'. Seems like there is a problem in reading the base
> directory for hierarchical projects.
> Thanks for taking a look at this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-223) Generated pom.xml has invalid chars (does not correctly handle xml entities)
Generated pom.xml has invalid chars (does not correctly handle xml entities)
Key: MRELEASE-223
URL: http://jira.codehaus.org/browse/MRELEASE-223
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-4
Reporter: Stefano Bagnara
In our main pom we have this entry:
{code:xml}
hilmer
Søren Hilmer
sh at widetrail.dk
Developer
{code}
in the resulting pom.xml the entity is converted to the real value, and the
next time I try to use the pom it results in invalid output.
{code:xml}
hilmer
Søren Hilmer
sh at widetrail.dk
Developer
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-222) Wrong default tag name when used in a reactor environment
[ http://jira.codehaus.org/browse/MRELEASE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94222 ] Emmanuel Venisse commented on MRELEASE-222: --- The comment was that all your projects don't use the same parent and the release plugin choose the first project in the list instead of the root directory in the reactor list. > Wrong default tag name when used in a reactor environment > - > > Key: MRELEASE-222 > URL: http://jira.codehaus.org/browse/MRELEASE-222 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Stefano Bagnara >Assignee: Emmanuel Venisse >Priority: Critical > Fix For: 2.0-beta-5 > > > In JAMES project we have this structure (): > root (james-project) > - maven-skin (maven-skin) > - server (james-server-root) > - 2.2.0 (james-server-site-2-2-0) > All of them are in the org.apache.james groupId. > The main project have a site.xml declaring "maven-skin" as its own skin. > You can look at the real current poms here: > http://svn.apache.org/viewvc/james/project/trunk/pom.xml?revision=524429&view=markup > http://svn.apache.org/viewvc/james/project/trunk/maven-skin/pom.xml?revision=451625&view=markup > http://svn.apache.org/viewvc/james/project/trunk/server/pom.xml?revision=475214&view=markup > http://svn.apache.org/viewvc/james/project/trunk/server/2.2.0/pom.xml?revision=451625&view=markup > When I try to run "mvn release:prepare -DdryRun=true" it ask me the following: > - > [INFO] Checking dependencies and plugins for snapshots ... > What is the release version for "JAMES Skin"? (org.apache.james:maven-skin) > 1.1: : > What is the release version for "Apache JAMES Project"? > (org.apache.james:james-project) 1.1: : > What is the release version for "JAMES Server"? > (org.apache.james:james-server-root) 1.0: : > What is the release version for "JAMES Server 2.2.0 Documentation"? > (org.apache.james:james-server-site-2-2-0) 1.0: : > What is SCM release tag or label for "JAMES Skin"? > (org.apache.james:maven-skin) maven-skin-1.1: : > What is the new development version for "JAMES Skin"? > (org.apache.james:maven-skin) 1.2-SNAPSHOT: : > What is the new development version for "Apache JAMES Project"? > (org.apache.james:james-project) 1.2-SNAPSHOT: : > What is the new development version for "JAMES Server"? > (org.apache.james:james-server-root) 1.1-SNAPSHOT: : > What is the new development version for "JAMES Server 2.2.0 Documentation"? > (org.apache.james:james-server-site-2-2-0) 1.1-SNAPSHOT: : > - > Why do it asks me the SCM release tag for "JAMES Skin" and not for James > project? > Why my james-project pom.xml was: > http://svn.apache.org/viewvc/james/project/trunk > and in the pom.xml.tag I find > http://svn.apache.org/viewvc/james/project/tags/maven-skin-1.1 > The urls for the sub modules pom.xml.tag are instead correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRELEASE-222) Wrong default tag name when used in a reactor environment
[ http://jira.codehaus.org/browse/MRELEASE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRELEASE-222. - Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 2.0-beta-5 Already fixed. > Wrong default tag name when used in a reactor environment > - > > Key: MRELEASE-222 > URL: http://jira.codehaus.org/browse/MRELEASE-222 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Stefano Bagnara >Assignee: Emmanuel Venisse >Priority: Critical > Fix For: 2.0-beta-5 > > > In JAMES project we have this structure (): > root (james-project) > - maven-skin (maven-skin) > - server (james-server-root) > - 2.2.0 (james-server-site-2-2-0) > All of them are in the org.apache.james groupId. > The main project have a site.xml declaring "maven-skin" as its own skin. > You can look at the real current poms here: > http://svn.apache.org/viewvc/james/project/trunk/pom.xml?revision=524429&view=markup > http://svn.apache.org/viewvc/james/project/trunk/maven-skin/pom.xml?revision=451625&view=markup > http://svn.apache.org/viewvc/james/project/trunk/server/pom.xml?revision=475214&view=markup > http://svn.apache.org/viewvc/james/project/trunk/server/2.2.0/pom.xml?revision=451625&view=markup > When I try to run "mvn release:prepare -DdryRun=true" it ask me the following: > - > [INFO] Checking dependencies and plugins for snapshots ... > What is the release version for "JAMES Skin"? (org.apache.james:maven-skin) > 1.1: : > What is the release version for "Apache JAMES Project"? > (org.apache.james:james-project) 1.1: : > What is the release version for "JAMES Server"? > (org.apache.james:james-server-root) 1.0: : > What is the release version for "JAMES Server 2.2.0 Documentation"? > (org.apache.james:james-server-site-2-2-0) 1.0: : > What is SCM release tag or label for "JAMES Skin"? > (org.apache.james:maven-skin) maven-skin-1.1: : > What is the new development version for "JAMES Skin"? > (org.apache.james:maven-skin) 1.2-SNAPSHOT: : > What is the new development version for "Apache JAMES Project"? > (org.apache.james:james-project) 1.2-SNAPSHOT: : > What is the new development version for "JAMES Server"? > (org.apache.james:james-server-root) 1.1-SNAPSHOT: : > What is the new development version for "JAMES Server 2.2.0 Documentation"? > (org.apache.james:james-server-site-2-2-0) 1.1-SNAPSHOT: : > - > Why do it asks me the SCM release tag for "JAMES Skin" and not for James > project? > Why my james-project pom.xml was: > http://svn.apache.org/viewvc/james/project/trunk > and in the pom.xml.tag I find > http://svn.apache.org/viewvc/james/project/tags/maven-skin-1.1 > The urls for the sub modules pom.xml.tag are instead correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-222) Wrong default tag name when used in a reactor environment
Wrong default tag name when used in a reactor environment - Key: MRELEASE-222 URL: http://jira.codehaus.org/browse/MRELEASE-222 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Reporter: Stefano Bagnara Priority: Critical In JAMES project we have this structure (): root (james-project) - maven-skin (maven-skin) - server (james-server-root) - 2.2.0 (james-server-site-2-2-0) All of them are in the org.apache.james groupId. The main project have a site.xml declaring "maven-skin" as its own skin. You can look at the real current poms here: http://svn.apache.org/viewvc/james/project/trunk/pom.xml?revision=524429&view=markup http://svn.apache.org/viewvc/james/project/trunk/maven-skin/pom.xml?revision=451625&view=markup http://svn.apache.org/viewvc/james/project/trunk/server/pom.xml?revision=475214&view=markup http://svn.apache.org/viewvc/james/project/trunk/server/2.2.0/pom.xml?revision=451625&view=markup When I try to run "mvn release:prepare -DdryRun=true" it ask me the following: - [INFO] Checking dependencies and plugins for snapshots ... What is the release version for "JAMES Skin"? (org.apache.james:maven-skin) 1.1: : What is the release version for "Apache JAMES Project"? (org.apache.james:james-project) 1.1: : What is the release version for "JAMES Server"? (org.apache.james:james-server-root) 1.0: : What is the release version for "JAMES Server 2.2.0 Documentation"? (org.apache.james:james-server-site-2-2-0) 1.0: : What is SCM release tag or label for "JAMES Skin"? (org.apache.james:maven-skin) maven-skin-1.1: : What is the new development version for "JAMES Skin"? (org.apache.james:maven-skin) 1.2-SNAPSHOT: : What is the new development version for "Apache JAMES Project"? (org.apache.james:james-project) 1.2-SNAPSHOT: : What is the new development version for "JAMES Server"? (org.apache.james:james-server-root) 1.1-SNAPSHOT: : What is the new development version for "JAMES Server 2.2.0 Documentation"? (org.apache.james:james-server-site-2-2-0) 1.1-SNAPSHOT: : - Why do it asks me the SCM release tag for "JAMES Skin" and not for James project? Why my james-project pom.xml was: http://svn.apache.org/viewvc/james/project/trunk and in the pom.xml.tag I find http://svn.apache.org/viewvc/james/project/tags/maven-skin-1.1 The urls for the sub modules pom.xml.tag are instead correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-136) The plugin does not use JAVA_HOME variable and launches default JVM
[ http://jira.codehaus.org/browse/SUREFIRE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94217 ] Jonas Olsson commented on SUREFIRE-136: --- A work-around is to edit the mvn-script to insert JAVA_HOME/bin at head of PATH before execution. > The plugin does not use JAVA_HOME variable and launches default JVM > --- > > Key: SUREFIRE-136 > URL: http://jira.codehaus.org/browse/SUREFIRE-136 > Project: Maven Surefire > Issue Type: Improvement > Environment: Windows 2000, Maven 2.0.4 >Reporter: Andrey Somov >Assignee: Carlos Sanchez >Priority: Minor > Fix For: 2.4 > > Attachments: MSUREFIREREP-25.log > > > The plugin does not use JAVA_HOME variable and launches default JVM (in this > case default is not defined): > [INFO] Surefire report directory: > D:\tools\workspace\DB2Monster\monster-axis\target\surefire-reports > 'java' is not recognized as an internal or external command, > operable program or batch file. > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > JAVA_HOME does not necessary point to the default JVM. > The plugin shall use the same JVM as Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRAR-16) Missing artifact handler descriptor
Missing artifact handler descriptor --- Key: MRAR-16 URL: http://jira.codehaus.org/browse/MRAR-16 Project: Maven 2.x Rar Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Florent Guillaume When using this plugin, no .classpath is generated, and the .project does not contain a build or the java nature. See http://www.mail-archive.com/[EMAIL PROTECTED]/msg65470.html Emmanuel says: > It's a problem on the rar plugin that doesn't have an artifact handler > descriptor. > The eclipse plugin look at the handler to define if it's a java project or > not, and without this > handler, the language of rar project is defined by default to "none" instead > of "jar". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MCHECKSTYLE-54) checkstyle:check does not see provided scope dependencies
[ http://jira.codehaus.org/browse/MCHECKSTYLE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94216 ] Yoav Shapira commented on MCHECKSTYLE-54: - This issue still happens with Maven 2.0.5 and 2.0.6 on Windows XP, JDK5 and JDK6 both tested. > checkstyle:check does not see provided scope dependencies > - > > Key: MCHECKSTYLE-54 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-54 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Stephen Duncan Jr >Priority: Critical > > Running checkstyle:check against a project that uses Exceptions from > dependencies that are provided scope causes checktyle errors such as the > following: > name="/share/duncans/workspace/eclipse/cdcie-webapp-feedreader/src/main/java/mil/jfcom/cie/portal/feedreader/converter/ConverterImpl.java"> > > These errors go away when the scope is changed to compile. This does not > happen for checkstyle:checkstyle; the report correct indicates no checkstyle > errors. This is preventing us from using the checkstyle plugin to enforce > checkstyle rules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-157) Share version for multi-module releases
[ http://jira.codehaus.org/browse/MRELEASE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94215 ] Tom Schneider commented on MRELEASE-157: Thanks for the speedy response. Having this functionality will really help us out. (And others as well I hope) > Share version for multi-module releases > --- > > Key: MRELEASE-157 > URL: http://jira.codehaus.org/browse/MRELEASE-157 > Project: Maven 2.x Release Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-4 >Reporter: Joerg Schaible >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > Attachments: release-plugin-autoVersionSubmodules.patch > > > In our setup all artifacts of a multi-module setup share the same release. > Therefore it would be really good, if we could configure the plugin (e.g. > shareVersion=true) to ask once for the version to release and once for the > version to set after the release for all modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2854) Recreating pom.properties always breaks the archivers uptodate check
[
http://jira.codehaus.org/browse/MNG-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94213
]
Trygve Laugstol commented on MNG-2854:
--
A couple of code comments:
* Call the class PomPropertiesUtil instead of Manager. There are a lot of other
Manager classes in Maven and they are Plexus components, while this is a normal
utility class.
* Use org.codehaus.plexus.util.IOUtil.close() to close streams.
* When comparing the properties file why not generate Properties object and
load the existing properties file and use Properties.equals()? That should save
you some hassle.
> Recreating pom.properties always breaks the archivers uptodate check
>
>
> Key: MNG-2854
> URL: http://jira.codehaus.org/browse/MNG-2854
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.5
>Reporter: Jochen Wiedmann
> Attachments: maven-archiver-properties-2.patch,
> maven-archiver-properties.patch
>
>
> The maven-archiver creates a file called pom.properties on every invocation.
> (Unless the flag "addMavenDescriptor" is set to false, which few people do.)
> This forced recreation makes the uptodate check fail. In other words, jar
> files are always recreated, regardless whether anything was recompiled.
> Obviously, this makes the uptodate check of war files etc. fail as well,
> because the included jar files are always changed.. This is a major drawback,
> because it makes Maven much slower than, for example, Ant-.
> The attached patch proposes a solution for the same problem. What the patch
> does:
> - It is obviously bad, that the generated pom.properties file is in the
> projects directory. The
> patch moves the file to ${project.build.directory}/maven-archiver, which
> seems to me to
> be a more sensible solution.
> - Second, whether we like it or not, there are projects, which create
> multiple artifacts. In other
> words, it isn't good to have a single file. The patch renames the
> pom.properties file to
> ${groupId}/$artifactFinalName.properties. Hopefully, this is sufficiently
> unique.
> - Finally, the patch makes the maven-archiver check, whether the
> pom.properties file has
> actually changed. (In other words, whether groupId, artifactId, or version
> have changed.)
> It does so, by writing the file to an internal buffer and comparing the
> file on the disk and
> the internal buffer (after skipping the line with the timestamp).
> In other words, in the usual case, where groupId, artifactId and version
> haven't changed, the pom.properties file remains unchanged. In particular,
> the jar file doesn't need to be recreated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2964) Need documentation about Maven2 logging
Need documentation about Maven2 logging --- Key: MNG-2964 URL: http://jira.codehaus.org/browse/MNG-2964 Project: Maven 2 Issue Type: Improvement Components: Documentation: Faqs Affects Versions: 2.0.5 Reporter: Tano Dzhinski How to set message level for maven2 output? (it always shows INFO level messages) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRELEASE-191) Certain tests fail when checked-out in 'projects' subdir
[ http://jira.codehaus.org/browse/MRELEASE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRELEASE-191. - Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 2.0-beta-5 Applied. Thanks. > Certain tests fail when checked-out in 'projects' subdir > > > Key: MRELEASE-191 > URL: http://jira.codehaus.org/browse/MRELEASE-191 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Mark Hobson >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > Attachments: patch.txt > > > (Note this should be filed under maven-release-manager, but no such JIRA > project exists yet.) > Tests that use AbstractReleaseTestCase.createReactorProjects fail if the > project is checked-out in a sub-directory of 'projects', since the code > assumes the 'projects' directory in question is 'src/test/resources/projects'. > The attached patch changes the assumption to use 'test-classes' directory > instead, still not ideal but less problematic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRM-323) Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)
[ http://jira.codehaus.org/browse/MRM-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-323: - Affects Version/s: 1.0 > Managed repo in archiva cannot be accessed thru direct webdav url even with > valid credentials (Archiva deployed in Tomcat) > -- > > Key: MRM-323 > URL: http://jira.codehaus.org/browse/MRM-323 > Project: Archiva > Issue Type: Bug > Components: WebDAV interface >Affects Versions: 1.0 > Environment: - Tomcat 5.5.20 > - Linux > - Mozilla Firefox >Reporter: Maria Odea Ching > > Steps to re-create issue: > - Deploy Archiva in Tomcat, then start tomcat > - Access Archiva in browser and set the required configurations > - Add A Managed Repository with the following configuration: > - id: snapshots > - name: snapshots > - url: snapshots (it would have the value > http://localhost:[PORT]/archiva/repository/snapshots) > - directory: snapshots > - Go to User Management and add the Repository Observer role for the > 'snapshots' repo to the current user > - Open a new tab in your browser then type the webdav URL: > http://localhost:[PORT]/archiva/repository/snapshots > - Supply the user credentials for the 'snapshots' repository. You still > wouldn't be able to access it even if you supply the correct credentials. > Also, the following error shows up in the Archiva logs when you try to build > a Maven project with your settings.xml file configured to use the > repositories in archiva: > 102476 [http-9696-Processor23] ERROR > org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/archiva].[RepositoryServlet] > - Servlet.service() for servlet RepositoryServlet threw exception > javax.servlet.ServletException: Unable to service DAV request due to > unconfigured DavServerComponent for prefix [snapshots]. > at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:93) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-323) Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)
Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat) -- Key: MRM-323 URL: http://jira.codehaus.org/browse/MRM-323 Project: Archiva Issue Type: Bug Components: WebDAV interface Environment: - Tomcat 5.5.20 - Linux - Mozilla Firefox Reporter: Maria Odea Ching Steps to re-create issue: - Deploy Archiva in Tomcat, then start tomcat - Access Archiva in browser and set the required configurations - Add A Managed Repository with the following configuration: - id: snapshots - name: snapshots - url: snapshots (it would have the value http://localhost:[PORT]/archiva/repository/snapshots) - directory: snapshots - Go to User Management and add the Repository Observer role for the 'snapshots' repo to the current user - Open a new tab in your browser then type the webdav URL: http://localhost:[PORT]/archiva/repository/snapshots - Supply the user credentials for the 'snapshots' repository. You still wouldn't be able to access it even if you supply the correct credentials. Also, the following error shows up in the Archiva logs when you try to build a Maven project with your settings.xml file configured to use the repositories in archiva: 102476 [http-9696-Processor23] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/archiva].[RepositoryServlet] - Servlet.service() for servlet RepositoryServlet threw exception javax.servlet.ServletException: Unable to service DAV request due to unconfigured DavServerComponent for prefix [snapshots]. at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:93) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-518) Google Juice POM has wrong "" - should be "jar" and not "pom"
Google Juice POM has wrong "" - should be "jar" and not "pom" Key: MEV-518 URL: http://jira.codehaus.org/browse/MEV-518 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Arik Kfir The pom for guice-1.0 states a packaging of "pom", but it really represents a jar (sits alongside the guice-1.0.jar file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-191) Certain tests fail when checked-out in 'projects' subdir
[ http://jira.codehaus.org/browse/MRELEASE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94194 ] Mark Hobson commented on MRELEASE-191: -- Any chance of squeezing this into 2.0-beta-5 please? > Certain tests fail when checked-out in 'projects' subdir > > > Key: MRELEASE-191 > URL: http://jira.codehaus.org/browse/MRELEASE-191 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Mark Hobson > Attachments: patch.txt > > > (Note this should be filed under maven-release-manager, but no such JIRA > project exists yet.) > Tests that use AbstractReleaseTestCase.createReactorProjects fail if the > project is checked-out in a sub-directory of 'projects', since the code > assumes the 'projects' directory in question is 'src/test/resources/projects'. > The attached patch changes the assumption to use 'test-classes' directory > instead, still not ideal but less problematic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRELEASE-157) Share version for multi-module releases
[ http://jira.codehaus.org/browse/MRELEASE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRELEASE-157. - Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 2.0-beta-5 Applied with some code aggregation in MapVersionsPhase > Share version for multi-module releases > --- > > Key: MRELEASE-157 > URL: http://jira.codehaus.org/browse/MRELEASE-157 > Project: Maven 2.x Release Plugin > Issue Type: New Feature >Affects Versions: 2.0-beta-4 >Reporter: Joerg Schaible >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > Attachments: release-plugin-autoVersionSubmodules.patch > > > In our setup all artifacts of a multi-module setup share the same release. > Therefore it would be really good, if we could configure the plugin (e.g. > shareVersion=true) to ask once for the version to release and once for the > version to set after the release for all modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2788) Anchor tags on POM amd Settings reference pages are broken in Firefox
[ http://jira.codehaus.org/browse/MNG-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94188 ] Dennis Lundberg commented on MNG-2788: -- These pages are generated. > Anchor tags on POM amd Settings reference pages are broken in Firefox > - > > Key: MNG-2788 > URL: http://jira.codehaus.org/browse/MNG-2788 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.4 > Environment: Firefox 2.0.0.1 on Windows XP SP2. >Reporter: Ryan Breidenbach >Assignee: Dennis Lundberg >Priority: Trivial > Attachments: pom.html.diff > > > The TOC anchors at the top of the POM and Settings Reference pages do not > work in Firefox. It appears that all of the anchor links are capitalized > while the anchor labels are all lower case. Also, some of the links contain > spaces while the labels contain underscores. This is causing the links to > fail in Firefox. > http://maven.apache.org/pom.html > http://maven.apache.org/settings.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] Closed: (MRELEASE-221) XML header missing in modified POM after release:prepare
[ http://jira.codehaus.org/browse/MRELEASE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed MRELEASE-221. - Resolution: Cannot Reproduce Fix Version/s: 2.0-beta-5 The xml header is in the POM > XML header missing in modified POM after release:prepare > > > Key: MRELEASE-221 > URL: http://jira.codehaus.org/browse/MRELEASE-221 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: Windows XP, CVSNT, Eclipse >Reporter: Alain Coetmeur > Fix For: 2.0-beta-5 > > > When release plugin modifies the POM to prepare a new release, > the new file does not containt the XML header > > it cause problems with XML editors who ignore the encoding and breaks all > unusual characters. > some XML tools also don't accept XML files without headers... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2788) Anchor tags on POM amd Settings reference pages are broken in Firefox
[ http://jira.codehaus.org/browse/MNG-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wing-tung Leung updated MNG-2788: - Attachment: pom.html.diff This patch fixed the HTML anchors in the top menu, in order to match the target names. > Anchor tags on POM amd Settings reference pages are broken in Firefox > - > > Key: MNG-2788 > URL: http://jira.codehaus.org/browse/MNG-2788 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.4 > Environment: Firefox 2.0.0.1 on Windows XP SP2. >Reporter: Ryan Breidenbach >Assignee: Dennis Lundberg >Priority: Trivial > Attachments: pom.html.diff > > > The TOC anchors at the top of the POM and Settings Reference pages do not > work in Firefox. It appears that all of the anchor links are capitalized > while the anchor labels are all lower case. Also, some of the links contain > spaces while the labels contain underscores. This is causing the links to > fail in Firefox. > http://maven.apache.org/pom.html > http://maven.apache.org/settings.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: (MNG-2788) Anchor tags on POM amd Settings reference pages are broken in Firefox
[ http://jira.codehaus.org/browse/MNG-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94177 ] wing-tung Leung commented on MNG-2788: -- Are these simply static HTML pages? If so, I'm happy to provide you the patch or updated page with corrected links. IMHO, this is not a Firefox issue, because it interprets the HTML correctly. > Anchor tags on POM amd Settings reference pages are broken in Firefox > - > > Key: MNG-2788 > URL: http://jira.codehaus.org/browse/MNG-2788 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.4 > Environment: Firefox 2.0.0.1 on Windows XP SP2. >Reporter: Ryan Breidenbach >Assignee: Dennis Lundberg >Priority: Trivial > > The TOC anchors at the top of the POM and Settings Reference pages do not > work in Firefox. It appears that all of the anchor links are capitalized > while the anchor labels are all lower case. Also, some of the links contain > spaces while the labels contain underscores. This is causing the links to > fail in Firefox. > http://maven.apache.org/pom.html > http://maven.apache.org/settings.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] Updated: (MRM-322) Add proxied repository page lacks '*' on identifier field.
[ http://jira.codehaus.org/browse/MRM-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated MRM-322: Attachment: MRM-322-archiva-webapp.patch Patch attached. > Add proxied repository page lacks '*' on identifier field. > -- > > Key: MRM-322 > URL: http://jira.codehaus.org/browse/MRM-322 > Project: Archiva > Issue Type: Improvement > Components: web application >Reporter: Teodoro Cue Jr. >Priority: Minor > Attachments: MRM-322-archiva-webapp.patch > > > The Identifier field is required so '*' should be put beside it just like the > other required fields in the application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-1493) Uploading pyx4me 2.0.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Skarzhevskyy updated MAVENUPLOAD-1493: --- Attachment: m2-sync-com.pyx4me.sh Created release directory web access http://pyx4me.com/maven2-release/ rsync script created --- Carlos, for another project org/microemu/ published in the same directory should I create a new script ? > Uploading pyx4me 2.0.1 to The Central Repository > > > Key: MAVENUPLOAD-1493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1493 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy >Assignee: Carlos Sanchez > Attachments: m2-sync-com.pyx4me.sh > > > The collection of maven-plugins and Archetype used develop applications for > the Java Micro Edition Platform > Upload has 3 parent poms to be loaded first. > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-maven-plugins-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/proguard-maven-plugin-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/pyx4me-archetypes-parent-2.0.1-bundle.jar > http://www.pyx4j.com/downloads/pyx4me-2.0.1/j2me-simple-2.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-322) Add proxied repository page lacks '*' on identifier field.
Add proxied repository page lacks '*' on identifier field. -- Key: MRM-322 URL: http://jira.codehaus.org/browse/MRM-322 Project: Archiva Issue Type: Improvement Components: web application Reporter: Teodoro Cue Jr. Priority: Minor The Identifier field is required so '*' should be put beside it just like the other required fields in the application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MSOURCES-16) Unable to find the mojo 'org.apache.maven.plugins:maven-source-plugin:2.0.3:aggregate'
Unable to find the mojo 'org.apache.maven.plugins:maven-source-plugin:2.0.3:aggregate' -- Key: MSOURCES-16 URL: http://jira.codehaus.org/browse/MSOURCES-16 Project: Maven 2.x Sources Plugin Issue Type: Bug Affects Versions: 2.0.3 Environment: mvn 2.0.6 Reporter: KlaasJan Elzinga With a multi module project I receive the following exception: [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-source-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-source-plugin:2.0.3:aggregate' in the plu gin 'org.apache.maven.plugins:maven-source-plugin' org/codehaus/plexus/archiver/ArchiverException [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error getting reports from the plugin 'org.apache.maven.plugins:maven-source-plugin': Unable to find the mojo 'org.apache.maven.plugin s:maven-source-plugin:2.0.3:aggregate' in the plugin 'org.apache.maven.plugins:maven-source-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:642) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.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: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-source-plugin:2.0.3:aggregate' in the plugin 'org.apache.maven.plugins:mave n-source-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571) at org.apache.maven.plugin.DefaultPluginManager.getReport(DefaultPluginManager.java:495) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:683) ... 18 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-source-plugin:2 .0.3:aggregate', 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) ... 20 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: 'org.apache.maven.plugin.source.AggregatorSou rceJarMojo' 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) ... 22 more Caused by: java.lang.NoClassDefFoun
