[JBoss JIRA] (SHRINKRES-136) System scoped dependencies shouldn't be added to WAR
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-136?page=com.atlassian.jira.plu... ]
Karel Piwko closed SHRINKRES-136.
---------------------------------
Closing issues. Released as a part of 2.0.0-beta-4 release.
> System scoped dependencies shouldn't be added to WAR
> ----------------------------------------------------
>
> Key: SHRINKRES-136
> URL: https://issues.jboss.org/browse/SHRINKRES-136
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: impl-maven
> Affects Versions: 2.0.0-beta-3
> Reporter: Ron Šmeral
> Assignee: Karel Piwko
> Fix For: 2.0.0-beta-4
>
>
> When resolving dependencies with {{importRuntimeDependencies}} and adding them to an archive as in
> {code}
> File[] libs = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeDependencies().asFile();
> ShrinkWrap.create(WebArchive.class, "seam-blog.war").addAsLibraries(libs);
> {code}
> system-scoped dependencies are resolved and added to the archive as well.
> This should not happen and should be aligned with the behaviour of the maven war plugin, as described in this issue: https://jira.codehaus.org/browse/MWAR-23.
--
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, 5 months
[JBoss JIRA] (SHRINKRES-129) Unstable test with classpath resources do to file:// protocol
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-129?page=com.atlassian.jira.plu... ]
Karel Piwko closed SHRINKRES-129.
---------------------------------
Closing issues. Released as a part of 2.0.0-beta-4 release.
> Unstable test with classpath resources do to file:// protocol
> -------------------------------------------------------------
>
> Key: SHRINKRES-129
> URL: https://issues.jboss.org/browse/SHRINKRES-129
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: impl-maven
> Affects Versions: 2.0.0-beta-3
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Fix For: 2.0.0-beta-4
>
>
> Following test might fail based on underlying filesystem:
> org.jboss.shrinkwrap.resolver.impl.maven.integration.ArtifactDependenciesTestCase.pomBasedArtifactLocatedInsideJar
> The problem is about:
> file://./target/repository, which is not a valid path. File protocol expects an absolute path.
> The problem is not reproducible on all platforms.
--
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, 5 months
[JBoss JIRA] (SHRINKRES-77) Align functionality from MavenResolutionFilter with Aether DependencyFilter
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-77?page=com.atlassian.jira.plug... ]
Karel Piwko closed SHRINKRES-77.
--------------------------------
Closing issues. Released as a part of 2.0.0-beta-4 release.
> Align functionality from MavenResolutionFilter with Aether DependencyFilter
> ---------------------------------------------------------------------------
>
> Key: SHRINKRES-77
> URL: https://issues.jboss.org/browse/SHRINKRES-77
> Project: ShrinkWrap Resolvers
> Issue Type: Feature Request
> Components: api-maven
> Affects Versions: 2.0.0-alpha-4
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Labels: api-change
> Fix For: 2.0.0-beta-4
>
>
> Aether is able to filter based on path to the parent of dependency resolution. This is handy in order to create a filter which could filter based on level-nesting of the dependency itself, which is useful for lazy loading dependencies.
> We need to be able to pass List<DependencyNode> parents equivalent to the filter.
--
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, 5 months
[JBoss JIRA] (SHRINKRES-1) MavenImporter does not import MANIFEST.MF file
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-1?page=com.atlassian.jira.plugi... ]
Karel Piwko closed SHRINKRES-1.
-------------------------------
Closing issues. Released as a part of 2.0.0-beta-4 release.
> MavenImporter does not import MANIFEST.MF file
> ----------------------------------------------
>
> Key: SHRINKRES-1
> URL: https://issues.jboss.org/browse/SHRINKRES-1
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-3
> Reporter: Karel Piwko
> Assignee: Karel Piwko
> Fix For: 2.0.0-beta-4
>
>
> MavenImporter packages intermediate results from target directory of a Maven project.
> However, for MANIFEST.MF, this file is added later on during package phase, so it is not included in the file.
> Solving this issue is cumbersome, because this file is created as the archive is constructed. We have to somehow emulate Maven archiver to get the file before the jar/war/ear packaging is done.
--
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, 5 months