Re: How to create a site/doxia plugin?
Hi Peter,
IIUC, you want to create a JspWiki parser, to be able to write JspWiki markup
by hand and let maven-site-plugin parse it to integrate into the html site.
That's it?
Then the sink part is not interesting to you: this would to output JspWiki
format instead of html.
I fear I did not check this doc when I changed some bits over versions: there
are probably a few glitches in this doc.
I'll have a look.
In the mean time, just have a look at modules in Doxia itself should help you.
And remember: Parser is what you want to parse JspWiki. Sink is what you don't
need, to output JspWiki: would be useful only if you want to support JspWiki
as output in Doxia converter, for example [1]
Regards,
Hervé
[1] https://maven.apache.org/doxia/doxia-tools/doxia-converter/index.html
Le mardi 3 juillet 2018, 10:20:06 CEST Peter Nabbefeld a écrit :
> Hi Hervé,
>
> sorry for being unspecific - I want some basic support for JspWiki format.
>
> So far, I found https://maven.apache.org/doxia/developers/modules.html,
> but it's incomplete and outdated ("SinkFactory" was changed into an
> interface, "AbstractSiteModule" seems to no more exist).
>
> Kind regards
>
> Peter
>
> Am 03.07.2018 um 08:14 schrieb Hervé BOUTEMY:
> > Hi Peter,
> >
> > What do you call a Doxia plugin?
> >
> > I see misc interpretations:
> >
> > - a Doxia module [1], to support a new output format = a new Sink, see the
> > currfent modules that provide Sinks (and not only parsers) [2]
> >
> > - a Skin [3], to have a web site that matches better your intent
> >
> > - a new Maven plugin that integrates reports in another way than
> > maven-site- plugin and maven-pdf-plugin
> >
> > Perhaps it's something else: you'll need to describe more precisely what
> > parts you want to reuse and which part you want to extend
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://maven.apache.org/doxia/overview.html
> >
> > [2] https://maven.apache.org/doxia/references/index.html
> >
> > [3] https://maven.apache.org/skins/index.html
> >
> > Le mardi 3 juillet 2018, 07:30:19 CEST Peter Nabbefeld a écrit :
> >> Thank You, this is really an interesting plugin. But I don't want to
> >> break site generation, as I'm using it for other reports like JavaDoc,
> >> too.
> >>
> >> I just want to write a doxia plugin, if possible, as all text-based
> >> documentation generators seem to be more or less broken or at least not
> >> able to generate the docs in the way I want.
> >>
> >> Kind regards
> >>
> >> Peter
> >>
> >> Am 02.07.2018 um 14:48 schrieb Mark Raynsford:
> >>> On 2018-07-02T13:55:20 +0200
> >>>
> >>> Peter Nabbefeld wrote:
> Hello,
>
> I haven't ever written a maven plugin. But, as I'm not satisfied with
> the doxia plugins available, I'd like to write my own. So, how would I
> have to write a doxia plugin?
> >>>
> >>> Here's a plugin I wrote last year and still use to the present day:
> >>> https://github.com/io7m/minisite/
> >>>
> >>> It produces sites that look like this:
> >>> https://www.io7m.com/software/junreachable/
> >>>
> >>> The com.io7m.minisite.core module is independent of Maven, and the
> >>> com.io7m.minisite.maven_plugin module implements the actual plugin (by
> >>> taking data from the current Maven project and passing it to the core).
> >>>
> >>> One thing you will need to do is unbind the existing Maven site plugin
> >>> from the lifecycle in any project that actually uses your plugin
> >>> (assuming that you bind your own site plugin to the "site" phase of the
> >>>
> >>> build). Here's an example of how to do this:
> >>> https://github.com/io7m/primogenitor/blob/develop/pom.xml#L908
> >>
> >> -
> >> 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
>
> -
> 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: after upgrade to maven 3.5.4 release plans fail when trying to upload source jar twice
Hi Karl. 1) when I comment out the maven-source-plugin and run "mvn clean install" I don't see any -sources.jar files in my local repo. 2) I tried it just with the execution part commented out, and I don't see any -sources jars again. I had expected to from your above comment. 3) I noticed that the super pom changed from using a goal of "jar" to "jar-no-fork" http://maven.apache.org/ref/3.5.3/maven-model-builder/super-pom.html http://maven.apache.org/ref/3.5.4/maven-model-builder/super-pom.html I think that this is from an issue you originally reported https://issues.apache.org/jira/browse/MNG-5940 4) If I change my original config to have "jar-no-fork", then I get the original behaviour with both 3.5.3 and 3.5.4 (I think, only tested locally without nexus) 5) What's the suggested way to attach sources? If it's jar-no-fork then I think that the cookbook is out of date. https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html Tomorrow I'll test point #4 and if you say #5 if the best way, I'll make the change to our corporate pom. It will take a long time to have all the projects and prod branches updated. :-/ I really appreciate your help and time with this. Jim On Tue, Jul 3, 2018 at 3:06 PM Karl Heinz Marbaise wrote: > Hi, > > The issue looks a bit like: > > https://issues.apache.org/jira/browse/MNG-5359 > > On 03/07/18 21:04, Karl Heinz Marbaise wrote: > > Hi Jim, > > > > first thanks for the example project which helps a lot to find the real > > problem... > > > > > > So the issue is related to two things. First you have defined your own a > > release profile which is ok so far... > > > > The problem is related to the definition of the maven-sources-plugin > > like this: > > > > > >maven-source-plugin > >3.0.1 > > > > > >attach-sources > > > > jar > > > > > > > > > > > > which in result means the maven-source-plugin will be executed > > twice...which looks like this: > > > > > > > > [INFO] --- maven-source-plugin:3.0.1:jar-no-fork (attach-sources) @ > > hello-world-not-using-corp-parent-war --- > > [INFO] Building jar: > > > /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar > > > > > [INFO] > > [INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > > > generate-sources @ hello-world-not-using-corp-parent-war >>> > > [INFO] > > [INFO] <<< maven-source-plugin:3.0.1:jar (attach-sources) < > > generate-sources @ hello-world-not-using-corp-parent-war <<< > > [INFO] > > [INFO] > > [INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ > > hello-world-not-using-corp-parent-war --- > > [INFO] > > [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ > > hello-world-not-using-corp-parent-war --- > > [INFO] Skipping javadoc generation > > [INFO] > > [INFO] --- maven-install-plugin:2.4:install (default-install) @ > > hello-world-not-using-corp-parent-war --- > > [INFO] Installing > > > /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war > > > to > > > /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war > > > > > [INFO] Installing > > > /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/pom.xml > > > to > > > /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.pom > > > > > [INFO] Installing > > > /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar > > > to > > > /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar > > > > > [INFO] Installing > > > /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar > > > to > > > /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar > > > > > > > > > If you do a "mvn clean install" it will not cause a problem cause the > > created sources.jar will be overwritten...but if you do a mvn clean > > deploy nexus will prevent the upload of the second sources jar which >
Re: Wrong version ids in doxia-modules
Hi Pete, On 03/07/18 22:43, Peter Nabbefeld wrote: Hello, I'm experimenting with a doxia module, using org.apache.maven.doxia/doxia-modules/1.8 as parent. When looking at the effective graph, I see every dependency with version 1.0-SNAPSHOT, though release version is 1.8, e.g.: org.apache.maven.doxia doxia-core 1.0-SNAPSHOT test-jar I've also noticed, only version 1.0-SNAPSHOT is available as a jar dependency, all the release version are sources only - why? maybe I misunderstand your question but based on the search in Central: http://search.maven.org/#search%7Cga%7C1%7Corg.apache.maven.doxia They are all available as JAR's as well as sources etc. ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Wrong version ids in doxia-modules
Hello, I'm experimenting with a doxia module, using org.apache.maven.doxia/doxia-modules/1.8 as parent. When looking at the effective graph, I see every dependency with version 1.0-SNAPSHOT, though release version is 1.8, e.g.: org.apache.maven.doxia doxia-core 1.0-SNAPSHOT test-jar I've also noticed, only version 1.0-SNAPSHOT is available as a jar dependency, all the release version are sources only - why? Kind regards Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: after upgrade to maven 3.5.4 release plans fail when trying to upload source jar twice
Hi Karl. I've created a minimal project. The git and nexus / repo info would have to be set in a settings.xml file, and the nexus repo would have to not allow overwriting releases. https://github.com/sellersj/hello-world-not-using-corp-parent This works for maven 3.5.3 but not 3.5.4 If you need a log, I'll have to scrub it and that will take me more time. Thanks so much for your help. Jim On Sat, Jun 30, 2018 at 6:11 AM Jim Sellers wrote: > I’ll create one next week. > > Thanks for your help. > > Jim > On Sat, Jun 30, 2018 at 2:43 AM Karl Heinz Marbaise > wrote: > >> Hi Jim, >> >> On 29/06/18 21:15, Jim Sellers wrote: >> > Hi all. >> > >> > We have nexus reject over writing releases. >> > >> > After upgrading maven from 3.5.3 to 3.5.4, the release plan tries to >> upload >> > the -sources jars twice, failing the build. >> > >> > This is for a multi module project. >> > pom >> > \- ear >> > \- war >> > >> > Example error message >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy >> (default-deploy) >> > on project TestProjectWAR: Failed to deploy artifacts: Could not >> transfer >> > artifact ca.gc.ic.test:TestProjectWAR:jar:sources:1.6.0 from/to >> > internal-nexus ( >> > >> https://my-nexus.example.com/maven-proxy/content/repositories/internal-released >> ): >> > Failed to transfer file: >> > >> https://my-nexus.example.com/maven-proxy/content/repositories/internal-released/com/example/TestProjectWAR/1.6.0/TestProjectWAR-1.6.0-sources.jar >> . >> > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1] >> > >> > Revering maven to 3.5.3 fixes it. Anyone else seeing this behaviour? >> >> Do you have a sample project which reproduces the issue (github / >> bitbucket / gitlab) and very important the whole pom filesalso a log >> file would be helpful... >> >> >> Kind regards >> Karl Heinz Marbaise >> >
Re: after upgrade to maven 3.5.4 release plans fail when trying to upload source jar twice
Hi, The issue looks a bit like: https://issues.apache.org/jira/browse/MNG-5359 On 03/07/18 21:04, Karl Heinz Marbaise wrote: Hi Jim, first thanks for the example project which helps a lot to find the real problem... So the issue is related to two things. First you have defined your own a release profile which is ok so far... The problem is related to the definition of the maven-sources-plugin like this: maven-source-plugin 3.0.1 attach-sources jar which in result means the maven-source-plugin will be executed twice...which looks like this: [INFO] --- maven-source-plugin:3.0.1:jar-no-fork (attach-sources) @ hello-world-not-using-corp-parent-war --- [INFO] Building jar: /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar [INFO] [INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > generate-sources @ hello-world-not-using-corp-parent-war >>> [INFO] [INFO] <<< maven-source-plugin:3.0.1:jar (attach-sources) < generate-sources @ hello-world-not-using-corp-parent-war <<< [INFO] [INFO] [INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ hello-world-not-using-corp-parent-war --- [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ hello-world-not-using-corp-parent-war --- [INFO] Skipping javadoc generation [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ hello-world-not-using-corp-parent-war --- [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/pom.xml to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.pom [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar If you do a "mvn clean install" it will not cause a problem cause the created sources.jar will be overwritten...but if you do a mvn clean deploy nexus will prevent the upload of the second sources jar which result in the error you have described So the solution: The maven-source-plugin is already defined in the super pom of maven and if you simply omit the definition this will work: [INFO] --- maven-war-plugin:2.2:war (default-war) @ hello-world-not-using-corp-parent-war --- [INFO] Packaging webapp [INFO] Assembling webapp [hello-world-not-using-corp-parent-war] in [/Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp resources [/Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/src/main/webapp] [INFO] Webapp assembled in [24 msecs] [INFO] Building war: /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war [INFO] WEB-INF/web.xml already added, skipping [INFO] [INFO] --- maven-source-plugin:3.0.1:jar-no-fork (attach-sources) @ hello-world-not-using-corp-parent-war --- [INFO] Building jar: /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ hello-world-not-using-corp-parent-war --- [INFO] Skipping javadoc generation [INFO] [INFO] ---
Re: after upgrade to maven 3.5.4 release plans fail when trying to upload source jar twice
Hi Jim, first thanks for the example project which helps a lot to find the real problem... So the issue is related to two things. First you have defined your own a release profile which is ok so far... The problem is related to the definition of the maven-sources-plugin like this: maven-source-plugin 3.0.1 attach-sources jar which in result means the maven-source-plugin will be executed twice...which looks like this: [INFO] --- maven-source-plugin:3.0.1:jar-no-fork (attach-sources) @ hello-world-not-using-corp-parent-war --- [INFO] Building jar: /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar [INFO] [INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > generate-sources @ hello-world-not-using-corp-parent-war >>> [INFO] [INFO] <<< maven-source-plugin:3.0.1:jar (attach-sources) < generate-sources @ hello-world-not-using-corp-parent-war <<< [INFO] [INFO] [INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ hello-world-not-using-corp-parent-war --- [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ hello-world-not-using-corp-parent-war --- [INFO] Skipping javadoc generation [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ hello-world-not-using-corp-parent-war --- [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/pom.xml to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.pom [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar [INFO] Installing /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar to /Users/kama/.m2/repository/com/github/sellersj/no/corp/parent/hello-world-not-using-corp-parent-war/0.0.5-SNAPSHOT/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar If you do a "mvn clean install" it will not cause a problem cause the created sources.jar will be overwritten...but if you do a mvn clean deploy nexus will prevent the upload of the second sources jar which result in the error you have described So the solution: The maven-source-plugin is already defined in the super pom of maven and if you simply omit the definition this will work: [INFO] --- maven-war-plugin:2.2:war (default-war) @ hello-world-not-using-corp-parent-war --- [INFO] Packaging webapp [INFO] Assembling webapp [hello-world-not-using-corp-parent-war] in [/Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT] [INFO] Processing war project [INFO] Copying webapp resources [/Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/src/main/webapp] [INFO] Webapp assembled in [24 msecs] [INFO] Building war: /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT.war [INFO] WEB-INF/web.xml already added, skipping [INFO] [INFO] --- maven-source-plugin:3.0.1:jar-no-fork (attach-sources) @ hello-world-not-using-corp-parent-war --- [INFO] Building jar: /Users/kama/ws-git-maven-bugs/MNG-duplicate-files/hello-world-not-using-corp-parent/hello-world-not-using-corp-parent-war/target/hello-world-not-using-corp-parent-war-0.0.5-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ hello-world-not-using-corp-parent-war --- [INFO] Skipping javadoc generation [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ hello-world-not-using-corp-parent-war --- [INFO] Installing
Re: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter ->
On 30-06-18 16:39, Karen Goh wrote: Hi expert, I used maven build and run goal : deploy to see how my spring framework project run but I got the above error. There is this stackoverflow person which has similar problem as mine: https://stackoverflow.com/questions/27153024/repository-element-was-not-specified-in-the-pom-inside-distributionmanagement-el/39439911 So, I read up the below: https://maven.apache.org/pom.html#Distribution_Management My question is since I am doing this on a stand alone basis and do not need to share the POM denpendencies, how do I get rid of this message? you seem confused as to what "mvn deploy" actually does, it places an artifact in a repository, see: https://maven.apache.org/plugins/maven-deploy-plugin/ if that is not what you want then using mvn install should suffice. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: No compiler is provided in this environment - how to stop this error ?
On Sun, 6/24/18, Karl Heinz Marbaise wrote: Subject: Re: No compiler is provided in this environment - how to stop this error ? To: "Maven Users List" , jeffma...@jeffmaury.com Date: Sunday, June 24, 2018, 3:00 PM Hi, do you really want to work with SNAPSHOT versions? I would prefer to work with releases instead .. org.springframework.boot spring-boot-starter-parent 2.0.3.RELEASE which is available from Central... So you don't need any definition of repositories in your pom file...if you have just remove them... Furthermore I see in the screenshots that there are compilation errors...furthermore to drill down to the problem it would be more helpful to test on plain command line...and from within Eclipse etc.. Thanks Karl. Guess there is alot of things I have to pick up. Will watch youtube for tutorial in this area. Kind regards Karl Heinz Marbaise On 24/06/18 06:02, Karen Goh wrote: > Thanks Jeff. It is working now. > > However, I'd like to know is it possible to change the version to 2.0.3 from 2.1.0 in maven pom.xml ? > > > org.springframework.boot > spring-boot-starter-parent > 2.0.3.BUILD-SNAPSHOT > > > I have tried to change on the advice of a forum member in Java Range. > > But, I keep receiving error message : > > Project build error: Non-resolvable parent POM for com.Superhi5:SpringBootHi5CRUD:0.0.1-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring- > boot-starter-parent:pom:2.0.3.BUILD-SNAPSHOT from/to spring-snapshots (https://repo.spring.io/snapshot): repo.spring.io and 'parent.relativePath' points at no local > POM > > > I tried various ways like doing mvn clean, mvn purge local repositories, update and then sue the below as per stackoverflow suggestion to change the version but to no avai. > > >https://books.google.de/books?id=yEqrMNX3LAgC=PA124=IoIU0MYUp-=huettermann+automatic+releasing=de=PA123#v=onepage=huettermann%20automatic%20releasing=false > > Hope you could let me know how should I go about changing the version without all these errros. > > Tks & rgds, > Karen > > > > On Fri, 6/22/18, Jeff MAURY wrote: > > Subject: Re: No compiler is provided in this environment - how to stop this error ? > To: "Maven Users List" , "Karen Goh" > Date: Friday, June 22, 2018, 7:24 PM > > Your JAVA_HOME must point a jdk > not à jre > > Le ven. 22 juin > 2018 à 13:16, Karen Goh > a > écrit : > > > > Hi, > > > > I have been > trying to tackle the below error without avail. > > > > In my due diligence, > I have done the necessary checking like making sure > > that the environment is run on 1.8JDK > > > > Please see > screenshot > > > > https://ibb.co/eopTVT > > > > https://ibb.co/g2wE4o > > > > I got the below when > I did the following: > > > > 1st, I did run maven clean > > 2nd, I did maven install > > > > And the error > appeared. > > > > > > > > --- > maven-resources-plugin:3.0.1:resources (default-resources) > @ > > SpringBootHi5CRUD --- > > [INFO] Using 'UTF-8' encoding to > copy filtered resources. > > [INFO] Copying > 1 resource > > [INFO] Copying 0 resource > > [INFO] > > [INFO] --- > maven-compiler-plugin:3.7.0:compile (default-compile) @ > > SpringBootHi5CRUD --- > > > [INFO] Changes detected - recompiling the module! > > [INFO] Compiling 6 source files to > > > C:\Users\Karen.Goh\eclipse-workspace\SpringBoothi5\target\classes > > [INFO] > - > > [ERROR] COMPILATION ERROR : > > [INFO] > - > > [ERROR] No compiler is provided in this > environment. Perhaps you are > > running on > a JRE rather than a JDK? > > [INFO] 1 > error > > [INFO] > - > > [INFO] > > > > > [INFO] BUILD FAILURE > > > [INFO] > > > > > [INFO] Total time: 16.031 s > > [INFO] Finished at: > 2018-06-22T18:53:34+08:00 > > [INFO] Final > Memory: 20M/182M > > [INFO] > > > > > [ERROR] Failed to execute goal > > > org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile > > (default-compile) on project > SpringBootHi5CRUD: Compilation failure > > > [ERROR] No compiler is provided in this environment. Perhaps > you are > > running on a JRE
Re: How to create a site/doxia plugin?
Hi Hervé,
sorry for being unspecific - I want some basic support for JspWiki format.
So far, I found https://maven.apache.org/doxia/developers/modules.html,
but it's incomplete and outdated ("SinkFactory" was changed into an
interface, "AbstractSiteModule" seems to no more exist).
Kind regards
Peter
Am 03.07.2018 um 08:14 schrieb Hervé BOUTEMY:
Hi Peter,
What do you call a Doxia plugin?
I see misc interpretations:
- a Doxia module [1], to support a new output format = a new Sink, see the
currfent modules that provide Sinks (and not only parsers) [2]
- a Skin [3], to have a web site that matches better your intent
- a new Maven plugin that integrates reports in another way than maven-site-
plugin and maven-pdf-plugin
Perhaps it's something else: you'll need to describe more precisely what parts
you want to reuse and which part you want to extend
Regards,
Hervé
[1] https://maven.apache.org/doxia/overview.html
[2] https://maven.apache.org/doxia/references/index.html
[3] https://maven.apache.org/skins/index.html
Le mardi 3 juillet 2018, 07:30:19 CEST Peter Nabbefeld a écrit :
Thank You, this is really an interesting plugin. But I don't want to
break site generation, as I'm using it for other reports like JavaDoc, too.
I just want to write a doxia plugin, if possible, as all text-based
documentation generators seem to be more or less broken or at least not
able to generate the docs in the way I want.
Kind regards
Peter
Am 02.07.2018 um 14:48 schrieb Mark Raynsford:
On 2018-07-02T13:55:20 +0200
Peter Nabbefeld wrote:
Hello,
I haven't ever written a maven plugin. But, as I'm not satisfied with
the doxia plugins available, I'd like to write my own. So, how would I
have to write a doxia plugin?
Here's a plugin I wrote last year and still use to the present day:
https://github.com/io7m/minisite/
It produces sites that look like this:
https://www.io7m.com/software/junreachable/
The com.io7m.minisite.core module is independent of Maven, and the
com.io7m.minisite.maven_plugin module implements the actual plugin (by
taking data from the current Maven project and passing it to the core).
One thing you will need to do is unbind the existing Maven site plugin
from the lifecycle in any project that actually uses your plugin
(assuming that you bind your own site plugin to the "site" phase of the
build). Here's an example of how to do this:
https://github.com/io7m/primogenitor/blob/develop/pom.xml#L908
-
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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to create a site/doxia plugin?
Hi Peter, What do you call a Doxia plugin? I see misc interpretations: - a Doxia module [1], to support a new output format = a new Sink, see the currfent modules that provide Sinks (and not only parsers) [2] - a Skin [3], to have a web site that matches better your intent - a new Maven plugin that integrates reports in another way than maven-site- plugin and maven-pdf-plugin Perhaps it's something else: you'll need to describe more precisely what parts you want to reuse and which part you want to extend Regards, Hervé [1] https://maven.apache.org/doxia/overview.html [2] https://maven.apache.org/doxia/references/index.html [3] https://maven.apache.org/skins/index.html Le mardi 3 juillet 2018, 07:30:19 CEST Peter Nabbefeld a écrit : > Thank You, this is really an interesting plugin. But I don't want to > break site generation, as I'm using it for other reports like JavaDoc, too. > > I just want to write a doxia plugin, if possible, as all text-based > documentation generators seem to be more or less broken or at least not > able to generate the docs in the way I want. > > Kind regards > > Peter > > Am 02.07.2018 um 14:48 schrieb Mark Raynsford: > > On 2018-07-02T13:55:20 +0200 > > > > Peter Nabbefeld wrote: > >> Hello, > >> > >> I haven't ever written a maven plugin. But, as I'm not satisfied with > >> the doxia plugins available, I'd like to write my own. So, how would I > >> have to write a doxia plugin? > > > > Here's a plugin I wrote last year and still use to the present day: > >https://github.com/io7m/minisite/ > > > > It produces sites that look like this: > >https://www.io7m.com/software/junreachable/ > > > > The com.io7m.minisite.core module is independent of Maven, and the > > com.io7m.minisite.maven_plugin module implements the actual plugin (by > > taking data from the current Maven project and passing it to the core). > > > > One thing you will need to do is unbind the existing Maven site plugin > > from the lifecycle in any project that actually uses your plugin > > (assuming that you bind your own site plugin to the "site" phase of the > > > > build). Here's an example of how to do this: > >https://github.com/io7m/primogenitor/blob/develop/pom.xml#L908 > > - > 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
