[jira] Commented: (MAVENUPLOAD-1335) Please upload OpenOffice.org Java/Uno JARs 2.1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85967 ] Carlos Sanchez commented on MAVENUPLOAD-1335: - by convention artifactId is set to the name of the jar, so it should be juh, jurt,... They will be under org.openoffice so there will be no clashes > Please upload OpenOffice.org Java/Uno JARs 2.1.0 > > > Key: MAVENUPLOAD-1335 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1335 > Project: maven-upload-requests > Issue Type: Task >Reporter: Mirko Nasato > > OpenOffice.org includes some JARs that can be used in a standalone Java app > to connect to a running OpenOffice.org instance. > The OpenOffice.org team agreed to distributing those JARs through Maven 2 and > assigned the task to myself > http://www.openoffice.org/issues/show_bug.cgi?id=71358 > Please find the bundles here > http://jooreports.sourceforge.net/m2/openoffice.org-juh-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-jurt-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-ridl-2.1.0-bundle.jar > http://jooreports.sourceforge.net/m2/openoffice.org-unoil-2.1.0-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] Closed: (MAVENUPLOAD-1321) jawin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1321. --- Assignee: Carlos Sanchez Resolution: Incomplete > jawin > - > > Key: MAVENUPLOAD-1321 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1321 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Anna Alekseevna Nejentseva > Assigned To: Carlos Sanchez > Attachments: jawin.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] Closed: (MAVENUPLOAD-1329) WizCrypt 2.2 Release Jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1329. --- Assignee: Carlos Sanchez Resolution: Fixed > WizCrypt 2.2 Release Jars > - > > Key: MAVENUPLOAD-1329 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1329 > Project: maven-upload-requests > Issue Type: Task >Reporter: Subhash Chandran > Assigned To: Carlos Sanchez > > Bundle Jar: > http://wiztools.org/upload/wizcrypt-2.2-bundle.jar > Project URL: > http://wizcrypt.wiztools.org/ > My name and email in the project site: > http://wizcrypt.wiztools.org/team-list.html > 2.2 version of WizCrypt is an important release for it speeds up the IO > operation. It is also being used in the swing based encryption tool > jEnkryptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1327) uploading bluecove-1.2.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1327. --- Assignee: Carlos Sanchez Resolution: Fixed > uploading bluecove-1.2.1 to The Central Repository > --- > > Key: MAVENUPLOAD-1327 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1327 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy > Assigned To: Carlos Sanchez > > http://pyx4j.com/downloads/bluecove-1.2.1-bundle.jar > BlueCove is a LGPL licensed JSR-82 implementation that currently interfaces > with the Microsoft Bluetooth stack -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1332) uploading jfig-1.5.1 to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1332. --- Assignee: Carlos Sanchez Resolution: Fixed > uploading jfig-1.5.1 to The Central Repository > -- > > Key: MAVENUPLOAD-1332 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1332 > Project: maven-upload-requests > Issue Type: Task >Reporter: Vlad Skarzhevskyy > Assigned To: Carlos Sanchez > > http://pyx4j.com/downloads/jfig-1.5.1-bundle.jar > A Configuration utility that provides simple, flexible and powerful > functionality for managing one or more configurations in a java environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1333) Version 1.3 of UISPec4J
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1333. --- Assignee: Carlos Sanchez Resolution: Fixed > Version 1.3 of UISPec4J > --- > > Key: MAVENUPLOAD-1333 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1333 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Pascal Pratmarty > Assigned To: Carlos Sanchez > Attachments: uispec4j-1.3-bundle.jar > > > UISpec4J is an Open Source functional and/or unit testing library for > Swing-based Java applications, built on top of the JUnit test harness. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1336) SoftEU URL Rewriter
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1336. --- Assignee: Carlos Sanchez Resolution: Fixed > SoftEU URL Rewriter > --- > > Key: MAVENUPLOAD-1336 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1336 > Project: maven-upload-requests > Issue Type: Task >Reporter: Petr Ferschmann > Assigned To: Carlos Sanchez > > URL Rewriter is a tool for rewriting URLs in Java Servlets. It is similar to > apache 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] Commented: (MAVENUPLOAD-1339) WebworkWebflow version 1.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85966 ] Carlos Sanchez commented on MAVENUPLOAD-1339: - googlecode.com does not exist, so you cant use it as groupId. Also you need to provide the parent pom > WebworkWebflow version 1.0.1 > > > Key: MAVENUPLOAD-1339 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1339 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tom Schneider > Attachments: webworkwebflow-plugin-1.0.1-bundle.jar > > > http://webworkwebflow.googlecode.com/files/webworkwebflow-plugin-1.0.1-bundle.jar > http://code.google.com/p/webworkwebflow/ > http://wiki.opensymphony.com/display/WW/Spring+Webflow > WebworkWebflow provides integration between Spring Webflow and Webwork. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1310) NanoXML Lite
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85965 ] Carlos Sanchez commented on MAVENUPLOAD-1310: - none of the two errors commented has been fixed > NanoXML Lite > > > Key: MAVENUPLOAD-1310 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1310 > Project: maven-upload-requests > Issue Type: Task >Reporter: Tassilo Schweyer > > NanoXML Lite is an extremely small (6KB) XML parser -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1338) JUnit-Toolkit version 0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1338. --- Assignee: Carlos Sanchez Resolution: Fixed > JUnit-Toolkit version 0.4 > - > > Key: MAVENUPLOAD-1338 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1338 > Project: maven-upload-requests > Issue Type: Task >Reporter: Rupert Smith > Assigned To: Carlos Sanchez > Attachments: junit-toolkit-0.4-bundle.jar > > > http://www.thebadgerset.co.uk/junit-toolkit/junit-toolkit-0.4-bundle.jar > http://www.thebadgerset.co.uk/junit-toolkit/ > http://www.thebadgerset.co.uk/junit-toolkit/team-list.html > JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour > analysis, and concurrency testing. > Version 0.4 adds a new test runner with more features and fixes all memory > leaks that would prevent its use in longer running tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1337) Upload of latest Findbugs (v. 1.1.3) artifacts to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85964 ] Carlos Sanchez commented on MAVENUPLOAD-1337: - file does not exist > Upload of latest Findbugs (v. 1.1.3) artifacts to ibiblio > - > > Key: MAVENUPLOAD-1337 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1337 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jon Christiansen > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1340) Upload hibernate-tools 3.2.0-beta9a
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85962 ] Carlos Sanchez commented on MAVENUPLOAD-1340: - missing license and scm entry in jtidy pom > Upload hibernate-tools 3.2.0-beta9a > --- > > Key: MAVENUPLOAD-1340 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1340 > Project: maven-upload-requests > Issue Type: Task >Reporter: Johann Reyes > > http://hiberforum.org/hibernate-tools-3.2.0.beta9a-bundle.jar > http://hiberforum.org/jtidy-r8-20060801-bundle.jar > http://tools.hibernate.org > Please upload new version of hibernate-tools + updated dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-675) Add Working Copy to the Legends
[ http://jira.codehaus.org/browse/CONTINUUM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry S. Isidro updated CONTINUUM-675: -- Attachment: legendbg.gif File Attached: legendbg.gif This is the background gif for the legends list. > Add Working Copy to the Legends > --- > > Key: CONTINUUM-675 > URL: http://jira.codehaus.org/browse/CONTINUUM-675 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Shinobu Kawai >Priority: Trivial > Fix For: 1.1 > > Attachments: [CONTINUUM-675]-continuum-webapp.patch, legendbg.gif > > > Add "Working Copy" to the Legends on the left -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1320) Javassist 3.1 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1320. --- Assignee: Carlos Sanchez Resolution: Fixed > Javassist 3.1 upload request > > > Key: MAVENUPLOAD-1320 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1320 > Project: maven-upload-requests > Issue Type: Task >Reporter: Hugo Palma > Assigned To: Carlos Sanchez > > Simple Java bytecode manipulation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1330) jsr107cache-1.0 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-1330. --- Assignee: Carlos Sanchez Resolution: Fixed > jsr107cache-1.0 release > --- > > Key: MAVENUPLOAD-1330 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1330 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Assigned To: Carlos Sanchez > Attachments: jsr107cache-1.0-bundle.jar > > > jsr107cache is a place for the evolving JCACHE API so that code can be > written to the spec before final release. > ehcache, another project available under this repository has a dependency on > jsr107cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1143) user with only 'project user' role can start a project-level build
[ http://jira.codehaus.org/browse/CONTINUUM-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-1143: --- Attachment: CONTINUUM-1143-continuum-webapp.patch Patch attached. > user with only 'project user' role can start a project-level build > -- > > Key: CONTINUUM-1143 > URL: http://jira.codehaus.org/browse/CONTINUUM-1143 > Project: Continuum > Issue Type: Bug > Components: Security >Affects Versions: 1.1 >Reporter: Wendy Smoak > Assigned To: Teodoro Cue Jr. >Priority: Critical > Attachments: CONTINUUM-1143-continuum-webapp.patch > > > The 'build now' icon for a project-level build is enabled for users without > the developer role. > See: > http://people.apache.org/~wsmoak/maven/continuum/continuum-project-user-role-can-build.jpg > Here, the guest user has been given the 'project user' role and should not be > able to start any builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEJB-23) Add classifier support
[ http://jira.codehaus.org/browse/MEJB-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEJB-23: Assignee: Stephane Nicoll Testcase included: yes Affects Version/s: (was: 2.1) Fix Version/s: 2.1 sounds good. > Add classifier support > -- > > Key: MEJB-23 > URL: http://jira.codehaus.org/browse/MEJB-23 > Project: Maven 2.x Ejb Plugin > Issue Type: New Feature >Affects Versions: 2.0 > Environment: n/a >Reporter: Stephen Coy > Assigned To: Stephane Nicoll > Fix For: 2.1 > > Attachments: ejb-classifier.patch > > > Both maven-war-plugin and maven-ear-plugin support the specification of a > classifier for the generated artifacts. The maven-ear-plugin even supports > specifying a classifier for component ejb-jars. > However this feature is missing from the maven-ejb-plugin. > The attached patch adds this feature. > I've found the classifier to be an essential element when creating builds > targeted at different deployment environments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEJB-16) clientExcludes generates empty packages i client-jar
[ http://jira.codehaus.org/browse/MEJB-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85959 ] Stephane Nicoll commented on MEJB-16: - Could you please let us know if it works now? > clientExcludes generates empty packages i client-jar > > > Key: MEJB-16 > URL: http://jira.codehaus.org/browse/MEJB-16 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Discovered on MAC OSX, but I dont think it is OS > dependent >Reporter: Anders Kr. Andersen > Assigned To: Stephane Nicoll >Priority: Minor > Fix For: 2.1 > > > When I use the ... the excluded packages are still package > in the jar. But empty. > The bigggest problem is probably the visual testing the developer is doing. > Seeing that packages remanis in the jar ... and discovering that they are > empty simple just takes a little time. > I don't think the JVM have any problem with this ? > But I don't think it is in the JAR specification either :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEJB-16) clientExcludes generates empty packages i client-jar
[ http://jira.codehaus.org/browse/MEJB-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEJB-16: Fix Version/s: 2.1 > clientExcludes generates empty packages i client-jar > > > Key: MEJB-16 > URL: http://jira.codehaus.org/browse/MEJB-16 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.0 > Environment: Discovered on MAC OSX, but I dont think it is OS > dependent >Reporter: Anders Kr. Andersen >Priority: Minor > Fix For: 2.1 > > > When I use the ... the excluded packages are still package > in the jar. But empty. > The bigggest problem is probably the visual testing the developer is doing. > Seeing that packages remanis in the jar ... and discovering that they are > empty simple just takes a little time. > I don't think the JVM have any problem with this ? > But I don't think it is in the JAR specification either :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEJB-22) Cannot specify additional classpath entries in ejb manifest when using addClasspath
[ http://jira.codehaus.org/browse/MEJB-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEJB-22. --- Assignee: Stephane Nicoll Resolution: Cannot Reproduce It works, at least w/ archiver 2.2 that is used by the current version of the plugin. > Cannot specify additional classpath entries in ejb manifest when using > addClasspath > --- > > Key: MEJB-22 > URL: http://jira.codehaus.org/browse/MEJB-22 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows Xp, JDK 1.4, maven 2.0.4 >Reporter: Wisniewski Eric > Assigned To: Stephane Nicoll > Fix For: 2.1 > > > The plugin configuration snippet below leads to the generation of an illegal > jar manifest file, as it contains two Class-Path entries. This works in Maven > 1.1b2 by adding the following to project.properties: > maven.jar.manifest.classpath.add=true > maven.jar.classpath=help/ resources/ > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > resources/ > > > > > And the generating manifest : > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: 1691694 > Build-Jdk: 1.4.2_06 > Extension-Name: cfp-ejb > Implementation-Title: cfp-ejb > Implementation-Version: 1.0-SNAPSHOT > Class-Path: junit-3.8.1.jar > Class-Path: resources/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEJB-22) Cannot specify additional classpath entries in ejb manifest when using addClasspath
[ http://jira.codehaus.org/browse/MEJB-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85957 ] Stephane Nicoll commented on MEJB-22: - It has certainly nothing to do with the EJB plugin per se. If it still an issue it's in the plexus archiver. > Cannot specify additional classpath entries in ejb manifest when using > addClasspath > --- > > Key: MEJB-22 > URL: http://jira.codehaus.org/browse/MEJB-22 > Project: Maven 2.x Ejb Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows Xp, JDK 1.4, maven 2.0.4 >Reporter: Wisniewski Eric > Fix For: 2.1 > > > The plugin configuration snippet below leads to the generation of an illegal > jar manifest file, as it contains two Class-Path entries. This works in Maven > 1.1b2 by adding the following to project.properties: > maven.jar.manifest.classpath.add=true > maven.jar.classpath=help/ resources/ > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > resources/ > > > > > And the generating manifest : > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: 1691694 > Build-Jdk: 1.4.2_06 > Extension-Name: cfp-ejb > Implementation-Title: cfp-ejb > Implementation-Version: 1.0-SNAPSHOT > Class-Path: junit-3.8.1.jar > Class-Path: resources/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-675) Add Working Copy to the Legends
[ http://jira.codehaus.org/browse/CONTINUUM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry S. Isidro updated CONTINUUM-675: -- Attachment: [CONTINUUM-675]-continuum-webapp.patch File Attached: [CONTINUUM-675]-continuum-webapp.patch This adds the 'working copy' icon to the legends list. > Add Working Copy to the Legends > --- > > Key: CONTINUUM-675 > URL: http://jira.codehaus.org/browse/CONTINUUM-675 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Shinobu Kawai >Priority: Trivial > Fix For: 1.1 > > Attachments: [CONTINUUM-675]-continuum-webapp.patch > > > Add "Working Copy" to the Legends on the left -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-994) New indexes created during continuum startup when using postgresql
[
http://jira.codehaus.org/browse/CONTINUUM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85955
]
Richard C. L. Li commented on CONTINUUM-994:
Continuum will generate an exception when using with postgresql and JPOX 1.1.6
upon browsing the web page at the first time, the problem is resides in plexus:
{panel}
http://jira.codehaus.org/browse/PLX-322
{panel}
> New indexes created during continuum startup when using postgresql
> --
>
> Key: CONTINUUM-994
> URL: http://jira.codehaus.org/browse/CONTINUUM-994
> Project: Continuum
> Issue Type: Bug
> Components: Database
>Affects Versions: 1.0.3
>Reporter: Richard C. L. Li
> Fix For: 1.1
>
>
> I used postgresql 8.1.4 with continuum and everytime when continuum startup,
> it creates a set of indexes. I configured to restart continuum once a day
> and after 2 months it generated tens of indexes in every table.
> I guessed this maybe the problem of the the UPPER CASE of the table and
> column names, this may make the detection of indexes fails and the JDO
> recreate everytime it startup.
> Workaround: after starting continuum for the first time and set the property
> org.jpox.autoCreateSchema to false so that indexes will not 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] Commented: (MAVENUPLOAD-1330) jsr107cache-1.0 release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85950 ] Greg Luck commented on MAVENUPLOAD-1330: Carlos Hi. Is there a problem with this. I really need it added. Greg > jsr107cache-1.0 release > --- > > Key: MAVENUPLOAD-1330 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1330 > Project: maven-upload-requests > Issue Type: Task >Reporter: Greg Luck > Attachments: jsr107cache-1.0-bundle.jar > > > jsr107cache is a place for the evolving JCACHE API so that code can be > written to the spec before final release. > ehcache, another project available under this repository has a dependency on > jsr107cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2792) When Maven runs Java 6, maven-metadata.xml file is "corrupted"
When Maven runs Java 6, maven-metadata.xml file is "corrupted" -- Key: MNG-2792 URL: http://jira.codehaus.org/browse/MNG-2792 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: Matthew Beermann Priority: Critical Attachments: maven-metadata.xml When you run Maven under Java 6, the "maven-metadata.xml" file that gets written to the remote repository is markedly different from the one generated under Java 5 and earlier. This file is "corrupted" in the sense that Maven reports errors about it, and might not be able to locate snapshots as a result. See attachment for an example file; you'd expect to see build numbers or -SNAPSHOTs, but not both at once. This issue is described further at http://www.nabble.com/Maven-and-JDK-1.6-t3060866s177.html (originally message only, not the followups). This might be related to MNG-2709, but I don't think it's a duplicate, as it has nothing to do with testing or parents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-94) doxia creates a name anchors with spaces which is not valid XHTML.
[ http://jira.codehaus.org/browse/DOXIA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85944 ] Henning Schmiedehausen commented on DOXIA-94: - HEAD, always HEAD. Doxia HEAD, Maven HEAD, Plexus HEAD. Looking at the number of open bugs, I don't think that any maven developer is interested in bug reports that is not against the current HEAD. > doxia creates a name anchors with spaces which is not valid XHTML. > -- > > Key: DOXIA-94 > URL: http://jira.codehaus.org/browse/DOXIA-94 > Project: doxia > Issue Type: Bug >Reporter: Henning Schmiedehausen > > consider the following section: > > > doxia renders this to be > section name > > According to the w3c XHTML validator, a name anchor must not contain any > spaces, it must be a single word. So this is not valid XHTML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-91) Update Doxia Decoration model to actually work in reactor build.
[ http://jira.codehaus.org/browse/DOXIA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85942 ] Henning Schmiedehausen commented on DOXIA-91: - Yep, same here. Maven 2.0.4 and 2.0.5-SNAPSHOT (do we have a release yet?). Which platform did you use? I ran my tests on Linux, I don't have a built HEAD on Windows and the process of getting the jumble of maven, plexus, doxia and everything else to get built took my fastest machines two hours. I don't want to think how long my old windows notebook would take for this... If you are on Windows, I will try to run the tests for you this weekend. Can you attach the failed test report? That would help me tremendously. > Update Doxia Decoration model to actually work in reactor build. > > > Key: DOXIA-91 > URL: http://jira.codehaus.org/browse/DOXIA-91 > Project: doxia > Issue Type: Improvement > Components: Decoration Model >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > Attachments: doxia-decoration.patch, doxia-decoration.patch > > > This is a major patch to the decoration model to bring some sanity in the > link resolution when it is used under the reactor build. It generates > breadcrumbs and item links correctly in all scenarios that I have tested (the > current HEAD code does not) and passes all the unit tests that are already > there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-94) doxia creates a name anchors with spaces which is not valid XHTML.
[ http://jira.codehaus.org/browse/DOXIA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85943 ] Wendy Smoak commented on DOXIA-94: -- Please include the versions you're using. This sounds similar to http://jira.codehaus.org/browse/MSITE-168 which is fixed (but possibly not yet released.) > doxia creates a name anchors with spaces which is not valid XHTML. > -- > > Key: DOXIA-94 > URL: http://jira.codehaus.org/browse/DOXIA-94 > Project: doxia > Issue Type: Bug >Reporter: Henning Schmiedehausen > > consider the following section: > > > doxia renders this to be > section name > > According to the w3c XHTML validator, a name anchor must not contain any > spaces, it must be a single word. So this is not valid XHTML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-79) Doxia generates different XHTML for the same xdoc code
[ http://jira.codehaus.org/browse/DOXIA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Schmiedehausen reopened DOXIA-79: - Nah. I don't believe you. I just fetched the Doxia HEAD, built it and the issue is not only still there but for the fun of it I've also opened DOXIA-93, DOXIA-94, DOXIA-95 and DOXIA-96 just to show you that this thing still has not just "a few bugs". > Doxia generates different XHTML for the same xdoc code > -- > > Key: DOXIA-79 > URL: http://jira.codehaus.org/browse/DOXIA-79 > Project: doxia > Issue Type: Bug > Components: Core >Affects Versions: 1.0-alpha-8, 1.0 >Reporter: Henning Schmiedehausen > Assigned To: Vincent Siveton > Fix For: 1.0 > > > Consider the following xdoc code: > > > p1 > > l1 > > > > p2 > > l1 > > > > This renders to the following XHTML code: > 1 > s1 > p1 > l1 > > s2 > p2 > l1 > > > Please not the missing around 'p2'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-96) Doxia xdoc chokes on macros and pushes to the output
Doxia xdoc chokes on macros and pushes to the output - Key: DOXIA-96 URL: http://jira.codehaus.org/browse/DOXIA-96 Project: doxia Issue Type: Bug Components: Core Affects Versions: 1.0-alpha-8, 1.0 Reporter: Henning Schmiedehausen Consider the following xdoc file: test1 The 'news' macro is the Doxia macro described on http://velocity.apache.org/site/tools/velocity-site-news-extension/index.html This results in the following content: section name [... Macro output omitted ...] Please note the additional that somehow got into the output. This is obviously no valid XHTML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-95) Doxia omits closing elements
Doxia omits closing elements - Key: DOXIA-95 URL: http://jira.codehaus.org/browse/DOXIA-95 Project: doxia Issue Type: Bug Reporter: Henning Schmiedehausen Consider the following xdoc file: test1 text list1 text2 list1 This renders to the following HTML output: section name text list1 text2 list1 Please note that there is no closing between and This is obviously no valid XHTML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-94) doxia creates a name anchors with spaces which is not valid XHTML.
doxia creates a name anchors with spaces which is not valid XHTML. -- Key: DOXIA-94 URL: http://jira.codehaus.org/browse/DOXIA-94 Project: doxia Issue Type: Bug Reporter: Henning Schmiedehausen consider the following section: doxia renders this to be section name According to the w3c XHTML validator, a name anchor must not contain any spaces, it must be a single word. So this is not valid XHTML. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (DOXIA-93) xdoc renderer chokes on multiple block elements in a section
xdoc renderer chokes on multiple block elements in a section Key: DOXIA-93 URL: http://jira.codehaus.org/browse/DOXIA-93 Project: doxia Issue Type: Bug Components: Core Affects Versions: 1.0-alpha-8, 1.0 Reporter: Henning Schmiedehausen Consider the following xdoc file: test1 text list1 text2 list1 text3 The current doxia HEAD renders this to: section name text list1 text2 list1 text3 Note the missing '' tags around text2 and text3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-493) aopalliance/aopalliance/1.0 license is wrong
aopalliance/aopalliance/1.0 license is wrong Key: MEV-493 URL: http://jira.codehaus.org/browse/MEV-493 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: Daniel Kulp The aopalliance code is public domain, not LGPL: http://aopalliance.sourceforge.net/ The license tag in the pom should be changed to reflect that so license validator tools can report the right 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] Created: (MCOMPILER-51) incorrectly evaluates ${project.build.directory} as current-dir relative
incorrectly evaluates ${project.build.directory} as
current-dir relative
--
Key: MCOMPILER-51
URL: http://jira.codehaus.org/browse/MCOMPILER-51
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Environment: Mac OS X 10.4.8, JDK 1.5.0_06
Reporter: Matt Bishop
Priority: Minor
This affects 2.0.4, I have not tested on other versions.
If a pom.xml's ${project.build.directory} is set to an absolute path and the
same pom.xml's project/build/outputDirectory references this property, the
compiler sends built classes to a path relative to the current dir. However,
if the outputDirectory property is hard-coded to the absolute path, then the
build classes are properly dropped in the absolute path. Example:
/Volumes/RamDisk/target
${project.build.directory}/classes
Incorrectly sends javac output to
/Users/matt/myProject/Volumes/RamDisk/target/classes
However:
/Volumes/RamDisk/target
${project.build.directory}/classes
Correctly sends javac output to /Volumes/RamDisk/target/classes
As a note, other users of an absolute ${project.build.directory} handle the
path correctly, such as the maven-war-plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-51) incorrectly evaluates ${project.build.directory} as current-dir relative
[
http://jira.codehaus.org/browse/MCOMPILER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85931
]
Matt Bishop commented on MCOMPILER-51:
--
I meant to say:
/Volumes/RamDisk/target/classes
Correctly sends...
> incorrectly evaluates ${project.build.directory} as
> current-dir relative
> --
>
> Key: MCOMPILER-51
> URL: http://jira.codehaus.org/browse/MCOMPILER-51
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Environment: Mac OS X 10.4.8, JDK 1.5.0_06
>Reporter: Matt Bishop
>Priority: Minor
>
> This affects 2.0.4, I have not tested on other versions.
> If a pom.xml's ${project.build.directory} is set to an absolute path and the
> same pom.xml's project/build/outputDirectory references this property, the
> compiler sends built classes to a path relative to the current dir. However,
> if the outputDirectory property is hard-coded to the absolute path, then the
> build classes are properly dropped in the absolute path. Example:
>
> /Volumes/RamDisk/target
> ${project.build.directory}/classes
> Incorrectly sends javac output to
> /Users/matt/myProject/Volumes/RamDisk/target/classes
> However:
>
> /Volumes/RamDisk/target
> ${project.build.directory}/classes
> Correctly sends javac output to /Volumes/RamDisk/target/classes
> As a note, other users of an absolute ${project.build.directory} handle the
> path correctly, such as the maven-war-plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-180) Ability to add additions to classpath
[ http://jira.codehaus.org/browse/SUREFIRE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85929 ] John T. Kwon commented on SUREFIRE-180: --- Please, if someone will let me upload the changes to make this happen, I've already implemented them on my local build, and it works great. Let me know how I can become a contributor. > Ability to add additions to classpath > - > > Key: SUREFIRE-180 > URL: http://jira.codehaus.org/browse/SUREFIRE-180 > Project: Maven Surefire > Issue Type: Improvement > Environment: N/A >Reporter: David J. M. Karlsen > Assigned To: fabrizio giustina > Attachments: MSUREFIRE-153-maven-surefire-plugin.patch, > SurefirePlugin.java-diff > > > There should be a possibility to add arbritary resources to the classpath > while executing the tests. These resources would only be available while > executing the tests, so they won't be added in the archive. > i suggest a configuration element > > some/path > /some/other/path > > This issue somewhat related to http://jira.codehaus.org/browse/MJAR-13 / > ability to exclude/include filtering in archiver/jar-plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1141) Add buttons to add Ant/Shell projects in projectGroupSummary
[ http://jira.codehaus.org/browse/CONTINUUM-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85928 ] Natalie Burdick commented on CONTINUUM-1141: I like the last option for organization and workflow, fewer things to click as a user...but, is there a plan to use this convention consistently where there are multiple choices like this? > Add buttons to add Ant/Shell projects in projectGroupSummary > > > Key: CONTINUUM-1141 > URL: http://jira.codehaus.org/browse/CONTINUUM-1141 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan > Fix For: 1.1 > > Attachments: CONTINUUM-1141-projectGroupSummary.GIF, > CONTINUUM-1141-projectGroupSummary.GIF, projectGroupSummary.GIF > > > Currently only allows add m1 and m2 projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2553) Maven Local Settings Model should allow configuration of distributions (distributionManagement)
[ http://jira.codehaus.org/browse/MNG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85902 ] Marcos Silva Pereira commented on MNG-2553: --- We also have the same problem here. Solve this problem will be so useful. > Maven Local Settings Model should allow configuration of distributions > (distributionManagement) > --- > > Key: MNG-2553 > URL: http://jira.codehaus.org/browse/MNG-2553 > Project: Maven 2 > Issue Type: Improvement > Components: Settings >Affects Versions: 2.0.4 >Reporter: Jimisola Laursen > > There is a good use case where this would be very useful. > E.g. I develop a plugin in mojo-sandbox and want to test it in an environment > other than the one that I developed it on (e.g. a computer at work). I check > out the plugin to this, build and then want to deploy to another repository > (e..g a company's internal repository). I don't want to fiddle with the > pom.xml of the plugin, just refer to a profile in settings.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: (MSITE-208) ... Link Not Generating
[ http://jira.codehaus.org/browse/MSITE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85890 ] Subhash Chandran commented on MSITE-208: I get the following output: Group Id: org.apache.maven.plugins Artifact Id: maven-site-plugin Version: 2.0-beta-5 Goal Prefix: site > ... Link Not Generating > - > > Key: MSITE-208 > URL: http://jira.codehaus.org/browse/MSITE-208 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Environment: Linux 2.6, Maven2.0.4, Java 6.0 >Reporter: Subhash Chandran > > I have the following in my src/site/site.xml: > > WizCrypt > img/logo.png > http://wizcrypt.wiztools.org/ > > For the banner, the link http://wizcrypt.wiztools.org/ is not getting > generated. The generated output: > http://wizcrypt.wiztools.org/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2791) Error parsing Maven 1 POM file with an extend tag
Error parsing Maven 1 POM file with an extend tag - Key: MNG-2791 URL: http://jira.codehaus.org/browse/MNG-2791 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.1.x Environment: Maven 2 Eclipse plugin 0.0.10 (latest from SVN) using the following jars: lucene-core-2.0.0.jar maven-embedder-2.1.0.v20070110-2115-dep.jar Eclipse 3.2 Session Data: eclipse.buildId=M20060921-0945 java.version=1.6.0 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_ES Command-line arguments: -os win32 -ws win32 -arch x86 -data c:\workspace -clean Reporter: Rodrigo Ruiz Trying to rebuild a project that depends on an artifact obtained from a Maven1 repository, I get the following stacktrace: org.eclipse.core.runtime.CoreException: Parsing error [whatever].pom; org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognised tag: 'extend' (position: START_TAG seen ...\n ... @4:11) at org.maven.ide.eclipse.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:137) at org.maven.ide.eclipse.embedder.ClassPathResolver.getJavaDocUrl(ClassPathResolver.java:241) at org.maven.ide.eclipse.embedder.ClassPathResolver.resolveClasspathEntries(ClassPathResolver.java:154) at org.maven.ide.eclipse.builder.Maven2Builder.updateClasspath(Maven2Builder.java:95) at org.maven.ide.eclipse.builder.Maven2Builder.build(Maven2Builder.java:86) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:603) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:167) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:230) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:233) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:252) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:285) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:145) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:208) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) org.eclipse.core.runtime.CoreException[4]: org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognised tag: 'extend' (position: START_TAG seen ...\n ... @4:11) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2405) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4438) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4449) at org.apache.maven.embedder.MavenEmbedder.readModel(MavenEmbedder.java:208) at org.maven.ide.eclipse.embedder.MavenModelManager.readMavenModel(MavenModelManager.java:133) at org.maven.ide.eclipse.embedder.ClassPathResolver.getJavaDocUrl(ClassPathResolver.java:241) at org.maven.ide.eclipse.embedder.ClassPathResolver.resolveClasspathEntries(ClassPathResolver.java:154) at org.maven.ide.eclipse.builder.Maven2Builder.updateClasspath(Maven2Builder.java:95) at org.maven.ide.eclipse.builder.Maven2Builder.build(Maven2Builder.java:86) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:603) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:167) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:230) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:233) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:252) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:285) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:145) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:208) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-180) Rewritten poms loose comments
[ http://jira.codehaus.org/browse/MRELEASE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85869 ] Julien HENRY commented on MRELEASE-180: --- I can confirm this bug. > Rewritten poms loose comments > -- > > Key: MRELEASE-180 > URL: http://jira.codehaus.org/browse/MRELEASE-180 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Guillaume Nodet > > When releasing ServiceMix, the following file was used before running the > release plugin: > > http://svn.apache.org/viewvc/incubator/servicemix/branches/servicemix-3.0/pom.xml?revision=470027&view=markup > But when actually releasing, the modified pom has lost the comments: > > http://svn.apache.org/viewvc/incubator/servicemix/branches/servicemix-3.0/pom.xml?revision=470031&view=markup > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPARTIFACT-74) artifact-install fails when maven-xdoc-plugin 1.10 is installed
[ http://jira.codehaus.org/browse/MPARTIFACT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85868 ] Lukas Theussl commented on MPARTIFACT-74: - AFAIK, xdoc-plugin-10 should be compatible with maven-1.0.2. However, I don't see how the xdoc plugin can make the jar:install goal fail. Can you attach a full copy of the error log, and your exact system setup (maven -i)? Also try to clear your cache, m1.0 had some cache problems when upgrading certain plugins. > artifact-install fails when maven-xdoc-plugin 1.10 is installed > --- > > Key: MPARTIFACT-74 > URL: http://jira.codehaus.org/browse/MPARTIFACT-74 > Project: maven-artifact-plugin > Issue Type: Bug >Affects Versions: 1.5.2 > Environment: Linux, jdk 1.5, maven 1.0.2 >Reporter: Philippe Sevestre >Priority: Minor > > After upgrading maven-xdoc-plugin from 1.9 to 1.10, jar:install goals fail > with the following message: > /home/phil/.maven/cache/maven-artifact-plugin-1.5.2/plugin.jelly:62:9: > Error getting the project as a string > Going back to maven-xdoc-plugin 1.9 solves this problem... > Not sure if this belongs to here or xdoc, but I think it worths reporting. > Running with debug messages enabled shows another nested exception > complaining about a unknown "artifactDirectory" tag somewhere. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2790) lastUpdated timestamp in local repository metadata not updated on install if it already exists
[ http://jira.codehaus.org/browse/MNG-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2790. - Assignee: Brett Porter Resolution: Fixed Fix Version/s: 2.0.6 > lastUpdated timestamp in local repository metadata not updated on install if > it already exists > -- > > Key: MNG-2790 > URL: http://jira.codehaus.org/browse/MNG-2790 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.5 >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 2.0.6 > > > while this was always the case, it went unnoticed because the file timestamp > was relied upon instead of the metadata timestamp (Which is now used in > consideration, and is causing snapshots to be used from the remote repository > even if it has been built locally) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2790) lastUpdated timestamp in local repository metadata not updated on install if it already exists
lastUpdated timestamp in local repository metadata not updated on install if it already exists -- Key: MNG-2790 URL: http://jira.codehaus.org/browse/MNG-2790 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Brett Porter while this was always the case, it went unnoticed because the file timestamp was relied upon instead of the metadata timestamp (Which is now used in consideration, and is causing snapshots to be used from the remote repository even if it has been built locally) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-1146) When a release fails, remove the "pending" status on phases that were not executed
[ http://jira.codehaus.org/browse/CONTINUUM-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edwin Punzalan closed CONTINUUM-1146. - Resolution: Fixed Fix Version/s: 1.1 > When a release fails, remove the "pending" status on phases that were not > executed > -- > > Key: CONTINUUM-1146 > URL: http://jira.codehaus.org/browse/CONTINUUM-1146 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Affects Versions: 1.0.3 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan >Priority: Minor > Fix For: 1.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1146) When a release fails, remove the "pending" status on phases that were not executed
When a release fails, remove the "pending" status on phases that were not executed -- Key: CONTINUUM-1146 URL: http://jira.codehaus.org/browse/CONTINUUM-1146 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.0.3 Reporter: Edwin Punzalan Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MANTRUN-65) Add a configuration element that allows you to skip plugin's execution
Add a configuration element that allows you to skip plugin's execution
-
Key: MANTRUN-65
URL: http://jira.codehaus.org/browse/MANTRUN-65
Project: Maven 2.x Antrun Plugin
Issue Type: New Feature
Affects Versions: 1.1
Reporter: Matt Raible
The DbUnit, Hibernate3 and SQL Maven 2 Plugins have a "skip" configuration
element that can be set to true in order to skip execution. This is a nice
feature because it allows you pass in -Dmaven.test.skip=true and skip execution
by adding the following in your pom.xml.
...
${maven.test.skip}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-1320) Javassist 3.1 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85866 ] Hugo Palma commented on MAVENUPLOAD-1320: - I've put together a bundle with groupId jboss here http://tapidea.javaforge.com/jboss/javassist-3.1-bundle.jar in case it is indeed the correct group. > Javassist 3.1 upload request > > > Key: MAVENUPLOAD-1320 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1320 > Project: maven-upload-requests > Issue Type: Task >Reporter: Hugo Palma > > Simple Java bytecode manipulation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (CONTINUUM-1141) Add buttons to add Ant/Shell projects in projectGroupSummary
[ http://jira.codehaus.org/browse/CONTINUUM-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CONTINUUM-1141 stopped by Edwin Punzalan. > Add buttons to add Ant/Shell projects in projectGroupSummary > > > Key: CONTINUUM-1141 > URL: http://jira.codehaus.org/browse/CONTINUUM-1141 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan > Fix For: 1.1 > > Attachments: CONTINUUM-1141-projectGroupSummary.GIF, > CONTINUUM-1141-projectGroupSummary.GIF, projectGroupSummary.GIF > > > Currently only allows add m1 and m2 projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1141) Add buttons to add Ant/Shell projects in projectGroupSummary
[ http://jira.codehaus.org/browse/CONTINUUM-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edwin Punzalan updated CONTINUUM-1141: -- Attachment: CONTINUUM-1141-projectGroupSummary.GIF > Add buttons to add Ant/Shell projects in projectGroupSummary > > > Key: CONTINUUM-1141 > URL: http://jira.codehaus.org/browse/CONTINUUM-1141 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan > Fix For: 1.1 > > Attachments: CONTINUUM-1141-projectGroupSummary.GIF, > CONTINUUM-1141-projectGroupSummary.GIF, projectGroupSummary.GIF > > > Currently only allows add m1 and m2 projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1141) Add buttons to add Ant/Shell projects in projectGroupSummary
[ http://jira.codehaus.org/browse/CONTINUUM-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edwin Punzalan updated CONTINUUM-1141: -- Attachment: CONTINUUM-1141-projectGroupSummary.GIF Attached another screenshot > Add buttons to add Ant/Shell projects in projectGroupSummary > > > Key: CONTINUUM-1141 > URL: http://jira.codehaus.org/browse/CONTINUUM-1141 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Affects Versions: 1.1 >Reporter: Edwin Punzalan > Assigned To: Edwin Punzalan > Fix For: 1.1 > > Attachments: CONTINUUM-1141-projectGroupSummary.GIF, > projectGroupSummary.GIF > > > Currently only allows add m1 and m2 projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-2206) bad properties interpolation with profiles
[
http://jira.codehaus.org/browse/MNG-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85859
]
Geoffrey De Smet commented on MNG-2206:
---
Is my problem of "cmd line property does not override others" is probably the
same issue:
[based on m2.0.5's first rc on the dev list]
I have this profile in my pom.xml:
development
true
true
${no.daisy.test}
So without my settings.xml "mvn install" doesn't run the tests.
But in my settings.xml I have a profile like this:
daisy_1_5
false
...
So now "mvn install" does run the tests.
However when I now try
mvn -Dmaven.test.skip install
The tests are still run,
while I expected my cmd line variable to overwrite my pom.xml and setting.xml
properties.
> bad properties interpolation with profiles
> ---
>
> Key: MNG-2206
> URL: http://jira.codehaus.org/browse/MNG-2206
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.3
> Environment: cygwin
>Reporter: Olivier Lamy
> Assigned To: Edwin Punzalan
>Priority: Blocker
> Fix For: 2.0.x
>
> Attachments: MNG-2206-maven-project.patch, pom.xml
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> create two profiles in your settings.xml
> - id test with a property dev
> - id snapshots with a property snapshots
>
> dev
> snapshots
>
> With the attached pom run :
> mvn validate :
> [echo] dev
> mvn -P snapshots validate :
> [echo] dev
> Olivier
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-193) Release should update from scm and must be able to build it before proceeding with release:prepare
Release should update from scm and must be able to build it before proceeding with release:prepare -- Key: MRELEASE-193 URL: http://jira.codehaus.org/browse/MRELEASE-193 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-4 Reporter: Edwin Punzalan Currently, only checks for local modifications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
