[jira] [Commented] (SUREFIRE-1262) Add modulepath support
[
https://issues.apache.org/jira/browse/SUREFIRE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256455#comment-16256455
]
Hudson commented on SUREFIRE-1262:
--
SUCCESS: Integrated in Jenkins build maven-surefire-dev #86 (See
[https://builds.apache.org/job/maven-surefire-dev/86/])
[SUREFIRE-1262] Add modulepath support (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=29621dd06d00ed6d946390446ea8d2a3c04bb0c5])
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/DefaultForkConfiguration.java
* (add)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/ModulePathIT.java
* (add)
surefire-integration-tests/src/test/resources/modulepath/src/main/java/module-info.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/StartupConfiguration.java
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ClasspathForkConfiguration.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ModularClasspath.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/util/Relocator.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
* (edit) pom.xml
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/Classpath.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/AbstractPathConfiguration.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/BooterSerializer.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/util/DefaultScanResult.java
* (add) surefire-integration-tests/src/test/resources/modulepath/pom.xml
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ClasspathConfiguration.java
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/JarManifestForkConfiguration.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/AbstractSurefireMojoTest.java
* (add)
surefire-integration-tests/src/test/resources/modulepath/src/main/java/com/app/Main.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/InPluginVMSurefireStarter.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/BooterDeserializerStartupConfigurationTest.java
* (edit)
surefire-api/src/test/java/org/apache/maven/surefire/util/ScanResultTest.java
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/AbstractClasspathForkConfiguration.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/Platform.java
* (add)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ModularClasspathForkConfiguration.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkConfiguration.java
* (add)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ModularClasspathConfiguration.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/surefire/providerapi/ServiceLoader.java
* (edit)
maven-surefire-plugin/src/test/java/org/apache/maven/plugin/surefire/SurefirePluginTest.java
* (edit)
surefire-booter/src/test/java/org/apache/maven/surefire/booter/SystemUtilsTest.java
* (add)
surefire-integration-tests/src/test/resources/modulepath/src/test/java/com/app/AppTest.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/ForkConfigurationTest.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/surefire/util/RelocatorTest.java
* (edit) maven-surefire-common/pom.xml
> Add modulepath support
> --
>
> Key: SUREFIRE-1262
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1262
> Project: Maven Surefire
> Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Tibor Digana
> Fix For: Backlog
>
>
> With the Jigsaw project Java9 is extended with a modulepath. This means that
> surefire should be executed in a different way.
> When working with a modulepath, the Classpath in the MANIFEST of the
> executable jar will be ignored, you need need to add everything on
> commandline.
> Just like javadoc, the java executable has an {{@}} option, where you
> can add arguments per line. So this is the new preferred way to build the
> module-path.
> IIUC for surefire it is important to add {{--patch-module
> target/test-classes}} (was: -Xpatch) which makes it possible to use the same
>
[jira] [Created] (MSITE-803) checkstyle version 8.4 not accessible.
Ernst Reissner created MSITE-803: Summary: checkstyle version 8.4 not accessible. Key: MSITE-803 URL: https://issues.apache.org/jira/browse/MSITE-803 Project: Maven Site Plugin Issue Type: Wish Environment: One may use checkstyle plugin for various versions of checkstyle e.g. 8.4 specifying com.puppycrawl.tools checkstyle 8.4 e.g. in the pluginManagement. In contrast, it is not possible to specify this in the reporting section. As a workaround, i would prefer adding a checkstyleVersion property in the configuration. Not that by default the plugin used checkstyle 6.11.2 whereas the current is 8.4. Reporter: Ernst Reissner -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MINDEXER-108) Lift restriction on leading wildcard queries
Andreas Sewe created MINDEXER-108:
-
Summary: Lift restriction on leading wildcard queries
Key: MINDEXER-108
URL: https://issues.apache.org/jira/browse/MINDEXER-108
Project: Maven Indexer
Issue Type: Improvement
Affects Versions: 6.0
Reporter: Andreas Sewe
The {{DefaultQueryCreator}} prevents queries with leading wildcard:
{noformat}
if ( query.startsWith( "*" ) || query.startsWith( "?" ) )
{
throw new ParseException( "Query cannot start with '*' or '?'!" );
}
{noformat}
While this was necessary in older versions of Lucene, the version used now
happily executes such queries. The restriction can thus be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MNG-6302) Provide some "progress" hints
[
https://issues.apache.org/jira/browse/MNG-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252866#comment-16252866
]
Hervé Boutemy edited comment on MNG-6302 at 11/16/17 5:23 PM:
--
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/136
merged as a branch in Maven git
https://github.com/apache/maven/tree/MNG-6302_module-progress
and reworked to avoid additional line "Module i/n" but have instead
integrated at the end of "Building" line:
{noformat}[INFO]
[INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
[15/15]
[INFO]
{noformat}
was (Author: githubbot):
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/136
merged as a branch in Maven git
https://github.com/apache/maven/tree/MNG-6302_module-progress
and reworked to avoid additional line "Module i/n" but have instead
integrated at the end of "Building" line:
```
[INFO]
[INFO] Building Apache Maven Distribution 3.5.3-SNAPSHOT
[15/15]
[INFO]
```
> Provide some "progress" hints
> -
>
> Key: MNG-6302
> URL: https://issues.apache.org/jira/browse/MNG-6302
> Project: Maven
> Issue Type: New Feature
>Reporter: Romain Manni-Bucau
>
> High level need is to know when you launched a "long"/"big" build where you
> are without having to scroll for days. Some progress information would be
> neat.
> A proposal is to add the info in term of module number of total number of
> modules after the artifact logging like:
> {code}
> [INFO]
>
> [INFO] Building Foo 1.0.0-SNAPSHOT
> [INFO]
>
> [INFO] Module 10 / 100
> {code}
> If it can be more fancy it would be appreciated but this simple solution
> looks good enough to fulfill the original requirement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MPDF-81) Override the copyright footer
[ https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255482#comment-16255482 ] Hervé Boutemy commented on MPDF-81: --- I continued my work on the topic: I did DOXIA-556, to get http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/doxia-core/document.html now I think that the new configuration should just go into new fields in Document descriptor, ie pdf.xml: this descriptor did not evolve for years, but that's just because there was not so much work on pdf we just need to define what field we want to put in this descriptor to have a clean structure Currently, fields are grouped in 3 groups: meta, toc and cover Given your experience on new configuration that would be required to enhance pdf results, do you have proposals on model evolution? > Override the copyright footer > - > > Key: MPDF-81 > URL: https://issues.apache.org/jira/browse/MPDF-81 > Project: Maven PDF Plugin > Issue Type: New Feature >Affects Versions: 1.3 >Reporter: Alex O'Ree > Fix For: 1.4 > > Attachments: maven-pdf-plugin2.pdf > > > As of right now, it doesn't look possible to override the content of the > footer which is on all non-title page pages. It currently reads (c) year - > organization All rights reserved. > I don't see anywhere in the code where this is defined or in any of the > resource files. It is in the generated fo files but it's not obvious where > the xslt is. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (DOXIA-565) improve Doxia document descriptor documentation
[ https://issues.apache.org/jira/browse/DOXIA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIA-565. --- Resolution: Fixed > improve Doxia document descriptor documentation > --- > > Key: DOXIA-565 > URL: https://issues.apache.org/jira/browse/DOXIA-565 > Project: Maven Doxia > Issue Type: Improvement > Components: Core, Documentation >Affects Versions: 1.7 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 1.8 > > > not really easy to understand currently > http://maven.apache.org/doxia/doxia-archives/doxia-1.7/doxia-core/document.html > this impacts improvements expected for maven-pdf-plugin like MPDF-81 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DOXIA-556) Add support for macros in vm templates
[
https://issues.apache.org/jira/browse/DOXIA-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255331#comment-16255331
]
Hervé Boutemy commented on DOXIA-556:
-
please give examples: what you describe ĥappens at misc levels
see http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/index.html
- {{.vm}} is processed by Velocity, with Velocity macros
- then the result is processed by Doxia, like any content that has not been
processed by Velocity, with Doxia Macros
Maybe you're hit by Velocity and Markdown conflict on hash sign: I managed to
add some explanations for next maven-site-plugin version in
http://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/examples/creating-content.html#Filtering
I suppose it's the issue you're facing: please confirm that I can close this
issue
> Add support for macros in vm templates
> --
>
> Key: DOXIA-556
> URL: https://issues.apache.org/jira/browse/DOXIA-556
> Project: Maven Doxia
> Issue Type: Improvement
>Reporter: Alex O'Ree
>
> see also [DOXIA-492]
> The current support for MACROs, such as TOC, appears to not function in
> templated/filtered documents, such as markdown.md.vm. Would it be possible to
> enabling MACRO support in .vm templates?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DOXIA-565) improve Doxia document descriptor documentation
[ https://issues.apache.org/jira/browse/DOXIA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255264#comment-16255264 ] Hudson commented on DOXIA-565: -- SUCCESS: Integrated in Jenkins build doxia #3 (See [https://builds.apache.org/job/doxia/3/]) [DOXIA-565] improved Doxia Document descriptor reference (hboutemy: [http://gitbox.apache.org/repos/asf/?p=maven-doxia.git=commit=1e62dde86b1bcf0bbfec37e2a5f0b2e6d178bacb]) * (edit) doxia-core/src/main/mdo/document.mdo * (edit) doxia-core/src/site/site.xml * (delete) doxia-core/src/site/apt/using-document-xsd.apt > improve Doxia document descriptor documentation > --- > > Key: DOXIA-565 > URL: https://issues.apache.org/jira/browse/DOXIA-565 > Project: Maven Doxia > Issue Type: Improvement > Components: Core, Documentation >Affects Versions: 1.7 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 1.8 > > > not really easy to understand currently > http://maven.apache.org/doxia/doxia-archives/doxia-1.7/doxia-core/document.html > this impacts improvements expected for maven-pdf-plugin like MPDF-81 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DOXIASITETOOLS-4) DocumentModel needs to be more general
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255233#comment-16255233 ] Hervé Boutemy commented on DOXIASITETOOLS-4: document model moved from doxia-doc-renderer to doxia core in http://svn.apache.org/r595393 > DocumentModel needs to be more general > -- > > Key: DOXIASITETOOLS-4 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-4 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Doc renderer >Affects Versions: 1.0-alpha-9 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.1 > > > The DocumentModel needs to provide much more information in order to be > useful. > * DocumentMeta should provide all the information that could go on a cover > page: companyLogo, projectLogo, coverProjectName, coverVersion, coverType, > coverProjectCompany, coverDate > * DocumentTOC needs to handle nested toc items > There's probably more, this is just taken from my current needs for the pdf > plugin. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DOXIA-565) improve Doxia document descriptor documentation
Hervé Boutemy created DOXIA-565: --- Summary: improve Doxia document descriptor documentation Key: DOXIA-565 URL: https://issues.apache.org/jira/browse/DOXIA-565 Project: Maven Doxia Issue Type: Improvement Components: Core, Documentation Affects Versions: 1.7 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: 1.8 not really easy to understand currently http://maven.apache.org/doxia/doxia-archives/doxia-1.7/doxia-core/document.html this impacts improvements expected for maven-pdf-plugin like MPDF-81 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SUREFIRE-1445) Properties from configuration POM are not passed to Provider on JDK 9
Marc Philipp created SUREFIRE-1445:
--
Summary: Properties from configuration POM are not passed to
Provider on JDK 9
Key: SUREFIRE-1445
URL: https://issues.apache.org/jira/browse/SUREFIRE-1445
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin, Maven Surefire Plugin
Affects Versions: 2.20.1, 2.20, 2.19.1
Environment: JDK 9
Reporter: Marc Philipp
Priority: Blocker
Given the POM below, the {{JUnitPlatformProvider}} can read {{"excludeTags"}} =
{{"slow"}} from {{ProviderParameters.getProviderProperties()}} when it runs on
JDK 8 but not on JDK 9.
The reason is that the constructor of {{SurefireProperties}} relies on an
implementation detail of the class it extends, namely that {{putAll()}} will
call {{put()}} for each entry. However, while {{Properties}} does that on JDK
8, it doesn't on JDK 9.
Here's a link to the line in {{SurefireProperties}}:
https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireProperties.java#L62
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
junit5
tagging
1.0-SNAPSHOT
maven-surefire-plugin
2.19.1
slow
org.junit.platform
junit-platform-surefire-provider
1.0.2
org.junit.jupiter
junit-jupiter-engine
5.0.2
org.junit.jupiter
junit-jupiter-api
5.0.2
test
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SUREFIRE-1444) org.apache.maven.surefire.booter.SurefireBooterForkException
rfs created SUREFIRE-1444: - Summary: org.apache.maven.surefire.booter.SurefireBooterForkException Key: SUREFIRE-1444 URL: https://issues.apache.org/jira/browse/SUREFIRE-1444 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.20.1 Environment: Windows 7 Pro 64 bits Maven 3.5.2 , jdk 1.8.0_152 Reporter: rfs mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1 maven repository is deleted before but same result. mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1 [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 9.490 s [INFO] Finished at: 2017-11-16T08:58:19+01:00 [INFO] Final Memory: 35M/290M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on project project-name: There are test fa ilures. [ERROR] [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. [ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur efirebooter7359328160006854832.jar D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 2017-11-16T08-58-14_352-jvmRun1 surefire80634 62497440390334tmp surefire_0627218662296028436tmp" [ERROR] Error occurred in starting fork, check output in log [ERROR] Process Exit Code: 1 [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exi t called? [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur efirebooter7359328160006854832.jar D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195 2017-11-16T08-58-14_352-jvmRun1 surefire80634 62497440390334tmp surefire_0627218662296028436tmp" [ERROR] Error occurred in starting fork, check output in log [ERROR] Process Exit Code: 1 [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686) [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535) [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280) [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245) [ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124) [ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954) [ERROR] at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832) [ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) [ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:955) [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290) [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [ERROR] at
[jira] [Commented] (MDEP-323) dependency:go-offline -DexcludeGroupIds=xxxx still try to resolve artifacts in the excluded group xxxx
[
https://issues.apache.org/jira/browse/MDEP-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254955#comment-16254955
]
Markus Windhager commented on MDEP-323:
---
I also got the same Issue.
The "com.oracle.adf.library:ADF-Library-Dependencies:12.1.3-0-0" pom is an
artificial dependency automatically created by JDeveloper.
The adf-library-dependencies pom is different for each and every module and
should therefore never be deployed to the artifactory...
So fixing this behaviour is crucial for me.
{{$ mvn -v
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T21:39:06+02:00)
Maven home: C:\Development\apache-maven-3.5.0\bin\..
Java version: 1.8.0_92, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_92\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
$ mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.2:go-offline -f
pom.xml -DexcludeArtifactIds=ADF-Library-Dependencies
[WARNING] The POM for
com.oracle.adf.library:ADF-Library-Dependencies:pom:12.1.3-0-0 is missing, no
dependency information available
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 8.355 s
[INFO] Finished at: 2017-11-16T09:26:12+01:00
[INFO] Final Memory: 16M/201M
[INFO]
[ERROR] Failed to execute goal on project Test: Could not resolve dependencies
for project test:Test:jar:1.0-SNAPSHOT:
The following artifacts could not be resolved:
com.oracle.adf.library:ADF-Library-Dependencies:pom:12.1.3-0-0}}
> dependency:go-offline -DexcludeGroupIds= still try to resolve artifacts
> in the excluded group
> --
>
> Key: MDEP-323
> URL: https://issues.apache.org/jira/browse/MDEP-323
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
>Affects Versions: 2.3
> Environment: windows / cygwin xp64 bit / bash / maven 3.0.3
>Reporter: Jason Pyeron
> Attachments: go-offline_copy-dependencies_patch_sample.zip, test.tgz
>
>
> see thread:
> http://mail-archives.apache.org/mod_mbox/maven-users/201109.mbox/%3c0B02C46601D44673A4A2DF4C4F907E9E@black%3e
> in attached sample pom structure:
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.3:go-offline
> -DexcludeGroupIds=us.pdinc.foo.maven.test
> fails
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSITE-802) Support more than one directory
[ https://issues.apache.org/jira/browse/MSITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254946#comment-16254946 ] Hervé Boutemy commented on MSITE-802: - thanks for the example: it's a report without taking time to create a report plugin :) notice reading shelldocs documentation, it looks like it directly generates HTML (which could directly go to target/site), but in your snippet, it generates Markdown and let the user find a tool to translate Markdown to html (that's why Markdown has to go into target/generated-site/markdown, to let maven-site-plugin translate it to html with site's Maven skin) I think I'll add a section in http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html on "Generating Content" that will introduce the different ways to generate content in fact, I think this will cover a long overdue documentation: how to create a reporting plugin? Interesting and useful, but more complex We're driving a new maven-site-plugin release soon for Java 9 compatibility, I need to work on this soon... > Support more than one directory > --- > > Key: MSITE-802 > URL: https://issues.apache.org/jira/browse/MSITE-802 > Project: Maven Site Plugin > Issue Type: Task >Reporter: Allen Wittenauer >Assignee: Hervé Boutemy >Priority: Minor > Fix For: 3.7 > > > It would be great if maven-site-plugin could support more than one site > directory per module. Specifically, I'm looking for a way to process > generated content without copying all of src/site into target where my > generated content is sitting or using a separate module that only handles > generated content to get aggregated later. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
