Hi,

Maybe you have a custom settings.xml in so it cant find the snapshots:
C:\Users\holger.DESKTOP-HP9BDTK\.m2

Otherwise you can run 'ant clean package' from fop directory.

Thanks

-----Original Message-----
From: Holger Bast [mailto:holgerb...@gmx.de] 
Sent: 18 April 2017 13:26
To: Simon Steiner <simonsteiner1...@gmail.com>
Cc: fop-dev@xmlgraphics.apache.org
Subject: Re: Tagging fo:blocks as artifacts

Hi Simon,
I just made a fresh check out (trunk, 
http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/) and tried building fop 
with and without IntelliJ, but still no luck.
Attached you'll find the complete log output. As I already told Chris, I last 
programmed in Java more than 10 years ago; Maven is also new for me.

Sorry to bother you with that...

Bye, Holger


> Gesendet: Dienstag, 18. April 2017 um 10:59 Uhr
> Von: "Simon Steiner" <simonsteiner1...@gmail.com>
> An: fop-dev@xmlgraphics.apache.org, "'Holger Bast'" 
> <holgerb...@gmx.de>
> Betreff: RE: Aw: Re: Tagging fo:blocks as artifacts
>
> Hi,
> 
> Can you build using pom.xml in root of repo:
> http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/pom.xml?view=markup
> 
> Thanks
> 
> -----Original Message-----
> From: Chris [mailto:bowditch_ch...@hotmail.com]
> Sent: 18 April 2017 09:44
> To: Holger Bast <holgerb...@gmx.de>
> Cc: fop-dev@xmlgraphics.apache.org
> Subject: Re: Aw: Re: Tagging fo:blocks as artifacts
> 
> Hi Holger,
> 
> This may not be relevant to fop-users anymore, but it is relevant to 
> the dev list, which I've CC'd. Please subscribe so you can see the 
> replies
> 
> Thanks,
> 
> Chris
> 
> On 13/04/2017 18:15, Holger Bast wrote:
> > Hey Chris,
> > sorry for contacting you directly again. But I'm struggling setting 
> > up my toolchain to get started and I think this is no necessary information 
> > for the list..
> >
> > I installed IntelliJ and Java 8 (JDK). I also checked out the 
> > repository (trunk) but I can't compile the fop-core. I also tested 
> > branch fop-2.2, but always the same error. I already tried updating the 
> > repos manually (Maven -> Repos) but this didn't help either. How can I 
> > download the missing artifact?
> >
> > Should I start working on trunk or on the latest release?
> >
> > Bye Holger
> >
> >
> >
> > [ERROR] Failed to execute goal on project fop-core: Could not 
> > resolve dependencies for project
> > org.apache.xmlgraphics:fop-core:jar:2.2: The following artifacts could not 
> > be resolved:
> > org.apache.xmlgraphics:fop-events:jar:2.2,
> > org.apache.xmlgraphics:fop-util:jar:2.2: Failure to find
> > org.apache.xmlgraphics:fop-events:jar:2.2 in 
> > https://repository.apache.org/content/repositories/releases was 
> > cached in the local repository, resolution will not be reattempted 
> > until the update interval of apache.releases.https has elapsed or 
> > updates are forced -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
> > execute goal on project fop-core: Could not resolve dependencies for 
> > project org.apache.xmlgraphics:fop-core:jar:2.2: The following artifacts 
> > could not be resolved:
> > org.apache.xmlgraphics:fop-events:jar:2.2,
> > org.apache.xmlgraphics:fop-util:jar:2.2: Failure to find
> > org.apache.xmlgraphics:fop-events:jar:2.2 in 
> > https://repository.apache.org/content/repositories/releases was 
> > cached in the local repository, resolution will not be reattempted until 
> > the update interval of apache.releases.https has elapsed or updates are 
> > forced
> >     at 
> > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221)
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
> >     at 
> > org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245)
> >     at 
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
> >     at 
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> >     at 
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> >     at 
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> >     at 
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> >     at 
> > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> >     at 
> > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> >     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> >     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> >     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> >     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> >     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> >     at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> >     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >     at 
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> >     at 
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >     at java.lang.reflect.Method.invoke(Method.java:498)
> >     at 
> > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> >     at 
> > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> >     at 
> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> >     at 
> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> >     at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> > Caused by: org.apache.maven.project.DependencyResolutionException: 
> > Could not resolve dependencies for project
> > org.apache.xmlgraphics:fop-core:jar:2.2: The following artifacts could not 
> > be resolved:
> > org.apache.xmlgraphics:fop-events:jar:2.2,
> > org.apache.xmlgraphics:fop-util:jar:2.2: Failure to find
> > org.apache.xmlgraphics:fop-events:jar:2.2 in 
> > https://repository.apache.org/content/repositories/releases was 
> > cached in the local repository, resolution will not be reattempted until 
> > the update interval of apache.releases.https has elapsed or updates are 
> > forced
> >     at 
> > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:211)
> >     at 
> > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
> >     ... 24 more
> > Caused by: org.eclipse.aether.resolution.DependencyResolutionException: The 
> > following artifacts could not be resolved:
> > org.apache.xmlgraphics:fop-events:jar:2.2,
> > org.apache.xmlgraphics:fop-util:jar:2.2: Failure to find
> > org.apache.xmlgraphics:fop-events:jar:2.2 in 
> > https://repository.apache.org/content/repositories/releases was 
> > cached in the local repository, resolution will not be reattempted until 
> > the update interval of apache.releases.https has elapsed or updates are 
> > forced
> >     at 
> > org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
> >     at 
> > org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205)
> >     ... 25 more
> > Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The 
> > following artifacts could not be resolved:
> > org.apache.xmlgraphics:fop-events:jar:2.2,
> > org.apache.xmlgraphics:fop-util:jar:2.2: Failure to find
> > org.apache.xmlgraphics:fop-events:jar:2.2 in 
> > https://repository.apache.org/content/repositories/releases was 
> > cached in the local repository, resolution will not be reattempted until 
> > the update interval of apache.releases.https has elapsed or updates are 
> > forced
> >     at 
> > org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> >     at 
> > org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> >     at 
> > org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
> >     ... 26 more
> > Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: 
> > Failure to find
> > org.apache.xmlgraphics:fop-events:jar:2.2 in 
> > https://repository.apache.org/content/repositories/releases was 
> > cached in the local repository, resolution will not be reattempted until 
> > the update interval of apache.releases.https has elapsed or updates are 
> > forced
> >     at 
> > org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:231)
> >     at 
> > org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> >     at 
> > org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> >     at 
> > org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> >     at 
> > org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> >     ... 28 more
> > [ERROR]
> > [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/DependencyResolutio
> > nE
> > xception
> >
> > Process finished with exit code 1
> >
> >
> > Chris schrieb:
> >> Hi Holger,
> >>
> >> I'm happy to advise you, but please lets keep FOP related stuff on list.
> >>
> >> The basic info you need for setting up a FOP Dev environment is here:
> >> https://xmlgraphics.apache.org/fop/dev/
> >>
> >> The latest FOP versions are developed using Maven, which makes 
> >> importing the source code into your favorite IDE a one click process.
> >> I personally use IntelliJ, but others use Eclipse or Netbeans
> >>
> >> Thanks,
> >>
> >> Chris
> >>
> >> On 12/04/2017 09:04, Holger Bast wrote:
> >>> Hey Chris,
> >>> thx for your mail.
> >>> The last time I programmed in Java was more then 10 years ago. But I 
> >>> would try implementing this feature.
> >>> What do I need for that? Toolchain? Repository?
> >>>
> >>> Bye, Holger
> >>>
> >>>
> >>>> Gesendet: Montag, 10. April 2017 um 10:14 Uhr
> >>>> Von: Chris <bowditch_ch...@hotmail.com>
> >>>> An: "fop-us...@xmlgraphics.apache.org" 
> >>>> <fop-us...@xmlgraphics.apache.org>
> >>>> Betreff: Re: Tagging fo:blocks as artifacts
> >>>>
> >>>> Hi Holger,
> >>>>
> >>>> I agree the easiest solution would be to mark the unwanted blocks 
> >>>> as artifacts. Its a shame that FOP only supports role="artifact" 
> >>>> on fo:table-header and fo:table-footer :( If you were to submit a 
> >>>> patch on an enhancement it would be welcomed. I think this would 
> >>>> be a good improvement to FOP's accessibility support.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Chris
> >>>>
> >>>> On 05/04/2017 21:41, Holger Bast wrote:
> >>>>> Hi there,
> >>>>> I'm trying to use fop (2.1) to generate accessible pdf files. My 
> >>>>> document source is docbook5 that is transformed to xsl-fo and then 
> >>>>> processed with fop to pdf.
> >>>>> The official docbook5-xsl files often generate deep nested fo:block 
> >>>>> structures like the following example:
> >>>>>
> >>>>> <fo:block>
> >>>>>       <fo:block>
> >>>>>          <fo:block ...>
> >>>>>             <fo:block keep-with-next.within-column="always">
> >>>>>                <fo:block ...>
> >>>>>                   <fo:marker 
> >>>>> marker-class-name="section.head.marker">Level 1</fo:marker>
> >>>>>                   <fo:block font-size="20.735999999999997pt">1.1. Level 
> >>>>> 1</fo:block>
> >>>>>                </fo:block>
> >>>>>             </fo:block>
> >>>>>          </fo:block>
> >>>>>       </fo:block>
> >>>>>       <fo:block/>
> >>>>> </fo:block>
> >>>>>
> >>>>> This code also generates a deep nested p(aragraph) structure in 
> >>>>> the pdf file, because every fo:block automatically is tagged as 
> >>>>> paragraph. I'm trying to evaluate different approaches to get rid of 
> >>>>> this nested structure:
> >>>>>
> >>>>> 1) better code generation
> >>>>> That's the most obvious point but the docbook-xsl files are quite 
> >>>>> complex and I think this goal is hard to achieve.
> >>>>>
> >>>>> 2) tagging the unwanted block as 'artifacts'
> >>>>> Is there a way to tag fo:blocks as kind of artifact, so that 
> >>>>> they are not recognized being part of the document structure? 
> >>>>> The role="artifact" can only be applied to 'wrapper' and 
> >>>>> 'static-content' structures. An explicit way to deactivate tagging for 
> >>>>> dedicated structure elements would be nice and the easiest way for me.
> >>>>>
> >>>>> 3) merging of the fo:blocks
> >>>>> Another way would be merging all nested fo:blocks that only 
> >>>>> contain another fo:block element as child together that only one 
> >>>>> is left which can correctly be rendered. This goal is not easy to 
> >>>>> achieve, because you must have an eye on the attributes; 
> >>>>> addition/subtraction of indents and so on.
> >>>>>
> >>>>> 4) ??
> >>>>>
> >>>>> Did I forget something? Are there other ways to get rid of this nested 
> >>>>> structure?
> >>>>>
> >>>>> Thanks, Holger
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ----------------------------------------------------------------
> >>>>> --
> >>>>> --- To unsubscribe, e-mail: 
> >>>>> fop-users-unsubscr...@xmlgraphics.apache.org
> >>>>> For additional commands, e-mail: 
> >>>>> fop-users-h...@xmlgraphics.apache.org
> >>>>>
> >>>>> .
> >>>>>
> >>>> -----------------------------------------------------------------
> >>>> --
> >>>> -- To unsubscribe, e-mail: 
> >>>> fop-users-unsubscr...@xmlgraphics.apache.org
> >>>> For additional commands, e-mail: 
> >>>> fop-users-h...@xmlgraphics.apache.org
> >>>>
> >>>>
> >>> .
> >>>
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: 
> >> fop-users-unsubscr...@xmlgraphics.apache.org
> >> For additional commands, e-mail: 
> >> fop-users-h...@xmlgraphics.apache.org
> >>
> > .
> >
> 
> 
> 

Reply via email to