[jira] Commented: (MNG-2578) Make it possible to set default versions for reporting-plugins (i.e. plugins under )
[ http://jira.codehaus.org/browse/MNG-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92945 ] Heinrich Nirschl commented on MNG-2578: --- Seems to be the same as MNG-1931 > Make it possible to set default versions for reporting-plugins (i.e. plugins > under ) > > > Key: MNG-2578 > URL: http://jira.codehaus.org/browse/MNG-2578 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0.4 >Reporter: Jimisola Laursen > > Make it possible to set default versions for reporting-plugins (i.e. plugins > under ). > dependencies have dependencyManagement and plugins have pluginManagement, but > there doesn't seem to be anything for reportPluginManagement. > Could be that I missed out on something, but I doubt it since I stumbled on > this issue with aspectj-maven-plugin and it's aspectj-report (similar to > javadoc). > The same plugin is used under build and reporting. pluginManagement stated > that version 1.0-beta-4-SNAPSHOT should be used, but it was only for build. > Instead 1.0-beta-2 (not snapshot) was used for the report. > This issue came up in the following thread in mojo-user: > http://www.nabble.com/Problems-with-aspectj-maven-plugin-and-reporting-using-ajdoc-tf2060246.html#a6507979 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-257) Dependency not on eclipse class path
Dependency not on eclipse class path Key: MECLIPSE-257 URL: http://jira.codehaus.org/browse/MECLIPSE-257 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Environment: Linux Reporter: Goran Oberg When I exclude a transitive dependency and add it separately with another scope, the dependency doesn't add to the eclipse class path. Example: jboss.seam jboss-seam 1.2.1.GA org.hibernate hibernate-annotations org.hibernate hibernate-annotations 3.2.0.ga provided Maven compile the code and include dependencies as expected in the war, but eclipse is highligthing hibernate-annotations as missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MECLIPSE-257) Dependency not on eclipse class path
[ http://jira.codehaus.org/browse/MECLIPSE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92947 ] Goran Oberg commented on MECLIPSE-257: -- At the moment I add the dependency in a parent pom as a workaround > Dependency not on eclipse class path > > > Key: MECLIPSE-257 > URL: http://jira.codehaus.org/browse/MECLIPSE-257 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: Linux >Reporter: Goran Oberg > > When I exclude a transitive dependency and add it separately with another > scope, the dependency doesn't add to the eclipse class path. > Example: > > jboss.seam > jboss-seam > 1.2.1.GA > > > org.hibernate > hibernate-annotations > > > > > org.hibernate > hibernate-annotations > 3.2.0.ga > provided > > Maven compile the code and include dependencies as expected in the war, but > eclipse is highligthing hibernate-annotations as missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-197) 2.2-beta-1 regression, project artifact no longer included in
2.2-beta-1 regression, project artifact no longer included in - Key: MASSEMBLY-197 URL: http://jira.codehaus.org/browse/MASSEMBLY-197 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Reporter: Max Bowsher Priority: Blocker In 2.1, included the project artifact itself - i.e., all the jars actually needed to execute the project. In 2.2-beta-1, is omitting the project artifact, so that assemblies that functioned correctly when built with 2.1, fail to execute when built with 2.2-beta-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: (MAVENUPLOAD-1485) Upload EasyMock-PropertyUtils-1.1
Upload EasyMock-PropertyUtils-1.1 - Key: MAVENUPLOAD-1485 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1485 Project: maven-upload-requests Issue Type: Task Reporter: Stephen Duncan Jr Code hosted site: http://code.google.com/p/jrduncans/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MANTLR-17) Support for Antlr 3
[ http://jira.codehaus.org/browse/MANTLR-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92951 ] David Holroyd commented on MANTLR-17: - I've written a plugin for v3, http://maven.badgers-in-foil.co.uk/sites/maven-antlr3-plugin/ I'd be happy to contribute this code. > Support for Antlr 3 > --- > > Key: MANTLR-17 > URL: http://jira.codehaus.org/browse/MANTLR-17 > Project: Maven 2.x Antlr Plugin > Issue Type: Wish >Reporter: Brian Hanafee > > Antlr 3.0 is a major rewrite of ANTLR. It's not clear whether the right > approach would be to upgrade this plug-in or to write a new plug-in. > There is a (partial) [workaround using the antrun > plugin|http://www.antlr.org/wiki/display/ANTLR3/Using+ANTLR+3+with+Maven+2]. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCLOVER-60) Create architecture documentation
[ http://jira.codehaus.org/browse/MCLOVER-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Massol updated MCLOVER-60: -- Fix Version/s: (was: 2.4) > Create architecture documentation > - > > Key: MCLOVER-60 > URL: http://jira.codehaus.org/browse/MCLOVER-60 > Project: Maven 2.x Clover Plugin > Issue Type: Task >Affects Versions: 2.3 >Reporter: Vincent Massol >Assignee: Vincent Massol > > There used to be architecture but it's been removed when the plugin's > architecture was modified. Update it and show it again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPA-9) Create top-level Maven site
[ http://jira.codehaus.org/browse/MPA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-9: -- Fix Version/s: (was: 2006-q4) > Create top-level Maven site > --- > > Key: MPA-9 > URL: http://jira.codehaus.org/browse/MPA-9 > Project: Maven Project Administration > Issue Type: Task > Components: sites >Affects Versions: 2006-q3 >Reporter: Jason van Zyl >Assignee: Brett Porter > > Create top-level Maven site using db.apache.org as a template. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-43) rename m1 plugins in JIRA
[ http://jira.codehaus.org/browse/MPA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-43: --- Fix Version/s: (was: 2006-q4) > rename m1 plugins in JIRA > - > > Key: MPA-43 > URL: http://jira.codehaus.org/browse/MPA-43 > Project: Maven Project Administration > Issue Type: Improvement > Components: Issue Management >Affects Versions: 2006-q3 >Reporter: Brett Porter > > can we bulk change the name of the JIRA projects for the maven 1 plugins to > be Maven 1.x XXX like the Maven 2 equivalents to reduce confusion? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-46) Remove or change m1 plugins leaders
[ http://jira.codehaus.org/browse/MPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-46: --- Fix Version/s: (was: 2006-q4) > Remove or change m1 plugins leaders > --- > > Key: MPA-46 > URL: http://jira.codehaus.org/browse/MPA-46 > Project: Maven Project Administration > Issue Type: Task > Components: Issue Management >Reporter: Arnaud Heritier >Priority: Minor > > The list of leaders for m1 plugins is no more revelant. > Users can suppose that there are a lot of guys working on them whereas we are > only 3 (actually). > I think it's not possible to not have a leader for a project but perhaps we > could create a generic account for the maven team. > WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-51) Create a New JIRA Project for Maven Site
[ http://jira.codehaus.org/browse/MPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-51: --- Fix Version/s: (was: 2006-q4) > Create a New JIRA Project for Maven Site > > > Key: MPA-51 > URL: http://jira.codehaus.org/browse/MPA-51 > Project: Maven Project Administration > Issue Type: Task >Reporter: Carlos Sanchez > > The Maven site itself needs a new JIRA project to capture problems, needs, > and tasks related to Maven site improvment. > Hmmm, group_id, artifact_id and version. Left 'em blank. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPA-31) have ibiblio convert .htaccess rules to httpd.conf
[ http://jira.codehaus.org/browse/MPA-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-31: --- Fix Version/s: (was: 2006-q4) > have ibiblio convert .htaccess rules to httpd.conf > -- > > Key: MPA-31 > URL: http://jira.codehaus.org/browse/MPA-31 > Project: Maven Project Administration > Issue Type: Sub-task > Components: repository management >Affects Versions: 2006-q3 >Reporter: Brett Porter > > after a sufficient period of testing, ibiblio has requested that the rules be > moved to httpd.conf as its performance will be better than in .htaccess -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-72) Please make "sources" jar available to Maven1 users
[ http://jira.codehaus.org/browse/MPA-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-72: --- Fix Version/s: (was: 2006-q4) > Please make "sources" jar available to Maven1 users > --- > > Key: MPA-72 > URL: http://jira.codehaus.org/browse/MPA-72 > Project: Maven Project Administration > Issue Type: Bug > Components: repository management >Reporter: Emmanuel Venisse >Assignee: Brett Porter > > Hello guys, > From a previous post I know Maven1 repo is a redirect to maven2 repository > content, with path transcripted to match maven2 hierarchy. > commons-collection (as an example) has sources jar in maven2 repo > (http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1-sources.jar), > but I cannot get them using maven1 from > http://www.ibiblio.org/maven/commons-collections/java-sources/commons-collections-3.1-sources.jar > Maybe a new Apache rewrite rule may be required for this. > I would also be very interested if someone can give me the rewrite rule used > on ibiblio to convert m1 dependency path to m2 repo hierarchy. > Nicolas De Loof -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-78) add license text to confluence wikis
[ http://jira.codehaus.org/browse/MPA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-78: --- Fix Version/s: (was: 2006-q4) > add license text to confluence wikis > > > Key: MPA-78 > URL: http://jira.codehaus.org/browse/MPA-78 > Project: Maven Project Administration > Issue Type: Task > Components: sites >Reporter: Brett Porter > > we should add a notice to the wiki (perhaps in the footer?) that indicates to > users and contributors what the license for submitted content is (presumably, > ASL) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-32) make suitable arrangements with other maven mirrors
[ http://jira.codehaus.org/browse/MPA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-32: --- Fix Version/s: (was: 2006-q4) > make suitable arrangements with other maven mirrors > --- > > Key: MPA-32 > URL: http://jira.codehaus.org/browse/MPA-32 > Project: Maven Project Administration > Issue Type: Sub-task > Components: repository management >Affects Versions: 2006-q3 >Reporter: Brett Porter > > once we turn off the additional syncing of maven1 content, then the other > mirrors will not get updated. We should see if they can map the content using > mod_rewrite as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-29) Create mod_rewrite rules to divert m1 repository requests to the m2 repository
[ http://jira.codehaus.org/browse/MPA-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-29: --- Fix Version/s: (was: 2006-q4) > Create mod_rewrite rules to divert m1 repository requests to the m2 repository > -- > > Key: MPA-29 > URL: http://jira.codehaus.org/browse/MPA-29 > Project: Maven Project Administration > Issue Type: Task > Components: repository management >Affects Versions: 2006-q3 >Reporter: Jason van Zyl >Assignee: Brett Porter > > It is possible for us not to have to convert the repositories by turning an > m1 repository request into an m2 style request and direct it at the m2 > repository. This would allow us to maintain the one canonical repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-57) migrate all Maven projects to the Basic Issue Creation Scheme in JIRA
[ http://jira.codehaus.org/browse/MPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-57: --- Fix Version/s: (was: 2006-q4) > migrate all Maven projects to the Basic Issue Creation Scheme in JIRA > - > > Key: MPA-57 > URL: http://jira.codehaus.org/browse/MPA-57 > Project: Maven Project Administration > Issue Type: Task > Components: Issue Management >Affects Versions: 2006-q3 >Reporter: Brett Porter > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-80) Open a staging sites area at http://maven.zones.apache.org/staging/
[ http://jira.codehaus.org/browse/MPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-80: --- Fix Version/s: (was: 2006-q4) > Open a staging sites area at http://maven.zones.apache.org/staging/ > --- > > Key: MPA-80 > URL: http://jira.codehaus.org/browse/MPA-80 > Project: Maven Project Administration > Issue Type: Task > Components: sites >Affects Versions: 2006-q3 >Reporter: Arnaud Heritier >Assignee: Jason van Zyl >Priority: Minor > > As discussed here [1] it could be interesting for us to have a common staging > area to deploy our documentations (instead of using our accounts on > people.apache.org). > Brett proposed to use the zone for that : > http://maven.zones.apache.org/staging/ (maven 2) > http://maven.zones.apache.org/staging/maven-1.x/ (maven 1 ie, following live > site structure). > I think that all committers must have the rights to deploy the web sites here. > [1] > http://www.nabble.com/CI-for-M1-%3A-Can-I-use-a-continuum-instance-somewhere---tf2051570.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: (MPA-87) Create a Jira Project for Modello plugin for maven 1.X
[ http://jira.codehaus.org/browse/MPA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-87: --- Affects Version/s: (was: 2007-q1) 2007-q2 > Create a Jira Project for Modello plugin for maven 1.X > -- > > Key: MPA-87 > URL: http://jira.codehaus.org/browse/MPA-87 > Project: Maven Project Administration > Issue Type: Task > Components: Issue Management >Affects Versions: 2007-q2 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > > Project: maven-modello-plugin > Key: MPMODELLO > URL: http://maven.apache.org/maven-1.x/plugins/modello/ > Project Lead: Arnaud Heritier > Notification Scheme: Maven > Permission Scheme: maven > Project Category: Maven 1 Plugins -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPA-33) turn off maven1 sync/uploads
[ http://jira.codehaus.org/browse/MPA-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MPA-33: --- Fix Version/s: (was: 2006-q4) > turn off maven1 sync/uploads > > > Key: MPA-33 > URL: http://jira.codehaus.org/browse/MPA-33 > Project: Maven Project Administration > Issue Type: Sub-task > Components: repository management >Affects Versions: 2006-q3 >Reporter: Brett Porter > > we need to stop uploading new artifacts to the maven1 repo, and stop syncing > outwards to ibiblio (we still need to sync in from other sources, however, > but this will soon be taken care of by the repo 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] Closed: (MPA-87) Create a Jira Project for Modello plugin for maven 1.X
[ http://jira.codehaus.org/browse/MPA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MPA-87. -- Resolution: Fixed Fix Version/s: 2007-q2 Done > Create a Jira Project for Modello plugin for maven 1.X > -- > > Key: MPA-87 > URL: http://jira.codehaus.org/browse/MPA-87 > Project: Maven Project Administration > Issue Type: Task > Components: Issue Management >Affects Versions: 2007-q2 >Reporter: Arnaud Heritier >Assignee: Arnaud Heritier > Fix For: 2007-q2 > > > Project: maven-modello-plugin > Key: MPMODELLO > URL: http://maven.apache.org/maven-1.x/plugins/modello/ > Project Lead: Arnaud Heritier > Notification Scheme: Maven > Permission Scheme: maven > Project Category: Maven 1 Plugins -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1242) Update Continuum Model
Update Continuum Model
--
Key: CONTINUUM-1242
URL: http://jira.codehaus.org/browse/CONTINUUM-1242
Project: Continuum
Issue Type: Task
Affects Versions: 1.1-alpha-1
Reporter: Iouri Goussev
Priority: Minor
When building Continuum jpox complaints about the use of deprecated attributes.
[INFO]
[INFO] Building Continuum Model
[INFO]task-segment: [test]
[INFO]
[INFO] [modello:java {execution: modello-continuum}]
[INFO] outputDirectory:
/export/home/elendal/continuum/continuum-model/target/classes/META-INF
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[INFO] Generating current version: 1.1.0
[INFO] [modello:jpox-metadata-class {execution: modello-continuum}]
[INFO] outputDirectory:
/export/home/elendal/continuum/continuum-model/target/classes/META-INF
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[INFO] Generating current version: 1.1.0
[INFO] [modello:stax-reader {execution: modello-continuum}]
[INFO] outputDirectory:
/export/home/elendal/continuum/continuum-model/target/classes/META-INF
[WARNING] You are using the attribute syntax.
It has been deprecated in favor of the syntax
instead.
[WARNING] You are using the attribute syntax. It has
been deprecated in favor of the syntax instead.
[WARNING] You a
[jira] Reopened: (MAVEN-1829) Upgrade maven-site-plugin to v 1.7.1
[ http://jira.codehaus.org/browse/MAVEN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier reopened MAVEN-1829: Release 1.7.2 to fix some problems with rsync feature > Upgrade maven-site-plugin to v 1.7.1 > > > Key: MAVEN-1829 > URL: http://jira.codehaus.org/browse/MAVEN-1829 > Project: Maven 1.x > Issue Type: Sub-task >Affects Versions: 1.1-beta-3 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.1-rc1 > > > http://jira.codehaus.org/browse/MPSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1242) Update Continuum Model
[
http://jira.codehaus.org/browse/CONTINUUM-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iouri Goussev updated CONTINUUM-1242:
-
Attachment: continuum-model.diff
Patch to remove warning messages.
> Update Continuum Model
> --
>
> Key: CONTINUUM-1242
> URL: http://jira.codehaus.org/browse/CONTINUUM-1242
> Project: Continuum
> Issue Type: Task
>Affects Versions: 1.1-alpha-1
>Reporter: Iouri Goussev
>Priority: Minor
> Attachments: continuum-model.diff
>
>
> When building Continuum jpox complaints about the use of deprecated
> attributes.
> [INFO]
>
> [INFO] Building Continuum Model
> [INFO]task-segment: [test]
> [INFO]
>
> [INFO] [modello:java {execution: modello-continuum}]
> [INFO] outputDirectory:
> /export/home/elendal/continuum/continuum-model/target/classes/META-INF
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [INFO] Generating current version: 1.1.0
> [INFO] [modello:jpox-metadata-class {execution: modello-continuum}]
> [INFO] outputDirectory:
> /export/home/elendal/continuum/continuum-model/target/classes/META-INF
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax. It
> has been deprecated in favor of the syntax instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the syntax
> instead.
> [WARNING] You are using the attribute syntax.
> It has been deprecated in favor of the
[jira] Updated: (MAVEN-1829) Upgrade maven-site-plugin to v 1.7.2
[ http://jira.codehaus.org/browse/MAVEN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MAVEN-1829: --- Summary: Upgrade maven-site-plugin to v 1.7.2 (was: Upgrade maven-site-plugin to v 1.7.1) > Upgrade maven-site-plugin to v 1.7.2 > > > Key: MAVEN-1829 > URL: http://jira.codehaus.org/browse/MAVEN-1829 > Project: Maven 1.x > Issue Type: Sub-task >Affects Versions: 1.1-beta-3 >Reporter: Lukas Theussl >Assignee: Arnaud Heritier > Fix For: 1.1-rc1 > > > http://jira.codehaus.org/browse/MPSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MAVEN-1841) Upgrade maven-announcement-plugin to v 1.4.1
Upgrade maven-announcement-plugin to v 1.4.1 Key: MAVEN-1841 URL: http://jira.codehaus.org/browse/MAVEN-1841 Project: Maven 1.x Issue Type: Sub-task Reporter: Arnaud Heritier Assignee: Arnaud Heritier -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MAVEN-1842) Upgrade maven-developer-activity-plugin to v 1.6.1
Upgrade maven-developer-activity-plugin to v 1.6.1 -- Key: MAVEN-1842 URL: http://jira.codehaus.org/browse/MAVEN-1842 Project: Maven 1.x Issue Type: Sub-task Reporter: Arnaud Heritier Assignee: Arnaud Heritier -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MAVEN-1843) Upgrade maven-file-activity-plugin to v 1.6.1
Upgrade maven-file-activity-plugin to v 1.6.1 - Key: MAVEN-1843 URL: http://jira.codehaus.org/browse/MAVEN-1843 Project: Maven 1.x Issue Type: Sub-task Reporter: Arnaud Heritier -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-1243) wording to explain no-build case
wording to explain no-build case Key: CONTINUUM-1243 URL: http://jira.codehaus.org/browse/CONTINUUM-1243 Project: Continuum Issue Type: Improvement Affects Versions: 1.0 Environment: windows XP java 1.5 Reporter: Larry Hamel Priority: Trivial If there are no files changed in source, the message in the Continuum log is: - The project was not built because all changes are unknown. This is confusing wording. Can you change that to something like: - - The project was not built because no changes were detected in source since the last build. thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-193) NullPointer in local provider update when a new file is added
[
http://jira.codehaus.org/browse/SCM-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92981
]
Marius Barbulescu commented on SCM-193:
---
I saw in AbstractUpdateCommand this code:
ChangeSet change = (ChangeSet) i.next();
if ( startDate != null && change.getDate() != null )
{
if ( startDate.after( change.getDate() ) )
the NPE comes from here:
static final long getMillisOf(Date date) {
if (date.cdate == null) {
means that change.getDate() returns null.
I would update the code like this:
ChangeSet change = (ChangeSet) i.next();
Date changeDate = change.getDate();
if ( startDate != null && changeDate != null )
{
if ( startDate.after( changeDate ) )
> NullPointer in local provider update when a new file is added
> -
>
> Key: SCM-193
> URL: http://jira.codehaus.org/browse/SCM-193
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-local
>Affects Versions: 1.0-beta-3
>Reporter: Carlos Sanchez
>Assignee: Emmanuel Venisse
>Priority: Critical
> Fix For: 1.0-beta-4
>
>
> org.apache.maven.continuum.scm.ContinuumScmException: Error while update
> sources.
> at
> org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272)
> at
> org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58)
> at
> org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166)
> at
> org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47)
> at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM
> command.
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
> at
> org.apache.maven.scm.provider.local.LocalScmProvider.update(LocalScmProvider.java:191)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:386)
> at
> org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:363)
> at
> org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at java.util.Date.getMillisOf(Date.java:938)
> at java.util.Date.after(Date.java:911)
> at
> org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:89)
> at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55)
> ... 9 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2949) interactiveMode, offline, and usePluginRegistry properties of the global settings are not honoured
interactiveMode, offline, and usePluginRegistry properties of the global settings are not honoured -- Key: MNG-2949 URL: http://jira.codehaus.org/browse/MNG-2949 Project: Maven 2 Issue Type: Bug Components: Settings Affects Versions: 2.0.6, 2.0.5, 2.0.4 Reporter: Franz Allan Valencia See Setting the , , and elements in the user settings file allows maven to use them. But these elements are not know to maven if these are set in the global settings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2949) interactiveMode, offline, and usePluginRegistry properties of the global settings are not honoured
[ http://jira.codehaus.org/browse/MNG-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franz Allan Valencia See updated MNG-2949: -- Attachment: MNG-2949-maven-settings.patch MNG-2949-maven-settings.patch fixes this issue and test cases. > interactiveMode, offline, and usePluginRegistry properties of the global > settings are not honoured > -- > > Key: MNG-2949 > URL: http://jira.codehaus.org/browse/MNG-2949 > Project: Maven 2 > Issue Type: Bug > Components: Settings >Affects Versions: 2.0.4, 2.0.5, 2.0.6 >Reporter: Franz Allan Valencia See > Attachments: MNG-2949-maven-settings.patch > > > Setting the , , and elements > in the user settings file allows maven to use them. But these elements are > not know to maven if these are set in the global settings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-307) Tests fail if in path with spaces
[
http://jira.codehaus.org/browse/SUREFIRE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92983
]
Wim Deblauwe commented on SUREFIRE-307:
---
It is ok now. Thanks!
> Tests fail if in path with spaces
> -
>
> Key: SUREFIRE-307
> URL: http://jira.codehaus.org/browse/SUREFIRE-307
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, TestNG support
>Affects Versions: 2.3
> Environment: Windows XP
> Maven 2.0.5
> Java 1.6.0
>Reporter: Wim Deblauwe
>
> I use TestNG with Surefire. My build fails if my project is in a path with
> spaces, because my tests fail. In my tests I have the following code:
> new File( getClass().getResource( "sample-java-utils-log.xml" ).toURI() )
> This results in the following error:
> java.net.URISyntaxException: Illegal character in path at index 18:
> file:/C:/Documents and
> Settings/wdb/.hudson/jobs/Vigilog/workspace/trunk/target/test-classes/net/sourceforge/vigilog/parse/sample-
> java-utils-log.xml
> at java.net.URI$Parser.fail(Unknown Source)
> at java.net.URI$Parser.checkChars(Unknown Source)
> at java.net.URI$Parser.parseHierarchical(Unknown Source)
> at java.net.URI$Parser.parse (Unknown Source)
> at java.net.URI.(Unknown Source)
> at java.net.URL.toURI(Unknown Source)
> at
> net.sourceforge.vigilog.parse.JavaLoggingXMLFileLogFileParserTest.testParse(JavaLoggingXMLFileLogFileParserTest.java
> :38)
> If I put my project in a path without spaces, I don't have this problem (I
> noticed this problem, because I tried Hudson build server and it checks the
> project out to my home directory)
> According to Jesse Glick from the Hudson mailing list, the problem is due to
> the following fact (full thread:
> http://www.nabble.com/Build-fails-under-hudson-due-to-TestNG-unit-tests-tf3354110.html):
> Wim Deblauwe wrote:
> > If it is any help, this is the source code of IsolatedClassLoader:
> > http://svn.apache.org/viewvc/maven/surefire/trunk/surefire-booter/src/main/java/org/apache/maven/surefire/booter/IsolatedClassLoader.java?view=markup
> It sure does help, because this class is probably to blame for your problem:
> http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-api/src/main/java/org/apache/maven/surefire/util/UrlUtils.java
> Note the call to File.toURL(), deprecated as of JDK 6 because
> $ jrunscript
> js> println(new java.io.File("/tmp/foo and bar/baz").toURI().toURL())
> file:/tmp/foo%20and%20bar/baz
> js> println(new java.io.File("/tmp/foo and bar/baz").toURL())
> file:/tmp/foo and bar/baz
> js> println(new java.io.File("/tmp/foo and bar/baz").toURL().toURI())
> script error: sun.org.mozilla.javascript.internal.WrappedException:
> Wrapped java.net.URISyntaxException: Illegal character in path at index
> 13: file:/tmp/foo and bar/baz (#1) in at line number 1
> js>
> If you want to reproduce this, check out my open source project to a
> directory with spaces from:
> https://vigilog.svn.sourceforge.net/svnroot/vigilog/trunk
> and run 'mvn test'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
