Re: [maven-scm-publish-plugin] Could not copy content to SCM checkout... source... and destination... are the same
Thank you VERY much Hervé.
I looked at this code when I was tired and didn't see it.
Have a great weekend.
lewismc
On 2022/01/08 19:10:10 Hervé BOUTEMY wrote:
> Hi,
>
> I was able to reproduce your issue.
>
> If you read the log, there is no issue with svn command.
> The issue is when doing:
> [INFO] Updating checkout directory with actual content in /Users/lmcgibbn/
> Downloads/any23/any23-site
>
> and the error message is:
> Could not copy content to SCM checkout: Source 'xxx' and destination 'xxx'
> are
> the same -> [Help 1]
>
> and it's true:
> https://github.com/apache/any23/blob/master/pom.xml#L1244
>
> content value = ${site.filePath}
> checkoutDirectory = ${site.scmPubCheckoutDirectory} = ${site.filePath} (as
> defined in properties)
>
> that's not normal: content value should be something like target/site or
> target/staging
>
>
> see plugin documentation
> https://maven.apache.org/plugins/maven-scm-publish-plugin/
>
> (eventually contact me on ASF Slack...)
>
> Regards,
>
> Hervé
>
>
> Le samedi 8 janvier 2022, 08:48:12 CET lewis john mcgibbney a écrit :
> > Hi scm-users@,
> > Plugin configuration is as follows
> >
> >
> > org.apache.maven.plugins
> > maven-scm-publish-plugin
> > 3.1.0
> >
> > true
> > Apache Any23 ${project.version} site
> > deployment
> >
> > ${site.scmPubCheckoutDirectory}
> > ${site.deploymentBaseUrl}
> > ${site.filePath}
> >
> >
> >
> > When I execute it as part of the Apache Any23 website release (
> > https://github.com/apache/any23/blob/master/deploy-site.sh#L20) it fails
> > with the following
> >
> > [INFO] --- maven-scm-publish-plugin:3.1.0:publish-scm (default-cli) @
> > apache-any23 ---
> > [INFO] Updating the pub tree from scm:svn:
> > https://svn.apache.org/repos/asf/any23/site into
> > /Users/lmcgibbn/Downloads/any23/any23-site
> > [INFO] Executing: /bin/sh -c cd /Users/lmcgibbn/Downloads/any23/any23-site
> > && svn --username lewismc --password '*' --no-auth-cache
> > --non-interactive update /Users/lmcgibbn/Downloads/any23/any23-site@
> > [INFO] Updating checkout directory with actual content in
> > /Users/lmcgibbn/Downloads/any23/any23-site
> > [INFO]
> >
> > [INFO] Reactor Summary for Apache Any23 2.7-SNAPSHOT:
> > [INFO]
> > [INFO] Apache Any23 ... FAILURE [
> > 2.957 s]
> > [INFO] Apache Any23 :: Base API ... SUCCESS [
> > 23.288 s]
> > [INFO] Apache Any23 :: Test Resources . SUCCESS [
> > 9.331 s]
> > [INFO] Apache Any23 :: CSV Utilities .. SUCCESS [
> > 14.311 s]
> > [INFO] Apache Any23 :: Mime Type Detection SUCCESS [
> > 20.215 s]
> > [INFO] Apache Any23 :: Encoding Detection . SUCCESS [
> > 18.632 s]
> > [INFO] Apache Any23 :: Core ... SUCCESS [
> > 32.095 s]
> > [INFO] Apache Any23 :: CLI SUCCESS [
> > 21.820 s]
> > [INFO]
> >
> > [INFO] BUILD FAILURE
> > [INFO]
> >
> > [INFO] Total time: 02:55 min
> > [INFO] Finished at: 2022-01-07T23:20:55-08:00
> > [INFO]
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm
> > (default-cli) on project apache-any23: Could not copy content to SCM
> > checkout: Source
> > '/Users/lmcgibbn/Downloads/any23/any23-site/.svn/pristine/61/617e72262042de8
> > cf1f11bc8e3aaa231669f181a.svn-base' and destination
> > '/Users/lmcgibbn/Downloads/any23/any23-site/.svn/pristine/61/617e72262042de8
> > cf1f11bc8e3aaa231669f181a.svn-base' are the same -> [Help 1]
> >
> > As you can see the svn update configuration seems to add an at character in
> > the website checkout directory /Users/lmcgibbn/Downloads/any23/any23-site@
> >
> > Can someone explain why this is happening and does anyone have a suggestion
> > for how I fix it?
> >
> > I also saw https://issues.apache.org/jira/browse/SCM-859 and I looked at
> > the corresponding pull request but there is not too much context.
> >
> > Thanks for any assistance.
> >
> > lewismc
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[maven-scm-publish-plugin] Could not copy content to SCM checkout... source... and destination... are the same
Hi scm-users@,
Plugin configuration is as follows
org.apache.maven.plugins
maven-scm-publish-plugin
3.1.0
true
Apache Any23 ${project.version} site
deployment
${site.scmPubCheckoutDirectory}
${site.deploymentBaseUrl}
${site.filePath}
When I execute it as part of the Apache Any23 website release (
https://github.com/apache/any23/blob/master/deploy-site.sh#L20) it fails
with the following
[INFO] --- maven-scm-publish-plugin:3.1.0:publish-scm (default-cli) @
apache-any23 ---
[INFO] Updating the pub tree from scm:svn:
https://svn.apache.org/repos/asf/any23/site into
/Users/lmcgibbn/Downloads/any23/any23-site
[INFO] Executing: /bin/sh -c cd /Users/lmcgibbn/Downloads/any23/any23-site
&& svn --username lewismc --password '*' --no-auth-cache
--non-interactive update /Users/lmcgibbn/Downloads/any23/any23-site@
[INFO] Updating checkout directory with actual content in
/Users/lmcgibbn/Downloads/any23/any23-site
[INFO]
[INFO] Reactor Summary for Apache Any23 2.7-SNAPSHOT:
[INFO]
[INFO] Apache Any23 ... FAILURE [
2.957 s]
[INFO] Apache Any23 :: Base API ... SUCCESS [
23.288 s]
[INFO] Apache Any23 :: Test Resources . SUCCESS [
9.331 s]
[INFO] Apache Any23 :: CSV Utilities .. SUCCESS [
14.311 s]
[INFO] Apache Any23 :: Mime Type Detection SUCCESS [
20.215 s]
[INFO] Apache Any23 :: Encoding Detection . SUCCESS [
18.632 s]
[INFO] Apache Any23 :: Core ... SUCCESS [
32.095 s]
[INFO] Apache Any23 :: CLI SUCCESS [
21.820 s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 02:55 min
[INFO] Finished at: 2022-01-07T23:20:55-08:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm
(default-cli) on project apache-any23: Could not copy content to SCM
checkout: Source
'/Users/lmcgibbn/Downloads/any23/any23-site/.svn/pristine/61/617e72262042de8cf1f11bc8e3aaa231669f181a.svn-base'
and destination
'/Users/lmcgibbn/Downloads/any23/any23-site/.svn/pristine/61/617e72262042de8cf1f11bc8e3aaa231669f181a.svn-base'
are the same -> [Help 1]
As you can see the svn update configuration seems to add an at character in
the website checkout directory /Users/lmcgibbn/Downloads/any23/any23-site@
Can someone explain why this is happening and does anyone have a suggestion
for how I fix it?
I also saw https://issues.apache.org/jira/browse/SCM-859 and I looked at
the corresponding pull request but there is not too much context.
Thanks for any assistance.
lewismc
--
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc
Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory
Hi Jörg,
This is excellent and worked a treat. Thank you so much, for future reference,
once the dependencies are declared with a , here is the correct plugin
configuration solution
org.apache.maven.plugins
maven-dependency-plugin
copy
prepare-package
copy-dependencies
provided
${output.directory}
Really clean and very useful.
Thank you
Lewis
On 2018/02/23 23:05:42, Jörg Schaible wrote:
> Hi,
>
> if you use the copy goal, you don't have to add them to your list of
> dependencies. Personally I would use the
> copy-dependencies goal and copy only the ones with scope provided (i.e. you
> don't have to specify each one
> again).
>
> Cheers,
> Jörg
>
>
> Am Fri, 23 Feb 2018 09:58:09 -0800 schrieb lewis john mcgibbney:
>
> > I should also say, that the workaround is to list each and every
> > transitive dependency in the dependency declaration with scope
> > 'provided', such that they are NOT on the normal runtime classpath but
> > ARE correctly copied into the target directory defined within the
> > maven-dependency-plugin configuration as shown above.
> > The only issue with this workaround is that it is extremely messy,
> > bloats my POM and is difficult to maintain as I have now introduced
> > around 50 or so additional dependencies which all have versions, etc.
> > Thanks again for any hints.
> > Lewis
> >
> > On Fri, Feb 23, 2018 at 9:55 AM, lewis john mcgibbney
> > wrote:
> >
> >> Hello users@,
> >> I am looking to dynamically load JAR's during a program execution based
> >> upon a users input and therefore using the maven-dependency-plugin to
> >> do this.
> >> Specifically, the plugin configuration looks as follows
> >>
> >>
> >> org.apache.maven.plugins
> >> maven-dependency-plugin
> >>
> >>
> >> copy prepare-package
> >>
> >> copy
> >>
> >>
> >>
> >>
> >> org.apache.any23.plugins
> >> apache-any23-openie
> >> ${project.version}
> >> ${output.directory}
> >>
> >> ...
> >> This works fine, however I have an issue with regards to these specific
> >> JARs being present on the classpath during the build and runtime
> >> depending on the I assign to them within the dependency
> >> definition.
> >> If I mark the scope as 'runtime', the dependencies are added to the
> >> normal classpath which I do not want, as the purpose here is dynamic
> >> classloading via user input.
> >> On the other hand, if I define the dependency scope as 'provided' then
> >> no transitive dependencies are acquired hence I encounter
> >> java.lang.NoClassDefFoundError as although the primary dependency is
> >> present, it's own dependencies are not.
> >>
> >> Does anyone have a way to get around this. Ideally I am looking for a
> >> solution to define a specific location I was dependencies (and the
> >> transitive dependencies) to reside such that I can load them
> >> dynamically at runtime.
> >> Thank you kindly in advance,
> >> Lewis
> >>
> >> --
> >> http://home.apache.org/~lewismc/
> >> http://people.apache.org/keys/committer/lewismc
> >>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory
I should also say, that the workaround is to list each and every transitive
dependency in the dependency declaration with scope 'provided', such that
they are NOT on the normal runtime classpath but ARE correctly copied into
the target directory defined within the maven-dependency-plugin
configuration as shown above.
The only issue with this workaround is that it is extremely messy, bloats
my POM and is difficult to maintain as I have now introduced around 50 or
so additional dependencies which all have versions, etc.
Thanks again for any hints.
Lewis
On Fri, Feb 23, 2018 at 9:55 AM, lewis john mcgibbney
wrote:
> Hello users@,
> I am looking to dynamically load JAR's during a program execution based
> upon a users input and therefore using the maven-dependency-plugin to do
> this.
> Specifically, the plugin configuration looks as follows
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> copy
> prepare-package
>
> copy
>
>
>
>
> org.apache.any23.plugins
> apache-any23-openie
> ${project.version}
> ${output.directory}
>
> ...
> This works fine, however I have an issue with regards to these specific
> JARs being present on the classpath during the build and runtime depending
> on the I assign to them within the dependency definition.
> If I mark the scope as 'runtime', the dependencies are added to the normal
> classpath which I do not want, as the purpose here is dynamic classloading
> via user input.
> On the other hand, if I define the dependency scope as 'provided' then no
> transitive dependencies are acquired hence I encounter
> java.lang.NoClassDefFoundError as although the primary dependency is
> present, it's own dependencies are not.
>
> Does anyone have a way to get around this. Ideally I am looking for a
> solution to define a specific location I was dependencies (and the
> transitive dependencies) to reside such that I can load them dynamically at
> runtime.
> Thank you kindly in advance,
> Lewis
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>
--
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc
[Maven Dependency Plugin] Inheriting transitive dependencies whilst defining an artifact output directory
Hello users@,
I am looking to dynamically load JAR's during a program execution based
upon a users input and therefore using the maven-dependency-plugin to do
this.
Specifically, the plugin configuration looks as follows
org.apache.maven.plugins
maven-dependency-plugin
copy
prepare-package
copy
org.apache.any23.plugins
apache-any23-openie
${project.version}
${output.directory}
...
This works fine, however I have an issue with regards to these specific
JARs being present on the classpath during the build and runtime depending
on the I assign to them within the dependency definition.
If I mark the scope as 'runtime', the dependencies are added to the normal
classpath which I do not want, as the purpose here is dynamic classloading
via user input.
On the other hand, if I define the dependency scope as 'provided' then no
transitive dependencies are acquired hence I encounter
java.lang.NoClassDefFoundError as although the primary dependency is
present, it's own dependencies are not.
Does anyone have a way to get around this. Ideally I am looking for a
solution to define a specific location I was dependencies (and the
transitive dependencies) to reside such that I can load them dynamically at
runtime.
Thank you kindly in advance,
Lewis
--
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc
Re: Deploying non-unique SNAPSHOTs
If I do mvn package and build the snapshots locally (which I think builds non unique artifacts) can I then manually push these to the apache snapshots repository? Thank you. Lewis On Saturday, February 23, 2013, Joachim Durchholz wrote: > Am 23.02.2013 17:44, schrieb Lewis John Mcgibbney: >> >> I'm on 3.x unfortunately. >> @Joachim >> Can you please elaborate a bit on artifactory please? > > I have no access to the Artifactory installation right now and for the upcoming week. > IIRC it's an option on the repository. I modified only those repositories where I'm actually deploying stuff to, which was just one for us: local-lib-snapshot or something like that. > Hope that gets you going. > > Regards, > Jo > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- *Lewis*
Re: Deploying non-unique SNAPSHOTs
I'm on 3.x unfortunately. @Joachim Can you please elaborate a bit on artifactory please? Thanks Lewis On Saturday, February 23, 2013, Joachim Durchholz wrote: > Am 23.02.2013 08:55, schrieb Stephen Connolly: >> >> Maven 3.x removed the ability to deploy non-unique snapshots. > > This should be documented in the plugin's docs. > I wasted half an afternoon trying to get this to work, and that was just for me. > > There's an option on the repository in Artifactory that can restore that behaviour. > I guess Artifactory is simply stripping off the unique identifiers. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- *Lewis*
Re: Is install always required before compile?
Hi Dennis On Sun, Aug 12, 2012 at 7:28 PM, Dennis Lundberg wrote: > No. My gut feeling is that you have something wrong in your dependency > tree regarding your internal modules. Looking at the parent pom.xml you > seem to be using test jars in two different ways. Either type=test-jar > or classifier=tests. The first one has had problems depending on which > version of Maven you use, see http://jira.codehaus.org/browse/MNG-2045 > Changing the incorrect 's to 's for consistency worked a charm and its now solved. This was actually careless from me as it was myself that initially changed the classifier's to types as per the maven javadoc plugin notes. Thank you very much for your quick, constructive feedback. Best Lewis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Is install always required before compile?
Hi, I am currently working on a project which has required us to branch [0] Gora trunk and begin some slight APi refactoring to accommodate the added functionality we intend to implement. I have one question though. If I do a clean checkout of the code then run mvn clean compile I get a failure due to the new refactoring. If however I do mvn clean install, then mvn clean compile everything is OK. Is this normal behavior? Kind Regards and thank you in advance for any suggestion or help. Lewis [0] http://svn.apache.org/repos/asf/gora/branches/goraamazon/ -- Lewis - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Incorrectly generated URLs in pom's using maven release plugin
Hi Dennis, On Mon, Apr 23, 2012 at 9:54 PM, Dennis Lundberg wrote: > > > > There are some wrong urls in the pom.xml files, namely in the scm > section. > > (I am not sure what impact of this is). It is about: > > -the pom.xml in the project root --> seems incorrect. > > > Not sure what happened to this one... > Do you envisage that this will pose any problems further down the line, other than something which could be considered simply as a typo of sorts? I am speaking from RM perspective and whether this justifies rolling another RC. What do you think? > > > -the sources-dist/pom.xml --> like above, plus: url, connection and > > developerConnection have 'trunk' postfixed. > > -the subprojects (store implementations) pom.xml --> like above. > > This is because the SCM URLs that you have in your subprojects in trunk > are wrong. They are currently pointing to > http://svn.apache.org/viewvc/gora/trunk/ > when they should be pointing to > http://svn.apache.org/viewvc/gora/trunk// > > OK I will update this in the project trunk, I suppose the same stands for this as does for the above! Again, thanks in advance for your input. Best Lewis
Incorrectly generated URLs in pom's using maven release plugin
Hi, When pushing out a release candidate for a VOTE, it was brought to my attention that all generated module pom's contain incorrect URLs. I've attached a brief description of what is wrong below with the link to the staged repos here [0]. The release plugin is version 2.2.2 There are some wrong urls in the pom.xml files, namely in the scm section. (I am not sure what impact of this is). It is about: -the pom.xml in the project root --> seems incorrect. -the sources-dist/pom.xml --> like above, plus: url, connection and developerConnection have 'trunk' postfixed. -the subprojects (store implementations) pom.xml --> like above. My cmd's to create the staged tag was mvn release:clean release:prepare -P apache -DautoVersionSubmodules=true mvn release:perform -P apache 1) WIll these characteristics have any relative effect on the atrifacts? 2) Is there any mechanism I can use to prevent this happening? If it is trivial then I will more than likely spin another RC. Thank you in advance for any help. Lewis [0] https://repository.apache.org/content/repositories/orgapachegora-074/ -- *Lewis*
Using Maven Shade plugin to create Uber-Jar of another Maven plugin
Hi, There is some code within the maven-license-plugin which I would like to package into a jar file and extend, this would enable my project to use it @ runtime. I am currently working to configure the Maven shade plugin to do this, but haven't quite got the configuration correct yet. First things first I suppose... 1) Has anyone used the maven-shade-plugin to retrieve a plugin artefact and use the resulting uber jar within your /lib directory @ runtime. If so can anyone pass on some implementation details as I'm struggling? My project is structured as follows parent project ├── main module │ ├── build │ ├── conf │ │ └── license-headers.txt for use @ runtime │ ├── lib <<< location where I would like the shaded maven-license-plugin uber jar to be available for use @ runtime │ ├── lib-ext │ ├── pom.xml │ ├── src │ │ │ └── target ├── parent-pom.xml I thought it would be best to try and describe the problem before I begin pasting pom.xml code all ovet the place. Thanks in advance for any suggestions or direction. Lewis -- *Lewis*
