[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build
[ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262896#action_262896 ] Hannes Schmidt commented on MNG-1323: - Can this please be backported to 2.2.x. I've been using Maven since 2005 and this thing has been bugging me once every so often with enough time in between for my brain to garbage collect my awareness of this bug. So I basically spend a few hours every year hunting plugin dependency problems with reactor builds and ultimately land on this page. BTW, my workaround is to collect all plugin dependencies in the pluginManagement section of a parent pom that's common to all modules. > Plugin extensions (dependencies) not resolved in reactor build > -- > > Key: MNG-1323 > URL: http://jira.codehaus.org/browse/MNG-1323 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 >Reporter: Kenney Westerhof > Fix For: 3.0-alpha-1 > > Attachments: MNG-1323-components-2.0.x.diff, > MNG-1323-core-integration-testing-2.diff, > MNG-1323-core-integration-testing.diff, > MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, > MNG1323-maven-core-2.1.diff, two-antruns.zip > > > I've added a dependency on an Ant Task in > project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ > and run that anttask using the antrun plugin. > When run from the project dir itself it runs fine. > When running from the root of the project tree (reactor build, project one > level below root), > antrun bails out because the taskdef can't be found (not on classpath). > It looks like the dependency isn't resolved, or not added to the plugins' > classrealm. -- 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
[jira] Commented: (MWAR-249) War plugin doesn't let modify the contents of the "exploded" directory
[ http://jira.codehaus.org/browse/MWAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262834#action_262834 ] Bruno Medeiros commented on MWAR-249: - It would be good to see this fixed. Is there any rules to patch proposal? > War plugin doesn't let modify the contents of the "exploded" directory > -- > > Key: MWAR-249 > URL: http://jira.codehaus.org/browse/MWAR-249 > Project: Maven 2.x WAR Plugin > Issue Type: Bug >Affects Versions: 2.1, 2.2 > Environment: maven 3 >Reporter: cem koc > Attachments: Test.zip > > > Shortly I am trying to modify the contents of the "exploded" directory before > package phase. I was successfully modifying contents of the exploded > directories before updating my war plugin. > My goal was > 1) Creating an exploded directory of the sources. > 2) Modifying contents with Replace plugin > 3) Creating a war file including modified files > To recreate issue, > *) mvn clean prepare-package --> This will create as expected file. > *) mvn clean package --> This will replace again modified file with old one. > Thanks -- 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
[jira] Created: (SCM-618) StringIndexOutOfBoundsException when doing checkout from SVN in combination with plexus-utils:2.0.5+
StringIndexOutOfBoundsException when doing checkout from SVN in combination
with plexus-utils:2.0.5+
Key: SCM-618
URL: http://jira.codehaus.org/browse/SCM-618
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-svn
Affects Versions: 1.5
Reporter: Benjamin Bentmann
Attachments: pom.xml
Running {{mvn clean generate-sources}} on the attached POM yields
{noformat}
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
[INFO] Building Unnamed - test:test:jar:0.1
[INFO]task-segment: [clean, generate-sources]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory D:\z\target
[INFO] [scm:checkout {execution: checkout}]
[INFO] Removing D:\z\target\maven-model
[INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout
http://svn.apache.org/repos/asf/maven/pom/trunk/maven "D:\z\target\maven-model""
[INFO] Working directory: D:\z\target
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Cannot run checkout command :
Embedded error: Exception while executing SCM command.
String index out of range: -1
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot run checkout
command :
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot run checkout
command :
at
org.apache.maven.scm.plugin.CheckoutMojo.checkout(CheckoutMojo.java:137)
at
org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:93)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM
command.
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63)
at
org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java:356)
at
org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.checkout(AbstractSvnScmProvider.java:292)
at
org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:428)
at
org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:405)
at
org.apache.maven.scm.manager.AbstractScmManager.checkOut(AbstractScmManager.java:399)
at
org.apache.maven.scm.plugin.CheckoutMojo.checkout(CheckoutMojo.java:125)
... 20 more
Caused by: org.apache.maven.scm.ScmException: Error while executing command.
at
org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:95)
at
org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:82)
at
[jira] Closed: (DOXIA-403) FO module creating non-wellformed xls-fo output
[
http://jira.codehaus.org/browse/DOXIA-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed DOXIA-403.
---
Resolution: Fixed
Fix Version/s: 1.1.5
Assignee: Lukas Theussl
I have corrected the example snippet,
[r1089880|http://svn.apache.org/viewvc?rev=1089880&view=rev]. The
beginDocument()/endDocument() are currently required by the FOSink.
> FO module creating non-wellformed xls-fo output
>
>
> Key: DOXIA-403
> URL: http://jira.codehaus.org/browse/DOXIA-403
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - FO
>Affects Versions: 1.1.3
>Reporter: Sergey Shikov
>Assignee: Lukas Theussl
> Fix For: 1.1.5
>
>
> This code, copy&pasted from Doxia site, producing non-wellformed FO document:
> Java:
> {code}
> try {
> // Open input apt document:
> StringReader source= new StringReader("h1. test");
> // Create FO sink:
> Writer writer = new StringWriter();
> FoSink fosink= new FoSink(writer);
> Parser parser= new ConfluenceParser();
> parser.parse(source, fosink);
> // close streams
> fosink.close();
> source.close();
> System.out.println(writer.toString());
> } catch (ParseException e) {
> e.printStackTrace();
> } catch (IOException e) {
> e.printStackTrace();
> }
> {code}
> Result:
> {code:xml}
>
>
> font-family="Garamond,serif" font-size="11pt">
> font-family="Helvetica,sans-serif" keep-with-next="always" color="#00"
> font-size="12pt">1 test
>
>
>
>
> {code}
> No open tag fo:root in document.
--
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
[jira] Created: (MRESOURCES-142) Filter does not process sources
Filter does not process sources
---
Key: MRESOURCES-142
URL: http://jira.codehaus.org/browse/MRESOURCES-142
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Rainer Flicker
Filter does not process sources.
pom.xml:
...
src/main/java
true
../filtered-sources/java
src/main/resources
true
**/persistence-test.xml
target/filtered-sources/java
...
---
mvn clean install -Djavamail.jndi="java:Mail"
With version 2.5, filtered sources contains ${javamail.jndi}, while with
version 2.4.3,
they contain "java:Mail".
--
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
[jira] Commented: (MRELEASE-673) release using different filename than pom.xml does not work
[ http://jira.codehaus.org/browse/MRELEASE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262796#action_262796 ] bernard patteeuw commented on MRELEASE-673: --- think I just found: pomFileName instead of -f > release using different filename than pom.xml does not work > --- > > Key: MRELEASE-673 > URL: http://jira.codehaus.org/browse/MRELEASE-673 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: bernard patteeuw > > [INFO] [ERROR] The goal you specified requires a project to execute but there > is no POM in this directory (C:\data\projects\ZZZ\CCC). Please verify > you invoked Maven from the correct directory. -> [Help 1] > [INFO] org.apache.maven.lifecycle.MissingProjectException: The goal you > specified requires a project to execute but there is no POM in this directory > (C:\data\projects\ZZZ\CCC). Please verify you invoked Maven from the correct > directory. -- 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
[jira] Closed: (MRELEASE-673) release using different filename than pom.xml does not work
[ http://jira.codehaus.org/browse/MRELEASE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bernard patteeuw closed MRELEASE-673. - Resolution: Not A Bug > release using different filename than pom.xml does not work > --- > > Key: MRELEASE-673 > URL: http://jira.codehaus.org/browse/MRELEASE-673 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Reporter: bernard patteeuw > > [INFO] [ERROR] The goal you specified requires a project to execute but there > is no POM in this directory (C:\data\projects\ZZZ\CCC). Please verify > you invoked Maven from the correct directory. -> [Help 1] > [INFO] org.apache.maven.lifecycle.MissingProjectException: The goal you > specified requires a project to execute but there is no POM in this directory > (C:\data\projects\ZZZ\CCC). Please verify you invoked Maven from the correct > directory. -- 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
[jira] Created: (MRELEASE-673) release using different filename than pom.xml does not work
release using different filename than pom.xml does not work --- Key: MRELEASE-673 URL: http://jira.codehaus.org/browse/MRELEASE-673 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: bernard patteeuw [INFO] [ERROR] The goal you specified requires a project to execute but there is no POM in this directory (C:\data\projects\ZZZ\CCC). Please verify you invoked Maven from the correct directory. -> [Help 1] [INFO] org.apache.maven.lifecycle.MissingProjectException: The goal you specified requires a project to execute but there is no POM in this directory (C:\data\projects\ZZZ\CCC). Please verify you invoked Maven from the correct directory. -- 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
[jira] Commented: (MSITE-578) Incorrect and confusing documentation of site directories
[
http://jira.codehaus.org/browse/MSITE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262795#action_262795
]
Lukas Theussl commented on MSITE-578:
-
The @required tag means that the parameter is required for the plugin to work
which is not the same as "required for the user to specify". Eg a parameter
could default to another expression which might be null at run time. However,
in the current case it is probably confusing, I removed it:
[r1089852|http://svn.apache.org/viewvc?rev=1089852&view=rev] and
[r1089853|http://svn.apache.org/viewvc?rev=1089853&view=rev].
> Incorrect and confusing documentation of site directories
> -
>
> Key: MSITE-578
> URL: http://jira.codehaus.org/browse/MSITE-578
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 2.2, 3.0-beta-3
>Reporter: SebbASF
>Assignee: Lukas Theussl
> Fix For: 2.3, 3.0-beta-4
>
>
> The site:stage goal contains the following doc:
> generatedSiteDirectory:
> Directory containing generated documentation.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${project.build.directory}/generated-site
> The expression looks wrong.
> The explanation is also a bit ambiguous - is the directory used to find
> already generated documentation, or is it used as the output directory from
> site:stage? In which case, how does it differ from outputDirectory ?
> The page also contains:
> outputDirectory:
> Directory containing the generated project sites and report distributions.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${siteOutputDirectory}
> * Default: ${project.reporting.outputDirectory}
> Again, it's not obvious if this is an output or input directory.
> Also, why is the parameter marked as "Required" when there is a default?
--
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
[jira] Commented: (MSITE-578) Incorrect and confusing documentation of site directories
[
http://jira.codehaus.org/browse/MSITE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262794#action_262794
]
SebbASF commented on MSITE-578:
---
The fixed descriptions are much clearer, thanks.
However, generatedSiteDirectory and outputDirectory are still marked as
"required", even though they have defaults.
> Incorrect and confusing documentation of site directories
> -
>
> Key: MSITE-578
> URL: http://jira.codehaus.org/browse/MSITE-578
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 2.2, 3.0-beta-3
>Reporter: SebbASF
>Assignee: Lukas Theussl
> Fix For: 2.3, 3.0-beta-4
>
>
> The site:stage goal contains the following doc:
> generatedSiteDirectory:
> Directory containing generated documentation.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${project.build.directory}/generated-site
> The expression looks wrong.
> The explanation is also a bit ambiguous - is the directory used to find
> already generated documentation, or is it used as the output directory from
> site:stage? In which case, how does it differ from outputDirectory ?
> The page also contains:
> outputDirectory:
> Directory containing the generated project sites and report distributions.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${siteOutputDirectory}
> * Default: ${project.reporting.outputDirectory}
> Again, it's not obvious if this is an output or input directory.
> Also, why is the parameter marked as "Required" when there is a default?
--
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
[jira] Closed: (MNG-5060) Fails to resolve plugin dependencies in Maven 3.0.x
[
http://jira.codehaus.org/browse/MNG-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-5060.
--
Resolution: Not A Bug
Fix Version/s: (was: 3.0.4)
Assignee: Benjamin Bentmann
>From the plugin's {{EasybMojo.java}}:
{code:xml}
ArtifactResolutionResult resolutionResult =
resolver.resolveTransitively(singleton(easybArtifact),
mojoArtifact, EMPTY_LIST, localRepository, metadataSource);
{code}
which can be expected to fail due to {{EMPTY_LIST}} when considering
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository.
So please fill this against the plugin, asking them to pass the proper set of
remote repos (project or plugin) to resolve the artifacts.
> Fails to resolve plugin dependencies in Maven 3.0.x
> ---
>
> Key: MNG-5060
> URL: http://jira.codehaus.org/browse/MNG-5060
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.3
>Reporter: John Smart
>Assignee: Benjamin Bentmann
>Priority: Blocker
>
> For some projects, Maven 3.x fails to resolve/download plugin dependencies,
> whereas Maven 2.x worked fine. Could be an aether bug. The artifact when
> resolving in aether has "remoteRepositories" : size:0
> The situation appears to be that it it downloads it from central, adds in
> _maven.repositories as
> #NOTE: This is an internal implementation file, its format can be changed
> without prior notice.
> #Thu Apr 07 20:42:04 NZST 2011
> easyb-core-1.1.jar>central=
> easyb-core-1.1.pom>central=
> and then proceeds to only look for
> easyb-core-1-1.pom>=
> (i.e. local only repository) which isn't there.
> An example of this problem can be reproduced by building the following
> project from github:
> https://github.com/wakaleo/thucydides/tree/maven-3.0.x-bug-example
> Just run mvn install. With Maven 2.2.1 it works fine. With Maven 3.0.x you
> get the following:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2:05.397s
> [INFO] Finished at: Thu Apr 07 23:08:55 NZST 2011
> [INFO] Final Memory: 23M/81M
> [INFO]
>
> [ERROR] Missing:
> [ERROR] --
> [ERROR] 1) org.easyb:easyb-core:jar:1.1
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.easyb -DartifactId=easyb-core
> -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.easyb -DartifactId=easyb-core
> -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> [ERROR]
> [ERROR] Path to dependency:
> [ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1
> [ERROR] 2) org.easyb:easyb-core:jar:1.1
> [ERROR]
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR]
> [ERROR] for artifact:
> [ERROR] org.easyb:maven-easyb-plugin:jar:1.1
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] (none)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoundException
> It does this despite the fact that the dependency in question is (a) on
> central, (b) in the local repository, or (c) both. If you try to install it
> manually, it fails with a message saying that there is already a JAR file
> there.
--
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
[jira] Reopened: (MNG-5060) Fails to resolve plugin dependencies in Maven 3.0.x
[ http://jira.codehaus.org/browse/MNG-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MNG-5060: > Fails to resolve plugin dependencies in Maven 3.0.x > --- > > Key: MNG-5060 > URL: http://jira.codehaus.org/browse/MNG-5060 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.3 >Reporter: John Smart >Priority: Blocker > Fix For: 3.0.4 > > > For some projects, Maven 3.x fails to resolve/download plugin dependencies, > whereas Maven 2.x worked fine. Could be an aether bug. The artifact when > resolving in aether has "remoteRepositories" : size:0 > The situation appears to be that it it downloads it from central, adds in > _maven.repositories as > #NOTE: This is an internal implementation file, its format can be changed > without prior notice. > #Thu Apr 07 20:42:04 NZST 2011 > easyb-core-1.1.jar>central= > easyb-core-1.1.pom>central= > and then proceeds to only look for > easyb-core-1-1.pom>= > (i.e. local only repository) which isn't there. > An example of this problem can be reproduced by building the following > project from github: > https://github.com/wakaleo/thucydides/tree/maven-3.0.x-bug-example > Just run mvn install. With Maven 2.2.1 it works fine. With Maven 3.0.x you > get the following: > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2:05.397s > [INFO] Finished at: Thu Apr 07 23:08:55 NZST 2011 > [INFO] Final Memory: 23M/81M > [INFO] > > [ERROR] Missing: > [ERROR] -- > [ERROR] 1) org.easyb:easyb-core:jar:1.1 > [ERROR] > [ERROR] Try downloading the file manually from the project website. > [ERROR] > [ERROR] Then, install it using the command: > [ERROR] mvn install:install-file -DgroupId=org.easyb -DartifactId=easyb-core > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file > [ERROR] > [ERROR] Alternatively, if you host your own repository you can deploy the > file there: > [ERROR] mvn deploy:deploy-file -DgroupId=org.easyb -DartifactId=easyb-core > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > [ERROR] > [ERROR] Path to dependency: > [ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1 > [ERROR] 2) org.easyb:easyb-core:jar:1.1 > [ERROR] > [ERROR] -- > [ERROR] 1 required artifact is missing. > [ERROR] > [ERROR] for artifact: > [ERROR] org.easyb:maven-easyb-plugin:jar:1.1 > [ERROR] > [ERROR] from the specified remote repositories: > [ERROR] (none) > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoundException > It does this despite the fact that the dependency in question is (a) on > central, (b) in the local repository, or (c) both. If you try to install it > manually, it fails with a message saying that there is already a JAR file > there. -- 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
[jira] Commented: (WAGON-110) Support directory operations sanely.
[
http://jira.codehaus.org/browse/WAGON-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262788#action_262788
]
Oleg Estekhin commented on WAGON-110:
-
When the WagonDirectoryScanner in the scandir(String,String) method tries to
check whether the resource name denotes a directory, it tries to add a trailing
'/' character to the resource name and asks Wagon.resourceExists to check
whether a resource with such a name exists.
If for any reason the Wagon or some underlying library will decide to remove
the trailing '/' as part of some normalization process before checking for
resource existance, the Wagon will return true from the resourceExists, and
WagonDirectoryScanner will wrongly think it is a directory.
The WagonDirectoryScanner.scandir obtains a list of files inside a direcotry by
calling the Wagon.getFileList(). The getFileList's javadoc does not require
that directories inside the returned list should have the trailing '/', but the
WagonTestCase expects it to be so.
Names that already have the trailing '/' are considered by the
WagonDirectoryScanner.scandir and WagonDirectoryScanner.isDirectory to be
directories without asking Wagon.resourceExists, but all other names in the
list returned from the Wagon.getFileList will be checked by adding '/' and
asking Wagon.resourceExists.
Consider adding isDirectory(String):boolean method to the Wagon interface that
will explicitely check whether the wagon treats the specified resource name as
a directory or not.
Anyway, the Wagon.getFileList javadoc should be updated to reflect that
directory names should have the trailing '/'.
> Support directory operations sanely.
>
>
> Key: WAGON-110
> URL: http://jira.codehaus.org/browse/WAGON-110
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-provider-api
>Reporter: Luke Daley
> Fix For: 1.x
>
>
> The {{Wagon}} provider API is confused for directory operations. To simplify,
> I propose a new interface be created (e.g. {{DirectoryWagon}}) that wagons
> can implement...
> {code}
> bool isDirectory(String path) throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> String[] getFileList(String path) throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> void mkdir(String path) throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> void mkdirs(String path) throw throws TransferFailedException,
> ResourceDoesNotExistException, AuthorizationException;
> {code}
> This would also require removing all directory related methods from the
> {{Wagon}} interface. The {{AbstractWagon}} implementation could
> _transparently_ use the primitives from the {{DirectoryWagon}} interface (if
> implemented) to handle directory operations.
--
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
[jira] Closed: (MNG-5060) Fails to resolve plugin dependencies in Maven 3.0.x
[ http://jira.codehaus.org/browse/MNG-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Smart closed MNG-5060. --- Resolution: Fixed Fix Version/s: 3.0.4 Looks like this is an easyb issue. I'll reopen if it turns out not to be. > Fails to resolve plugin dependencies in Maven 3.0.x > --- > > Key: MNG-5060 > URL: http://jira.codehaus.org/browse/MNG-5060 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.3 >Reporter: John Smart >Priority: Blocker > Fix For: 3.0.4 > > > For some projects, Maven 3.x fails to resolve/download plugin dependencies, > whereas Maven 2.x worked fine. Could be an aether bug. The artifact when > resolving in aether has "remoteRepositories" : size:0 > The situation appears to be that it it downloads it from central, adds in > _maven.repositories as > #NOTE: This is an internal implementation file, its format can be changed > without prior notice. > #Thu Apr 07 20:42:04 NZST 2011 > easyb-core-1.1.jar>central= > easyb-core-1.1.pom>central= > and then proceeds to only look for > easyb-core-1-1.pom>= > (i.e. local only repository) which isn't there. > An example of this problem can be reproduced by building the following > project from github: > https://github.com/wakaleo/thucydides/tree/maven-3.0.x-bug-example > Just run mvn install. With Maven 2.2.1 it works fine. With Maven 3.0.x you > get the following: > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2:05.397s > [INFO] Finished at: Thu Apr 07 23:08:55 NZST 2011 > [INFO] Final Memory: 23M/81M > [INFO] > > [ERROR] Missing: > [ERROR] -- > [ERROR] 1) org.easyb:easyb-core:jar:1.1 > [ERROR] > [ERROR] Try downloading the file manually from the project website. > [ERROR] > [ERROR] Then, install it using the command: > [ERROR] mvn install:install-file -DgroupId=org.easyb -DartifactId=easyb-core > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file > [ERROR] > [ERROR] Alternatively, if you host your own repository you can deploy the > file there: > [ERROR] mvn deploy:deploy-file -DgroupId=org.easyb -DartifactId=easyb-core > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > [ERROR] > [ERROR] Path to dependency: > [ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1 > [ERROR] 2) org.easyb:easyb-core:jar:1.1 > [ERROR] > [ERROR] -- > [ERROR] 1 required artifact is missing. > [ERROR] > [ERROR] for artifact: > [ERROR] org.easyb:maven-easyb-plugin:jar:1.1 > [ERROR] > [ERROR] from the specified remote repositories: > [ERROR] (none) > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoundException > It does this despite the fact that the dependency in question is (a) on > central, (b) in the local repository, or (c) both. If you try to install it > manually, it fails with a message saying that there is already a JAR file > there. -- 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
[jira] Updated: (MNG-5060) Fails to resolve plugin dependencies in Maven 3.0.x
[ http://jira.codehaus.org/browse/MNG-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-5060: --- Component/s: Artifacts and Repositories Affects Version/s: 3.0.3 > Fails to resolve plugin dependencies in Maven 3.0.x > --- > > Key: MNG-5060 > URL: http://jira.codehaus.org/browse/MNG-5060 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.0.3 >Reporter: John Smart >Priority: Blocker > > For some projects, Maven 3.x fails to resolve/download plugin dependencies, > whereas Maven 2.x worked fine. Could be an aether bug. The artifact when > resolving in aether has "remoteRepositories" : size:0 > The situation appears to be that it it downloads it from central, adds in > _maven.repositories as > #NOTE: This is an internal implementation file, its format can be changed > without prior notice. > #Thu Apr 07 20:42:04 NZST 2011 > easyb-core-1.1.jar>central= > easyb-core-1.1.pom>central= > and then proceeds to only look for > easyb-core-1-1.pom>= > (i.e. local only repository) which isn't there. > An example of this problem can be reproduced by building the following > project from github: > https://github.com/wakaleo/thucydides/tree/maven-3.0.x-bug-example > Just run mvn install. With Maven 2.2.1 it works fine. With Maven 3.0.x you > get the following: > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2:05.397s > [INFO] Finished at: Thu Apr 07 23:08:55 NZST 2011 > [INFO] Final Memory: 23M/81M > [INFO] > > [ERROR] Missing: > [ERROR] -- > [ERROR] 1) org.easyb:easyb-core:jar:1.1 > [ERROR] > [ERROR] Try downloading the file manually from the project website. > [ERROR] > [ERROR] Then, install it using the command: > [ERROR] mvn install:install-file -DgroupId=org.easyb -DartifactId=easyb-core > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file > [ERROR] > [ERROR] Alternatively, if you host your own repository you can deploy the > file there: > [ERROR] mvn deploy:deploy-file -DgroupId=org.easyb -DartifactId=easyb-core > -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > [ERROR] > [ERROR] Path to dependency: > [ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1 > [ERROR] 2) org.easyb:easyb-core:jar:1.1 > [ERROR] > [ERROR] -- > [ERROR] 1 required artifact is missing. > [ERROR] > [ERROR] for artifact: > [ERROR] org.easyb:maven-easyb-plugin:jar:1.1 > [ERROR] > [ERROR] from the specified remote repositories: > [ERROR] (none) > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoundException > It does this despite the fact that the dependency in question is (a) on > central, (b) in the local repository, or (c) both. If you try to install it > manually, it fails with a message saying that there is already a JAR file > there. -- 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
[jira] Created: (MNG-5060) Fails to resolve plugin dependencies in Maven 3.0.x
Fails to resolve plugin dependencies in Maven 3.0.x --- Key: MNG-5060 URL: http://jira.codehaus.org/browse/MNG-5060 Project: Maven 2 & 3 Issue Type: Bug Reporter: John Smart Priority: Blocker For some projects, Maven 3.x fails to resolve/download plugin dependencies, whereas Maven 2.x worked fine. Could be an aether bug. The artifact when resolving in aether has "remoteRepositories" : size:0 The situation appears to be that it it downloads it from central, adds in _maven.repositories as #NOTE: This is an internal implementation file, its format can be changed without prior notice. #Thu Apr 07 20:42:04 NZST 2011 easyb-core-1.1.jar>central= easyb-core-1.1.pom>central= and then proceeds to only look for easyb-core-1-1.pom>= (i.e. local only repository) which isn't there. An example of this problem can be reproduced by building the following project from github: https://github.com/wakaleo/thucydides/tree/maven-3.0.x-bug-example Just run mvn install. With Maven 2.2.1 it works fine. With Maven 3.0.x you get the following: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:05.397s [INFO] Finished at: Thu Apr 07 23:08:55 NZST 2011 [INFO] Final Memory: 23M/81M [INFO] [ERROR] Missing: [ERROR] -- [ERROR] 1) org.easyb:easyb-core:jar:1.1 [ERROR] [ERROR] Try downloading the file manually from the project website. [ERROR] [ERROR] Then, install it using the command: [ERROR] mvn install:install-file -DgroupId=org.easyb -DartifactId=easyb-core -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file [ERROR] [ERROR] Alternatively, if you host your own repository you can deploy the file there: [ERROR] mvn deploy:deploy-file -DgroupId=org.easyb -DartifactId=easyb-core -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [ERROR] [ERROR] Path to dependency: [ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1 [ERROR] 2) org.easyb:easyb-core:jar:1.1 [ERROR] [ERROR] -- [ERROR] 1 required artifact is missing. [ERROR] [ERROR] for artifact: [ERROR] org.easyb:maven-easyb-plugin:jar:1.1 [ERROR] [ERROR] from the specified remote repositories: [ERROR] (none) [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MultipleArtifactsNotFoundException It does this despite the fact that the dependency in question is (a) on central, (b) in the local repository, or (c) both. If you try to install it manually, it fails with a message saying that there is already a JAR file there. -- 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
[jira] Closed: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-539. --- Resolution: Not A Bug Assignee: Lukas Theussl > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Assignee: Lukas Theussl >Priority: Minor > Attachments: MSITE-539.zip > > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Commented: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262784#action_262784 ] Stevo Slavic commented on MSITE-539: Can not reproduce this anymore. > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > Attachments: MSITE-539.zip > > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Closed: (MSITE-578) Incorrect and confusing documentation of site directories
[
http://jira.codehaus.org/browse/MSITE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-578.
---
Resolution: Fixed
Fixed in
[r1089802|http://svn.apache.org/viewvc?view=revision&revision=1089802] and
[r1089804|http://svn.apache.org/viewvc?view=revision&revision=1089804].
> Incorrect and confusing documentation of site directories
> -
>
> Key: MSITE-578
> URL: http://jira.codehaus.org/browse/MSITE-578
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 2.2, 3.0-beta-3
>Reporter: SebbASF
>Assignee: Lukas Theussl
> Fix For: 2.3, 3.0-beta-4
>
>
> The site:stage goal contains the following doc:
> generatedSiteDirectory:
> Directory containing generated documentation.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${project.build.directory}/generated-site
> The expression looks wrong.
> The explanation is also a bit ambiguous - is the directory used to find
> already generated documentation, or is it used as the output directory from
> site:stage? In which case, how does it differ from outputDirectory ?
> The page also contains:
> outputDirectory:
> Directory containing the generated project sites and report distributions.
> * Type: java.io.File
> * Required: Yes
> * Expression: ${siteOutputDirectory}
> * Default: ${project.reporting.outputDirectory}
> Again, it's not obvious if this is an output or input directory.
> Also, why is the parameter marked as "Required" when there is a default?
--
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
[jira] Commented: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262782#action_262782 ] Lukas Theussl commented on MSITE-539: - Attaching a simple test project, run 'mvn site' using maven-3.0.3 I get no warnings or complains about bad practice. > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > Attachments: MSITE-539.zip > > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Updated: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-539: Attachment: MSITE-539.zip > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > Attachments: MSITE-539.zip > > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Issue Comment Edited: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262778#action_262778 ] Stevo Slavic edited comment on MSITE-539 at 4/7/11 4:28 AM: Yes, I found example there misleading, version element for every reporting plugin listed under reportPlugins was not respected - if I remember well, if reporting plugins were only defined in reportingPlugins Maven 3 would report that it's not good practice that reporting plugin version is not specified, even though version was specified as in example. Only by specifying reporting plugins in pluginManagement I was able to configure required version, and have Maven not complain about bad practice. After specifying version of reporting plugins in pluginManagement section, I could, and now typically do remove version of plugins in reportPlugins section. was (Author: sslavic): Yes, I found example there misleading, version element for every reporting plugin listed under reportPlugins was not respected - if I remember well, if reporting plugins were only defined in reportingPlugins Maven 3 would report that it's not good practice that reporting plugin version is not specified. Only by specifying reporting plugins in pluginManagement I was able to configure required version, and have Maven not complain about bad practice. After specifying version of reporting plugins in pluginManagement section, I could, and now typically do remove version of plugins in reportPlugins section. > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Commented: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262778#action_262778 ] Stevo Slavic commented on MSITE-539: Yes, I found example there misleading, version element for every reporting plugin listed under reportPlugins was not respected - if I remember well, if reporting plugins were only defined in reportingPlugins Maven 3 would report that it's not good practice that reporting plugin version is not specified. Only by specifying reporting plugins in pluginManagement I was able to configure required version, and have Maven not complain about bad practice. After specifying version of reporting plugins in pluginManagement section, I could, and now typically do remove version of plugins in reportPlugins section. > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Commented: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262777#action_262777 ] Olivier Lamy commented on MSITE-539: Could you provide a sample which doesn't work and the corresponding mvn output execution > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Commented: (MSITE-539) Reporting plugin version references in new configuration example are wrong and misleading
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262776#action_262776 ] Olivier Lamy commented on MSITE-539: do you talked about [http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html] section New Configuration ?? > Reporting plugin version references in new configuration example are wrong > and misleading > - > > Key: MSITE-539 > URL: http://jira.codehaus.org/browse/MSITE-539 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Stevo Slavic >Priority: Minor > > [New configuration > example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration] > shows invalid reference to maven-javadoc-plugin version - version info there > won't break a build but it is simply not used by Maven 3 or site plugin > (maven reports that version info is not available for such reporting plugin). > Such wrong example might mislead users that this is expected way of > specifying version of reporting plugin used within maven site plugin > configuration. Example following new configuration example, related to > version resolution, is valid, it specifies reporting plugin version info in > pluginManagement section. -- 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
[jira] Issue Comment Edited: (MJARSIGNER-14) Keystore password should be entered in an interactive way
[
http://jira.codehaus.org/browse/MJARSIGNER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262674#action_262674
]
Eric TOURNIER edited comment on MJARSIGNER-14 at 4/7/11 4:07 AM:
-
This patch asks the user for a keystore password if it is not configured in
pom.xml
The case of a missing key password is not included in this patch
was (Author: eric_t):
This patch asks the user for a keystore password if it not configured in
pom.xml
The case of a missing key password is not included in this patch
> Keystore password should be entered in an interactive way
> -
>
> Key: MJARSIGNER-14
> URL: http://jira.codehaus.org/browse/MJARSIGNER-14
> Project: Maven 2.x Jar Signer Plugin
> Issue Type: Improvement
>Affects Versions: 1.2
>Reporter: Eric TOURNIER
>Priority: Minor
> Attachments: MJARSIGNER-14-maven-jarsigner-plugin.patch
>
>
> For security reasons, it could be useful not to configure keystore password
> in the {{pom.xml}} file. Then, when these informations are missing, the
> plugin should ask the user to enter this password in an interactive way.
--
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
[jira] Closed: (MSITE-342) Module name with double quotes breaks site descriptor
[ http://jira.codehaus.org/browse/MSITE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-342. --- Resolution: Duplicate Assignee: Lukas Theussl > Module name with double quotes breaks site descriptor > - > > Key: MSITE-342 > URL: http://jira.codehaus.org/browse/MSITE-342 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site descriptor >Reporter: Vladimir Tsukur >Assignee: Lukas Theussl >Priority: Minor > > Plugin doesn't work when there are double quotes in the module name. > E.g. the name of the module is specified as follows: > "flushpongle" Framework > or in this way: > "flushpongle" Framework > If you try to execute 'mvn site' on a module that have double quotes in its > name, you recieve the following error: > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error parsing site descriptor > Embedded error: expected = after attribute name (position: START_DOCUMENT > seen ...mitations\r\nunder the License.\r\n-->\r\n\r\n name=""flushpongle"... @21:29) > So, the name of the module is taken 'as is' for the value of name attribute. > Inner double quotes makes output invalid. -- 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
