[jira] (ARCHETYPE-403) Error reading archetype catalog http://repo1.maven.org/maven2 on archetype:generate
Jens Rapp created ARCHETYPE-403:
---
Summary: Error reading archetype catalog
http://repo1.maven.org/maven2 on archetype:generate
Key: ARCHETYPE-403
URL: https://jira.codehaus.org/browse/ARCHETYPE-403
Project: Maven Archetype
Issue Type: Bug
Components: Archetypes, Generator
Affects Versions: 2.2, 2.1
Reporter: Jens Rapp
hello,
we use maven behind a cascade of two maven proxies. (only second one is in our
hands, the other one connects to internet)
When we call mvn archetype:generate this happens:
{quote}
hal# /opt/maven-2.1.0/bin/mvn archetype:generate
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]
[INFO] Building Maven Default Project
[INFO]task-segment: [archetype:generate] (aggregator-style)
[INFO]
[INFO] Preparing archetype:generate
[INFO] No goals needed for project - skipping
[INFO] [archetype:generate]
[INFO] Generating project in Interactive mode
[WARNING] Error reading archetype catalog http://repo1.maven.org/maven2
org.apache.maven.wagon.TransferFailedException: Error transferring file:
repo1.maven.org
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:143)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.archetype.source.RemoteCatalogArchetypeDataSource.downloadCatalog(RemoteCatalogArchetypeDataSource.java:119)
at
org.apache.maven.archetype.source.RemoteCatalogArchetypeDataSource.getArchetypeCatalog(RemoteCatalogArchetypeDataSource.java:87)
at
org.apache.maven.archetype.DefaultArchetypeManager.getRemoteCatalog(DefaultArchetypeManager.java:216)
at
org.apache.maven.archetype.DefaultArchetypeManager.getRemoteCatalog(DefaultArchetypeManager.java:205)
at
org.apache.maven.archetype.ui.generation.DefaultArchetypeSelector.getArchetypesByCatalog(DefaultArchetypeSelector.java:200)
at
org.apache.maven.archetype.ui.generation.DefaultArchetypeSelector.selectArchetype(DefaultArchetypeSelector.java:71)
at
org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:197)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
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: java.net.UnknownHostException: repo1.maven.org
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
at sun.net.www.http.HttpClient.(HttpClient.java:233)
at sun.net.www.http.HttpClient.New(HttpClient.java:306)
at sun.net.www.http.HttpClient.New(HttpClient.java:323)
at
sun.net.www.protocol.http.HttpURLConnection
[jira] (MNG-5237) Cannot download maven dependencies through proxy
[
https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293847#comment-293847
]
Babak Vahdat commented on MNG-5237:
---
Being behind a HTTP Proxy I'm suffering from the same behavior (upgrading Maven
3.0.3 => 3.0.4)
I followed the new 1.1.0 schema
(http://maven.apache.org/xsd/settings-1.1.0.xsd) however with no success.
And actually the Proxy I'm behind of does *not* require my personal credentials
of me (username/password) but just checks the IP, that's all! That was also why
I didn't have to provide correct username/password while using 3.0.3. However
now even using correct credentials under 3.0.4 it blows up with:
{code}
Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed
to read artifact descriptor for
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:jar:1.0
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296)
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(DefaultDependencyCollector.java:412)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:240)
... 25 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could
not transfer artifact
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:pom:1.0 from/to
smx.repo (http://svn.apache.org/repos/asf/servicemix/m2-repo/): Not authorized
by proxy, ReasonPhrase:Proxy Authentication Required.
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281)
... 28 more
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not
transfer artifact
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:pom:1.0 from/to
smx.repo (http://svn.apache.org/repos/asf/servicemix/m2-repo/): Not authorized
by proxy, ReasonPhrase:Proxy Authentication Required.
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:951)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)
at
org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Not
authorized by proxy, ReasonPhrase:Proxy Authentication Required.
at
org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:843)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:601)
... 4 more
{code}
To prove that using the same box I can successfuly access the Internet,
following couple of lines of code which *does* deliver me the content of
http://www.google.ch
{code}
public static void main(String[] args) throws Exception {
InetSocketAddress address = new InetSocketAddress("proxy.domain.name",
proxy.port.number);
Proxy proxy = new Proxy(Proxy.Type.HTTP, address);
URL url = new URL("http://www.google.ch";);
URLConnection connection = url.openConnection(proxy);
InputStream is = connection.getInputStream();
int c;
while ((c = is.read()) != -1) {
System.out.print((char) c);
}
}
{code}
> Cannot download maven dependencies through proxy
>
>
> Key: MNG-5237
> URL: https://jira.codehaus.org/browse/MNG-5237
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 3.0.4
> Environment:
[jira] (MNG-5258) localRepository in settings.xml does not handle ~ as home.dir
Thomas Zeeman created MNG-5258: -- Summary: localRepository in settings.xml does not handle ~ as home.dir Key: MNG-5258 URL: https://jira.codehaus.org/browse/MNG-5258 Project: Maven 2 & 3 Issue Type: Bug Components: Bootstrap & Build, Settings Affects Versions: 3.0.4, 2.2.1 Environment: Linux (Ubuntu 11.10), Java 6 Reporter: Thomas Zeeman My provided settings.xml contained a localRepository part with the value ~/.m2/repository and when invoking any maven command, this caused issues. Steps to reproduce: 1 - create a settings.xml with the following content: ~/.m2/repository 2 - run mvn clean in an existing project 3 - maven will create a ~ directory in the project where it will download all artifacts to. Apart from essentially creating a private repository for each project (which can quickly take up way more space than necessary, cause issues about missing artifacts) it may also cause issues if you try to remove it and forget to escape the ~; ie if you do rm -rf ~ instead of rm -rf '~'. I also tested with maven 2.2.1 and that will blow up with errors about not being able to create /.m2/repository/. Both 3.0.4 and 2.2.1 were downloaded from maven.apache.org, not installed via apt/dpkg. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5237) Cannot download maven dependencies through proxy
[
https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293847#comment-293847
]
Babak Vahdat edited comment on MNG-5237 at 3/12/12 5:25 AM:
Being behind a HTTP Proxy I'm suffering from the same behavior (upgrading Maven
3.0.3 => 3.0.4)
I followed the new 1.1.0 schema
(http://maven.apache.org/xsd/settings-1.1.0.xsd) however with no success.
And actually the Proxy I'm behind of does *not* require my personal credentials
at all (username/password) but just checks only the IP of the box I'm
connecting from, that's all! That was also why I didn't have to provide correct
username/password while using 3.0.3. However now even using correct credentials
under 3.0.4 it blows up with:
{code}
Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed
to read artifact descriptor for
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:jar:1.0
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296)
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.process(DefaultDependencyCollector.java:412)
at
org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:240)
... 25 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could
not transfer artifact
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:pom:1.0 from/to
smx.repo (http://svn.apache.org/repos/asf/servicemix/m2-repo/): Not authorized
by proxy, ReasonPhrase:Proxy Authentication Required.
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)
at
org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281)
... 28 more
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not
transfer artifact
org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:pom:1.0 from/to
smx.repo (http://svn.apache.org/repos/asf/servicemix/m2-repo/): Not authorized
by proxy, ReasonPhrase:Proxy Authentication Required.
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:951)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)
at
org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Not
authorized by proxy, ReasonPhrase:Proxy Authentication Required.
at
org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:843)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:601)
... 4 more
{code}
To prove that using the same box I can successfuly access the Internet,
following couple of lines of code which *does* deliver me the content of
http://www.google.ch
{code}
public static void main(String[] args) throws Exception {
InetSocketAddress address = new InetSocketAddress("proxy.domain.name",
proxy.port.number);
Proxy proxy = new Proxy(Proxy.Type.HTTP, address);
URL url = new URL("http://www.google.ch";);
URLConnection connection = url.openConnection(proxy);
InputStream is = connection.getInputStream();
int c;
while ((c = is.read()) != -1) {
System.out.print((char) c);
}
}
{code}
was (Author: bvahdat):
Being behind a HTTP Proxy I'm suffering from the same behavior (upgrading
Maven 3.0.3 => 3.0.4)
I followed the new 1.1.0 schema
(http://maven.apache.org/xsd/settings-1.1.0.xsd) however with no success.
And actually the Proxy I'
[jira] (MDEP-348) Add skip parameter to copy-dependencies goal
Mikhail Mazursky created MDEP-348: - Summary: Add skip parameter to copy-dependencies goal Key: MDEP-348 URL: https://jira.codehaus.org/browse/MDEP-348 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: copy-dependencies, purge-local-repository, unpack-dependencies Affects Versions: 2.4 Environment: Maven 3.0.4 Reporter: Mikhail Mazursky Copy goal have this parameter but copy-dependencies misses it. I need it now, please add it. Also unpack and unpack-dependencies goal have the same issue (and maybe other goals too). In general it may be usefull to have this parameter in every goal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-111) minimizeJar should not remove classes specifically included by filters
[ https://jira.codehaus.org/browse/MSHADE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293886#comment-293886 ] Shmuel Blitz commented on MSHADE-111: - This feature is superb. It will allow using minijar with log4j and with spring. > minimizeJar should not remove classes specifically included by filters > -- > > Key: MSHADE-111 > URL: https://jira.codehaus.org/browse/MSHADE-111 > Project: Maven 2.x Shade Plugin > Issue Type: Improvement >Affects Versions: 1.5 >Reporter: Shane StClair > Attachments: mshade-111-fixed-again.patch, mshade-111-fixed.patch, > mshade-111.patch > > > Currently there is no way to specify classes that should not be removed by > minimizeJar. This means that projects using dynamically loaded classes > (log4j, for instance) cannot use minimizeJar. This patch prevents minimizeJar > from removing classes that were specified for inclusion in a filter. > The patch also fixes a test in ComponentsXmlResourceTransformerTest that was > failing on Windows due to different line breaks in a string comparison. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5259) Mechanism to download POMs only
Peter Johnson created MNG-5259: -- Summary: Mechanism to download POMs only Key: MNG-5259 URL: https://jira.codehaus.org/browse/MNG-5259 Project: Maven 2 & 3 Issue Type: Improvement Components: Dependencies Affects Versions: 3.0.4 Environment: Any Reporter: Peter Johnson Priority: Minor Attachments: patch_pomsonly.txt We often run various reports (e.g., dependency:tree) on a high-level POM that pulls in numerous artifacts at various levels in the dependency hierarchy. (Our highest-level POM defines a release of our product, it has dependencies that are OVAs (VM images), which in tern have dependencies that are typically installation packages (TAR.GZs, ZIps, MSIs, EXEs, ISOs), which in turn reference individual components (JARs, WARs, EXEs, DLLs, etc).) Some of our artifacts tend to be rather large (the OVAs are GBs in size), and since the reports need only the information in the POMs and not the artifacts themselves, we found it handy to add a "poms.only" flag to our report generation to prevent the artifacts from being downloaded from the remote repository. Thus we run: mvn dependency:tree -Dpoms.only Now our reports complete within a few minutes, rather than in a few hours. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-736) Add dryRun flag to release:perform
[
https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-736.
---
Resolution: Fixed
Fix Version/s: 2.3
Fixed in [rev. 1299865|http://svn.apache.org/viewvc?rev=1299865&view=rev].
We've decided that the plugin will skip the execution of the perform goals. The
tests have already run during the {{prepare}} and since we don't check out the
code it would run twice.
For the authentication and authorization to deploy the artifacts or the site we
might need other release-phases or separate goal.
Most important: it's now possible to do a {{mvn release:prepare release:perform
-Ddryrun}} at once.
> Add dryRun flag to release:perform
> --
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
>Affects Versions: 2.2.2
> Environment: mvn 3.0.3
>Reporter: Dominik Bartholdi
>Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the
> "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help
> the user to trigger a maven release. This plugin allows to define a
> commandline which should be executed in case of a release build. The common
> configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when
> triggering a build and in this case it would just add "-DdryRun=true" to the
> configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets
> executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean
> I have to remove "release:perform" from the passed argument, which is relay
> ugly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5260) Provide option for obtaining complete dependency hierarchy
Peter Johnson created MNG-5260: -- Summary: Provide option for obtaining complete dependency hierarchy Key: MNG-5260 URL: https://jira.codehaus.org/browse/MNG-5260 Project: Maven 2 & 3 Issue Type: Improvement Components: Dependencies Affects Versions: 3.0.4 Environment: Any Reporter: Peter Johnson Priority: Minor Attachments: patch_alldeps.txt Our lawyers are keen on us providing them with a list of all open source components in our code so that they can ensure we are properly following the licenses. Since license information is in the POM (well, for most components, but that's another story), and since Maven provides a nice report for and artifact and its dependencies, including the licenses used, we decided to sue that instead of manually coming up with a list (which is what we used to do, needless to say, the manually-generated list was always wrong). Anyway, this worked well until we tried to report on something (such as an EAR) that had a WAR as a dependency. In that case, we got the license info for the WAR, but nothing about any of the components packaged into the WAR. Initially, we though to just run a separate report on the WAR, but that lead to many too many reports and also the need to remember to run all of them (we have a main POM that describes all of the components that make up our product's release, and we wanted to run the report only on that POM). So we patched Maven Core such that the includesDependencies property for an artifact type would be ignored (essentially, always false). Now we can get a complete report, including information about dependencies for a WAR, using: mvn site -Dall.deps -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-747) Support Jazz SCM
Chris Graham created MRELEASE-747: - Summary: Support Jazz SCM Key: MRELEASE-747 URL: https://jira.codehaus.org/browse/MRELEASE-747 Project: Maven 2.x Release Plugin Issue Type: New Feature Components: scm Affects Versions: 2.2.2 Environment: N/A Reporter: Chris Graham Attachments: maven-release-2.2.2-patch-jazz.patch The Jazz SCM plugin requires SCM translation of the URL's in the POM. This patch addresses that. Note. This issue will ultimately depend on mavn-scm 1.7 being released, as that version will include the maven-scm-providers-jazz module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
