May 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKWRAP-457) Archive imported using ZipExporter is exported with wrong extension

by Michal Matloka (JIRA)

Michal Matloka created SHRINKWRAP-457: ----------------------------------------- Summary: Archive imported using ZipExporter is exported with wrong extension Key: SHRINKWRAP-457 URL: https://issues.jboss.org/browse/SHRINKWRAP-457 Project: ShrinkWrap Issue Type: Bug Reporter: Michal Matloka When e.g. ear is imported using ZipImporter, when exporting as EnterpriseArchive it gets .jar extensions. It is visible e.g. when creating @Deployment with Arquillian. Imported .ear becomes .jar, what is not handled properly by the application server (deployment does not work properly). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-127) Use global maven configuration from M2_HOME/conf

by Michal Matloka (JIRA)

Michal Matloka created SHRINKRES-127: ---------------------------------------- Summary: Use global maven configuration from M2_HOME/conf Key: SHRINKRES-127 URL: https://issues.jboss.org/browse/SHRINKRES-127 Project: ShrinkWrap Resolvers Issue Type: Enhancement Affects Versions: 2.0.0-beta-3 Reporter: Michal Matloka Assignee: Andrew Rubinger Currently SWR uses configuration from user.home directory and from locations pointed by old maven 2 properties (e.g. org.apache.maven.global-settings). Global settings from M2_HOME directory are currently not included. According to http://maven.apache.org/settings.html {quote} There are two locations where a settings.xml file may live: The Maven install: $M2_HOME/conf/settings.xml A user's install: $\{user.home}/.m2/settings.xml The former settings.xml are also called global settings, the latter settings.xml are referred to as user settings. If both files exists, their contents gets merged, with the user-specific settings.xml being dominant. {quote} Related code: https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-126) Support for p2 repositories

by Michal Matloka (JIRA)

Michal Matloka created SHRINKRES-126: ---------------------------------------- Summary: Support for p2 repositories Key: SHRINKRES-126 URL: https://issues.jboss.org/browse/SHRINKRES-126 Project: ShrinkWrap Resolvers Issue Type: Enhancement Reporter: Michal Matloka Assignee: Andrew Rubinger [~gastaldi] has sent me an issue they had with aether in Forge saying we might have similiar problem in SWR: FORGE-866 https://github.com/forge/core/commit/7acb9217bdff22ed0084fd853002d3e466a9... According to [~kpiwko] usage with p2 repositories was never tested. Support for p2 repositires probably needs to be verified. -- 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

11 years

1
0
0 / 0

[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 updated SHRINKRES-1: -------------------------------- Affects Version/s: 2.0.0-beta-3 > 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 > > 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

11 years

1
0
0 / 0

[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 updated SHRINKRES-1: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/shrinkwrap/resolver/pull/46 Adding support for Manifest in Maven Importer. Minor additions to the API were required. [~alrubinger], could you please review you like the changes as much as I do ;-)? > MavenImporter does not import MANIFEST.MF file > ---------------------------------------------- > > Key: SHRINKRES-1 > URL: https://issues.jboss.org/browse/SHRINKRES-1 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-112) MavenImporter ignores AcceptScopesStrategy for dependency inclusion

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-112?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-112: ---------------------------------- Fix Version/s: 2.0.0-beta-4 > MavenImporter ignores AcceptScopesStrategy for dependency inclusion > ------------------------------------------------------------------- > > Key: SHRINKRES-112 > URL: https://issues.jboss.org/browse/SHRINKRES-112 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0-beta-2 > Reporter: Karel Piwko > Priority: Blocker > Fix For: 2.0.0-beta-4 > > > AcceptScopesStrategy is not correctly propagated: > {code} > @Deployment(testable = false) > public static WebArchive createDeployment() > { > return ShrinkWrap.create(MavenImporter.class) > .loadPomFromFile("pom.xml") > .importBuildOutput(new AcceptScopesStrategy(ScopeType.COMPILE, ScopeType.RUNTIME)) > .as(WebArchive.class); > } > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-126) JavaDoc incorrect for parameters

by Ralf Battenfeld (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-126?page=com.atlassian.jira.pl... ] Ralf Battenfeld commented on SHRINKDESC-126: -------------------------------------------- Hi Michal Jesper is asking for this to be fixed in the 2.0.0-X branch. DO you have time to fix it? Tx, Ralf > JavaDoc incorrect for parameters > -------------------------------- > > Key: SHRINKDESC-126 > URL: https://issues.jboss.org/browse/SHRINKDESC-126 > Project: ShrinkWrap Descriptors > Issue Type: Bug > Components: metadata-parser > Affects Versions: 2.0.0-alpha-3 > Reporter: Jesper Pedersen > Assignee: Michal Matloka > > The generated .java files from the metadata-parser gives: > {noformat} > [javadoc] /xyz/build/embedded/src/main/java/org/jboss/jca/embedded/dsl/datasources11/impl/ConfigPropertyTypeImpl.java:58: warning - @param argument "configPropertyType" is not a parameter name. > {noformat} > for > {noformat} > /** > * Sets the body text for the element <code>config-propertyType</code> > * @param configPropertyType the value for the body text <code>config-propertyType</code> > * @return the current instance of <code>ConfigPropertyType<T></code> > */ > public ConfigPropertyType<T> text(String value) > { > childNode.text(value); > return this; > } > {noformat} > It should be 'value' instead. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-131) Findbugs: Namespace

by Ralf Battenfeld (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-131?page=com.atlassian.jira.pl... ] Ralf Battenfeld commented on SHRINKDESC-131: -------------------------------------------- Hi Andrew I was sending a pull request: https://github.com/shrinkwrap/descriptors/pull/85 a while ago. I had to cancel the previous request and rebased the change to the new branch. Is that may the problem? Let me know if you need more for this pull request. Tx, Ralf > Findbugs: Namespace > ------------------- > > Key: SHRINKDESC-131 > URL: https://issues.jboss.org/browse/SHRINKDESC-131 > Project: ShrinkWrap Descriptors > Issue Type: Bug > Components: metadata-parser > Affects Versions: 2.0.0-alpha-4 > Reporter: Jesper Pedersen > Assignee: Ralf Battenfeld > Priority: Minor > Attachments: shrinkdesc-131.patch > > > The following warnings are found by findbugs of the code generated by the metadata parser: > {noformat} > WMI Method org.jboss.jca.embedded.dsl.datasources10.impl.DatasourcesDescriptorImpl.getNamespaces() makes inefficient use of keySet iterator instead of entrySet iterator > > WMI Method org.jboss.jca.embedded.dsl.datasources10.impl.DatasourcesDescriptorImpl.removeAllNamespaces() makes inefficient use of keySet iterator instead of entrySet iterator > {noformat} -- 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

11 years

1
0
0 / 0

[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... ] Work on SHRINKRES-1 started by Karel Piwko. > MavenImporter does not import MANIFEST.MF file > ---------------------------------------------- > > Key: SHRINKRES-1 > URL: https://issues.jboss.org/browse/SHRINKRES-1 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > > 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

11 years

1
0
0 / 0

[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 reassigned SHRINKRES-1: ----------------------------------- Assignee: Karel Piwko > MavenImporter does not import MANIFEST.MF file > ---------------------------------------------- > > Key: SHRINKRES-1 > URL: https://issues.jboss.org/browse/SHRINKRES-1 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Reporter: Karel Piwko > Assignee: Karel Piwko > > 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues May 2013