[jira] Created: (MRELEASE-403) Release plugin ignores given version number
Release plugin ignores given version number --- Key: MRELEASE-403 URL: http://jira.codehaus.org/browse/MRELEASE-403 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Environment: Maven version: 2.0.9 Java version: 1.6.0_10 OS name: linux version: 2.6.27-9-generic arch: amd64 Family: unix Reporter: Kurt Huwig When asked for the release version I answer 1.0.0: What is the release version for Kern scale library? (de.scooterattack:kern) 1.0: : 1.0.0 but the resulting release.properties contains 1.0 instead: #release configuration #Tue Jan 06 09:12:57 CET 2009 scm.tag=kern-1.0 scm.url=scm\:svn\:http\://svn.it.lan/java/trunk/kern preparationGoals=clean verify scm.commentPrefix=[maven-release-plugin] project.scm.de.scooterattack\:kern.empty=true exec.additionalArguments=-P Repository_Proxy,gwt-1.5.3,maven-hybris-plugin,maven-ant-tasks,hybris-3.0-u2,Repository_Proxy project.dev.de.scooterattack\:kern=1.1-SNAPSHOT completedPhase=end-release project.rel.de.scooterattack\:kern=1.0 This was working some months ago when I made the previous release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MINSTALL-28) Error in Project Attempting to Use maven-install-plugin with 'lib' Packaging
[
http://jira.codehaus.org/browse/MINSTALL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINSTALL-28.
-
Assignee: Benjamin Bentmann
Resolution: Not A Bug
Yep, this appears to be beyond the scope of the Install Plugin itself. A
packaging can't be chosen at will but must have been registered with the core
(via extensions). So this more a configuration/best practice issue to be solved
by the [user list|http://maven.apache.org/mail-lists.html].
Error in Project Attempting to Use maven-install-plugin with 'lib' Packaging
Key: MINSTALL-28
URL: http://jira.codehaus.org/browse/MINSTALL-28
Project: Maven 2.x Install Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: Win2003, running mvn 2.04 in Cygwin bash shell
Locally built version maven-install-plugin 2.2-SNAPSHOT
Reporter: Brad Harper
Assignee: Benjamin Bentmann
I'm using M2 'maven-native-plugin' to build C++ libraries and apps. Within the
overall project structure I have a module to handle a set of 3rd-party
(library) artifacts. Some of these are native libraries (without source) and
some are
built from open source.
I'd like to run
% mvn install
in the 3rd-party module and have the pre-built libraries simply copied
into the local repository with an /artifactId that can be expressed in
the /dependencyManagement part elsewhere.
The POM descriptor for one of these native library sub-modules contains
{code:xml}
packaginglib/packaging
build
plugins
plugin
artifactIdmaven-install-plugin/artifactId
executions
execution
idinstall-library/id
phaseinstall/phase
configuration
groupIdcom-epsiia-dxr-third-party/groupId
artifactIddxr-third-party-com-emc-centera-fplibrary-WINDOWS-X86/artifactId
version2.0SP1/version
packaginglib/packaging
fileFPLibrary.lib/file
/configuration
/execution
/executions
/plugin
/plugins
/build
{code}
but maven complains
{noformat}
[ERROR] BUILD ERROR
[INFO]
[INFO] Cannot find lifecycle mapping for packaging: 'lib'
Component descriptor cannot be found in the component repository:
org.apache.maven.lifecyle.mapping.LifecycleMappinglib.
{noformat}
The 'maven-native-plugin' is supplied by codehaus.org and the plugin's
use is declared in an ancestor POM descriptor. In modules where C++
source is compiled/linked, the 'install' goal moves the resulting
artifact into the repository.
Shouldn't this work?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3956) Maven unable to find the child modules
[
http://jira.codehaus.org/browse/MNG-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Kumar Patil updated MNG-3956:
Attachment: pom.xml
pom.xml
Hi,
I have attached both the POM. Please can you have a look.
Cheers,
Sanjay Patil
Maven unable to find the child modules
--
Key: MNG-3956
URL: http://jira.codehaus.org/browse/MNG-3956
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Windows XP, Maven 2.0.9
Reporter: Sanjay Kumar Patil
Priority: Blocker
Fix For: 2.0.x
Attachments: mng-3956.zip, pom.xml, pom.xml
Hi, Please can you assist me here.
I am using Maven 2.0.9. I have created a parent project for one of my Java
project and was trying to run mvn compile cmd from the parent level
but it fails. This is what i have declared in my parent POM.
{code:xml}
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdcom.johnlewis.jjs/groupId
artifactIdjlp_jjs_jjs2core-parent/artifactId
packagingpom/packaging
name/
version0.0.1-SNAPSHOT/version
description/
modules
module../jlp_jjs_jjs2core/module
/modules
/project
{code}
The error message is
{noformat}
+ Error stacktraces are turned on.
Maven version: 2.0.9
Java version: 1.5.0
OS name: windows xp version: 5.1 build 2600 service pack 2 arch: x86
Family: dos
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\tso005\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program
Files\Maven\apache-maven-2.0.9\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[DEBUG] Trace
java.lang.StackOverflowError
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:957)
at
java.security.AccessController.doPrivileged(AccessController.java:275)
at java.net.URLClassLoader.findClass(URLClassLoader.java:487)
at java.lang.ClassLoader.loadClass(ClassLoader.java:603)
at java.lang.ClassLoader.loadClass(ClassLoader.java:595)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:569)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:243)
at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:30)
at
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupList(DefaultPlexusContainer.java:423)
at
org.apache.maven.profiles.DefaultProfileManager.isActive(DefaultProfileManager.java:260)
at
org.apache.maven.profiles.DefaultProfileManager.getActiveProfiles(DefaultProfileManager.java:209)
at
org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfiles(DefaultMavenProjectBuilder.java:1478)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:761)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
[...]
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
at
[jira] Reopened: (MNG-3821) [regression] Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets
[
http://jira.codehaus.org/browse/MNG-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann reopened MNG-3821:
Not sure why this was marked fixed but the corresponding IT is still failing,
both with the staged 3.0-alpha-1 and the SVN head.
[regression] Project builder blows up when POM declares two plugins which use
the same id for their executions/reportsets
-
Key: MNG-3821
URL: http://jira.codehaus.org/browse/MNG-3821
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle, POM
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Shane Isbell
Fix For: 3.0-alpha-1
Running the core IT 2695 with trunk delivered:
{noformat}
java.io.IOException:
org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name
/plugin must match start t
ag name executions from line 43 (position: START_TAG seen
...executions/plugin... @43:22) :
[...]
at
org.apache.maven.project.builder.PomClassicTransformer.transformToDomainModel(PomClassicTransformer.java:237)
at
org.apache.maven.shared.model.ModelTransformerContext.transform(ModelTransformerContext.java:286)
at
org.apache.maven.project.builder.impl.DefaultProjectBuilder.buildFromLocalPath(DefaultProjectBuilder.java:176)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModelFromLocalPath(DefaultMavenProjectBuilder.java:544)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:132)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:286)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:256)
at
org.apache.maven.DefaultMaven.createReactorManager(DefaultMaven.java:93)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:147)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:854)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
[ERROR]
Failed to build MavenProject instance for:
M:\maven\core-it\core-it-suite\src\test\resources\mng-2695\pom.xml
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3821) [regression] Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets
[
http://jira.codehaus.org/browse/MNG-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-3821:
---
Fix Version/s: (was: 3.0-alpha-1)
3.0-alpha-2
[regression] Project builder blows up when POM declares two plugins which use
the same id for their executions/reportsets
-
Key: MNG-3821
URL: http://jira.codehaus.org/browse/MNG-3821
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle, POM
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
Running the core IT 2695 with trunk delivered:
{noformat}
java.io.IOException:
org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name
/plugin must match start t
ag name executions from line 43 (position: START_TAG seen
...executions/plugin... @43:22) :
[...]
at
org.apache.maven.project.builder.PomClassicTransformer.transformToDomainModel(PomClassicTransformer.java:237)
at
org.apache.maven.shared.model.ModelTransformerContext.transform(ModelTransformerContext.java:286)
at
org.apache.maven.project.builder.impl.DefaultProjectBuilder.buildFromLocalPath(DefaultProjectBuilder.java:176)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModelFromLocalPath(DefaultMavenProjectBuilder.java:544)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:132)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:286)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:256)
at
org.apache.maven.DefaultMaven.createReactorManager(DefaultMaven.java:93)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:147)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:854)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
[ERROR]
Failed to build MavenProject instance for:
M:\maven\core-it\core-it-suite\src\test\resources\mng-2695\pom.xml
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-3821) [regression] Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets
[
http://jira.codehaus.org/browse/MNG-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160074#action_160074
]
Benjamin Bentmann edited comment on MNG-3821 at 1/6/09 4:39 AM:
Not sure why this was marked fixed but the corresponding IT MNG-3821 is still
failing, both with the staged 3.0-alpha-1 and the SVN head.
was (Author: bentmann):
Not sure why this was marked fixed but the corresponding IT is still
failing, both with the staged 3.0-alpha-1 and the SVN head.
[regression] Project builder blows up when POM declares two plugins which use
the same id for their executions/reportsets
-
Key: MNG-3821
URL: http://jira.codehaus.org/browse/MNG-3821
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle, POM
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
Running the core IT 2695 with trunk delivered:
{noformat}
java.io.IOException:
org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name
/plugin must match start t
ag name executions from line 43 (position: START_TAG seen
...executions/plugin... @43:22) :
[...]
at
org.apache.maven.project.builder.PomClassicTransformer.transformToDomainModel(PomClassicTransformer.java:237)
at
org.apache.maven.shared.model.ModelTransformerContext.transform(ModelTransformerContext.java:286)
at
org.apache.maven.project.builder.impl.DefaultProjectBuilder.buildFromLocalPath(DefaultProjectBuilder.java:176)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModelFromLocalPath(DefaultMavenProjectBuilder.java:544)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:132)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:286)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:256)
at
org.apache.maven.DefaultMaven.createReactorManager(DefaultMaven.java:93)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:147)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:854)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
[ERROR]
Failed to build MavenProject instance for:
M:\maven\core-it\core-it-suite\src\test\resources\mng-2695\pom.xml
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-3970) [regression] Repositories injected by profiles are not used for dependency resolution
[regression] Repositories injected by profiles are not used for dependency
resolution
-
Key: MNG-3970
URL: http://jira.codehaus.org/browse/MNG-3970
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories, Profiles
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Priority: Minor
{code:xml}
profile
idprofile/id
!-- to be activated explicitly on the CLI by its id --
repositories
repository
idmaven-core-it/id
urlfile:///${basedir}/repo/url
releases
checksumPolicyignore/checksumPolicy
/releases
snapshots
checksumPolicyignore/checksumPolicy
/snapshots
/repository
/repositories
/profile
{code}
dependencies from the above repo are not resolvable even if the profile is
active.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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: (WAGON-254) wagon-ftp :: error uploading site:: too many open files
[ http://jira.codehaus.org/browse/WAGON-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160083#action_160083 ] Richard Gomes commented on WAGON-254: - For whomever interested When running from command line: --- I've circumvented the problem by defining 2 roles: developers and managers. Developers execute mvn clean integration-test whilst managers execute mvn -Drole=manager clean site-deploy, I mean: only managers are intended to deploy artifacts and/or generate the documentation website. When profile manager is selected... * Maven 2.1.0-M1 is required instead of Maven 2.0.9 * Newer versions of extensions are loaded, requiring Maven 2.1.0-M1 * .m2/settings.xml must define username/password for deployment When running inside Eclipse: -- For some reason, external installation of Maven-2.0.9 was still giving problems. I really dont understand why I reverted to Embeded installation and now it does not complain anymore. See also: https://jquant.svn.sourceforge.net/svnroot/jquant/trunk/jquantlib/pom.xml (SVN revision 641) http://jira.codehaus.org/browse/MNGECLIPSE-684 Cheers Richard Gomes wagon-ftp :: error uploading site:: too many open files --- Key: WAGON-254 URL: http://jira.codehaus.org/browse/WAGON-254 Project: Maven Wagon Issue Type: Bug Affects Versions: 1.0-beta-4 Environment: Maven version: 2.1.0-M1 Java version: 1.6.0_10-rc2 Default locale: en_GB, platform encoding: UTF-8 OS name: linux version: 2.6.26-1-amd64 arch: amd64 family: unix Reporter: Richard Gomes Assignee: Dan Tran Priority: Minor Fix For: 1.0-beta-5 Attachments: wagon-ftp_too-many-open-files.tar.bz2 A complete log file is attached. Below you can see the stack trace: [INFO] Error uploading site Embedded error: IOException caught while attempting to upload /home/rgomes/workspace/jquantlib/target/site/testapidocs/org/jquantlib/testsuite/math/distributions/InverseCumulativeNormalTest.dot Too many open files [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading site at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:701) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:538) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:369) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site at org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:203) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:676) ... 16 more Caused by: org.apache.maven.wagon.TransferFailedException: IOException caught while attempting to upload /home/rgomes/workspace/jquantlib/target/site/testapidocs/org/jquantlib/testsuite/math/distributions/InverseCumulativeNormalTest.dot at org.apache.maven.wagon.providers.ftp.FtpWagon.ftpRecursivePut(FtpWagon.java:639) at org.apache.maven.wagon.providers.ftp.FtpWagon.ftpRecursivePut(FtpWagon.java:580) at org.apache.maven.wagon.providers.ftp.FtpWagon.ftpRecursivePut(FtpWagon.java:573)
[jira] Commented: (MNG-3956) Maven unable to find the child modules
[ http://jira.codehaus.org/browse/MNG-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160085#action_160085 ] Sanjay Kumar Patil commented on MNG-3956: - Hi Benjamin, I have fixed this problem but I dont know the reason for it. Thing is that my child module artifact id was same as parent POM project name and thats why it was going in loop. I gave a different name today and it started working. Now I have come across another error while running mvn site command from the parent POM. I fails with the below error. [DEBUG] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [DEBUG] Setting property: site.resource.loader.class = 'org.codehaus.plexus.velocity.SiteResourceLoader'. [DEBUG] Setting property: velocimacro.messages.on = 'false'. [DEBUG] Setting property: resource.loader = 'classpath,site'. [DEBUG] Setting property: runtime.log.invalid.references = 'false'. [DEBUG] Setting property: resource.manager.logwhenfound = 'false'. [DEBUG] Setting property: velocimacro.permissions.allow.inline.to.replace.global = 'true'. [DEBUG] *** [DEBUG] Starting Apache Velocity v1.5 (compiled: 2007-02-22 08:52:29) [DEBUG] RuntimeInstance initializing. [DEBUG] Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties [DEBUG] LogSystem has been deprecated. Please use a LogChute implementation. [DEBUG] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [DEBUG] ResourceLoader instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [DEBUG] ResourceLoader instantiated: org.codehaus.plexus.velocity.SiteResourceLoader [DEBUG] ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) [DEBUG] Default ResourceManager initialization complete. [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Include [DEBUG] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [DEBUG] Created '20' parsers. [DEBUG] Velocimacro : initialization starting. [DEBUG] Velocimacro : allowInline = true : VMs can be defined inline in templates [DEBUG] Velocimacro : allowInlineToOverride = true : VMs defined inline may replace previous VM definitions [DEBUG] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [DEBUG] Velocimacro : autoload off : VM system will not automatically reload global library macros [DEBUG] Velocimacro : Velocimacro : initialization complete. [DEBUG] RuntimeInstance successfully initialized. [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site' -- [DEBUG] (f) generateReports = true [DEBUG] (f) generatedSiteDirectory = C:\Work\IDE\workspace\tso005\jlp_jjs_JJS2Core~SP\jlp_jjs_JJS2Core_Java\target\generated-site [DEBUG] (f) inputEncoding = ISO-8859-1 [DEBUG] (f) localRepository = [local] - file://c:\work\mavenrepository2 [DEBUG] (f) outputDirectory = C:\Work\IDE\workspace\tso005\jlp_jjs_JJS2Core~SP\jlp_jjs_JJS2Core_Java\target\site [DEBUG] (f) outputEncoding = ISO-8859-1 [DEBUG] (f) project = MavenProject: com.johnlewis.jjs:jlp_jjs_jjs2core_Java:0.0.1-SNAPSHOT @ C:\Work\IDE\workspace\tso005\jlp_jjs_JJS2Core~SP\jlp_jjs_JJS2Core_Java\pom.xml [DEBUG] (f) reactorProjects = [MavenProject: com.johnlewis.jjs:jlp_jjs_jjs2core_Java:0.0.1-SNAPSHOT @ C:\Work\IDE\workspace\tso005\jlp_jjs_JJS2Core~SP\jlp_jjs_JJS2Core_Java\pom.xml, MavenProject: com.johnlewis.jjs:jlp_jjs_jjs2core-parent:0.0.1-SNAPSHOT @ C:\Work\IDE\workspace\tso005\jlp_jjs_JJS2Core~SP\jlp_jjs_JJS2Core\pom.xml] [DEBUG] (f) reports = [org.apache.maven.plugin.checkstyle.checkstylerep...@2a222a22, org.codehaus.mojo.cobertura.coberturareportm...@781a781a, org.codehaus.mojo.findbugs.findbugsm...@426a426a, org.codehaus.mojo.jdepend.jdependm...@5e505e50, org.apache.maven.report.projectinfo.cimrep...@27f827f8, org.apache.maven.report.projectinfo.dependenciesrep...@62b662b6, org.apache.maven.report.projectinfo.dependencyconvergencerep...@6500650, org.apache.maven.report.projectinfo.issuetrackingrep...@27642764, org.apache.maven.report.projectinfo.licenserep...@b540b54, org.apache.maven.report.projectinfo.mailinglistsrep...@6e586e58, org.apache.maven.report.projectinfo.projectindexpagerep...@22dc22dc, org.apache.maven.report.projectinfo.projectsummaryrep...@a640a64, org.apache.maven.report.projectinfo.scmrep...@271c271c, org.apache.maven.report.projectinfo.teamlistrep...@32743274] [DEBUG] (f) repositories = [[central] - http://repo1.maven.org/maven2] [DEBUG]
[jira] Commented: (MNG-3956) Maven unable to find the child modules
[
http://jira.codehaus.org/browse/MNG-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160087#action_160087
]
Benjamin Bentmann commented on MNG-3956:
Make sure that your copy of
{{org/apache/maven/skins/maven-default-skin/maven-metadata-central.xml}} in
your local repo matches the [official remote
copy|http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml]
or delete the file's parent directory to have Maven redownload it. Also, try
to add the flag -U to your command line to force a re-check of the metadata.
Your skin issue is likely a duplicate of MNG-3139.
Maven unable to find the child modules
--
Key: MNG-3956
URL: http://jira.codehaus.org/browse/MNG-3956
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Windows XP, Maven 2.0.9
Reporter: Sanjay Kumar Patil
Priority: Blocker
Fix For: 2.0.x
Attachments: mng-3956.zip, mng-3956.zip, pom.xml, pom.xml,
sandebug.log
Hi, Please can you assist me here.
I am using Maven 2.0.9. I have created a parent project for one of my Java
project and was trying to run mvn compile cmd from the parent level
but it fails. This is what i have declared in my parent POM.
{code:xml}
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdcom.johnlewis.jjs/groupId
artifactIdjlp_jjs_jjs2core-parent/artifactId
packagingpom/packaging
name/
version0.0.1-SNAPSHOT/version
description/
modules
module../jlp_jjs_jjs2core/module
/modules
/project
{code}
The error message is
{noformat}
+ Error stacktraces are turned on.
Maven version: 2.0.9
Java version: 1.5.0
OS name: windows xp version: 5.1 build 2600 service pack 2 arch: x86
Family: dos
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\tso005\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program
Files\Maven\apache-maven-2.0.9\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[DEBUG] Trace
java.lang.StackOverflowError
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:957)
at
java.security.AccessController.doPrivileged(AccessController.java:275)
at java.net.URLClassLoader.findClass(URLClassLoader.java:487)
at java.lang.ClassLoader.loadClass(ClassLoader.java:603)
at java.lang.ClassLoader.loadClass(ClassLoader.java:595)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:569)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:243)
at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:30)
at
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupList(DefaultPlexusContainer.java:423)
at
org.apache.maven.profiles.DefaultProfileManager.isActive(DefaultProfileManager.java:260)
at
org.apache.maven.profiles.DefaultProfileManager.getActiveProfiles(DefaultProfileManager.java:209)
at
org.apache.maven.project.DefaultMavenProjectBuilder.injectActiveProfiles(DefaultMavenProjectBuilder.java:1478)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:761)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at
[jira] Work started: (MNG-3938) [regression] Plugin executions with default id are not always merged
[
http://jira.codehaus.org/browse/MNG-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MNG-3938 started by Shane Isbell.
[regression] Plugin executions with default id are not always merged
Key: MNG-3938
URL: http://jira.codehaus.org/browse/MNG-3938
Project: Maven 2
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Shane Isbell
Priority: Minor
Fix For: 3.0-alpha-2
Plugin executions using the default id are not merged during inheritance if
a) the parent POM defines the plugin via plugin management
b) the parent POM omits the {{id}} for the plugin execution
c) the child POM uses {{iddefault/id}} for the plugin execution
This causes Maven 3.x to fail with a validation error (duplicate execution
ids)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3971) Provide parity in features between native ant-mojo support and antrun plugin
Provide parity in features between native ant-mojo support and antrun plugin Key: MNG-3971 URL: http://jira.codehaus.org/browse/MNG-3971 Project: Maven 2 Issue Type: Improvement Components: Plugin API, Plugins and Lifecycle Affects Versions: 2.1.0-M1, 2.0.9 Reporter: John Casey In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven. The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3886) [regression] Ordering of goals from a plugin execution is not respected if plugin management applies
[
http://jira.codehaus.org/browse/MNG-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160099#action_160099
]
Shane Isbell commented on MNG-3886:
---
Plugin Management is applied after all the other inheritance rules and reverse
the order. Planning on adding support in model builder to handle the correct
ordering in these cases.
[regression] Ordering of goals from a plugin execution is not respected if
plugin management applies
Key: MNG-3886
URL: http://jira.codehaus.org/browse/MNG-3886
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.0-alpha-1
Reporter: Benjamin Bentmann
Assignee: Shane Isbell
Priority: Minor
Fix For: 3.0-alpha-3
For a POM snippet like
{code:xml}
execution
idtest/id
phasevalidate/phase
goals
goalone/goal
goaltwo/goal
/goals
/execution
{code}
the effective execution order of the specified goals is either [one, two] or
[two, one] depending on the existence of {{pluginManagement}} for the
plugin in question.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-3971) Provide parity in features between native ant-mojo support and antrun plugin
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160102#action_160102 ] John Casey commented on MNG-3971: - Probably the simplest way to inject classpaths is to mod the plugin tools that create the plugin descriptors for ant-mojos, injecting these as parameters...then, also modding the plugin support to actually do the injection using information that can be gleaned from Project, etc. information. Provide parity in features between native ant-mojo support and antrun plugin Key: MNG-3971 URL: http://jira.codehaus.org/browse/MNG-3971 Project: Maven 2 Issue Type: Improvement Components: Plugin API, Plugins and Lifecycle Affects Versions: 2.0.9, 2.1.0-M1 Reporter: John Casey Assignee: John Casey Fix For: 2.1.0-M2 In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven. The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3901) Merge all project building code into a single component
[ http://jira.codehaus.org/browse/MNG-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160103#action_160103 ] Shane Isbell commented on MNG-3901: --- Path translator is used by at least one of the plugins. That is why it is still there. project-builder is used by mercury, as this component has limited dependencies on trunk. maven-project, which extends project-builder has modello dependencies and a few other maven specific ones. We need to figure out that part. Merge all project building code into a single component --- Key: MNG-3901 URL: http://jira.codehaus.org/browse/MNG-3901 Project: Maven 2 Issue Type: Task Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.0-alpha-3 Right now we have the new project builder being used by the old project builder code. We need to collapse everything into the one new component and remove all dead components. I can see that the pathTranslator isn't being used any more. There are probably references to some other dead bits that need to be cleaned up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3972) core-it-plugins fails to build when using maven trunk
core-it-plugins fails to build when using maven trunk - Key: MNG-3972 URL: http://jira.codehaus.org/browse/MNG-3972 Project: Maven 2 Issue Type: Bug Components: General Affects Versions: 3.0-alpha-2 Reporter: Shane Isbell Priority: Minor core-it-plugins fails to build when using maven trunk: java.lang.NoClassDefFoundError: org.codehaus.plexus.personality.plexus.lifecycle.phase.Suspendable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160110#action_160110
]
Shane Isbell commented on MNG-3856:
---
The ${maven.version} interpolation is tricky. There are deployed poms in the
repo that have this property. If we specify a default ${maven.version} property
as 3.x, it may blow up on class not found exceptions. There is no way to know
what the intended version is supposed to be.
We should consider restricting from allowing this value to pass through
un-interpolated prior to deploy.
Fix interpolation to correctly treat all interpolated variables
---
Key: MNG-3856
URL: http://jira.codehaus.org/browse/MNG-3856
Project: Maven 2
Issue Type: Bug
Reporter: Oleg Gusakov
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
There are several dependencies that have non-replaced variables, coming from
maven-mercury implementation:
{code}
== org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar ==
org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
== org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
== org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
== org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
== org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.5::jar ==
org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
== org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2323) Upload of FDS-API 1.04
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2323. --- Assignee: Carlos Sanchez Resolution: Fixed Upload of FDS-API 1.04 -- Key: MAVENUPLOAD-2323 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2323 Project: Maven Upload Requests Issue Type: Wish Reporter: Edouard Hue Assignee: Carlos Sanchez Attachments: fdsapi-1.0.4-bundle.jar This is not a Maven project. The author (Steve Souza) isn't currently intersted in migrating fdsapi to Maven. This bundle was generated from the 1_04 release available at http://sourceforge.net/project/showfiles.php?group_id=87044package_id=90549release_id=317647 using the repository plugin. Thanks for uploading ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2314) Upload hibernate tools 3.2.3.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2314. --- Assignee: Carlos Sanchez Resolution: Fixed Upload hibernate tools 3.2.3.GA --- Key: MAVENUPLOAD-2314 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2314 Project: Maven Upload Requests Issue Type: Wish Reporter: David J. M. Karlsen Assignee: Carlos Sanchez Please upload hibernate tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160121#action_160121
]
Oleg Gusakov commented on MNG-3856:
---
It really depends on the intent:
* exact version, like 3.0-alpha-1-SNAPSHOT
* family version, like 3.0
I propose to interpret as family version - 3.0, or 3.1
If a plugin depends on the exact version - there is something wrong.
Fix interpolation to correctly treat all interpolated variables
---
Key: MNG-3856
URL: http://jira.codehaus.org/browse/MNG-3856
Project: Maven 2
Issue Type: Bug
Reporter: Oleg Gusakov
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
There are several dependencies that have non-replaced variables, coming from
maven-mercury implementation:
{code}
== org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar ==
org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
== org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
== org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
== org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
== org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.5::jar ==
org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
== org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160122#action_160122
]
Benjamin Bentmann commented on MNG-3856:
I don't see Maven 2.x interpolating {{${maven.version}}} unless explicitly
provided by the user/POM, so why should Maven 3.x by providing any default
value?
Fix interpolation to correctly treat all interpolated variables
---
Key: MNG-3856
URL: http://jira.codehaus.org/browse/MNG-3856
Project: Maven 2
Issue Type: Bug
Reporter: Oleg Gusakov
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
There are several dependencies that have non-replaced variables, coming from
maven-mercury implementation:
{code}
== org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar ==
org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
== org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
== org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
== org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
== org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.5::jar ==
org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
== org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160123#action_160123
]
Oleg Gusakov commented on MNG-3856:
---
Good point - if it was not in 2.x, then we should not add it
Fix interpolation to correctly treat all interpolated variables
---
Key: MNG-3856
URL: http://jira.codehaus.org/browse/MNG-3856
Project: Maven 2
Issue Type: Bug
Reporter: Oleg Gusakov
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
There are several dependencies that have non-replaced variables, coming from
maven-mercury implementation:
{code}
== org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar ==
org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
== org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
== org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
== org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
== org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.5::jar ==
org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
== org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160131#action_160131
]
Oleg Gusakov commented on MNG-3856:
---
I re-ran it with 3.0-alpha-1, still the same:
although maven.version property is defined in the pom file
*maven-dependency-plugin-2.0.pom*, maven-mercury returns non-substituted
dependency:
{code}
did not find non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
{code}
Fix interpolation to correctly treat all interpolated variables
---
Key: MNG-3856
URL: http://jira.codehaus.org/browse/MNG-3856
Project: Maven 2
Issue Type: Bug
Reporter: Oleg Gusakov
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
There are several dependencies that have non-replaced variables, coming from
maven-mercury implementation:
{code}
== org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar ==
org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
== org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
== org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
== org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
== org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.5::jar ==
org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
== org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2309) Uploading XmlTask jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2309. --- Assignee: Carlos Sanchez Resolution: Incomplete Uploading XmlTask jar - Key: MAVENUPLOAD-2309 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2309 Project: Maven Upload Requests Issue Type: Wish Reporter: Sathish Kumar Assignee: Carlos Sanchez Hi, I want to use XmlTask in my project. But this jar is not available in the repo1.maven.org (or) mavenrepository.com. Pls, upload the XmlTask 1.14 version of jar to these repositories. Thanks, P.Sathish Kumar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2274) Docbook (net.sf.docbook) upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2274. --- Assignee: Carlos Sanchez Resolution: Fixed Added sync and relocation from old groups to new one Docbook (net.sf.docbook) upload --- Key: MAVENUPLOAD-2274 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2274 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Pronzato Assignee: Carlos Sanchez Hello, I am developer in the docbook project and I would like to deploy the following bundles on maven central repository: - http://docbook.sourceforge.net/maven/dist/docbook-5.0-bundle.jar - http://docbook.sourceforge.net/maven/dist/docbook-xml-5.0-bundle.jar - http://docbook.sourceforge.net/maven/dist/docbook-xsl-1.74.0-bundle.jar - http://docbook.sourceforge.net/maven/dist/docbook-xsl-saxon-1.0.0-bundle.jar - http://docbook.sourceforge.net/maven/dist/docbook-xsl-xalan-1.0.0-bundle.jar Here are some other informations: - groupId: net.sf.docbook - my developer nick name is mimil and is listed in the given contributor url - The bundles have been made using the jar command because most of my artifacts are pom package type and it sounds to not be compatible with the repository:bundle-create plugin. - docbook-5.0-bundle.jar is the parent pom and then do not contains artifact Regards, Mimil -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2310) New version of XINS for Maven2 repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2310. --- Assignee: Carlos Sanchez Resolution: Fixed New version of XINS for Maven2 repository - Key: MAVENUPLOAD-2310 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2310 Project: Maven Upload Requests Issue Type: Task Reporter: Anthony Goubard Assignee: Carlos Sanchez Hi, Here are new JAR file that I'd like to have uploaded in Maven: http://xins.sourceforge.net/maven/xins-server-2.2.jar http://xins.sourceforge.net/maven/xins-common-2.2.jar http://xins.sourceforge.net/maven/xins-client-2.2.jar http://xins.sourceforge.net/maven/logdoc-2.2.jar Kind regards, Anthony -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2315) Jericho HTML Parser 2.6.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2315. --- Assignee: Carlos Sanchez Resolution: Fixed Jericho HTML Parser 2.6.1 - Key: MAVENUPLOAD-2315 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2315 Project: Maven Upload Requests Issue Type: Task Reporter: Martin Jericho Assignee: Carlos Sanchez Jericho HTML Parser is a java library allowing analysis and manipulation of parts of an HTML document, including server-side tags, while reproducing verbatim any unrecognised or invalid HTML. It also provides high-level HTML form manipulation functions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2299) FitNesse and FitLibrary 20081201
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160136#action_160136 ] Carlos Sanchez commented on MAVENUPLOAD-2299: - jar xf fitlibrary-20081201-bundle.jar java.util.zip.ZipException: invalid entry size (expected 534330 but got 579392 bytes) at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:368) at java.util.zip.ZipInputStream.read(ZipInputStream.java:141) at sun.tools.jar.Main.extractFile(Main.java:714) at sun.tools.jar.Main.extract(Main.java:677) at sun.tools.jar.Main.run(Main.java:189) at sun.tools.jar.Main.main(Main.java:903) FitNesse and FitLibrary 20081201 Key: MAVENUPLOAD-2299 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2299 Project: Maven Upload Requests Issue Type: Wish Reporter: Pål Brattberg FitNesse is a fully integrated standalone wiki and acceptance testing framework using FIT. FitLibrary is an extension for FIT/FitNesse I'm not a developer of FitNesse, but I am for DbFit and WebTestFixtures which are dependant on FitNesse. The official JAR's are found at: http://www.fitnesse.org/FitNesse.DownLoad The JAR's packaged for Maven (with POM) are found at: http://julafton.com/fitnesse/fitnesse-20081201-bundle.jar http://julafton.com/fitnesse/fitlibrary-20081201-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2316) Simplestuff project : released 0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2316. --- Assignee: Carlos Sanchez Resolution: Fixed Simplestuff project : released 0.4 -- Key: MAVENUPLOAD-2316 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2316 Project: Maven Upload Requests Issue Type: Wish Reporter: Vincenzo Vitale Assignee: Carlos Sanchez Attachments: simplestuff-0.4-bundle.jar New release (0.4) of the SimpleStuff project You can see my name here: http://code.google.com/p/simplestuff/ Here the description of the first component included in SimpleStuff: http://code.google.com/p/simplestuff/wiki/SimpleBean -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2317) Upload oval-1.31
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160137#action_160137 ] Carlos Sanchez commented on MAVENUPLOAD-2317: - you need to remove the repositories and pluginrepositories sections from the pom Upload oval-1.31 Key: MAVENUPLOAD-2317 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2317 Project: Maven Upload Requests Issue Type: Task Reporter: Sebastian T OVal is a pragmatic and extensible validation framework for any kind of Java objects (not only JavaBeans). Constraints can be configured with annotations, POJOs or XML. Custom constraints can be expressed in pure Java or by using scripting languages such as JavaScript, Groovy, BeanShell, OGNL, MVEL or Ruby. Besides simple object validation OVal implements Programming by Contract features by utilizing AspectJ based aspects. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html Thanks in advance! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2311) Add jnex to maven 2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2311. --- Assignee: Carlos Sanchez Resolution: Fixed Add jnex to maven 2 --- Key: MAVENUPLOAD-2311 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2311 Project: Maven Upload Requests Issue Type: Wish Reporter: Marcel Baumann Assignee: Carlos Sanchez com.nexirius,nexir...@web.sourceforge.net:/home/users/n/ne/nexirius/htdocs/m2repo/jnex/jnex4.3,rsync_ssh,Marcel Baumann,marcel.baum...@nexirius.ch,, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2318) Upload easystream library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160138#action_160138 ] Carlos Sanchez commented on MAVENUPLOAD-2318: - you need to provide the parent pom too in a separate bundle (or easier setup an automatic synchronized repository) Upload easystream library - Key: MAVENUPLOAD-2318 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2318 Project: Maven Upload Requests Issue Type: Wish Reporter: Davide Simonetti http://io-tools.googlecode.com/files/easystream-1.1-bundle.jar http://code.google.com/p/io-tools/ Hi! i'm the owner of the project io-tools, can you please upload the artifact easystream ? The project owner (me) is listed in the right bar of the home page, near the bottom line. My email is dvd.s...@gmail.com contact me for any problem or question. Best regards. Davide Simonetti -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2303) please add to repo1 for automatic syncing
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160139#action_160139 ] Carlos Sanchez commented on MAVENUPLOAD-2303: - and which remote directory is it supposed to be? please add to repo1 for automatic syncing - Key: MAVENUPLOAD-2303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2303 Project: Maven Upload Requests Issue Type: Wish Reporter: jay colson Assignee: Carlos Sanchez org.synchronoss,sncrbu...@shell.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases,rsync_ssh,Jay Colson,jcol...@users.sourceforge.net,, Proof of domain ownership: jay.col...@synchronoss.com (synchronoss.org redrects to .com) maven public key has already been added to the sf user sncrbuild -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2320) Add project to central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160140#action_160140 ] Carlos Sanchez commented on MAVENUPLOAD-2320: - receiving file list ... rsync: link_stat /home/vidageek/maven.vidageek.net/net/vidageek/. failed: No such file or directory (2) Add project to central repository - Key: MAVENUPLOAD-2320 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2320 Project: Maven Upload Requests Issue Type: Wish Reporter: Jonas Abreu net.vidageek,maven_s...@vidageek.net:/home/vidageek/maven.vidageek.net/,rsync_ssh,Jonas Abreu,jo...@vidageek.net,, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2322) Stripes EJB3 Interceptor (version 1.0.1)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2322. --- Assignee: Carlos Sanchez Resolution: Fixed Stripes EJB3 Interceptor (version 1.0.1) Key: MAVENUPLOAD-2322 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2322 Project: Maven Upload Requests Issue Type: Wish Reporter: Samuel Santos Assignee: Carlos Sanchez Version 1.0.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: (MAVENUPLOAD-2321) Dozer 4.4 Upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2321. --- Assignee: Carlos Sanchez Resolution: Fixed Dozer 4.4 Upload Key: MAVENUPLOAD-2321 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2321 Project: Maven Upload Requests Issue Type: Task Reporter: Matt Tierney Assignee: Carlos Sanchez Attachments: dozer-4.4-bundle.jar Dozer is a Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types. Dozer supports simple property mapping, complex type mapping, bi-directional mapping, implicit-explicit mapping, as well as recursive mapping. This includes mapping collection attributes that also need mapping at the element level. Dozer not only supports mapping between attribute names, but also converting between types. Many conversion scenarios are supported out of the box, but Dozer also allows you to specify custom conversions via XML. The mapper is used any time you need to take one type of Java Bean and map it to another type of Java Bean. Most field mapping can be done automatically by Dozer using reflection, but any custom mapping can be predescribed in XML format. Mapping is bi-directional so only one relationship between classes needs defining. If any property names on both objects are the same you do not even need to do any explicit property mapping for these fields. Description Dozer is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types. Dozer supports simple property mapping, complex type mapping, bi-directional mapping, implicit-explicit mapping, as well as recursive mapping. This includes mapping collection attributes that also need mapping at the element level. Dozer not only supports mapping between attribute names, but also converting between types. Many conversion scenarios are supported out of the box, but Dozer also allows you to specify custom conversions via XML. The mapper is used any time you need to take one type of Java Bean and map it to another type of Java Bean. Most field mapping can be done automatically by Dozer using reflection, but any custom mapping can be predescribed in XML format. Mapping is bi-directional so only one relationship between classes needs defining. If any property names on both objects are the same you do not even need to do any explicit property mapping for these fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MRESOURCES-81) 2.3 escapes characters when filtering properties
2.3 escapes characters when filtering properties
Key: MRESOURCES-81
URL: http://jira.codehaus.org/browse/MRESOURCES-81
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: Windows
Reporter: Paul Jackson
When filtering a property additional escaping characters are inserted into the
replacement text. Here's an example pom snippett:
profiles
profile
idAutomated-Testing-Windows/id
properties
server.resource.typent/server.resource.type
server.remote.base.dirD:\\AutomatedTesting/server.remote.base.dir
server.remote.temp.dir${server.remote.base.dir}\\temp/server.remote.temp.dir
/properties
/profile
build
resources
resource
directorysrc/main/resources/${server.resource.type}/directory
filteringtrue/filtering
/resource
/resources
resources
plugins
plugin
artifactIdmaven-resources-plugin/artifactId
version2.3/version
executions
execution
idresources/id
phaseprocess-resources/phase
goals
goalresources/goal
/goals
configuration
outputDirectory${project.build.directory}/resources/outputDirectory
includeEmptyDirectoriestrue/includeEmptyDirectories
/configuration
/execution
/executions
/plugin
/plugins
/build
and the following line of text in a file in src\main\resources\nt
cd /d ${server.remote.temp.dir}
Resources plug in version 2.2 filters this property as follows:
cd /d D:\\AutomatedTesting\\temp
Resources plug in version 2.3 filters this property differently:
cd /d D\:AutomatedTestingtemp
Notice the extra backslashes inserted before each backslash (minor issue) and
colon (major issue). Is there a way to prevent maven from inserting these
escape characters?
I also checked out 2.4-SNAPSHOT revision 732027 and observed the same behavior.
Thanks,
-Paul
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2303) please add to repo1 for automatic syncing
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160143#action_160143 ] jay colson commented on MAVENUPLOAD-2303: - the repository directory is: /home/groups/c/cp/cpo/htdocs/sf-cpo-releases on this server: shell.sourceforge.net using this id: sncrbuild the sync error email that is sent everyday has this error message (containing a way wrong directory): groupId: org.synchronoss Error: rsync: change_dir /home/maven/bin/synchronize/m2-sync/mavens...@web.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases/org/synchronoss failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1040) [sender=3.0.3] Error synchronizing metadata. Exit code: 23 please add to repo1 for automatic syncing - Key: MAVENUPLOAD-2303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2303 Project: Maven Upload Requests Issue Type: Wish Reporter: jay colson Assignee: Carlos Sanchez org.synchronoss,sncrbu...@shell.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases,rsync_ssh,Jay Colson,jcol...@users.sourceforge.net,, Proof of domain ownership: jay.col...@synchronoss.com (synchronoss.org redrects to .com) maven public key has already been added to the sf user sncrbuild -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2303) please add to repo1 for automatic syncing
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160145#action_160145 ] Carlos Sanchez commented on MAVENUPLOAD-2303: - the sync at sourceforge is using mavensync user for all the other groups, you need to make sure your files are world readable the SF server has changed to web.sourceforge.net the directory is correct, it's the one you provided plus the groupId please add to repo1 for automatic syncing - Key: MAVENUPLOAD-2303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2303 Project: Maven Upload Requests Issue Type: Wish Reporter: jay colson Assignee: Carlos Sanchez org.synchronoss,sncrbu...@shell.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases,rsync_ssh,Jay Colson,jcol...@users.sourceforge.net,, Proof of domain ownership: jay.col...@synchronoss.com (synchronoss.org redrects to .com) maven public key has already been added to the sf user sncrbuild -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2303) please add to repo1 for automatic syncing
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160147#action_160147 ] jay colson commented on MAVENUPLOAD-2303: - it doesn't matter to me what local user you use ... I'm talking about the remote user (which needs to be sncrbuild, as that is the sourceforge user we setup with the sourceforge public key). if you want to use web.sourceforge.net instead of shell.sourceforge.net that is fine... then the rsync should be setup as such: org.synchronoss,sncrbu...@web.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases,rsync_ssh,Jay Colson,jcol...@users.sourceforge.net,, thanks, J please add to repo1 for automatic syncing - Key: MAVENUPLOAD-2303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2303 Project: Maven Upload Requests Issue Type: Wish Reporter: jay colson Assignee: Carlos Sanchez org.synchronoss,sncrbu...@shell.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases,rsync_ssh,Jay Colson,jcol...@users.sourceforge.net,, Proof of domain ownership: jay.col...@synchronoss.com (synchronoss.org redrects to .com) maven public key has already been added to the sf user sncrbuild -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2303) please add to repo1 for automatic syncing
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160148#action_160148 ] jay colson commented on MAVENUPLOAD-2303: - it is world readable as well, can be accessed via: http://cpo.sourceforge.net/sf-cpo-releases/org/synchronoss/cpo/ please add to repo1 for automatic syncing - Key: MAVENUPLOAD-2303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2303 Project: Maven Upload Requests Issue Type: Wish Reporter: jay colson Assignee: Carlos Sanchez org.synchronoss,sncrbu...@shell.sourceforge.net/home/groups/c/cp/cpo/htdocs/sf-cpo-releases,rsync_ssh,Jay Colson,jcol...@users.sourceforge.net,, Proof of domain ownership: jay.col...@synchronoss.com (synchronoss.org redrects to .com) maven public key has already been added to the sf user sncrbuild -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3973) MavenDependencyProcessor does not throw an Exception when parent pom not found
MavenDependencyProcessor does not throw an Exception when parent pom not found -- Key: MNG-3973 URL: http://jira.codehaus.org/browse/MNG-3973 Project: Maven 2 Issue Type: Bug Affects Versions: 3.0-alpha-1 Reporter: Oleg Gusakov Please indicate all problems like this with DependencyProcessorException or re-throw MetadataReaderException if it was thrown in a reader callback. Currently - MavenDependencyProcessor logs a warning and moves on -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3973) MavenDependencyProcessor does not throw an Exception when parent pom not found
[ http://jira.codehaus.org/browse/MNG-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Gusakov updated MNG-3973: -- Assignee: Shane Isbell Fix Version/s: 3.0-alpha-2 MavenDependencyProcessor does not throw an Exception when parent pom not found -- Key: MNG-3973 URL: http://jira.codehaus.org/browse/MNG-3973 Project: Maven 2 Issue Type: Bug Affects Versions: 3.0-alpha-1 Reporter: Oleg Gusakov Assignee: Shane Isbell Fix For: 3.0-alpha-2 Please indicate all problems like this with DependencyProcessorException or re-throw MetadataReaderException if it was thrown in a reader callback. Currently - MavenDependencyProcessor logs a warning and moves on -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-3856) Fix interpolation to correctly treat all interpolated variables
[
http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160154#action_160154
]
Oleg Gusakov commented on MNG-3856:
---
added a unit test with r732103
Fix interpolation to correctly treat all interpolated variables
---
Key: MNG-3856
URL: http://jira.codehaus.org/browse/MNG-3856
Project: Maven 2
Issue Type: Bug
Reporter: Oleg Gusakov
Assignee: Shane Isbell
Fix For: 3.0-alpha-2
There are several dependencies that have non-replaced variables, coming from
maven-mercury implementation:
{code}
== org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.scm:maven-scm-api:${maven-scm.version}::jar ==
org.apache.maven.plugins:maven-changelog-plugin:2.1::jar
== org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven:maven-artifact:${maven.version}::jar ==
org.apache.maven.plugins:maven-dependency-plugin:2.0::jar
== org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-ear-plugin:2.3.1::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-deploy-plugin:2.4::jar
== org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-javadoc-plugin:2.4::jar
== org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for
org.apache.maven.doxia:doxia-sink-api:${doxiaVersion}::jar ==
org.apache.maven.plugins:maven-plugin-plugin:2.4.3::jar
== org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.5::jar ==
org.apache.maven.plugins:maven-remote-resources-plugin:1.0::jar
== org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
org.apache.maven.mercury.metadata.MetadataTreeException: did not find
non-optional artifact for ${pom.groupId}:wagon-http-shared:1.0-beta-2::jar
== org.apache.maven.wagon:wagon-http-lightweight:1.0-beta-2::jar ==
org.apache.maven:maven-core:2.0.6::jar ==
org.apache.maven.plugins:maven-surefire-plugin:2.4.3::jar
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-246) TOC macro: higher entries are ignored
[
http://jira.codehaus.org/browse/DOXIA-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed DOXIA-246.
---
Assignee: Lukas Theussl
Resolution: Fixed
Fix Version/s: 1.1
Fixed in r732143.
TOC macro: higher entries are ignored
-
Key: DOXIA-246
URL: http://jira.codehaus.org/browse/DOXIA-246
Project: Maven Doxia
Issue Type: Bug
Components: Core
Affects Versions: 1.0-alpha-11
Reporter: Lukas Theussl
Assignee: Lukas Theussl
Fix For: 1.1
For the xdoc snippet below, using default macro parameters, the created TOC
has no sub-sub-sections in section 2 ; section 3 has no sub-sections, etc.
{code:xml}
section name=TITLE 1
subsection name=SUB TITLE 1.1bla bla... /subsection
subsection name=SUB TITLE 1.2 bla bla.../subsection
subsection name=SUB TITLE 1.3 bla bla...
h4SUB SUB TITLE 1.3.1/h4
h4SUB SUB TITLE 1.3.2/h4
h4SUB SUB TITLE 1.3.3/h4
/subsection
subsection name=SUB TITLE 1.4 bla bla.../subsection
/section
section name=TITLE 2
subsection name=SUB TITLE 2.1 bla bla... /subsection
subsection name=SUB TITLE 2.2 bla bla.../subsection
subsection name=SUB TITLE 2.3 bla bla...
h4SUB SUB TITLE 2.3.1/h4
h4SUB SUB TITLE 2.3.2/h4
h4SUB SUB TITLE 2.3.3/h4
/subsection
subsection name=SUB TITLE 2.4 bla bla.../subsection
/section
section name=TITLE 3
subsection name=SUB TITLE 3.1 bla bla... /subsection
subsection name=SUB TITLE 3.2 bla bla.../subsection
subsection name=SUB TITLE 3.3 bla bla...
h4SUB SUB TITLE 3.3.1/h4
h4SUB SUB TITLE 3.3.2/h4
h4SUB SUB TITLE 3.3.3/h4
/subsection
subsection name=SUB TITLE 3.4 bla bla.../subsection
/section
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3788) Profiles in profiles.xml not activated properly
[ http://jira.codehaus.org/browse/MNG-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160165#action_160165 ] Alejandro Scandroli commented on MNG-3788: -- I can confirm the issue and it's very easy to test just type: mvn help:active-profiles -P conwebDev and you will see that all the profiles in the profiles.xml are active. Profiles in profiles.xml not activated properly --- Key: MNG-3788 URL: http://jira.codehaus.org/browse/MNG-3788 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions: 2.0.9 Environment: Windows XP Professional Reporter: Walt Barrow Fix For: 2.0.x I created a profiles.xml file with three profiles in it as shown below. When I execute a Maven command like: mvn -f path-to-basedir\pom.xml -PconwebDev ... the properties defined by profile conwebFinal are used. I shuffled the profiles around in the file and whichever one was defined last was the one whose values took effect. It seems as if all profiles are being activated and the last one wins. When I put these same profiles in settings.xml or inside the main pom.xml, everything works properly. Here are the profiles: profiles !-- conweb Project-specific profiles -- profile idconwebDev/id properties app.propertiesconweb.properties/app.properties app.version.qualifierDEV/app.version.qualifier /properties /profile profile idconwebTest/id properties app.propertiesconweb.properties/app.properties app.version.qualifierTEST/app.version.qualifier /properties /profile profile idconwebFinal/id properties app.propertiesconweb.properties/app.properties app.version.qualifierFINAL/app.version.qualifier /properties /profile /profiles -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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-96) earSourceExcludes does not work for jar dependency filtering like warSourceExcludes / packagingExcludes for the maven-war-plugin
earSourceExcludes does not work for jar dependency filtering like warSourceExcludes / packagingExcludes for the maven-war-plugin Key: MEAR-96 URL: http://jira.codehaus.org/browse/MEAR-96 Project: Maven 2.x Ear Plugin Issue Type: Bug Environment: Windows XP SP3 Reporter: Scott Heaberlin The earSourceExcludes parameter of the EarMojo does not appear to have any effect on jar dependencies. Given the pom below, commons-logging.jar should be excluded from the resultant .ear archive but is not. The junit test for the ear mojo (test-project-014) uses earSourceExcludes but only with files that are in the earSourceDirectory. Similar functionality works for the maven-war-plugin (warSourceExcludes, which was renamed to packagingExcludes) so it was a little confusing to find that earSourceIncludes does not allow filtering in the same fashion. -- example pom.xml project xmlns=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; modelVersion4.0.0/modelVersion groupIdexample/groupId artifactIdexample-ear/artifactId packagingear/packaging nameexample-ear/name version0.1-SNAPSHOT/version description sample ear project demonstrating effectiveness of earSourceExcludes parameter of the maven-ear-plugin /description build plugins plugin artifactIdmaven-ear-plugin/artifactId version2.3.1/version configuration earSourceDirectorysrc/main/application/earSourceDirectory earSourceExcludes**/commons*/earSourceExcludes /configuration /plugin /plugins /build dependencies dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version1.2.7/version /dependency /dependencies /project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MEAR-96) earSourceExcludes does not work for jar dependency filtering like warSourceExcludes / packagingExcludes for the maven-war-plugin
[ http://jira.codehaus.org/browse/MEAR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Heaberlin updated MEAR-96: Attachment: pom.xml POM xml pasted into original description got munged; here is the original file. earSourceExcludes does not work for jar dependency filtering like warSourceExcludes / packagingExcludes for the maven-war-plugin Key: MEAR-96 URL: http://jira.codehaus.org/browse/MEAR-96 Project: Maven 2.x Ear Plugin Issue Type: Bug Environment: Windows XP SP3 Reporter: Scott Heaberlin Attachments: pom.xml The earSourceExcludes parameter of the EarMojo does not appear to have any effect on jar dependencies. Given the pom below, commons-logging.jar should be excluded from the resultant .ear archive but is not. The junit test for the ear mojo (test-project-014) uses earSourceExcludes but only with files that are in the earSourceDirectory. Similar functionality works for the maven-war-plugin (warSourceExcludes, which was renamed to packagingExcludes) so it was a little confusing to find that earSourceIncludes does not allow filtering in the same fashion. -- example pom.xml project xmlns=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; modelVersion4.0.0/modelVersion groupIdexample/groupId artifactIdexample-ear/artifactId packagingear/packaging nameexample-ear/name version0.1-SNAPSHOT/version description sample ear project demonstrating effectiveness of earSourceExcludes parameter of the maven-ear-plugin /description build plugins plugin artifactIdmaven-ear-plugin/artifactId version2.3.1/version configuration earSourceDirectorysrc/main/application/earSourceDirectory earSourceExcludes**/commons*/earSourceExcludes /configuration /plugin /plugins /build dependencies dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version1.2.7/version /dependency /dependencies /project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MEAR-96) earSourceExcludes does not work for jar dependency filtering like warSourceExcludes / packagingExcludes for the maven-war-plugin
[ http://jira.codehaus.org/browse/MEAR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160170#action_160170 ] Scott Heaberlin edited comment on MEAR-96 at 1/6/09 5:10 PM: - POM xml pasted into original description got munged; attached is the original example file. was (Author: sheaberlin): POM xml pasted into original description got munged; here is the original file. earSourceExcludes does not work for jar dependency filtering like warSourceExcludes / packagingExcludes for the maven-war-plugin Key: MEAR-96 URL: http://jira.codehaus.org/browse/MEAR-96 Project: Maven 2.x Ear Plugin Issue Type: Bug Environment: Windows XP SP3 Reporter: Scott Heaberlin Attachments: pom.xml The earSourceExcludes parameter of the EarMojo does not appear to have any effect on jar dependencies. Given the pom below, commons-logging.jar should be excluded from the resultant .ear archive but is not. The junit test for the ear mojo (test-project-014) uses earSourceExcludes but only with files that are in the earSourceDirectory. Similar functionality works for the maven-war-plugin (warSourceExcludes, which was renamed to packagingExcludes) so it was a little confusing to find that earSourceIncludes does not allow filtering in the same fashion. -- example pom.xml project xmlns=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; modelVersion4.0.0/modelVersion groupIdexample/groupId artifactIdexample-ear/artifactId packagingear/packaging nameexample-ear/name version0.1-SNAPSHOT/version description sample ear project demonstrating effectiveness of earSourceExcludes parameter of the maven-ear-plugin /description build plugins plugin artifactIdmaven-ear-plugin/artifactId version2.3.1/version configuration earSourceDirectorysrc/main/application/earSourceDirectory earSourceExcludes**/commons*/earSourceExcludes /configuration /plugin /plugins /build dependencies dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version1.2.7/version /dependency /dependencies /project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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: (MPATCH-5) Version 1.1 needs to be publicly released
Version 1.1 needs to be publicly released -- Key: MPATCH-5 URL: http://jira.codehaus.org/browse/MPATCH-5 Project: Maven 2.x Patch Plugin Issue Type: Task Affects Versions: 1.1 Environment: all Reporter: Jayson Raymond Priority: Minor The last reported issue for this release was fixed 9 months ago - and no other appear to have been reported. Because version with fixes is not officially released and remains a snapshot, users of the version with fixes cannot make use of the maven-release-plugin which requires all tools used to make release be released, not snapshots. This is a major pain point for our project which, without the release plugin, requires manual manipulation of version numbers in 40 some pom files. Plugin is working well in Linux, Windows XP and Vista environments (with the aid of cygwin). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-536) Plugin cannot handle java in a path name
Plugin cannot handle java in a path name -- Key: SUREFIRE-536 URL: http://jira.codehaus.org/browse/SUREFIRE-536 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.4.3 Reporter: SebbASF Commons SCXML has the following include: includeorg/apache/commons/scxml/env/javascript/EnvJavaScriptTestSuite.java/include However, the suite was not being found and executed. A bit of experimentation shows that the problem is the string java in the pathname. A work-round is to use: includeorg/apache/commons/scxml/env/j*avascript/EnvJavaScriptTestSuite.java/include or includeorg/apache/commons/scxml/env/jav*ascript/EnvJavaScriptTestSuite.java/include or includeorg/apache/commons/scxml/env/*/EnvJavaScriptTestSuite.java/include etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3507) ANSI Color logging for improved output visibility.
[
http://jira.codehaus.org/browse/MNG-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160189#action_160189
]
Johannes Buchner commented on MNG-3507:
---
A slightly different approach, yet considerably easier.
http://twoday.tuwien.ac.at/jo/stories/320760/
Works of course on environments that support it, but assuming all unices want
it, you can just fix your Maven2 Start Up Batch script to add this.
Like so: (at the end of the mvn bash script distributed)
exec $JAVACMD \
$MAVEN_OPTS \
-classpath ${M2_HOME}/boot/classworlds-*.jar \
-Dclassworlds.conf=${M2_HOME}/bin/m2.conf \
-Dmaven.home=${M2_HOME} \
${CLASSWORLDS_LAUNCHER} $QUOTED_ARGS |
sed -e 's/Tests run: \([^,]*\), Failures: \([^,]*\), Errors: \([^,]*\),
Skipped: \([^,]*\)/[1;32mTests run: \1[0m, Failures: [1;31m\2[0m, Errors:
[1;33m\3[0m, Skipped: [1;34m\4[0m/g' \
-e 's/\(\[WARN\].*\)/[1;33m\1[0m/g' \
-e 's/\(\[INFO\].*\)/[1;34m\1[0m/g' \
-e 's/\(\[ERROR\].*\)/[1;31m\1[0m/g'
Or is that just the one gentoo provides? Anyhow, you provide this to your
distributers.
ANSI Color logging for improved output visibility.
--
Key: MNG-3507
URL: http://jira.codehaus.org/browse/MNG-3507
Project: Maven 2
Issue Type: Improvement
Reporter: Rahul Thakur
Fix For: 3.x
Attachments: maven-colorlogger.zip, pom.xml
Is it possible for Maven to use ANSI color logging? IMO it would make Maven
logs much easier to read and increase the visibility of items that the user
want to see at any given point in time.
I think Andrew Williams did some work under Plexus sandbox to enable color
logging. There also a color logger available in Ant.
http://ant.apache.org/manual/listeners.html#AnsiColorLogger
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-420) ANSI color support
[ http://jira.codehaus.org/browse/SUREFIRE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160190#action_160190 ] Johannes Buchner commented on SUREFIRE-420: --- See my post at http://jira.codehaus.org/browse/MNG-3507?focusedCommentId=160189page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_160189 ANSI color support -- Key: SUREFIRE-420 URL: http://jira.codehaus.org/browse/SUREFIRE-420 Project: Maven Surefire Issue Type: New Feature Components: plugin Reporter: Dan Fabulich Fix For: 2.x shitty-maven-plugin supports ANSI coloring for its test results. Color is pretty! We should support it for all kinds of 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] Issue Comment Edited: (MNG-3507) ANSI Color logging for improved output visibility.
[
http://jira.codehaus.org/browse/MNG-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160189#action_160189
]
Johannes Buchner edited comment on MNG-3507 at 1/6/09 10:08 PM:
A slightly different approach, yet considerably easier.
http://twoday.tuwien.ac.at/jo/stories/320760/
Works of course on environments that support it, but assuming all unices want
it, you can just fix your Maven2 Start Up Batch script to add this.
Like so: (at the end of the mvn bash script distributed)
exec $JAVACMD \
$MAVEN_OPTS \
-classpath ${M2_HOME}/boot/classworlds-*.jar \
-Dclassworlds.conf=${M2_HOME}/bin/m2.conf \
-Dmaven.home=${M2_HOME} \
${CLASSWORLDS_LAUNCHER} $QUOTED_ARGS |
sed -e 's/Tests run: \([^,]*\), Failures: \([^,]*\), Errors: \([^,]*\),
Skipped: \([^,]*\)/[1;32mTests run: \1[0m, Failures: [1;31m\2[0m, Errors:
[1;33m\3[0m, Skipped: [1;34m\4[0m/g' \
-e 's/\(\[WARN\].*\)/[1;33m\1[0m/g' \
-e 's/\(\[INFO\].*\)/[1;34m\1[0m/g' \
-e 's/\(\[ERROR\].*\)/[1;31m\1[0m/g'
Or is that just the one gentoo provides? Anyhow, you could provide this to your
distributers.
was (Author: buchner.johannes):
A slightly different approach, yet considerably easier.
http://twoday.tuwien.ac.at/jo/stories/320760/
Works of course on environments that support it, but assuming all unices want
it, you can just fix your Maven2 Start Up Batch script to add this.
Like so: (at the end of the mvn bash script distributed)
exec $JAVACMD \
$MAVEN_OPTS \
-classpath ${M2_HOME}/boot/classworlds-*.jar \
-Dclassworlds.conf=${M2_HOME}/bin/m2.conf \
-Dmaven.home=${M2_HOME} \
${CLASSWORLDS_LAUNCHER} $QUOTED_ARGS |
sed -e 's/Tests run: \([^,]*\), Failures: \([^,]*\), Errors: \([^,]*\),
Skipped: \([^,]*\)/[1;32mTests run: \1[0m, Failures: [1;31m\2[0m, Errors:
[1;33m\3[0m, Skipped: [1;34m\4[0m/g' \
-e 's/\(\[WARN\].*\)/[1;33m\1[0m/g' \
-e 's/\(\[INFO\].*\)/[1;34m\1[0m/g' \
-e 's/\(\[ERROR\].*\)/[1;31m\1[0m/g'
Or is that just the one gentoo provides? Anyhow, you provide this to your
distributers.
ANSI Color logging for improved output visibility.
--
Key: MNG-3507
URL: http://jira.codehaus.org/browse/MNG-3507
Project: Maven 2
Issue Type: Improvement
Reporter: Rahul Thakur
Fix For: 3.x
Attachments: maven-colorlogger.zip, pom.xml
Is it possible for Maven to use ANSI color logging? IMO it would make Maven
logs much easier to read and increase the visibility of items that the user
want to see at any given point in time.
I think Andrew Williams did some work under Plexus sandbox to enable color
logging. There also a color logger available in Ant.
http://ant.apache.org/manual/listeners.html#AnsiColorLogger
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact 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-81) 2.3 escapes characters when filtering properties
[
http://jira.codehaus.org/browse/MRESOURCES-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160191#action_160191
]
Jason Royals commented on MRESOURCES-81:
I get the same error too, looks to be caused by MRESOURCES-42
Sometimes escaping the backslash is needed, and sometimes it is not, depending
on what is being filtered. In my situation I need to specify ${builddir} in an
XML file which is filtered. Now I get backslashes in the XML file where they
were not before, and the build breaks because the library that uses that XML
file is not expecting all that extra escaping.
I wonder if there could be an optional element under the {{resource}} and
{{testResource}}section of the pom to be able to control at a resources level
how characters are escaped. For example:
{code}
resource
directorysrc/main/webapp/WEB-INF/directory
filteringtrue/filtering
escapeNONE/escape
includes
include**/*.xml/include
/includes
targetPath../POSPolicyService-FunctionalTest/WEB-INF/targetPath
/resource
{code}
Possible values could be NONE, JAVA (just escape the backslashes) and PROPERTY
(escape colons and backslashes).
Thanks
2.3 escapes characters when filtering properties
Key: MRESOURCES-81
URL: http://jira.codehaus.org/browse/MRESOURCES-81
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: Windows
Reporter: Paul Jackson
When filtering a property additional escaping characters are inserted into
the replacement text. Here's an example pom snippett:
profiles
profile
idAutomated-Testing-Windows/id
properties
server.resource.typent/server.resource.type
server.remote.base.dirD:\\AutomatedTesting/server.remote.base.dir
server.remote.temp.dir${server.remote.base.dir}\\temp/server.remote.temp.dir
/properties
/profile
build
resources
resource
directorysrc/main/resources/${server.resource.type}/directory
filteringtrue/filtering
/resource
/resources
resources
plugins
plugin
artifactIdmaven-resources-plugin/artifactId
version2.3/version
executions
execution
idresources/id
phaseprocess-resources/phase
goals
goalresources/goal
/goals
configuration
outputDirectory${project.build.directory}/resources/outputDirectory
includeEmptyDirectoriestrue/includeEmptyDirectories
/configuration
/execution
/executions
/plugin
/plugins
/build
and the following line of text in a file in src\main\resources\nt
cd /d ${server.remote.temp.dir}
Resources plug in version 2.2 filters this property as follows:
cd /d D:\\AutomatedTesting\\temp
Resources plug in version 2.3 filters this property differently:
cd /d D\:AutomatedTestingtemp
Notice the extra backslashes inserted before each backslash (minor issue) and
colon (major issue). Is there a way to prevent maven from inserting these
escape characters?
I also checked out 2.4-SNAPSHOT revision 732027 and observed the same
behavior.
Thanks,
-Paul
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRESOURCES-81) 2.3 escapes characters when filtering properties
[
http://jira.codehaus.org/browse/MRESOURCES-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160191#action_160191
]
Jason Royals edited comment on MRESOURCES-81 at 1/6/09 10:39 PM:
-
I get the same error too, looks to be caused by MRESOURCES-42
Sometimes escaping the backslash is needed, and sometimes it is not, depending
on what is being filtered. In my situation I need to specify ${builddir} in an
XML file which is filtered. Now I get backslashes in the XML file where they
were not before, and the build breaks because the library that uses that XML
file is not expecting all that extra escaping.
I wonder if there could be an optional element under the {{resource}} and
{{testResource}} section of the pom to be able to control at a resources
level how characters are escaped. For example:
{code}
resource
directorysrc/main/webapp/WEB-INF/directory
filteringtrue/filtering
escapeNONE/escape
includes
include**/*.xml/include
/includes
targetPath../POSPolicyService-FunctionalTest/WEB-INF/targetPath
/resource
{code}
Possible values could be NONE, JAVA (just escape the backslashes) and PROPERTY
(escape colons and backslashes).
Thanks
was (Author: majikshoe):
I get the same error too, looks to be caused by MRESOURCES-42
Sometimes escaping the backslash is needed, and sometimes it is not, depending
on what is being filtered. In my situation I need to specify ${builddir} in an
XML file which is filtered. Now I get backslashes in the XML file where they
were not before, and the build breaks because the library that uses that XML
file is not expecting all that extra escaping.
I wonder if there could be an optional element under the {{resource}} and
{{testResource}}section of the pom to be able to control at a resources level
how characters are escaped. For example:
{code}
resource
directorysrc/main/webapp/WEB-INF/directory
filteringtrue/filtering
escapeNONE/escape
includes
include**/*.xml/include
/includes
targetPath../POSPolicyService-FunctionalTest/WEB-INF/targetPath
/resource
{code}
Possible values could be NONE, JAVA (just escape the backslashes) and PROPERTY
(escape colons and backslashes).
Thanks
2.3 escapes characters when filtering properties
Key: MRESOURCES-81
URL: http://jira.codehaus.org/browse/MRESOURCES-81
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: Windows
Reporter: Paul Jackson
When filtering a property additional escaping characters are inserted into
the replacement text. Here's an example pom snippett:
profiles
profile
idAutomated-Testing-Windows/id
properties
server.resource.typent/server.resource.type
server.remote.base.dirD:\\AutomatedTesting/server.remote.base.dir
server.remote.temp.dir${server.remote.base.dir}\\temp/server.remote.temp.dir
/properties
/profile
build
resources
resource
directorysrc/main/resources/${server.resource.type}/directory
filteringtrue/filtering
/resource
/resources
resources
plugins
plugin
artifactIdmaven-resources-plugin/artifactId
version2.3/version
executions
execution
idresources/id
phaseprocess-resources/phase
goals
goalresources/goal
/goals
configuration
outputDirectory${project.build.directory}/resources/outputDirectory
includeEmptyDirectoriestrue/includeEmptyDirectories
/configuration
/execution
/executions
/plugin
/plugins
/build
and the following line of text in a file in src\main\resources\nt
cd /d ${server.remote.temp.dir}
Resources plug in version 2.2 filters this property as follows:
cd /d D:\\AutomatedTesting\\temp
Resources plug in version 2.3 filters this property differently:
cd /d D\:AutomatedTestingtemp
Notice the extra backslashes inserted before each backslash (minor issue) and
colon (major issue). Is there a way to prevent maven from inserting these
escape characters?
I also checked out 2.4-SNAPSHOT revision 732027 and observed the same
behavior.
Thanks,
-Paul
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-272) TOC macro: allow to specify from/toDepth for *all* sections
TOC macro: allow to specify from/toDepth for *all* sections --- Key: DOXIA-272 URL: http://jira.codehaus.org/browse/DOXIA-272 Project: Maven Doxia Issue Type: Improvement Components: Core Affects Versions: 1.0-alpha-11 Reporter: Lukas Theussl Priority: Minor The description of the section parameter in the TOC macro currently reads: bq. Display the specificated section number or all sections if 0 (in this case, other parameters are ignored). I don't see any reason for this restriction, eg I would like to get a TOC showing subsections up to a certain depth for *all* sections, which is currently not possible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
