[JBoss JIRA] (SHRINKRES-167) Update jboss-parent to latest version (12)
by Karel Piwko (JIRA)
Karel Piwko created SHRINKRES-167:
-------------------------------------
Summary: Update jboss-parent to latest version (12)
Key: SHRINKRES-167
URL: https://issues.jboss.org/browse/SHRINKRES-167
Project: ShrinkWrap Resolvers
Issue Type: Component Upgrade
Components: build-resources
Affects Versions: 2.0.2
Reporter: Karel Piwko
Assignee: Andrew Rubinger
Fix For: 2.1.0
Update jboss-parent to recent version.
During the update:
* custom compiler plugin configuration can be removed
* surefire configuration can be updated to forkCount, reuseForks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 2 months
[JBoss JIRA] (SHRINKRES-168) Update ShrinkWrap to 1.2.1
by Karel Piwko (JIRA)
Karel Piwko created SHRINKRES-168:
-------------------------------------
Summary: Update ShrinkWrap to 1.2.1
Key: SHRINKRES-168
URL: https://issues.jboss.org/browse/SHRINKRES-168
Project: ShrinkWrap Resolvers
Issue Type: Component Upgrade
Components: build-resources
Affects Versions: 2.0.2
Reporter: Karel Piwko
Assignee: Andrew Rubinger
Fix For: 2.1.0
ShrinkWrap Core should be update to latest available version, 1.2.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 2 months
[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ]
Karel Piwko commented on SHRINKRES-140:
---------------------------------------
As for the plugin, I have figure out following:
1/ aether-api/impl/spi is by default not available on plugin classpath
2/ you need to mess with ClassRealm to get access to Aether libraries
3/ however, you get libraries packaged in Maven. In Maven 3.1.0 or 3.1.1, there is 0.9.0.M2, in Resolver we rely on 0.9.0.M4
4/ while when used externally it does not matter, in plugin it does
5/ we rely on aether-connector packages, that were not released for 0.9.0.M2, but there might be alternatives
6/ Maven 3.2.0 experimental build is still using 0.9.0.M2
So, there are two options:
a/ We can downgrade to 0.9.0.M2.
b/ We can drop plugin goal dependency tree
Seems to me it would be better to use the same deps as available in Maven. Good part is with changed Maven setup, we would actually verify SHRINKRES-26.
.
> Update Aether implementation to org.eclipse.aether one
> ------------------------------------------------------
>
> Key: SHRINKRES-140
> URL: https://issues.jboss.org/browse/SHRINKRES-140
> Project: ShrinkWrap Resolvers
> Issue Type: Component Upgrade
> Components: impl-maven
> Affects Versions: 2.0.0-beta-5
> Reporter: Karel Piwko
> Assignee: Michal Matloka
>
> Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version.
> Update should not affect user at all, it should comprise of replacing imports with new ones.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 2 months
[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ]
Karel Piwko commented on SHRINKRES-140:
---------------------------------------
I have asked about versioning because we have a plenty of people that are waiting for Maven 3.1.x support. Yet, we have some plans to add stuff in 2.1.0, such as Gradle importer. I don't want to make Maven 3.1.x support only part of 2.1.0-alpha-2 and force people wait until we release 2.1.0, they won't move from stable to alpha. Maybe we could just make 2.1.0, make 2.1.0-aplha-1 content + Gradle a part of 2.2.0-alpha-1 and directly continue on 2.2.0-alpha-1 development.
BTW, I still haven't fixed the plugin - it's dependency-tree goal. I have no idea what is going weird there, for some reason Maven is not putting some of aether libs on classpath no matter what I do. If we are going to release next minor version, I would be for dropping that functionality ;-)
[~mmatloka] as I fix the plugin, I'll run the sample app ;-).
> Update Aether implementation to org.eclipse.aether one
> ------------------------------------------------------
>
> Key: SHRINKRES-140
> URL: https://issues.jboss.org/browse/SHRINKRES-140
> Project: ShrinkWrap Resolvers
> Issue Type: Component Upgrade
> Components: impl-maven
> Affects Versions: 2.0.0-beta-5
> Reporter: Karel Piwko
> Assignee: Michal Matloka
>
> Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version.
> Update should not affect user at all, it should comprise of replacing imports with new ones.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 2 months
[JBoss JIRA] (SHRINKRES-166) org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-166?page=com.atlassian.jira.plu... ]
Karel Piwko commented on SHRINKRES-166:
---------------------------------------
Hi Abhijit,
what version of ShrinkWrap Resolvers are you using? What Maven version are you using?
Also, could you post/attach your settings.xml content?
Thanks,
Karel
> org.jboss.shrinkwrap.resolver.api.NoResolvedResultException
> -----------------------------------------------------------
>
> Key: SHRINKRES-166
> URL: https://issues.jboss.org/browse/SHRINKRES-166
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Environment: Jboss EAP 6.5, ShrinkWrap, Arquillian, Teiid
> Reporter: Abhijit Vikash
> Priority: Critical
>
> Feb 10, 2014 4:01:18 PM org.jboss.shrinkwrap.resolver.impl.maven.logging.LogRepositoryListener artifactDescriptorInvalid
> WARNING: Invalid artifact descriptor for org.jboss.teiid:teiid-client:jar:8.2.0.Final: 4 problems were encountered while building the effective model for org.jboss.teiid:teiid-client:8.2.0.Final
> [ERROR] Invalid packaging for parent POM org.jboss.teiid:teiid-parent:8.2.0.Final, must be "pom" but is "jar" @ org.jboss.teiid:teiid-parent:8.2.0.Final
> [ERROR] 'dependencies.dependency.version' for org.jboss.teiid:teiid-common-core:jar is missing. @
> [ERROR] 'dependencies.dependency.version' for org.jboss.teiid:teiid-common-core:test-jar is missing. @
> [ERROR] 'dependencies.dependency.version' for org.jboss.modules:jboss-modules:jar is missing. @
> org.jboss.shrinkwrap.resolver.api.NoResolvedResultException: Unable to collect/resolve dependency tree for a resulution due to: The following artifacts could not be resolved: org.hibernate:hibernate-core:jar:4.2.0.Final-redhat-1, org.hibernate:hibernate-entitymanager:jar:4.2.0.Final-redhat-1: Could not transfer artifact org.hibernate:hibernate-core:jar:4.2.0.Final-redhat-1 from/to jboss-ip-repository (http://maven.repository.redhat.com/techpreview/ip6/6.0.0.Beta/maven-repos...): No connector available to access repository jboss-ip-repository (http://maven.repository.redhat.com/techpreview/ip6/6.0.0.Beta/maven-repos...) of type default using the available factories WagonRepositoryConnectorFactory, caused by: No connector available to access repository jboss-ip-repository (http://maven.repository.redhat.com/techpreview/ip6/6.0.0.Beta/maven-repos...) of type default using the available factories WagonRepositoryConnectorFactory
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.wrapException(MavenWorkingSessionImpl.java:497)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.resolveDependencies(MavenWorkingSessionImpl.java:262)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.using(MavenStrategyStageBaseImpl.java:67)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:49)
> at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:38)
> at com.nielsen.engineering.mediaworks.dataservices.services.test.ejb.PanelInfoServiceBeanTest.createArchive(PanelInfoServiceBeanTest.java:76)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94)
> at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:57)
> at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:100)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.testng.Arquillian.arquillianBeforeClass(Arquillian.java:103)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
> at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:173)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:105)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1125)
> at org.testng.TestRunner.privateRun(TestRunner.java:749)
> at org.testng.TestRunner.run(TestRunner.java:600)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274)
> at org.testng.SuiteRunner.run(SuiteRunner.java:223)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:995)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:920)
> at org.testng.TestNG.run(TestNG.java:856)
> at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:72)
> at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:88)
> at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:101)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
> at $Proxy0.invoke(Unknown Source)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> 2014-02-10 16:01:19,285 ERROR [connection:105].handleException(): JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
> Tests run: 15, Failures: 1, Errors: 0, Skipped: 8, Time elapsed: 66.118 sec <<< FAILURE!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 2 months