[jira] [Commented] (MCOMPILER-44) 'outputDirectory' configuration property should not be read-only
[ https://issues.apache.org/jira/browse/MCOMPILER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17686873#comment-17686873 ] Jin Kwon commented on MCOMPILER-44: --- I my case I need to compile same source into multiple directories for further processing task and deploy multiple artifacts with different classifier. > 'outputDirectory' configuration property should not be read-only > > > Key: MCOMPILER-44 > URL: https://issues.apache.org/jira/browse/MCOMPILER-44 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Ian P. Springer >Assignee: Carlos Sanchez Gonzalez >Priority: Major > > I am trying to set up a 'dev' build profile that, when enabled, will cause my > artifacts to be built directly to an exploded ejb-jar deployment dir, instead > of target/classes/. The purpose is to make the development process more > efficient by skipping a number of time-consuming intermediate mvn steps (i.e. > jarring the artifact, copying the jar to the local repo, unjarring the > artifact to its deploy/test location). > Since profiles do not allow you to override project.build.outputDirectory, I > proceeded to override the outputDirectory config props in the > maven-clean-plugin, the maven-compiler-plugin, and the > maven-resources-plugin. The maven-clean-plugin and the maven-resources-plugin > allow me to modify the outputDirectory without any complaints, but the > maven-compiler-plugin does not... It fails with the following error: > [INFO] Error configuring: org.apache.maven.plugins:maven-compiler-plugin. > Reason: ERROR: Cannot override read-only parameter: outputDirectory in goal: > compiler:compile > Please make this property non-read-only. Making it read-only seriously limits > the flexibility of Maven2. > Thanks, > Ian -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7233) doesn't work when an another trigger exists
[
https://issues.apache.org/jira/browse/MNG-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411754#comment-17411754
]
Jin Kwon commented on MNG-7233:
---
A sentence with a question mark is a question?
> doesn't work when an another trigger exists
> --
>
> Key: MNG-7233
> URL: https://issues.apache.org/jira/browse/MNG-7233
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap Build
>Affects Versions: 3.6.3
>Reporter: Jin Kwon
>Priority: Major
>
> I have following profiles.
> {code:xml}
>
> active-by-default
>
> true
>
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> provided
>
>
>
>
> java8
>
> (,1.8]
>
>
>
>
> com.github.wvengen
> proguard-maven-plugin
>
>
> ${java.home}/lib/rt.jar
> ${java.home}/lib/jce.jar
> ${java.home}/lib/jsse.jar
>
>
>
>
>
>
>
> java9
>
> [1.9,)
>
>
>
>
> com.github.wvengen
> proguard-maven-plugin
>
>
> ${java.home}/jmods/java.base.jmod
>
>
>
>
>
>
> {code}
> Those two {{java-}} profiles are for ProGuard.
> And I found the {{active-by-default}} profile doesn't work.
> I found it works when I remove one of those {{java-}} profile.
> Is this intended?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MNG-7233) doesn't work when an another trigger exists
Jin Kwon created MNG-7233:
-
Summary: doesn't work when an another trigger
exists
Key: MNG-7233
URL: https://issues.apache.org/jira/browse/MNG-7233
Project: Maven
Issue Type: Bug
Components: Bootstrap Build
Affects Versions: 3.6.3
Reporter: Jin Kwon
I have following profiles.
{code:xml}
active-by-default
true
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
provided
java8
(,1.8]
com.github.wvengen
proguard-maven-plugin
${java.home}/lib/rt.jar
${java.home}/lib/jce.jar
${java.home}/lib/jsse.jar
java9
[1.9,)
com.github.wvengen
proguard-maven-plugin
${java.home}/jmods/java.base.jmod
{code}
Those two {{java-}} profiles are for ProGuard.
And I found the {{active-by-default}} profile doesn't work.
I found it works when I remove one of those {{java-}} profile.
Is this intended?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-403) Imports are wrongly modified even for excluded artifacts
[
https://issues.apache.org/jira/browse/MSHADE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSHADE-403:
Description:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
import com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
Should I relocate for each {{com.whatever}} packages from non-excluded
artifacts?
Or shouldn't those packages from excluded artifacts skipped?
was:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
import com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
Should I relocate for each {{com.whatever}} packages from non-excluded
artifacts?
> Imports are wrongly modified even for excluded artifacts
>
>
> Key: MSHADE-403
> URL: https://issues.apache.org/jira/browse/MSHADE-403
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Jin Kwon
>Priority: Major
>
> For following dependencies,
> {code:xml}
>
> org.mongodb
> mongodb-driver-reactivestreams
> ${version.org.mongodb}
> compile
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> compile
>
> {code}
> I excluded them
> {code:xml}
>
>
> org.mongodb:*
>
>
> {code}
> and relocate for other artifacts.
> {code:xml}
>
> com
> com.mycompany.relocated.com
>
> com.mycompany.**
>
>
> {code}
> Those excluded artifacts are not contained in the shaded artifact as expected.
> But I see wrongly modified imports in one of main classes.
> {code:java}
> import com.mycompany.relocated.com.mongodb.MongoClientSettings;
> import com.mycompany.relocated.com.mongodb.client.MongoClient;
> import com.mycompany.relocated.com.mongodb.client.MongoClients;
> {code}
> Should I relocate for each {{com.whatever}} packages from non-excluded
> artifacts?
> Or shouldn't those packages from excluded artifacts skipped?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-403) Imports are wrongly modified even for excluded artifacts
[
https://issues.apache.org/jira/browse/MSHADE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSHADE-403:
Description:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
import com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
Should I relocate for each {{com.whatever}} packages from non-excluded
artifacts?
was:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
import com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
> Imports are wrongly modified even for excluded artifacts
>
>
> Key: MSHADE-403
> URL: https://issues.apache.org/jira/browse/MSHADE-403
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Jin Kwon
>Priority: Major
>
> For following dependencies,
> {code:xml}
>
> org.mongodb
> mongodb-driver-reactivestreams
> ${version.org.mongodb}
> compile
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> compile
>
> {code}
> I excluded them
> {code:xml}
>
>
> org.mongodb:*
>
>
> {code}
> and relocate for other artifacts.
> {code:xml}
>
> com
> com.mycompany.relocated.com
>
> com.mycompany.**
>
>
> {code}
> Those excluded artifacts are not contained in the shaded artifact as expected.
> But I see wrongly modified imports in one of main classes.
> {code:java}
> import com.mycompany.relocated.com.mongodb.MongoClientSettings;
> import com.mycompany.relocated.com.mongodb.client.MongoClient;
> import com.mycompany.relocated.com.mongodb.client.MongoClients;
> {code}
> Should I relocate for each {{com.whatever}} packages from non-excluded
> artifacts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-403) Imports are wrongly modified even for excluded artifacts
[
https://issues.apache.org/jira/browse/MSHADE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSHADE-403:
Description:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
import com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
was:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
> Imports are wrongly modified even for excluded artifacts
>
>
> Key: MSHADE-403
> URL: https://issues.apache.org/jira/browse/MSHADE-403
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Jin Kwon
>Priority: Major
>
> For following dependencies,
> {code:xml}
>
> org.mongodb
> mongodb-driver-reactivestreams
> ${version.org.mongodb}
> compile
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> compile
>
> {code}
> I excluded them
> {code:xml}
>
>
> org.mongodb:*
>
>
> {code}
> and relocate for other artifacts.
> {code:xml}
>
> com
> com.mycompany.relocated.com
>
> com.mycompany.**
>
>
> {code}
> Those excluded artifacts are not contained in the shaded artifact as expected.
> But I see wrongly modified imports in one of main classes.
> {code:java}
> import com.mycompany.relocated.com.mongodb.MongoClientSettings;
> import com.mycompany.relocated.com.mongodb.client.MongoClient;
> import com.mycompany.relocated.com.mongodb.client.MongoClients;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-403) Imports are wrongly modified even for excluded artifacts
[
https://issues.apache.org/jira/browse/MSHADE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSHADE-403:
Description:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports from one of main class.
{code:java}
mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
was:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact.
But I see wrongly modified imports from one of main class.
{code:java}
mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
> Imports are wrongly modified even for excluded artifacts
>
>
> Key: MSHADE-403
> URL: https://issues.apache.org/jira/browse/MSHADE-403
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Jin Kwon
>Priority: Major
>
> For following dependencies,
> {code:xml}
>
> org.mongodb
> mongodb-driver-reactivestreams
> ${version.org.mongodb}
> compile
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> compile
>
> {code}
> I excluded them
> {code:xml}
>
>
> org.mongodb:*
>
>
> {code}
> and relocate for other artifacts.
> {code:xml}
>
> com
> com.mycompany.relocated.com
>
> com.mycompany.**
>
>
> {code}
> Those excluded artifacts are not contained in the shaded artifact as expected.
> But I see wrongly modified imports from one of main class.
> {code:java}
> mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
> import com.mycompany.relocated.com.mongodb.client.MongoClient;
> import com.mycompany.relocated.com.mongodb.client.MongoClients;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-403) Imports are wrongly modified even for excluded artifacts
[
https://issues.apache.org/jira/browse/MSHADE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSHADE-403:
Description:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports in one of main classes.
{code:java}
mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
was:
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact as expected.
But I see wrongly modified imports from one of main class.
{code:java}
mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
> Imports are wrongly modified even for excluded artifacts
>
>
> Key: MSHADE-403
> URL: https://issues.apache.org/jira/browse/MSHADE-403
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Jin Kwon
>Priority: Major
>
> For following dependencies,
> {code:xml}
>
> org.mongodb
> mongodb-driver-reactivestreams
> ${version.org.mongodb}
> compile
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> compile
>
> {code}
> I excluded them
> {code:xml}
>
>
> org.mongodb:*
>
>
> {code}
> and relocate for other artifacts.
> {code:xml}
>
> com
> com.mycompany.relocated.com
>
> com.mycompany.**
>
>
> {code}
> Those excluded artifacts are not contained in the shaded artifact as expected.
> But I see wrongly modified imports in one of main classes.
> {code:java}
> mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
> import com.mycompany.relocated.com.mongodb.client.MongoClient;
> import com.mycompany.relocated.com.mongodb.client.MongoClients;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MSHADE-403) Imports are wrongly relocated event for excluded artifacts
Jin Kwon created MSHADE-403:
---
Summary: Imports are wrongly relocated event for excluded artifacts
Key: MSHADE-403
URL: https://issues.apache.org/jira/browse/MSHADE-403
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 3.2.4
Reporter: Jin Kwon
For following dependencies,
{code:xml}
org.mongodb
mongodb-driver-reactivestreams
${version.org.mongodb}
compile
org.mongodb
mongodb-driver-sync
${version.org.mongodb}
compile
{code}
I excluded them
{code:xml}
org.mongodb:*
{code}
and relocate for other artifacts.
{code:xml}
com
com.mycompany.relocated.com
com.mycompany.**
{code}
Those excluded artifacts are not contained in the shaded artifact.
But I see wrongly modified imports from one of main class.
{code:java}
mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
import com.mycompany.relocated.com.mongodb.client.MongoClient;
import com.mycompany.relocated.com.mongodb.client.MongoClients;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-403) Imports are wrongly modified even for excluded artifacts
[
https://issues.apache.org/jira/browse/MSHADE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSHADE-403:
Summary: Imports are wrongly modified even for excluded artifacts (was:
Imports are wrongly relocated event for excluded artifacts)
> Imports are wrongly modified even for excluded artifacts
>
>
> Key: MSHADE-403
> URL: https://issues.apache.org/jira/browse/MSHADE-403
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Jin Kwon
>Priority: Major
>
> For following dependencies,
> {code:xml}
>
> org.mongodb
> mongodb-driver-reactivestreams
> ${version.org.mongodb}
> compile
>
>
> org.mongodb
> mongodb-driver-sync
> ${version.org.mongodb}
> compile
>
> {code}
> I excluded them
> {code:xml}
>
>
> org.mongodb:*
>
>
> {code}
> and relocate for other artifacts.
> {code:xml}
>
> com
> com.mycompany.relocated.com
>
> com.mycompany.**
>
>
> {code}
> Those excluded artifacts are not contained in the shaded artifact.
> But I see wrongly modified imports from one of main class.
> {code:java}
> mport com.mycompany.relocated.com.mongodb.MongoClientSettings;
> import com.mycompany.relocated.com.mongodb.client.MongoClient;
> import com.mycompany.relocated.com.mongodb.client.MongoClients;
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-674) Support element-list from unpacked javadoc with offlineLink
[
https://issues.apache.org/jira/browse/MJAVADOC-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308315#comment-17308315
]
Jin Kwon commented on MJAVADOC-674:
---
I'm currently doing this.
{code:xml}
org.apache.maven.plugins
maven-antrun-plugin
3.0.0
copy-element-list-to-package-list
package
run
{code}
> Support element-list from unpacked javadoc with offlineLink
> ---
>
> Key: MJAVADOC-674
> URL: https://issues.apache.org/jira/browse/MJAVADOC-674
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Components: javadoc
>Affects Versions: 3.2.0
> Environment: Apache Maven 3.6.3
> (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
> Java version: 1.8.0_281, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_281.jdk/Contents/Home/jre
> Default locale: en_KR, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
>Reporter: Jin Kwon
>Priority: Minor
> Labels: element-list, offline-link
>
> I'm not sure of duplication of this issue, but.
> When I tried to {{dependency:unpack}} a javadoc-jar and tried do
> {{offlineLink}} to the dir, I get.
> {code}
> [WARNING] javadoc: warning - Error reading file:
> /.../target/unpacked-javadoc/.../package-list
> {code}
> The unpacked javadoc dir contains {{element-list}} not {{package-list}}.
> Can anybody please make maven-javadoc-plugin detects the {{element-list}}
> file?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MJAVADOC-674) Support element-list from unpacked javadoc with offlineLink
Jin Kwon created MJAVADOC-674:
-
Summary: Support element-list from unpacked javadoc with
offlineLink
Key: MJAVADOC-674
URL: https://issues.apache.org/jira/browse/MJAVADOC-674
Project: Maven Javadoc Plugin
Issue Type: Improvement
Components: javadoc
Affects Versions: 3.2.0
Environment: Apache Maven 3.6.3
(cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec
Java version: 1.8.0_281, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk1.8.0_281.jdk/Contents/Home/jre
Default locale: en_KR, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
Reporter: Jin Kwon
I'm not sure of duplication of this issue, but.
When I tried to {{dependency:unpack}} a javadoc-jar and tried do
{{offlineLink}} to the dir, I get.
{code}
[WARNING] javadoc: warning - Error reading file:
/.../target/unpacked-javadoc/.../package-list
{code}
The unpacked javadoc dir contains {{element-list}} not {{package-list}}.
Can anybody please make maven-javadoc-plugin detects the {{element-list}} file?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MJAVADOC-651) Separate visibility control for main and test
[
https://issues.apache.org/jira/browse/MJAVADOC-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MJAVADOC-651:
--
Description:
Recently, I found myself that I have no public/projected classes in my
{{src/test/java}} directory.
Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
recommends this way.
And I failed to find a way to control the {{show}} property as successfully
separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
{{default-test-aggregate-no-fork}}(site).
was:
Recently, I found myself that I have no public/projected classes in my
{{src/test/java}} directory.
Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
recommends this way.
And I failed to find a way to control the {{show}} property as successfully
separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
{{test-aggregate-no-fork}}(site).
> Separate visibility control for main and test
> -
>
> Key: MJAVADOC-651
> URL: https://issues.apache.org/jira/browse/MJAVADOC-651
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 3.2.0
>Reporter: Jin Kwon
>Priority: Major
>
> Recently, I found myself that I have no public/projected classes in my
> {{src/test/java}} directory.
> Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
> recommends this way.
> And I failed to find a way to control the {{show}} property as successfully
> separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
> {{default-test-aggregate-no-fork}}(site).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MJAVADOC-651) Separate visibility control for main and test
Jin Kwon created MJAVADOC-651:
-
Summary: Separate visibility control for main and test
Key: MJAVADOC-651
URL: https://issues.apache.org/jira/browse/MJAVADOC-651
Project: Maven Javadoc Plugin
Issue Type: New Feature
Affects Versions: 3.2.0
Reporter: Jin Kwon
Recently, I found myself that I have no public/projected classes in my
{{src/test/java}} directory.
Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
recommends this way.
And I failed to find a way to control the {{show}} property as successfully
separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
{{test-aggregate-no-fork}}(site).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
[
https://issues.apache.org/jira/browse/MNG-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088552#comment-17088552
]
Jin Kwon commented on MNG-6895:
---
Exactly!
> Add aliasing feature for settings.xml:///servers/server
> ---
>
> Key: MNG-6895
> URL: https://issues.apache.org/jira/browse/MNG-6895
> Project: Maven
> Issue Type: New Feature
> Components: Settings
>Reporter: Jin Kwon
>Priority: Major
>
> In some cases there might be multiple server elements for the same endpoint
> with different {{id}}s.
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
> username
> {password}
>
> ...
> {code}
> Can we have an attribute look like this?
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
>
> ...
> {code}
> Or
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
[
https://issues.apache.org/jira/browse/MNG-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088493#comment-17088493
]
Jin Kwon edited comment on MNG-6895 at 4/21/20, 9:46 AM:
-
Nope. The situation is opposite. For a same endpoint of a repository, different
projects (from different divisions) uses different {{id}} in their
repositories/distributionManagement section.
Unifying the {{id}} value in such a huge organization might not possible.
was (Author: jinahya):
Nope. The situation is opposite. For a same endpoint of a repository, different
projects (from different divisions) uses different {{id}} in their
repositories/distributionManagement section.
> Add aliasing feature for settings.xml:///servers/server
> ---
>
> Key: MNG-6895
> URL: https://issues.apache.org/jira/browse/MNG-6895
> Project: Maven
> Issue Type: New Feature
> Components: Settings
>Reporter: Jin Kwon
>Priority: Major
>
> In some cases there might be multiple server elements for the same endpoint
> with different {{id}}s.
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
> username
> {password}
>
> ...
> {code}
> Can we have an attribute look like this?
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
>
> ...
> {code}
> Or
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
[
https://issues.apache.org/jira/browse/MNG-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088493#comment-17088493
]
Jin Kwon commented on MNG-6895:
---
Nope. The situation is opposite. For a same endpoint of a repository, different
projects (from different divisions) uses different {{id}} in their
repositories/distributionManagement section.
> Add aliasing feature for settings.xml:///servers/server
> ---
>
> Key: MNG-6895
> URL: https://issues.apache.org/jira/browse/MNG-6895
> Project: Maven
> Issue Type: New Feature
> Components: Settings
>Reporter: Jin Kwon
>Priority: Major
>
> In some cases there might be multiple server elements for the same endpoint
> with different {{id}}s.
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
> username
> {password}
>
> ...
> {code}
> Can we have an attribute look like this?
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
>
> ...
> {code}
> Or
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
[
https://issues.apache.org/jira/browse/MNG-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-6895:
--
Description:
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
other
...
{code}
Or
{code:xml}
...
...
some
username
{password}
...
{code}
was:
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
other
...
{code}
Or
{code:xml}
...
...
some
username
{password}
...
{code}
> Add aliasing feature for settings.xml:///servers/server
> ---
>
> Key: MNG-6895
> URL: https://issues.apache.org/jira/browse/MNG-6895
> Project: Maven
> Issue Type: New Feature
> Components: Settings
>Reporter: Jin Kwon
>Priority: Major
>
> In some cases there might be multiple server elements for the same endpoint
> with different {{id}}s.
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
> username
> {password}
>
> ...
> {code}
> Can we have an attribute look like this?
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
>
> ...
> {code}
> Or
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
[
https://issues.apache.org/jira/browse/MNG-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-6895:
--
Description:
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
other
...
{code}
Or
{code:xml}
...
...
some
username
{password}
...
{code}
was:
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
other
...
{code}
> Add aliasing feature for settings.xml:///servers/server
> ---
>
> Key: MNG-6895
> URL: https://issues.apache.org/jira/browse/MNG-6895
> Project: Maven
> Issue Type: New Feature
> Components: Settings
>Reporter: Jin Kwon
>Priority: Major
>
> In some cases there might be multiple server elements for the same endpoint
> with different {{id}}s.
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
> username
> {password}
>
> ...
> {code}
> Can we have an attribute look like this?
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
>
> ...
> {code}
> Or
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
[
https://issues.apache.org/jira/browse/MNG-6895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-6895:
--
Description:
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
other
...
{code}
was:
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
https://issues.apache.org/jira/browse/MNG-6895
> Project: Maven
> Issue Type: New Feature
> Components: Settings
>Reporter: Jin Kwon
>Priority: Major
>
> In some cases there might be multiple server elements for the same endpoint
> with different {{id}}s.
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
> username
> {password}
>
> ...
> {code}
> Can we have an attribute look like this?
> {code:xml}
> ...
>
> ...
>
> some
> username
> {password}
>
>
> other
>
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MNG-6895) Add aliasing feature for settings.xml:///servers/server
Jin Kwon created MNG-6895:
-
Summary: Add aliasing feature for settings.xml:///servers/server
Key: MNG-6895
URL: https://issues.apache.org/jira/browse/MNG-6895
Project: Maven
Issue Type: New Feature
Components: Settings
Reporter: Jin Kwon
In some cases there might be multiple server elements for the same endpoint
with different {{id}}s.
{code:xml}
...
...
some
username
{password}
other
username
{password}
...
{code}
Can we have an attribute look like this?
{code:xml}
...
...
some
username
{password}
[jira] [Commented] (MSITE-832) stage-deploy fails with maven-site-plugin 3.7.1 and wagon-webdav-jackrabbit 3.3.1: NoSuchMethodError:org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBuffer
[
https://issues.apache.org/jira/browse/MSITE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742685#comment-16742685
]
Jin Kwon commented on MSITE-832:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy (default-deploy) on
project onacit-persistence-parent: Execution default-deploy of goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy:
java.lang.NoSuchMethodError:
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.7.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/onacit/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.7.1/maven-site-plugin-3.7.1.jar
[ERROR] urls[1] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.4/maven-reporting-exec-1.4.jar
[ERROR] urls[2] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[3] =
file:/Users/onacit/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] =
file:/Users/onacit/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
[ERROR] urls[5] =
file:/Users/onacit/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
[ERROR] urls[6] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
[ERROR] urls[8] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[9] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[10] =
file:/Users/onacit/.m2/repository/org/apache/maven/maven-archiver/3.1.1/maven-archiver-3.1.1.jar
[ERROR] urls[11] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[12] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[13] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-archiver/3.4/plexus-archiver-3.4.jar
[ERROR] urls[14] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-io/2.7.1/plexus-io-2.7.1.jar
[ERROR] urls[15] =
file:/Users/onacit/.m2/repository/org/apache/commons/commons-compress/1.11/commons-compress-1.11.jar
[ERROR] urls[16] =
file:/Users/onacit/.m2/repository/org/iq80/snappy/snappy/0.4/snappy-0.4.jar
[ERROR] urls[17] =
file:/Users/onacit/.m2/repository/org/tukaani/xz/1.5/xz-1.5.jar
[ERROR] urls[18] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar
[ERROR] urls[19] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.24/plexus-utils-3.0.24.jar
[ERROR] urls[20] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.jar
[ERROR] urls[21] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar
[ERROR] urls[22] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar
[ERROR] urls[23] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar
[ERROR] urls[24] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[25] =
file:/Users/onacit/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[26] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[27] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.8/doxia-module-apt-1.8.jar
[ERROR] urls[28] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.8/doxia-module-xdoc-1.8.jar
[ERROR] urls[29] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.8/doxia-module-fml-1.8.jar
[ERROR] urls[30] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-markdown/1.8/doxia-module-markdown-1.8.jar
[ERROR] urls[31] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark-all/0.18.4/flexmark-all-0.18.4.jar
[ERROR] urls[32] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark/0.18.4/flexmark-0.18.4.jar
[ERROR] urls[33] =
[jira] [Commented] (MSITE-832) stage-deploy fails with maven-site-plugin 3.7.1 and wagon-webdav-jackrabbit 3.3.1: NoSuchMethodError:org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBuffer
[
https://issues.apache.org/jira/browse/MSITE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742688#comment-16742688
]
Jin Kwon commented on MSITE-832:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy (default-deploy) on
project onacit-persistence-parent: Execution default-deploy of goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy:
java.lang.NoSuchMethodError:
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.7.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/onacit/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.7.1/maven-site-plugin-3.7.1.jar
[ERROR] urls[1] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.4/maven-reporting-exec-1.4.jar
[ERROR] urls[2] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[3] =
file:/Users/onacit/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] =
file:/Users/onacit/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
[ERROR] urls[5] =
file:/Users/onacit/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
[ERROR] urls[6] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
[ERROR] urls[8] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[9] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[10] =
file:/Users/onacit/.m2/repository/org/apache/maven/maven-archiver/3.1.1/maven-archiver-3.1.1.jar
[ERROR] urls[11] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[12] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[13] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-archiver/3.4/plexus-archiver-3.4.jar
[ERROR] urls[14] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-io/2.7.1/plexus-io-2.7.1.jar
[ERROR] urls[15] =
file:/Users/onacit/.m2/repository/org/apache/commons/commons-compress/1.11/commons-compress-1.11.jar
[ERROR] urls[16] =
file:/Users/onacit/.m2/repository/org/iq80/snappy/snappy/0.4/snappy-0.4.jar
[ERROR] urls[17] =
file:/Users/onacit/.m2/repository/org/tukaani/xz/1.5/xz-1.5.jar
[ERROR] urls[18] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar
[ERROR] urls[19] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.24/plexus-utils-3.0.24.jar
[ERROR] urls[20] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.jar
[ERROR] urls[21] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar
[ERROR] urls[22] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar
[ERROR] urls[23] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar
[ERROR] urls[24] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[25] =
file:/Users/onacit/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[26] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[27] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.8/doxia-module-apt-1.8.jar
[ERROR] urls[28] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.8/doxia-module-xdoc-1.8.jar
[ERROR] urls[29] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.8/doxia-module-fml-1.8.jar
[ERROR] urls[30] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-markdown/1.8/doxia-module-markdown-1.8.jar
[ERROR] urls[31] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark-all/0.18.4/flexmark-all-0.18.4.jar
[ERROR] urls[32] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark/0.18.4/flexmark-0.18.4.jar
[ERROR] urls[33] =
[jira] [Issue Comment Deleted] (MSITE-832) stage-deploy fails with maven-site-plugin 3.7.1 and wagon-webdav-jackrabbit 3.3.1: NoSuchMethodError:org.apache.maven.wagon.shared.http.AbstractHttpClientWag
[
https://issues.apache.org/jira/browse/MSITE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MSITE-832:
---
Comment: was deleted
(was: {code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy (default-deploy) on
project onacit-persistence-parent: Execution default-deploy of goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy:
java.lang.NoSuchMethodError:
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.7.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/onacit/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.7.1/maven-site-plugin-3.7.1.jar
[ERROR] urls[1] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.4/maven-reporting-exec-1.4.jar
[ERROR] urls[2] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[3] =
file:/Users/onacit/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] =
file:/Users/onacit/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
[ERROR] urls[5] =
file:/Users/onacit/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
[ERROR] urls[6] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
[ERROR] urls[8] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[9] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[10] =
file:/Users/onacit/.m2/repository/org/apache/maven/maven-archiver/3.1.1/maven-archiver-3.1.1.jar
[ERROR] urls[11] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[12] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[13] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-archiver/3.4/plexus-archiver-3.4.jar
[ERROR] urls[14] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-io/2.7.1/plexus-io-2.7.1.jar
[ERROR] urls[15] =
file:/Users/onacit/.m2/repository/org/apache/commons/commons-compress/1.11/commons-compress-1.11.jar
[ERROR] urls[16] =
file:/Users/onacit/.m2/repository/org/iq80/snappy/snappy/0.4/snappy-0.4.jar
[ERROR] urls[17] =
file:/Users/onacit/.m2/repository/org/tukaani/xz/1.5/xz-1.5.jar
[ERROR] urls[18] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar
[ERROR] urls[19] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.24/plexus-utils-3.0.24.jar
[ERROR] urls[20] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.jar
[ERROR] urls[21] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar
[ERROR] urls[22] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar
[ERROR] urls[23] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar
[ERROR] urls[24] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[25] =
file:/Users/onacit/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[26] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[27] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.8/doxia-module-apt-1.8.jar
[ERROR] urls[28] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.8/doxia-module-xdoc-1.8.jar
[ERROR] urls[29] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.8/doxia-module-fml-1.8.jar
[ERROR] urls[30] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-markdown/1.8/doxia-module-markdown-1.8.jar
[ERROR] urls[31] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark-all/0.18.4/flexmark-all-0.18.4.jar
[ERROR] urls[32] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark/0.18.4/flexmark-0.18.4.jar
[ERROR] urls[33] =
[jira] [Comment Edited] (MSITE-832) stage-deploy fails with maven-site-plugin 3.7.1 and wagon-webdav-jackrabbit 3.3.1: NoSuchMethodError:org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getB
[
https://issues.apache.org/jira/browse/MSITE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742685#comment-16742685
]
Jin Kwon edited comment on MSITE-832 at 1/15/19 2:42 AM:
-
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy (default-deploy) on
project onacit-persistence-parent: Execution default-deploy of goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.7.1:deploy:
java.lang.NoSuchMethodError:
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-site-plugin:3.7.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/onacit/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.7.1/maven-site-plugin-3.7.1.jar
[ERROR] urls[1] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.4/maven-reporting-exec-1.4.jar
[ERROR] urls[2] =
file:/Users/onacit/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[3] =
file:/Users/onacit/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[4] =
file:/Users/onacit/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
[ERROR] urls[5] =
file:/Users/onacit/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.1.0/maven-shared-utils-3.1.0.jar
[ERROR] urls[6] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
[ERROR] urls[8] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[9] =
file:/Users/onacit/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[10] =
file:/Users/onacit/.m2/repository/org/apache/maven/maven-archiver/3.1.1/maven-archiver-3.1.1.jar
[ERROR] urls[11] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[12] =
file:/Users/onacit/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[13] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-archiver/3.4/plexus-archiver-3.4.jar
[ERROR] urls[14] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-io/2.7.1/plexus-io-2.7.1.jar
[ERROR] urls[15] =
file:/Users/onacit/.m2/repository/org/apache/commons/commons-compress/1.11/commons-compress-1.11.jar
[ERROR] urls[16] =
file:/Users/onacit/.m2/repository/org/iq80/snappy/snappy/0.4/snappy-0.4.jar
[ERROR] urls[17] =
file:/Users/onacit/.m2/repository/org/tukaani/xz/1.5/xz-1.5.jar
[ERROR] urls[18] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar
[ERROR] urls[19] =
file:/Users/onacit/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.24/plexus-utils-3.0.24.jar
[ERROR] urls[20] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.jar
[ERROR] urls[21] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar
[ERROR] urls[22] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar
[ERROR] urls[23] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar
[ERROR] urls[24] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[25] =
file:/Users/onacit/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[26] =
file:/Users/onacit/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[27] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.8/doxia-module-apt-1.8.jar
[ERROR] urls[28] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.8/doxia-module-xdoc-1.8.jar
[ERROR] urls[29] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.8/doxia-module-fml-1.8.jar
[ERROR] urls[30] =
file:/Users/onacit/.m2/repository/org/apache/maven/doxia/doxia-module-markdown/1.8/doxia-module-markdown-1.8.jar
[ERROR] urls[31] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark-all/0.18.4/flexmark-all-0.18.4.jar
[ERROR] urls[32] =
file:/Users/onacit/.m2/repository/com/vladsch/flexmark/flexmark/0.18.4/flexmark-0.18.4.jar
[ERROR] urls[33] =
[jira] [Created] (MNG-6213) Maven doesn't check the validity of scope value
Jin Kwon created MNG-6213:
-
Summary: Maven doesn't check the validity of scope value
Key: MNG-6213
URL: https://issues.apache.org/jira/browse/MNG-6213
Project: Maven
Issue Type: Improvement
Components: POM
Affects Versions: 3.3.9
Environment: Apache Maven 3.3.9
(bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T01:41:47+09:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.4", arch: "x86_64", family: "mac"
Reporter: Jin Kwon
Priority: Minor
I accidentally put a wrong value into the {{scope}} tag.
{code:xml}
org.glassfish.jersey
jersey-bom
2.26-b03
pom
include
{code}
And, of course, my dependency doesn't work.
{code:xml}
org.glassfish.jersey.core
jersey-common
test
{code}
{code}
'dependencies.dependency.version' for
org.glassfish.jersey.core:jersey-common:jar is missing.
{code}
Maven should complains about the wrong value of {{include}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MRELEASE-963) User property for tagNameFormat is ignored
[
https://issues.apache.org/jira/browse/MRELEASE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15559232#comment-15559232
]
Jin Kwon commented on MRELEASE-963:
---
I just face the same problem.
Overriding with a property doesn't work.
{code:xml}
@{project.artifactId}-@{project.version}
{code}
Reassigning with parent value yields an error
{code:xml}
@{project.artifactId}-${tagNameFormat}
{code}
{code}
... Detected the following recursive expression cycle in 'tagNameFormat':
[tagNameFormat] ...
{code}
> User property for tagNameFormat is ignored
> --
>
> Key: MRELEASE-963
> URL: https://issues.apache.org/jira/browse/MRELEASE-963
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.5.3
>Reporter: Christopher Tubbs
>
> I attempted to override the {{tagNameFormat}} in my pom.xml, using:
> {code:xml}
>
> custom-@{project.version}
>
> {code}
> This did not work. The property was completely ignored. It does work if you
> set the property in the plugin's configuration in the {{}}
> section, though.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-323) Running a single test using -Dtest has no effect
[
https://issues.apache.org/jira/browse/SUREFIRE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424003#comment-15424003
]
Jin Kwon commented on SUREFIRE-323:
---
And {{-Dit.test=}} also doesn't do anything at all
> Running a single test using -Dtest has no effect
>
>
> Key: SUREFIRE-323
> URL: https://issues.apache.org/jira/browse/SUREFIRE-323
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: java version "1.5.0_09"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
>Reporter: Graham Leggett
>Assignee: Brett Porter
>
> Using the -D option from the command line to run a test as per the
> instructions at
> http://maven.apache.org/plugins/maven-surefire-plugin/examples/single-test.html,
> the test is ignored.
> The test is not configured within the pom, because the test should only be
> run by hand, not as part of the build. Thus the need to run the test on its
> own.
> bash-3.00$ mvn -Dtest=**/*TestConcurrency test
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Alchemy Measure
> [INFO]task-segment: [test]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> The following command line options also do not work:
> bash-3.00$ mvn -Dtest=TestConcurrency test
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Alchemy Measure
> [INFO]task-segment: [test]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSHADE-218) MANIFEST entries copied from a custom execution-ed jar
Jin Kwon created MSHADE-218:
---
Summary: MANIFEST entries copied from a custom execution-ed jar
Key: MSHADE-218
URL: https://issues.apache.org/jira/browse/MSHADE-218
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.4.2
Environment: $ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-11T01:41:47+09:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_65, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.2", arch: "x86_64", family: "mac"
Reporter: Jin Kwon
Priority: Minor
{{maven-shade-plugin}} copies a manifest entry from a custom {{jar:jar}}.
When I add following execution which is not {{jar:default-jar}},
{code:xml}
org.apache.maven.plugins
maven-jar-plugin
jar-cp
jar
package
true
${project.build.finalName}.cp.lib/
${mainClass}
${project.build.finalName}.cp
{code}
{{maven-shade-plugin}} copies that {{Class-Path:}} entry.
{code}
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
...
Class-Path: [[this is not expected]]
...
Build-Jdk: 1.8.0_65
Main-Class: ...
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSHADE-218) MANIFEST entries copied from a custom execution-ed jar
[
https://issues.apache.org/jira/browse/MSHADE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098229#comment-15098229
]
Jin Kwon commented on MSHADE-218:
-
When I change the custom {{jar}}'s phase to {{prepare-package}} which is
executed before {{default-jar}}, problem solved.
It seems {{MSHADE}} is looking for the last {{jar}} execution.
> MANIFEST entries copied from a custom execution-ed jar
> --
>
> Key: MSHADE-218
> URL: https://issues.apache.org/jira/browse/MSHADE-218
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: $ mvn -version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-11T01:41:47+09:00)
> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
> Java version: 1.8.0_65, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.2", arch: "x86_64", family: "mac"
>Reporter: Jin Kwon
>Priority: Minor
>
> {{maven-shade-plugin}} copies a manifest entry from a custom {{jar:jar}}.
> When I add following execution which is not {{jar:default-jar}},
> {code:xml}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> jar-cp
>
> jar
>
> package
>
>
>
> true
>
> ${project.build.finalName}.cp.lib/
> ${mainClass}
>
>
> ${project.build.finalName}.cp
>
>
>
>
> {code}
> {{maven-shade-plugin}} copies that {{Class-Path:}} entry.
> {code}
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> ...
> Class-Path: [[this is not expected]]
> ...
> Build-Jdk: 1.8.0_65
> Main-Class: ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] (MNG-5621) Transitive dependency for both compile and test
Jin Kwon created MNG-5621: - Summary: Transitive dependency for both compile and test Key: MNG-5621 URL: https://jira.codehaus.org/browse/MNG-5621 Project: Maven 2 3 Issue Type: Improvement Components: Dependencies Affects Versions: 3.2.1 Environment: Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00) Maven home: /usr/local/Cellar/maven/3.2.1/libexec Java version: 1.8.0, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac Reporter: Jin Kwon Priority: Trivial 1. artifact `B` depends on `A` in test scope. 2. artifact 'C' depends on 'B' in compile scope and test scope with test-jar expected: artifact 'C''s classpath contains 'A' actual : 'A' is unknown in 'C''s test time. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5621) Transitive dependency for both compile and test
[
https://jira.codehaus.org/browse/MNG-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-5621:
--
Description:
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
artifactIdB/artifactId
dependencies
dependency
artifactIdA/artifactId
scopetest/scope
/dependency
/dependencies
{code}
{code:xml}
artifactIdC/artifactId
dependencies
dependency
artifactIdB/artifactId
scopecompile/scope
/dependency
dependency
artifactIdB/artifactId
typetest-jar/type
scopetest/scope
/dependency
/dependencies
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
was:
1. artifact `B` depends on `A` in test scope.
2. artifact 'C' depends on 'B' in compile scope and test scope with test-jar
expected: artifact 'C''s classpath contains 'A'
actual : 'A' is unknown in 'C''s test time.
Transitive dependency for both compile and test
---
Key: MNG-5621
URL: https://jira.codehaus.org/browse/MNG-5621
Project: Maven 2 3
Issue Type: Improvement
Components: Dependencies
Affects Versions: 3.2.1
Environment: Apache Maven 3.2.1
(ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.8.0, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Jin Kwon
Priority: Trivial
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
artifactIdB/artifactId
dependencies
dependency
artifactIdA/artifactId
scopetest/scope
/dependency
/dependencies
{code}
{code:xml}
artifactIdC/artifactId
dependencies
dependency
artifactIdB/artifactId
scopecompile/scope
/dependency
dependency
artifactIdB/artifactId
typetest-jar/type
scopetest/scope
/dependency
/dependencies
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5621) Transitive dependency for both compile and test
[
https://jira.codehaus.org/browse/MNG-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MNG-5621:
--
Description:
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
artifactIdB/artifactId
dependencies
dependency
artifactIdA/artifactId
scopetest/scope
/dependency
/dependencies
{code}
{code:xml}
artifactIdC/artifactId
dependencies
dependency
artifactIdB/artifactId
scopecompile/scope
/dependency
dependency
artifactIdB/artifactId
typetest-jar/type
scopetest/scope
/dependency
/dependencies
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
Is this normal behaviour or {{test-jar with test}} overrides {{compile}}
was:
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
artifactIdB/artifactId
dependencies
dependency
artifactIdA/artifactId
scopetest/scope
/dependency
/dependencies
{code}
{code:xml}
artifactIdC/artifactId
dependencies
dependency
artifactIdB/artifactId
scopecompile/scope
/dependency
dependency
artifactIdB/artifactId
typetest-jar/type
scopetest/scope
/dependency
/dependencies
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
Transitive dependency for both compile and test
---
Key: MNG-5621
URL: https://jira.codehaus.org/browse/MNG-5621
Project: Maven 2 3
Issue Type: Improvement
Components: Dependencies
Affects Versions: 3.2.1
Environment: Apache Maven 3.2.1
(ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-15T02:37:52+09:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.8.0, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Jin Kwon
Priority: Trivial
* artifact `B` depends on `A` in test scope.
* artifact 'C' depends on 'B' in compile scope and test scope with test-jar
{code:xml}
artifactIdB/artifactId
dependencies
dependency
artifactIdA/artifactId
scopetest/scope
/dependency
/dependencies
{code}
{code:xml}
artifactIdC/artifactId
dependencies
dependency
artifactIdB/artifactId
scopecompile/scope
/dependency
dependency
artifactIdB/artifactId
typetest-jar/type
scopetest/scope
/dependency
/dependencies
{code}
{{expected: artifact 'C''s classpath contains 'A'}}
{{actual : 'A' is unknown in 'C''s test time}}
Is this normal behaviour or {{test-jar with test}} overrides {{compile}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-655) Finishing finding version at build.plugins.
[
https://jira.codehaus.org/browse/MSITE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=309739#comment-309739
]
Jin Kwon commented on MSITE-655:
Dear Herve Boutemy.
I should admit that my new test case works as you insisted.
I think I had some problem with sonatype's oss parent archetype or some deploy
plugin.
the maven-site-pluin detects the version from /build/pluginManagement/plugins
if /build/plugins doesn't have any specified version and relies on the
pluginManagement.
Sorry for the mess. You should close this issue.
Here comes my simple pom.xml. Please confirm my test was ok.
{noformat}
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdmaven-site-plugin-javadoc-test/artifactId
version1.0-SNAPSHOT/version
packagingjar/packaging
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
/properties
dependencyManagement/
dependencies/
build
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.9/version
/plugin
plugin
artifactIdmaven-site-plugin/artifactId
version3.1/version
/plugin
/plugins
/pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/reportPlugins
/configuration
/plugin
/plugins
/build
namemaven-site-plugin-javadoc-test/name
urlhttp://maven.apache.org/url
/project
{noformat}
Finishing finding version at build.plugins.
---
Key: MSITE-655
URL: https://jira.codehaus.org/browse/MSITE-655
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900)
Maven home: C:\Programs\apache-maven-3.0.4
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_07\jre
Default locale: en_US, platform encoding: MS949
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Jin Kwon
Priority: Minor
With order/strategy explaing on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution
,
maven-site-plugin stops searching the version on build.plugins even if there
is no version specified.
With following pom,
{code:xml}
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
/plugin
/plugins
/pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/reportPlugins
/configuration
plugin
/plugins
{code}
maven-site-plugin seems work for maven-javadoc-plugin:2.7 not 2.8.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-655) Finishing finding version at build.plugins.
[
https://jira.codehaus.org/browse/MSITE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon closed MSITE-655.
--
Resolution: Cannot Reproduce
Finishing finding version at build.plugins.
---
Key: MSITE-655
URL: https://jira.codehaus.org/browse/MSITE-655
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900)
Maven home: C:\Programs\apache-maven-3.0.4
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_07\jre
Default locale: en_US, platform encoding: MS949
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Jin Kwon
Priority: Minor
With order/strategy explaing on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution
,
maven-site-plugin stops searching the version on build.plugins even if there
is no version specified.
With following pom,
{code:xml}
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
/plugin
/plugins
/pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/reportPlugins
/configuration
plugin
/plugins
{code}
maven-site-plugin seems work for maven-javadoc-plugin:2.7 not 2.8.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308846#comment-308846
]
Jin Kwon commented on MSITE-443:
I just find that maven-site-plugin seems have some problem although works as
explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
build
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
| must follow the lights; it doesn't.
/plugin
|
plugin
|
artifactIdmaven-site-plugin/artifactId
|
version3.1/version
|
/plugin
|
/plugins
|
/pluginManagement
|
plugins
|
plugin
|
artifactIdmaven-javadoc-plugin/artifactId | 2.7
---|
/plugin|
plugin |
groupIdorg.apache.maven.plugins/groupId|
artifactIdmaven-site-plugin/artifactId |
executions |
execution |
idattach-descriptor/id |
goals|
goalattach-descriptor/goal |
/goals |
/execution |
/executions |
configuration|
reportPlugins |
plugin |
artifactIdmaven-javadoc-plugin/artifactId ---|
/plugin
/reportPlugins
/configuration
plugin
/plugins
/build
add a reportingManagement section
-
Key: MSITE-443
URL: https://jira.codehaus.org/browse/MSITE-443
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Environment: maven-site-plugin 2.0-beta-3-SNAPSHOT
Reporter: Indrajit Raychaudhuri
Fix For: 3.0
Consider the following POM:
{code:xml}
!-- ... ... --
!-- ... ... --
build
pluginManagement
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
authorfalse/author
/configuration
/plugin
/pluginManagement
/build
!-- ... ... --
!-- ... ... --
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/plugins
/reporting
!-- ... ... --
{code}
{{mvn site:site}} doesn't honor the javadoc configuration specified in the
{{pluginManagement/}} section.
However, {{mvn javadoc:javadoc}} honors them.
This is true not just for javadoc but other plugins like checkstyle as well.
I guess, the {{reporting/}} section doesn't use the {{pluginManagement/}}
section at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308846#comment-308846
]
Jin Kwon edited comment on MSITE-443 at 9/18/12 8:03 AM:
-
I just find that maven-site-plugin seems have some problem although works as
explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
{noformat}
build
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
| must follow the lights; it doesn't.
/plugin
|
plugin
|
artifactIdmaven-site-plugin/artifactId
|
version3.1/version
|
/plugin
|
/plugins
|
/pluginManagement
|
plugins
|
plugin
|
artifactIdmaven-javadoc-plugin/artifactId | 2.7
---|
/plugin|
plugin |
groupIdorg.apache.maven.plugins/groupId|
artifactIdmaven-site-plugin/artifactId |
executions |
execution |
idattach-descriptor/id |
goals|
goalattach-descriptor/goal |
/goals |
/execution |
/executions |
configuration|
reportPlugins |
plugin |
artifactIdmaven-javadoc-plugin/artifactId ---|
/plugin
/reportPlugins
/configuration
plugin
/plugins
/build
{noformat}
was (Author: jinahya):
I just find that maven-site-plugin seems have some problem although works
as explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
build
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
| must follow the lights; it doesn't.
/plugin
|
plugin
|
artifactIdmaven-site-plugin/artifactId
|
version3.1/version
|
/plugin
|
/plugins
|
/pluginManagement
|
plugins
|
plugin
|
artifactIdmaven-javadoc-plugin/artifactId | 2.7
---|
/plugin|
plugin |
groupIdorg.apache.maven.plugins/groupId|
artifactIdmaven-site-plugin/artifactId |
executions |
execution |
idattach-descriptor/id |
goals|
goalattach-descriptor/goal |
/goals |
/execution |
/executions |
configuration|
reportPlugins |
plugin |
[jira] (MSITE-443) add a reportingManagement section
[
https://jira.codehaus.org/browse/MSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=308846#comment-308846
]
Jin Kwon edited comment on MSITE-443 at 9/18/12 8:05 AM:
-
I just find that maven-site-plugin seems have some problem although works as
explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
{noformat}
build
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
| must follow the lights; it doesn't.
/plugin
|
plugin
|
artifactIdmaven-site-plugin/artifactId
|
version3.1/version
|
/plugin
|
/plugins
|
/pluginManagement
|
plugins
|
plugin
|
artifactIdmaven-javadoc-plugin/artifactId | 2.7
---|
/plugin|
plugin |
groupIdorg.apache.maven.plugins/groupId|
artifactIdmaven-site-plugin/artifactId |
executions |
execution |
idattach-descriptor/id |
goals|
goalattach-descriptor/goal |
/goals |
/execution |
/executions |
configuration|
reportPlugins |
plugin |
artifactIdmaven-javadoc-plugin/artifactId ---|
/plugin
/reportPlugins
/configuration
plugin
/plugins
/build
{noformat}
was (Author: jinahya):
I just find that maven-site-plugin seems have some problem although works
as explained on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution.
{noformat}
build
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
| must follow the lights; it doesn't.
/plugin
|
plugin
|
artifactIdmaven-site-plugin/artifactId
|
version3.1/version
|
/plugin
|
/plugins
|
/pluginManagement
|
plugins
|
plugin
|
artifactIdmaven-javadoc-plugin/artifactId | 2.7
---|
/plugin|
plugin |
groupIdorg.apache.maven.plugins/groupId|
artifactIdmaven-site-plugin/artifactId |
executions |
execution |
idattach-descriptor/id |
goals|
goalattach-descriptor/goal |
/goals |
/execution |
/executions |
configuration|
reportPlugins |
plugin |
[jira] (MSITE-655) Finishing finding version at build.plugins.
Jin Kwon created MSITE-655:
--
Summary: Finishing finding version at build.plugins.
Key: MSITE-655
URL: https://jira.codehaus.org/browse/MSITE-655
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900)
Maven home: C:\Programs\apache-maven-3.0.4
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_07\jre
Default locale: en_US, platform encoding: MS949
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Jin Kwon
Priority: Minor
With order/strategy explaing on
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Version_Resolution
,
maven-site-plugin stops searching the version on build.plugins even if there is
no version specified.
With following pom,
{code:xml}
pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8.1/version
/plugin
/plugins
/pluginManagement
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
/plugin
/reportPlugins
/configuration
plugin
/plugins
{code}
maven-site-plugin seems work for maven-javadoc-plugin:2.7 not 2.8.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-482) jar-with-dependencies ref doesn't refer previously created artifact jar's content.
jar-with-dependencies ref doesn't refer previously created artifact jar's content. -- Key: MASSEMBLY-482 URL: http://jira.codehaus.org/browse/MASSEMBLY-482 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-5 Environment: Apache Maven 2.2.1 (r801777; 2009-08-07 04:16:01+0900) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.2 arch: i386 Family: mac Reporter: Jin Kwon Priority: Minor jar-with-dependencies doesn't contain contents from previously(in package lifecycle) created artifact jar. I'm not sure that this problem is an issue or not but, I placed proguard-maven-plugin configuration before the assembly plugin. proguard plugin changes artifact jar's content with obfuscated one. When 2.2-beta-4 jar-with-dependencies ref property makes new bit jar with the content of previously modified jar. with 2.2-beta-5, it doesn't. Can anybody resolve this situation? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
