[jira] [Commented] (MRESOLVER-21) Maven Resolver trying to resolve optional dependencies
[
https://issues.apache.org/jira/browse/MRESOLVER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961888#comment-15961888
]
Cedric Beust commented on MRESOLVER-21:
---
Digging into the rabbit hole further.
Here is the lovely dependency that JCenter has:
http://jcenter.bintray.com/commons-logging/commons-logging/99.0-does-not-exist/
The parent dependency is
`jasperreports/jasperreports/2.0.5/jasperreports-2.0.5.pom` and it depends on
`commons-logging` with:
```
commons-logging
commons-logging
[1.0,)
compile
```
So it's a version range, so Maven Resolver takes the highest it can find on
JCenter, which is... 99-doesnt-exist. And boom.
> Maven Resolver trying to resolve optional dependencies
> --
>
> Key: MRESOLVER-21
> URL: https://issues.apache.org/jira/browse/MRESOLVER-21
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Reporter: Cedric Beust
>
> I modified the `ResolveTransitiveDependencies.java` example in two ways:
> - Modified the id to
> `"org.springframework:spring-context-support:2.5.6.SEC03"`
> - Replaced the filter with one that excludes optional dependencies
> I'm including the full code below.
> Despite that, `system.resolveDependencies()` fails with a
> `DependencyResolutionException when trying to resolve a bunch of optional
> dependencies, sugh as `jasperreports`.
> Head of the stack trace:
> {noformat}org.eclipse.aether.resolution.DependencyResolutionException: Failed
> to collect dependencies at
> org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
> jasperreports:jasperreports:jar:2.0.5 ->
> commons-logging:commons-logging:jar:99.0-does-not-exist
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:380)
> at
> org.apache.maven.resolver.examples.ResolveTransitiveDependencies.main(ResolveTransitiveDependencies.java:71)
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at
> org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
> jasperreports:jasperreports:jar:2.0.5 ->
> commons-logging:commons-logging:jar:99.0-does-not-exist
> at
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:341)
> ... 1 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed
> to read artifact descriptor for
> commons-logging:commons-logging:jar:99.0-does-not-exist{noformat}
> {code:java}
> public static void main( String[] args )
> throws Exception
> {
> System.out.println(
> "" );
> System.out.println(
> ResolveTransitiveDependencies.class.getSimpleName() );
> RepositorySystem system = Booter.newRepositorySystem();
> RepositorySystemSession session = Booter.newRepositorySystemSession(
> system );
> Artifact artifact = new DefaultArtifact(
> "org.springframework:spring-context-support:2.5.6.SEC03" );
> DependencyFilter classpathFlter =
> DependencyFilterUtils.classpathFilter( JavaScopes.COMPILE );
> DependencyFilter optionalFilter = new DependencyFilter() {
> @Override
> public boolean accept(DependencyNode dependencyNode,
> List list) {
> return ! dependencyNode.getDependency().getOptional();
> }
> };
> CollectRequest collectRequest = new CollectRequest();
> collectRequest.setRoot( new Dependency( artifact, JavaScopes.COMPILE
> ) );
> collectRequest.setRepositories( Booter.newRepositories( system,
> session ) );
> DependencyRequest dependencyRequest = new DependencyRequest(
> collectRequest, optionalFilter );
> try {
> List artifactResults =
> system.resolveDependencies(session,
> dependencyRequest).getArtifactResults();
> for (ArtifactResult artifactResult : artifactResults) {
> System.out.println(artifactResult.getArtifact() + " resolved
> to "
> + artifactResult.getArtifact().getFile());
> }
> } catch(Exception ex) {
> ex.printStackTrace();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MRESOLVER-21) Maven Resolver trying to resolve optional dependencies
[
https://issues.apache.org/jira/browse/MRESOLVER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961888#comment-15961888
]
Cedric Beust edited comment on MRESOLVER-21 at 4/8/17 5:00 PM:
---
Digging into the rabbit hole further.
Here is the lovely dependency that JCenter has:
http://jcenter.bintray.com/commons-logging/commons-logging/99.0-does-not-exist/
The parent dependency is
`jasperreports/jasperreports/2.0.5/jasperreports-2.0.5.pom` and it depends on
`commons-logging` with:
```
commons-logging
commons-logging
[1.0,)
compile
```
It's a version range, so Maven Resolver takes the highest it can find on
JCenter, which is... 99-doesnt-exist. And boom.
was (Author: cbeust):
Digging into the rabbit hole further.
Here is the lovely dependency that JCenter has:
http://jcenter.bintray.com/commons-logging/commons-logging/99.0-does-not-exist/
The parent dependency is
`jasperreports/jasperreports/2.0.5/jasperreports-2.0.5.pom` and it depends on
`commons-logging` with:
```
commons-logging
commons-logging
[1.0,)
compile
```
So it's a version range, so Maven Resolver takes the highest it can find on
JCenter, which is... 99-doesnt-exist. And boom.
> Maven Resolver trying to resolve optional dependencies
> --
>
> Key: MRESOLVER-21
> URL: https://issues.apache.org/jira/browse/MRESOLVER-21
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Reporter: Cedric Beust
>
> I modified the `ResolveTransitiveDependencies.java` example in two ways:
> - Modified the id to
> `"org.springframework:spring-context-support:2.5.6.SEC03"`
> - Replaced the filter with one that excludes optional dependencies
> I'm including the full code below.
> Despite that, `system.resolveDependencies()` fails with a
> `DependencyResolutionException when trying to resolve a bunch of optional
> dependencies, sugh as `jasperreports`.
> Head of the stack trace:
> {noformat}org.eclipse.aether.resolution.DependencyResolutionException: Failed
> to collect dependencies at
> org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
> jasperreports:jasperreports:jar:2.0.5 ->
> commons-logging:commons-logging:jar:99.0-does-not-exist
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:380)
> at
> org.apache.maven.resolver.examples.ResolveTransitiveDependencies.main(ResolveTransitiveDependencies.java:71)
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at
> org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
> jasperreports:jasperreports:jar:2.0.5 ->
> commons-logging:commons-logging:jar:99.0-does-not-exist
> at
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:341)
> ... 1 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed
> to read artifact descriptor for
> commons-logging:commons-logging:jar:99.0-does-not-exist{noformat}
> {code:java}
> public static void main( String[] args )
> throws Exception
> {
> System.out.println(
> "" );
> System.out.println(
> ResolveTransitiveDependencies.class.getSimpleName() );
> RepositorySystem system = Booter.newRepositorySystem();
> RepositorySystemSession session = Booter.newRepositorySystemSession(
> system );
> Artifact artifact = new DefaultArtifact(
> "org.springframework:spring-context-support:2.5.6.SEC03" );
> DependencyFilter classpathFlter =
> DependencyFilterUtils.classpathFilter( JavaScopes.COMPILE );
> DependencyFilter optionalFilter = new DependencyFilter() {
> @Override
> public boolean accept(DependencyNode dependencyNode,
> List list) {
> return ! dependencyNode.getDependency().getOptional();
> }
> };
> CollectRequest collectRequest = new CollectRequest();
> collectRequest.setRoot( new Dependency( artifact, JavaScopes.COMPILE
> ) );
> collectRequest.setRepositories( Booter.newRepositories( system,
> session ) );
> DependencyRequest dependencyRequest = new DependencyRequest(
> collectRequest, optionalFilter );
> try {
> List artifactResults =
>
[jira] [Commented] (MRESOLVER-21) Maven Resolver trying to resolve optional dependencies
[
https://issues.apache.org/jira/browse/MRESOLVER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961877#comment-15961877
]
Cedric Beust commented on MRESOLVER-21:
---
An update to this ticket: the error only happens if I add JCenter in the list
of repos:
```
new RemoteRepository.Builder( "jcenter", "default",
"https://jcenter.bintray.com; ).build()
```
If there's only Maven Central, the resolution succeeds.
> Maven Resolver trying to resolve optional dependencies
> --
>
> Key: MRESOLVER-21
> URL: https://issues.apache.org/jira/browse/MRESOLVER-21
> Project: Maven Resolver
> Issue Type: Bug
> Components: resolver
>Reporter: Cedric Beust
>
> I modified the `ResolveTransitiveDependencies.java` example in two ways:
> - Modified the id to
> `"org.springframework:spring-context-support:2.5.6.SEC03"`
> - Replaced the filter with one that excludes optional dependencies
> I'm including the full code below.
> Despite that, `system.resolveDependencies()` fails with a
> `DependencyResolutionException when trying to resolve a bunch of optional
> dependencies, sugh as `jasperreports`.
> Head of the stack trace:
> {noformat}org.eclipse.aether.resolution.DependencyResolutionException: Failed
> to collect dependencies at
> org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
> jasperreports:jasperreports:jar:2.0.5 ->
> commons-logging:commons-logging:jar:99.0-does-not-exist
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:380)
> at
> org.apache.maven.resolver.examples.ResolveTransitiveDependencies.main(ResolveTransitiveDependencies.java:71)
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at
> org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
> jasperreports:jasperreports:jar:2.0.5 ->
> commons-logging:commons-logging:jar:99.0-does-not-exist
> at
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:341)
> ... 1 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed
> to read artifact descriptor for
> commons-logging:commons-logging:jar:99.0-does-not-exist{noformat}
> {code:java}
> public static void main( String[] args )
> throws Exception
> {
> System.out.println(
> "" );
> System.out.println(
> ResolveTransitiveDependencies.class.getSimpleName() );
> RepositorySystem system = Booter.newRepositorySystem();
> RepositorySystemSession session = Booter.newRepositorySystemSession(
> system );
> Artifact artifact = new DefaultArtifact(
> "org.springframework:spring-context-support:2.5.6.SEC03" );
> DependencyFilter classpathFlter =
> DependencyFilterUtils.classpathFilter( JavaScopes.COMPILE );
> DependencyFilter optionalFilter = new DependencyFilter() {
> @Override
> public boolean accept(DependencyNode dependencyNode,
> List list) {
> return ! dependencyNode.getDependency().getOptional();
> }
> };
> CollectRequest collectRequest = new CollectRequest();
> collectRequest.setRoot( new Dependency( artifact, JavaScopes.COMPILE
> ) );
> collectRequest.setRepositories( Booter.newRepositories( system,
> session ) );
> DependencyRequest dependencyRequest = new DependencyRequest(
> collectRequest, optionalFilter );
> try {
> List artifactResults =
> system.resolveDependencies(session,
> dependencyRequest).getArtifactResults();
> for (ArtifactResult artifactResult : artifactResults) {
> System.out.println(artifactResult.getArtifact() + " resolved
> to "
> + artifactResult.getArtifact().getFile());
> }
> } catch(Exception ex) {
> ex.printStackTrace();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MRESOLVER-21) Maven Resolver trying to resolve optional dependencies
[
https://issues.apache.org/jira/browse/MRESOLVER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cedric Beust updated MRESOLVER-21:
--
Description:
I modified the `ResolveTransitiveDependencies.java` example in two ways:
- Modified the id to `"org.springframework:spring-context-support:2.5.6.SEC03"`
- Replaced the filter with one that excludes optional dependencies
I'm including the full code below.
Despite that, `system.resolveDependencies()` fails with a
`DependencyResolutionException when trying to resolve a bunch of optional
dependencies, sugh as `jasperreports`.
Head of the stack trace:
```
org.eclipse.aether.resolution.DependencyResolutionException: Failed to collect
dependencies at org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
jasperreports:jasperreports:jar:2.0.5 ->
commons-logging:commons-logging:jar:99.0-does-not-exist
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:380)
at
org.apache.maven.resolver.examples.ResolveTransitiveDependencies.main(ResolveTransitiveDependencies.java:71)
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed
to collect dependencies at
org.springframework:spring-context-support:jar:2.5.6.SEC03 ->
jasperreports:jasperreports:jar:2.0.5 ->
commons-logging:commons-logging:jar:99.0-does-not-exist
at
org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
at
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:341)
... 1 more
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to
read artifact descriptor for
commons-logging:commons-logging:jar:99.0-does-not-exist
```
```
public static void main( String[] args )
throws Exception
{
System.out.println(
"" );
System.out.println( ResolveTransitiveDependencies.class.getSimpleName()
);
RepositorySystem system = Booter.newRepositorySystem();
RepositorySystemSession session = Booter.newRepositorySystemSession(
system );
Artifact artifact = new DefaultArtifact(
"org.springframework:spring-context-support:2.5.6.SEC03" );
DependencyFilter classpathFlter =
DependencyFilterUtils.classpathFilter( JavaScopes.COMPILE );
DependencyFilter optionalFilter = new DependencyFilter() {
@Override
public boolean accept(DependencyNode dependencyNode,
List list) {
return ! dependencyNode.getDependency().getOptional();
}
};
CollectRequest collectRequest = new CollectRequest();
collectRequest.setRoot( new Dependency( artifact, JavaScopes.COMPILE )
);
collectRequest.setRepositories( Booter.newRepositories( system, session
) );
DependencyRequest dependencyRequest = new DependencyRequest(
collectRequest, optionalFilter );
try {
List artifactResults =
system.resolveDependencies(session,
dependencyRequest).getArtifactResults();
for (ArtifactResult artifactResult : artifactResults) {
System.out.println(artifactResult.getArtifact() + " resolved to
"
+ artifactResult.getArtifact().getFile());
}
} catch(Exception ex) {
ex.printStackTrace();
}
}
```
was:
I modified the `ResolveTransitiveDependencies.java` example in two ways:
- Modified the id to `"org.springframework:spring-context-support:2.5.6.SEC03"`
- Replaced the filter with one that excludes optional dependencies
I'm including the full code below.
Despite that, `system.resolveDependencies()` fails with a
`DependencyResolutionException when trying to resolve a bunch of optional
dependencies, sugh as `jasperreports`.
```
public static void main( String[] args )
throws Exception
{
System.out.println(
"" );
System.out.println( ResolveTransitiveDependencies.class.getSimpleName()
);
RepositorySystem system = Booter.newRepositorySystem();
RepositorySystemSession session = Booter.newRepositorySystemSession(
system );
Artifact artifact = new DefaultArtifact(
"org.springframework:spring-context-support:2.5.6.SEC03" );
DependencyFilter classpathFlter =
DependencyFilterUtils.classpathFilter( JavaScopes.COMPILE );
DependencyFilter optionalFilter = new DependencyFilter() {
@Override
public boolean accept(DependencyNode dependencyNode,
List list) {
return ! dependencyNode.getDependency().getOptional();
}
};
CollectRequest collectRequest = new CollectRequest();
[jira] [Created] (MRESOLVER-21) Maven Resolver trying to resolve optional dependencies
Cedric Beust created MRESOLVER-21:
-
Summary: Maven Resolver trying to resolve optional dependencies
Key: MRESOLVER-21
URL: https://issues.apache.org/jira/browse/MRESOLVER-21
Project: Maven Resolver
Issue Type: Bug
Components: resolver
Reporter: Cedric Beust
I modified the `ResolveTransitiveDependencies.java` example in two ways:
- Modified the id to `"org.springframework:spring-context-support:2.5.6.SEC03"`
- Replaced the filter with one that excludes optional dependencies
I'm including the full code below.
Despite that, `system.resolveDependencies()` fails with a
`DependencyResolutionException when trying to resolve a bunch of optional
dependencies, sugh as `jasperreports`.
```
public static void main( String[] args )
throws Exception
{
System.out.println(
"" );
System.out.println( ResolveTransitiveDependencies.class.getSimpleName()
);
RepositorySystem system = Booter.newRepositorySystem();
RepositorySystemSession session = Booter.newRepositorySystemSession(
system );
Artifact artifact = new DefaultArtifact(
"org.springframework:spring-context-support:2.5.6.SEC03" );
DependencyFilter classpathFlter =
DependencyFilterUtils.classpathFilter( JavaScopes.COMPILE );
DependencyFilter optionalFilter = new DependencyFilter() {
@Override
public boolean accept(DependencyNode dependencyNode,
List list) {
return ! dependencyNode.getDependency().getOptional();
}
};
CollectRequest collectRequest = new CollectRequest();
collectRequest.setRoot( new Dependency( artifact, JavaScopes.COMPILE )
);
collectRequest.setRepositories( Booter.newRepositories( system, session
) );
DependencyRequest dependencyRequest = new DependencyRequest(
collectRequest, optionalFilter );
try {
List artifactResults =
system.resolveDependencies(session,
dependencyRequest).getArtifactResults();
for (ArtifactResult artifactResult : artifactResults) {
System.out.println(artifactResult.getArtifact() + " resolved to
"
+ artifactResult.getArtifact().getFile());
}
} catch(Exception ex) {
ex.printStackTrace();
}
}
```
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (SUREFIRE-850) Document how to run TestNG JUnit 4 tests
[ https://jira.codehaus.org/browse/SUREFIRE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294284#comment-294284 ] Cedric Beust commented on SUREFIRE-850: --- FYI, TestNG supports JUnit 4 as of last week and this will be part of the next version (6.5 probably). Feedback welcome since it's brand new, you can try it from github master, or feel free to email me. Document how to run TestNG JUnit 4 tests -- Key: SUREFIRE-850 URL: https://jira.codehaus.org/browse/SUREFIRE-850 Project: Maven Surefire Issue Type: Improvement Components: documentation Affects Versions: 2.12 Reporter: Matthew Adams It's becoming a FAQ as to how to run both TestNG JUnit 4 tests in the same Maven project. I've thrown my answer into the ring at http://blog.matthewadams.me/2012/03/running-testng-junit-4-tests-in-same.html Can you please incorporate this documented strategy, or what you feel is an improvement of it, into the surefire documentation please? -- 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] Created: (SUREFIRE-739) preserve-order attribute is ignored with Surefire plugin 2.8.1
preserve-order attribute is ignored with Surefire plugin 2.8.1 -- Key: SUREFIRE-739 URL: http://jira.codehaus.org/browse/SUREFIRE-739 Project: Maven Surefire Issue Type: Bug Components: TestNG support Affects Versions: 2.8.1 Reporter: Cedric Beust This is a clone of http://jira.opensymphony.com/browse/TESTNG-477 , which I'm pasting here: preserve-order attribute is completely ignored with Surefire plugin 2.8.1 and TestNG 5.14.1. It looks like the test classes are executed in some random order instead of the one specified in testng.xml. This execution order is correct with Surefire plugin 2.5. Here is the file: !DOCTYPE suite SYSTEM http://testng.org/testng-1.0.dtd; suite name=Component Tests verbose=2 annotations=JDK test name=My Tests preserve-order=true classes class name=server.InstallTest / class name=server.ATest / class name=server.SCHTest / class name=server.PRGTest / class name=server.SIBBTest / class name=server.EDNTest / class name=server.PPVTest / /classes /test /suite -- 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-648) Make surefire plugin compatible with TestNG 5.14
[ http://jira.codehaus.org/browse/SUREFIRE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=237462#action_237462 ] Cedric Beust commented on SUREFIRE-648: --- I just fixed the problem in 5.14.2, which should appear on Maven Central within the hour. Please try it and let me know. Make surefire plugin compatible with TestNG 5.14 Key: SUREFIRE-648 URL: http://jira.codehaus.org/browse/SUREFIRE-648 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Affects Versions: 2.6 Reporter: Stevo Slavic Attachments: testng-groups.zip Latest TestNG version surefire plugin is compatible with is 5.13.1. groups configuration option does not work with 5.14. Attached example [^testng-groups.zip] works well when testng version is configured to 5.13.1, and doesn't work as expected when testng version is configured to 5.14. Same applies to failsafe plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2793) Please upload JCommander 1.0 to the Maven repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cedric Beust closed MAVENUPLOAD-2793. - Resolution: Fixed Please upload JCommander 1.0 to the Maven repository Key: MAVENUPLOAD-2793 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2793 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust This is version 1.0 of JCommander, which I created. Can you please add it to the Maven repository? Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2793) Please upload JCommander 1.0 to the Maven repository
Please upload JCommander 1.0 to the Maven repository Key: MAVENUPLOAD-2793 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2793 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust This is version 1.0 of JCommander, which I created. Can you please add it to the Maven repository? Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MREPOSITORY-23) Wrong error message [INFO] project.scm.url must be present.
Wrong error message [INFO] project.scm.url must be present. - Key: MREPOSITORY-23 URL: http://jira.codehaus.org/browse/MREPOSITORY-23 Project: Maven 2.x Repository Plugin Issue Type: Bug Reporter: Cedric Beust When I tried to create a bundle, I got the following error: $ mvn repository:bundle-create [ERROR] BUILD ERROR [INFO] [INFO] project.scm.url must be present. Yet, my pom has this value: ... scm connectionhttp://github.com/cbeust/jcommander/connection The bug is the error message: what is missing is project.scm.connection, not url. Adding this tag fixed the problem: scm urlhttp://github.com/cbeust/jcommander/url connectionhttp://github.com/cbeust/jcommander/connection /scm -- 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: (MREPOSITORY-23) Wrong error message [INFO] project.scm.url must be present.
[ http://jira.codehaus.org/browse/MREPOSITORY-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=228225#action_228225 ] Cedric Beust commented on MREPOSITORY-23: - Bad paste, I meant: Yet, my pom has this value: ... scm urlhttp://github.com/cbeust/jcommander/url You get the idea. Wrong error message [INFO] project.scm.url must be present. - Key: MREPOSITORY-23 URL: http://jira.codehaus.org/browse/MREPOSITORY-23 Project: Maven 2.x Repository Plugin Issue Type: Bug Reporter: Cedric Beust When I tried to create a bundle, I got the following error: $ mvn repository:bundle-create [ERROR] BUILD ERROR [INFO] [INFO] project.scm.url must be present. Yet, my pom has this value: ... scm connectionhttp://github.com/cbeust/jcommander/connection The bug is the error message: what is missing is project.scm.connection, not url. Adding this tag fixed the problem: scm urlhttp://github.com/cbeust/jcommander/url connectionhttp://github.com/cbeust/jcommander/connection /scm -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2689) TestNG 5.11
TestNG 5.11 --- Key: MAVENUPLOAD-2689 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2689 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.11-bundle.jar Hi guys, Could you please publish TestNG 5.11, which I just released? Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2530) TestNG 5.10
TestNG 5.10 --- Key: MAVENUPLOAD-2530 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2530 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.10beta-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-2530) TestNG 5.10
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cedric Beust closed MAVENUPLOAD-2530. - Resolution: Fixed I attached the wrong bundle, please ignore this and I'll file a new upload request. TestNG 5.10 --- Key: MAVENUPLOAD-2530 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2530 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.10beta-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] Created: (MAVENUPLOAD-2531) TestNG 5.10
TestNG 5.10 --- Key: MAVENUPLOAD-2531 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2531 Project: Maven Upload Requests Issue Type: Wish Reporter: Cedric Beust Attachments: testng-5.10-bundle.jar I am the TestNG creator. -- 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-2012) TestNG 5.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=130557#action_130557 ] Cedric Beust commented on MAVENUPLOAD-2012: --- Yup, go ahead. Thanks for doing this, Dan! TestNG 5.8 -- Key: MAVENUPLOAD-2012 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2012 Project: maven-upload-requests Issue Type: Task Reporter: Dan Fabulich Attachments: testng-5.8-bundle.jar TestNG 5.8. I'm not a developer, but I'll happily lend a hand. Created using TestNG's new dist-maven-bundle ant task, but against the 5.8 tag which doesn't include this source. That makes this bundle a one-off, so there may be errors. -- 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
