[JBoss JIRA] (SHRINKWRAP-490) Allow ExplodedExporter to export directly into a target directory
by Aslak Knutsen (JIRA)
Aslak Knutsen created SHRINKWRAP-490:
----------------------------------------
Summary: Allow ExplodedExporter to export directly into a target directory
Key: SHRINKWRAP-490
URL: https://issues.jboss.org/browse/SHRINKWRAP-490
Project: ShrinkWrap
Issue Type: Feature Request
Components: api, impl-base
Affects Versions: 1.2.2
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
The ExplodedExporter currently support
* exportExploded(parent)
* exportExploded(parent, targetName)
exportExploded(parent) automatically append archive.name to the output path.
We're currently missing a way to write directly to a given directory with out having to do a little dance like:
{code}
File target = new File("some/dir");
archive.as(ExplodedExporter.class).exportExploded(target.getParent(), target.getName());
{code}
Propose new ExplodedExport method exportExplodedInto(File target)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (SHRINKRES-222) Environment variables are not replaced when using ParsedPomFile.getProperties()
by Matous Jobanek (JIRA)
[ https://issues.jboss.org/browse/SHRINKRES-222?page=com.atlassian.jira.plu... ]
Matous Jobanek commented on SHRINKRES-222:
------------------------------------------
Hi, I guess that you are trying to resolve pom.xml file that is not in your project directory, is it right? In this case, SWR doesn't replace the environments, that's right - I can have a look if it is possible to implement it.
If the pom.xml file is in your project directory, I would recommend not to use the original file, but the generated one in the {{/target}} directory. There the pom.xml files should be generated with and the properties should be replaced.
> Environment variables are not replaced when using ParsedPomFile.getProperties()
> -------------------------------------------------------------------------------
>
> Key: SHRINKRES-222
> URL: https://issues.jboss.org/browse/SHRINKRES-222
> Project: ShrinkWrap Resolvers
> Issue Type: Bug
> Components: maven
> Affects Versions: 2.1.1
> Environment: Windows 7 x64
> Reporter: Falko M.
>
> In Maven you can define properties using environment variables, e.g.:
> {{<someProp>$\{env.SOME_ENV\}<someProp>}}
> See also: http://books.sonatype.com/mvnref-book/reference/resource-filtering-sect-p...
> On the command line, those placeholders a replaced as expected. This can be checked via {{mvn help:effective-pom}}.
> Unfortunately, {{ParsedPomFile.getProperties()}} does *not* replace those placeholders. It returns them "as is" (e.g. {{"$\{env.SOME_ENV\}"}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months