[jira] Commented: (MPCLOVER-56) Upgrade to Clover 1.3.13
[ http://jira.codehaus.org/browse/MPCLOVER-56?page=comments#action_75273 ] Lukas Theussl commented on MPCLOVER-56: --- It's not on ibiblio yet? > Upgrade to Clover 1.3.13 > > > Key: MPCLOVER-56 > URL: http://jira.codehaus.org/browse/MPCLOVER-56 > Project: maven-clover-plugin > Issue Type: Improvement >Affects Versions: 1.11 >Reporter: Vincent Massol > Fix For: 1.12 > > -- 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: (MPCLOVER-57) clover:merge should use maven.multiproject.basedir
[ http://jira.codehaus.org/browse/MPCLOVER-57?page=all ] Lukas Theussl closed MPCLOVER-57. - Resolution: Fixed > clover:merge should use maven.multiproject.basedir > -- > > Key: MPCLOVER-57 > URL: http://jira.codehaus.org/browse/MPCLOVER-57 > Project: maven-clover-plugin > Issue Type: Bug >Affects Versions: 1.11 >Reporter: Lukas Theussl > Assigned To: Lukas Theussl > Fix For: 1.12 > > -- 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-161) need flag to specify eclipse project name
[ http://jira.codehaus.org/browse/MECLIPSE-161?page=comments#action_75272 ] Joerg Schaible commented on MECLIPSE-161: - I'd rather have a prefix or suffix that is added to the artifactId as project name for Eclipse. In a multi-module project you will build a lot of Eclipse projects at once, so specifying the name does not help. > need flag to specify eclipse project name > - > > Key: MECLIPSE-161 > URL: http://jira.codehaus.org/browse/MECLIPSE-161 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Brian Fox >Priority: Minor > > We have multiple branches of our projects and the name is the same. We need > the ability to define a new name so that both can coexist in eclipse at the > same time. (you can't choose the name when importing). I was thinking of just > a simple -Declipse.name= would be sufficient. -- 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: (MPCLOVER-57) clover:merge should use maven.multiproject.basedir
clover:merge should use maven.multiproject.basedir -- Key: MPCLOVER-57 URL: http://jira.codehaus.org/browse/MPCLOVER-57 Project: maven-clover-plugin Issue Type: Bug Affects Versions: 1.11 Reporter: Lukas Theussl Assigned To: Lukas Theussl Fix For: 1.12 -- 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-898) Replace links by icons in projectGroupBuildDefinition
[ http://jira.codehaus.org/browse/CONTINUUM-898?page=all ] Marvin King updated CONTINUUM-898: -- Attachment: CONTINUUM898-continuum-webapp.patch - includes a refactored projectGroupTab > Replace links by icons in projectGroupBuildDefinition > - > > Key: CONTINUUM-898 > URL: http://jira.codehaus.org/browse/CONTINUUM-898 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Reporter: Marvin King > Assigned To: Marvin King > Fix For: 1.1 > > Attachments: CONTINUUM898-continuum-webapp.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-164) Rewritten POM loses all the comments
[ http://jira.codehaus.org/browse/MRELEASE-164?page=all ] Brett Porter closed MRELEASE-164. - Assignee: Brett Porter Resolution: Incomplete yep, maven doesn't prescribe the versions of the plugins you use - that happens in the POM. 2.0-beta-4 is much improved and already released. > Rewritten POM loses all the comments > > > Key: MRELEASE-164 > URL: http://jira.codehaus.org/browse/MRELEASE-164 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Kohsuke Kawaguchi > Assigned To: Brett Porter > > When I run "mvn release:prepare", it updates the version information in POM, > but it also scraps off all the comments and other useful information in the > POM. The version rewriting process should only touch the version number > portion of the POM. -- 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-164) Rewritten POM loses all the comments
[ http://jira.codehaus.org/browse/MRELEASE-164?page=comments#action_75263 ] Kohsuke Kawaguchi commented on MRELEASE-164: My apologies. I was using maven 2.0.4, so I just assumed that all the plugins are also 2.0.4. I just checked and the version was 2.0-beta-3. I think you are saying it has been fixed since then. > Rewritten POM loses all the comments > > > Key: MRELEASE-164 > URL: http://jira.codehaus.org/browse/MRELEASE-164 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Kohsuke Kawaguchi > > When I run "mvn release:prepare", it updates the version information in POM, > but it also scraps off all the comments and other useful information in the > POM. The version rewriting process should only touch the version number > portion of the POM. -- 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: (MRESOURCES-25) Filtering of property values containing backslashes in path names still does not escape them?
[ http://jira.codehaus.org/browse/MRESOURCES-25?page=comments#action_75262
]
Brian Fox commented on MRESOURCES-25:
-
We are seeing this also and are using 2.2
> Filtering of property values containing backslashes in path names still does
> not escape them?
> -
>
> Key: MRESOURCES-25
> URL: http://jira.codehaus.org/browse/MRESOURCES-25
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Environment: Windows
>Reporter: Bryan Carpenter
>
> This was originally reported as MRESOURCES-17, and I understood from the
> comments
> there it was fixed in version 2.2 of the plugin. But I have tried using that
> version of the
> resources plugin, and I am still seeing the same problem.
> My source property file contains:
> org.apache.ws.security.crypto.merlin.file=${basedir}/keys/x509.PFX.MSFT
> After filtering it looks like this:
>
> org.apache.ws.security.crypto.merlin.file=D:\cygwin\home\dbc\cvs\omii-packaging\source\ws-wss4j/keys/x509.PFX.MSFT
> and when the this is read in by `Properties.load()' the value ends up as:
> d:cygwinhomedbccvsomii-packagingsourcews-wss4j/keys/x509.PFX.MSFT
--
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-161) need flag to specify eclipse project name
need flag to specify eclipse project name - Key: MECLIPSE-161 URL: http://jira.codehaus.org/browse/MECLIPSE-161 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Brian Fox Priority: Minor We have multiple branches of our projects and the name is the same. We need the ability to define a new name so that both can coexist in eclipse at the same time. (you can't choose the name when importing). I was thinking of just a simple -Declipse.name= would be sufficient. -- 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-164) Rewritten POM loses all the comments
[ http://jira.codehaus.org/browse/MRELEASE-164?page=comments#action_75261 ] Brett Porter commented on MRELEASE-164: --- What version of the plugin are you using? You said it affects version 2.0, which doesn't exist yet. This shouldn't be a problem in the latest beta, but would be in an older version. > Rewritten POM loses all the comments > > > Key: MRELEASE-164 > URL: http://jira.codehaus.org/browse/MRELEASE-164 > Project: Maven 2.x Release Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Kohsuke Kawaguchi > > When I run "mvn release:prepare", it updates the version information in POM, > but it also scraps off all the comments and other useful information in the > POM. The version rewriting process should only touch the version number > portion of the POM. -- 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-2361) Document pomRefId attribute for M2 ant tasks on M2 website.
[ http://jira.codehaus.org/browse/MNG-2361?page=comments#action_75259 ] Antoine Levy-Lambert commented on MNG-2361: --- Hi, if one of the maven developers would write down in this bug report where is the source for http://maven.apache.org/ant-tasks.html in Subversion, it should be possible to fix that. Regards, Antoine > Document pomRefId attribute for M2 ant tasks on M2 website. > --- > > Key: MNG-2361 > URL: http://jira.codehaus.org/browse/MNG-2361 > Project: Maven 2 > Issue Type: Wish > Components: Ant tasks >Affects Versions: 2.0.4 > Environment: Not of importance. >Reporter: Davy Toch >Priority: Minor > Fix For: 2.0.5 > > > Consider the following ANT script: >xmlns:m="antlib:org.apache.maven.artifact.ant"> > > > > > > > > > > > > > > The following **undocumented** shorthand notation is available: >xmlns:m="antlib:org.apache.maven.artifact.ant"> > > > > > > > > The shorter, the better :-). -- 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-2509) M2/ANT : Weird ClassCastException in in macrodef when calling Beanshell scripting.
[ http://jira.codehaus.org/browse/MNG-2509?page=comments#action_75258 ]
Antoine Levy-Lambert commented on MNG-2509:
---
Hello Davy,
can you start ant with -verbose or -debug to get a stack trace.
If the stack trace leads you to believe that it is an ant bug (could be) then
you can cross post this issue in bugzilla.
Mention it here so that the Maven developers know that this is followed up on
the Ant side.
Regards,
Antoine
> M2/ANT : Weird ClassCastException in in macrodef when calling
> Beanshell scripting.
> --
>
> Key: MNG-2509
> URL: http://jira.codehaus.org/browse/MNG-2509
> Project: Maven 2
> Issue Type: Bug
> Components: Ant tasks
>Affects Versions: 2.0.4
> Environment: - ANT 1.6.5 (with bsh-2.0b4.jar in ANT_HOME/lib)
> - JDK 1.5
>Reporter: Davy Toch
> Attachments: build.xml, pom.xml
>
>
> Hi,
> In ANT, sometimes more than one artifact is generated from the same
> build file (e.g. myapp.jar, myapp-client.jar, myapp-with-deps.jar).
> If using the M2 plugin for ANT (currently 2.0.4), this would mean
> we would need three POM's for the above 3 artifacts. However, in the
> above case the 3 POM's would be almost identical.
> So I have taken the following approach in order to have only one generic
> POM:
> pom.xml (with ANT tokens _TOKEN_...):
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> be.steria.test
> _TOKEN_ARTIFACTID_
> _TOKEN_PACKAGING_
> 1.5-SNAPSHOT
> Test artifact
>
>
> log4j
> log4j
> 1.2.9
> compile
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
> repo_dev
> scp://localhost/m2demo/repo_dev
>
>
>
> build.xml:
>xmlns:m="antlib:org.apache.maven.artifact.ant">
>
>
>
>
>
>
>toFile="[EMAIL PROTECTED]">
>
>
>to="@{artifactId}"/>
>to="@{packaging}"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
> artifactId="myapp-with-deps"/>
>
>
>
>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
>pomRefId="M2POM_MYAPP"/>
>pomRefId="M2POM_MYAPP_CLIENT"/>
>pomRefId="M2POM_MYAPP_WITH_DEPS"/>
>
>
> Now if I execute the above, everything works fine, but if I add
[jira] Commented: (MPDIST-31) Move consolidated javadocs into multiproject:site.
[ http://jira.codehaus.org/browse/MPDIST-31?page=comments#action_75255 ] Arnaud Heritier commented on MPDIST-31: --- Or in the javadoc project itself (javadoc:multiproject). We encouraged a long long time ago to deprecate multiproject:XXX goal when XXX is another plugin. > Move consolidated javadocs into multiproject:site. > -- > > Key: MPDIST-31 > URL: http://jira.codehaus.org/browse/MPDIST-31 > Project: maven-dist-plugin > Issue Type: Task >Affects Versions: 1.7 >Reporter: Lukas Theussl > Assigned To: Lukas Theussl > Fix For: 1.7.1 > > > Makes more sense there. However, we'll need to release another version of the > multiproject 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] Updated: (MSUREFIREREP-26) Incoherent data between 'Package List ' and 'Test Cases' items in report
[ http://jira.codehaus.org/browse/MSUREFIREREP-26?page=all ] Bernd updated MSUREFIREREP-26: -- Attachment: MSUREFIREREP-26-maven-surefire-plugin.patch added a test, removed some duplication in the code, replaces last patch > Incoherent data between 'Package List ' and 'Test Cases' items in report > > > Key: MSUREFIREREP-26 > URL: http://jira.codehaus.org/browse/MSUREFIREREP-26 > Project: Maven 2.x Surefire report Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Damien Lecan > Attachments: MSUREFIREREP-26-maven-surefire-plugin.patch, > MSUREFIREREP-26-maven-surefire-plugin.patch, surefire-report.html > > > As it can be seen of the attached file, the ConfigTest has incoherent data > between items 'Package List ' and 'Test Cases' . > In 'Package List ' : > Class Tests Errors FailuresSuccess RateTime > ConfigTest3 0 0100% > 0.585 > ConfigTest has just 3 tests. > But, in 'Test Cases', there are much more than 3 tests (they are duplicated > from the other tested class ManagerTest !) > ConfigTest > testCBEM1 0.039 > testCBEM2 0.001 > testCBEM3 0.001 > testCBEM4 0.001 > testCBEM5 0 > testCBEM6 0 > testCBEM7 0 > testCBEM8 0 > testCBEM9 0 > testCBEM10 0.001 > testCBEM11 0 > testCBEM12 0.001 > testGetBooleanProperty 0.528 > testGetFloatProperty0.029 > testGetIntProperty 0.012 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPDIST-30) Dist plugin should take into account the javadoc properties
[ http://jira.codehaus.org/browse/MPDIST-30?page=all ] Lukas Theussl updated MPDIST-30: Affects Version/s: (was: 1.7.1) 1.7 Point 2 should be fixed in SVN, point 1 requires a bit more work... > Dist plugin should take into account the javadoc properties > --- > > Key: MPDIST-30 > URL: http://jira.codehaus.org/browse/MPDIST-30 > Project: maven-dist-plugin > Issue Type: Improvement >Affects Versions: 1.7 > Environment: Win 2K, JDK 1.6 b2 >Reporter: Benoit Xhenseval > Assigned To: Lukas Theussl > Fix For: 1.7.1 > > > 1/ The consolidated javadoc does not seem to take into account any javadoc > settings, nor use any default like: > maven.javadoc.bottom (for copyright stuff). > 2/ I also seems to complain (just warnings) that the classpath does not > include reference to the dependencies jars (hence it cannot link to some > imported classes, eg: > [javadoc] > C:\project\objectlabkit\datecalc-joda\src\main\java\net\objectlab\kit\datecalc\joda\HolidayHandlerYearMonthDayWrapper.java:23: > package org.joda.time does not exist > [javadoc] import org.joda.time.LocalDate; > [javadoc] ^ > May be it could include the dependencies by default? > 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] Created: (MPDIST-31) Move consolidated javadocs into multiproject:site.
Move consolidated javadocs into multiproject:site. -- Key: MPDIST-31 URL: http://jira.codehaus.org/browse/MPDIST-31 Project: maven-dist-plugin Issue Type: Task Affects Versions: 1.7 Reporter: Lukas Theussl Assigned To: Lukas Theussl Fix For: 1.7.1 Makes more sense there. However, we'll need to release another version of the multiproject 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] Updated: (MPDIST-30) Dist plugin should take into account the javadoc properties
[ http://jira.codehaus.org/browse/MPDIST-30?page=all ] Lukas Theussl updated MPDIST-30: Assignee: Lukas Theussl Fix Version/s: 1.7.1 > Dist plugin should take into account the javadoc properties > --- > > Key: MPDIST-30 > URL: http://jira.codehaus.org/browse/MPDIST-30 > Project: maven-dist-plugin > Issue Type: Improvement >Affects Versions: 1.7.1 > Environment: Win 2K, JDK 1.6 b2 >Reporter: Benoit Xhenseval > Assigned To: Lukas Theussl > Fix For: 1.7.1 > > > 1/ The consolidated javadoc does not seem to take into account any javadoc > settings, nor use any default like: > maven.javadoc.bottom (for copyright stuff). > 2/ I also seems to complain (just warnings) that the classpath does not > include reference to the dependencies jars (hence it cannot link to some > imported classes, eg: > [javadoc] > C:\project\objectlabkit\datecalc-joda\src\main\java\net\objectlab\kit\datecalc\joda\HolidayHandlerYearMonthDayWrapper.java:23: > package org.joda.time does not exist > [javadoc] import org.joda.time.LocalDate; > [javadoc] ^ > May be it could include the dependencies by default? > 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] Reopened: (MEAR-33) add option to include modules in EAR in exploded (i.e. directory) form, rather than as in jar form
[ http://jira.codehaus.org/browse/MEAR-33?page=all ] Ian Springer reopened MEAR-33: -- I just build 2.3-SNAPSHOT and tried this out. I added the following setting to my ear-plugin config: ejb,war,sar But when I run mvn install, I get the following error: [ERROR] BUILD ERROR [INFO] [INFO] No Archiver found for EAR modules Embedded error: No such archiver: 'sar'. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: No Archiver found for EA R modules at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: No Archiver found for EAR modules at org.apache.maven.plugin.ear.EarMojo.execute(EarMojo.java:208) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more Caused by: org.codehaus.plexus.archiver.manager.NoSuchArchiverException: No such archiver: 'sar'. at org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArch iver(DefaultArchiverManager.java:80) at org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArch iver(DefaultArchiverManager.java:114) at org.apache.maven.plugin.ear.EarMojo.unpack(EarMojo.java:382) at org.apache.maven.plugin.ear.EarMojo.execute(EarMojo.java:189) ... 18 more It looks like the plexus-archiver needs to be updated to grok the sar extension. > add option to include modules in EAR in exploded (i.e. directory) form, > rather than as in jar form > -- > > Key: MEAR-33 > URL: http://jira.codehaus.org/browse/MEAR-33 > Project: Maven 2.x Ear Plugin > Issue Type: New Feature >Affects Versions: 2.2 >Reporter: Ian Springer > Assigned To: Stephane Nicoll > Fix For: 2.3 > > Attachments: MEAR-33.patch > > > In JBoss, and perhaps other app servers, modules can be packaged in an EAR as > directories. For example: > my.ear/ > my.war/ > service1.sar/ > service2.sar/ > Please add an option on the ear plugin that allows you to specify that > modules should be packaged in exploded form. -- 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: (MEAR-41) publish 2.3-SNAPSHOT to snapshots repo
publish 2.3-SNAPSHOT to snapshots repo --- Key: MEAR-41 URL: http://jira.codehaus.org/browse/MEAR-41 Project: Maven 2.x Ear Plugin Issue Type: Task Affects Versions: 2.3 Reporter: Ian Springer Would someone please publish a 2.3-SNAPSHOT build to http://people.apache.org/maven-snapshot-repository/? Thanks, Ian -- 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: (MPARTIFACT-72) m1.1-rc1 Creating an upload-bundle for a plugin without any java code does not work...
[ http://jira.codehaus.org/browse/MPARTIFACT-72?page=all ] Lukas Theussl closed MPARTIFACT-72. --- Resolution: Fixed > m1.1-rc1 Creating an upload-bundle for a plugin without any java code does > not work... > -- > > Key: MPARTIFACT-72 > URL: http://jira.codehaus.org/browse/MPARTIFACT-72 > Project: maven-artifact-plugin > Issue Type: Bug >Affects Versions: 1.8.1 > Environment: Win 2K >Reporter: Benoit Xhenseval > Assigned To: Lukas Theussl > Fix For: 1.8.1 > > > Hi > Currently using 1.8.1-SNAPSHOT > If I call the target artifact:create-upload-bundle on a maven plugin which > does NOT have any java code (only some jelly), it looks like there is a > problem in the artifact plugin (or the javadoc one). The javadoc plugin > fails (as there are no java code) but the artifact plugin cannot handle the > failure and stops as well. I believe that it should carry on. > any quick suggestion? > thanks > Benoit > - > artifact:create-upload-bundle: > java:prepare-filesystem: > java:compile: > [echo] No java source files to compile. > java:jar-resources: > test:test: > [echo] No tests to run. > jar:jar: > [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\bundle > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [echo] Rewriting POM... > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [echo] Copying license: C:\project\qalab\maven-qalab-plugin/LICENSE.txt > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [jar] Building MANIFEST-only jar: > C:\project\qalab\maven-qalab-plugin\target\bundle\maven-qalab-plugin-0.9.2-sources > .jar > xdoc:init-i18n: > xdoc:init: > [echo] Generates the directory structure required for xdocs > maven-javadoc-plugin:report: > [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\javadoc > [mkdir] Created dir: > C:\project\qalab\maven-qalab-plugin\target\javadoc\src > [echo] *** > [echo] * No sources found. Javadoc not created ! * > [echo] *** > javadoc: > javadoc:jar: > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-artifact-plugin-1.8.1-SNAPSHOT/plugin.jelly > Element... ant:copy > Line.. 225 > Column 141 > Warning: Could not find file > C:\project\qalab\maven-qalab-plugin\target\maven-qalab-plugin-0.9.2_javadoc.jar > to copy. > Total time : 30 seconds > Finished at : 19 September 2006 17:34:10 BST -- 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-1140) org.apache.derby:derby 10.1.3.1 missing in maven-metadata.xml
org.apache.derby:derby 10.1.3.1 missing in maven-metadata.xml -- Key: MAVENUPLOAD-1140 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1140 Project: maven-upload-requests Issue Type: Task Reporter: Rainer Wasserfuhr the version 10.1.3.1 is missing in maven-metadata.xml, however, the 10.1.3.1 jar is available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-446) typo in jtds pom
typo in jtds pom Key: MEV-446 URL: http://jira.codehaus.org/browse/MEV-446 Project: Maven Evangelism Issue Type: Bug Components: Invalid POM Reporter: fabrizio giustina http://repo1.maven.org/maven2/net/sourceforge/jtds/jtds/1.2/jtds-1.2.pom has a tag spelledthat should be removed (there are no dependencies listed) -- 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: (MPDIST-20) Support multiprojects
[ http://jira.codehaus.org/browse/MPDIST-20?page=all ] Lukas Theussl closed MPDIST-20. --- Assignee: Lukas Theussl Resolution: Fixed The patch has been applied indeed but the comments above indicate that the issue is not completely resolved. I'm closing it anyway as I don't have time to investigate, please open another ticket for any remaining issues. > Support multiprojects > - > > Key: MPDIST-20 > URL: http://jira.codehaus.org/browse/MPDIST-20 > Project: maven-dist-plugin > Issue Type: Improvement >Reporter: Phil Steitz > Assigned To: Lukas Theussl > Attachments: dist-plugin-2.patch, dist-plugin.patch, > dist-plugin3.patch, distPlugin4.patch > > > There is currently no way to make source and distributions for multiprojects. > It would be great if the dist plugin supported this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPARTIFACT-72) m1.1-rc1 Creating an upload-bundle for a plugin without any java code does not work...
[ http://jira.codehaus.org/browse/MPARTIFACT-72?page=all ] Lukas Theussl updated MPARTIFACT-72: Assignee: Lukas Theussl Fix Version/s: 1.8.1 > m1.1-rc1 Creating an upload-bundle for a plugin without any java code does > not work... > -- > > Key: MPARTIFACT-72 > URL: http://jira.codehaus.org/browse/MPARTIFACT-72 > Project: maven-artifact-plugin > Issue Type: Bug >Affects Versions: 1.8.1 > Environment: Win 2K >Reporter: Benoit Xhenseval > Assigned To: Lukas Theussl > Fix For: 1.8.1 > > > Hi > Currently using 1.8.1-SNAPSHOT > If I call the target artifact:create-upload-bundle on a maven plugin which > does NOT have any java code (only some jelly), it looks like there is a > problem in the artifact plugin (or the javadoc one). The javadoc plugin > fails (as there are no java code) but the artifact plugin cannot handle the > failure and stops as well. I believe that it should carry on. > any quick suggestion? > thanks > Benoit > - > artifact:create-upload-bundle: > java:prepare-filesystem: > java:compile: > [echo] No java source files to compile. > java:jar-resources: > test:test: > [echo] No tests to run. > jar:jar: > [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\bundle > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [echo] Rewriting POM... > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [echo] Copying license: C:\project\qalab\maven-qalab-plugin/LICENSE.txt > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [jar] Building MANIFEST-only jar: > C:\project\qalab\maven-qalab-plugin\target\bundle\maven-qalab-plugin-0.9.2-sources > .jar > xdoc:init-i18n: > xdoc:init: > [echo] Generates the directory structure required for xdocs > maven-javadoc-plugin:report: > [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\javadoc > [mkdir] Created dir: > C:\project\qalab\maven-qalab-plugin\target\javadoc\src > [echo] *** > [echo] * No sources found. Javadoc not created ! * > [echo] *** > javadoc: > javadoc:jar: > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-artifact-plugin-1.8.1-SNAPSHOT/plugin.jelly > Element... ant:copy > Line.. 225 > Column 141 > Warning: Could not find file > C:\project\qalab\maven-qalab-plugin\target\maven-qalab-plugin-0.9.2_javadoc.jar > to copy. > Total time : 30 seconds > Finished at : 19 September 2006 17:34:10 BST -- 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-1139) Upload 1.2.1 "cayenne", "cayenne-nodeps" and "cayenne-client-nodeps"
Upload 1.2.1 "cayenne", "cayenne-nodeps" and "cayenne-client-nodeps" Key: MAVENUPLOAD-1139 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1139 Project: maven-upload-requests Issue Type: Task Reporter: Andrus Adamchik Cayenne is already on ibiblio. Please upload these three new bundles for the final release: http://dev.objectstyle.org/~andrus/cayenne/release/1.2.1/cayenne-1.2.1-bundle.jar http://dev.objectstyle.org/~andrus/cayenne/release/1.2.1/cayenne-client-nodeps-1.2.1-bundle.jar http://dev.objectstyle.org/~andrus/cayenne/release/1.2.1/cayenne-nodeps-1.2.1-bundle.jar Thanks! Andrus -- 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-1138) Upload jxls-core-0.9.1
Upload jxls-core-0.9.1 --- Key: MAVENUPLOAD-1138 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1138 Project: maven-upload-requests Issue Type: Task Reporter: Leonid Vysochyn jXLS is small and easy-to-use Java library for generating Excel files using XLS templates. Parent pom can be found here: http://jxls.sourceforge.net/repository/jxls-0.9.1/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] Created: (SCM-234) SCM Plugin documentation is not usable due to several broken links
SCM Plugin documentation is not usable due to several broken links -- Key: SCM-234 URL: http://jira.codehaus.org/browse/SCM-234 Project: Maven SCM Issue Type: Improvement Components: documentation Reporter: Jimisola Laursen SCM Plugin documentation is not usable due to several broken links and have had so for a long time if I remember right. http://maven.apache.org/scm/plugins/ Some of the broken links are: http://maven.apache.org/scm/plugins/scm-url-format.html http://maven.apache.org/scm/plugins/scms-overview.html Considering the fact that it is essential to Maven it be nice if it worked. -- 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-164) Rewritten POM loses all the comments
Rewritten POM loses all the comments Key: MRELEASE-164 URL: http://jira.codehaus.org/browse/MRELEASE-164 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0 Reporter: Kohsuke Kawaguchi When I run "mvn release:prepare", it updates the version information in POM, but it also scraps off all the comments and other useful information in the POM. The version rewriting process should only touch the version number portion of the POM. -- 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-72) m1.1-rc1 Creating an upload-bundle for a plugin without any java code does not work...
[ http://jira.codehaus.org/browse/MPARTIFACT-72?page=comments#action_75232 ] Benoit Xhenseval commented on MPARTIFACT-72: Solution: add failonerror="false" on the > m1.1-rc1 Creating an upload-bundle for a plugin without any java code does > not work... > -- > > Key: MPARTIFACT-72 > URL: http://jira.codehaus.org/browse/MPARTIFACT-72 > Project: maven-artifact-plugin > Issue Type: Bug >Affects Versions: 1.8.1 > Environment: Win 2K >Reporter: Benoit Xhenseval > > Hi > Currently using 1.8.1-SNAPSHOT > If I call the target artifact:create-upload-bundle on a maven plugin which > does NOT have any java code (only some jelly), it looks like there is a > problem in the artifact plugin (or the javadoc one). The javadoc plugin > fails (as there are no java code) but the artifact plugin cannot handle the > failure and stops as well. I believe that it should carry on. > any quick suggestion? > thanks > Benoit > - > artifact:create-upload-bundle: > java:prepare-filesystem: > java:compile: > [echo] No java source files to compile. > java:jar-resources: > test:test: > [echo] No tests to run. > jar:jar: > [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\bundle > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [echo] Rewriting POM... > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [echo] Copying license: C:\project\qalab\maven-qalab-plugin/LICENSE.txt > [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle > [jar] Building MANIFEST-only jar: > C:\project\qalab\maven-qalab-plugin\target\bundle\maven-qalab-plugin-0.9.2-sources > .jar > xdoc:init-i18n: > xdoc:init: > [echo] Generates the directory structure required for xdocs > maven-javadoc-plugin:report: > [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\javadoc > [mkdir] Created dir: > C:\project\qalab\maven-qalab-plugin\target\javadoc\src > [echo] *** > [echo] * No sources found. Javadoc not created ! * > [echo] *** > javadoc: > javadoc:jar: > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-artifact-plugin-1.8.1-SNAPSHOT/plugin.jelly > Element... ant:copy > Line.. 225 > Column 141 > Warning: Could not find file > C:\project\qalab\maven-qalab-plugin\target\maven-qalab-plugin-0.9.2_javadoc.jar > to copy. > Total time : 30 seconds > Finished at : 19 September 2006 17:34:10 BST -- 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: (MPARTIFACT-72) m1.1-rc1 Creating an upload-bundle for a plugin without any java code does not work...
m1.1-rc1 Creating an upload-bundle for a plugin without any java code does not work... -- Key: MPARTIFACT-72 URL: http://jira.codehaus.org/browse/MPARTIFACT-72 Project: maven-artifact-plugin Issue Type: Bug Affects Versions: 1.8.1 Environment: Win 2K Reporter: Benoit Xhenseval Hi Currently using 1.8.1-SNAPSHOT If I call the target artifact:create-upload-bundle on a maven plugin which does NOT have any java code (only some jelly), it looks like there is a problem in the artifact plugin (or the javadoc one). The javadoc plugin fails (as there are no java code) but the artifact plugin cannot handle the failure and stops as well. I believe that it should carry on. any quick suggestion? thanks Benoit - artifact:create-upload-bundle: java:prepare-filesystem: java:compile: [echo] No java source files to compile. java:jar-resources: test:test: [echo] No tests to run. jar:jar: [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\bundle [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle [echo] Rewriting POM... [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle [echo] Copying license: C:\project\qalab\maven-qalab-plugin/LICENSE.txt [copy] Copying 1 file to C:\project\qalab\maven-qalab-plugin\target\bundle [jar] Building MANIFEST-only jar: C:\project\qalab\maven-qalab-plugin\target\bundle\maven-qalab-plugin-0.9.2-sources .jar xdoc:init-i18n: xdoc:init: [echo] Generates the directory structure required for xdocs maven-javadoc-plugin:report: [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\javadoc [mkdir] Created dir: C:\project\qalab\maven-qalab-plugin\target\javadoc\src [echo] *** [echo] * No sources found. Javadoc not created ! * [echo] *** javadoc: javadoc:jar: BUILD FAILED File.. file:/C:/Documents and Settings/xhensevb/.maven/cache/maven-artifact-plugin-1.8.1-SNAPSHOT/plugin.jelly Element... ant:copy Line.. 225 Column 141 Warning: Could not find file C:\project\qalab\maven-qalab-plugin\target\maven-qalab-plugin-0.9.2_javadoc.jar to copy. Total time : 30 seconds Finished at : 19 September 2006 17:34:10 BST -- 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-160) Wrong description with the goal "add-maven-repo" documentation
Wrong description with the goal "add-maven-repo" documentation -- Key: MECLIPSE-160 URL: http://jira.codehaus.org/browse/MECLIPSE-160 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Reporter: Naoki Nose The plugin documentation says the goal eclipse:add-maven-repo adds the classpath variable MAVEN_REPO to Eclipse. But that goal adds the variable M2_REPO actually. -- 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-780) Problem with check out with more than one sheduled projects
[ http://jira.codehaus.org/browse/CONTINUUM-780?page=all ] Emmanuel Venisse closed CONTINUUM-780. -- Resolution: Fixed Fixed. > Problem with check out with more than one sheduled projects > --- > > Key: CONTINUUM-780 > URL: http://jira.codehaus.org/browse/CONTINUUM-780 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 > Environment: Win2003 SP1, Maven 2.0.4 >Reporter: Thorsten Düvelmeyer > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > > it seems to be a problem with the local provider. The local provider doesn't > initialize the change > date because we can't know it and in DefaultContinuumScm, we check it. Please > create an issue. > Emmanuel > [EMAIL PROTECTED] a écrit : > > Hi, > > > > now i have five projects, that start at 12:00. > > All Projects get this error (see below). > > > > (Manuell starting works fine - scm provider is 'file') > > > > What is going wrong? > > > > > > Thanks, > > Thorsten > > > > > > > > Build statistics: > > State: Error > > Previous State: Ok > > Started at: Fr, 14 Jul 2006 12:00:51 +0200 > > Finished at: Fr, 14 Jul 2006 12:01:05 +0200 > > Total time: 14s > > Build Trigger: Schedule > > Exit code: 0 > > Building machine hostname: srv-ew-web > > Operating system : Windows 2003(Service Pack 1) > > Java version : 1.5.0_06(Sun Microsystems Inc.) > > > > > > > > > > Build Error: > > > > > > org.apache.maven.continuum.scm.ContinuumScmException: Cannot checkout > > sources. > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:276) > > > > 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: java.lang.NullPointerException > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.convertScmResult(DefaultContinuumScm.java:414) > > > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:244) > > > > ... 5 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] Updated: (CONTINUUM-780) Problem with check out with more than one sheduled projects
[ http://jira.codehaus.org/browse/CONTINUUM-780?page=all ] Emmanuel Venisse updated CONTINUUM-780: --- Assignee: Emmanuel Venisse Fix Version/s: 1.1 > Problem with check out with more than one sheduled projects > --- > > Key: CONTINUUM-780 > URL: http://jira.codehaus.org/browse/CONTINUUM-780 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 > Environment: Win2003 SP1, Maven 2.0.4 >Reporter: Thorsten Düvelmeyer > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > > it seems to be a problem with the local provider. The local provider doesn't > initialize the change > date because we can't know it and in DefaultContinuumScm, we check it. Please > create an issue. > Emmanuel > [EMAIL PROTECTED] a écrit : > > Hi, > > > > now i have five projects, that start at 12:00. > > All Projects get this error (see below). > > > > (Manuell starting works fine - scm provider is 'file') > > > > What is going wrong? > > > > > > Thanks, > > Thorsten > > > > > > > > Build statistics: > > State: Error > > Previous State: Ok > > Started at: Fr, 14 Jul 2006 12:00:51 +0200 > > Finished at: Fr, 14 Jul 2006 12:01:05 +0200 > > Total time: 14s > > Build Trigger: Schedule > > Exit code: 0 > > Building machine hostname: srv-ew-web > > Operating system : Windows 2003(Service Pack 1) > > Java version : 1.5.0_06(Sun Microsystems Inc.) > > > > > > > > > > Build Error: > > > > > > org.apache.maven.continuum.scm.ContinuumScmException: Cannot checkout > > sources. > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:276) > > > > 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: java.lang.NullPointerException > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.convertScmResult(DefaultContinuumScm.java:414) > > > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:244) > > > > ... 5 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: (MAVENUPLOAD-1137) Upload Echo2-Extras 0.3
Upload Echo2-Extras 0.3 --- Key: MAVENUPLOAD-1137 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1137 Project: maven-upload-requests Issue Type: Task Reporter: Edson Yanaga Attachments: echo2-extras-app-0.3-bundle.jar, echo2-extras-webcontainer-0.3-bundle.jar http://www.insula.com.br/maven-upload/echo2-extras-app-0.3-bundle.jar http://www.insula.com.br/maven-upload/echo2-extras-webcontainer-0.3-bundle.jar http://www.nextapp.com/platform/echo2/extras/ Echo2 Extras are adittional componentes to the Echo2 platform. It dependes on MAVENUPLOAD-1136 -- 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: (MASSEMBLY-146) Including -javadoc.jars in a package
[ http://jira.codehaus.org/browse/MASSEMBLY-146?page=comments#action_75223
]
Dan Tran commented on MASSEMBLY-146:
the answer to orginal question, use assembly's fileset to pick up the javadoc's
jar file in ${project.build.directory}
> Including -javadoc.jars in a package
>
>
> Key: MASSEMBLY-146
> URL: http://jira.codehaus.org/browse/MASSEMBLY-146
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
>Reporter: Frank Cornelis
>
> Via the maven-javadoc-plugin it's very easy to construct secundary artifact
> -javadoc.jars.
> How can I include these javadoc JARs in my assembly?
--
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: (MASSEMBLY-146) Including -javadoc.jars in a package
[ http://jira.codehaus.org/browse/MASSEMBLY-146?page=comments#action_75222 ] Dan Tran commented on MASSEMBLY-146: Frank, you second post should be in a separate JIRA > Including -javadoc.jars in a package > > > Key: MASSEMBLY-146 > URL: http://jira.codehaus.org/browse/MASSEMBLY-146 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Frank Cornelis > > Via the maven-javadoc-plugin it's very easy to construct secundary artifact > -javadoc.jars. > How can I include these javadoc JARs in my assembly? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-1136) Upload Echo2 2.1.0.beta5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1136?page=all ] Edson Yanaga updated MAVENUPLOAD-1136: -- Attachment: echo2-webrender-2.1.0.beta5-bundle.jar Echo2 WebRender bundle. > Upload Echo2 2.1.0.beta5 > > > Key: MAVENUPLOAD-1136 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1136 > Project: maven-upload-requests > Issue Type: Task >Reporter: Edson Yanaga > Attachments: echo2-app-2.1.0.beta5-bundle.jar, > echo2-webcontainer-2.1.0.beta5-bundle.jar, > echo2-webrender-2.1.0.beta5-bundle.jar > > > http://www.insula.com.br/maven-upload/echo2-app-2.1.0.beta5-bundle.jar > http://www.insula.com.br/maven-upload/echo2-webcontainer-2.1.0.beta5-bundle.jar > http://www.insula.com.br/maven-upload/echo2-webrender-2.1.0.beta5-bundle.jar > http://www.nextapp.com/platform/echo2/echo/ > Echo2 is a framework for developing rich client applications in the browser. > I'm not a developer, and the packages are named nextapp.* (don't know if it > will be a problem...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-1136) Upload Echo2 2.1.0.beta5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1136?page=all ] Edson Yanaga updated MAVENUPLOAD-1136: -- Attachment: echo2-webcontainer-2.1.0.beta5-bundle.jar Echo2-WebContainer bundle > Upload Echo2 2.1.0.beta5 > > > Key: MAVENUPLOAD-1136 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1136 > Project: maven-upload-requests > Issue Type: Task >Reporter: Edson Yanaga > Attachments: echo2-app-2.1.0.beta5-bundle.jar, > echo2-webcontainer-2.1.0.beta5-bundle.jar > > > http://www.insula.com.br/maven-upload/echo2-app-2.1.0.beta5-bundle.jar > http://www.insula.com.br/maven-upload/echo2-webcontainer-2.1.0.beta5-bundle.jar > http://www.insula.com.br/maven-upload/echo2-webrender-2.1.0.beta5-bundle.jar > http://www.nextapp.com/platform/echo2/echo/ > Echo2 is a framework for developing rich client applications in the browser. > I'm not a developer, and the packages are named nextapp.* (don't know if it > will be a problem...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1136) Upload Echo2 2.1.0.beta5
Upload Echo2 2.1.0.beta5 Key: MAVENUPLOAD-1136 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1136 Project: maven-upload-requests Issue Type: Task Reporter: Edson Yanaga Attachments: echo2-app-2.1.0.beta5-bundle.jar http://www.insula.com.br/maven-upload/echo2-app-2.1.0.beta5-bundle.jar http://www.insula.com.br/maven-upload/echo2-webcontainer-2.1.0.beta5-bundle.jar http://www.insula.com.br/maven-upload/echo2-webrender-2.1.0.beta5-bundle.jar http://www.nextapp.com/platform/echo2/echo/ Echo2 is a framework for developing rich client applications in the browser. I'm not a developer, and the packages are named nextapp.* (don't know if it will be a problem...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-1136) Upload Echo2 2.1.0.beta5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1136?page=all ] Edson Yanaga updated MAVENUPLOAD-1136: -- Attachment: echo2-app-2.1.0.beta5-bundle.jar echo2-app bundle. > Upload Echo2 2.1.0.beta5 > > > Key: MAVENUPLOAD-1136 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1136 > Project: maven-upload-requests > Issue Type: Task >Reporter: Edson Yanaga > Attachments: echo2-app-2.1.0.beta5-bundle.jar > > > http://www.insula.com.br/maven-upload/echo2-app-2.1.0.beta5-bundle.jar > http://www.insula.com.br/maven-upload/echo2-webcontainer-2.1.0.beta5-bundle.jar > http://www.insula.com.br/maven-upload/echo2-webrender-2.1.0.beta5-bundle.jar > http://www.nextapp.com/platform/echo2/echo/ > Echo2 is a framework for developing rich client applications in the browser. > I'm not a developer, and the packages are named nextapp.* (don't know if it > will be a problem...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-780) Problem with check out with more than one sheduled projects
[ http://jira.codehaus.org/browse/CONTINUUM-780?page=comments#action_75218 ] Arne Degenring commented on CONTINUUM-780: -- Occasionally some of our builds are failing during scheduled builds. Forced builds are working fine. I see the same stacktrace as above. A difference is that not all builds are failing, and the problems do not occur every time. I'm using Continuum 1.0.3, but I've updated maven-scm-api and maven-scm-provider-local (snapshot version maven-scm-provider-local-1.0-20060616.154545-4.jar). (originally discussed on http://www.nabble.com/Occassional-NPEs-while-checking-out-through-scm-local-in-scheduled-build-tf2289437.html) > Problem with check out with more than one sheduled projects > --- > > Key: CONTINUUM-780 > URL: http://jira.codehaus.org/browse/CONTINUUM-780 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.0.3 > Environment: Win2003 SP1, Maven 2.0.4 >Reporter: Thorsten Düvelmeyer > > it seems to be a problem with the local provider. The local provider doesn't > initialize the change > date because we can't know it and in DefaultContinuumScm, we check it. Please > create an issue. > Emmanuel > [EMAIL PROTECTED] a écrit : > > Hi, > > > > now i have five projects, that start at 12:00. > > All Projects get this error (see below). > > > > (Manuell starting works fine - scm provider is 'file') > > > > What is going wrong? > > > > > > Thanks, > > Thorsten > > > > > > > > Build statistics: > > State: Error > > Previous State: Ok > > Started at: Fr, 14 Jul 2006 12:00:51 +0200 > > Finished at: Fr, 14 Jul 2006 12:01:05 +0200 > > Total time: 14s > > Build Trigger: Schedule > > Exit code: 0 > > Building machine hostname: srv-ew-web > > Operating system : Windows 2003(Service Pack 1) > > Java version : 1.5.0_06(Sun Microsystems Inc.) > > > > > > > > > > Build Error: > > > > > > org.apache.maven.continuum.scm.ContinuumScmException: Cannot checkout > > sources. > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:276) > > > > 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: java.lang.NullPointerException > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.convertScmResult(DefaultContinuumScm.java:414) > > > > at > > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:244) > > > > ... 5 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] Commented: (MASSEMBLY-146) Including -javadoc.jars in a package
[ http://jira.codehaus.org/browse/MASSEMBLY-146?page=comments#action_75216 ] Frank Cornelis commented on MASSEMBLY-146: -- The maven-assembly-plugin contains a serious bug concerting dependencies with explicit classifier specified. When you have primary dependency X and another dependency X with classifier javadoc, the assembly plugin is overwriting the primary artifact X with the secondary artifact X-javadoc! Thus you end up with a JAR containing only HTML in case of the javadoc classifier! This one was very difficult to find out for me... lost time on it. Please fix it before you drive other people crazy on it! > Including -javadoc.jars in a package > > > Key: MASSEMBLY-146 > URL: http://jira.codehaus.org/browse/MASSEMBLY-146 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Reporter: Frank Cornelis > > Via the maven-javadoc-plugin it's very easy to construct secundary artifact > -javadoc.jars. > How can I include these javadoc JARs in my assembly? -- 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: (MNGECLIPSE-29) Plug-In is not using settings.xml
[ http://jira.codehaus.org/browse/MNGECLIPSE-29?page=comments#action_75213 ] Jan De Laender commented on MNGECLIPSE-29: -- Hi, I met the same issue. Using maven 2, eclipse 3.2, m2eclipse 0.0.9. via CLI, compile and install are successfully processed. instead, in eclipse, the tasks fail, because of the proxy problem. Now copied my settings.xml file (on win xp) to ~/.m2/settings.xml including the proxy settings. This made the problem disappear. Thanks Roland for the information. Regards, Jan > Plug-In is not using settings.xml > - > > Key: MNGECLIPSE-29 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-29 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug >Affects Versions: 0.0.3 > Environment: Windows (probably ANY behind a Proxy or Firewall) >Reporter: Werner Keil >Priority: Minor > Attachments: pom.xml > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > While Maven 2 on its own runs the same goal (test) from the command line > without errors the Plug-in for Eclipse fails trying to update itself or some > other dependency: > [DEBUG] Found 0 components to load on start > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and > Settings\username\.m2\plugin-registry.xml' > [DEBUG] Building Maven global-level settings from: 'C:\Documents and > Settings\username\workspace\32\mtest\conf\settings.xml' > [DEBUG] Building Maven user-level settings from: 'C:\Documents and > Settings\username\.m2\settings.xml' > [DEBUG] mtest:mtest:jar:1.0.1-SNAPSHOT (selected for null) > [DEBUG] junit:junit:jar:3.8.1 (selected for compile) > [INFO] > > [INFO] Building mtest > [INFO]task-segment: [test] > [INFO] > > [DEBUG] maven-resources-plugin: resolved to version 2.1 from repository > central > [DEBUG] Found 0 components to load on start > [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central > [DEBUG] Found 0 components to load on start > [DEBUG] maven-surefire-plugin: resolved to version 2.0 from repository central > [DEBUG] Found 0 components to load on start > [DEBUG] org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.1 > (selected for runtime) > [DEBUG] commons-io:commons-io:jar:1.0 (selected for runtime) > [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) > [DEBUG] Skipping disabled repository snapshots > [DEBUG] Trying repository central > org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for > execution of 'resources:resources'. > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:508) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:494) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307)>> > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:439) > at > org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:383) > at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:71) > Caused by: org.apache.maven.plugin.PluginConfigurationException: Error > configuring: org.apache.maven.plugins:maven-resources-plugin. Reason: Cannot > resolve plugin dependencies > at > org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:650) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:541) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:394) > ... 8 more > Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: > Error transferring file > org.apache.maven:maven-model:2.0:jar > from the specified remote repositories: > snapshots (http://snapshots.maven.codehaus.org/maven2), > central (http://repo1.maven.org/maven2) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:150) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:64) > at > org.apache.maven.plugin.DefaultPluginManager.resolveCoreArtifacts(DefaultPluginManager.java:682) > at
[jira] Closed: (CONTINUUM-921) Edit notifier function for Ant projects doesn't have validation.
[ http://jira.codehaus.org/browse/CONTINUUM-921?page=all ] Emmanuel Venisse closed CONTINUUM-921. -- Assignee: Emmanuel Venisse (was: Maria Odea Ching) Resolution: Fixed Fix Version/s: 1.1 Apply. Thanks. > Edit notifier function for Ant projects doesn't have validation. > > > Key: CONTINUUM-921 > URL: http://jira.codehaus.org/browse/CONTINUUM-921 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Teodoro Cue Jr. > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM-921-continuum-webapp.patch > > Original Estimate: 10 hours > Time Spent: 8 hours > Remaining Estimate: 2 hours > > There are * on the textfields. Meaning, they are required. But currently, > pressing the submit button with empty strings are accepted. -- 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: (MPDIST-30) Dist plugin should take into account the javadoc properties
Dist plugin should take into account the javadoc properties --- Key: MPDIST-30 URL: http://jira.codehaus.org/browse/MPDIST-30 Project: maven-dist-plugin Issue Type: Improvement Affects Versions: 1.7.1 Environment: Win 2K, JDK 1.6 b2 Reporter: Benoit Xhenseval 1/ The consolidated javadoc does not seem to take into account any javadoc settings, nor use any default like: maven.javadoc.bottom (for copyright stuff). 2/ I also seems to complain (just warnings) that the classpath does not include reference to the dependencies jars (hence it cannot link to some imported classes, eg: [javadoc] C:\project\objectlabkit\datecalc-joda\src\main\java\net\objectlab\kit\datecalc\joda\HolidayHandlerYearMonthDayWrapper.java:23: package org.joda.time does not exist [javadoc] import org.joda.time.LocalDate; [javadoc] ^ May be it could include the dependencies by default? 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: (MPDIST-20) Support multiprojects
[ http://jira.codehaus.org/browse/MPDIST-20?page=comments#action_75201 ] Benoit Xhenseval commented on MPDIST-20: Shouldn't this be closed? Looks like the patch made it to 1.7.1 at least? > Support multiprojects > - > > Key: MPDIST-20 > URL: http://jira.codehaus.org/browse/MPDIST-20 > Project: maven-dist-plugin > Issue Type: Improvement >Reporter: Phil Steitz > Attachments: dist-plugin-2.patch, dist-plugin.patch, > dist-plugin3.patch, distPlugin4.patch > > > There is currently no way to make source and distributions for multiprojects. > It would be great if the dist plugin supported this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MEV-445) fop:fop 0.20.5 project on repo1.maven.org has inconsistenc Class-Path: and pom.xml dependencies
[ http://jira.codehaus.org/browse/MEV-445?page=all ] Carlos Sanchez moved MNG-2567 to MEV-445: - Priority: (was: Major) Environment: (was: repo1.maven.org) Affects Version/s: (was: 2.0.4) Component/s: (was: Dependencies) Dependencies Complexity: (was: Intermediate) Workflow: jira (was: Maven New) Key: MEV-445 (was: MNG-2567) Project: Maven Evangelism (was: Maven 2) > fop:fop 0.20.5 project on repo1.maven.org has inconsistenc Class-Path: and > pom.xml dependencies > --- > > Key: MEV-445 > URL: http://jira.codehaus.org/browse/MEV-445 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies >Reporter: Markus KARG > > repo1.maven.org contains the project "fop" version "0.20.5". > The pom.xml's dependencies and the main artifact's Class-Path MANIFEST.MF > entries are not in sync. > As a result, someone that has a pom.xml depending on the fop 0.20.5 project > on repo1.maven.org will end up with a broken classpath (since the JARs told > in the Class-Path: attribute are not there). > I could not find the maintainer of that project's pom.xml, so since you are > the maintainer of the complete repository, please either fix it or lookup and > inform the maintainer of the pom.xml. > I already contacted the maintainer of the "original FOP product" (Jeremias > MÄRKI), but he said that he has not provided the repo1.maven.org download for > fop and he doesn't know who provided it. > Also I have asked the maven users list who could fix it, but no one answered. > It seems that there is stuff on you repository that actually is without a > maintainer. > This situation is not acceptible, since there should be a maintainer for each > project ever. -- 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] Moved: (MEV-444) XALAN-2.4.1 is missing dependency on xercesImpl.jar in pom.xml
[ http://jira.codehaus.org/browse/MEV-444?page=all ] Carlos Sanchez moved MNG-2566 to MEV-444: - Priority: (was: Major) Environment: (was: repo1.maven.org) Affects Version/s: (was: 2.0.4) Component/s: (was: Dependencies) Dependencies Complexity: (was: Intermediate) Workflow: jira (was: Maven New) Key: MEV-444 (was: MNG-2566) Project: Maven Evangelism (was: Maven 2) > XALAN-2.4.1 is missing dependency on xercesImpl.jar in pom.xml > -- > > Key: MEV-444 > URL: http://jira.codehaus.org/browse/MEV-444 > Project: Maven Evangelism > Issue Type: Bug > Components: Dependencies >Reporter: Markus KARG > > repo1.maven.org contains the project "xalan" version "2.4.1". > The pom.xml's dependencies and the main artifact's Class-Path MANIFEST.MF > entries are not in sync. > As a result, someone that has a pom.xml depending on the xalan 2.4.1 project > on repo1.maven.org will end up with a broken classpath (since the JARs told > in the Class-Path: attribute are not there). > I could not find the maintainer of that project's pom.xml, so since you are > the maintainer of the complete repository, please either fix it or lookup and > inform the maintainer of the 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] Created: (MNG-2567) fop:fop 0.20.5 project on repo1.maven.org has inconsistenc Class-Path: and pom.xml dependencies
fop:fop 0.20.5 project on repo1.maven.org has inconsistenc Class-Path: and pom.xml dependencies --- Key: MNG-2567 URL: http://jira.codehaus.org/browse/MNG-2567 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.4 Environment: repo1.maven.org Reporter: Markus KARG repo1.maven.org contains the project "fop" version "0.20.5". The pom.xml's dependencies and the main artifact's Class-Path MANIFEST.MF entries are not in sync. As a result, someone that has a pom.xml depending on the fop 0.20.5 project on repo1.maven.org will end up with a broken classpath (since the JARs told in the Class-Path: attribute are not there). I could not find the maintainer of that project's pom.xml, so since you are the maintainer of the complete repository, please either fix it or lookup and inform the maintainer of the pom.xml. I already contacted the maintainer of the "original FOP product" (Jeremias MÄRKI), but he said that he has not provided the repo1.maven.org download for fop and he doesn't know who provided it. Also I have asked the maven users list who could fix it, but no one answered. It seems that there is stuff on you repository that actually is without a maintainer. This situation is not acceptible, since there should be a maintainer for each project ever. -- 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-2566) XALAN-2.4.1 is missing dependency on xercesImpl.jar in pom.xml
XALAN-2.4.1 is missing dependency on xercesImpl.jar in pom.xml -- Key: MNG-2566 URL: http://jira.codehaus.org/browse/MNG-2566 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.4 Environment: repo1.maven.org Reporter: Markus KARG repo1.maven.org contains the project "xalan" version "2.4.1". The pom.xml's dependencies and the main artifact's Class-Path MANIFEST.MF entries are not in sync. As a result, someone that has a pom.xml depending on the xalan 2.4.1 project on repo1.maven.org will end up with a broken classpath (since the JARs told in the Class-Path: attribute are not there). I could not find the maintainer of that project's pom.xml, so since you are the maintainer of the complete repository, please either fix it or lookup and inform the maintainer of the 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] Updated: (CONTINUUM-921) Edit notifier function for Ant projects doesn't have validation.
[ http://jira.codehaus.org/browse/CONTINUUM-921?page=all ] Maria Odea Ching updated CONTINUUM-921: --- Attachment: CONTINUUM-921-continuum-webapp.patch Attached patch that has validation for the notifier page. Thanks :) > Edit notifier function for Ant projects doesn't have validation. > > > Key: CONTINUUM-921 > URL: http://jira.codehaus.org/browse/CONTINUUM-921 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.1 >Reporter: Teodoro Cue Jr. > Assigned To: Maria Odea Ching > Attachments: CONTINUUM-921-continuum-webapp.patch > > Original Estimate: 10 hours > Time Spent: 1 hour > Remaining Estimate: 9 hours > > There are * on the textfields. Meaning, they are required. But currently, > pressing the submit button with empty strings are accepted. -- 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-19) Various encoding problems with InputStream and XML
[ http://jira.codehaus.org/browse/MSITE-19?page=comments#action_75188 ] Darius commented on MSITE-19: - When using site:run DoxiaFilter does not set any output encoding. I think it should call servletResponse.setCharacterEncoding() or servletResponse.setContentType() with output encoding that is specified in pom.xml before caling servletResponse.getWriter(). Maven 2.0.4 (bin) with maven-site-plugin-2.0-beta-5.jar. My apt files are utf-8 and I get correct html files, but in preview mode (site:run) I see "?"s. Darius > Various encoding problems with InputStream and XML > -- > > Key: MSITE-19 > URL: http://jira.codehaus.org/browse/MSITE-19 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Reporter: Naoki Nose > Fix For: 2.0 > > Attachments: plexus-i18n.diff, plexus-site-renderer.diff, > plexus-utils.diff, plexus-utils_2.diff, project-info-report_ja.properties, > project-info-report_zh_CN.properties, project-info-report_zh_CN.properties, > site-plugin_ja.properties, site-plugin_zh_CN.properties > > > There is various encoding problems with InputStream and XML in different > components. > - Property resource file is encoded with UTF-8 , but Java reads bundle with > UTF-8. > - In different components Reader is constructed with default system encoding. > - MXParser ignores encoding attribute in xml declaration. -- 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-929) The value in the Description field of the Edit User Group page is truncated until the first comma symbol
The value in the Description field of the Edit User Group page is truncated until the first comma symbol Key: CONTINUUM-929 URL: http://jira.codehaus.org/browse/CONTINUUM-929 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Environment: Linux FC4, JDK1.5, Maven 2.0.4, Jetty 6.0.0beta17 Reporter: Napoleon Esmundo C. Ramirez When adding or editing the Description field of the User Group, the value is truncated on the first occurence of the comma symbol. -- 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-893) Add a delete confirmation screen for user group
[ http://jira.codehaus.org/browse/CONTINUUM-893?page=all ] Emmanuel Venisse closed CONTINUUM-893. -- Assignee: Emmanuel Venisse (was: Marvin King) Resolution: Fixed Fix Version/s: 1.1 Applied. Thanks. > Add a delete confirmation screen for user group > --- > > Key: CONTINUUM-893 > URL: http://jira.codehaus.org/browse/CONTINUUM-893 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Reporter: Marvin King > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM893-continuum-webapp.patch > > Time Spent: 7 hours > Remaining Estimate: 0 minutes > -- 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-895) Add a delete confirmation screen for user
[ http://jira.codehaus.org/browse/CONTINUUM-895?page=all ] Emmanuel Venisse closed CONTINUUM-895. -- Assignee: Emmanuel Venisse (was: Marvin King) Resolution: Fixed Fix Version/s: 1.1 > Add a delete confirmation screen for user > - > > Key: CONTINUUM-895 > URL: http://jira.codehaus.org/browse/CONTINUUM-895 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Reporter: Marvin King > Assigned To: Emmanuel Venisse > 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] Closed: (CONTINUUM-890) passwords fields in user edition screen aren't html password fields
[ http://jira.codehaus.org/browse/CONTINUUM-890?page=all ] Emmanuel Venisse closed CONTINUUM-890. -- Assignee: Emmanuel Venisse (was: Marvin King) Resolution: Fixed Fix Version/s: 1.1 Applied. Thanks. > passwords fields in user edition screen aren't html password fields > --- > > Key: CONTINUUM-890 > URL: http://jira.codehaus.org/browse/CONTINUUM-890 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Marvin King > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM890-continuum-webapp.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-889) passwords fields in configuration screen aren't html password fields
[ http://jira.codehaus.org/browse/CONTINUUM-889?page=all ] Emmanuel Venisse closed CONTINUUM-889. -- Assignee: Emmanuel Venisse (was: Marvin King) Resolution: Fixed Fix Version/s: 1.1 Applied. Thanks > passwords fields in configuration screen aren't html password fields > > > Key: CONTINUUM-889 > URL: http://jira.codehaus.org/browse/CONTINUUM-889 > Project: Continuum > Issue Type: Bug > Components: Web interface >Reporter: Marvin King > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM889-continuum-webapp.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNGECLIPSE-189) JUnit runner does not process resource filters before running
[ http://jira.codehaus.org/browse/MNGECLIPSE-189?page=all ]
Jonathan Share updated MNGECLIPSE-189:
--
Attachment: filter-test.zip
The requested test case, sorry for the delay.
When run from the command line the test case passes due to the process-filters
target being run.
When run from the eclipse jUnit runner, with or without the m2eclipse plugin
as there is not integration with the filters provided by maven the test case
fails.
> JUnit runner does not process resource filters before running
> -
>
> Key: MNGECLIPSE-189
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-189
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
>Affects Versions: 0.0.9
> Environment: Eclipse 3.1.2 Linux
>Reporter: Jonathan Share
> Assigned To: Eugene Kuleshov
>Priority: Trivial
> Attachments: filter-test.zip
>
>
> I have a project that uses a resource filter to set the path to some files
> depending on what platform the developer is on. Using maven on the command
> line this is processed correctly and the Unit tests pass. However, I wish to
> use the JUnit runner within eclipse however as my resources do not get
> filtered before the tests try to load them I get exceptions creating URL
> objects with ${news.image.url} in them.
> Desired behaviour
> ===
> This plugin should provide a launcher for the junit runner that first runs
> the process-resources (apologies if this is wrong, writing from memory here)
> target and ensure the classpath is configured correctly so that the non
> processed resources are not available to the JUnit runner before running the
> JUnit 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] Reopened: (MNGECLIPSE-189) JUnit runner does not process resource filters before running
[ http://jira.codehaus.org/browse/MNGECLIPSE-189?page=all ]
Jonathan Share reopened MNGECLIPSE-189:
---
Sorry for the delay providing a test case, I have been ill and overloaded at
work. :-D
> JUnit runner does not process resource filters before running
> -
>
> Key: MNGECLIPSE-189
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-189
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
>Affects Versions: 0.0.9
> Environment: Eclipse 3.1.2 Linux
>Reporter: Jonathan Share
> Assigned To: Eugene Kuleshov
>Priority: Trivial
>
> I have a project that uses a resource filter to set the path to some files
> depending on what platform the developer is on. Using maven on the command
> line this is processed correctly and the Unit tests pass. However, I wish to
> use the JUnit runner within eclipse however as my resources do not get
> filtered before the tests try to load them I get exceptions creating URL
> objects with ${news.image.url} in them.
> Desired behaviour
> ===
> This plugin should provide a launcher for the junit runner that first runs
> the process-resources (apologies if this is wrong, writing from memory here)
> target and ensure the classpath is configured correctly so that the non
> processed resources are not available to the JUnit runner before running the
> JUnit 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] Closed: (CONTINUUM-862) Hide links for project group operations based on users permissions
[ http://jira.codehaus.org/browse/CONTINUUM-862?page=all ] Carlos Sanchez closed CONTINUUM-862. Resolution: Fixed > Hide links for project group operations based on users permissions > -- > > Key: CONTINUUM-862 > URL: http://jira.codehaus.org/browse/CONTINUUM-862 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Carlos Sanchez > Fix For: 1.1 > > > Permissions tab should only be visible to users with admin permission over > the group > Edit group, build group, ... links should be hidden -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-233) maven-scm-api bug in test cases
[ http://jira.codehaus.org/browse/SCM-233?page=all ] John Tolentino updated SCM-233: --- Attachment: SCM-233-maven-scm-api.diff This patch excludes the basedir from the filtered paths checked in the tests. > maven-scm-api bug in test cases > --- > > Key: SCM-233 > URL: http://jira.codehaus.org/browse/SCM-233 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-api >Affects Versions: 1.0 >Reporter: John Tolentino > Assigned To: John Tolentino > Attachments: SCM-233-maven-scm-api.diff > > > Doing a release of an application using maven-scm will create an error when > executing the tests for the maven-scm-api > When it did the checkout the source was placed into the > foo/target/foo-1.0/maven-scm-api directory and the test cases where > executed...this resulted in an error in the ScmFileSetTest which appeared to > come from the test case using */target/* in an execludes and a file not being > removed or something... perhaps because of the directory path looking like > /home/user/src/foo-trunk/target/foo-1.0/maven-scm-api/target/foo > we need to make sure that */target/* is treated right when there are two > "target" tokens in the path -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-233) maven-scm-api bug in test cases
maven-scm-api bug in test cases --- Key: SCM-233 URL: http://jira.codehaus.org/browse/SCM-233 Project: Maven SCM Issue Type: Bug Components: maven-scm-api Affects Versions: 1.0 Reporter: John Tolentino Doing a release of an application using maven-scm will create an error when executing the tests for the maven-scm-api When it did the checkout the source was placed into the foo/target/foo-1.0/maven-scm-api directory and the test cases where executed...this resulted in an error in the ScmFileSetTest which appeared to come from the test case using */target/* in an execludes and a file not being removed or something... perhaps because of the directory path looking like /home/user/src/foo-trunk/target/foo-1.0/maven-scm-api/target/foo we need to make sure that */target/* is treated right when there are two "target" tokens in the path -- 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-862) Hide links for project group operations based on users permissions
[ http://jira.codehaus.org/browse/CONTINUUM-862?page=comments#action_75171 ] Carlos Sanchez commented on CONTINUUM-862: -- actually it's not projectGroupSummary but projectsummarycomponent > Hide links for project group operations based on users permissions > -- > > Key: CONTINUUM-862 > URL: http://jira.codehaus.org/browse/CONTINUUM-862 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Carlos Sanchez > Fix For: 1.1 > > > Permissions tab should only be visible to users with admin permission over > the group > Edit group, build group, ... links should be hidden -- 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
