[jira] [Commented] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Jira


[ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335175#comment-17335175
 ] 

Andreas Lehmkühler commented on PDFBOX-5180:


PDFBOX-3386 is about the downgrade of the plugin. It is 5 years ago prior to 
2.0.3. I'm wondering why nobody else complaint about that. However, I've found 
some evidence on my local machine at least for the SNAPSHOT of 2.0.16

On the other hand we are using the enforcer plugin and are defining java 1.7 
and maven 3.1 as minimum requirement. Saying that, it should be save to update 
the plugin to 3.5.1. Starting with 4.0.0 the minimum java version is 8

[~Schmidor] How did you locally check that your changes work?

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
> Attachments: pom.xml
>
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Comment Edited] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Tilman Hausherr (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335112#comment-17335112
 ] 

Tilman Hausherr edited comment on PDFBOX-5180 at 4/29/21, 3:29 AM:
---

Yes there was a complaint that the 2.0 version didn't build on a jdk6 system.

I'm not sure if we had given up on that one, in favor of using the jdk6 system 
for compiling only (which failed with some maven versions).


was (Author: tilman):
Yes there was a complaint that the 2.0 version didn't build on a jdk6 system.

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
> Attachments: pom.xml
>
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2602) Enhance command line tools

2021-04-28 Thread Tilman Hausherr (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335115#comment-17335115
 ] 

Tilman Hausherr commented on PDFBOX-2602:
-

I've created PDFBOX-5181. Yes, checking for whether we're running headless 
would be the solution I prefer.

> Enhance command line tools
> --
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.8.8, 2.0.0
>Reporter: Maruan Sahyoun
>Assignee: Maruan Sahyoun
>Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all 
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an 
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards 
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Updated] (PDFBOX-5181) pdfbox-app doesn't run in a headless environment

2021-04-28 Thread Tilman Hausherr (Jira)


 [ 
https://issues.apache.org/jira/browse/PDFBOX-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tilman Hausherr updated PDFBOX-5181:

Component/s: Utilities

> pdfbox-app doesn't run in a headless environment
> 
>
> Key: PDFBOX-5181
> URL: https://issues.apache.org/jira/browse/PDFBOX-5181
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 3.0.0 PDFBox
>Reporter: Tilman Hausherr
>Priority: Major
>
> Follow-up to PDFBOX-2602
> {code}
> ...
> Caused by: java.awt.HeadlessException:
> No X11 DISPLAY variable was set, but this program performed an operation 
> which requires it.
> at 
> java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208)
> at java.desktop/java.awt.Window.(Window.java:548)
> at java.desktop/java.awt.Frame.(Frame.java:423)
> at java.desktop/java.awt.Frame.(Frame.java:388)
> at java.desktop/javax.swing.JFrame.(JFrame.java:180)
> at org.apache.pdfbox.debugger.PDFDebugger.(PDFDebugger.java:208)
> ... 18 more
> {code}
> PDFDebugger it itself an awt object (a JFrame).
> We may also run into problems with tools that use awt, e.g. PDFToImage.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Updated] (PDFBOX-5181) pdfbox-app doesn't run in a headless environment

2021-04-28 Thread Tilman Hausherr (Jira)


 [ 
https://issues.apache.org/jira/browse/PDFBOX-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tilman Hausherr updated PDFBOX-5181:

Description: 
Follow-up to PDFBOX-2602
{code}
...
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which 
requires it.
at 
java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208)
at java.desktop/java.awt.Window.(Window.java:548)
at java.desktop/java.awt.Frame.(Frame.java:423)
at java.desktop/java.awt.Frame.(Frame.java:388)
at java.desktop/javax.swing.JFrame.(JFrame.java:180)
at org.apache.pdfbox.debugger.PDFDebugger.(PDFDebugger.java:208)
... 18 more
{code}
PDFDebugger it itself an awt object (a JFrame).

We may also run into problems with tools that use awt, e.g. PDFToImage.


  was:
Follow-up to PDFBOX-2602
{code}
...
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which 
requires it.
at 
java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208)
at java.desktop/java.awt.Window.(Window.java:548)
at java.desktop/java.awt.Frame.(Frame.java:423)
at java.desktop/java.awt.Frame.(Frame.java:388)
at java.desktop/javax.swing.JFrame.(JFrame.java:180)
at org.apache.pdfbox.debugger.PDFDebugger.(PDFDebugger.java:208)
... 18 more
{code}



> pdfbox-app doesn't run in a headless environment
> 
>
> Key: PDFBOX-5181
> URL: https://issues.apache.org/jira/browse/PDFBOX-5181
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 3.0.0 PDFBox
>Reporter: Tilman Hausherr
>Priority: Major
>
> Follow-up to PDFBOX-2602
> {code}
> ...
> Caused by: java.awt.HeadlessException:
> No X11 DISPLAY variable was set, but this program performed an operation 
> which requires it.
> at 
> java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208)
> at java.desktop/java.awt.Window.(Window.java:548)
> at java.desktop/java.awt.Frame.(Frame.java:423)
> at java.desktop/java.awt.Frame.(Frame.java:388)
> at java.desktop/javax.swing.JFrame.(JFrame.java:180)
> at org.apache.pdfbox.debugger.PDFDebugger.(PDFDebugger.java:208)
> ... 18 more
> {code}
> PDFDebugger it itself an awt object (a JFrame).
> We may also run into problems with tools that use awt, e.g. PDFToImage.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Created] (PDFBOX-5181) pdfbox-app doesn't run in a headless environment

2021-04-28 Thread Tilman Hausherr (Jira)
Tilman Hausherr created PDFBOX-5181:
---

 Summary: pdfbox-app doesn't run in a headless environment
 Key: PDFBOX-5181
 URL: https://issues.apache.org/jira/browse/PDFBOX-5181
 Project: PDFBox
  Issue Type: Bug
Affects Versions: 3.0.0 PDFBox
Reporter: Tilman Hausherr


Follow-up to PDFBOX-2602
{code}
...
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which 
requires it.
at 
java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208)
at java.desktop/java.awt.Window.(Window.java:548)
at java.desktop/java.awt.Frame.(Frame.java:423)
at java.desktop/java.awt.Frame.(Frame.java:388)
at java.desktop/javax.swing.JFrame.(JFrame.java:180)
at org.apache.pdfbox.debugger.PDFDebugger.(PDFDebugger.java:208)
... 18 more
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Tilman Hausherr (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335112#comment-17335112
 ] 

Tilman Hausherr commented on PDFBOX-5180:
-

Yes there was a complaint that the 2.0 version didn't build on a jdk6 system.

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
> Attachments: pom.xml
>
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Oliver Schmidtmer (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335006#comment-17335006
 ] 

Oliver Schmidtmer commented on PDFBOX-5180:
---

Changing the maven-bundle-plugin version from 2.5.4 to 5.1.1 as in trunk did it 
for me. But that is commented in the POM with ""

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
> Attachments: pom.xml
>
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Updated] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Oliver Schmidtmer (Jira)


 [ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Schmidtmer updated PDFBOX-5180:
--
Attachment: pom.xml

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
> Attachments: pom.xml
>
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Updated] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Oliver Schmidtmer (Jira)


 [ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Schmidtmer updated PDFBOX-5180:
--
Attachment: (was: pom.xml)

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Updated] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Oliver Schmidtmer (Jira)


 [ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Schmidtmer updated PDFBOX-5180:
--
Attachment: pom.xml

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
> Attachments: pom.xml
>
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2602) Enhance command line tools

2021-04-28 Thread Maruan Sahyoun (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334916#comment-17334916
 ] 

Maruan Sahyoun commented on PDFBOX-2602:


One option is to check if we are running in a headless env and only dependent 
on that include/don't include the debug command. That's a change to how the 
debug command is included/detected by picocli.

> Enhance command line tools
> --
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.8.8, 2.0.0
>Reporter: Maruan Sahyoun
>Assignee: Maruan Sahyoun
>Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all 
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an 
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards 
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2602) Enhance command line tools

2021-04-28 Thread Maruan Sahyoun (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334906#comment-17334906
 ] 

Maruan Sahyoun commented on PDFBOX-2602:


Wouldn't it be easier to remove PDFDebugger from the PDFBox up as we also 
distribute it as a standalone app?

if we want to keep it for convenience I can look at resolving the issue. 
Rendenring commands will also not work in a headless environment also it's not 
immediately visible because they are initialized later. 

Shouldn't we handle it in a different ticket?

> Enhance command line tools
> --
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.8.8, 2.0.0
>Reporter: Maruan Sahyoun
>Assignee: Maruan Sahyoun
>Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all 
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an 
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards 
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2602) Enhance command line tools

2021-04-28 Thread Tilman Hausherr (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334889#comment-17334889
 ] 

Tilman Hausherr commented on PDFBOX-2602:
-

How about an intermediate class between PDFBox and PDFDebugger that just passes 
the parameters?

> Enhance command line tools
> --
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.8.8, 2.0.0
>Reporter: Maruan Sahyoun
>Assignee: Maruan Sahyoun
>Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all 
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an 
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards 
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Tilman Hausherr (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334850#comment-17334850
 ] 

Tilman Hausherr commented on PDFBOX-5180:
-

Seems we're not the first with this problem:
https://stackoverflow.com/questions/4251488/maven-release-plugin-fails-source-artifacts-getting-deployed-twice
https://stackoverflow.com/questions/28407831/maven-maven-deploy-plugin-always-upload-twice


> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2602) Enhance command line tools

2021-04-28 Thread Tilman Hausherr (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334849#comment-17334849
 ] 

Tilman Hausherr commented on PDFBOX-2602:
-

Ouch, this one is more complicated, PDFDebugger it itself an awt object (a 
JFrame). Maybe we need to find out whether PDFBox is running in headless mode.

> Enhance command line tools
> --
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.8.8, 2.0.0
>Reporter: Maruan Sahyoun
>Assignee: Maruan Sahyoun
>Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all 
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an 
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards 
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-5180) Snapshot Deploy not working

2021-04-28 Thread Oliver Schmidtmer (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334846#comment-17334846
 ] 

Oliver Schmidtmer commented on PDFBOX-5180:
---

Most likely there are changes between 2.0 and trunk in the POMs, which cause 
this to be resolved.

Theres a blog post, 
[https://www.robinhowlett.com/blog/2019/05/15/solved-when-the-maven-deploy-plugin-silently-fails-to-deploy/]
 , where this problem was caused by differences between the root POM and the 
sub POMs. When I have time for that, I will try to find out which changes 
between 2.0 to trunk might be the cause.

> Snapshot Deploy not working
> ---
>
> Key: PDFBOX-5180
> URL: https://issues.apache.org/jira/browse/PDFBOX-5180
> Project: PDFBox
>  Issue Type: Bug
>Affects Versions: 2.0.24
>Reporter: Oliver Schmidtmer
>Priority: Major
>
> When building and deploying snapshots, the build number is higher than the 
> last uploaded snapshot. So the dependency resolution to 2.0.24-SNAPSHOT does 
> not work.
> It seems the deploy plugin is triggered twice, but only once there are 
> uploads. The other sub projects are also affected.
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/2.0.24-SNAPSHOT/maven-metadata.xml]
> {code:java}
> 
>  org.apache.pdfbox
>  pdfbox
>  2.0.24-SNAPSHOT
>   
>
>20210426.180431
>154
>   
>   20210426180431
>   
>
> jar
> 2.0.24-20210426.180213-153
> 20210426180431
>
>
> pom
>  2.0.24-20210426.180213-153
>  20210426180431
> 
>   
>  
> 
> {code}
> In trunk / 3.0 this doesn't happen:
>  
> [https://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox/3.0.0-SNAPSHOT/maven-metadata.xml]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2941) Improve PDFDebugger (2)

2021-04-28 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334842#comment-17334842
 ] 

ASF subversion and git services commented on PDFBOX-2941:
-

Commit 1889270 from Tilman Hausherr in branch 'pdfbox/branches/2.0'
[ https://svn.apache.org/r1889270 ]

PDFBOX-2941: don't abort if there's an exception when rendering a glyph; remove 
unneeded code

> Improve PDFDebugger (2)
> ---
>
> Key: PDFBOX-2941
> URL: https://issues.apache.org/jira/browse/PDFBOX-2941
> Project: PDFBox
>  Issue Type: Improvement
>  Components: Utilities
>Affects Versions: 2.0.0
>Reporter: Tilman Hausherr
>Priority: Major
> Attachments: gs-bugzilla694570.pdf, keep_zoom.diff, osx-tabs.png, 
> pdfdebugger-screenshot-reverted.png, pdfdebugger-screenshot-trunc.png, 
> screenshot_debugger_new.png, screenshot_debugger_not_aligned.png, 
> screenshot_debugger_old.png, screenshot_w7_fontsize.png, 
> separate_filter_choice_from_text_hex_views.diff, sonar_qube_resolve.diff, 
> sonar_qube_resolve_25_08.diff
>
>
> This is a follow-up issue to PDFBOX-2530 to implement extra ideas that came 
> up in GSoC2015, ideas that were not implemented due to lack of time, and new 
> ideas.
> *Viewing*
>  - refactor PDFDebugger.java
>  - ✓ render glyphs of fonts
>  - ✓ refactor StreamPane to share stream filtering among Text view and hex 
> view
>  - ✓ password dialog when hitting protected PDF
>  - show "pretty" XML
>  - display filtered streams even if the unfiltered stream is corrupt 
> (PDFBOX-2976)
>  - ✓ display the "caused by" part exception stack trace (nested exceptions)
>  - ✓ keep zoom
>  - ✓ integrate DrawPrintTextLocations into rendering
>  - integrate area text extraction with a mouse-created rectangle that shows 
> the coordinates in a status line
>  - ✓ show permission flags of {{Encrypt/P}} entry
>  - ✓ show signature flags of {{Root/AcroForm/SigFlags}} entry, see Table 219 
> in PDF spec
>  - ✓ show page labels additional to page number (see file from TIKA-2121 as 
> example)
>  - ✓ "reopen" menu item (useful when editing an existing PDF to create a 
> reduced PDF)
>  - choose zoom automatically so that PDF page can be seen in full
> *Editing*
>  - save modified PDFs
>  - editing in hex viewer
>  - remove nodes (e.g. elements from a COSDictionary)
>  - delete array or dictionary elements
>  - load content streams
>  - edit & keep content streams



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2941) Improve PDFDebugger (2)

2021-04-28 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334841#comment-17334841
 ] 

ASF subversion and git services commented on PDFBOX-2941:
-

Commit 1889269 from Tilman Hausherr in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1889269 ]

PDFBOX-2941: don't abort if there's an exception when rendering a glyph; remove 
unneeded code

> Improve PDFDebugger (2)
> ---
>
> Key: PDFBOX-2941
> URL: https://issues.apache.org/jira/browse/PDFBOX-2941
> Project: PDFBox
>  Issue Type: Improvement
>  Components: Utilities
>Affects Versions: 2.0.0
>Reporter: Tilman Hausherr
>Priority: Major
> Attachments: gs-bugzilla694570.pdf, keep_zoom.diff, osx-tabs.png, 
> pdfdebugger-screenshot-reverted.png, pdfdebugger-screenshot-trunc.png, 
> screenshot_debugger_new.png, screenshot_debugger_not_aligned.png, 
> screenshot_debugger_old.png, screenshot_w7_fontsize.png, 
> separate_filter_choice_from_text_hex_views.diff, sonar_qube_resolve.diff, 
> sonar_qube_resolve_25_08.diff
>
>
> This is a follow-up issue to PDFBOX-2530 to implement extra ideas that came 
> up in GSoC2015, ideas that were not implemented due to lack of time, and new 
> ideas.
> *Viewing*
>  - refactor PDFDebugger.java
>  - ✓ render glyphs of fonts
>  - ✓ refactor StreamPane to share stream filtering among Text view and hex 
> view
>  - ✓ password dialog when hitting protected PDF
>  - show "pretty" XML
>  - display filtered streams even if the unfiltered stream is corrupt 
> (PDFBOX-2976)
>  - ✓ display the "caused by" part exception stack trace (nested exceptions)
>  - ✓ keep zoom
>  - ✓ integrate DrawPrintTextLocations into rendering
>  - integrate area text extraction with a mouse-created rectangle that shows 
> the coordinates in a status line
>  - ✓ show permission flags of {{Encrypt/P}} entry
>  - ✓ show signature flags of {{Root/AcroForm/SigFlags}} entry, see Table 219 
> in PDF spec
>  - ✓ show page labels additional to page number (see file from TIKA-2121 as 
> example)
>  - ✓ "reopen" menu item (useful when editing an existing PDF to create a 
> reduced PDF)
>  - choose zoom automatically so that PDF page can be seen in full
> *Editing*
>  - save modified PDFs
>  - editing in hex viewer
>  - remove nodes (e.g. elements from a COSDictionary)
>  - delete array or dictionary elements
>  - load content streams
>  - edit & keep content streams



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-4892) Improve code quality (4)

2021-04-28 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/PDFBOX-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334838#comment-17334838
 ] 

ASF subversion and git services commented on PDFBOX-4892:
-

Commit 1889268 from Tilman Hausherr in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1889268 ]

PDFBOX-4892: improve log msg

> Improve code quality (4)
> 
>
> Key: PDFBOX-4892
> URL: https://issues.apache.org/jira/browse/PDFBOX-4892
> Project: PDFBox
>  Issue Type: Improvement
>Affects Versions: 2.0.20
>Reporter: Tilman Hausherr
>Priority: Minor
>
> This is a longterm issue for the task to improve code quality, by using the 
> [SonarQube report|https://sonarcloud.io/project/issues?id=pdfbox-reactor], 
> hints in different IDEs, the FindBugs tool and other code quality tools.
> This is a follow-up of PDFBOX-4071, which was getting too long.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org



[jira] [Commented] (PDFBOX-2602) Enhance command line tools

2021-04-28 Thread Jira


[ 
https://issues.apache.org/jira/browse/PDFBOX-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334784#comment-17334784
 ] 

Jakov Vežić commented on PDFBOX-2602:
-

With the latest snapshot I get 
{code:java}
Exception in thread "main" picocli.CommandLine$InitializationException: Could 
not inject spec
at 
picocli.CommandLine$Model$CommandReflection.initFromAnnotatedTypedMembers(CommandLine.java:11532)
at 
picocli.CommandLine$Model$CommandReflection.initFromAnnotatedFields(CommandLine.java:11466)
at 
picocli.CommandLine$Model$CommandReflection.extractCommandSpec(CommandLine.java:11399)
at 
picocli.CommandLine$Model$CommandSpec.forAnnotatedObject(CommandLine.java:6202)
at picocli.CommandLine.(CommandLine.java:227)
at picocli.CommandLine.toCommandLine(CommandLine.java:3517)
at picocli.CommandLine.addSubcommand(CommandLine.java:373)
at picocli.CommandLine.addSubcommand(CommandLine.java:354)
at org.apache.pdfbox.tools.PDFBox.main(PDFBox.java:51)
Caused by: picocli.CommandLine$PicocliException: Could not get scope for field 
picocli.CommandLine$Model$CommandSpec 
org.apache.pdfbox.debugger.PDFDebugger.spec
at picocli.CommandLine$Model$FieldBinding.set(CommandLine.java:11662)
... 9 more
Caused by: picocli.CommandLine$InitializationException: Could not instantiate 
class org.apache.pdfbox.debugger.PDFDebugger: 
java.lang.reflect.InvocationTargetException
at picocli.CommandLine$DefaultFactory.create(CommandLine.java:5516)
at 
picocli.CommandLine$Model$CommandUserObject.getInstance(CommandLine.java:11813)
at 
picocli.CommandLine$Model$CommandUserObject.get(CommandLine.java:11838)
at picocli.CommandLine$Model$FieldBinding.set(CommandLine.java:11661)
... 9 more
Caused by: java.lang.reflect.InvocationTargetException
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at picocli.CommandLine$DefaultFactory.create(CommandLine.java:5491)
at picocli.CommandLine$DefaultFactory.create(CommandLine.java:5512)
... 12 more
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which 
requires it.
at 
java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208)
at java.desktop/java.awt.Window.(Window.java:548)
at java.desktop/java.awt.Frame.(Frame.java:423)
at java.desktop/java.awt.Frame.(Frame.java:388)
at java.desktop/javax.swing.JFrame.(JFrame.java:180)
at org.apache.pdfbox.debugger.PDFDebugger.(PDFDebugger.java:208)
... 18 more

{code}
no matter which command I run.

> Enhance command line tools
> --
>
> Key: PDFBOX-2602
> URL: https://issues.apache.org/jira/browse/PDFBOX-2602
> Project: PDFBox
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.8.8, 2.0.0
>Reporter: Maruan Sahyoun
>Assignee: Maruan Sahyoun
>Priority: Minor
> Fix For: 3.0.0 PDFBox
>
>
> The command line tools shall be enhanced to have the same behavior across all 
> tools.
> From the discussion on the dev mailing list
> - add an -h option to print the usage
> - print the usage to System.err and use an exit code of 1 if there was an 
> invalid command line parameter
> - print messages on exceptions to System.err
> - rethrow the exception so java can handle it if it will terminate afterwards 
> anyway
> - use an exit code of 1if rethrowing doesn't make sense
> Additional input:
> https://clig.dev/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org